WO2024083219A1 - Procédé et appareil de traitement de message, et dispositif et support de stockage - Google Patents

Procédé et appareil de traitement de message, et dispositif et support de stockage Download PDF

Info

Publication number
WO2024083219A1
WO2024083219A1 PCT/CN2023/125621 CN2023125621W WO2024083219A1 WO 2024083219 A1 WO2024083219 A1 WO 2024083219A1 CN 2023125621 W CN2023125621 W CN 2023125621W WO 2024083219 A1 WO2024083219 A1 WO 2024083219A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
sid
backup
node
header
Prior art date
Application number
PCT/CN2023/125621
Other languages
English (en)
Chinese (zh)
Inventor
姜文颖
程伟强
Original Assignee
中国移动通信有限公司研究院
中国移动通信集团有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国移动通信有限公司研究院, 中国移动通信集团有限公司 filed Critical 中国移动通信有限公司研究院
Publication of WO2024083219A1 publication Critical patent/WO2024083219A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular to a message processing method, device, equipment and storage medium.
  • the network adopts the Segment Routing over IPv6 (SRv6) policy technology based on the Internet Protocol Version 6 (IPv6) forwarding plane to provide users with high-quality connection services, it generally provides dual-provider edge (Provider Edge, PE) or multi-PE multi-homing connection services, and forms active-standby protection between each PE.
  • PE Provider Edge
  • CE Customer Edge
  • the implementation mechanism of the SRv6 tail node failure protection solution is relatively complex.
  • the embodiments of the present disclosure hope to provide a message processing method, apparatus, device and storage medium.
  • the embodiment of the present disclosure is intended to provide a message processing method, which is applied to a first node, where the first node is an ingress node, and the method includes:
  • First information is added to an extended header of a first message to obtain a second message; wherein the first information includes at least one backup SID.
  • adding an extension header to the first message, and encapsulating the first SID and the first information in the extension header includes:
  • a Segment Routing Header is added to an outer layer Internet Protocol Version 6 (IPv6) header of the first message, and the first SID and the first information are encapsulated in a segment list (segmentlist) of the SRH; wherein,
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID.
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID, including:
  • the encapsulation position of the first information in the segment list is adjacent to the encapsulation position of the first SID in the segment list and is after the encapsulation position of the first SID.
  • the encapsulation position of the backup SID is SL[0].
  • the method includes:
  • At least one backup SID in the first information is sorted according to the priority of the backup SID, and the backup SID with the lowest priority is encapsulated at the end of the first information.
  • the method further includes:
  • the method further includes:
  • the first SID is a SID of a first flavor or a SID of a first type
  • the remaining backup SIDs in the first information except the backup SID encapsulated in the last position in the first information are SIDs of the first flavor or SIDs of the first type.
  • the first type of SID includes:
  • the SID of the second behavior or the SID of the second behavior type is the SID of the second behavior type.
  • the method includes at least one of the following:
  • the first egress node is a primary tail node of SRv6;
  • the first SID is a SID allocated by the first egress node
  • the backup SID is a SID allocated by a protection node of the first egress node; wherein the protection node is a backup egress node of the first egress node.
  • the backup SID is a SID allocated by the protection node of the first egress node, including:
  • backup SIDs There are multiple backup SIDs, and different backup SIDs are allocated by different protection nodes of the first egress node.
  • the method further includes: sending the second message.
  • At least one embodiment of the present disclosure provides a message processing method, which is applied to a network node, and the method includes:
  • the second message includes a first SID and first information, and the first information includes at least one backup SID;
  • the destination address of the second message is changed to a backup SID to obtain a third message
  • the changing the destination address of the second message to a backup SID includes:
  • the destination address of the second message is changed to a reachable backup SID.
  • changing the destination address of the second message to a reachable backup SID includes:
  • the value of the SL pointer is reduced by 1 successively until the node corresponding to the backup SID pointed to by the current pointer is reachable, and then the destination address of the second message is changed to the backup SID pointed to by the current pointer.
  • At least one embodiment of the present disclosure provides a message processing method, which is applied to a second node, where the second node is an egress node, and the method includes:
  • the destination address in the second message or the third message is the local SID of the second node, and the destination address is a SID of the first flavor, remove the outer message header of the second message or the third message to obtain a fourth message; and/or, when the destination address in the second message or the third message is the local SID of the second node, and the destination address is a SID of the first type, remove the outer message header of the second message or the third message to obtain a fourth message;
  • the destination address is a SID of a first behavior of a first flavor or a SID of a first behavior type of a first flavor.
  • the removing the outer message header of the second message or the third message further includes:
  • the step of determining the value of the second information of the second message or the third message is not performed; the outer message header of the second message or the third message is removed;
  • the method further includes:
  • the first type of SID includes:
  • the SID of the second behavior or the SID of the second behavior type is the SID of the second behavior type.
  • removing the outer message header of the second message or the third message includes:
  • the second information is the segmentleft field information in the outer encapsulation message header SRH.
  • removing the outer message header of the second message or the third message includes:
  • the method further includes:
  • the SID of the first flavor or the SID of the first type is advertised to the first node and/or the network device through a routing protocol.
  • At least one embodiment of the present disclosure provides a message processing method, which is applied to a first node, where the first node is an ingress node, and the method includes:
  • a first bit in the first message is set to a first value, and first information is added to an extended header of the first message to obtain a fifth message; wherein the first information includes at least one backup SID.
  • the first bit is at least one reserved bit of the first message.
  • adding an extension header to the first message, and encapsulating the first SID and the first information in the extension header includes:
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID.
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID, including:
  • the encapsulation position of the first information in the segment list is adjacent to the encapsulation position of the first SID in the segment list and is after the encapsulation position of the first SID.
  • the encapsulation position of the backup SID is SL[0].
  • the method further includes:
  • the method includes at least one of the following:
  • the first egress node is a primary tail node of SRv6;
  • the first SID is a SID allocated by the first egress node
  • the backup SID is a SID allocated by a protection node of the first egress node; wherein the protection node is a backup egress node of the first egress node.
  • the backup SID is a SID allocated by the protection node of the first egress node, including:
  • backup SIDs There are multiple backup SIDs, and different backup SIDs are allocated by different protection nodes of the first egress node.
  • the method further includes: sending the fifth message.
  • At least one embodiment of the present disclosure provides a message processing method, which is applied to a network node, and the method includes:
  • the fifth message includes a first bit, a first SID, and first information, and the first information includes at least one backup SID;
  • the changing the destination address of the fifth message to a backup SID includes:
  • the destination address of the fifth message is changed to a reachable backup SID.
  • changing the destination address of the fifth message to a reachable backup SID includes:
  • Subtract 1 from the value of the SL pointer, and change the destination address of the fifth message to the backup SID pointed to by the current pointer;
  • the value of the SL pointer is reduced by 1 successively until the node corresponding to the backup SID pointed to by the current pointer is reachable, and then the destination address of the fifth message is changed to the backup SID pointed to by the current pointer.
  • At least one embodiment of the present disclosure provides a message processing method, which is applied to a second node, where the second node is an egress node, and the method includes:
  • the seventh message is sent.
  • the removing the outer message header of the second message or the third message further includes:
  • the step of determining the value of the third information of the fifth message or the sixth message is not performed; the outer message header of the fifth message or the sixth message is removed;
  • the value of the third information of the fifth message or the sixth message is at least one specific value; and remove the outer message header of the fifth message or the sixth message.
  • the method further includes:
  • the third information is the segmentleft field information in the outer encapsulation message header SRH.
  • removing the outer message header of the fifth message or the sixth message includes:
  • At least one embodiment of the present disclosure provides a message processing device, including:
  • the first processing unit is used to add an extension header to the first message, and encapsulate the first SID and the first information in the extension header to obtain a second message; wherein the first information includes at least one backup SID; or, add the first information to the extension header of the first message to obtain the second message; wherein the first information includes at least one backup SID.
  • At least one embodiment of the present disclosure provides a message processing device, including:
  • a first transceiver unit configured to receive a second message; wherein the second message includes a first SID and first information, and the first information includes at least one backup SID;
  • a second processing unit configured to change the destination address of the second message to a backup SID to obtain a third message when the node corresponding to the first SID is unreachable;
  • the first transceiver unit is further used to send the third message.
  • At least one embodiment of the present disclosure provides a message processing device, including:
  • a second transceiver unit used to receive a second message or a third message
  • a third processing unit configured to, when the destination address in the second message or the third message is the local SID of the second node and the destination address is a SID of the first flavor, remove the outer message header of the second message or the third message to obtain a fourth message; and/or, when the destination address in the second message or the third message is the local SID of the second node and the destination address is a SID of the first type, remove the outer message header of the second message or the third message to obtain a fourth message;
  • At least one embodiment of the present disclosure provides a message processing device, including:
  • the fourth processing unit is used to set the first bit in the first message to the first value, add an extension header to the first message, encapsulate the first SID and the first information in the extension header, and obtain a fifth message; wherein the first information includes at least one backup SID; or, set the first bit in the first message to the first value, and add the first information to the extension header of the first message to obtain a fifth message; wherein the first information includes at least one backup SID.
  • At least one embodiment of the present disclosure provides a message processing device, including:
  • a third transceiver unit configured to receive a fifth message; wherein the fifth message includes a first bit, a first SID, and first information, and the first information includes at least one backup SID;
  • a fifth processing unit configured to change the destination address of the fifth message to a backup SID to obtain a sixth message when the node corresponding to the first SID is unreachable and the first bit is a first value;
  • the fifth transceiver unit is further used to send the sixth message.
  • At least one embodiment of the present disclosure provides a message processing device, including:
  • a fourth transceiver unit configured to receive a fifth message or a sixth message
  • a sixth processing unit configured to, when the destination address in the fifth message or the sixth message is the local SID of the second node and the first bit in the fifth message or the sixth message is the first value, remove the The outer message header of the fifth message or the sixth message is used to obtain a seventh message;
  • the sixth transceiver unit is further used to send the seventh message.
  • At least one embodiment of the present disclosure provides a network device, including a processor and a memory for storing a computer program that can be run on the processor.
  • processor when used to run the computer program, it executes the steps of any of the above methods.
  • At least one embodiment of the present disclosure provides a storage medium having a computer program stored thereon, wherein the computer program implements the steps of any of the above methods when executed by a processor.
  • the information transmission method, apparatus, device and storage medium provided by the embodiments of the present disclosure add an extension header to the first message, and encapsulate the first SID and the first information in the extension header to obtain a second message; wherein the first information includes at least one backup SID; or, add the first information to the extension header of the first message to obtain a second message; wherein the first information includes at least one backup SID.
  • the technical solution provided by the embodiments of the present disclosure provides a simplified tail node/egress node protection mechanism, which can realize fast path switching protection when the SRv6 tail node/egress node fails in a multi-homing access scenario by extending the data plane.
  • FIG1 is a schematic diagram of the SRv6 SID format in the related art
  • FIG2 is a schematic diagram of a first implementation flow of a message processing method according to an embodiment of the present disclosure
  • FIG3 is a schematic diagram of allocating backup SIDs according to an embodiment of the present disclosure.
  • FIG4 is a schematic diagram of the packaging position of the first information in an embodiment of the present disclosure.
  • FIG5 is a schematic diagram 1 of sorting at least one backup SID in the first information according to an embodiment of the present disclosure
  • FIG6 is a second schematic diagram of sorting at least one backup SID in the first information according to an embodiment of the present disclosure
  • FIG7 is a second schematic diagram of the implementation flow of the message processing method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of an embodiment of the present disclosure in which the destination address of the second message is changed to a backup SID;
  • FIG9 is a third schematic diagram of the implementation flow of the message processing method according to an embodiment of the present disclosure.
  • FIG10 is a fourth schematic diagram of the implementation flow of the message processing method according to an embodiment of the present disclosure.
  • FIG11 is a schematic diagram 1 of the Flags field in the IPv6 SRH according to an embodiment of the present disclosure
  • FIG12 is a second schematic diagram of the Flags field in the IPv6 SRH in an embodiment of the present disclosure.
  • FIG13 is a schematic diagram of a fifth implementation flow of a message processing method according to an embodiment of the present disclosure.
  • FIG14 is a sixth schematic diagram of the implementation flow of the message processing method according to an embodiment of the present disclosure.
  • FIG15 is a schematic diagram of a network structure and SID allocation of each device according to an embodiment of the present disclosure.
  • FIG16 is a schematic diagram 1 of message forwarding for SRv6 Policy dual homing node/egress node failure protection according to an embodiment of the present disclosure
  • FIG17 is a second schematic diagram of message forwarding for SRv6 Policy dual homing node/egress node failure protection according to an embodiment of the present disclosure
  • FIG18 is a second schematic diagram of the network structure and SID allocation of each device according to an embodiment of the present disclosure.
  • FIG19 is a schematic diagram 1 of message forwarding for SRv6 Policy multi-home node/egress node failure protection according to an embodiment of the present disclosure
  • FIG20 is a second schematic diagram of message forwarding for SRv6 Policy multi-home node/egress node failure protection according to an embodiment of the present disclosure
  • FIG21 is a third schematic diagram of message forwarding for SRv6 Policy multi-home node/egress node failure protection according to an embodiment of the present disclosure
  • FIG22 is a fourth schematic diagram of message forwarding for SRv6 Policy multi-home node/egress node failure protection according to an embodiment of the present disclosure
  • FIG23 is a schematic diagram 1 of message forwarding for SRv6 BE dual homing node/egress node failure protection according to an embodiment of the present disclosure
  • FIG24 is a second schematic diagram of message forwarding for SRv6 BE dual homing node/egress node failure protection according to an embodiment of the present disclosure
  • FIG25 is a schematic diagram of the first structure of the message processing device according to an embodiment of the present disclosure.
  • FIG26 is a second schematic diagram of the composition structure of the message processing device according to an embodiment of the present disclosure.
  • FIG27 is a third schematic diagram of the composition structure of the message processing device according to an embodiment of the present disclosure.
  • FIG28 is a fourth schematic diagram of the composition structure of the message processing device according to an embodiment of the present disclosure.
  • FIG29 is a fifth structural diagram of the message processing device according to an embodiment of the present disclosure.
  • FIG30 is a sixth schematic diagram of the composition structure of the message processing device according to an embodiment of the present disclosure.
  • FIG. 31 is a schematic diagram of the composition structure of the network device according to an embodiment of the present disclosure.
  • SRv6 Policy is a source routing tunnel technology that introduces an SRv6 extension header, Segment Routing Header (SRH), into IPv6 packets. It forms an SRv6 path by encapsulating an ordered segment list at the header node, such as Segmentlist ⁇ SID1, SID2, ... SIDn>, to guide user packets to be forwarded in the network along the specified path from SID1 to SIDn.
  • RFC8986 clearly defines the format of SRv6 SID.
  • SRv6 SID is a special IPv6 address that has both the routing capability of a common IPv6 address and the behavior capability unique to SRv6.
  • FIG1 is a schematic diagram of the SRv6 SID format in the related art.
  • the SRv6 SID consists of three parts: locator, function, and argument, totaling 128 bits.
  • the Locator has a positioning function, so it is generally unique within the SR domain. Other nodes in the network can locate this node through the Locator network segment route. At the same time, all SRv6 SIDs published by this node can also be reached through the Locator network segment route.
  • Function represents the device's instructions, which are pre-set by the device. The Function part is used to instruct the SRv6 SID generation node to perform corresponding functional operations. The Function part can also be divided into an optional parameter segment (Arguments).
  • the format of the SRv6 SID becomes Locator: Function: Arguments. Arguments occupy the low bits of the IPv6 address. The Arguments field can be used to define some message flows and services.
  • Table 1 shows the various behavior types of SRv6 SIDs. SRv6 SIDs with different behaviors represent different functions. "Behavior" identifies the behavior bound to the SID. Table 1 lists a series of behaviors that can be associated with the SID. The first column of Table 1 is the name of the SID of various behavior types, and the second column of Table 1 is the function of the SID of the behavior type.
  • the node publishes the SID on the control plane, and the behavior value associated with the SID is published together with the SID on the control plane.
  • Table 2 shows the three flavor types defined in RFC8986.
  • Flavor is usually a variant of Behavior.
  • the variant here can be understood as a modification, supplement or superposition of the behavior bound to one or more Behavior type SIDs.
  • An End.X SID with PSP Flavor means that the SRH processing of the End.X behavior type SID is modified:
  • the tunnel path Segmentlist can be arranged using node SID (End SID) or adjacent SID (End.X SID).
  • node SID End SID
  • adjacent SID End.X SID
  • the tunnel path is a strict path, and each hop is specified; when some SIDs in the path use node SID, the tunnel path is a one-hop loose path, because there may be different reachable links between the two nodes.
  • the current network uses SRv6 Policy technology to provide users with high-quality connection services, it generally provides dual PE or multi-PE multi-home connection services, and each PE forms a primary and backup protection.
  • the technical solution for SRv6 tail node failure protection is mainly the mirror protection solution proposed in the document [ID.ietf-rtgwg-srv6-egress-protection].
  • the current SRv6 The mirror protection solution for the tail node has a complex implementation mechanism and requires the expansion of the control plane protocol, making it difficult to upgrade existing network equipment.
  • the embodiments of the present disclosure propose a simplified tail node/egress node protection mechanism, which can implement fast path switching protection when the SRv6 tail node/egress node fails in a multi-homing access scenario by extending the data plane.
  • FIG2 is a schematic diagram of an implementation flow of a message processing method according to an embodiment of the present disclosure, which is applied to a first node, where the first node is an ingress node. As shown in FIG2 , the method includes:
  • Step 201 Add an extension header to the first message, and encapsulate the first SID and the first information in the extension header to obtain a second message; wherein the first information includes at least one backup SID; or, add the first information to the extension header of the first message to obtain a second message; wherein the first information includes at least one backup SID.
  • the SID can be a service SID (service SID), specifically, a VPN SID.
  • the message header includes a fixed header or a regular header, and optionally also includes an extended header.
  • a packet may carry 0, 1, or more extended headers.
  • IPv6 packet header includes the IPv6 header (or IPv6 fixed header, IPv6 regular header, IPv6 header), and optionally also includes the IPv6 extension header (IPv6 Extension Headers).
  • IPv6 packet can carry 0, 1, or more IPv6 extension headers.
  • IPv6 extension headers are added additionally as needed, such as Segment Routing header (SRH), Destination Options header (DOH), Hop-by-Hop Options header (HBH), Routing header, Fragment header, Authentication header, Encapsulating Security Payload header, etc.
  • SSH Segment Routing header
  • DOH Destination Options header
  • HH Hop-by-Hop Options header
  • Routing header Fragment header
  • Authentication header Encapsulating Security Payload header, etc.
  • the backup SID is the service SID assigned to the user by each backup tail node/egress device in the multi-homing access scenario of the user site.
  • the head node can publish through a control protocol such as BGP, receive the service SID of the primary egress and the service SID of the backup egress, or allocate the service SID to each egress device through a controller and send it to the head node, or statically configure it at the head node.
  • FIG3 is a schematic diagram of allocating backup SIDs according to an embodiment of the present disclosure.
  • PE2, PE3, and PE4 are dual-homing access devices of site CE2 of VPN1 user, wherein PE2 is the primary access device. (Primary Egress or Active Egress), PE3 is the first backup access device (Backup Egress), PE4 is the second backup access device (Backup Egress), then the VPN SID allocated by PE2 to the VPN1 user is the primary service SID (primary SID or Primary SID or Active SID), and the VPN SIDs allocated by PE3 and PE4 to the VPN1 user are the first backup service SID (Backup SID) and the second backup service SID (Backup SID), that is, A:3::B100 in Figure 3 is the first backup SID of A:2::B100, and A:4::B100 is the second backup SID of A:2::B100. It should be noted that there is no limit to the number of backup access devices here, and each backup access node
  • adding an extension header to the first message, and encapsulating the first SID and the first information in the extension header includes:
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID.
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID, including:
  • the encapsulation position of the first information in the segment list is adjacent to the encapsulation position of the first SID in the segment list and is after the encapsulation position of the first SID.
  • the encapsulation position of the first information in the segment list is after the encapsulation position of the first SID, which can be understood as the encapsulation position of the first information is closer to the top of the stack than the first SID.
  • FIG4 is a schematic diagram of the encapsulation position of the first information in the embodiment of the present disclosure.
  • the first SID is the primary SID (main SID or Active SID)
  • the first information is the Backup SID. It can be seen that the Backup SID is next to the primary SID and is located after the primary SID in the Segment List, and is closer to the top of the stack than the primary SID.
  • the encapsulation position of the backup SID is SL[0].
  • SL[0] is Segment List[0], which is the top of the Segment List stack.
  • the method comprises:
  • At least one backup SID in the first information is sorted according to the priority of the backup SID, and the backup SID with the lowest priority is encapsulated at the end of the first information.
  • the first information i.e., the backup SID
  • the first information includes multiple backup SIDs of different priorities, wherein the highest priority backup SID is located at the front of the first information, i.e., closer to the bottom of the stack, and adjacent to the first SID (primary VPN SID or primary SID or Active SID); the lowest priority backup SID is located at the end of the first information, i.e., closest to the top of the stack, and farthest from the first SID.
  • the head node/entry node of the SRv6 Policy encapsulates the IPv6 outer header, it needs to encapsulate the backup SID in the last position SL[0] of the segmentlist of the SRH extension header, that is, the backup SID is placed immediately after the primary VPN SID.
  • the backup SIDs are placed in order of priority, that is, the primary VPN SID is followed by the highest priority backup SID, followed by the second priority backup SID, and so on, and the lowest priority backup SID is placed at the last SL[0].
  • the head node/entry node of the SRv6 BE when encapsulating the IPv6 outer header, the head node/entry node of the SRv6 BE must add an SRH extension header with an active SID (primary VPN SID) and one to multiple backup SIDs in descending order of priority.
  • the encapsulation content of the segmentlist of the SRH extension header is shown in Figure 6.
  • the primary SID is used as the destination address of the outer IP header.
  • the method further comprises:
  • the method further comprises:
  • the first SID is a SID of a first flavor or a SID of a first type
  • the remaining backup SIDs in the first information except the backup SID encapsulated in the last position in the first information are SIDs of the first flavor or SIDs of the first type.
  • the first type of SID includes:
  • the SID of the second behavior or the SID of the second behavior type is the SID of the second behavior type.
  • the SID of the second behavior or the SID of the second behavior type is a newly defined behavior or behavior type compared to the existing relevant standards.
  • it can be the SID of END.PSD (Penultimate Segment Decapsulation) or the SID of END.PSD behavior or the SID of END.PSD type or END.PSD The SID of the behavior type.
  • END.PSD can be a variation of End.DT4, End.DT6, End.DT46, End.DX4, End.DX6, End.DX2, End.DX2V, and End.DX2M behavior.
  • N When a network node N receives a packet with S as the destination and S is the local END.PSD SID, N does the following:
  • N When processing the upper layer header of a packet that matches a FIB entry locally instantiated with the End.DT6 SID, N does the following:
  • the method before adding an extension header to the first message and encapsulating the first SID and the first information in the extension header, or before adding the first information to the extension header of the first message, the method further includes:
  • the first SID is a SID of a first flavor or a SID of a first type
  • the SID is the SID of the first flavor or the SID of the first type
  • an extension header is added to encapsulate the first SID and the first information in the extension header or the first information is added to the extension header of the first message.
  • the method includes at least one of the following:
  • the first egress node is a primary tail node of SRv6;
  • the first SID is a SID allocated by the first egress node
  • the backup SID is a SID allocated by a protection node of the first egress node; wherein the protection node is a backup egress node of the first egress node.
  • the first SID and the backup SID are the service SID (Service SID) or VPN SID assigned to the same customer (user) by the primary egress node and the backup egress node respectively.
  • the protection node specifically, can be a multi-homing access PE device of the CE device.
  • the backup SID is a SID allocated by a protection node of the first egress node, including:
  • backup SIDs There are multiple backup SIDs, and different backup SIDs are allocated by different protection nodes of the first egress node.
  • the method further includes: sending the second message.
  • An SRv6 Policy tail node/egress node protection scheme is proposed.
  • One or more backup SIDs are carried in the Segmentlist of the IPv6 packet header SRH on the data plane.
  • the backup SID is used as the destination address to forward the traffic to the backup tail node/egress node, thus realizing user-unaware protection switching.
  • FIG7 is a schematic diagram of an implementation flow of a message processing method according to an embodiment of the present disclosure, which is applied to a network node.
  • the method includes:
  • Step 701 Receive a second message; wherein the second message includes a first SID and first information, and the first information includes at least one backup SID;
  • Step 702 When the node corresponding to the first SID is unreachable, the destination of the second message is The address is changed to the backup SID, and the third message is obtained;
  • Step 703 Send the third message.
  • the "node corresponding to the first SID" here means that the SID itself is an address, such as an IPv6 address. That is, the first SID is the local SID of the corresponding node. The message can be routed to the corresponding node through the SID.
  • a network node may receive several second messages, and the several second messages constitute traffic. Therefore, receiving and processing the second message mentioned above may also be understood as: performing the above processing on the second message in the received traffic.
  • the network node here is not limited to the intermediate node in the path, but can also be the entry node, that is, the first node.
  • changing the destination address of the second message to a backup SID includes:
  • the destination address of the second message is changed to a reachable backup SID.
  • changing the destination address of the second message to a reachable backup SID includes:
  • the value of the SL pointer is reduced by 1 successively until the node corresponding to the backup SID pointed to by the current pointer is reachable, and then the destination address of the second message is changed to the backup SID pointed to by the current pointer.
  • FIG8 is a schematic diagram of an embodiment of the present disclosure in which the destination address of the second message is changed to a backup SID.
  • the SID pointed to by the SL pointer here can refer to the SID pointed to by the arrow in FIG8 (the arrow is the SL pointer).
  • the SID A:2:B100 pointed to by the current SL pointer is the first SID (primary SID or active SID)
  • the SID A:3:B100 pointed to by the current SL pointer is the first backup SID in the first information.
  • the destination address (Destination Address, DA) in the encapsulation format of this message (third message) is also changed to the backup SID A:3:B100.
  • DA Destination Address
  • FIG9 is a schematic diagram of an implementation flow of a message processing method according to an embodiment of the present disclosure, which is applied to a second node, where the second node is an egress node. As shown in FIG9 , the method includes:
  • Step 901 receiving a second message or a third message
  • Step 902 when the destination address in the second message or the third message is the local SID of the second node, and the destination address is the SID of the first flavor, remove the outer message header of the second message or the third message to obtain a fourth message; and/or, when the destination address in the second message or the third message is the local SID of the second node, and the destination address is the SID of the first type, remove the outer message header of the second message or the third message to obtain a fourth message;
  • Step 903 Send the fourth message.
  • the second node when the second node receives the second message, it indicates that the second node is the main egress node and its status is normal.
  • the second node receives the third message, it indicates that the second node is the backup egress node and its status is normal, and the main egress node fails.
  • the first Flavor for example, can be the penultimate segment decapsulation (PSD) Flavor; “a SID with a PSD flavor” can be expressed as “an SID with PSD Flavor” in English.
  • PSD penultimate segment decapsulation
  • the sending here can be forwarding, forward, transfer, etc.
  • the following describes a solution when the destination address in the second message or the third message is the local SID of the second node and the destination address is the SID of the first Flavor.
  • removing an outer message header of the second message or the third message includes:
  • the step of determining the value of the second information of the second message or the third message is not performed; the outer message header of the second message or the third message is removed;
  • the first behavior type SID specific examples may be End.DT4, End.DT6, End.DT46, End.DX4, End.DX6, End.DX2, End.DX2V and End.DX2M type SIDs.
  • the SID of the first behavior of the first flavor or the SID of the first behavior type of the first flavor may be the End.DT4 SID of the PSD Flavor, the End.DT6 SID of the PSD Flavor, the End.DT46 SID of the PSD Flavor, or the End.DT6 SID of the PSD Flavor.
  • the corresponding English words may be an End.DT4 SID with PSD Flavor, an End.DT6 SID with PSD Flavor, an End.DT46 SID with PSD Flavor, an End.DX4 SID with PSD Flavor, an End.DX6 SID with PSD Flavor, an End.DX2 SID with PSD Flavor, an End.DX2V SID with PSD Flavor, or an End.DX2M SID with PSD Flavor.
  • the first modification method for the SRH processing flow is that the step of determining whether the pointer value is non-0 is not performed in the SRH processing step.
  • the first method may be applicable to the case where the first information of the second message or the third message includes multiple backup SIDs.
  • the modification made by the present disclosure to the SRH process is: deleting the steps S02 to S04.
  • Deleting the steps S02 to S04 means not executing the step of determining whether SL is non-zero, and not executing S03.
  • the steps of sending an ICMP parameter problem with code 0 to the source address, setting the pointer to the SL field, interrupting the data packet processing, and discarding the data packet directly execute step S05, that is, entering the processing of the next header of the data packet.
  • the node When processing the Upper-Layer header of a packet that matches a FIB entry instantiated locally as the End.DT4 SID, i.e., when processing the next header of the SRH, the node shall do the following:
  • step S02 in the processing flow of the next header is to remove the outer IPv6 header and all extension headers, that is, to remove the outer message header of the second message or the third message in the present disclosure.
  • the second modification method is to modify the pointer value determination step in the original SRH processing flow, that is, to determine that the value of the second information of the second message or the third message is a specific first value, or a second value... or an Nth value.
  • the second modification manner is applicable when the first information of the second message or the third message contains only one backup SID.
  • modify instruction S02 in the processing flow of SRH of End.DT4 SID to:
  • the next header processing step of S05 is executed, that is, the step of removing the outer message header of the second message or the third message; the specific processing flow is as follows: If the condition of non-0 and non-1 is met, steps S03 and S04 are executed.
  • the method further comprises:
  • the value of the second information of the second message or the third message is not at least one specific value” can be understood as: the value of the second information of the second message or the third message is not a specific first value, and is not a specific second value, ..., and is not a specific Nth value.
  • the following describes a solution when the destination address in the second message or the third message is the local SID of the second node and the destination address is a first type of SID.
  • the first type of SID includes:
  • the SID of the second behavior or the SID of the second behavior type is the SID of the second behavior type.
  • the SID of the second behavior (Behavior) or the SID of the second behavior (Behavior) type is a newly defined behavior or behavior type compared to the existing relevant standards.
  • it can be the SID of END.PSD (Penultimate Segment Decapsulation) or the SID of END.PSD behavior or the SID of END.PSD type or the SID of END.PSD behavior type.
  • END.PSD can be a variation of End.DT4, End.DT6, End.DT46, End.DX4, End.DX6, End.DX2, End.DX2V, and End.DX2M behavior.
  • N When a network node N receives a packet with S as the destination and S is the local END.PSD SID, N does the following:
  • N When processing the upper layer header of a packet that matches a FIB entry locally instantiated with the End.DT6 SID, N does the following:
  • removing the outer message header of the second message or the third message includes:
  • the destination address in the second message or the third message is the local SID of the second node, and the destination address is the SID of the second behavior (Behavior), if there are multiple backup SIDs in the first information of the second message or the third message, the outer message header of the second message or the third message is removed to obtain the fourth message.
  • the destination address in the second message or the third message is the local SID of the second node, and the destination address is the SID of the second behavior
  • the backup SID in the first information of the second message or the third message is one
  • it is first determined that the value of the second information of the second message or the third message is at least one specific value. For example, when it is determined that the value of the second information is 0 or 1, the outer message header of the second message or the third message is removed to obtain the fourth message.
  • the specific method of removing the message header is similar to the method of removing the message header in the above "the destination address is the SID of the first behavior of the first flavor", but in actual implementation, it can also be Takes a different execution process than the above removal method.
  • the second information is the segmentleft field information in the outer encapsulation message header SRH.
  • removing the outer message header of the second message or the third message includes:
  • the method further comprises:
  • the SID of the first flavor or the SID of the first type is announced to the first node and/or the network device via a routing protocol;
  • the SID of the first flavor or the SID of the first type is notified to the first node and/or the network device through the routing protocol, so that all node devices in the network know that the SID is the SID of the first flavor or the SID of the first type. It should be noted that this is only a way to let the entire network know.
  • the first node, the network device, and the second node can also be configured (node device self-configuration or third-party controller configuration) so that the entire network devices know that the SID is the SID of the first flavor or the SID of the first type.
  • the SRv6 head node/entry node When the SRv6 head node/entry node performs SRv6 outer tunnel message encapsulation, it first determines whether the primary VPN SID of the SRv6 tail node/egress node has a backup SID. If so, the backup SID is added after the VPN SID in the SRH segmentlist, that is, the position of SegmentList(0) is the backup SID. If there are multiple backup SIDs, they are added in the VPN in descending order of priority. The backup SIDs are added in sequence, with the lowest priority backup SID placed last.
  • Packets are forwarded along the SRv6 path in the following two situations:
  • the message is forwarded normally to the SRv6 active egress node.
  • the node finds that the destination S in the header of the received data packet has the following conditions:
  • S is equal to the local VPN SID with PSD Flavor
  • the node does not perform a check on the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, and then forwards the decapsulated exposed data packet to the corresponding destination.
  • the device finds that the next SID in the segmentlist (primary VPN SID) is unreachable, so the device searches for the first reachable SID (the reachable downstream node) from the SIDs after the unreachable SID (primary VPN SID) in the segmentlist according to the SRH.segmentlist path order.
  • the SL value is reduced by 1, so that the SL pointer points to the first backup SID after the VPN SID, and then the destination address of the data packet is modified to Segment List [SL] (i.e., the first backup SID), and the message is sent to the first backup tail node/egress node corresponding to the first backup SID; if the first backup SID is unreachable, the SL value continues to be reduced by 1, and the SL pointer points to the second priority backup SID thereafter.
  • SL Segment List
  • the multi-homed egress node protection processing mechanism on the SRv6 BE path is consistent with the protection processing on the SRv6 Policy path. The only difference is that when the head node/entry node of the SRv6 BE encapsulates the IPv6 outer header, an SRH extension header with an active SID (primary VPN SID or Primary SID or Active SID) and 1 to multiple backup SIDs (Backup SIDs) in descending order of priority must be added at the same time.
  • the encapsulation content of the segmentlist of the SRH extension header is shown in Figure 6.
  • the primary SID is used as the destination address of the outer IP header.
  • FIG10 is a schematic diagram of an implementation flow of a message processing method according to an embodiment of the present disclosure, which is applied to a first node, where the first node is an ingress node. As shown in FIG10 , the method includes:
  • Step 1001 Set the first bit in the first message to a first value, add an extension header to the first message, encapsulate the first SID and the first information in the extension header, and obtain a fifth message; wherein the first information includes at least one backup SID; or, set the first bit in the first message to a first value, and add the first information to the extension header of the first message, and obtain a fifth message; wherein the first information includes at least one backup SID.
  • the "first bit” herein may include at least one specific bit.
  • the first bit is set to a first value, for example, the first bit may be set to 1.
  • the first bit is at least one reserved bit of the first message.
  • the reserved bit here can be at least one bit in the Flags field in the IPv6 SRH.
  • Figures 11 and 12 are schematic diagrams of the Flags field in the IPv6 SRH in the embodiment of the present disclosure. As shown in Figure 11, the Flag field in the existing IPv6 SRH header is extended to occupy one bit to indicate that the backup protection mechanism of the node is started. When the next-hop SID is unreachable, the next reachable SID is found in the subsequent SIDs in the segment list, and the message is forwarded to the destination. At the same time, it indicates that the node does not need to judge the SL value of the Segmentlist when removing the outer encapsulation header of the data packet.
  • the B bit represents the backup flag bit and/or the removal of the outer encapsulation header mark bit. If the B-flag is If set to 1, it means that the backup protection mechanism of the node is started. When the SID pointed to by the current SL pointer is unreachable, the next reachable SID is obtained from the subsequent SID of the unreachable SID in the sengmentlist along the SegmentList path. If B-flag is set to 1, when a node not indicated by SRH.SegmentList[0] (such as the node indicated by SRH.SegmentList[1]) receives a data packet with B-Flag as 1, it is necessary to remove the outer encapsulation header of the data packet. If B-flag is set to 0, it is processed according to the original process and Behavior action. Reserved bit: unused for future use. Must be 0 during transmission and ignored when received.
  • adding an extension header to the first message, and encapsulating the first SID and the first information in the extension header includes:
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID.
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID, including:
  • the encapsulation position of the first information in the segment list is adjacent to the encapsulation position of the first SID in the segment list and is after the encapsulation position of the first SID.
  • the encapsulation position of the backup SID is SL[0].
  • the method further comprises:
  • the method includes at least one of the following:
  • the first egress node is a primary tail node of SRv6;
  • the first SID is a SID allocated by the first egress node
  • the backup SID is a SID allocated by a protection node of the first egress node; wherein the protection node is a backup egress node of the first egress node.
  • the backup SID is a SID allocated by a protection node of the first egress node, including:
  • backup SIDs There are multiple backup SIDs, and different backup SIDs are allocated by different protection nodes of the first egress node.
  • the method further includes: sending the fifth message.
  • FIG. 13 is a schematic diagram of an implementation flow of a message processing method according to an embodiment of the present disclosure, which is applied to a network node. As shown in FIG. 13 , the method includes:
  • Step 1301 Receive a fifth message; wherein the fifth message includes a first bit, a first SID, and first information, and the first information includes at least one backup SID;
  • Step 1302 When the node corresponding to the first SID is unreachable and the first bit is a first value, the destination address of the fifth message is changed to a backup SID to obtain a sixth message;
  • Step 1303 Send the sixth message.
  • changing the destination address of the fifth message to a backup SID includes:
  • the destination address of the fifth message is changed to a reachable backup SID.
  • changing the destination address of the fifth message to a reachable backup SID includes:
  • Subtract 1 from the value of the SL pointer, and change the destination address of the fifth message to the backup SID pointed to by the current pointer;
  • the value of the SL pointer is reduced by 1 successively until the node corresponding to the backup SID pointed to by the current pointer is reachable, and then the destination address of the fifth message is changed to the backup SID pointed to by the current pointer.
  • FIG. 14 is a schematic diagram of an implementation flow of a message processing method according to an embodiment of the present disclosure, which is applied to a second node, where the second node is an egress node. As shown in FIG. 14 , the method includes:
  • Step 1401 receiving the fifth message or the sixth message
  • Step 1402 When the destination address in the fifth message or the sixth message is the local SID of the second node and the first bit in the fifth message or the sixth message is the first value, remove the outer message header of the fifth message or the sixth message to obtain a seventh message;
  • Step 1403 Send the seventh message.
  • the SID can be a service SID (service SID) or a VPN SID.
  • service SID service SID
  • VPN SID VPN SID
  • it can be End.DT4, End.DT6, End.DT46, End.DX4, End.DX6, End.DX2, End.DX2V or End.DX2M type SID defined in RFC8986.
  • removing the outer message header of the second message or the third message further includes:
  • the value of the third information of the fifth message or the sixth message is not judged.
  • the method further comprises:
  • the third information is the segmentleft field information in the outer encapsulation message header SRH.
  • removing the outer message header of the fifth message or the sixth message includes:
  • the SRv6 head node/ingress node When the SRv6 head node/ingress node performs SRv6 outer tunnel message encapsulation, it first determines whether there is a backup SID for the primary VPN SID of the SRv6 tail node/egress node. If so, the SRH.B-flag value is set to 1, and the backup SID is added after the VPN SID in the SRH segmentlist, that is, the position of SegmentList(0) is the backup SID. If there are multiple backup SIDs, they are added in descending order of priority after the VPN SID, with the lowest priority backup SID placed at the end.
  • Packets are forwarded along the SRv6 path in the following two situations:
  • the message is forwarded normally to the SRv6 active tail node/egress node.
  • the node finds that the destination S in the message header of the received data packet is equal to the local End.DT4 or End.DT6 or End.DT46 or End.DX4, End.DX6 or End.DX2 or End.DX2V or End.DX2M SID, and the SRH.B-flag in the message header is 1.
  • the node does not check the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, and then forwards the decapsulated exposed data packet to the corresponding destination.
  • the device When the message is forwarded to the penultimate hop endpoint along the SRv6 tunnel path, the device will find that the next SID in the segmentlist (primary VPN SID or Primary SID or Active SID) is unreachable. If the SRH.B-flag in the current message header is 1, the device will search for the SID after the unreachable SID (primary VPN SID or Primary SID or Active SID) in the SRH.segmentlist along the SRH.segmentlist path until the first reachable SID is found, that is, the reachable downstream node.
  • the SL value is reduced by 1, so that the SL pointer points to the first backup SID after the primary VPN SID, and then the destination address of the data packet is modified to Segment List[SL] (i.e., the first backup SID), and the message is sent to the first backup tail node/exit node corresponding to the first backup SID; if the first backup SID is unreachable, the SL value continues to be reduced by 1, and the SL pointer points to the second priority backup SID thereafter.
  • SL Segment List[SL]
  • the multi-homed egress node protection processing mechanism on the SRv6 BE path is consistent with the protection processing on the SRv6 Policy path.
  • the only difference is that when the head node/entry node of the SRv6 BE encapsulates the IPv6 outer header, an SRH extension header with an active SID (primary VPN SID or Primary SID or Active SID) and 1 to multiple backup SIDs (Backup SID) in descending order of priority must be added at the same time.
  • the encapsulation content of the segmentlist of the SRH extension header is shown in Figure 6.
  • the SRH.B-flag is set to 1, and the primary VPN SID (Primary SID or Active SID) is used as the destination address of the outer IP header.
  • Segmentlist is expressed as ⁇ S1,S2,S3>, where S1 is the first SID to be accessed along the SRv6 path, S2 is the second SID to be accessed, and S3 is the last SID to be accessed.
  • Solution 1 (including Solution 1-1 and Solution 1-2): SRv6 Policy Dual End Node/Egress Node Protection Mechanism
  • FIG15 is a schematic diagram of the network structure and SID allocation of each device in an embodiment of the present disclosure. It is assumed that the network includes PE1, PE2, PE3, PE4, P1, P2, P3, and P4 router devices, wherein VPN1 users include two sites, CE1 and CE2, and site CE2 is dual-homed to PE2 and PE3. The traffic from CE1 to CE2 is carried through the SRv6 Policy tunnel.
  • the path information is as follows:
  • A:3::B100 assigns VPN SID of VPN1 user to PE3 device
  • A:4::B100 assigns VPN SID of VPN1 customer to PE4 device, that is, A:3::B100 is the primary service SID, A:4::B100 is the backup SID, and the correspondence between the primary service SID and the backup SID of the VPN1 user is configured on the SRv6 Policy head node PE1 device.
  • PE1 When PE1 receives the packet from CE1 and encapsulates the outer IPv6 header of the tunnel, it knows that VPN1 has a dual-homing protection tail node based on the locally configured backup SID information. Therefore, it first performs the following actions:
  • step B If not, perform one of the following actions:
  • Solution 1-2 the first sentence of step A above is changed to "Determine whether the primary VPN SID A:3::B100 in segmentlist is the END.PSD SID". The rest is exactly the same as Solution 1-1.
  • the PE1 device executes the standard SRv6 Policy forwarding process.
  • FIG16 is a schematic diagram of message forwarding for SRv6 Policy dual tail node/egress node fault protection in an embodiment of the present disclosure.
  • the main tail node/egress node PE3 is operating normally.
  • PE3 finds that the destination A:3::B100 in the message header of the received data packet is the local End.DT6 SID with PSD Flavor. It does not check the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, restores the inner original message, searches the routing table locally, and forwards the original message to CE2.
  • the P2 device finds that the next SID in the segmentlist (primary VPN SID or primary SID or active SID A:3::B100) is unreachable, so the device searches for the SID after the primary VPN SID (primary SID or active SID) along the SRH.segmentlist path until it finds the next SID.
  • a reachable SID i.e., a reachable downstream node.
  • P2 reads the backup SID A:4::B100 from the SL[0] position and modifies the destination address of the message to the backup SID A:4::B100.
  • the P2 device continues to send the message to the backup tail node/egress node PE4 according to the new destination address (backup SID). If PE4 fails, the message is discarded; if PE4 is normal, the message reaches the PE4 device.
  • backup SID new destination address
  • PE4 finds that the destination A:4::B100 in the header of the received data packet is the local End.DT6SID, so it removes the outer IPv6 encapsulation, restores the inner original message, searches the routing table locally, and forwards the original message to CE2, thereby automatically implementing automatic protection switching when the main tail node/egress node PE2 fails.
  • FIG15 is a schematic diagram of the network structure and SID allocation of each device in an embodiment of the present disclosure. It is assumed that the network includes PE1, PE2, PE3, PE4, P1, P2, P3, and P4 router devices, wherein VPN1 users include two sites, CE1 and CE2, and site CE2 is dual-homed to PE2 and PE3. The traffic from CE1 to CE2 is carried through the SRv6 Policy tunnel.
  • the path information is as follows:
  • A:3::B100 assigns VPN SID of VPN1 user to PE3 device
  • A:4::B100 assigns VPN SID of VPN1 customer to PE4 device, that is, A:3::B100 is the primary service SID, A:4::B100 is the backup SID, and the correspondence between the primary service SID and the backup SID of the VPN1 user is configured on the SRv6 Policy head node PE1 device.
  • PE1 When PE1 receives the packet sent by CE1 and encapsulates the outer IPv6 header of the tunnel, it knows that VPN1 has a dual-homing protection tail node based on the locally configured backup SID information. Therefore, it sets the value of SRH.B-flag to 1 and adds backup SID A:4::B100 after VPN SID A:3::B100 in segmentlist. That is, the backup SID is encapsulated in the SL[0] position.
  • the PE1 device executes the standard SRv6 Policy forwarding process.
  • FIG17 is a schematic diagram of message forwarding for SRv6 Policy dual tail node/egress node fault protection in an embodiment of the present disclosure.
  • the main tail node/egress node PE3 is operating normally.
  • PE3 finds that the destination A:3::B100 in the message header of the received data packet is the local End.DT6 SID and the SRH.B-flag in the message header is 1. It does not check the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, restores the inner original message, searches the routing table locally, and forwards the original message to CE2.
  • the P2 device finds that the next SID in the segmentlist (primary VPN SID or Primary SID or Active SID A:3::B100) is unreachable and the SRH.B-flag in the message header is 1, so the device searches for the SID after the current unreachable node in the SRH.segmentlist (primary VPN SID or Primary SID or Active SID) along the SRH.segmentlist path until the first reachable SID (that is, the reachable downstream node) is found.
  • PE4 If PE4 is normal, the node corresponding to the backup SID A:4::B100 is reachable, so P2 reads the backup SID A:4::B100 from the SL[0] position and changes the destination address of the message to the backup SID A:4::B100.
  • the P2 device continues to send the message to the backup tail node/egress node PE4 according to the new destination address A:4::B100 (backup SID).
  • PE4 finds that the destination A:4::B100 in the header of the received data packet is the local End.DT6SID, so it removes the outer IPv6 encapsulation, restores the inner original message, searches the local routing table, and forwards the original message to CE2, thus automatically realizing the main tail node/egress node PE2 failure Automatic protection switching.
  • Solution 1 (including Solution 1-1 and Solution 1-2): Protection mechanism for multiple home nodes/egress nodes
  • FIG18 is a schematic diagram of the network structure and SID allocation of each device in an embodiment of the present disclosure.
  • the network includes PE1, PE2, PE3, PE4, P1, P2, and P3 router devices, where VPN1 users include two sites, CE1 and CE2, and site CE2 is multi-homed to PE2, PE3, and PE4.
  • the traffic from CE1 to CE2 is carried through the SRv6 Policy tunnel.
  • the path information is as follows:
  • A:2::B100 is the VPN SID assigned to the VPN1 user by PE2
  • A:3::B100 is the VPN SID assigned to the VPN1 user by PE3
  • A:4::B100 is the VPN SID assigned to the VPN1 customer by PE4. That is, A:2::B100 is the primary service SID, A:3::B100 is the first backup SID, and A:4::B100 is the second backup SID.
  • the correspondence between the primary service SID and the backup SID of the VPN1 user is configured on the SRv6 Policy head node PE1.
  • PE1 When PE1 receives the packet from CE1 and encapsulates the outer IPv6 header of the tunnel, it knows that VPN1 has a multi-homing protection tail node based on the locally configured backup SID information. Therefore, it first performs the following actions:
  • step B If not, perform one of the following actions:
  • Solution 1-2 the first sentence of step A above is changed to "Determine whether the primary VPN SID A:2::B100 in segmentlist is the END.PSD SID", and the rest is exactly the same as Solution 1-1.
  • the PE1 device executes the standard SRv6 Policy forwarding process.
  • the main tail node/egress node PE2 is operating normally
  • P1 forwards the message to the active tail node/egress node PE2 normally.
  • PE2 finds that the destination A:2::B100 in the message header of the received data packet is the local End.DT6 SID with PSD Flavor. It does not check the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, restores the inner original message, searches the routing table locally, and forwards the original message to CE2.
  • the active tail node/egress node PE2 fails.
  • PE3 If PE3 is normal, the node corresponding to the backup SID A:3::B100 is reachable, so P1 reads the first backup SID A:3::B100 from the SL[1] position and changes the destination address of the message to the first backup SID A:3::B100.
  • the P1 device continues to send the message to the first backup tail node/egress node PE3 according to the new destination address (the first backup SID).
  • PE3 finds that the destination A:3::B100 in the message header of the received data packet is the local End.DT6 SID with PSD Flavor. It does not check the Segments Left value in SRH, but directly deletes the outer IPv6 header and all its extension headers to restore the inner original message. It searches the local routing table and forwards the original message to CE2. This automatically implements automatic protection switching when the main tail node/egress node PE2 fails.
  • Figure 19 is a schematic diagram of message forwarding for SRv6 Policy multi-home tail node/egress node failure protection (PE2 failure scenario) in an embodiment of the present disclosure.
  • Figure 19 shows message forwarding in a scenario where only the main tail node/egress node PE2 fails.
  • P1 reads the second backup SID A:4::B100 from the SL[0] position and modifies the destination address of the message to the second backup SID A:4::B100.
  • the P1 device continues to send the message to the second backup tail node/egress node PE4 according to the new destination address (second backup SID). If PE4 fails, the message is lost; if PE4 is normal, the message reaches the PE4 device.
  • the PE4 device finds that the destination A:4::B100 in the header of the received data packet is the local End.DT6SID, so it removes the outer IPv6 encapsulation, restores the inner original message, searches the routing table locally, and forwards the original message to the CE2 device, thereby automatically realizing automatic protection switching when the primary tail node/egress node PE2 and the first backup tail node/egress node PE3 fail at the same time.
  • FIG20 is a schematic diagram of message forwarding for SRv6 Policy multi-homing tail node/egress node failure protection in an embodiment of the present disclosure (a scenario where PE2 and PE3 fail at the same time).
  • FIG20 shows the main tail node/egress node. Message forwarding in the scenario where both PE2 and the first backup tail node/egress node PE3 fail at the same time.
  • Solution 2 Multiple home nodes/exit nodes protection mechanism
  • FIG18 is a schematic diagram of the network structure and SID allocation of each device in the embodiment of the present disclosure.
  • the network includes PE1, PE2, PE3, PE4, P1, P2, and P3 router devices, wherein VPN1 users include two sites, CE1 and CE2, and site CE2 is multi-homed to PE2, PE3, and PE4.
  • the traffic from CE1 to CE2 is carried through the SRv6 Policy tunnel, and the path information is as follows:
  • A:2::B100 is the VPN SID assigned to the VPN1 user by PE2
  • A:3::B100 is the VPN SID assigned to the VPN1 user by PE3
  • A:4::B100 is the VPN SID assigned to the VPN1 customer by PE4. That is, A:2::B100 is the primary service SID, A:3::B100 is the first backup SID, and A:4::B100 is the second backup SID.
  • the correspondence between the primary service SID and the backup SID of the VPN1 user is configured on the SRv6 Policy head node PE1.
  • PE1 When PE1 receives the message sent by CE1 and encapsulates the outer IPv6 header of the tunnel, it knows that VPN1 has a multi-homing protection tail node based on the locally configured backup SID information, so it sets the value of SRH.B-flag to 1 and adds the first backup SID A:3::B100 and the second backup SID A:4::B100 in descending order of priority after VPN SID A:2::B100 in segmentlist. That is, the first backup SID is encapsulated in SL[1] and the second backup SID is encapsulated in SL[0].
  • the PE1 device then executes the standard SRv6 Policy forwarding process.
  • the main tail node/egress node PE2 is operating normally
  • P1 forwards the message to the active tail node/egress node PE2 normally.
  • the active tail node/egress node PE2 fails.
  • the P1 device finds that the next SID in the segmentlist (primary VPN SID or Primary SID or Active SID A:2::B100) is unreachable and the SRH.B-flag in the message header is 1, so the device searches for the SID after the currently unreachable node in the SRH.segmentlist (primary VPN SID or Primary SID or Active SID) along the SRH.segmentlist path until the first reachable SID (that is, the reachable downstream node) is found.
  • PE3 If PE3 is normal, the node corresponding to the backup SID A:3::B100 is reachable, so P1 reads the first backup SID A:3::B100 from the SL[1] position and changes the destination address of the message to the first backup SID A:3::B100.
  • the P1 device continues to send the message to the first backup tail node/egress node PE3 according to the new destination address A:3::B100 (the first backup SID).
  • PE3 finds that the destination A:3::B100 in the header of the received data packet is the local End.DT6 SID, and the value of SRH.B-flag in the header is set to 1. It does not check the Segments Left value in SRH, but directly deletes the outer IPv6 header and all its extension headers to restore the inner original message. It searches the routing table locally and forwards the original message to CE2. This automatically implements automatic protection switching when the main tail node/egress node PE2 fails.
  • Figure 21 is a schematic diagram of message forwarding for SRv6 Policy multi-home tail node/egress node failure protection (PE2 failure scenario) in an embodiment of the present disclosure.
  • Figure 21 shows message forwarding in a scenario where only the main tail node/egress node PE2 fails.
  • P1 If PE4 is normal, the node corresponding to the backup SID A:4::B100 is reachable, P1 reads the second backup SID A:4::B100 from the SL[0] position, and modifies the destination address of the message to the second backup SID A:4::B100. The P1 device continues to send the message to the second backup tail node/egress node PE4 according to the new destination address (second backup SID).
  • the PE4 device finds that the destination A:4::B100 in the header of the received data packet is the local End.DT6SID, so it removes the outer IPv6 encapsulation, restores the inner original message, searches the routing table locally, and forwards the original message to the CE2 device, thereby automatically realizing automatic protection switching when the primary tail node/egress node PE2 and the first backup tail node/egress node PE3 fail at the same time.
  • Figure 22 is a schematic diagram of message forwarding for SRv6 Policy multi-home tail node/egress node failure protection in an embodiment of the present disclosure (a scenario where PE2 and PE3 fail at the same time).
  • Figure 22 shows message forwarding in a scenario where the primary tail node/egress node PE2 and the first backup tail node/egress node PE3 fail at the same time.
  • Solution 1 (including Solution 1-1 and Solution 1-2): SRv6 BE dual tail node/egress node protection mechanism
  • Figure 15 is a schematic diagram of the network structure and SID allocation of each device in the embodiment of the present disclosure, assuming that the network includes PE1, PE2, PE3, PE4, P1, P2, P3, P4 router devices.
  • VPN1 users include two sites CE1 and CE2, and site CE2 is dual-homed to PE2 and PE3, and the traffic from CE1 to CE2 is carried through the SRv6 BE tunnel.
  • A:3::B100 assigns VPN SID of VPN1 user to PE3 device
  • A:4::B100 assigns VPN SID of VPN1 customer to PE4 device, that is, A:3::B100 is the primary service SID, A:4::B100 is the backup SID, and the correspondence between the primary service SID and the backup SID of the VPN1 user is configured on the SRv6 Policy head node PE1 device.
  • PE1 receives the message sent by CE1. Based on the locally configured backup SID information, it knows that VPN1 has a dual-homing protection tail node. Therefore, when encapsulating the outer IPv6 header of the tunnel, it adds an SRH extension header with the active SID (primary VPN SID) A:3::B100 and the backup SID A:4::B100.
  • the primary VPN SID A:3::B100 is the VPN SID of the PSD Flavor or END.PSD SID.
  • PE1 uses the primary VPN SID A:3::B100 as the destination address in the outer IP header.
  • PE1 executes the standard SRv6 forwarding process. At this time, there are two situations:
  • the main tail node/egress node PE3 is operating normally.
  • Each node in the network forwards the message along PE1, P1, and P2 to the main tail node/exit node PE3 according to the destination address A:3::B100.
  • the PE3 device finds that the destination A:3::B100 in the message header of the received data packet is the VPN SID of the local PSD Flavor or the local END.PSD SID. It does not check the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, restores the inner original message, searches the routing table locally, and forwards the original message to the CE2 device.
  • PE1 finds that the destination address A:3::B100 is unreachable, so it searches for the SID after the currently unreachable node A:3::B100 (primary VPN SID or Primary SID or Active SID) in SRH.segmentlist in order until it finds the first reachable SID (i.e., the reachable downstream node).
  • PE1 If PE4 is normal, the node corresponding to the backup SID A:4::B100 is reachable, so PE1 reads the backup SID A:4::B100 from the SL[0] position and changes the destination address of the message to the backup SID A:4::B100.
  • the PE1 device continues to send the message to the backup tail node/egress node PE4 according to the new destination address A:4::B100 (backup SID).
  • Figure 23 is a schematic diagram of message forwarding for SRv6 BE dual-homing tail node/egress node failure protection (PE3 failure scenario) in an embodiment of the present disclosure.
  • Figure 23 shows message forwarding in the scenario of primary tail node/egress node PE3 failure.
  • the PE4 device finds that the destination A:4::B100 in the header of the received data packet is the local VPN SID, so it removes the outer IPv6 encapsulation, restores the inner original message, and forwards the original message to the CE2 device, thereby automatically realizing automatic protection switching when the main tail node/egress node PE2 fails.
  • Figure 15 is a schematic diagram of the network structure and SID allocation of each device in the embodiment of the present disclosure. It is assumed that the network includes PE1, PE2, PE3, PE4, P1, P2, P3, and P4 router devices, among which VPN1 users include two sites CE1 and CE2, and site CE2 is dual-homed to PE2 and PE3, and the traffic from CE1 to CE2 is carried through the SRv6 BE tunnel.
  • VPN1 users include two sites CE1 and CE2
  • site CE2 is dual-homed to PE2 and PE3, and the traffic from CE1 to CE2 is carried through the SRv6 BE tunnel.
  • A:3::B100 assigns VPN SID of VPN1 user to PE3 device
  • A:4::B100 assigns VPN SID of VPN1 customer to PE4 device, that is, A:3::B100 is the primary service SID, A:4::B100 is the backup SID, and the correspondence between the primary service SID and the backup SID of the VPN1 user is configured on the SRv6 Policy head node PE1 device.
  • VPN SID as END.DT6 SID.
  • PE1 receives the message sent by CE1. According to the locally configured backup SID information, it knows that VPN1 has a dual-home protection tail node. Therefore, when encapsulating the outer IPv6 header of the tunnel, it adds an SRH extension header with the active SID (primary VPN SID or Primary SID or Active SID) A:3::B100 and the backup SID A:4::B100, and sets the value of SRH.B-flag to 1.
  • the primary VPN SID A:3::B100 is used as the destination address of the external IP header.
  • PE1 executes the standard SRv6 forwarding process. At this time, there are two situations:
  • the main tail node/egress node PE3 is operating normally.
  • Each node in the network forwards the message along PE1, P1, and P2 to the main tail node/egress node PE3 according to the destination address A:3::B100.
  • the PE3 device finds that the destination A:3::B100 in the message header of the received data packet is the local End.DT6 SID and the SRH.B-flag in the message header is 1. It does not check the Segments Left value in the SRH, but directly deletes the outer IPv6 header and all its extension headers, restores the inner original message, searches the routing table locally, and forwards the original message to the CE2 device.
  • PE1 finds that the destination address A:3::B100 is unreachable and the SRH.B-flag in the packet header is 1, so it searches for the SID after the currently unreachable node (primary VPN SID or Primary SID or Active SID) in SRH.segmentlist in order until it finds the first reachable SID (i.e., the reachable downstream node).
  • PE1 If PE4 is normal, the node corresponding to the backup SID A:4::B100 is reachable, so PE1 reads the backup SID A:4::B100 from the SL[0] position and changes the destination address of the message to the backup SID A:4::B100.
  • the PE1 device continues to send the message to the backup tail node/egress node PE4 according to the new destination address A:4::B100 (backup SID).
  • Figure 24 is a schematic diagram of message forwarding for SRv6 BE dual-homing tail node/egress node fault protection (PE3 fault scenario) in an embodiment of the present disclosure.
  • Figure 24 shows message forwarding in the scenario of primary tail node/egress node PE3 failure.
  • PE4 finds that the destination A:4::B100 in the header of the received data packet is the local End.DT6SID, so it removes the outer IPv6 encapsulation, restores the inner original message, searches the routing table locally, and forwards the original message to CE2, thereby automatically implementing automatic protection switching when the main tail node/egress node PE2 fails.
  • FIG25 is a schematic diagram of the composition structure of the message processing device of the embodiment of the present disclosure. As shown in FIG25, the device includes:
  • the first processing unit 251 is used to add an extension header to the first message, and encapsulate the first SID and the first information in the extension header to obtain a second message; wherein the first information includes at least one backup SID; or, add the first information to the extension header of the first message to obtain the second message; wherein the first information includes at least one backup SID.
  • the first processing unit 251 is configured to:
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID.
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID, including:
  • the encapsulation position of the first information in the segment list is adjacent to the encapsulation position of the first SID in the segment list and is after the encapsulation position of the first SID.
  • the encapsulation position of the backup SID is SL[0].
  • the device is further used for:
  • At least one backup SID in the first information is sorted according to the priority of the backup SID, and the backup SID with the lowest priority is encapsulated at the end of the first information.
  • the device is further used for:
  • the method further comprises:
  • the first SID is a SID of a first flavor or a SID of a first type
  • the remaining backup SIDs in the first information except the backup SID encapsulated in the last position in the first information are SIDs of the first flavor or SIDs of the first type.
  • At least one of the following is also included:
  • the first egress node is a primary tail node of SRv6;
  • the first SID is a SID allocated by the first egress node
  • the backup SID is a SID allocated by a protection node of the first egress node; wherein the protection node is a backup egress node of the first egress node.
  • the backup SID is a SID allocated by a protection node of the first egress node, including:
  • backup SIDs There are multiple backup SIDs, and different backup SIDs are allocated by different protection nodes of the first egress node.
  • the device is further used to: send the second message.
  • the first processing unit 251 can be implemented by a processor in a message processing device.
  • the message processing device provided in the above embodiment performs message processing
  • only the division of the above program modules is used as an example.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • FIG26 is a schematic diagram of the composition structure of the message processing device of the embodiment of the present disclosure. As shown in FIG26, The device comprises:
  • the first transceiver unit 261 is configured to receive a second message; wherein the second message includes a first SID and first information, and the first information includes at least one backup SID;
  • the second processing unit 262 is configured to change the destination address of the second message to a backup SID to obtain a third message when the node corresponding to the first SID is unreachable;
  • the first transceiver unit 261 is further configured to send the third message.
  • the second processing unit 262 is configured to:
  • the destination address of the second message is changed to a reachable backup SID.
  • changing the destination address of the second message to a reachable backup SID includes:
  • the value of the SL pointer is reduced by 1 successively until the node corresponding to the backup SID pointed to by the current pointer is reachable, and then the destination address of the second message is changed to the backup SID pointed to by the current pointer.
  • the first transceiver unit 261 can be implemented by a communication interface in the message processing device; the second processing unit 262 can be implemented by a processor in the message processing device.
  • the message processing device provided in the above embodiment performs message processing
  • only the division of the above program modules is used as an example.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • FIG27 is a schematic diagram of the composition structure of the message processing device of the embodiment of the present disclosure. As shown in FIG27, the device includes:
  • the second transceiver unit 271 is used to receive the second message or the third message
  • the third processing unit 272 is configured to remove the outer message header of the second message or the third message to obtain a fourth message when the destination address in the second message or the third message is the local SID of the second node and the destination address is the SID of the first flavor; and/or, in the second message or When the destination address in the third message is the local SID of the second node and the destination address is the SID of the first type, remove the outer message header of the second message or the third message to obtain a fourth message;
  • the second transceiver unit 273 is further configured to send the fourth message.
  • the destination address is the SID of the first behavior of the first flavor or the SID of the behavior type of the first behavior of the first flavor.
  • the removing the outer message header of the second message or the third message further includes:
  • the step of determining the value of the second information of the second message or the third message is not performed; the outer message header of the second message or the third message is removed;
  • the device is further used for:
  • the first type of SID includes:
  • the second line is the SID of (Behavior) or the second line is the SID of Behavior type.
  • removing the outer message header of the second message or the third message includes:
  • the second information is the segmentleft field information in the outer encapsulation message header SRH.
  • removing the outer message header of the second message or the third message includes:
  • the device is further used for:
  • the SID of the first flavor or the SID of the first type is advertised to the first node and/or the network device through a routing protocol.
  • the second transceiver unit 271 can be a communication interface in the message processing device.
  • the third processing unit 272 can be implemented by a processor in the message processing device.
  • the message processing device provided in the above embodiment performs message processing
  • only the division of the above program modules is used as an example.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • FIG28 is a schematic diagram of the composition structure of the message processing device of the embodiment of the present disclosure. As shown in FIG28, the device includes:
  • the fourth processing unit 281 is used to set the first bit in the first message to the first value, add an extension header to the first message, encapsulate the first SID and the first information in the extension header, and obtain a fifth message; wherein the first information includes at least one backup SID; or, set the first bit in the first message to the first value, and add the first information in the extension header of the first message to obtain a fifth message; wherein the first information includes at least one backup SID.
  • the first bit is at least one reserved bit of the first message.
  • adding an extension header to the first message, and encapsulating the first SID and the first information in the extension header includes:
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID.
  • the encapsulation position of the first information is adjacent to the encapsulation position of the first SID, including:
  • the encapsulation position of the first information in the segment list is adjacent to the encapsulation position of the first SID in the segment list and is after the encapsulation position of the first SID.
  • the encapsulation position of the backup SID is SL[0].
  • the device is further used for:
  • At least one of the following is also included:
  • the first egress node is a primary tail node of SRv6;
  • the first SID is a SID allocated by the first egress node
  • the backup SID is a SID allocated by a protection node of the first egress node; wherein the protection node is a backup egress node of the first egress node.
  • the backup SID is a SID allocated by a protection node of the first egress node, including:
  • backup SIDs There are multiple backup SIDs, and different backup SIDs are allocated by different protection nodes of the first egress node.
  • the device is further used to: send the fifth message.
  • the fourth processing unit 281 can be implemented by a processor in a message processing device.
  • the message processing device provided in the above embodiment performs message processing
  • only the division of the above program modules is used as an example.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • FIG29 is a schematic diagram of the composition structure of the message processing device of the embodiment of the present disclosure. As shown in FIG29, the device includes:
  • the third transceiver unit 291 is configured to receive a fifth message; wherein the fifth message includes a first bit, a first SID, and first information, and the first information includes at least one backup SID;
  • a fifth processing unit 292 configured to change the destination address of the fifth message to a backup SID to obtain a sixth message when the node corresponding to the first SID is unreachable and the first bit is a first value;
  • the fifth transceiver unit is further used to send the sixth message.
  • changing the destination address of the fifth message to a backup SID includes:
  • the destination address of the fifth message is changed to a reachable backup SID.
  • changing the destination address of the fifth message to a reachable backup SID includes:
  • Subtract 1 from the value of the SL pointer, and change the destination address of the fifth message to the backup SID pointed to by the current pointer;
  • the value of the SL pointer is reduced by 1 successively until the node corresponding to the backup SID pointed to by the current pointer is reachable, and then the destination address of the fifth message is changed to the backup SID pointed to by the current pointer.
  • the third transceiver unit 291 can be implemented by a communication interface in the message processing device; the fifth processing unit 292 can be implemented by a processor in the message processing device.
  • the message processing device provided in the above embodiment performs message processing
  • only the division of the above program modules is used as an example.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • FIG30 is a schematic diagram of the composition structure of the message processing device of the embodiment of the present disclosure. As shown in FIG30, the device includes:
  • the fourth transceiver unit 301 is used to receive the fifth message or the sixth message;
  • a sixth processing unit 302 configured to, when the destination address in the fifth message or the sixth message is the local SID of the second node and the first bit in the fifth message or the sixth message is the first value, remove the outer message header of the fifth message or the sixth message to obtain a seventh message;
  • the sixth transceiver unit is further used to send the seventh message.
  • removing the outer message header of the second message or the third message further includes:
  • the step of determining the value of the third information of the fifth message or the sixth message is not performed; the outer message header of the fifth message or the sixth message is removed;
  • the value of the third information of the fifth message or the sixth message is at least one specific value; and remove the outer message header of the fifth message or the sixth message.
  • the device is further used for:
  • the third information is the segmentleft field information in the outer encapsulation message header SRH.
  • removing the outer message header of the fifth message or the sixth message includes:
  • the fourth transceiver unit 301 can be implemented by a communication interface in the message processing device; the sixth processing unit 302 can be implemented by a processor in the message processing device.
  • the message processing device provided in the above embodiment performs message processing
  • only the division of the above program modules is used as an example.
  • the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • the embodiment of the present disclosure further provides a network device, which may be the first node, the network node, or the second node as shown in FIG31 , including:
  • Communication interface 311, capable of exchanging information with other devices
  • the processor 312 is connected to the communication interface 311 and is used to execute the method provided by one or more technical solutions on the network device side when running the computer program.
  • the computer program is stored in the memory 313.
  • bus system 314 is used to realize the connection and communication between these components.
  • the bus system 314 also includes a power bus, a control bus and a status signal bus.
  • various buses are marked as bus system 314 in Figure 31.
  • the memory 313 in the embodiment of the present disclosure is used to store various types of data to support the network device Operation of network device 310.
  • Examples of such data include: any computer program for operating on network device 310.
  • the method disclosed in the above embodiment of the present disclosure can be applied to the processor 312, or implemented by the processor 312.
  • the processor 312 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 312 or the instruction in the form of software.
  • the above processor 312 may be a general processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • the processor 312 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present disclosure.
  • the general processor may be a microprocessor or any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present disclosure can be directly embodied as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a storage medium, which is located in the memory 313.
  • the processor 312 reads the information in the memory 313 and completes the steps of the above method in combination with its hardware.
  • the network device 310 can be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), field programmable gate array (FPGA), general processor, controller, microcontroller (MCU), microprocessor, or other electronic components to execute the aforementioned method.
  • ASIC application specific integrated circuits
  • DSP digital signal processor
  • PLD programmable logic device
  • CPLD complex programmable logic device
  • FPGA field programmable gate array
  • general processor controller
  • controller microcontroller
  • microprocessor or other electronic components to execute the aforementioned method.
  • the memory (memory 313) of the embodiment of the present disclosure can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a ferromagnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only disk (CD-ROM).
  • ROM read-only memory
  • PROM programmable read-only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • FRAM ferromagnetic random access memory
  • flash memory a magnetic surface memory
  • CD-ROM Compact disc read-only disk
  • magnetic surface storage can be disk storage or tape storage.
  • Volatile memory can be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • Synchronous Static Random Access Memory SSRAM
  • dynamic random access memory DRAM
  • synchronous dynamic random access memory Synchronous Dynamic Random Access Memory, SDRAM
  • double data rate synchronous dynamic random access memory Double Data Rate Synchronous Dynamic Random Access Memory, DDRSDRAM
  • enhanced synchronous dynamic random access memory Enhanced Synchronous Dynamic Random Access Memory, ESDRAM
  • synchronous connection dynamic random access memory SyncLink Dynamic Random Access Memory, SLDRAM
  • direct memory bus random access memory Direct Rambus Random Access Memory, DRRAM
  • the memory described in the embodiments of the present disclosure is intended to include but is not limited to these and any other suitable types of memory.
  • the embodiment of the present disclosure further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, a memory storing a computer program, and the computer program can be executed by the processor 312 of the network device 310 to complete the steps described in the aforementioned network device side method.
  • the computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un procédé et un appareil de traitement de message, ainsi qu'un dispositif et un support de stockage. Le procédé consiste à : ajouter un en-tête d'extension à un premier message, et encapsuler un premier ID de segment (SID) et des premières informations dans l'en-tête d'extension, de façon à obtenir un second message, les premières informations comprenant au moins un SID de sauvegarde ; ou ajouter des premières informations à un en-tête d'extension d'un premier message, de façon à obtenir un second message, les premières informations comprenant au moins un SID de sauvegarde.
PCT/CN2023/125621 2022-10-21 2023-10-20 Procédé et appareil de traitement de message, et dispositif et support de stockage WO2024083219A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211296073.0 2022-10-21
CN202211296073.0A CN117917886A (zh) 2022-10-21 2022-10-21 报文处理方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024083219A1 true WO2024083219A1 (fr) 2024-04-25

Family

ID=90729729

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/125621 WO2024083219A1 (fr) 2022-10-21 2023-10-20 Procédé et appareil de traitement de message, et dispositif et support de stockage

Country Status (2)

Country Link
CN (1) CN117917886A (fr)
WO (1) WO2024083219A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111935014A (zh) * 2020-10-19 2020-11-13 网络通信与安全紫金山实验室 基于SRv6网络的报文转发方法、装置、存储介质及电子设备
CN112511418A (zh) * 2020-06-22 2021-03-16 中兴通讯股份有限公司 报文指示方法、装置、设备和存储介质
CN113079089A (zh) * 2020-01-03 2021-07-06 华为技术有限公司 业务链的故障保护方法、装置、设备、系统及存储介质
WO2021169258A1 (fr) * 2020-02-24 2021-09-02 华为技术有限公司 Procédé d'acheminement de message, procédé de publication d'informations de routage, appareil et système
CN113794637A (zh) * 2021-08-20 2021-12-14 新华三信息安全技术有限公司 Sid列表的处理方法及装置
CN113973074A (zh) * 2021-10-26 2022-01-25 新华三信息安全技术有限公司 一种报文处理方法、装置、电子设备及介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113079089A (zh) * 2020-01-03 2021-07-06 华为技术有限公司 业务链的故障保护方法、装置、设备、系统及存储介质
WO2021169258A1 (fr) * 2020-02-24 2021-09-02 华为技术有限公司 Procédé d'acheminement de message, procédé de publication d'informations de routage, appareil et système
CN112511418A (zh) * 2020-06-22 2021-03-16 中兴通讯股份有限公司 报文指示方法、装置、设备和存储介质
CN111935014A (zh) * 2020-10-19 2020-11-13 网络通信与安全紫金山实验室 基于SRv6网络的报文转发方法、装置、存储介质及电子设备
CN113794637A (zh) * 2021-08-20 2021-12-14 新华三信息安全技术有限公司 Sid列表的处理方法及装置
CN113973074A (zh) * 2021-10-26 2022-01-25 新华三信息安全技术有限公司 一种报文处理方法、装置、电子设备及介质

Also Published As

Publication number Publication date
CN117917886A (zh) 2024-04-23

Similar Documents

Publication Publication Date Title
US11218408B2 (en) Packet processing method, device, and system
WO2021169258A1 (fr) Procédé d'acheminement de message, procédé de publication d'informations de routage, appareil et système
CN112787921B (zh) 报文传输方法、代理节点及存储介质
WO2021180077A1 (fr) Procédé d'établissement de chemin, procédé et appareil de transmission de données, nœud de réseau, et support de stockage
JP7432095B2 (ja) ＳＲｖ６サービス機能チェーンでパケットを転送する方法、ＳＦＦ、およびＳＦデバイス
WO2020182156A1 (fr) Procédé de transfert de message dans un réseau, nœud de réseau et système de réseau
JP7443537B2 (ja) パケット処理方法、パケット処理装置、およびパケット処理システム
CN112019433B (zh) 一种报文转发方法和装置
CN112953831A (zh) 一种报文转发方法及装置
US20090135833A1 (en) Ingress node and egress node with improved packet transfer rate on multi-protocol label switching (MPLS) network, and method of improving packet transfer rate in MPLS network system
WO2011103781A2 (fr) Procédé, dispositif pour la mise en oeuvre de la séparation d'identificateur et de localisateur et procédé d'encapsulation de données
JP6488426B2 (ja) マルチキャストデータパケット転送
US20220255772A1 (en) Packet sending method, apparatus, and system
WO2018214359A1 (fr) Procédé de traitement d'un paquet de données, dispositif de réseau d'accès et support de stockage lisible non transitoire
CN112737954B (zh) 报文处理方法、装置、系统、设备及存储介质
KR20220047854A (ko) Ｓｒ 네트워크에서의 패킷 포워딩 방법, 장치 및 시스템
WO2021088561A1 (fr) Procédé, dispositif et équipement de partage de charge dans un réseau de reproduction explicite à indice d'élément binaire
US11929923B2 (en) Packet transmission method and apparatus
CN112511988A (zh) 报文转发方法、设备、系统、网络设备和存储介质
WO2020182085A1 (fr) Procédé et dispositif de transmission pour un message
US20240056392A1 (en) Communication method and apparatus
WO2021073357A1 (fr) Procédé, dispositif, système et appareil de traitement de paquets, et support de stockage
WO2023045793A1 (fr) Procédé et appareil de détection de boucle
WO2024083219A1 (fr) Procédé et appareil de traitement de message, et dispositif et support de stockage
WO2023284774A1 (fr) Procédé de traitement de message et appareil associé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23879205

Country of ref document: EP

Kind code of ref document: A1