CN115037675B

CN115037675B - Message forwarding method and device

Info

Publication number: CN115037675B
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: 2024-09-06
Anticipated expiration: 2042-05-31
Also published as: CN115037675A

Abstract

The application provides a message forwarding method and device. The method is applied to a source node on any main path in SRv networks, and 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 SRv network; when a service message is received and the main path is monitored to be faulty, if at least one segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv is present 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 application can solve the problem of packet loss when the main path fails, and improves the 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 message.

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 individual segments, assigns segment identifiers (SEGMENT IDENTIFIER, 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 segment identifiers in the data packet in sequence.

Segment routing and internet protocol version six (Segment Routing Internet Protocol version, SRv) refers to combining SR technology with internet protocol version six (internet protocol version, IPv 6) protocols, defining an instantiated SRv SID according to the format of an IPv6 address, implementing SR functionality based on the forwarding plane of IPv 6.

In SRv network, when a source node on any main path needs to determine a TI-LFA FRR (Topology-INDEPENDENT LOOP-FREE ALTERNATE FAST Reroute) path corresponding to the path, an END SID (i.e., a segment identifier of a network node supporting both multiprotocol label switching (Multiprotocol Label Switching, MPLS) segment routing (Segment Routing with, MPLS SR) and SRv 6) and an END three-layer cross-connect segment identifier (Endpoint WITH LAYER-3cross-connect, end.x SID, i.e., a link segment identifier corresponding to a network node supporting SRv 6) of each network node in the entire SRv network need to be acquired.

However, in the SRv network, when an individual network node supports MPLS SR but does not support SRv, the source node cannot determine the TI-LFA FRR path corresponding to the path because the corresponding END SID and end.x SID cannot be provided, so when the source node forwards the 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 redetermine a new forwarding path because there is no corresponding backup path, and then forwards the service packet using the new forwarding path, which causes a problem of packet loss for a long time, and further results 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 device.

According to a first aspect of an embodiment of the present application, there is provided a method for forwarding a message, where the method is applied to a source node on any primary path in a SRv network, the method includes:

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 SRv network, wherein when any other network node supports both MPLS SR and SRv, 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 MPLS SR but does not support SRv < 6 >, 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, 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 the main path is monitored to be faulty, if at least one segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv is present 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 an embodiment of the present application, there is provided a packet forwarding apparatus, the apparatus being applied to a source node on any one of main paths in a SRv 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 except the source node in the SRv network, 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 SRv, 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 MPLS SR but does not support SRv < 6 >, 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, 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;

And the first encapsulation forwarding module is used for 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 if at least one segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv < 6 > exists in the constraint path information when the failure of the main path is detected, 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.

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

In the embodiment of the application, under the condition that individual network nodes support MPLS SR but do not support SRv in SRv network, for a source Node on any main path, the source Node can determine the TI-LFA FRR path corresponding to the path based on the End SID and end.X SID of the network nodes supporting both MPLS SR and SRv in SRv network and the Node SID and/or Adj SID of the network nodes supporting MPLS SR but do not support SRv6, so that the source Node can forward related service messages by using constraint path information corresponding to the TI-LFA FRR path corresponding to the path in time under the condition that the main path fails, and the problem of packet loss is avoided, 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 as claimed.

Drawings

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

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

Fig. 2A is one of networking schematic diagrams of SRv networks provided in an embodiment of the present application;

Fig. 2B is a schematic message format diagram of a service message provided by the embodiment of the present application on the network node A1, the network node MER2, and the network node MER1 sides in the networking shown in fig. 2A;

FIG. 3A is a second diagram illustrating a SRv network according to an embodiment of the present application;

Fig. 3B is a schematic message format diagram of a service message provided by the embodiment of the present application on the sides of network node A1, network node A3, network node MER2 and network node MER1 in the networking shown in fig. 3A;

Fig. 4A is a third networking schematic diagram of SRv networks according to an embodiment of the present application;

Fig. 4B is a schematic message format diagram of a service message provided by the embodiment of the present application on the sides of network node A1, network node A3, network node MER2 and network node MER1 in the networking shown in fig. 4A;

Fig. 5 is a schematic structural diagram of a message forwarding method according to 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 exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying 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 specification 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 or 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, these information should not be limited by 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 application. The word "if" or "if" as used herein may be interpreted as "at … …" or "when … …", depending on the context.

The embodiments of the present application will be described in detail.

The embodiment of the application provides a message forwarding method, which is applied to a source node on any main path in SRv networks, as shown in fig. 1, and can comprise the following steps:

S11, determining the 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 SRv network.

In this step, when any other network node supports both MPLS SR and SRv, 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 MPLS SR but does not support SRv, the segment identification information of the other network Node is the Node SID of the other network Node, and the link segment identification 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, and all designated network nodes do not include the source node and the destination node on the main path, 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.

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

And S12, when the service message is received and the main path is monitored to be faulty, if at least one piece of segment identification information and/or link segment identification information of the designated network node supporting MPLS SR but not SRv is/are present 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 the 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 the embodiment of the present 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 SRv network may be obtained by analyzing the Label switched path (Label SWITCHED PATH, LSP) packet sent by the neighboring network node.

And, for other network nodes supporting both MPLS SR and SRv, the source Node may obtain the End SID and end.x SID, and Node SID and Adj SID for the other network nodes; for other network nodes that support MPLS SR but do not support SRv6, the source Node may obtain the Node SID and Adj SID for the other network nodes.

The source Node then determines, when determining the TI-LFA FRR path corresponding to the primary path and constraint path information corresponding to the TI-LFA FRR path, using the End SID and end.x SID of the other network Node supporting both MPLS SR and SRv and the Node SID and Adj SID of the other network Node supporting MPLS SR but not SRv, a specific determination procedure similar to the existing determination procedure for determining the corresponding TI-LFA FRR path and related constraint path information using only the End SID and end.x SID of the network Node related to both MPLS SR and SRv is not described in detail herein.

Here, the TI-LFA FRR path has the smallest link overhead (Cost) value, and corresponding constraint path information (also referred to as REPAIR LIST) in which at least one segment identification information and/or link segment identification information of a designated network node capable of accurately guiding the service packet to the corresponding destination node is recorded.

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

And when determining that the designated network Node included in the constraint path information supports MPLS SR but does not support SRv, obtaining the encapsulated service packet for the first MPLS label information of the service packet Wen Fengzhuang, where the first MPLS label information includes the Node SID and/or Adj SID of the designated network Node included in the constraint path information.

It should be noted that, in the embodiment of the present application, for any specified network node included in the constraint path information, if the segment identification information and/or the link segment identification information of the specified network node in the constraint 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; if the segment identification information and/or link segment identification information of the specified network Node is the Node SID and/or Adj SID of the specified network Node, then it is determined that the specified network Node supports MPLS SR but not SRv s 6.

Here, the encapsulated service packet is used to instruct the designated network node to pop up the first MPLS label information and forward the first MPLS label information to the corresponding destination node when the encapsulated service packet is received.

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 constraint path information, if it is determined that the first designated network Node supports both MPLS SR and SRv s 6 and the second designated network Node supports MPLS SR but does not support SRv6 according to the constraint path information, obtaining an encapsulated service packet for a first IPv6 header of the service packet Wen Fengzhuang, a first routing extension header (Segment Routing Header, SRH) header, and second MPLS label information, 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 an end.x SID of the first designated network Node included in the constraint path information, a segment list information in the first SRH header includes an End SID and/or an end.x SID of the first designated network Node, and the second MPLS label information includes a Node SID and/or an Adj SID of the second designated network Node included in the constraint path information and is located behind the first SRH header; here, the first SRH header further includes information such as a remaining number of segments (SEGMENT LEFT, SL) value, where the SL value in the first SRH header=0, and the segment list information in the first SRH header may be specifically SEGMENT LIST [0] =end SID and/or end.x SID of the first specified network node;

If it is determined according to the constraint path information that the first specified network Node supports MPLS SR but does not support SRv6 and the second specified network Node supports both MPLS SR and SRv, obtaining an encapsulated service packet for a third MPLS label information, a second IPv6 header and a second SRH header of the service packet Wen Fengzhuang, where the third MPLS label information includes a Node SID and/or an Adj SID of the first specified 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 specified network nodes included in the constraint path information, and the segment list information in the second SRH header includes an End SID and/or an end.x SID of the second specified network Node, where the third MPLS label information is located in front of the second SRH header; here, the second SRH header further includes information such as a SL value, where the SL value in the second SRH header=0, and the segment list information in the second SRH header may be specifically SEGMENT LIST [0] =end SID and/or end.x SID of the second designated network node;

If it is determined according to the constraint path information that the first designated network node and the second designated network node both support MPLS SR but do not support SRv < 6 >, the fourth MPLS label information is a service packet Wen Fengzhuang, 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 the case that it is determined according to the constraint path information that the first designated network node supports both MPLS SR and SRv and the second designated network node supports MPLS SR but does not support SRv, the encapsulated packet may instruct the first designated network node to decapsulate SRv the encapsulated packet, forward the decapsulated packet (carrying the relevant MPLS label information) to the second designated network node further, pop up the relevant MPLS label information in the decapsulated packet by the second designated network node, and forward the same to the corresponding destination node.

In the case that the first designated network node supports MPLS SR but does not support SRv a 6 and the second designated network node supports both MPLS SR and SRv a, according to the constraint path information, the encapsulated packet may instruct the first designated network node to pop up relevant MPLS label information in the encapsulated packet, and then forward the packet to the second designated network node, where the second designated network node performs SRv decapsulation and then forwards the packet to the corresponding destination node.

In the case that it is determined according to the constraint path information that the first designated network node and the second designated network node both support MPLS SR but do not support SRv a 6, the encapsulated packet may instruct the first designated network node to pop up the first layer MPLS label information in the encapsulated packet, and then forward the first layer MPLS label information to the second designated network node, where the second designated network node pops up the second layer MPLS label information 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, the service message is packaged according to the constraint path information and a preset packaging rule, which specifically comprises the following steps:

For a first designated network Node, a second designated network Node and a third designated network Node in the constraint path information, if it is determined that the first designated network Node supports MPLS SR and SRv and the second designated network Node supports MPLS SR but does not support SRv6 according to the constraint path information, and the third designated network Node supports MPLS SR and SRv, the first designated network Node is a service packet Wen Fengzhuang third IPv6 header, a third SRH header, fifth MPLS label information, a fourth IPv6 header and a fourth SRH header, and a packaged service packet is obtained, 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 an end.x SID of the first designated network Node included in the constraint path information, segment list information in the third SRH header includes an End SID and/or end.x SID of the first designated network Node, fifth MPLS label information includes a second SID and a fourth SID address and/or a fourth SID address of the designated network Node included in the constraint path information, and the fourth IPv6 address is an End SID and/or a fourth SID of the end.x End list information of the third designated network Node included in the constraint path information; here, the third SRH header and the fourth SRH header each further include information such as a SL value, where the SL values in the third SRH header and the fourth SRH header=0, the segment list information in the third SRH header may be specifically SEGMENT LIST [0] =the End SID and/or end.x SID of the first specified network node, and the segment list information in the fourth SRH header may be specifically SEGMENT LIST [0] =the End SID and/or end.x SID of the third specified network node;

If it is determined according to the constraint path information that the first designated network node and the second designated network node support MPLS SR and SRv a 6 and the third designated network node supports MPLS SR but does not support SRv a, obtaining a packaged service packet according to fifth IPv6 header, fifth SRH header and sixth MPLS label information of the service packet Wen Fengzhuang, where a source IPv6 address of the fifth IPv6 header is an IPv6 address of the source node, and 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, where 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, sixth MPLS label information including the Node SID and/or Adj SID of the third designated network Node included in the constraint path information, the sixth MPLS label information being located after a fifth SRH header; here, the fifth SRH header further includes information such as a SL value, where SL value=1, and the segment list information in the fifth SRH header may specifically be: SEGMENT LIST [0] = End SID and/or end.x SID, segment List [1] = End SID and/or end.x SID of the first designated network node;

If it is determined according to the constraint path information that the first specified network node supports both MPLS SR and SRv and the second specified network node and the third specified network node both support MPLS SR but do not support SRv, obtaining an encapsulated service packet according to sixth IPv6 header, sixth SRH header and seventh MPLS label information of the service packet Wen Fengzhuang, 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 specified network node included in the constraint path information, and segment list information in the sixth SRH header includes an End SID and/or an end.x SID of the first specified network node, and the seventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the second appointed network Node and the Node SID and/or Adj SID of the third appointed network Node included in the constraint path information, and seventh MPLS label information is positioned behind a sixth SRH header; here, the sixth SRH header further includes information such as a SL value, where the SL value in the sixth SRH header=0, and the segment list information in the sixth SRH header may be specifically SEGMENT LIST [0] =end SID and/or end.x SID of the first specified network node;

If it is determined according to the constraint path information that the first specified network Node supports MPLS SR but does not support SRv6, the second specified network Node and the third specified network Node both support MPLS SR and support SRv, obtaining an encapsulated service packet for a service packet Wen Fengzhuang, a seventh IPv6 header and a seventh SRH header, where the eighth MPLS label information includes a Node SID and/or an Adj SID of the first specified 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, and a destination IPv6 address is an End SID and/or an end.x SID of the second specified 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 constraint path information, and eighth MPLS label information is located in front of a seventh IPv6 header; here, the seventh SRH header further includes information such as a SL value, and the SL value=1 in the seventh SRH header, and the segment list information in the seventh SRH header may specifically be: SEGMENT LIST [0] = End SID and/or end.x SID, segment List [1] = End SID and/or end.x SID of the second designated network node;

If it is determined according to the constraint path information that the first specified network Node supports MPLS SR but does not support SRv6, the second specified network Node supports MPLS SR and SRv, and the third specified network Node supports MPLS SR but does not support SRv6, obtaining a packaged service packet for service packet Wen Fengzhuang, an eighth IPv6 header, an eighth SRH header, and tenth MPLS label information, where the ninth MPLS label information includes a Node SID and/or an Adj SID of the first specified network Node included in the constraint path information, a source IPv6 address of the eighth 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 specified network Node included in the constraint path information, and the segment list information in the eighth SRH header includes an End SID and/or an end.x of the second specified network Node, and the tenth MPLS label information includes a Node SID and/or an end.x of the eighth specified network Node included in the constraint path information, and the eighth IPv6 header is located before the eighth SRH 34; here, the eighth SRH header further includes information such as a SL value, where the SL value in the eighth SRH header=0, and the segment list information in the eighth SRH header may be specifically SEGMENT LIST [0] =end SID and/or end.x SID of the second designated network node;

If it is determined according to the constraint path information that the first designated network node and the second designated network node both support MPLS SR but do not support SRv and the third designated network node supports MPLS SR and support SRv, obtaining an encapsulated service packet according to eleventh MPLS label information, ninth IPv6 header and ninth SRH header of the service packet Wen Fengzhuang, where the eleventh MPLS label information sequentially includes: the Node SID and/or AdjSID of the first specified network Node and the Node SID and/or AdjSID of the second specified network Node included in the constraint 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 specified network Node included in the constraint path information, the segment list information in the ninth SRH header includes the End SID and/or end.x SID of the third specified 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 a SL value, where the SL value in the ninth SRH header=0, and the segment list information in the ninth SRH header may be specifically SEGMENT LIST [0] =end SID and/or end.x SID of the third designated network node;

If it is determined according to the constraint path information that the first designated network node, the second designated network node and the third designated network node all support MPLS SR but not SRv, obtaining twelfth MPLS label information of the service packet Wen Fengzhuang, where the twelfth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first specified network Node included in the constraint path information, the Node SID and/or Adj SID of the second specified network Node included in the constraint path information, and the Node SID and/or Adj SID of the third specified network Node included in the constraint path information.

In this manner, for the source node, in the case that it is determined according to the constraint path information that the first designated network node supports both MPLS SR and SRv, the second designated network node supports MPLS SR but does not support SRv, and the third designated network node supports both MPLS SR and SRv, the encapsulated packet may instruct the first designated network node to perform one-time SRv decapsulation on the encapsulated packet, forward the decapsulated packet 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 one-time SRv decapsulation by the third designated network node, and forward the decapsulated packet to the corresponding destination node.

In the case that it is determined according to the constraint path information that the first designated network node and the second designated network node support both MPLS SR and SRv and that the third designated network node supports MPLS SR but does not support SRv, the encapsulated packet may instruct the first designated network node to modify the encapsulated service packet (modify the destination address in the corresponding IPv6 header and the value of SL in the corresponding SRH header) and then forward the modified packet to the second designated network node, decapsulate the modified packet by the second designated network node SRv, forward the decapsulated packet to the third designated network node further, pop up relevant MPLS label information in the decapsulated packet by the third designated network node, and forward the same to the corresponding destination node.

In the case that the first designated network node supports both MPLS SR and SRv and the second designated network node and the third designated network node both support MPLS SR but do not support SRv are determined according to the constraint path information, the encapsulated packet may instruct the first designated network node to decapsulate the encapsulated service packet SRv, forward the decapsulated packet to the second designated network node, pop up the first layer MPLS label information by the second designated network node, forward the first layer MPLS label information to the third designated network node, pop up the second layer MPLS label information by the third designated network node, and forward the second layer MPLS label information to the corresponding destination node.

In the case that it is determined according to the constraint path information that the first designated network node supports MPLS SR but does not support SRv, the second designated network node and the third designated network node both support MPLS SR and support SRv, the encapsulated packet may instruct the first designated network node to pop up relevant MPLS label information in the encapsulated service packet, and then forward the first designated network node to the second designated network node, modify the first designated network node (modify the destination address in the corresponding IPv6 header and the value of SL in the corresponding SRH header) by the second designated network node, forward the second designated network node to the third designated network node, and decapsulate the modified packet by the third designated network node by SRv and then forward the modified packet to the corresponding destination node.

In the case that it is determined according to the constraint path information that the first designated network node supports MPLS SR but does not support SRv a 6, the second designated network node supports MPLS SR and SRv a, and the third designated network node supports MPLS SR but does not support SRv a 6, the encapsulated packet may instruct the first designated network node to pop up relevant MPLS label information in the encapsulated service packet, forward the relevant MPLS label information to the second designated network node, perform SRv decapsulation on the relevant MPLS label information by the second designated network node, forward the relevant MPLS label information to the third designated network node, and pop up relevant MPLS label information in the encapsulated packet by the third designated network node, and forward the relevant MPLS label information to the corresponding destination node.

In the case that it is determined according to the constraint path information that the first designated network node and the second designated network node both support MPLS SR but do not support SRv and the third designated network node supports both MPLS SR and SRv, the encapsulated packet may instruct the first designated network node to pop up the first layer of MPLS label information in the encapsulated service packet, then forward the first layer of MPLS label information to the second designated network node, continue to pop up the second layer of MPLS label information by the second designated network node, forward the second layer of MPLS label information to the third designated network node, and forward the second layer of MPLS label information to the corresponding destination node after the third designated network node performs SRv decapsulation.

In the case that it is determined according to the constraint 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 SRv, the encapsulated packet may instruct the first designated network node to pop up the first layer MPLS label information in the encapsulated service packet, then forward the first layer MPLS label information to the second designated network node, continue to pop up the second layer MPLS label information by the second designated network node, forward the second layer MPLS label information to the third designated network node, and continue to pop up the third layer MPLS label information by the third designated network node, and forward the third layer MPLS label information to the corresponding destination node.

Further, in the embodiment of the present application, for the source node, when a service packet is received and it is monitored that the main path fails, if the constraint path information does not include segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv, the source node still processes the service packet according to the existing flow, that is, a tenth IPv6 header and a tenth SRH header of the service packet Wen Fengzhuang, so as to obtain a packaged service packet; the source IPv6 address of the tenth IPv6 header is an IPv6 address of the source node, the 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, the tenth SRH header includes End SIDs and/or end.x SIDs of all designated network nodes included in the constraint path information, and the End SIDs and/or end.x SIDs of all designated network nodes are arranged in sequence from far to near according to all designated network nodes on the TI-LFA FRR path.

The above message forwarding method is described in detail below with reference to specific embodiments.

Example 1

As shown in fig. 2A, it is assumed that network node MER1 (shown as MER1 in fig. 2A), network node A1 (shown as A1 in fig. 2A), and network node A2 (shown as A2 in fig. 2A) all support both MPLS SR and SRv6; assume that network node MER2 (shown as MER2 in fig. 2A) supports MPLS SR but does not support SRv.

Let it be assumed that the main path is network node A1- > network node MER1. And, assuming that the network Node A1 is a source Node, it is assumed that the network Node A1 determines that the TI-LFA FRR path corresponding to the main path is a network Node A1- > network Node A2- > network Node MER2 according to the End SID and end.x SID of the network Node A2, the Node SID and Adj SID of the network Node MER2, and the End SID and end.x SID of the network Node MER1, where the Node SID and Adj SID of the network Node MER2 are included in the corresponding constraint path information.

Assuming that at some point in time, network Node A1 receives the traffic packet and finds that the primary path fails, for example, a link between network Node A1 and network Node MER1 fails, in this case, network Node A1 may determine, according to the content in the constraint path information, that the designated network Node included in the constraint path information (i.e., network Node MER 2) supports MPLS SR but not SRv, at this point, network Node A1 encapsulates MPLS label information including Node SID and Adj SID of network Node MER2 for the traffic packet and forwards the encapsulated packet to the next hop network Node (i.e., network Node A2).

Here, the 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 MER 1) is denoted by MER1, and the payload content of the service packet is IP data.

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

After receiving the encapsulated message (the specific message format may be shown in fig. 2B), the network Node MER2 finds that the encapsulated message carries MPLS label information including its Node SID and Adj SID, at this time, the network Node MER2 pops up the Node SID and Adj SID carried in the encapsulated message to obtain the service message, and then determines an output interface of the service message based on the Adj SID, and forwards the service message to the network Node MER1 through the determined output interface. Here, the message format of the service 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 as MER1 in fig. 3A), network node A1 (shown as A1 in fig. 3A), network node A2 (shown as A2 in fig. 3A), and network node MER2 (shown as MER2 in fig. 3A) all support both MPLS SR and SRv6; assume that network node A3 (shown as A3 in fig. 3A) supports MPLS SR but does not support SRv6.

Let it be assumed that the main path is network node A1- > network node MER1. Further, assuming that the network Node A1 is a source Node, it is assumed that the network Node A1 determines that the TI-LFA FRR path corresponding to the main path is the network Node A1- > network Node A3- > network Node MER2- > network Node MER1 according to the End SID and end.x SID of the network Node A2, the Node SID (e.g., node1 SID) and Adj SID (e.g., adj1 SID) of the network Node MER2, the End SID and end.x SID (e.g., end2. X) of the network Node MER2, and the end.x SID (i.e., end2. X) of the network Node MER2 are included in the corresponding constraint path information.

Assuming that at some point in time, network Node A1 receives the traffic packet and finds that the primary path fails, for example, the link between network Node A1 and network Node MER1 fails, in this case, network Node A1 may determine, based on the content in the constraint path information, that the first designated network Node (i.e., network Node A3) included in the constraint path information supports MPLS SR but not SRv6, and the second designated network Node (i.e., network Node MER 2) supports both MPLS SR and SRv, at which point network Node A1 encapsulates MPLS label information including Node1 SID and Adj1 SID, IPv6 header and SRH header for the traffic packet and forwards the encapsulated packet to the next hop network Node (i.e., network Node A3).

Here, the 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 MER 1) is denoted by MER1, and the payload content of the service packet is IP data.

In addition, the source IPv6 address in the above 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 the network node MER2, and the SL value in the SRH header=0.

After receiving the encapsulated packet (the specific packet format may be 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 Adj 1SID carried in the encapsulated packet, and then determines an outgoing interface of the popped packet based on the Adj 1SID, and forwards the popped packet to the network Node MER2 through the determined outgoing interface.

After receiving the popped message (the specific message format may be 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=0, at this time, the network node MER2 decapsulates the popped message SRv to obtain the service message, determines an output interface of the service message based on the end.x SID, and forwards the service message to the network node MER1 through the determined output interface. Here, the message format of the service message reaching 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) all support both MPLS SR and SRv; assume that network node MER2 (shown as MER2 in fig. 4A) supports MPLS SR but does not support SRv.

Let it be assumed that the main path is network node A1- > network node MER1. Further, assuming that the network Node A1 is a source Node, it is assumed that the network Node A1 determines that the TI-LFA FRR path corresponding to the main path is the network Node A1- > network Node A3- > network Node MER2- > network Node MER1, and the Node SID and Adj SID of the network Node MER2 are included in the corresponding constraint path information according to the End SID and end.x SID of the network Node A2, the End SID and end.x SID (e.g., end1. X) of the network Node A3, the Node SID (e.g., node2 SID) and Adj SID (e.g., adj2 SID) of the network Node MER2, and the End SID and Adj SID of the network Node MER 2.

Assuming that at some point in time, network Node A1 receives the traffic packet and finds that the primary path fails, for example, the link between network Node A1 and network Node MER1 fails, in which case network Node A1 may determine, based on the contents of the constraint path information, that the first designated network Node included in the constraint path information (i.e., network Node A3) supports both MPLS SR and SRv6, and the second designated network Node (i.e., network Node MER 2) supports MPLS SR but not SRv6, at which point network Node A1 encapsulates the IPv6 header, SRH header, and MPLS label information including Node2 SID and Adj2 SID for the traffic packet and forwards the encapsulated packet to the next hop network Node (i.e., network Node A3).

Here, the 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 MER 1) is denoted by MER1, and the payload content of the service packet is IP data.

In addition, the source IPv6 address in the above 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 above SRH header is SEGMENT LIST [0] =end.x SID (i.e., end1. X) of the network node A3, and the SL value in the above SRH header=0.

After receiving the encapsulated packet (the specific packet format may be 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=0, at this time, the network node A3 decapsulates the encapsulated packet by SRv, determines the 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 message (the specific message format may be shown in fig. 4B), the network Node MER2 finds that the decapsulated message carries MPLS label information including its Node2 SID and Adj2 SID, and at this time, the network Node MER2 pops up the Node2 SID and Adj2 SID carried in the decapsulated message to obtain the service message, determines an outbound interface of the service message based on the Adj1 SID, and forwards the service message to the network Node MER1 through the determined outbound interface. Here, the message format of the service message reaching 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 supports MPLS SR but does not support SRv in SRv network, for a source Node on any main path, the source Node may determine the TI-LFA FRR path corresponding to the path based on the End SID and end.x SID of the network Node supporting both MPLS SR and SRv6 in SRv network and the Node SID and/or Adj SID of the network Node supporting MPLS SR but does not support SRv6, so that in the case that the main path fails, the source Node may forward the related service packet using constraint path information corresponding to the TI-LFA FRR path corresponding to the path in time, without occurrence of a packet loss problem, thereby improving network experience.

Based on the same inventive concept, the application also provides a message forwarding device, which is applied to a source node on any main path in SRv network, and the structure schematic diagram 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 except the source node in the SRv network, 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 SRv, 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 MPLS SR but does not support SRv < 6 >, 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, 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;

And the first encapsulation forwarding module 52 is configured to encapsulate the service packet according to the constraint 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, if at least one segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv's 6 exists in the constraint path information when the failure of the main path is detected.

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

and when the total number of all the designated nodes is 1, and the designated network nodes included in the constraint path information are determined to support MPLS SR but not SRv to support SRv according to the constraint path information, obtaining the packaged service message for the first MPLS label information of the service message Wen Fengzhuang, wherein the first MPLS label information includes the Node SID and/or the Adj SID of the designated network nodes 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 constraint path information, if it is determined that the first designated network Node supports both MPLS SR and SRv s 6 and the second designated network Node supports MPLS SR but does not support SRv according to the constraint path information, obtaining an encapsulated service packet for the first IPv6 header, a first SRH header, and second MPLS label information of the service packet Wen Fengzhuang, 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 an end.x SID of the first designated network Node included in the constraint path information, and the segment list information in the first SRH header includes an End SID and/or an end.x SID of the first designated network Node, and the second MPLS label information includes a Node SID and/or an Adj of the second designated network Node included in the constraint path information and is located behind the first MPLS label information;

If it is determined according to the constraint path information that the first specified network Node supports MPLS SR but does not support SRv6 and the second specified network Node supports both MPLS SR and SRv, obtaining an encapsulated service packet for the service packet Wen Fengzhuang, a third MPLS label information, a second IPv6 header and a second SRH header, where the third MPLS label information includes a Node SID and/or an Adj SID of the first specified 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 specified network nodes included in the constraint path information, and the segment list information in the second SRH header includes an End SID and/or an end.x SID of the second specified network Node, where the third MPLS label information is located in front of the second SRH header;

If it is determined according to the constraint path information that the first designated network node and the second designated network node both support MPLS SR but do not support SRv < 6 >, the fourth MPLS label information is the service packet Wen Fengzhuang, 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 constraint path information, if it is determined that the first designated network Node supports both MPLS SR and SRv and the second designated network Node supports MPLS SR but does not support SRv6 and the third designated network Node supports both MPLS SR and SRv according to the constraint path information, the service packet Wen Fengzhuang is a third IPv6 header, a third SRH header, a fifth MPLS label information, a fourth IPv6 header and a fourth SRH header, so as to obtain a packaged 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 SID of the first designated network Node included in the constraint path information, segment list information in the third SRH header includes an End SID and/or an End SID of the first designated network Node, a fifth IPv6 header includes a source SID and/or an End SID of the fourth designated network Node, and a destination IPv6 address of the third IPv6 header includes a constraint SID and/or an End SID of the fourth End SID in the constraint path information, and the End SID information includes a destination IPv6 address of the third IPv6 header includes the End SID and/or an End SID of the fourth End SID of the third designated network Node;

If it is determined according to the constraint path information that the first designated network node and the second designated network node support both MPLS SR and SRv6, and the third designated network node supports MPLS SR but does not support SRv6, obtaining encapsulated service packet for a fifth IPv6 header, a fifth SRH header, and sixth MPLS label information of the service packet Wen Fengzhuang, where a source IPv6 address of the fifth IPv6 header is an IPv6 address of the source node, and 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, 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, said sixth MPLS label information comprising the Node SID and/or Adj SID of the third designated network Node included in the constraint path information, said sixth MPLS label information being located after said fifth SRH header;

If it is determined according to the constraint path information that the first specified network node supports both MPLS SR and SRv and the second specified network node and the third specified network node both support MPLS SR but do not support SRv, obtaining an encapsulated service packet for the service packet Wen Fengzhuang, a sixth IPv6 header, a sixth SRH header, and seventh MPLS label information, 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 specified network node included in the constraint path information, and segment list information in the sixth SRH header includes an End SID and/or an end.x SID of the first specified network node, and the seventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the second appointed network Node and the Node SID and/or Adj SID of the third appointed network Node included in the constraint path information, wherein the seventh MPLS label information is positioned behind the sixth SRH header;

if it is determined according to the constraint path information that the first specified network Node supports MPLS SR but does not support SRv6, the second specified network Node and the third specified network Node both support MPLS SR and support SRv6, obtaining an encapsulated service packet for the eighth MPLS label information, a seventh IPv6 header and a seventh SRH header of the service packet Wen Fengzhuang, where the eighth MPLS label information includes a Node SID and/or an Adj SID of the first specified 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, and a destination IPv6 address is an End SID and/or an end.x SID of the second specified 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 appointed network node and the End SID and/or end.X SID of the second appointed network node included in the constraint path information, the eighth MPLS label information is positioned in front of the seventh IPv6 header;

If it is determined according to the constraint path information that the first specified network Node supports MPLS SR but does not support SRv, the second specified network Node supports MPLS SR and SRv, and the third specified network Node supports MPLS SR but does not support SRv, obtaining an encapsulated service packet for the service packet Wen Fengzhuang, a ninth MPLS label information, an eighth IPv6 header, an eighth SRH header, and a tenth MPLS label information, where the ninth MPLS label information includes a Node SID and/or an Adj SID of the first specified network Node included in the constraint path information, a source IPv6 address of the eighth IPv6 header is an IPv6 address of the source Node, a destination IPv6 address is an End SID and/or an End SID. X of the second specified network Node included in the constraint path information, a segment list information in the eighth SRH header includes an End SID and/or an End. X of the second specified network Node, and the tenth MPLS label information includes a Node SID and/or an Adj SID of the tenth MPLS label information in front of the constraint path information, and the eighth SID of the eighth specified network Node in front of the constraint path information;

If it is determined according to the constraint path information that the first designated network node and the second designated network node both support MPLS SR but do not support SRv and the third designated network node supports MPLS SR and support SRv, obtaining an encapsulated service packet according to eleventh MPLS label information, ninth IPv6 header and ninth SRH header of the service packet Wen Fengzhuang, where the eleventh MPLS label information sequentially includes: the Node SID and/or Adj SID of the first appointed network Node and the Node SID and/or Adj SID of the second appointed network Node are included in the constraint 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 appointed network Node included in the constraint path information, the segment list information in the ninth SRH header includes the End SID and/or end.x SID of the third appointed network Node, and the eleventh MPLS label information is located in front of the ninth IPv6 header;

If it is determined according to the constraint path information that the first designated network node, the second designated network node and the third designated network node all support MPLS SR but not SRv, obtaining a packaged service packet for the twelfth MPLS label information of the service packet Wen Fengzhuang, where the twelfth MPLS label information sequentially includes: the Node SID and/or Adj SID of the first specified network Node included in the constraint path information, the Node SID and/or Adj SID of the second specified network Node included in the constraint path information, and the Node SID and/or Adj SID of the third specified network Node included in the constraint path information.

Preferably, the apparatus further comprises:

A second encapsulation forwarding module (not shown in fig. 5), configured to, when the service packet is received and the main path is monitored to fail, obtain an encapsulated service packet for a tenth IPv6 header and a tenth SRH header of the service packet Wen Fengzhuang if no segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv is present in the constraint path information;

The source IPv6 address of the tenth IPv6 header is an IPv6 address of the source node, the 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, and the tenth SRH header includes End SIDs and/or end.x SIDs of all designated network nodes included in the constraint path information, where the End SIDs and/or end.x SIDs of all designated network nodes are arranged in sequence from far to near according to all designated network nodes on the TI-LFA FRR path.

From the above technical solutions, it can be seen that, in the embodiment of the present application, in the case that an individual network Node supports MPLS SR but does not support SRv in SRv network, for a source Node on any main path, the source Node may determine the TI-LFA FRR path corresponding to the path based on the End SID and end.x SID of the network Node supporting both MPLS SR and SRv6 in SRv network and the Node SID and/or Adj SID of the network Node supporting MPLS SR but not SRv6, so that in the case that the main path fails, the source Node may forward the relevant service packet using constraint path information corresponding to the TI-LFA FRR path corresponding to the path in time, so as to improve network experience.

An embodiment of the present application also provides an electronic device, as shown in fig. 6, including a processor 61 and a machine-readable storage medium 62, the machine-readable storage medium 62 storing machine-executable instructions executable by the processor 61, the processor 61 being caused by the machine-executable instructions to: the method for forwarding the message is realized.

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

The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but may also be a digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components.

In yet another embodiment of the present application, a computer readable storage medium is provided, in which a computer program is stored, the computer program implementing the steps of the above-mentioned message forwarding method when being executed by a processor.

The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.

Claims

1. A method for forwarding a message, wherein the method is applied to a source node on any one of a segment routing and internet protocol sixth edition SRv network, the method comprising:

Determining a topology-independent loop-free backup fast reroute 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 SRv network, wherein when any other network node supports both multiprotocol label switching segment routing MPLS SR and SRv, the segment identification information of the other network node is an End SID of the End point segment identification of the other network node, and the link segment identification information of the other network node is an End point three-layer cross connection segment identification end.XSID of the other network node; when any other network Node supports MPLS SR but does not support SRv < 6 >, the segment identification information of the other network Node is a Node segment identification Node SID of the other network Node, the link segment identification information of the other network Node is an Adj SID of an adjacent segment identification of the other network Node, 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, 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;

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

When determining that the designated network Node included in the constraint path information supports MPLS SR but does not support SRv, performing first multiprotocol label switching (MPLS) label information for the service packet Wen Fengzhuang according to the constraint path information, and obtaining 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.

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 constraint path information and a preset encapsulation rule, specifically includes:

For 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 SRv s 6 and the second designated network Node supports MPLS SR but does not support SRv6 according to the constraint path information, obtaining an encapsulated service packet for the first internet protocol version 6 IPv6 header of the service packet Wen Fengzhuang, a first routing extension header SRH header and second MPLS label information, 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 an end.x SID of the first designated network Node included in the constraint path information, and the segment list information in the first SRH header includes an End SID and/or an end.x SID of the first designated network Node, and the second MPLS label information includes a Node SID and/or an Adj SID of the second designated network Node included in the constraint path information and is located behind the first SRH header;

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

For a first designated network Node, a second designated network Node and a third designated network Node in the constraint path information, if it is determined that the first designated network Node supports MPLS SR and SRv and the second designated network Node supports MPLS SR but does not support SRv6 according to the constraint path information, and the third designated network Node supports MPLS SR and SRv, the first designated network Node is a third IPv6 header of the service packet Wen Fengzhuang, a third SRH header, fifth MPLS label information, a fourth IPv6 header and a fourth SRH header, so as 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 an end.x SID of the first designated network Node included in the constraint path information, a segment list information in the third SRH header includes an End SID and/or an end.x SID of the first designated network Node, a fifth IPv6 header includes a constraint SID and/or a fourth SID of the fourth designated network Node, and a fourth End identifier in the constraint path information includes a source IPv6 header or a fourth End SID of the fourth designated network Node, and a fourth End identifier in the constraint path information;

5. The method according to claim 1, wherein the method further comprises:

When the service message is received and the main path is monitored to be faulty, if the constraint path information does not contain segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv, the service message is a tenth IPv6 header and a tenth SRH header of the service message Wen Fengzhuang, and the packaged service message is obtained;

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

6. A message forwarding apparatus, the apparatus being adapted for use with a source node on any primary path in a segment routing and internet protocol sixth edition SRv 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 except the source node in the SRv network, a topology-independent loop-free backup fast reroute 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 multiprotocol label switching segment routing MPLS SR and SRv, the segment identification information of the other network node is an End SID of a destination segment identification of the other network node, and the link segment identification information of the other network node is an end.x SID of an endpoint three-layer cross-connect segment identification of the other network node; when any other network Node supports MPLS SR but does not support SRv < 6 >, the segment identification information of the other network Node is a Node segment identification Node SID of the other network Node, the link segment identification information of the other network Node is an Adj SID of an adjacent segment identification of the other network Node, 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, 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;

7. The apparatus of claim 6, wherein 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 MPLS SR but does not support SRv, MPLS label information is exchanged for the first multiprotocol label of the service packet Wen Fengzhuang, so as 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.

8. The apparatus of claim 6, wherein the first encapsulation 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 constraint path information, if it is determined that the first designated network Node supports both MPLS SR and SRv s 6 and the second designated network Node supports MPLS SR but does not support SRv according to the constraint path information, obtaining an encapsulated service packet for the first internet protocol version 6 IPv6 header of the service packet Wen Fengzhuang, a first routing extension header SRH header, and second MPLS label information, 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 an end.x SID of the first designated network Node included in the constraint path information, and the segment list information in the first SRH header includes an End SID and/or an end.x SID of the first designated network Node, and the second MPLS label information includes an End SID and/or a second SID of the second designated network Node included in the constraint path information and the second MPLS label information is located behind the first SID and/or the second SID of the first Node;

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

10. The apparatus of claim 6, wherein the apparatus further comprises:

The second encapsulation forwarding module is configured to, when the service packet is received and the failure of the main path is detected, obtain an encapsulated service packet for a tenth IPv6 header and a tenth SRH header of the service packet Wen Fengzhuang if segment identification information and/or link segment identification information of a designated network node supporting MPLS SR but not SRv are not included in the constraint path information;