Network fault recovery method, device, system, electronic device and storage medium

Abstract

The present disclosure provides a network fault recovery method, device, system, electronic device and computer-readable storage medium, which relates to the field of network technology and security technology. The method includes: a transmission node receives a data packet, matches the destination address in the data packet with the SID, obtains the behavior information corresponding to the SID matching the destination address, determines the new destination address according to the behavior information, and determines whether the new destination address is reachable. If not, parses the TLV field, obtains the backup transmission node address information corresponding to the protected transmission node, updates the backup transmission node address information to the new destination address, and transmits the data packet according to the new destination address. The embodiments of the present disclosure can save resources, efficiently recover network faults, and ensure the reliability of network operation.

Description

Background Art

[0002] In traditional IP networks, a link failure or node failure can cause a sudden interruption of traffic, thus affecting the user experience. The commonly used fault recovery method requires the router to recalculate the route and provide a recovery path after detecting a link or node failure. The whole process takes several seconds and is not suitable for latency-sensitive services. The backup path calculated in advance is stored in the upstream node of the protected node. Once the protected node fails, the upstream node immediately starts the backup path. This solution may cause the routing table to be too large and difficult to maintain.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The present disclosure provides a network fault recovery method, device, system, electronic device and computer-readable storage medium, which at least to some extent overcome the problem of low efficiency of network fault recovery in related technologies.

[0005] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0006] According to one aspect of the present disclosure, a network fault recovery method is provided, which is applied to a transmission node and includes:

[0007] Receive a data packet, match the destination address in the data packet with the segment identifier SID, determine a new destination address, and determine whether the new destination address is reachable;

[0008] If not, parse the type-length-value TLV field to obtain the backup transmission node address information corresponding to the protected transmission node, update the backup transmission node address information to the new destination address, and transmit the data packet according to the new destination address.

[0009] In one embodiment of the present disclosure, if the destination address in the data packet is matched with the segment identifier SID, a new destination address is determined, and whether the new destination address is reachable is determined, including:

[0010] Receive a data packet, match a destination address in the data packet with a segment identifier SID, and obtain behavior information corresponding to the SID;

[0011] Determine a new destination address based on the behavior information;

[0012] Determine whether the new destination address is reachable.

[0013] In one embodiment of the present disclosure, the TLV field includes the protected transmission node address information and the backup transmission node address information.

[0014] In one embodiment of the present disclosure, the fragment list includes a plurality of SIDs, each of which includes a location identifier, the behavior information, and a backup path processing parameter.

[0015] In one embodiment of the present disclosure, determining whether the new destination address is reachable includes:

[0016] Whether the new destination address is reachable is determined according to the location identifier, wherein the location identifier includes a network address prefix of the transmission node.

[0017] In one embodiment of the present disclosure, the behavior information includes at least one of the following:

[0018] Transmitting nodes do not process packets;

[0019] Check whether the new destination address is reachable. If so, forward the packet normally. Otherwise, parse the packet to obtain the backup transmission node address information.

[0020] Check whether the new destination address is reachable. If so, forward it normally. Otherwise, parse the data packet and select the backup transmission node address information through the backup path processing parameters.

[0021] In one embodiment of the present disclosure, it also includes:

[0022] When it is determined that the new destination address is reachable, the data packet is transmitted according to the new destination address.

[0023] In one embodiment of the present disclosure, it also includes:

[0024] Encapsulate data packets according to the instructions issued by the controller;

[0025] The destination address in the data packet is obtained according to the value of the initialized segment routing pointer Segment Left.

[0026] According to another aspect of the present disclosure, there is also provided a network fault recovery device, comprising:

[0027] Receive a data packet, match the destination address in the data packet with the segment identifier SID, determine a new destination address, and determine whether the new destination address is reachable;

[0028] If not, parse the type-length-value TLV field to obtain the backup transmission node address information corresponding to the protected transmission node, update the backup transmission node address information to the new destination address, and transmit the data packet according to the new destination address.

[0029] According to another aspect of the present disclosure, a network fault recovery system is also provided, including:

[0030] Backup path policy library, which stores the relevant policies of transmission nodes and paths;

[0031] Network topology information database, which stores network topology information and makes dynamic adjustments based on actual conditions;

[0032] The network fault fast recovery module provides backup paths for transmission nodes and paths in the network according to the backup requirements in the backup path policy library and the actual situation of the network topology, and encapsulates them into data packets and distributes them to the data network;

[0033] The backup path library stores the backed-up path information.

[0034] According to another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned network fault recovery methods by executing the executable instructions.

[0035] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the network failure recovery method described in any one of the above is implemented.

[0036] The network fault recovery method, device, system, electronic device and computer-readable storage medium provided by the embodiments of the present disclosure, a transmission node receives a data packet, matches the destination address in the data packet with the SID, obtains behavior information corresponding to the SID matching the destination address, determines a new destination address based on the behavior information, and determines whether the new destination address is reachable. If not, the TLV field is parsed to obtain the backup transmission node address information corresponding to the protected transmission node, and the backup transmission node address information is updated to the new destination address. The data packet is transmitted according to the new destination address, which can save resources, efficiently recover from network faults, and ensure the reliability of network operation.

[0037] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0039] Figure 1 A flow chart of a network failure recovery method in an embodiment of the present disclosure is shown;

[0040] Figure 2 A flowchart of another network failure recovery method in an embodiment of the present disclosure is shown;

[0041] Figure 3 A schematic diagram of a normal forwarding data packet in an embodiment of the present disclosure is shown;

[0042] Figure 4 A schematic diagram of starting a backup path to forward data packets in an embodiment of the present disclosure is shown;

[0043] Figure 5 A schematic diagram of a network fault recovery device in an embodiment of the present disclosure is shown;

[0044] Figure 6 A schematic diagram of a network fault recovery system in an embodiment of the present disclosure is shown; and

[0045] Figure 7 A structural block diagram of an electronic device in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0046] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0047] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0048] For ease of understanding, several terms involved in the present disclosure are explained below:

[0049] SR (Segment Routing) has a stateless characteristic. The source node selects the path and guides the message to be transmitted along the path. Other nodes do not need to maintain any flow-related information.

[0050] IPv6 (Internet Protocol Version 6).

[0051] SRv6 (Segment Routing Over IPv6, SR technology based on IPv6 forwarding plane) is a combination of SR technology and IPv6 technology.

[0052] SRH (Segment Routing Header) stores the IPv6 Segment List information, determines the IPv6 destination address information based on Segments Left and Segment List, and guides the message path and behavior.

[0053] TLV (Type-Length-Value) is an editable field.

[0054] The present exemplary implementation is described in detail below with reference to the accompanying drawings and embodiments.

[0055] First, a network failure recovery method is provided in an embodiment of the present disclosure. The method can be executed by any electronic device with computing and processing capabilities.

[0056] Figure 1 A flow chart of a network failure recovery method according to an embodiment of the present disclosure is shown as follows: Figure 1 As shown, the network fault recovery method provided in the embodiment of the present disclosure includes the following steps:

[0057] S102, receiving a data packet, matching a destination address in the data packet with a segment identifier SID, and acquiring behavior information corresponding to the SID.

[0058] In one embodiment, the segment list includes multiple SIDs, each SID includes a location identifier, behavior information, and backup path processing parameters.

[0059] It should be noted that the location identifier is the network address prefix of the transit node, making the node routable and reachable;

[0060] Behavior information is used to define the processing action for the data packet;

[0061] Backup path processing parameters are used for backup path processing parameters.

[0062] In one embodiment, the behavior information may include:

[0063] Transmitting nodes do not process packets;

[0064] Check whether the new destination address is reachable. If so, forward the packet normally. Otherwise, parse the packet to obtain the backup transmission node address information.

[0065] Check whether the new destination address is reachable. If so, forward it normally. Otherwise, parse the data packet and select the backup transmission node address information through the backup path processing parameters.

[0066] S104: Determine a new destination address according to the behavior information.

[0067] In one embodiment, a data packet is encapsulated according to an instruction sent by a controller; and a destination address in the data packet is obtained according to a value of an initialized segment routing pointer Segment Left.

[0068] S106, determining whether the new destination address is reachable.

[0069] In one embodiment, whether the new destination address is reachable is determined based on a location identifier, wherein the location identifier includes a network address prefix of the transmission node.

[0070] S108: If not, obtain the backup transmission node address information, update the backup transmission node address information to a new destination address, and transmit the data packet according to the new destination address.

[0071] In one embodiment, the type-length-value TLV field is parsed to obtain the backup transmission node address information corresponding to the protected transmission node.

[0072] In one embodiment, the TLV field includes information of the protected transmission node and the backup transmission node, for example, address information of the protected transmission node and the backup transmission node;

[0073] In one embodiment, the lengths of the information of the protected transmission node and the backup transmission node are defined as needed. For example, the lengths of the information of the protected transmission node and the backup transmission node are 64 bits respectively.

[0074] In one embodiment, when it is determined that the new destination address is reachable, the data packet is transmitted according to the new destination address.

[0075] In the above embodiment, based on the SRv6 protocol, the TLV field is customized and utilized, and then the SID is defined for the fault handling action. The source routing technology advantage of the customized forwarding of the SRv6 protocol is used to achieve rapid recovery of network failures, including node failures and link failures, save space in the routing table, and improve the overall reliability of the network.

[0076] Figure 2 A flowchart of another network failure recovery method in an embodiment of the present disclosure is shown. Figure 2 As shown, the network fault recovery method provided in the embodiment of the present disclosure includes the following steps:

[0077] S202: Build an SRv6 packet header in a certain order, and pack the SID values ​​of the transmission nodes on the primary path into the Segment List.

[0078] It should be noted that Segment Routing (SR) has a stateless characteristic. The source node selects the path and guides the message to be transmitted along the path. Other nodes do not need to maintain any flow-related information. The segment routing architecture is not based on a specific data plane implementation and can be applied in MPLS and IPv6. Because the IPv6 header has the characteristics of flexible programmability and address scalability, by defining SRH in the IPv6 header, segment routing technology can be applied to the IPv6 data plane, which is called "SRv6". The segment routing architecture is based on source routing, and the control policy is sent down to the specified network device through the controller, making it the best technical choice for the deployment of ultra-large-scale traffic engineering on network devices.

[0079] Table 1 is a data structure table of the SRv6 header field. The header of the SRv6 data packet is an SRH packet added after the original IPv6 header, as shown in Table 1:

[0080] Table 1 SRv6 packet header field data structure

[0081]

[0082] Among them, in the IPv6 header field:

[0083] Version number: 4 bits, ipv6 is 6;

[0084] Traffic Class: 8 bits, used to mark traffic for easy priority distinction and policy making;

[0085] Flow Label: 20 bits, used with Traffic Class;

[0086] Payload Length: 16 bits, the payload length of the IPv6 data packet, which refers to the length of the data content after the header, including the extension header.

[0087] Next Header: 8 bits, indicating which extension header or protocol type in the upper layer protocol follows the basic header;

[0088] Hop Limit: 8 bits. IPv6 uses the number of times a packet is forwarded between routers to limit the lifetime of a packet. Each time a packet is forwarded, this field is reduced by 1. When it reaches 0, the packet is discarded.

[0089] Source Address: 128 bits, sender host address;

[0090] Destination Address: 128 bits. In most cases, the destination address is the destination address. However, if there is a routing extension header, the destination address may be the next router interface in the sender's routing table.

[0091] Among them, in the SR header field:

[0092] Next Header;

[0093] Extension header length Hdr Ext Len: 8 bits refers to the length of the hop-by-hop option extension header, which does not include the NextHeader length;

[0094] Routing Type: 8 bits, refers to a specific routing header variable. Currently, only type 0 is defined for routing type, which contains the IP address of the intermediate router that the message needs to pass through.

[0095] Segment routing pointer Segment Left: refers to the number of intermediate routes that need to be passed before reaching the final destination.

[0096] It should be noted that the SRv6 packet header data structure has an IPv6 packet header at the front, followed by an SR packet header. The fields of the IPv6 packet header are not modified or adjusted. The Option TLVs field in the SRH part of the SR packet header is redefined and utilized. This field has a variable length, as shown in Table 2.

[0097] Table 2 Option TLVs field definition table

[0098] 0-63 bits 64-bit - 128-bit Address information of the protected transmission node Backup transmission node address information

[0099] In the Optional TLVs field, the first 64 bits are defined as "protected transmission node" to identify the IPv6 address information of the protected node; the last 64 bits are defined as "backup transmission node" to identify the IPv6 address information of the backup transmission node.

[0100] Each value in the Segment List field is a 128-bit SID. The definition of SID in the SRv6 protocol is shown in Table 3.

[0101] Table 3 SID definition table

[0102] Locator Function Args

[0103] The location identifier Locator field is the network address prefix of the transmission node, making the node reachable by route; the behavior information Function is used to define the processing action for the data packet, and the backup path processing parameter Args is used for the backup path processing parameter.

[0104] In an embodiment, in an actual application, parameters such as the backup path priority may be designed according to the importance of the protected transmission node.

[0105] In one embodiment, Table 4 defines the following Function:

[0106] Table 4 Function definition table

[0107]

[0108] It should be noted that each transmission node has multiple SIDs. In SRv6, each Segment is identified by SID. SID is a special IPv6 address that has both the routing capability of a common IPv6 address and the behavior capability unique to SRv6. The encapsulated SID contains the Function action and the Args parameter that require this transmission node to process the data packet.

[0109] S204: Write the IPv6 address of the backup node and the IPv6 address of the protected node into the TLV field according to the pre-selected backup path.

[0110] S206, the network controller packages the SRH header and the data packet into an IPv6 packet header and sends it to these nodes, with the target address being the SID value of the first node.

[0111] In one embodiment, after the receiver obtains the data packet, it first checks whether the next-hop IPv6 address is reachable according to the Loactor. If it is reachable, the data packet is forwarded according to the Segment Left address, that is, no fault occurs. If the next-hop IPv6 address is unreachable, it means that a fault occurs, then the TLV field is parsed, the protected transmission node is found to be the backup transmission node IPv6 address corresponding to the faulty node, and the next-hop IPv6 address is modified to ensure normal communication of the service.

[0112] In the above embodiment, the TLV field is expanded and effectively utilized, and then the SID is defined for the fault handling action. The source routing mechanism of the SRv6 protocol customized routing forwarding is fully utilized to achieve rapid recovery from both node failures and link failures, thereby improving the overall reliability of the network.

[0113] Figure 3 A schematic diagram of a normal forwarding data packet in an embodiment of the present disclosure is shown as follows: Figure 3As shown, in this example, the main path is the first transmission node 301-the second transmission node 302-the third transmission node 303-the fifth transmission node 305, the backup route is the first transmission node 301-the second transmission node 302-the fourth transmission node 304-the fifth transmission node 305, the protected transmission node is the third transmission node 303, and the backup transmission node is the fourth transmission node 304.

[0114] It should be noted that there are two key information in SRH. The first is the Segment List in the form of IPv6 address. The Segment List is arranged in order to form an explicit path in SRv6. The other key field is SegmentLeft (SL). Segment Left is a pointer that indicates the currently active Segment List. The minimum value of Segment Left is 0, and the maximum value is the number of Segment Lists minus 1. Segment Lists are pushed onto the stack in reverse order, which means that the bottom Segment List [2] is the first Segment List to be processed, the middle Segment List [1] is the second Segment List to be processed, and the top Segment List [0] is the last Segment List to be processed.

[0115] In SRv6, the IPv6 destination address field is a constantly changing field. Its value is determined by the Segment Left field and the following Segment List. When the pointer Segment Left points to an active segment, such as Segment List[2], the IPv6 address of Segment List[2] needs to be copied to the IPv6 destination address field.

[0116] The first transmission node 301 operates as follows: encapsulates the data packet according to the instruction sent by the controller, initializes the Segment Left value to 2, and the outer IPv6 destination address is A2:22;

[0117] The second transmission node 302 operates as follows: receiving the data packet, extracting the target IPv6 address and matching it with its own SID, and executing the corresponding operation after matching. For example, if Function is END.BP1, it searches for a route with a Segment Left value of 1 and a destination IPv6 address of A3:33. If the route is reachable, it updates the destination IP address to the third transmission node 303.

[0118] The third transmission node 303 operates as follows: receiving the data packet, extracting the target IPv6 address and matching it with its own SID, and executing the corresponding operation after matching. For example, if Function is END.BP0, it searches for a route with a Segment Left value of 0 and a destination IPv6 address of A5:55. If the route is reachable, it updates the destination IP address to the fifth transmission node 305.

[0119] The fifth transmission node 305 operates by accepting a data packet.

[0120] Figure 4 A schematic diagram of starting a backup path to forward data packets in an embodiment of the present disclosure is shown. Figure 4 As shown, in this example, the main path is the first transmission node 401-the second transmission node 402-the third transmission node 403-the fifth transmission node 405, the backup route is the first transmission node 401-the second transmission node 402-the fourth transmission node 404-the fifth transmission node 405, the protected transmission node is the third transmission node 403, and the backup transmission node is the fourth transmission node 404. When the third transmission node 403 or the link between the third transmission node 403 and the second transmission node 402 fails, the backup path is started to forward data packets as shown in the following figure:

[0121] The first transmission node 401 operates as follows: encapsulates the data packet according to the instruction sent by the controller, initializes the Segment Left value to 2, and the outer IPv6 destination address is A2:22;

[0122] The second transmission node 402 operates as follows: accepting data packets, extracting the target IPv6 address and matching it with its own SID. If a match is found, the corresponding operation is performed. For example, if Function is END.BP1, a route with a Segment Left value of 1 and a destination IPv6 address of A3:33 is searched. If the route is unreachable, the TLV field is parsed to obtain the next-hop address of the backup path as the fourth transmission node 404, and the destination IP is updated.

[0123] The fourth transmission node 404 operates as follows: receiving the data packet, extracting the target IPv6 address and matching it with its own SID, and after a match, executing the corresponding operation action. If Function is END.BP0, the destination IP is updated to be the fifth transmission node 405;

[0124] The fifth transmission node 405 operates by accepting a data packet.

[0125] In the above embodiment, based on the SRv6 protocol, the TLV field is customized and utilized, and then the SID is defined for the fault handling action. It has the characteristics of simple deployment and flexible expansion, can better realize traffic scheduling and path optimization, and greatly improve the utilization rate of network bandwidth. The source routing technology advantage of customized forwarding of the SRv6 protocol is used to achieve rapid recovery of network failures, including node failures and link failures, and save space in the routing table, thereby improving the overall reliability of the network. It has broad application prospects in the fields of network communications, wide area virtual private networks and other fields.

[0126] Based on the same inventive concept, the present disclosure also provides a network fault recovery device, such as the following embodiment. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0127] Figure 5 A schematic diagram of a network failure recovery device in an embodiment of the present disclosure is shown. Figure 5 As shown, the network fault recovery device 5 includes: a new address determination module 501, a backup address acquisition module 502;

[0128] The new address determination module 501 receives a data packet, matches the destination address in the data packet with the segment identifier SID, determines a new destination address, and determines whether the new destination address is reachable;

[0129] If not, the backup address acquisition module 502 parses the type-length-value TLV field to acquire the backup transmission node address information corresponding to the protected transmission node, updates the backup transmission node address information to the new destination address, and transmits the data packet according to the new destination address.

[0130] In the above embodiment, based on the SRv6 protocol, the TLV field is customized and utilized, and then the SID is defined for the fault handling action. The source routing technology advantage of the customized forwarding of the SRv6 protocol is used to achieve rapid recovery of network failures, including node failures and link failures, save space in the routing table, and improve the overall reliability of the network.

[0131] Based on the same inventive concept, the present disclosure also provides a network fault recovery system, such as the following embodiment. Since the principle of solving the problem in the system embodiment is similar to that in the above method embodiment, the implementation of the system embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0132] Figure 6 A schematic diagram of a network fault recovery system in an embodiment of the present disclosure is shown. Figure 6 As shown, the network fault recovery system 6 includes: a backup path policy library 601, a network topology information library 602, a network fault fast recovery module 603, a backup path library 604 and a network communication interface 605;

[0133] Backup path strategy database 601, which stores the relevant strategies for protecting key nodes and paths. The network failure fast recovery module will calculate different backup paths according to the strategies;

[0134] Network topology information database 602, which stores network topology information persistently and makes dynamic adjustments based on actual conditions;

[0135] The network fault fast recovery module 603 is currently the core unit, responsible for providing backup paths for key nodes and paths in the network according to the actual network topology and the backup requirements in the backup path policy library, and encapsulating them into a series of SRv6 data packets and distributing them to the data network;

[0136] The backup path database 604 stores the backed-up path information. The network failure fast recovery module generates a corresponding SRv6 data packet based on the backup information and sends it to the corresponding device.

[0137] In the above embodiment, the TLV field is expanded and effectively utilized, and then the SID is defined for the fault handling action. The source routing mechanism of the SRv6 protocol customized routing forwarding is fully utilized to achieve rapid recovery from both node failures and link failures, thereby improving the overall reliability of the network.

[0138] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0139] Refer to the following Figure 7 An electronic device 700 according to this embodiment of the present disclosure is described. Figure 7 The electronic device 700 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0140] like Figure 7 As shown, the electronic device 700 is in the form of a general computing device. The components of the electronic device 700 may include but are not limited to: at least one processing unit 710, at least one storage unit 720, and a bus 730 connecting different system components (including the storage unit 720 and the processing unit 710).

[0141] The storage unit stores program codes, which can be executed by the processing unit 710, so that the processing unit 710 executes the steps described in the above “exemplary method” section of this specification according to various exemplary embodiments of the present disclosure.

[0142] For example, the processing unit 710 can execute the following steps of the above-mentioned method embodiment: the transmission node receives the data packet, matches the destination address in the data packet with the SID, obtains the behavior information corresponding to the SID matching the destination address, determines the new destination address based on the behavior information, and determines whether the new destination address is reachable. If not, parses the TLV field, obtains the backup transmission node address information corresponding to the protected transmission node, updates the backup transmission node address information to the new destination address, and transmits the data packet according to the new destination address.

[0143] For example, the processing unit 710 can execute the following steps of the above method embodiment: construct the SRv6 packet header in a certain order, and pack the SID value of the transmission node on the main path into the Segment List; S204, according to the pre-selected backup path, write the IPv6 address of the backup node and the IPv6 address of the protected node into the TLV field; the network controller packs the SRH header and the data packet into the IPv6 packet header and sends it to these nodes, and the target address is the SID value of the first node.

[0144] For example, the processing unit 710 may perform the following steps of the above method embodiment: after the receiving party obtains the data packet, it first checks whether the next-hop IPv6 address is reachable according to the Loactor. If it is reachable, the data packet is forwarded according to the Segment Left address, that is, no fault occurs. If the next-hop IPv6 address is unreachable, it means that a fault occurs, then the TLV field is parsed, the protected transmission node is found to be the backup transmission node IPv6 address corresponding to the faulty node, the next-hop IPv6 address is modified, and the normal communication of the service is guaranteed.

[0145] The storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 7201 and / or a cache storage unit 7202 , and may further include a read-only storage unit (ROM) 7203 .

[0146] The storage unit 720 may also include a program / utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0147] Bus 730 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0148] The electronic device 700 may also communicate with one or more external devices 740 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the electronic device 700, and / or any device that enables the electronic device 700 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed through an input / output (I / O) interface 750.

[0149] Furthermore, the electronic device 700 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and / or public network, such as the Internet) through a network adapter 760. As shown, the network adapter 760 communicates with other modules of the electronic device 700 through a bus 730. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0150] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0151] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. A program product capable of implementing the above method of the present disclosure is stored thereon. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above “Exemplary Method” section of this specification.

[0152] For example, when the program product in the embodiment of the present disclosure is executed by a processor, the method implements the following steps: the transmission node receives a data packet, matches the destination address in the data packet with the SID, obtains behavior information corresponding to the SID matching the destination address, determines a new destination address based on the behavior information, and determines whether the new destination address is reachable; if not, parses the TLV field, obtains the backup transmission node address information corresponding to the protected transmission node, updates the backup transmission node address information to the new destination address, and transmits the data packet according to the new destination address.

[0153] For example, when the program product in the embodiment of the present disclosure is executed by a processor, the following steps are implemented: constructing the SRv6 packet header in a certain order, and packaging the SID value of the transmission node on the main path into the Segment List; S204, according to the pre-selected backup path, write the IPv6 address of the backup node and the IPv6 address of the protected node into the TLV field; the network controller packages the SRH header and the data packet into the IPv6 packet header and sends it to these nodes, and the target address is the SID value of the first node.

[0154] For example, when the program product in the embodiment of the present disclosure is executed by the processor, the following steps are implemented: after the receiving party obtains the data packet, it first checks whether the next-hop IPv6 address is reachable according to the Loactor. If it is reachable, the data packet is forwarded according to the Segment Left address, that is, no fault occurs. If the next-hop IPv6 address is unreachable, it means that a fault has occurred, then the TLV field is parsed, the IPv6 address of the backup transmission node corresponding to the protected transmission node corresponding to the faulty node is found, and the next-hop IPv6 address is modified to ensure normal communication of the service.

[0155] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0156] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0157] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0158] In specific implementations, program codes for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages, such as Java, C++, etc., and conventional procedural programming languages, such as "C" or similar programming languages. The program codes may be executed entirely on the user computing device, partially on the user computing device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0159] Where a remote computing device is involved, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0160] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0161] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0162] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0163] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A network failure recovery method, characterized in that: Applied to transport nodes, including: Receive a data packet, match the destination address in the data packet with the segment identifier SID, determine a new destination address, and judge whether the new destination address is reachable; wherein the SID includes behavior information; the behavior information includes at least one of the following: the transmission node does not process the data packet; checks whether the new destination address is reachable, and if so, forwards it normally, otherwise parses the data packet to obtain the backup transmission node address information; checks whether the new destination address is reachable, and if so, forwards it normally, otherwise parses the data packet to select the backup transmission node address information through the backup path processing parameter; If not, parse the type-length-value TLV field to obtain the backup transmission node address information corresponding to the protected transmission node, update the backup transmission node address information to the new destination address, and transmit the data packet according to the new destination address.

2. The network failure recovery method according to claim 1, characterized in that: If the destination address in the data packet is matched with the segment identifier SID, a new destination address is determined, and whether the new destination address is reachable includes: Receive a data packet, match a destination address in the data packet with a segment identifier SID, and obtain behavior information corresponding to the SID; Determine a new destination address based on the behavior information; Determine whether the new destination address is reachable.

3. The network failure recovery method according to claim 1, characterized in that: The TLV field includes the protected transmission node address information and the backup transmission node address information.

4. The network failure recovery method according to claim 2, characterized in that: The segment list includes a plurality of the SIDs, and each of the SIDs further includes a location identifier and a backup path processing parameter.

5. The network failure recovery method according to claim 2, characterized in that: The determining whether the new destination address is reachable includes: Whether the new destination address is reachable is determined according to the location identifier, wherein the location identifier includes a network address prefix of the transmission node.

6. The network failure recovery method according to claim 1, characterized in that: Also includes: When it is determined that the new destination address is reachable, the data packet is transmitted according to the new destination address.

7. The network failure recovery method according to claim 1, characterized in that: Also includes: Encapsulate data packets according to the instructions issued by the controller; The destination address in the data packet is obtained according to the value of the initialized segment routing pointer Segment Left.

8. A network failure recovery device, characterized in that: include: A new address determination module receives a data packet, matches the destination address in the data packet with the segment identifier SID, determines a new destination address, and determines whether the new destination address is reachable; wherein the SID includes behavior information; the behavior information includes at least one of the following: the transmission node does not process the data packet; checks whether the new destination address is reachable, and if so, forwards it normally, otherwise parses the data packet to obtain the backup transmission node address information; checks whether the new destination address is reachable, and if so, forwards it normally, otherwise parses the data packet to select the backup transmission node address information through the backup path processing parameters; The backup address acquisition module, if not, parses the type-length-value TLV field to obtain the backup transmission node address information corresponding to the protected transmission node, updates the backup transmission node address information to the new destination address, and transmits the data packet according to the new destination address.

9. A network fault recovery system, characterized in that: include: Backup path policy library, which stores the relevant policies of transmission nodes and paths; Network topology information database, which stores network topology information and makes dynamic adjustments based on actual conditions; The network fault fast recovery module provides backup paths for transmission nodes and paths in the network according to the backup requirements in the backup path policy library and the actual situation of the network topology, and encapsulates them into data packets and distributes them to the data network; Backup path library, storing the backed up path information; Wherein, the transmission node is used to execute the network fault recovery method described in any one of claims 1-7.

10. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the network failure recovery method according to any one of claims 1 to 7 by executing the executable instructions.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the network failure recovery method according to any one of claims 1 to 7 is implemented.

Images