CN115037675A

CN115037675A - Message forwarding method and device

Info

Publication number: CN115037675A
Application number: CN202210604521.2A
Authority: CN
Inventors: 翟翔
Original assignee: New H3C Technologies Co Ltd Hefei Branch
Current assignee: New H3C Technologies Co Ltd Hefei Branch
Priority date: 2022-05-31
Filing date: 2022-05-31
Publication date: 2022-09-09
Anticipated expiration: 2042-05-31
Also published as: CN115037675B

Abstract

The application provides a message forwarding method and device. The method is applied to a source node on any primary path in SRv6 network, and comprises: determining a TI-LFA FRR path corresponding to the main path and constraint path information corresponding to the TI-LFA FRR path according to the acquired segment identification information and link segment identification information of other network nodes except a source node in the SRv6 network; when a service message is received and a fault of the main path is monitored, if segment identification information and/or link segment identification information of at least one designated network node which supports MPLS SR but does not support SRv6 exists in the constraint path information, the service message is packaged according to the constraint path information and a preset packaging rule, and the packaged service message is forwarded to a next hop network node. The method and the device can solve the problem of packet loss when the main path fails, and improve network experience.

Description

Message forwarding method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for forwarding a packet.

Background

Segment Routing (SR) is a protocol designed based on the concept of source Routing to forward packets in a network. The SR divides the network path into segments, assigns Segment Identifiers (SID) to the segments or nodes, and enables the data packet to be transmitted through the forwarding path indicated by the Segment identifiers by carrying the sequentially arranged Segment identifiers in the data packet.

Segment Routing and Internet Protocol version six (Segment Routing Internet Protocol version6, SRv 6) refers to combining SR technology with Internet Protocol version six (Internet Protocol version6, IPv6) Protocol, defining SRv6 SID instantiated according to the format of IPv6 address, and implementing SR function based on the forwarding plane of IPv 6.

In SRv6 network, when a TI-LFA FRR (Topology-IndepEndent incoming Loop-free alternative Fast Reroute) path corresponding to the path needs to be determined, a source node on any main path needs to obtain an END SID (i.e., a Segment identifier of a network node that supports both multi-protocol Label Switching (MPLS) and SRv 6) and an END point three-Layer cross-connect Segment identifier (i.e., an END point with Layer-3 cross-connect-id, i.e., a link Segment identifier corresponding to a network node that supports SRv 6) of each network node in the entire SRv6 network, so as to determine the TI-LFA FRR path corresponding to the path.

However, in the case that an individual network node in the SRv6 network supports MPLS SR but does not support SRv6, because the corresponding END SID and end.x SID cannot be provided, the source node cannot determine the TI-LFA FRR path corresponding to the path, so that when the source node forwards a service packet using the primary path, once the primary path fails, for example, a certain network node or a certain link on the primary path fails, the source node needs to re-determine a new forwarding path and then forwards the service packet using the new forwarding path because there is no corresponding backup path, which may cause a long-time packet loss problem, thereby resulting in poor network experience.

Disclosure of Invention

In order to overcome the problems in the related art, the application provides a message forwarding method and a message forwarding device.

According to a first aspect of the embodiments of the present application, there is provided a packet forwarding method, where the method is applied to a source node on any primary path in SRv6 networks, and the method includes:

determining, according to the acquired segment identification information and link segment identification information of other network nodes in the SRv6 network except the source node, a TI-LFA FRR path corresponding to the main path and constraint path information corresponding to the TI-LFA FRR path, where when any other network node supports both MPLS SR and SRv6, the segment identification information of the other network node is an End SID of the other network node, and the link segment identification information of the other network node is an end.x SID of the other network node; when any other network Node supports the MPLS SR but does not support SRv6, the segment identification information of the other network Node is the Node SID of the other network Node, the link segment identification information of the other network Node is the Adj SID of the other network Node, the constraint path information includes the segment identification information and/or the link segment identification information of at least one designated network Node on the TI-LFA FRR path, and the total number of all designated network nodes is not greater than 3, and all designated network nodes do not include the source Node and the destination Node on the main path;

when a service message is received and a fault of the main path is monitored, if segment identification information and/or link segment identification information of at least one designated network node which supports MPLS SR but does not support SRv6 exists in the constraint path information, the service message is packaged according to the constraint path information and a preset packaging rule, and the packaged service message is forwarded to a next-hop network node, wherein the next-hop network node is determined by the source node based on a backup forwarding table corresponding to the TI-LFA FRR path.

According to a second aspect of the embodiments of the present application, there is provided a packet forwarding apparatus, where the apparatus is applied to a source node on any primary path in an SRv6 network, the apparatus includes:

a determining module, configured to determine, according to the acquired segment identification information and link segment identification information of other network nodes in the SRv6 network except the source node, a TI-LFA FRR path corresponding to the main path and constraint path information corresponding to the TI-LFA FRR path, where when any other network node supports both MPLS SR and SRv6, the segment identification information of the other network node is an End SID of the other network node, and the link segment identification information of the other network node is an end.x SID of the other network node; when any other network Node supports the MPLS SR but does not support SRv6, the segment identification information of the other network Node is the Node SID of the other network Node, the link segment identification information of the other network Node is the Adj SID of the other network Node, the constraint path information includes the segment identification information and/or the link segment identification information of at least one designated network Node on the TI-LFA FRR path, and the total number of all designated network nodes is not greater than 3, and all designated network nodes do not include the source Node and the destination Node on the main path;

a first encapsulation forwarding module, configured to, when receiving a service packet and monitoring that a fault occurs in the main path, if segment identification information and/or link segment identification information of at least one designated network node that supports MPLS SR but does not support SRv6 exists in the constrained path information, encapsulate the service packet according to the constrained path information and a preset encapsulation rule, and forward the encapsulated service packet to a next-hop network node, where the next-hop network node is determined by the source node based on a backup forwarding table corresponding to the TI-LFA FRR path.

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

in this embodiment of the present application, in a case that SRv6 a network has individual network nodes that support MPLS SR but do not support SRv6, for a source Node on any main path, based on an End SID and an end.x SID of a network Node that supports MPLS SR and SRv6 in a SRv6 network and a Node SID and/or an Adj SID of a network Node that supports MPLS SR but does not support SRv6, a TI-LFA FRR path corresponding to the path may be determined, so that in a case that the main path fails, the source Node may timely forward a relevant service packet using constraint path information corresponding to the TI-LFA FRR path corresponding to the path, and a packet loss problem may not occur, thereby improving network experience.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic flowchart of a message forwarding method according to an embodiment of the present application;

fig. 2A is a schematic networking diagram of SRv6 network according to an embodiment of the present disclosure;

fig. 2B is a schematic diagram of a packet format of a service packet at a network node a1, a network node MER2, and a network node MER1 side in the networking shown in fig. 2A according to the embodiment of the present application;

fig. 3A is a second schematic diagram of a network SRv6 according to an embodiment of the present invention;

fig. 3B is a schematic diagram of a packet format of a service packet at a network node a1, a network node A3, a network node MER2, and a network node MER1 in the networking shown in fig. 3A according to the embodiment of the present application;

fig. 4A is a third schematic diagram of a SRv6 network according to an embodiment of the present invention;

fig. 4B is a schematic diagram of a packet format of a service packet at a network node a1, a network node A3, a network node MER2, and a network node MER1 in the networking shown in fig. 4A according to the embodiment of the present application;

fig. 5 is a schematic structural diagram of a message forwarding method provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The words "if" or "if" as used herein may be interpreted as "at … …" or "at … …" depending on the context.

Next, examples of the present application will be described in detail.

An embodiment of the present application provides a packet forwarding method, which is applied to a source node on any main path in an SRv6 network, and as shown in fig. 1, the method may include the following steps:

s11, determining the TI-LFA FRR path corresponding to the main path and the constraint path information corresponding to the TI-LFA FRR path according to the acquired segment identification information and link segment identification information of other network nodes except the source node in the SRv6 network.

In this step, when any other network node supports both MPLS SR and SRv6, the segment id information of the other network node is the End SID of the other network node, and the link segment id information of the other network node is the end.x SID of the other network node.

When any other network Node supports MPLS SR but does not support SRv6, the segment id information of the other network Node is the Node SID of the other network Node, and the link segment id information of the other network Node is the Adj SID of the other network Node.

In addition, in this step, the constraint path information includes segment identification information and/or link segment identification information of at least one designated network node on the TI-LFA FRR path, and the total number of all designated network nodes is not greater than 3, the source node and the destination node on the main path are not included in all designated network nodes, and the segment identification information and/or link segment identification information of all designated network nodes on the TI-LFA FRR path included in the constraint path information are arranged in order from near to far according to all designated network nodes on the TI-LFA FRR path.

Here, once the TI-LFA FRR path is determined for any given network node in the constrained path information, the relevant information of the given network node included in the constrained path information is also determined, which may be the segment identification information of the given network node, the link segment identification information of the given network node, or the segment identification information and the link segment identification information of the given network node.

S12, when receiving the service message and monitoring the main path to have a fault, if the constraint path information has at least one segment identification information and/or link segment identification information of a designated network node which supports MPLS SR but does not support SRv6, encapsulating the service message according to the constraint path information and a preset encapsulation rule, and forwarding the encapsulated service message to a next hop network node.

In this step, the next hop network node is determined for the source node based on the backup forwarding table corresponding to the TI-LFA FRR path.

It should be noted that, in this embodiment of the application, for the source node, the segment identification information and the link segment identification information of other network nodes except the source node in the network may be obtained SRv6 by analyzing a Label Switched Path (LSP) message sent by a neighboring network node.

Moreover, for other network nodes which support both MPLS SR and SRv6, the source Node may obtain the End SID and the end.x SID, and the Node SID and the Adj SID of the other network Node; for other network nodes that support MPLS SR but do not support SRv6, the source Node may acquire the Node SID and Adj SID of this other network Node.

When determining the TI-LFA FRR path corresponding to the main path and the constraint path information corresponding to the TI-LFA FRR path, the subsequent source Node uses the End SID and the end.x SID of the other network Node that supports both MPLS SR and SRv6, and the Node SID and the Adj SID of the other network Node that supports MPLS SR but does not support SRv6 to determine, and the specific determination process is similar to the existing determination process for determining the corresponding TI-LFA FRR path and the relevant constraint path information only using the End SID and the end.x SID of the network Node that supports both MPLS SR and SRv6, and is not described in detail herein.

Here, the link overhead (Cost) value of the TI-LFA FRR path is minimum, and corresponding constraint path information (also referred to as replay List) records at least one segment identifier and/or link segment identifier of a designated network node that can accurately direct the service packet to a corresponding destination node.

Specifically, in step S12, when the total number of all designated nodes is 1, the source node may encapsulate the service packet in the following manner:

and when it is determined that the specified network Node included in the constraint path information supports MPLS SR but does not support SRv6 according to the constraint path information, encapsulating first MPLS label information for the service packet to obtain an encapsulated service packet, where the first MPLS label information includes a Node SID and/or an Adj SID of the specified network Node included in the constraint path information.

It should be noted that, in this embodiment of the present application, for any specified network node included in the constrained path information, if the segment identification information and/or the link segment identification information of the specified network node in the constrained path information is the End SID and/or the end.x SID of the specified network node, it is determined that the specified network node supports both MPLS SR and SRv 6; if the segment ID information and/or link segment ID information of the designated network Node is the Node SID and/or Adj SID of the designated network Node, then it is determined that the designated network Node supports MPLS SR but not SRv 6.

Here, the encapsulated service packet is used to indicate that the designated network node pops up the first MPLS label information and then forwards the MPLS label information to the corresponding destination node when receiving the encapsulated service packet.

When the total number of all the designated nodes is 2, the source node may encapsulate the service packet in the following manner:

for a first designated network Node and a second designated network Node in the constrained path information, if it is determined that the first designated network Node supports both MPLS SR and SRv6 and the second designated network Node supports MPLS SR but not SRv6 according to the constrained path information, encapsulating a first IPv6 Header, a first Routing extension Header (SRH) Header and second MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address in the first IPv6 Header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or end.x SID of the first designated network Node included in the constrained path information, the Segment list information in the first SRH Header includes the End SID and/or end.x of the first designated network Node, and the second SID label information includes a Node SID and/or Adj of the second designated network Node included in the constrained path information, the second MPLS label information is positioned behind the first SRH header; here, the first SRH header further includes information such as a remaining Segment quantity (SL) value, where the SL value in the first SRH header is 0, and the Segment List information in the first SRH header may specifically be Segment List [0] ═ End SID and/or end.x SID of the first specified network node;

if it is determined that the first designated network Node supports MPLS SR but not SRv6 and the second designated network Node supports MPLS SR and SRv6 according to the constraint path information, encapsulating a third MPLS label information, a second IPv6 header, and a second SRH header for the service packet to obtain an encapsulated service packet, where the third MPLS label information includes a Node SID and/or Adj SID of the first designated network Node included in the constraint path information, a source IPv6 address in the second IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or an end.x SID of the two designated network nodes included in the constraint path information, a segment list information in the second SRH header includes the End SID and/or the end.x of the second designated network Node, and the third label information is located in front of the second SRH header; here, the second SRH header further includes information such as SL value, the SL value in the second SRH header is 0, and the Segment List information in the second SRH header may specifically be Segment List [0] ═ End SID and/or end.x SID of the second specified network node;

if it is determined that the first designated network node and the second designated network node both support MPLS SR but not SRv6 according to the constrained path information, encapsulating fourth MPLS label information for the service packet, where the fourth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first designated network Node and the Node SID and/or Adj SID of the second designated network Node are included in the constraint path information.

In this manner, for the source node, in a case that it is determined that the first designated network node supports both MPLS SR and SRv6 according to the constraint path information, and the second designated network node supports MPLS SR but does not support SRv6, the encapsulated packet may indicate that the first designated network node decapsulates the encapsulated packet by SRv6, further forward the decapsulated packet (carrying related MPLS label information) to the second designated network node, and forward the decapsulated packet to the corresponding destination node after the second designated network node pops up the related MPLS label information in the decapsulated packet.

Under the condition that it is determined that the first designated network node supports MPLS SR but not SRv6 according to the constraint path information, and the second designated network node supports both MPLS SR and SRv6, the encapsulated packet may indicate the first designated network node to pop up relevant MPLS label information in the encapsulated packet, and then forward to the second designated network node, which performs SRv6 decapsulation and then forwards to the corresponding destination node.

Under the condition that it is determined that the first designated network node and the second designated network node both support MPLS SR but do not support SRv6 according to the constraint path information, the encapsulated packet may indicate that the first designated network node pops up first-layer MPLS label information in the encapsulated packet, and then forwards the first-layer MPLS label information to the second designated network node, and the second-layer MPLS label information is popped up by the second designated network node and then forwards the second-layer MPLS label information to the corresponding destination node.

When the total number of all the designated nodes is 3, encapsulating the service packet according to the constraint path information and a preset encapsulation rule, specifically comprising:

aiming at a first designated network node, a second designated network node and a third designated network node in the constrained path information, if the first designated network node supports both MPLS SR and SRv6, the second designated network node supports MPLS SR but not SRv6 and the third designated network node supports both MPLS SR and SRv6 according to the constrained path information, encapsulating a third IPv6 header, a third SRH header, fifth MPLS label information, a fourth IPv6 header and a fourth SRH header for a service packet to obtain an encapsulated service packet, wherein a source IPv6 address of the third IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.X SID of the first designated network node included in the constrained path information, and segment list information in the third SRH header includes an End SID and/or an end.X SID of the first designated network node, the fifth MPLS label information includes the Node SID and/or Adj SID of the second designated network Node included in the constrained path information, the source IPv6 address of the fourth IPv6 header is the IPv6 address of the source Node, the destination IPv6 address is the End SID and/or end.x SID of the third designated network Node included in the constrained path information, the segment list information in the fourth SRH header includes the End SID and/or end.x SID of the third designated network Node, and the fifth MPLS label information is located in front of the fourth IPv6 header and behind the third SRH header; here, the third SRH header and the fourth SRH header each further include information such as SL value, where the SL value in the third SRH header and the fourth SRH header is 0, the Segment List information in the third SRH header may specifically be Segment List [0] ═ End SID and/or end.x SID of the first specified network node, and the Segment List information in the fourth SRH header may specifically be Segment List [0] ═ End SID and/or end.x SID of the third specified network node;

if it is determined that the first designated network node and the second designated network node both support MPLS SR and SRv6, and the third designated network node supports MPLS SR but not SRv6, then encapsulating a fifth IPv6 header, a fifth SRH header, and sixth MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the fifth IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network node included in the constrained path information, and the fifth SRH header sequentially includes: the End SID and/or end.x SID of the second designated network Node and the End SID and/or end.x SID of the first designated network Node, the sixth MPLS label information includes the Node SID and/or Adj SID of the third designated network Node included in the constrained path information, and the sixth MPLS label information is located behind the fifth SRH header; here, the fifth SRH header further includes information such as an SL value, where the SL value in the fifth SRH header is 1, and the segment list information in the fifth SRH header may specifically be: segment List [0] End SID and/or end.x SID of the second designated network node, and Segment List [1] End SID and/or end.x SID of the first designated network node;

if it is determined that the first designated network node supports both MPLS SR and SRv6 according to the constraint path information, and the second designated network node and the third designated network node both support MPLS SR but not SRv6, encapsulating a sixth IPv6 header, a sixth SRH header, and seventh MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the sixth IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network node included in the constraint path information, a segment list information in the sixth SRH header includes the End SID and/or the end.x SID of the first designated network node, and the seventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the second designated network Node and the Node SID and/or Adj SID of the third designated network Node included in the constraint path information, and the seventh MPLS label information is located behind the sixth SRH header; here, the sixth SRH header further includes information such as an SL value, where the SL value in the sixth SRH header is 0, and the Segment List information in the sixth SRH header may specifically be Segment List [0] ═ the End SID and/or the end.x SID of the first specified network node;

if it is determined that the first designated network Node supports MPLS SR but does not support SRv6, the second designated network Node and the third designated network Node both support MPLS SR and support SRv6 according to the constraint path information, encapsulating an eighth MPLS label information, a seventh IPv6 header and a seventh SRH header for the service packet to obtain an encapsulated service packet, where the eighth MPLS label information includes a Node SID and/or Adj SID of the first designated network Node included in the constraint path information, a source IPv6 address of the seventh IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or end.x SID of the second designated network Node included in the constraint path information, and the seventh SRH header sequentially includes: the End SID and/or end.x SID of the third designated network node and the End SID and/or end.x SID of the second designated network node included in the constrained path information, wherein the eighth MPLS label information is located in front of the seventh IPv6 header; here, the seventh SRH header further includes information such as an SL value, the SL value in the seventh SRH header is 1, and the segment list information in the seventh SRH header may specifically be: segment List [0] is the End SID and/or end.x SID of the third designated network node, and Segment List [1] is the End SID and/or end.x SID of the second designated network node;

if it is determined that the first designated network Node supports the MPLS SR but not SRv6, the second designated network Node supports both the MPLS SR and SRv6, and the third designated network Node supports the MPLS SR but not SRv6 according to the constrained path information, encapsulating ninth MPLS label information, an eighth IPv6 header, an eighth SRH header, and tenth MPLS label information for the service packet to obtain an encapsulated service packet, where the ninth MPLS label information includes the Node SID and/or Adj SID of the first designated network Node included in the constrained path information, the source IPv6 address of the eighth IPv6 header is the IPv6 address of the source Node, the destination IPv6 address is the End SID and/or end.x SID of the second designated network Node included in the constrained path information, and the segment list information in the eighth SRH header includes the End SID and/or end.x SID of the second designated network Node, tenth MPLS label information includes the Node SID and/or AdjSID of the third designated network Node included in the constraint path information, the ninth MPLS label information is located before the eighth IPv6 header, and the tenth MPLS label information is located before the eighth SRH header; here, the eighth SRH header further includes information such as SL value, the SL value in the eighth SRH header is 0, and the Segment List information in the eighth SRH header may specifically be Segment List [0] ═ End SID and/or end.x SID of the second designated network node;

if it is determined according to the constrained path information that both the first designated network node and the second designated network node support MPLS SR but not SRv6, and the third designated network node supports MPLS SR and also supports SRv6, then encapsulating eleventh MPLS label information, a ninth IPv6 header, and a ninth SRH header for the service packet to obtain an encapsulated service packet, where the eleventh MPLS label information sequentially includes: the Node SID and/or AdjSID of the first designated network Node and the Node SID and/or AdjSID of the second designated network Node included in the constrained path information, a source IPv6 address of a ninth IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is a segment list information in a ninth SRH header of the End SID and/or end.x SID of the third designated network Node included in the constrained path information, where the segment list information includes the End SID and/or end.x SID of the third designated network Node, and the eleventh MPLS label information is located in front of the ninth IPv6 header; here, the ninth SRH header further includes information such as SL value, the SL value in the ninth SRH header is 0, and the Segment List information in the ninth SRH header may specifically be Segment List [0] ═ End SID and/or end.x SID of the third designated network node;

if it is determined that the first designated network node, the second designated network node and the third designated network node all support MPLS SR but do not support SRv6 according to the constrained path information, encapsulating twelfth MPLS label information for the service packet to obtain the encapsulated service packet, where the twelfth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first designated network Node included in the constraint path information, the Node SID and/or Adj SID of the second designated network Node included in the constraint path information, and the Node SID and/or Adj SID of the third designated network Node included in the constraint path information.

In this manner, for the source node, in a case that it is determined that the first designated network node supports both MPLS SR and SRv6 according to the constraint path information, the second designated network node supports MPLS SR but not MPLS SR SRv6, and the third designated network node supports both MPLS SR and SRv6, the encapsulated packet may instruct the first designated network node to decapsulate the encapsulated packet once SRv6, forward the decapsulated packet further to the second designated network node, pop up relevant MPLS label information in the decapsulated packet by the second designated network node, forward the decapsulated packet to the third designated network node, perform SRv6 decapsulation again by the third designated network node, and forward the decapsulated packet to the corresponding destination node.

Under the condition that the first designated network node and the second designated network node both support MPLS SR and support SRv6 and the third designated network node supports MPLS SR but does not support SRv6 according to the constraint path information, the encapsulated packet can indicate that the first designated network node changes the encapsulated service packet (changes the destination address in the corresponding IPv6 header and the SL value in the corresponding SRH header), and then forwards the encapsulated service packet to the second designated network node, the second designated network node decapsulates the changed packet by SRv6, and further forwards the decapsulated packet to the third designated network node, and the third designated network node pops up related MPLS label information in the decapsulated packet and then forwards the decapsulated packet to the corresponding destination node.

When it is determined that the first designated network node supports both MPLS SR and SRv6 according to the constraint path information, and the second designated network node and the third designated network node both support MPLS SR but do not support SRv6, the encapsulated packet may indicate that the first designated network node decapsulates the encapsulated service packet SRv6, further forward the decapsulated packet to the second designated network node, further forward to the third designated network node after the first layer of MPLS label information is popped up by the second designated network node, and forward to the corresponding destination node after the second layer of MPLS label information is popped up by the third designated network node.

Under the condition that it is determined that the first designated network node supports MPLS SR but does not support SRv6, and that the second designated network node and the third designated network node both support MPLS SR and SRv6 according to the constraint path information, the encapsulated packet may indicate that the first designated network node pops up relevant MPLS label information in the encapsulated service packet, and then further forward the encapsulated service packet to the second designated network node, the second designated network node modifies the encapsulated service packet (modifies the destination address in the corresponding IPv6 header and the value of SL in the corresponding SRH header), and then forwards the modified packet to the third designated network node, and the third designated network node performs SRv6 decapsulation on the modified packet, and then forwards the modified packet to the corresponding destination node.

When it is determined that the first designated network node supports the MPLS SR but not SRv6, the second designated network node supports both the MPLS SR and SRv6, and the third designated network node supports the MPLS SR but not SRv6 according to the constraint path information, the encapsulated packet may indicate the first designated network node to pop up the relevant MPLS label information in the encapsulated service packet, and then further forward the relevant MPLS label information to the second designated network node, the second designated network node performs SRv6 decapsulation on the encapsulated service packet and then forwards the encapsulated service packet to the third designated network node, and the third designated network node pops up the relevant MPLS label information in the decapsulated packet and then forwards the encapsulated service packet to the corresponding destination node.

Under the condition that it is determined that the first designated network node and the second designated network node both support MPLS SR but not SRv6 according to the constraint path information, and the third designated network node supports both MPLS SR and SRv6, the encapsulated packet may indicate that the first designated network node pops up first-layer MPLS label information in the encapsulated service packet, and then further forward the first designated network node to the second designated network node, and the second designated network node continues to pop up second-layer MPLS label information and then forward the second-layer MPLS label information to the third designated network node, and the third designated network node performs SRv6 decapsulation on the third designated network node and then forwards the third designated network node to the corresponding destination node.

Under the condition that it is determined that the first designated network node, the second designated network node and the third designated network node all support MPLS SR but do not support SRv6 according to the constraint path information, the encapsulated packet may indicate that the first designated network node pops up first-layer MPLS label information in the encapsulated service packet, and then further forwards the first-layer MPLS label information to the second designated network node, the second designated network node continuously pops up second-layer MPLS label information and then forwards the second-layer MPLS label information to the third designated network node, and the third designated network node continuously pops up third-layer MPLS label information and then forwards the third-layer MPLS label information to the corresponding destination node.

Further, in this embodiment of the present application, for the source node, when a service packet is received and a failure of the main path is monitored, if segment identification information and/or link segment identification information of a specified network node that supports MPLS SR but does not support SRv6 does not exist in the constrained path information, the process is still performed according to the existing flow, that is, a tenth IPv6 header and a tenth SRH header are encapsulated in the service packet, so as to obtain an encapsulated service packet; the source IPv6 address of the tenth IPv6 header is the IPv6 address of the source node, the destination IPv6 address is the End SID and/or end.x SID of the first designated network node included in the constrained path information, the tenth SRH header includes the End SID and/or end.x SID of all designated network nodes included in the constrained path information, and the End SID and/or end.x SID of all designated network nodes are arranged in the order from far to near according to all designated network nodes on the TI-LFA FRR path.

The following describes the above message forwarding method in detail with reference to specific embodiments.

Example one

As shown in fig. 2A, assume that network node MER1 (shown in fig. 2A as MER1), network node a1 (shown in fig. 2A as a1), and network node a2 (shown in fig. 2A as a2) all support both MPLS SRs and SRv 6; assume that network node MER2 (shown in fig. 2A as MER2) supports MPLS SR but not SRv 6.

Assume that the primary path is network node a 1- > network node MER 1. Moreover, assume that the network Node a1 is a source Node, and assume that the network Node a1 determines that the TI-LFA FRR path corresponding to the main path is the network Node a 1- > the network Node a 2- > the network Node MER2 according to the End SID and the end.x SID of the network Node a2, the Node SID and the Adj SID of the network Node MER2, and the End SID and the end.x SID of the network Node MER1, and the corresponding constraint path information includes the Node SID and the Adj SID of the network Node MER 2.

Assuming that at a certain moment, the network Node a1 receives the traffic packet and finds that the primary path fails, for example, a link between the network Node a1 and the network Node MER1 fails, in this case, the network Node a1 may determine, according to the content in the constrained path information, that the specified network Node (i.e., the network Node MER2) included in the constrained path information supports MPLS SR but does not support SRv6, at this moment, the network Node a1 encapsulates MPLS label information including the Node SID and Adj SID of the network Node MER2 for the traffic packet, and forwards the encapsulated packet to the next-hop network Node (i.e., the network Node a 2).

Here, a specific message format of the service message may be as shown in fig. 2B. In fig. 2B, the source IPv6 address of the service packet (i.e., the IPv6 address of the network node a1) is denoted by a1, the destination IPv6 address of the service packet (i.e., the IPv6 address of the network node MER1) is denoted by MER1, and the payload content of the service packet is IP data.

After receiving the encapsulated packet, network Node a2 finds that the encapsulated packet carries MPLS label information that is not its Node SID and Adj SID, and at this time, network Node a2 forwards the encapsulated packet to network Node MER2 based on the MPLS forwarding table.

After receiving the encapsulated packet (a specific packet format may be as shown in fig. 2B), the network Node MER2 finds that the encapsulated packet carries MPLS label information including its Node SID and Adj SID, at this time, the network Node MER2 pops up the Node SID and the Adj SID carried in the encapsulated packet to obtain the service packet, then determines an outgoing interface of the service packet based on the Adj SID, and forwards the service packet to the network Node MER1 through the determined outgoing interface. Here, the message format of the traffic message arriving at the network node MER1 side may be as shown in fig. 2B.

Example two

As shown in fig. 3A, assume that network node MER1 (shown in fig. 3A as MER1), network node a1 (shown in fig. 3A as a1), network node a2 (shown in fig. 3A as a2), and network node MER2 (shown in fig. 3A as MER2) each support both MPLS SRs and SRv 6; assume that network node A3 (shown as A3 in fig. 3A) supports MPLS SR but not SRv 6.

Assume that the primary path is network node a 1- > network node MER 1. And, assuming that network Node a1 is the source Node, assuming that network Node a1 determines that the TI-LFA FRR path corresponding to the main path is network Node a 1- > network Node A3- > network Node MER 2- > network Node MER1, and the Node SID and Adj SID of network Node a 6335 and the End SID and end.x SID of network Node MER1 are included in the constraint path information, according to the End SID and end.x SID of network Node a2, the End SID (e.g., Node1 SID) and Adj SID (e.g., Adj1 SID) of network Node A3, the End SID and end.x SID of network Node MER2 (i.e., End2.x SID) of network Node A3 are included in the constraint path information.

Assuming that, at a certain time, the network Node a1 receives the service packet and discovers that the primary path has a failure, for example, a link between the network Node a1 and the network Node MER1 has a failure, in this case, the network Node a1 may determine, according to the content in the constrained path information, that a first specified network Node (i.e., the network Node A3) included in the constrained path information supports MPLS SR but does not support SRv6, and a second specified network Node (i.e., the network Node MER2) supports both MPLS SR and SRv6, at this time, the network Node a1 encapsulates MPLS label information including Node 1SID and Adj 1SID, an IPv6 header and an SRH header for the service packet, and forwards the encapsulated packet to a next-hop network Node (i.e., the network Node A3).

Here, a specific message format of the service message may be as shown in fig. 3B. In fig. 3B, the source IPv6 address of the service packet (i.e., the IPv6 address of the network node a1) is denoted by a1, the destination IPv6 address of the service packet (i.e., the IPv6 address of the network node MER1) is denoted by MER1, and the payload content of the service packet is IP data.

In addition, the source IPv6 address in the IPv6 header is the IPv6 address of the network node a1, and the destination IPv6 address is the end.x SID (i.e., end2.x) of the network node MER 2. The Segment List information in the SRH header is Segment List [0] ═ end.x SID (i.e., end2.x) of network node MER2, and the SL value in the SRH header is 0.

After receiving the encapsulated packet (a specific packet format may be as shown in fig. 3B), the network Node A3 finds that the encapsulated packet carries MPLS label information including its Node 1SID and Adj 1SID, at this time, the network Node A3 pops up the Node 1SID and the Adj 1SID carried in the encapsulated packet, then determines an outgoing interface of the popped up packet based on the Adj 1SID, and forwards the popped up packet to the network Node MER2 through the determined outgoing interface.

After receiving the popped message (a specific message format may be as shown in fig. 3B), the network node MER2 finds that the destination IPv6 address in the IPv6 header is its end.x SID and the SL value in the SRH header is 0, at this time, the network node MER2 decapsulates the popped message SRv6 to obtain the service message, determines the outgoing interface of the service message based on the end.x SID, and forwards the service message to the network node MER1 through the determined outgoing interface. Here, the message format of the traffic message arriving at the network node MER1 side may be as shown in fig. 3B.

EXAMPLE III

As shown in fig. 4A, assume that network node MER1 (shown as MER1 in fig. 4A), network node a1 (shown as a1 in fig. 4A), network node a2 (shown as a2 in fig. 4A), and network node A3 (shown as A3 in fig. 4A) both support MPLS SR and SRv 6; assume that network node MER2 (shown in fig. 4A as MER2) supports MPLS SR but not SRv 6.

Assume that the primary path is network node a 1- > network node MER 1. And, assuming that network Node a1 is the source Node, assuming that network Node a1 determines that the TI-LFA FRR path corresponding to the primary path is network Node a 1- > network Node A3- > network Node MER 2- > network Node MER1, and the Node SID and Adj SID of network Node MER2 according to the End SID and end.x SID of network Node a2, the End SID and end.x SID of network Node A3 (e.g., End1.x), the Node SID and Adj SID of network Node MER2 (e.g., Adj2 SID), and the End SID and end.x SID of network Node MER1, and the end.x SID (i.e., End1.x) of network Node A3 is included in the corresponding constrained path information.

Assuming that, at a certain time, the network Node a1 receives the traffic packet and discovers that the primary path has a failure, for example, a link between the network Node a1 and the network Node MER1 has a failure, in this case, the network Node a1 may determine, according to the content in the constrained path information, that a first designated network Node (i.e., the network Node A3) included in the constrained path information supports both MPLS SR and SRv6, and a second designated network Node (i.e., the network Node MER2) supports MPLS SR but does not support SRv6, at this time, the network Node a1 encapsulates, for the traffic packet, an IPv6 header, an SRH header, and MPLS label information including Node2 SID and Adj2 SID, and forwards the encapsulated packet to a next-hop network Node (i.e., the network Node A3).

Here, a specific message format of the service message may be as shown in fig. 4B. In fig. 4B, the source IPv6 address of the service packet (i.e., the IPv6 address of the network node a1) is denoted by a1, the destination IPv6 address of the service packet (i.e., the IPv6 address of the network node MER1) is denoted by MER1, and the payload content of the service packet is IP data.

In addition, the source IPv6 address in the IPv6 header is the IPv6 address of the network node a1, and the destination IPv6 address is the end.x SID (i.e., end1.x) of the network node A3. The Segment List information in the SRH header is Segment List [0] ═ end.x SID (i.e., end1.x) of network node a3, and the SL value in the SRH header is 0.

After receiving the encapsulated packet (a specific packet format may be as shown in fig. 4B), the network node A3 finds that the destination IPv6 address in the IPv6 header in the encapsulated packet is its end.x SID, and the SL value in the SRH header is 0, at this time, the network node A3 decapsulates the encapsulated packet SRv6, determines an egress interface of the decapsulated packet based on the end.x SID, and forwards the decapsulated packet to the network node MER2 through the determined egress interface.

After receiving the decapsulated packet (a specific packet format may be as shown in fig. 4B), the network Node MER2 finds that the decapsulated packet carries MPLS label information including its Node2 SID and Adj2 SID, at this time, the network Node MER2 pops up the Node2 SID and the Adj2 SID carried in the decapsulated packet, obtains the service packet, determines an egress interface of the service packet based on the Adj 1SID, and forwards the service packet to the network Node MER1 through the determined egress interface. Here, the message format of the traffic message arriving at the network node MER1 side may be as shown in fig. 4B.

As can be seen from the above technical solutions, in the embodiment of the present application, in the case that an individual network Node in an SRv6 network supports MPLS SR but does not support SRv6, for a source Node on any main path, a TI-LFA FRR path corresponding to the path may be determined based on an End SID and an end.x SID of a network Node in a SRv6 network that supports MPLS SR but does not support SRv6, and a Node SID and/or an Adj SID of a network Node that supports MPLS SR but does not support SRv6, so that in the case that the main path fails, the source Node may timely forward a relevant service packet using constrained path information corresponding to the TI-LFA FRR path corresponding to the path, and a packet loss problem may not occur, thereby improving network experience.

Based on the same inventive concept, the present application further provides a packet forwarding device, where the device is applied to a source node on any main path in SRv6 network, and a schematic structural diagram of the device is shown in fig. 5, and specifically includes:

a determining module 51, configured to determine, according to the acquired segment identification information and link segment identification information of other network nodes in the SRv6 network except the source node, a TI-LFA FRR path corresponding to the main path and constraint path information corresponding to the TI-LFA FRR path, where when any other network node supports both MPLS SR and SRv6, the segment identification information of the other network node is an End SID of the other network node, and the link segment identification information of the other network node is an end.x SID of the other network node; when any other network Node supports the MPLS SR but does not support SRv6, the segment identification information of the other network Node is the Node SID of the other network Node, the link segment identification information of the other network Node is the Adj SID of the other network Node, the constraint path information includes the segment identification information and/or the link segment identification information of at least one designated network Node on the TI-LFA FRR path, and the total number of all designated network nodes is not greater than 3, and all designated network nodes do not include the source Node and the destination Node on the main path;

the first encapsulating and forwarding module 52 is configured to, when receiving a service packet and monitoring that the main path fails, encapsulate, according to the constrained path information and a preset encapsulating rule, the service packet if at least one piece of segment identification information and/or link segment identification information of a designated network node that supports MPLS SR but does not support SRv6 exists in the constrained path information, and forward the encapsulated service packet to a next-hop network node, where the next-hop network node is determined by the source node based on a backup forwarding table corresponding to the TI-LFA FRR path.

Preferably, the first encapsulation forwarding module is specifically configured to:

when the total number of all the designated nodes is 1, and it is determined according to the constraint path information that the designated network Node included in the constraint path information supports the MPLS SR but does not support SRv6, encapsulating first MPLS label information for the service packet to obtain an encapsulated service packet, where the first MPLS label information includes a Node SID and/or an Adj SID of the designated network Node included in the constraint path information.

when the total number of all the designated nodes is 2, for a first designated network Node and a second designated network Node in the constrained path information, if it is determined that the first designated network Node supports both MPLS SR and SRv6 and the second designated network Node supports MPLS SR but not MPLS SR SRv6 according to the constrained path information, encapsulating a first IPv6 header, a first SRH header, and second MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address in the first IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or end.x of the first designated network Node included in the constrained path information, a segment list information in the first IPv header includes the End SID and/or end.x of the first designated network Node, and the second SID information includes the Node SID and/or end.x of the second designated network Node included in the constrained path information /or Adj SID, the second MPLS label information being located after the first SRH header;

if it is determined from the constrained path information that the first designated network node supports MPLS SR but not SRv6 and the second designated network node supports both MPLS SR and SRv6, then the third MPLS label information, the second IPv6 header and the second SRH header are encapsulated for the service packet to obtain an encapsulated service packet, wherein the third MPLS label information comprises the Node SID and/or Adj SID of the first designated network Node included in the constraint path information, the source IPv6 address in the second IPv6 header is the IPv6 address of the source node, the destination IPv6 address is the End SID and/or the end.X SID of the two specified network nodes included in the constrained path information, the segment list information in the second SRH header includes the End SID and/or end.x SID of the second designated network node, and the third MPLS label information is located in front of the second SRH header;

if it is determined that both the first designated network node and the second designated network node support MPLS SR but do not support SRv6 according to the constrained path information, encapsulating fourth MPLS label information for the service packet, where the fourth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first designated network Node and the Node SID and/or Adj SID of the second designated network Node are included in the constraint path information.

when the total number of all the designated nodes is 3, for a first designated network node, a second designated network node and a third designated network node in the constrained path information, if it is determined that the first designated network node supports both MPLS SR and SRv6, the second designated network node supports MPLS SR but not SRv6, and the third designated network node supports both MPLS SR and SRv6 according to the constrained path information, encapsulating a third IPv6 header, a third SRH header, fifth label information, a fourth IPv6 header and a fourth SRH header for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the third IPv6 header is an MPLS 6 address of the source node, a destination IPv6 address is an End and/or end.x SID of the first designated network node included in the constrained path information, and a segment list information in the third SRH header includes an End and/or end.x SID of the first designated network node in the constrained path information, the fifth MPLS label information includes the Node SID and/or Adj SID of the second designated network Node included in the constrained path information, the source IPv6 address of the fourth IPv6 header is the IPv6 address of the source Node, the destination IPv6 address is the End SID and/or end.x SID of the third designated network Node included in the constrained path information, the segment list information in the fourth SRH header includes the End SID and/or end.x SID of the third designated network Node, and the fifth MPLS label information is located before the fourth IPv6 header and behind the third SRH header;

if it is determined that the first designated network node and the second designated network node both support MPLS SR and SRv6, and the third designated network node supports MPLS SR but not SRv6, then encapsulating a fifth IPv6 header, a fifth SRH header, and sixth MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the fifth IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network node included in the constrained path information, and the fifth SRH header sequentially includes: the End SID and/or end.x SID of the second designated network Node and the End SID and/or end.x SID of the first designated network Node, where the sixth MPLS label information includes the Node SID and/or Adj SID of the third designated network Node included in the constrained path information, and the sixth MPLS label information is located after the fifth SRH header;

if it is determined according to the constrained path information that the first designated network node supports both MPLS SR and SRv6, and the second designated network node and the third designated network node both support MPLS SR but not SRv6, encapsulating a sixth IPv6 header, a sixth SRH header, and seventh MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the sixth IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network node included in the constrained path information, a segment list information in the sixth SRH header includes the End SID and/or the end.x SID of the first designated network node, and the seventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the second designated network Node and the Node SID and/or Adj SID of the third designated network Node included in the constraint path information are included, where the seventh MPLS label information is located behind the sixth SRH header;

if it is determined that the first designated network Node supports MPLS SR but does not support SRv6, the second designated network Node and the third designated network Node both support MPLS SR and SRv6 according to the constraint path information, encapsulating an eighth MPLS label information, a seventh IPv6 header and a seventh SRH header for the service packet to obtain an encapsulated service packet, where the eighth MPLS label information includes a Node SID and/or Adj SID of the first designated network Node included in the constraint path information, a source IPv6 address of the seventh IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or an end.x SID of the second designated network Node included in the constraint path information, and the seventh SRH header sequentially includes: the End SID and/or end.x SID of the third designated network node and the End SID and/or end.x SID of the second designated network node, included in the constrained path information, are located before the seventh IPv6 header;

if it is determined that the first designated network Node supports MPLS SR but not SRv6, the second designated network Node supports MPLS SR but not SRv6, and the third designated network Node supports MPLS SR but not SRv6 according to the constrained path information, encapsulating ninth MPLS label information, an eighth IPv6 header, an eighth SRH header, and tenth MPLS label information for the service packet to obtain an encapsulated service packet, where the ninth MPLS label information includes the Node SID and/or Adj SID of the first designated network Node included in the constrained path information, a source IPv6 address of the eighth IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is the End SID and/or end.x SID of the second designated network Node included in the constrained path information, and segment list information in the eighth SRH header includes the End SID and/or end.x SID of the second designated network Node, the tenth MPLS label information includes the Node SID and/or Adj SID of the third designated network Node included in the constrained path information, and the ninth MPLS label information is located before the eighth IPv6 header, and the tenth MPLS label information is located before the eighth SRH header;

if it is determined according to the constrained path information that both the first designated network node and the second designated network node support MPLS SR but not SRv6, and the third designated network node supports MPLS SR and also supports SRv6, then encapsulating eleventh MPLS label information, a ninth IPv6 header, and a ninth SRH header for the service packet to obtain an encapsulated service packet, where the eleventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the first designated network Node and the Node SID and/or Adj SID of the second designated network Node included in the constrained path information, the source IPv6 address of the ninth IPv6 header is the IPv6 address of the source Node, the destination IPv6 address is the End SID and/or end.x SID of the third designated network Node included in the constrained path information, the segment list information in the ninth SRH header includes the End SID and/or end.x SID of the third designated network Node, and the eleventh MPLS label information is located before the ninth IPv6 header;

if it is determined according to the constrained path information that the first designated network node, the second designated network node, and the third designated network node all support MPLS SR but do not support SRv6, encapsulating twelfth MPLS label information for the service packet to obtain an encapsulated service packet, where the twelfth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first designated network Node included in the constraint path information, the Node SID and/or Adj SID of the second designated network Node included in the constraint path information, and the Node SID and/or Adj SID of the third designated network Node included in the constraint path information.

Preferably, the apparatus further comprises:

a second encapsulating and forwarding module (not shown in fig. 5), configured to, when receiving the service packet and monitoring that the main path fails, encapsulate, if segment identification information and/or link segment identification information of a specified network node that supports MPLS SR but does not support SRv6 does not exist in the constrained path information, a tenth IPv6 header and a tenth SRH header for the service packet, so as to obtain an encapsulated service packet;

the source IPv6 address of the tenth IPv6 header is the IPv6 address of the source node, the destination IPv6 address is the End SID and/or end.x SID of the first designated network node included in the constrained path information, the tenth SRH header includes the End SID and/or end.x SID of all designated network nodes included in the constrained path information, and the End SID and/or end.x SID of all designated network nodes are arranged in the order from far to near of all designated network nodes on the TI-LFA FRR path.

It can be seen from the foregoing technical solutions that, in the embodiment of the present application, in the case that an individual network Node supports an MPLS SR but does not support SRv6 in an SRv6 network, for a source Node on any main path, a TI-LFA FRR path corresponding to the path may be determined based on an End SID and an end.x SID of a network Node that supports both the MPLS SR and SRv6 in a SRv6 network, and a Node SID and/or Adj SID of a network Node that supports the MPLS SR but does not support SRv6 in the SRv6 network, so that in the case that the main path fails, the source Node may timely forward a relevant service packet using constrained path information corresponding to the TI-LFA FRR path corresponding to the path, and a packet loss problem may not occur, thereby improving network experience.

An electronic device is further provided in an embodiment of the present application, as shown in fig. 6, including a processor 61 and a machine-readable storage medium 62, where the machine-readable storage medium 62 stores machine-executable instructions that can be executed by the processor 61, and the processor 61 is caused by the machine-executable instructions to: and implementing the message forwarding method.

The machine-readable storage medium may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Alternatively, the machine-readable storage medium may be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In another embodiment provided by the present application, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the message forwarding method.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A message forwarding method is applied to a source node on any main path in SRv6 network, and the method comprises the following steps:

determining a TI-LFA FRR path corresponding to the main path and constraint path information corresponding to the TI-LFA FRR path according to the acquired segment identification information and link segment identification information of other network nodes except the source node in the SRv6 network, wherein when any other network node supports both MPLS SR and SRv6, the segment identification information of the other network node is the End SID of the other network node, and the link segment identification information of the other network node is the end.X SID of the other network node; when any other network Node supports the MPLS SR but does not support SRv6, the segment identifier information of the other network Node is the Node SID of the other network Node, the link segment identifier information of the other network Node is the Adj SID of the other network Node, the constraint path information includes the segment identifier information and/or the link segment identifier information of at least one specified network Node on the TI-LFA FRR path, and the total number of all specified network nodes is not greater than 3, and all specified network nodes do not include the source Node and the destination Node on the main path;

when a service message is received and a fault of the main path is monitored, if at least one segment identification information and/or link segment identification information of a designated network node which supports MPLS SR but does not support SRv6 exists in the constrained path information, encapsulating the service message according to the constrained path information and a preset encapsulation rule, and forwarding the encapsulated service message to a next-hop network node, wherein the next-hop network node is determined by the source node based on a backup forwarding table corresponding to the TI-LFA FRR path.

2. The method according to claim 1, wherein when the total number of all designated nodes is 1, encapsulating the service packet according to the constrained path information and a preset encapsulation rule, specifically comprising:

when it is determined that the designated network Node included in the constrained path information supports MPLS SR but does not support SRv6 according to the constrained path information, encapsulating first MPLS label information for the service packet to obtain an encapsulated service packet, where the first MPLS label information includes a Node SID and/or an Adj SID of the designated network Node included in the constrained path information.

3. The method according to claim 1, wherein when the total number of all designated nodes is 2, encapsulating the service packet according to the constrained path information and a preset encapsulation rule, specifically comprising:

aiming at a first designated network Node and a second designated network Node in the constraint path information, if it is determined that the first designated network Node supports both MPLS SR and SRv6 and the second designated network Node supports MPLS SR but not SRv6 according to the constraint path information, encapsulating a first IPv6 header, a first SRH header and second MPLS label information for the service packet to obtain an encapsulated service packet, wherein a source IPv6 address in the first IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network Node included in the constraint path information, a segment list information in the first IPv6 header includes the End SID and/or the end.x SID of the first designated network Node, and the second label information includes a Node SID and/or an MPLS Adj of the second designated network Node included in the constraint path information, the second MPLS label information is located after the first SRH header;

if it is determined from the constrained path information that the first designated network node supports MPLS SR but not SRv6 and the second designated network node supports both MPLS SR and SRv6, then the third MPLS label information, the second IPv6 header, and the second SRH header are encapsulated for the service packet, so as to obtain an encapsulated service packet, wherein the third MPLS label information comprises the Node SID and/or Adj SID of the first designated network Node included in the constraint path information, the source IPv6 address in the second IPv6 header is the IPv6 address of the source node, the destination IPv6 address is the End SID and/or the end.X SID of the two specified network nodes included in the constrained path information, the segment list information in the second SRH header includes the End SID and/or end.x SID of the second designated network node, and the third MPLS label information is located in front of the second SRH header;

4. The method according to claim 1, wherein when the total number of all designated nodes is 3, encapsulating the service packet according to the constrained path information and a preset encapsulation rule, specifically comprising:

for a first designated network node, a second designated network node and a third designated network node in the constrained path information, if it is determined that the first designated network node supports both MPLS SR and SRv6, the second designated network node supports MPLS SR but does not support SRv6, and the third designated network node supports both MPLS SR and SRv6 according to the constrained path information, encapsulating a third IPv6 header, a third SRH header, fifth MPLS label information, a fourth IPv6 header and a fourth SRH header in the service packet to obtain an encapsulated service packet, where a source IPv6 address of the third IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or end.x SID of the first designated network node included in the constrained path information, and segment list information in the third SRH header includes an End SID and/or end.x SID of the first designated network node, the fifth MPLS label information includes the Node SID and/or Adj SID of the second designated network Node included in the constrained path information, the source IPv6 address of the fourth IPv6 header is the IPv6 address of the source Node, the destination IPv6 address is the End SID and/or end.x SID of the third designated network Node included in the constrained path information, the segment list information in the fourth SRH header includes the End SID and/or end.x SID of the third designated network Node, and the fifth MPLS label information is located before the fourth IPv6 header and behind the third SRH header;

if it is determined that the first designated network node and the second designated network node both support MPLS SR and SRv6, and the third designated network node supports MPLS SR but not SRv6, then encapsulating a fifth IPv6 header, a fifth SRH header, and sixth MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the fifth IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network node included in the constrained path information, and the fifth SRH header sequentially includes: the End SID and/or end.x SID of the second designated network Node and the End SID and/or end.x SID of the first designated network Node, where the sixth MPLS label information includes the Node SID and/or Adj SID of the third designated network Node included in the constrained path information, and the sixth MPLS label information is located behind the fifth SRH header;

if it is determined according to the constrained path information that the first designated network node supports both MPLS SR and SRv6, and the second designated network node and the third designated network node both support MPLS SR but not SRv6, encapsulating a sixth IPv6 header, a sixth SRH header, and seventh MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address of the sixth IPv6 header is an IPv6 address of the source node, a destination IPv6 address is an End SID and/or an end.x SID of the first designated network node included in the constrained path information, a segment list information in the sixth SRH header includes the End SID and/or the end.x SID of the first designated network node, and the seventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the second designated network Node and the Node SID and/or Adj SID of the third designated network Node included in the constraint path information, where the seventh MPLS label information is located behind the sixth SRH header;

if it is determined that the first designated network Node supports MPLS SR but does not support SRv6, the second designated network Node and the third designated network Node both support MPLS SR and SRv6 according to the constraint path information, encapsulating an eighth MPLS label information, a seventh IPv6 header and a seventh SRH header for the service packet to obtain an encapsulated service packet, where the eighth MPLS label information includes a Node SID and/or Adj SID of the first designated network Node included in the constraint path information, a source IPv6 address of the seventh IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or an end.x SID of the second designated network Node included in the constraint path information, and the seventh SRH header sequentially includes: the End SID and/or end.x SID of the third designated network node and the End SID and/or end.x SID of the second designated network node included in the constrained path information are included, and the eighth MPLS label information is located before the seventh IPv6 header;

5. The method of claim 1, further comprising:

when the service message is received and the main path is monitored to have a fault, if the segment identification information and/or the link segment identification information of the designated network node which supports the MPLS SR but does not support SRv6 does not exist in the constraint path information, a tenth IPv6 head and a tenth SRH head are packaged for the service message to obtain a packaged service message;

the source IPv6 address of the tenth IPv6 header is the IPv6 address of the source node, the destination IPv6 address is the End SID and/or end.x SID of the first designated network node included in the constrained path information, the tenth SRH header includes the End SIDs and/or end.x SIDs of all designated network nodes included in the constrained path information, and the End SIDs and/or end.x SIDs of all designated network nodes are arranged in the order from far to near of all designated network nodes on the TI-LFA FRR path.

6. A message forwarding apparatus, applied to a source node on any primary path in SRv6 network, the apparatus comprising:

a determining module, configured to determine, according to the acquired segment identification information and link segment identification information of other network nodes in the SRv6 network except the source node, a TI-LFA FRR path corresponding to the main path and constraint path information corresponding to the TI-LFA FRR path, where when any other network node supports both MPLS SR and SRv6, the segment identification information of the other network node is an End SID of the other network node, and the link segment identification information of the other network node is an end.x SID of the other network node; when any other network Node supports the MPLS SR but does not support SRv6, the segment identifier information of the other network Node is the Node SID of the other network Node, the link segment identifier information of the other network Node is the Adj SID of the other network Node, the constraint path information includes the segment identifier information and/or the link segment identifier information of at least one specified network Node on the TI-LFA FRR path, and the total number of all specified network nodes is not greater than 3, and all specified network nodes do not include the source Node and the destination Node on the main path;

the first encapsulation forwarding module is configured to, when a service packet is received and a failure of the main path is monitored, encapsulate the service packet according to the constraint path information and a preset encapsulation rule if segment identification information and/or link segment identification information of at least one specified network node that supports MPLS SR but does not support SRv6 exists in the constraint path information, and forward the encapsulated service packet to a next-hop network node, where the next-hop network node is determined by the source node based on a backup forwarding table corresponding to the TI-LFA FRR path.

7. The apparatus of claim 6, wherein the first encapsulating forwarding module is specifically configured to:

8. The apparatus according to claim 6, wherein the first encapsulating forwarding module is specifically configured to:

when the total number of all the designated nodes is 2, for a first designated network Node and a second designated network Node in the constrained path information, if it is determined that the first designated network Node supports both MPLS SR and SRv6 and the second designated network Node supports MPLS SR but not MPLS SR SRv6 according to the constrained path information, encapsulating a first IPv6 header, a first SRH header, and second MPLS label information for the service packet to obtain an encapsulated service packet, where a source IPv6 address in the first IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or end.x of the first designated network Node included in the constrained path information, a segment list information in the first SRH header includes the End SID and/or end.x of the first designated network Node, and the second SID information includes the Node SID and/or end.x of the second designated network Node included in the constrained path information An Adj SID, the second MPLS label information being located behind the first SRH header;

9. The apparatus of claim 6, wherein the first encapsulating forwarding module is specifically configured to:

if it is determined that the first designated network node, the second designated network node and the third designated network node all support MPLS SR but do not support SRv6 according to the constrained path information, encapsulating twelfth MPLS label information for the service packet to obtain an encapsulated service packet, where the twelfth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first designated network Node included in the constraint path information, the Node SID and/or Adj SID of the second designated network Node included in the constraint path information, and the Node SID and/or Adj SID of the third designated network Node included in the constraint path information.

10. The apparatus of claim 6, further comprising:

a second encapsulating and forwarding module, configured to, when the service packet is received and a failure of the main path is monitored, encapsulate a tenth IPv6 header and a tenth SRH header for the service packet if segment identification information and/or link segment identification information of a specified network node that supports MPLS SR but does not support SRv6 does not exist in the constrained path information, so as to obtain an encapsulated service packet;