NODE PROTECTION METHOD, DEVICE, ELECTRONIC DEVICE, AND MEDIUM

The SRv6-based node protection method and device facilitate rapid rerouting of service messages to reachable nodes in SRv6 networks, addressing delays and enhancing reliability by directly forwarding messages to backup paths when primary paths fail.

JP2024545522AActive Publication Date: 2024-12-09NEW H3C TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024536036
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2022-10-24
Publication Date
2024-12-09
Estimated Expiration
2042-10-24

AI Technical Summary

Technical Problem

Interactive multimedia services such as VoIP are highly sensitive to network packet losses and experience significant delays when a link or node failure occurs, typically taking hundreds of milliseconds to resume service transmission, which is not acceptable for real-time communication needs.

Method used

A node protection method and device that utilize Segment Routing IPv6 (SRv6) to quickly reroute service messages by changing the destination address to a backup SID when an endpoint node in the primary path becomes unreachable, allowing service messages to be forwarded directly to a reachable endpoint node without discarding and retransmitting over a backup path.

Benefits of technology

This approach reduces service delays and improves network reliability by enabling fast path switching and immediate forwarding of service messages upon node or link failures in SRv6 networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024545522000001_ABST
    Figure 2024545522000001_ABST
Patent Text Reader

Abstract

The present application provides a node protection method, device, electronic device, and medium, and relates to the field of communication technology. The node protection method includes: acquiring a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including an SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for transferring the first service message; transferring a second service message to an endpoint node indicated in the backup SID, the second service message including a destination address, the destination address being changed to the backup SID after it is determined that all endpoint nodes in the primary path are unreachable endpoint nodes and that the endpoint node indicated in the backup SID is a reachable endpoint node. According to the present invention, it is possible to reduce a service delay when a failure occurs in a link or node.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present application relates to the field of communications technology, and in particular to a node protection method, device, electronic device, and medium. [Background technology]

[0002] For example, interactive multimedia service applications such as voice over Internet Protocol (VoIP) are very sensitive to network packet loss and generally can only tolerate a network packet loss of tens of milliseconds. However, when a link or node in the network fails, it usually takes hundreds of milliseconds to several seconds to resume service transmission, which cannot meet the needs of the service. Summary of the Invention

[0003] In view of the above, the present application provides a node protection method, device, electronic device, and medium for reducing service delay when a link or node failure occurs. Specific technical solutions are as follows:

[0004] In a first aspect, the present application provides a node protection method applied to a first node, the node protection method comprising: Obtaining a first service message sent from a second node, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including an SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; forwarding a second service message to an endpoint node indicated in the backup SID, the second service message including the destination address, the destination address being changed to the backup SID after it is determined that each endpoint node in the primary path indicated in the SID of each endpoint node is an unreachable endpoint node and that the endpoint node indicated in the backup SID is a reachable endpoint node.

[0005] In one possible embodiment, the SRH further includes a SL, and after obtaining the first service message, the node protection method includes: Obtaining a first SL based on a difference between a current SL and a fixed value, and obtaining a first SID corresponding to the first SL from the SID list; If the endpoint node indicated by the first SID is unreachable, the first SL is set as a current SL, and a process of acquiring a first SL according to a difference between the current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list is repeated until a first SID of an endpoint node that is reachable is acquired from the SID list; If the first SID of the reachable endpoint node is the backup SID, change the destination address to the backup SID to obtain the second service message; If the first SID of the reachable endpoint node is not the backup SID, change the destination address to the first SID of the reachable endpoint node to obtain a third service message, and forward the third service message to the endpoint node indicated by the first SID.

[0006] In one possible embodiment, after obtaining the first service message, the node protection method includes: If the destination address is an SID in which a specified additional behavior is configured, removing the IPv6 header and the SRH to obtain a fourth service message; and forwarding the fourth service message.

[0007] In one possible embodiment, the endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is a second node, and a BE path exists between the first node and the second node.

[0008] In one possible embodiment, the SID encapsulated in the penultimate element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is the backup SID.

[0009] In one possible embodiment, when the first node is a source node, obtaining the first service message includes: receiving a fifth service message; If a next hop of a routing table entry matching the fifth service message is an SRv6 policy and the SRv6 policy includes a primary path and a backup path, encapsulating the IPv6 header and the SRH in an outer layer of the fifth service message to obtain the first service message.

[0010] In a second aspect, the present application provides a node protection device for application to a first node, the node protection device comprising: An acquisition module used for acquiring a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including an SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; a sending module used to forward a second service message to an endpoint node indicated in the backup SID, the second service message including the destination address, the destination address being changed to the backup SID after it is determined that all endpoint nodes in the primary path are unreachable endpoint nodes and the endpoint node indicated in the backup SID is a reachable endpoint node; and

[0011] In one possible embodiment, the SRH further includes a SL, and the node protection device further includes a modification module; The acquisition module is further used for: acquiring a first SL based on a difference between a current SL and a fixed value, and acquiring a first SID corresponding to the first SL from the SID list; and if an endpoint node indicated by the first SID is unreachable, setting the first SL as a current SL, and repeating the process of acquiring a first SL based on a difference between a current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list until a first SID of an endpoint node that is reachable is acquired from the SID list; The change module is used for changing the destination address to the backup SID when the first SID of the reachable endpoint node is the backup SID to obtain the second service message; The modification module is further used for modifying the destination address to the first SID of the reachable endpoint node when the first SID of the reachable endpoint node is not the backup SID to obtain a third service message; The sending module is further used for forwarding the third service message to an endpoint node indicated in the first SID.

[0012] In one possible embodiment, the node protection device comprises: If the destination address is an SID in which a specified additional behavior is configured, the IPv6 header and the SRH are removed to obtain a fourth service message, and a removal module is further included. The sending module is further used for forwarding the fourth service message.

[0013] In one possible embodiment, the endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is a second node, and a BE path exists between the first node and the second node.

[0014] In one possible embodiment, the SID encapsulated in the penultimate element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is the backup SID.

[0015] In one possible embodiment, when the first node is a source node, the acquisition module specifically: receiving a fifth service message; If the next hop of a routing table entry matching the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulating the IPv6 header and the SRH in an outer layer of the fifth service message to obtain the first service message.

[0016] In a third aspect, the present application provides an electronic device, the electronic device comprising: A processor; A transceiver; a machine-readable storage medium storing machine-executable instructions executable by said processor; The machine executable instructions cause the processor to: Obtaining a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including an SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; forwarding a second service message to an endpoint node indicated by the backup SID, the second service message including the destination address, the destination address being changed to the backup SID after it is determined that all endpoint nodes in the primary path are unreachable endpoint nodes and that the endpoint node indicated by the backup SID is a reachable endpoint node.

[0017] In one possible embodiment, the SRH further includes a SL, and the machine executable instructions further include causing the processor to: Obtaining a first SL based on a difference between a current SL and a fixed value, and obtaining a first SID corresponding to the first SL from the SID list; If the endpoint node indicated by the first SID is unreachable, the first SL is set as a current SL, and a process of acquiring a first SL according to a difference between the current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list is repeated until a first SID of an endpoint node that is reachable is acquired from the SID list; If the first SID of the reachable endpoint node is the backup SID, change the destination address to the backup SID to obtain the second service message; if the first SID of the reachable endpoint node is not the backup SID, change the destination address to the first SID of the reachable endpoint node to obtain a third service message, and forward the third service message to the endpoint node indicated by the first SID.

[0018] In one possible embodiment, the machine executable instructions further include causing the processor to: If the destination address is an SID in which a specified additional behavior is configured, removing the IPv6 header and the SRH to obtain a fourth service message; and transmitting the fourth service message.

[0019] In one possible embodiment, the endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is a second node, and a BE path exists between the first node and the second node.

[0020] In one possible embodiment, the SID encapsulated in the penultimate element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is the backup SID.

[0021] In one possible embodiment, when the electronic device is a source node, the machine executable instructions specifically direct the processor to: receiving a fifth service message; If the next hop of a routing table entry matching the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulating the IPv6 header and the SRH in an outer layer of the fifth service message to obtain the first service message.

[0022] In a fourth aspect, embodiments of the present application provide a machine-readable storage medium storing machine-executable instructions, which when recalled and executed by a processor, cause the processor to implement a method according to the first aspect above.

[0023] In a fifth aspect, embodiments of the present application provide a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method according to the first aspect above.

[0024] According to the above technical solution, after the first node obtains the first service message, if it is determined that all the endpoint nodes in the primary path are unreachable endpoint nodes and the endpoint node indicated in the backup SID is a reachable endpoint node, the second service message can be forwarded to the endpoint node indicated in the backup SID. That is, when a failure occurs in a node or a link between nodes in the primary path, the first service message can be forwarded from the first node in the primary path to the endpoint node indicated in the backup SID without the need to discard packets and then resend the service message via the backup path. This can reduce service delays caused by node or link failures and improve network reliability. [Brief description of the drawings]

[0025] In order to more clearly describe the technical solutions of the embodiments of the present application and the prior art, the drawings necessary for the embodiments and the prior art will be briefly described below. Of course, the drawings described below are only a part of the embodiments of the present application, and those skilled in the art can obtain other embodiments based on these drawings without creative efforts. [Figure 1] Figure 1 is a schematic diagram of the SRv6SID format. [Diagram 2] Figure 2 is a schematic diagram of the SRv6 message format. [Diagram 3] FIG. 3 is an exemplary schematic diagram of an SRv6 message forwarding process. [Figure 4] FIG. 4 is a flowchart of a method for node protection provided in an embodiment of the present application. [Diagram 5] FIG. 5 is a schematic diagram of the SRH format provided in the present application. [Figure 6] FIG. 6 is a flowchart of another node protection method provided in an embodiment of the present application. [Figure 7] FIG. 7 is a schematic diagram of an application scenario provided in an embodiment of the present application. [Figure 8] FIG. 8 is a schematic diagram of another application scenario provided in an embodiment of the present application. [Figure 9] FIG. 9 is a schematic diagram of a node protection device provided in an embodiment of the present application. [Figure 10] FIG. 10 is a schematic diagram of the configuration of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be described in more detail below with reference to the drawings and examples. It is clear that the described examples are only some of the embodiments of the present invention, and are not all of the embodiments. Based on the embodiments of the present invention, all other embodiments that can be obtained by those skilled in the art without creative efforts are all included in the protection scope of the present invention.

[0027] For ease of understanding, the following will explain and explain the relevant concepts of the present embodiment.

[0028] 1. Overview of SRv6. Segment Routing (SR) employs a source node path selection mechanism that encapsulates the SID (Segment Identifier) ​​of the segment through which the forwarding path passes in advance at the source node, and when a message passes through the SR node, the SR node forwards the message according to the SID of the message. Nodes other than the source node do not need to maintain the path state.

[0029] Segment Routing IPv6 (SRv6) refers to the realization of SR based on the IPv6 forwarding plane. SRv6 explicitly indicates the forwarding path of an IPv6 message by inserting one routing extension header, i.e., Segment Routing Header (SRH), into the IPv6 message and adding the SIDs of all segments through which the forwarding path passes, i.e., the SID list, to the SRH. SRv6 provides flexible and efficient control for Software Defined Wide Area Networks (SD-WANs), has the characteristics of easy deployment and scalability, and can better realize traffic scheduling and path optimization, ensure the quality of important services, balance traffic distribution, improve the utilization rate of leased lines, and reduce line costs.

[0030] Depending on their functions, nodes in an SRv6 network can be divided into several roles:

[0031] The source node is responsible for inserting the SRH into the IPv6 header of an IPv6 message, or for encapsulating the IPv6 header into the outer layer of a message and inserting the SRH. The source node is used to direct the message flow to an SRv6 path defined by the Segment List in the SRH.

[0032] A relay node is located on the SRv6 path of a message, is not involved in SRv6 processing, and only performs general IPv6 message forwarding. A relay node may be a node that supports SRv6 or a node that does not support SRv6.

[0033] If the IPv6 destination address of the received SRv6 message is an SRv6 SID located in the endpoint node, the endpoint node processes the message according to the instruction of the SRv6 SID and updates the SRH. In the embodiments described below, the endpoint node is referred to as an endpoint node.

[0034] A tail node is the last endpoint node in an SRv6 forwarding path.

[0035] The same node may have different roles in different SRv6 paths, for example, a node that is a source node in one SRv6 path may be a relay node or an endpoint node in another SRv6 path.

[0036] SRv6 SID is for defining network functions and representing network commands. The format of SRv6 SID is the format of IPv6 address, and as shown in Figure 1, SRv6 SID consists of four parts: Locator, Function, Arguments, and MBZ (Must be zero) field.

[0037] The locator is used to identify the segment to which the SID belongs, and is unique in the SR domain.

[0038] Function: This is to identify the local operation command bound to the SID, and after a specified node receives service in the SR domain, it will perform the associated operation according to the Function field of the SRv6 SID.

[0039] Arguments are used to define information such as message flow and services.

[0040] MBZ (Must be zero): If the total number of bits in Locator, Function, and Arguments is less than 128 bits, fill the other bits with 0.

[0041] 2. SRv6 message format. The SRv6 message encapsulation format is the outer layer of the original 3-layer data message with a new IPv6 header and SRH. The SRH is a routing extension header with a routing type value of 4. The SRv6 message format is as shown in Figure 2, which includes the IPv6 header, SRH, and the original message.

[0042] The IPv6 header includes a version number, a traffic class, a flow label, a payload length, a next header, a hop limit, a source address (SA), and a destination address (DA), and the length of both the source address and the destination address may be 128 bits. Here, a value of 43 for the next header indicates that the next header is a routing extension header.

[0043] SRH includes the following: The Next Header is 8 bits in length and identifies the type of the next message header. The SRH length (Hdr Ext Length) is 8 bits long and indicates the length of the SRH header in 8-byte units, not including the first 8 bytes. The Routing Type has a length of 8 bits and a value of 4, which indicates that an SRH is included. The segment index (Segments Left, SL) is 8 bits long and indicates the number of the next SID to search. Its initial value is n-1, where n indicates the number of SIDs encapsulated in the SRH. The value of SL is decremented by 1 each time an endpoint node is passed through. The Last Entry field is 8 bits long and its value is the number of the first SID in the actual forwarding path of the message in the SRH. The flag bits (Flags) are 8 bits in length and are flag bit information. A Tag is 16 bits in length and marks a group of messages that have the same characteristics. A Segment List is a list of SIDs, ordered according to the furthest nodes in the message's forwarding path: Segment List[0] indicates the last SID in the forwarding path, Segment List[1] indicates the penultimate SID in the forwarding path, and so on. Since SIDs are in IPv6 address format, each SID is a 128-bit IPv6 address. Optional Type Length Value objects(variable) are optional type length value object variables.

[0044] 3. SRv6 message transmission process. As shown in FIG. 3, device A in FIG. 3 is a source node, devices C and E are endpoint nodes, and devices B and D are relay nodes.

[0045] Step 1: After receiving an IPv6 message as a source node, device A encapsulates an SRH and an IPv6 header for the IPv6 message, and then forwards the encapsulated message to device B by searching the routing table according to the destination address in the encapsulated IPv6 header.

[0046] Since the path from device A to device D must pass through two endpoint nodes, device C and device E, SL in the SRH is 1, and the SID list encapsulated in the SRH includes Segment List [0] = E and Segment List [1] = C.

[0047] In the IPv6 header, the source address is the address of device A, and the destination address is the address indicated in SL. In other words, the address in Segment List [1] indicated by SL=1 is the address of device C.

[0048] Step 2: After receiving the message, device B searches its routing table according to the destination address in the IPv6 header and forwards the message to device C.

[0049] Step 3: Device C checks the SL in the SRH, and if SL>0, it subtracts 1 from the value of SL and updates the destination address in the IPv6 header to the address indicated in SL, that is, to the Segment List [0] corresponding to SL=0, that is, to the address of device E. Then, device C transfers the message to device D.

[0050] Step 4: After receiving the message, device D searches its routing table according to the destination address in the IPv6 header and forwards the message to device E.

[0051] Step 5: Device E, which is the end node, receives the message and checks the SL value in the SRH header. If SL=0 is found, it decapsulates the message, removes the IPv6 header and SRH encapsulation, and forwards the message according to the destination address in the original message.

[0052] In order to reduce service delay when a link or node failure occurs, an embodiment of the present application provides a node protection method applied to a first node. The first node may be an endpoint node in an SRv6 TE path, and as shown in Figure 4, the node protection method includes the following steps:

[0053] S401, obtain a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including a SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message.

[0054] S402, forward a second service message to an endpoint node indicated in the backup SID, where the second service message includes a destination address, and the destination address is the backup SID.

[0055] The destination address is changed to the backup SID after it is determined that each endpoint node in the primary path is an unreachable endpoint node and that the endpoint node indicated in the backup SID is a reachable endpoint node.

[0056] After receiving the first service message, the first node may sequentially determine whether each endpoint node in the SID list is reachable. If it is determined that none of the endpoint nodes in the primary path are reachable and the endpoint node indicated in the backup SID is reachable, the first node may obtain a second service message and forward the second service message by changing the destination address in the IPv6 header of the first node to the backup SID.

[0057] According to the node protection method, after the first node obtains the first service message, if it is determined that all of the endpoint nodes in the primary path are unreachable endpoint nodes and the endpoint node indicated in the backup SID is a reachable endpoint node, the first service message can be forwarded to the endpoint node indicated in the backup SID. In other words, if a failure occurs in a node or a link between nodes in the primary path, the first service message can be forwarded from the first node in the primary path to the endpoint node indicated in the backup SID without the need to discard packets and then resend the service message via the backup path. This can reduce service delays caused by node or link failures and improve network reliability.

[0058] In this embodiment, the SID encapsulated in the penultimate element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is a backup SID.

[0059] As shown in Fig. 5, in the SRH of the embodiment of the present application, the second-to-last element in the SID list, i.e., Segment List [1], encapsulates the SID of the last node in the primary path. The last element, i.e., Segment List [0], encapsulates the backup SID. The initial value of SL is n, and Last Entry = n. For an explanation of the other fields included in Fig. 5, please refer to the explanation of the SRH in Fig. 2 of the above embodiment.

[0060] In the related art, the SRH includes the SID of the endpoint node in the primary path, and the embodiment of the present application adds a backup SID based on this. As can be seen, the embodiment of the present application only concerns the modification of the data forwarding plane, and does not extend the routing protocol of the control plane, so that the implementation is simple and has little impact on the traditional SRv6 network.

[0061] In some embodiments of the present application, the SRH further includes a SL, and as shown in FIG. 6, the node protection method includes the following steps:

[0062] S601, obtain a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including a SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message.

[0063] S601 is the same as S401.

[0064] S602: A first SL is obtained based on the difference between the current SL and a fixed value, and a first SID corresponding to the first SL is obtained from the SID list.

[0065] For example, if the first SL=3, the first SID corresponding to the first SL is SID3 encapsulated in Segment List[3] in the SRH.

[0066] S603: if the endpoint node indicated by the first SID is unreachable, the first SL is set as the current SL, and S602 is repeated until the first SID of the reachable endpoint node is obtained from the SID list.

[0067] For example, if the endpoint node indicated by SID3 is unreachable, set SL=3 as the current SL, and obtain SID2 encapsulated in Segment List[2] corresponding to SL=2 from the SID list. If the endpoint node indicated in SID2 is still unreachable, obtain SID1 encapsulated in Segment List[1] corresponding to SL=1 from the SID list; If the endpoint node indicated in SID1 is still unreachable, obtain SID0 encapsulated in Segment List[0] corresponding to SL=0 from the SID list.

[0068] According to the above process, it is sufficient to stop when the first SID of the reachable endpoint node is obtained.

[0069] When obtaining the first SID of the reachable endpoint node, the first node may change the destination address of the first service message to the first SID and forward it to the endpoint node indicated in the first SID. The first SID may be a backup SID or may be the SID of the endpoint node in the primary path. If the first SID is a backup SID, execute S604; if the first SID is not a backup SID, execute S606.

[0070] S604, if the first SID of the reachable endpoint node is a backup SID, change the destination address to the backup SID to obtain a second service message.

[0071] However, in compliance with the regulations of the SRv6 related protocols, it is further necessary to update the SL in the SRH to a value that points to the backup SID, that is, SL=0 in the SRH of the second service message.

[0072] Referring to the example of S603, if it is finally determined that the endpoint node corresponding to the SID encapsulated in Segment List[0] is reachable, the first SID can be determined as the backup SID, so that the destination address in the IPv6 header of the first service message can be changed to the backup SID, the value of SL can be updated to 0, and the second service message can be obtained.

[0073] S605, forwarding a second service message to an endpoint node indicated in the backup SID, where the second service message includes a destination address, and the destination address is the backup SID.

[0074] S605 is the same as S402 above.

[0075] S606, if the first SID of the reachable endpoint node is not a backup SID, change the destination address to the first SID of the reachable endpoint node to obtain a third service message, and forward the third service message to the endpoint node indicated in the first SID.

[0076] However, in accordance with the regulations of the SRv6 related protocols, it is necessary to further update the SL in the SRH to a value that points to the first SID. That is, the SL in the SRH of the third service message points to the Segment List in which the first SID is encapsulated.

[0077] For example, referring to the example of S603, if the first SID of the reachable endpoint node is SID1, the destination address in the IPv6 header of the first service message may be changed to SID1, the value of SL may be updated to 1, a third service message may be obtained, and the third service message may be forwarded.

[0078] According to the node protection method, when the first node determines that the next hop endpoint node is unreachable, it can determine whether the subsequent endpoint node is reachable based on the SID list in a hop-by-hop manner until it obtains the first SID of the reachable endpoint node. Furthermore, it can modify the first service message based on the first SID of the reachable endpoint node, and forward the modified service message to the reachable endpoint node. If the reachable endpoint node is not a backup SID, that is, if some endpoint nodes or some links in the primary path fail, the first node can skip the failed endpoint node or link and forward the service message to the reachable endpoint node, so as to forward the service message quickly. If the reachable endpoint node is a backup SID, the first node can forward the modified service message to the endpoint node indicated in the backup SID, and when a failure occurs in the primary path, it can realize a fast path switching, forward the service message quickly, prevent a long service delay, and improve the reliability of the SRv6 network.

[0079] In some embodiments of the present application, the first node may be the last node in the primary path, and a specified additional behavior (Flavor) is placed on the SID of the last node in the primary path.

[0080] As an example, the specified additional behavior may be referred to as a penultimate hop decapsulation (PSD) flavor, where the specified additional behavior is for defining a decapsulation behavior of a penultimate hop endpoint node that removes the outer layer encapsulation of a service message and forwards the inner layer original message.

[0081] After receiving the first service message, if the first node determines that the destination address is an SID in which a locally specified additional behavior is configured, the first node removes the IPv6 header and the SRH, obtains a fourth service message, and forwards the fourth service message.

[0082] It can be understood that after deleting the IPv6 header and the SRH of the first service message, the original service message encapsulated in the inner layer, that is, the fourth service message, can be obtained, and the first node can forward the fourth service message based on the routing table.

[0083] In this case, the SL of the first service message received by the first node is 1, and the destination address is the same as the SID encapsulated in the Segment List [1] in the SRH. The fact that the first node receives the first service message indicates that no failure occurs in the primary path, and the first node, as the tail node, can continue to decapsulate and transmit the first service message, and does not need to forward it to the backup node indicated in the Segment List [0] in the SID list according to the SID list, so the original service message encapsulated in the first service message can be promptly forwarded to the destination address of the original service message.

[0084] In this embodiment, when the first node is an intermediate endpoint node or an end node in the primary path, the method for the first node to obtain the first service message is as follows: Receive the first service message sent from a third node, and the third node is the previous hop node of the first node in the primary path.

[0085] When the first node is a source node, the method by which the first node obtains the first message is as follows: When receiving a fifth service message, if the next hop of the routing table entry that matches the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulate an IPv6 header and an SRH in the outer layer of the fifth service message to obtain the first service message.

[0086] However, the source node can learn the routing information of each node in the SRv6 network, and further determine the optimal path and the suboptimal path through the routing optimization policy. The optimal path can be the primary path, the suboptimal path can be the backup path, and the end node of the suboptimal path can be the backup node.

[0087] The source node may encapsulate the IPv6 header and the SRH in the outer layer of the fifth service message. In this case, the source address of the IPv6 header is the address of the source node, and the destination address is the address of the endpoint node that is the next hop of the source node in the SID list of the primary path. Suppose that the SID list corresponding to the primary path includes n SIDs, the value of SL in the SRH is n, Segment List[n] to Segment List[1] in the SRH are n SIDs in the SID list, and Segment List[0] in the SRH is the SID of the last node of the backup path. In this case, the format of the SRH in the first service message may refer to FIG. 5.

[0088] In the above embodiment, the endpoint node indicated in the backup SID is the tail node in the backup path for forwarding the first service message.

[0089] The node protection method provided in the embodiment of the present application will be described below by taking a specific scenario.

[0090] As shown in FIG. 7, there are two SRv6 TE forwarding paths between a customer edge device (CE) 1 and a customer edge device (CE) 2 in FIG. 7, PE1-->P1-->P2-->PE3 is the primary path, PE1 is the source node, P1 and P2 are intermediate nodes, and PE3 is the end node.

[0091] PE2-->P3-->P4-->PE4 is a backup path, with PE2 being the source node, P3 and P4 being intermediate nodes, and PE4 being the tail node.

[0092] Suppose PE1's Locator is A0::1, P1's Locator is A1::1, P2's End.X SID is A2::1, PE3 has Locator A3::1 and VPN SID A3::100, and the VPN SID A3::100 has PSD addition behavior. PE4 has Locator prefix A4::1 / 64 and VPN SID A4::200.

[0093] Note that Fig. 7 is an example of a scenario, and the nodes in the primary path and the backup path shown in Fig. 7 are all endpoint nodes. In actual implementation, there may be further relay nodes in the primary path and the backup path.

[0094] Each endpoint node in Figure 7 can distribute routing by flooding to inform other endpoint nodes of its own SID. The source node PE1 learns the dual-homing routing of CE2, and can determine a primary path and a backup path to CE2 by a routing optimization policy, and the tail node in the primary path can be the primary tail node and the tail node in the backup path can be the backup tail node. In the normal case, the traffic from CE1 to CE2 is forwarded along the primary path PE1-->P1-->P2-->PE3, the primary tail node is PE3, the backup tail node is PE4, and the backup SID of PE3 is the VPN SID A4::200 of PE4.

[0095] When PE1 receives a message from CE1 to CE2, the forwarding process of the message is as follows: Step 1: PE1 determines that a message from CE1 to CE2 needs to be forwarded via the path PE1-->P1-->P2-->PE3, and PE1 can add an IPv6 header and an SRH to the message.

[0096] Here, the destination address in the IPv6 header is the SID of P1, i.e., A1::1. The segment list in the SRH is<A1::1,A2::1,A3::100,A4::200> That is, Segment List[3] is A1::1 of P1, Segment List[2] is A2::1 of P2, Segment List[1] is A4::100 of PE3, Segment List[0] is A4::200 of PE4, and SL=3.

[0097] Step 2, PE1 forwards the message to P1 according to A1::1.

[0098] Step 3, P1 forwards the message to P2 according to the following Segment List A2::1.

[0099] Step 4: After P2 receives the message whose destination address is END.X SID A2::1, P2 can forward the message on the link between P2 and PE3 according to END.X SID A2::1, in which the destination address of the message is the VPN SID A3::100 of PE3.

[0100] Step 5: after receiving the message whose destination address is VPN SID A3::100, PE3 determines that the VPN SID A3::100 has a PSD addition behavior, and determines that the local is the penultimate hop node according to the SL, then performs penultimate hop decapsulation and lookup forwarding processing, removes the IPv6 header and SRH, and forwards the inner-layer original service message to CE2.

[0101] The above steps 1 to 5 are the message transfer process when no failure occurs on the primary path.

[0102] If PE3 fails, steps 4 and 5 may be replaced as follows:

[0103] When P2 receives a message whose destination address is END.X SID A2::1, it first subtracts 1 from the SL in the message, changing it to 1. Then, P2 obtains the next Segment List[1], that is, the SID of PE3, from the Segment List in accordance with SL=1. After searching the Forward Information database (FIB) forwarding table according to the SID in Segment List[1], it finds that the route to PE3 is unreachable, so it performs the following processes in order.

[0104] The SL is decremented by 1, i.e. the current SL is changed to 0, Change the destination address in the IPv6 header of the message to the Segment List[0] pointed to by the current SL, i.e., A4::200 of PE4, Search the FIB forwarding table using the new destination address to obtain the outgoing interface and next hop information; According to the outgoing interface and next hop information, the message is forwarded to PE4.

[0105] Furthermore, after receiving the message, if PE4 determines that SL=0 and the destination address is its own VPN SID, it can delete the IPv6 header and SRH of the message and forward the inner-layer original service message to CE2.

[0106] If a failure occurs in an intermediate node, for example, if a failure occurs in P2, steps 3 to 5 may be replaced as follows.

[0107] When P1 receives a message with a destination address of A1::1, it first subtracts 1 from the SL in the message, changing it to 2. Then, P1 obtains the next Segment List[2], that is, the SID of P2, from the Segment List in accordance with SL=2. If, as a result of searching the FIB forwarding table according to the SID in Segment List[2], it finds that the route to P2 is unreachable, it performs the following processes in order.

[0108] Decrement SL by 1, i.e. the current SL is changed to 1, The FIB forwarding table is searched using Segment List[1] (i.e., the SID of PE3) pointed to by the current SL=1.

[0109] When it is determined that the route of PE3 is unreachable, the SL is decremented by 1 again, i.e., the current SL is changed to 0.

[0110] Search the FIB forwarding table using Segment List[0] (i.e., PE4's SID) pointed to by the current SL=0, and if it is determined that the route of PE4 is reachable, change the destination address in the IPv6 header of the message to the SID of PE4, i.e., A4::200; Then, it uses the new destination address to look up the FIB forwarding table to obtain the outgoing interface and next hop information. According to the outgoing interface and next hop information, the message is forwarded to PE4.

[0111] Furthermore, after receiving the message, if PE4 determines that SL=0 and the destination address is its own VPN SID, it deletes the IPv6 header and SRH of the message, and forwards the inner-layer original service message to CE2, so that the original service message enters the VPN private network in which CE2 exists.

[0112] As can be seen, regardless of whether a tail node or intermediate node fails, a rapid path switching can be achieved to forward a message to a reachable endpoint node, thereby improving the network performance of SRv6.

[0113] In another scenario of the present embodiment, an escape function can also be realized after a failure occurs in a critical SRv6 forwarding path.

[0114] After receiving the fifth service message, if the source node determines that the next hop of the routing table entry that matches the destination address of the fifth service message is an SRv6 policy, it needs to determine whether the end node of the primary path included in the SRv6 policy has a backup node. In this scenario, the backup node may be an escape device.

[0115] Accordingly, the endpoint node indicated in the backup SID included in the SID list in the above embodiment is the second node, and a best-effort (BE) path exists between the first node and the second node, where the second node may be referred to as an escape device, i.e., when a node in the primary path fails, the escape device can realize message forwarding.

[0116] As shown in Figure 8, Figure 8 is an example of the scenario, in which there is a forwarding path PE1-->P1-->P2-->PE2 in an IPv6 bearer network between CE1 and CE2, PE1 is the source node, P1 and P2 are intermediate nodes, and PE2 is the end node. The SID of PE2 has a PSD Flavor.

[0117] A common escape device PE3 is deployed in the IPv6 bearer network, and a BE path exists between PE1, P1, P2 and PE3, and the BE path can be used as a backup path.

[0118] When PE1 receives a message from CE1 to CE2, it can add an IPv6 header and an SRH to the message.

[0119] The destination address in the IPv6 header is the SID of P1, Segment List[3] in the SRH is the SID of P1, Segment List[2] is the SID of P2, Segment List[1] is the SID of PE2, and Segment List[0] is the SID of PE3.

[0120] Normally, the message is forwarded via PE1-->P1-->P2-->PE2. After PE2 receives the message, if it determines that the destination address of the message is its own SID and that the SID has a PSD Flavor assigned to it, it deletes the IPv6 header and SRH of the message and sends the original inner-layer service message to CE2.

[0121] If a failure occurs between PE1 and PE2, for example, if P2 fails, after P1 receives the message, if it determines that both P2 and PE2 are unreachable, it can change the destination address of the message to the SID of PE3, update the SL to 0, and forward the modified message to PE3 based on the BE path.

[0122] After receiving the message, if PE3 determines that the destination address is its own SID and SL=0, it can delete the IPv6 header and SRH of the message and forward the original inner-layer service message to CE2.

[0123] According to the above method, even if there is no backup SRv6 TE forwarding path, the message can be forwarded to the escape device based on the BE forwarding method, and the escape device can forward the message to the CE, thereby further reducing the service delay when a node or link fails, and improving the reliability of the SRv6 network.

[0124] Corresponding to the above-mentioned method embodiment, the embodiment of the present application provides a node protection device applied to a first node. As shown in FIG. 9, the node protection device includes: An acquiring module 901, which is used for acquiring a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including an SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; a sending module 902 for forwarding a second service message to an endpoint node indicated in the backup SID, the second service message including a destination address, the destination address being changed to the backup SID after it is determined that all of the endpoint nodes in the primary path are unreachable endpoint nodes and the endpoint node indicated in the backup SID is a reachable endpoint node.

[0125] In one embodiment, the SRH further includes a SL, and the node protection device further includes a modification module; The acquisition module 901 is further used for acquiring a first SL according to a difference between the current SL and a fixed value, acquiring a first SID corresponding to the first SL from the SID list, and if an endpoint node indicated by the first SID is unreachable, setting the first SL as a current SL, and repeating the process of acquiring a first SL according to a difference between the current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list until an endpoint node indicated by the first SID is reached; The modification module is used for modifying a destination address to the backup SID when the first SID of the reachable endpoint node is a backup SID to obtain a second service message; The modification module is further used for modifying the destination address to the first SID of the reachable endpoint node when the first SID of the reachable endpoint node is not a backup SID to obtain a third service message; The sending module 902 is further used for forwarding the third service message to the endpoint node indicated in the first SID.

[0126] In one embodiment, the node protection device further comprises: A removal module is included, which removes the IPv6 header and the SRH when the destination address is an SID in which the specified additional behavior is configured, and obtains a fourth service message; The sending module 902 is further used for transmitting a fourth service message.

[0127] In one implementation, the endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is the second node, and a BE path exists between the first node and the second node.

[0128] In one implementation, the SID encapsulated in the penultimate element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is a backup SID.

[0129] In one implementation, when the first node is a source node, the acquisition module 901 specifically: receiving a fifth service message; If the next hop of the routing table entry that matches the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulate the IPv6 header and the SRH into the outer layer of the fifth service message to obtain a first service message.

[0130] Corresponding to the above method embodiment, the present embodiment further provides an electronic device, which may be a first node. As shown in Fig. 10, the electronic device includes a processor 1001, a machine-readable storage medium 1002, and a transceiver 1004. The machine-readable storage medium 1002 stores machine-executable instructions that can be executed by the processor 1001, The machine executable instructions are transmitted to the processor 1001, Obtaining a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including an SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; forwarding a second service message to an endpoint node indicated in the backup SID, the second service message including a destination address, the destination address being changed to the backup SID after it is determined that each endpoint node in the primary path is an unreachable endpoint node and that the endpoint node indicated in the backup SID is a reachable endpoint node.

[0131] In one implementation, the SRH further includes a SL, and the machine executable instructions cause the processor to: Obtaining a first SL based on a difference between the current SL and a fixed value, and obtaining a first SID corresponding to the first SL from the SID list; If the endpoint node indicated by the first SID is unreachable, the first SL is set as the current SL, and the process of obtaining the first SL according to the difference between the current SL and a fixed value and obtaining the first SID corresponding to the first SL from the SID list is repeated until the first SID of the reachable endpoint node is obtained from the SID list; if the first SID of the reachable endpoint node is a backup SID, change the destination address to the backup SID to obtain a second service message; If the first SID of the reachable endpoint node is not a backup SID, change the destination address to the first SID of the reachable endpoint node to obtain the third service message, and forward the third service message to the endpoint node indicated by the first SID.

[0132] In one implementation, the machine executable instructions may include instructions to the processor 1001: If the destination address is an SID in which the specified additional behavior is configured, removing the IPv6 header and the SRH, and obtaining a fourth service message; and transmitting a fourth service message.

[0133] In one implementation, the endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is the second node, and a BE path exists between the first node and the second node.

[0134] In one implementation, the SID encapsulated in the penultimate element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is a backup SID.

[0135] In one implementation, when the electronic device is a source node, the machine executable instructions specifically cause the processor 1001 to: receiving a fifth service message; If the next hop of the routing table entry matching the fifth service message is an SRv6 policy and the SRv6 policy includes a primary path and a backup path, encapsulate the IPv6 header and the SRH in the outer layer of the fifth service message to obtain the first service message.

[0136] As shown in Fig. 10, the electronic device may further include a communication bus 1003. The processor 1001, the machine-readable storage medium 1002, and the transceiver 1004 communicate with each other via the communication bus 1003, which may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus 1003 may be divided into an address bus, a data bus, a control bus, etc.

[0137] The transceiver 1004 may be a wireless communication module, and the transceiver 1004 performs data interaction with other devices under the control of the processor 1001.

[0138] The machine-readable storage medium 1002 may include Random Access Memory (RAM) and / or Non-Volatile Memory (NVM), such as at least one magnetic disk memory. Note that the machine-readable storage medium 1002 may also be a storage device remote from at least one of the processors.

[0139] The processor 1001 may be a general-purpose processor including a central processing unit (CPU), a network processor (NP), etc., or may be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware assembly.

[0140] Based on the same inventive concept, an embodiment of the present application provides a machine-readable storage medium storing machine-executable instructions executable by a processor, the machine-executable instructions causing the processor to implement steps in any of the above-mentioned node protection methods.

[0141] In another embodiment provided herein, there is further provided a computer program product including instructions, which, when executed on a computer, causes the computer to implement steps in any of the node protection methods in the above embodiments.

[0142] In this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not require or imply any such actual relationship or sequence between those entities or operations. In addition, the terms "comprise", "include", "includes" or any other variant thereof means "comprise" in a non-exclusive sense. Thus, a process, method, product, or device that includes a set of elements does not include only those elements, but also includes other elements not expressly listed, or includes elements inherent to such process, method, product, or device. In the absence of further limitations, an element limited by a statement "including a ..." does not exclude the presence of other identical elements in the process, method, product, or device that includes the recited element.

[0143] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be cross-referenced, and the emphasis in each embodiment is on the differences from other embodiments. In particular, the embodiments of the segment identification determination device, device, and machine-readable storage medium are basically similar to the embodiments of the segment identification determination method, so they are only briefly described. For related parts, please refer to the description of the segment identification determination method.

[0144] The above description is only the preferred embodiment of the present application, and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. 1. A node protection method applied to a first node, comprising: Obtaining a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including a SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; forwarding a second service message to an endpoint node indicated by the backup SID, the second service message including the destination address, the destination address being changed to the backup SID after it is determined that all of the endpoint nodes in the primary path are unreachable endpoint nodes and that the endpoint node indicated by the backup SID is a reachable endpoint node; A node protection method comprising:

2. The SRH further includes a service node (SL). After receiving the first service message, the node protection method includes: Obtaining a first SL according to a difference between a current SL and a fixed value, and obtaining a first SID corresponding to the first SL from the SID list; If the endpoint node indicated by the first SID is unreachable, the first SL is set as a current SL, and a process of acquiring a first SL according to a difference between the current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list is repeated until a first SID of an endpoint node that is reachable is acquired from the SID list; if the first SID of the reachable endpoint node is the backup SID, change the destination address to the backup SID to obtain the second service message; If the first SID of the reachable endpoint node is not the backup SID, changing the destination address to the first SID of the reachable endpoint node to obtain a third service message, and forwarding the third service message to the endpoint node indicated by the first SID.

2. The node protection method according to claim 1, wherein:

3. After obtaining the first service message, the node protection method includes: If the destination address is an SID in which a specified additional behavior is configured, removing the IPv6 header and the SRH to obtain a fourth service message; and forwarding the fourth service message.

2. The node protection method according to claim 1, wherein:

4. The endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is a second node, and a BE path exists between the first node and the second node. The node protection method according to any one of claims 1 to 3, characterized in that:

5. the SID encapsulated in the second-to-last element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is the backup SID; The node protection method according to any one of claims 1 to 3, characterized in that:

6. When the first node is a source node, obtaining the first service message includes: receiving a fifth service message; If a next hop of a routing table entry that matches the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulating the IPv6 header and the SRH into an outer layer of the fifth service message to obtain the first service message.

2. The node protection method according to claim 1, wherein:

7. A node protection device applied to a first node, comprising: An acquisition module used for acquiring a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including a SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; a transmission module for transmitting a second service message to the endpoint node indicated by the backup SID, the second service message including the destination address, the destination address being changed to the backup SID after it is determined that all of the endpoint nodes in the primary path are unreachable endpoint nodes and the endpoint node indicated by the backup SID is a reachable endpoint node; A node protection device comprising:

8. The SRH further includes a SL, and the node protection device further includes a modification module; The acquisition module is further used for: acquiring a first SL according to a difference between a current SL and a fixed value, and acquiring a first SID corresponding to the first SL from the SID list; and if an endpoint node indicated by the first SID is unreachable, the first SL is set as a current SL, and the process of acquiring a first SL according to a difference between the current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list is repeated until a first SID of an endpoint node that is reachable is acquired from the SID list; The modification module is used for modifying the destination address to the backup SID when the first SID of the reachable endpoint node is the backup SID to obtain the second service message; The modification module is further used for modifying the destination address to the first SID of the reachable endpoint node when the first SID of the reachable endpoint node is not the backup SID to obtain a third service message; the sending module is further used for forwarding the third service message to an endpoint node indicated by the first SID; 8. The node protection device according to claim 7, wherein:

9. If the destination address is an SID for which a specified additional behavior is configured, the IPv6 header and the SRH are deleted to obtain a fourth service message. the sending module is further used for forwarding the fourth service message; 8. The node protection device according to claim 7, wherein:

10. The endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is a second node, and a BE path exists between the first node and the second node.

10. The node protection device according to claim 7, wherein the node protection device is a node protection device having a plurality of nodes.

11. the SID encapsulated in the second-to-last element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is the backup SID; 10. The node protection device according to claim 7, wherein the node protection device is a node protection device having a plurality of nodes.

12. If the first node is a source node, the acquisition module: receiving a fifth service message; If the next hop of a routing table entry that matches the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulating the IPv6 header and the SRH into an outer layer of the fifth service message to obtain the first service message.

8. The node protection device according to claim 7, wherein:

13. A processor; A transceiver; a machine-readable storage medium storing machine-executable instructions executable by said processor; The machine executable instructions cause the processor to: Obtaining a first service message, the first service message including an IPv6 header and an SRH, the IPv6 header including a destination address, the SRH including a SID list, the SID list including a backup SID and an SID of an endpoint node in a primary path for forwarding the first service message; forwarding a second service message to an endpoint node indicated by the backup SID, the second service message including the destination address, the destination address being changed to the backup SID after it is determined that all of the endpoint nodes in the primary path are unreachable endpoint nodes and that the endpoint node indicated by the backup SID is a reachable endpoint node; An electronic device comprising:

14. The SRH further includes a SL, and the machine-executable instructions further include causing the processor to: Obtaining a first SL according to a difference between a current SL and a fixed value, and obtaining a first SID corresponding to the first SL from the SID list; If the endpoint node indicated by the first SID is unreachable, repeating the process of acquiring a first SL according to a difference between the current SL and a fixed value and acquiring a first SID corresponding to the first SL from the SID list, until acquiring a first SID of a reachable endpoint node from the SID list, with the first SL as a current SL; if the first SID of the reachable endpoint node is the backup SID, change the destination address to the backup SID to obtain the second service message; if the first SID of the reachable endpoint node is not the backup SID, change the destination address to the first SID of the reachable endpoint node to obtain a third service message, and forward the third service message to the endpoint node indicated by the first SID.

14. The electronic device according to claim 13.

15. The machine executable instructions further include causing the processor to: If the destination address is an SID in which a specified additional behavior is configured, removing the IPv6 header and the SRH to obtain a fourth service message; and forwarding the fourth service message.

14. The electronic device according to claim 13.

16. The endpoint node indicated in the backup SID is a tail node in a backup path for forwarding the first service message; or The endpoint node indicated in the backup SID is a second node, and a BE path exists between the first node and the second node; 16. The electronic device according to claim 13, wherein the first and second electrodes are arranged in a first direction.

17. the SID encapsulated in the second-to-last element in the SID list is the SID of the last node in the primary path, and the SID encapsulated in the last element is the backup SID; 16. The electronic device according to claim 13, wherein the first and second electrodes are arranged in a first direction.

18. When the electronic device is a source node, the machine-executable instructions cause the processor to: receiving a fifth service message; If a next hop of a routing table entry that matches the fifth service message is an SRv6 policy, and the SRv6 policy includes a primary path and a backup path, encapsulating the IPv6 header and the SRH into an outer layer of the fifth service message to obtain the first service message.

14. The electronic device according to claim 13.

19. A machine-readable storage medium having machine-executable instructions stored thereon, the machine-executable instructions, when invoked and executed by a processor, causing the processor to implement steps in a node protection method according to any one of claims 1 to 3 and 6. A machine-readable storage medium comprising:

Citation Information

Patent Citations

  • SRv6 Endpoint fault protection method

    CN113364677A

  • Method, device and system for notifying processing capability of network device

    CN114531395A

  • SCALABLE EDGE NODE PROTECTION USING IPv6 SEGMENT ROUTING EXTENSION HEADER

    US20150109902A1

  • Service Chain Fault Protection Method, Apparatus, Device and System, and Storage Medium

    US20220337514A1