WO2021169516A1 - 一种路径检测方法、电子设备及存储介质 - Google Patents

一种路径检测方法、电子设备及存储介质 Download PDF

Info

Publication number
WO2021169516A1
WO2021169516A1 PCT/CN2020/137304 CN2020137304W WO2021169516A1 WO 2021169516 A1 WO2021169516 A1 WO 2021169516A1 CN 2020137304 W CN2020137304 W CN 2020137304W WO 2021169516 A1 WO2021169516 A1 WO 2021169516A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
algorithm
node
fec element
igp
Prior art date
Application number
PCT/CN2020/137304
Other languages
English (en)
French (fr)
Inventor
彭少富
赵德涛
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021169516A1 publication Critical patent/WO2021169516A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/06—Deflection routing, e.g. hot-potato routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/70—Routing based on monitoring results

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a path detection method, electronic device, and storage medium.
  • Draft-ietf-lsr-flex-algo-05 proposed IGP (Interior Gateway Protocol) Flexible Algorithm (Flex-algorithm) technology (Flex-algo for short) to run multiple IGP algorithm calculations in the same network topology , Obtain multiple Flex-Algo planes and plan data transmission paths in each plane.
  • Flex-algo plane each node will take itself as the root node and use the corresponding IGP algorithm to calculate the optimal forwarding path to other destination nodes. According to the destination node to be reached, this node will obtain and know the next destination node.
  • Flex-algo can be used in combination with SR-MPLS (Segment Routing MPLS segment routing applied to MPLS (Multiprotocol Label Switching) forwarding plane) or SRv6 (Segment Routing IPv6 segment routing applied to IPv6 forwarding plane).
  • SR-MPLS Segment Routing MPLS segment routing applied to MPLS (Multiprotocol Label Switching) forwarding plane
  • SRv6 Segment Routing IPv6 segment routing applied to IPv6 forwarding plane
  • the purpose of the embodiments of the present application is to provide a path detection method.
  • the implementation of the present application provides a path detection method, including: determining the target FEC element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane; wherein the target FEC element includes The internal gateway protocol IGP algorithm information corresponding to the network topology plane; the echo request message generated according to the target FEC element is sent to the target node along the forwarding path related to the algorithm for the target node to verify the target FEC element; The explicit request message includes the target FEC element; according to the check result of the target FEC element fed back by the target node, it is determined whether the forwarding path is valid.
  • the embodiment of the present application also provides a path detection method, including: receiving an echo request message, the echo request message including the target FEC element of the target node to be detected; wherein the target FEC element includes the network topology where the forwarding path is located The interior gateway protocol IGP algorithm information corresponding to the plane; verify the target FEC element, and generate an echo response message including the verification result of the target FEC element; feedback the echo response message to the root node for the root node according to the target The check result of the FEC element determines whether the forwarding path is valid.
  • the embodiment of the present application also provides an electronic device, including: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are at least One processor executes, so that at least one processor can execute the above-mentioned path detection method.
  • the embodiment of the present application also provides a computer-readable storage medium that stores a computer program, and the computer program is executed by a processor to implement the above-mentioned path detection method.
  • Fig. 1 is a flowchart of a path detection method according to the first embodiment of the present application
  • Fig. 2 is a schematic diagram of a network topology according to the first embodiment of the present application.
  • FIG. 3 is a schematic diagram of the structure of the first FEC element according to the first embodiment of the present application.
  • FIG. 4 is a schematic diagram of a second FEC element structure according to the first embodiment of the present application.
  • FIG. 5 is a schematic diagram of the structure of a third FEC element in the first embodiment of the present application.
  • Fig. 6 is a schematic diagram of a network topology according to the second embodiment of the present application.
  • Fig. 7 is a schematic diagram of a network topology according to the third embodiment of the present application.
  • FIG. 8 is a flowchart of a path detection method in the fourth embodiment of the present application.
  • FIG. 9 is a schematic diagram of the structure of an electronic device according to the fifth embodiment of the present application.
  • the purpose of the implementation of this application is to provide a path detection method to achieve accurate detection and verification of the validity of the algorithm-related forwarding path in the Flex-algo plane, so as to avoid the invalidity of the calculated forwarding path from causing data transmission and business operation. Influence.
  • the first embodiment of the present application relates to a path detection method, which determines the target FEC (forwarding equivalence class) element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane; wherein, the target FEC element includes the network The interior gateway protocol IGP algorithm information corresponding to the topology plane; the echo request message generated according to the target FEC element is sent to the target node along the forwarding path related to the algorithm for the target node to verify the target FEC element; among them, echo The request message includes the target FEC element; according to the verification result of the target FEC element fed back by the target node, it is determined whether the forwarding path is valid.
  • the target FEC element forwarding equivalence class
  • the FEC element including the IGP algorithm information is constructed in advance to proceed the forwarding path.
  • it can directly call the target FEC element containing the specific IGP algorithm information to perform path detection according to the algorithm corresponding to the Flex-algo plane, ensuring that the forwarding path in each Flex-algo plane can be accurately detected.
  • the path detection method in this embodiment can be applied to the path detection of whether a variety of forwarding paths are valid.
  • a segmented routing architecture based on strict shortest path The segment routing and forwarding path calculated by the forwarding (strict SPF) algorithm, the segment routing and forwarding path based on the flexible IGP algorithm technology, the overlay service forwarding path, and the segment routing traffic engineering (SR-TE) example, etc., in this embodiment It is applied to the segmented routing and forwarding path based on the flexible IGP algorithm technology as an example for description, which specifically includes the following steps:
  • Step 101 Determine the target FEC element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane.
  • the root node of the forwarding path determines the target FEC element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane; where the target FEC element includes the network topology
  • the network topology diagram of the forwarding path related to the algorithm is shown in Figure 2.
  • ISIS Intermediate System to Intermediate System
  • SR-MPLS the control plane protocol of SR-MPLS.
  • Two Flex-algo planes are created, where the Algorithm corresponding to the Flex-algo 128 plane is 128, and the Algorithm corresponding to the Flex-algo 129 plane is 129.
  • the Flex-algo 128 plane includes nodes S, A, B, D and the bidirectional links connecting these nodes.
  • the Flex-algo 129 plane includes nodes S, B, C, D and the bidirectional links connecting these nodes.
  • the Prefix-SIDs associated with Algorithm 128 and 129 are 1280 and 1290, respectively.
  • Other nodes learn the FTN (FEC to NHLFE Map, FEC to Next Hop Label Forwarding Unit Mapping) and ILM (Incoming Label Mapping) forwarding entries that will be established to Prefix-D in the future.
  • the MPLS label information included in the entries is based on the Prefix -SID 1280 or 1290 is generated according to the existing technology. Assume that in the Flex-algo 128 plane and the Flex-algo 129 plane, the shortest forwarding path from the source node S to the end node D is S-B-D.
  • the root node initiates LSPPingSR-LSP Prefix-D Algorithm 128 to check whether the SR-BE (Segment Routing Best Effort) path SBD from the Flex-algo 128 plane to the destination node D is valid, and then node S will act as the Initiator
  • the (root) node takes node D as the target node, and the FEC element of node D as the target FEC element, where the FEC element of node D includes the algorithm information corresponding to the Flex-algo 128 plane.
  • the root node determines the target FEC element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane, it determines the path detection method of the forwarding path; if the path detection method is LSPPing detection, it will forward The terminal node of the path is used as the target node to obtain the target FEC element; if the path detection method is LSPTraceroute detection, each route node in the forwarding path is used as the target node to obtain the target FEC element.
  • a route node is a node in a segment list (Segment List), and the target FEC element may be an IGP-Prefix Segment type or an IGP-Adjacency Segment type.
  • Step 102 Send the echo request message generated according to the target FEC element to the target node along the forwarding path related to the algorithm for the target node to verify.
  • the root node After obtaining the target FEC element of the target node, the root node generates an echo request message according to the target FEC element, and sends the echo request message generated according to the target FEC element to the target along the forwarding path related to the algorithm Node, for the target node to verify the target FEC element; wherein, the echo request message includes the target FEC element.
  • the IGP algorithm information is included in the extension field of the target FEC element.
  • the target FEC element including the algorithm information is added to the target FEC element stack of the echo request message, and it is encapsulated with the relevant label information generated according to the prefix identifier
  • the echo request message is then sent to the target node along the forwarding path related to the algorithm, and the target node verifies the target FEC element, so as to check whether the path calculated by the specific IGP algorithm is valid Detection.
  • the target FEC element is obtained by adding an extension field including algorithm information to the existing IGP Segment FEC element.
  • the types of the FEC element adding the extension field include: IPv4 IGP-Prefix Segment ID, IPv6 IGP-Prefix Segment ID Sub -TLV or IGP-Adjacency Segment ID Sub-TLV, after adding an extension field including IGP algorithm information on the basis of the existing IGP SegmentFEC element, the three types of including algorithms for IPV4 IGP-Prefix, IPV6 IGP-Prefix and IGP-Adjacency
  • the FEC element of the information, IPv4 IGP-Prefix Segment ID per Algorithm Sub-TLV, IPv6 IGP-Prefix Segment ID per Algorithm Sub-TLV and IGP-Adjacency Segment ID per Algorithm Sub-TLV are shown in Figure 3 and Figure 4, respectively.
  • the algorithm field may include an algorithm value identifying the algorithm.
  • the addition position and value of the extended algorithm field can be adjusted as needed, and this embodiment does not limit the specific setting of the extended field.
  • node D After the root node S generates the echo request message, it first sends the message to Transit (transit node) B, and then transparently transmits the echo request message to the destination node D through node B.
  • Transit node B According to the definition of RFC8029, node D checks itself according to the preset conditions of sending the echo request message to the control plane, and performs subsequent processing according to the check result.
  • the preset condition for uploading the echo request message to the control plane can be any of the following conditions: the TTL of the top label of the MPLS label stack is timed out, the top label of the MPLS label stack is the router alert label (Router Alert Label), and the IP header
  • the destination IP in the IP header is in the range of 127/8, the Router Alert Option in the IP header is valid, and the TTL in the IP header has timed out.
  • node D sends the received echo request message to the control plane, and node D acts as the responder (response) node in the control
  • the plane recognizes the path detection type according to the destination UDPport as 3503, and checks the target FEC element.
  • an echo reply echo response
  • the destination node when the destination node performs the verification of the FEC element, it can generally refer to the verification process of RFC8029.
  • the responding node determines the type of the IGP protocol according to the target FEC element, and The target FEC element is checked according to the type of the IGP protocol. That is, first, according to the Protocol value in the target FEC element, determine the type of the IGP protocol used when creating the path related to the algorithm, and determine the verification of the target FEC element and label according to the type of the IGP protocol.
  • modify step 4 of section 4.4.1 in RFC8029 to the following in advance, and perform verification according to the modified process:
  • step 4.a If the incoming label bound to the FEC element currently to be checked is an implicit empty label, set the FEC-status to 2, and then execute step 4.a.
  • FEC-return-code 10 which means "The label mapped by the current FEC element is not the current top-level label in the label stack (Mapping for this FEC is not the given label at stack-depth)", and FEC-status is set to 1, Then return.
  • IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV is 0, then any locally enabled IGP protocol will be used;
  • IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV is 1, the IGP protocol is OSPF;
  • IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV is 2
  • IGP protocol is ISIS
  • the value of the protocol in the IPv4 IGP-Prefix-Segment ID per Algorithm sub-TLV cannot be identified, the value of the protocol is regarded as 0;
  • the Best-return-code is set to 10, which means "The label of the current FEC element mapping is not the label of the ⁇ Return Subcode> layer in the label stack (Mapping for this FEC) is not the given label at stack- depth ⁇ RSC>)".
  • Verification 1 The non-PHP flag is set during node-SID notification: If the protocol is OSPF (Open Shortest Path First), the NP-Flag in SR-OSPF should be set to 0; if the protocol is ISIS , The P-Flag in SR-ISIS should be set to 0.
  • OSPF Open Shortest Path First
  • ISIS ISIS
  • the method for determining the IGP protocol type is similar to the method in CASE1, so I won't repeat it here.
  • Best-return-code 10 which means "The label of the current FEC element mapping is not the label of the ⁇ Return Subcode> layer in the label stack (Mapping for this FEC) is not the given label at stack-depth ⁇ RSC>)".
  • CASE4 If Label-stack-depth is greater than 0, and the FEC-stack-depth in Target FEC Stack sub-TLV is IPv6 IGP-Prefix Segment ID per Algorithm Sub-TLV, the processing is similar to the above CASE2 and will not be repeated.
  • the IGP protocol is OSPF
  • the IGP protocol is ISIS
  • Verification 2 IGP-Adjacency Segment ID per Algorithm sub-TLV
  • the Advertising Node Identifier in the sub-TLV indicates that the node represented by the IGP-Adjacency Segment ID per Algorithm FEC, this verification only needs to be in the link state database maintained by the node Query confirmation;
  • Adj.Type is equal to 4 or 6 (IGP Adjacency or LAN Adjacency):
  • Verification 3 IGP-Adjacency Segment ID per Algorithm sub-TLV
  • the Advertising Node Identifier in the sub-TLV indicates that the node represented by the IGP-Adjacency Segment ID per Algorithm FEC, this verification only needs to be in the link state database maintained by the node Query confirmation;
  • an echo response message including the verification result of the target FEC element is generated, and then the echo response message including the verification result of the target FEC element is fed back to the root node.
  • Step 103 Determine whether the forwarding path is valid according to the verification result of the target FEC element fed back by the target node.
  • the destination node After the destination node generates an echo response message according to the check result of the target FEC element, it feeds back the echo response message including the check result of the target FEC element to the root node of the path, and the root node feeds back according to the target node's feedback
  • the check result of the target FEC element determines whether the forwarding path is valid.
  • the root node after receiving the echo response message, determines the check result of the target FEC element according to the return code value of the target FEC element detection result in the message, and then determines the check result of the target FEC element Whether the forwarding path is valid.
  • the result of the target FEC element check is the value of the return code Best-return-code, and the value of Best-return-code in the received echo response message is 12.
  • the root node determines the verification result of the target FEC element according to the corresponding meaning assigned to different values of Best-return-code in advance. After querying, the result corresponding to the value of 12 is learned; the current element in the FEC stack is not connected to the interface Protocol not associated with interface at FEC-stack-depth, then the root node can determine that the verification of the target FEC element fails, and then the root node determines that the forwarding path is an invalid path based on the result of the target FEC element verification failure, and Displays the detection result of invalid forwarding path.
  • this embodiment provides a path detection method, which redefines the FEC element including the IGP algorithm information by adding an extension field including the IGP algorithm information to the existing FEC element;
  • detecting whether the path is valid determine the target FEC element to be detected that includes the algorithm information corresponding to the network topology plane where the forwarding path is located, and determine whether the forwarding path is valid according to the check result of the target FEC element, by checking the FEC element and
  • the extension of the path detection protocol ensures that it can accurately detect whether the forwarding path in the Flex-algo plane is effective.
  • the second embodiment of this application relates to a path detection method.
  • the second embodiment is roughly the same as the first embodiment.
  • the value of the algorithm for identifying the algorithm in the algorithm field can be obtained through IANA (Internet Assigned Numbers Authority).
  • the standard value assigned by the Internet Digital Distribution Agency) for the algorithm can also be a user-defined algorithm value.
  • IANA assigns standard values to some algorithms to detect whether the paths calculated by some commonly used algorithms are valid; through user-defined algorithm values for the algorithms, the path calculated by the algorithm selected by the user is effective and efficient. Detection, the specific detection steps in the path detection process can refer to the first embodiment.
  • Step 101 Determine the target FEC element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane.
  • the root node determines the target FEC element of the target node according to the algorithm corresponding to the network topology plane and the forwarding path and detection method.
  • the target FEC element is added with an extension field including IGP algorithm information.
  • IGP algorithm in the extension field The information is indicated by the value of the algorithm, where the value of the algorithm includes the standard value assigned by the Internet digital distribution agency IANA for the algorithm and the value of the algorithm defined by the user.
  • the value and meaning of the algorithm in the algorithm field added by the FEC element are as follows: 0 ⁇ 127: the standard value assigned by IANA, for example, 0 means “SPF algorithm based on link metric" shortest path forwarding based on link metric Algorithm, 1 means “Strict SPF algorithm based on link metric” Strict shortest path forwarding algorithm based on link metric; 128-255: Used to identify IGP Flex-algo, which is defined by the user. For example, the user can create a Flex-algo plane with an Algorithm of 128 or a Flex-algo plane with an Algorithm of 129. In practical applications, the range of the algorithm value can be set according to actual conditions or needs, and this embodiment does not limit the setting of the algorithm value.
  • the root node R1 detects the path calculated based on the strict shortest path algorithm under the segmented routing architecture.
  • the algorithm standard assigned by IANA for the strict shortest path algorithm is 1.
  • ISIS is used as the control plane protocol of SR-MPLS in the IPv4 network.
  • Ingress (start) node R1 is established to egress (exit) node R3 based on Strict SPF (strict shortest path) algorithm SR LSP (Segment Routing Label Switching Path) ,
  • Strict SPF strict shortest path
  • SR LSP Segment Routing Label Switching Path
  • the Strict SPF Prefix-SID assigned by the R3 node to its loopback route Prefix-R3 is 300, and the R1 and R2 nodes will learn the FTN and ILM forwarding entries that will be established to the Prefix-R3 in the future, and the MPLS labels included in the entries
  • the information is generated according to the Prefix-SID 300 with reference to the prior art.
  • Root node R1 initiates LSP ping SR-LSP Prefix-R3 Algorithm 1
  • node R3 is used as the target node according to the forwarding path and path detection method
  • IPv4 IGP-Prefix is set according to the algorithm corresponding to the network topology plane where the forwarding path is located.
  • Segment ID per Algorithm ⁇ Prefix-R3, Algorithm 1> as the target FEC element.
  • Step 102 Send the echo request message generated according to the target FEC element to the target node along the forwarding path related to the algorithm for the target node to verify.
  • the top label of the stack is the label corresponding to Prefix-SID 300
  • the label TTL 255
  • an echo request message is generated.
  • the target FEC stack TLV may also include FEC elements corresponding to the remaining tags in the label stack.
  • R3 After generating the echo request message, it sends the message to the R2 node, and the R2 node transparently transmits the message to node R3. After receiving the echo request message, R3 will send the echo request message to the control plane according to the conditions After detecting itself, R3 detects that it meets the preset conditions and sends the message to the control plane. The R3 node, as the responding node, verifies the target FEC element.
  • the R3 node constructs an echo reply message according to the verification result of the target FEC element, and the echo reply message contains the information of successful verification, and feeds back the echo reply message to the root node R1.
  • Step 103 Determine whether the forwarding path is valid according to the verification result of the target FEC element fed back by the target node.
  • the root node determines whether the path is valid according to the inspection result of the target FEC element, and outputs the inspection result.
  • the algorithm value in the extension field of the FEC element includes the standard value assigned by IANA for a specific algorithm or a user-defined algorithm value, and some specific algorithms are used by IANA. Allocate standard values so that when detecting paths calculated by some algorithms, the target FEC element including specific algorithm information can be called to accurately detect whether the forwarding path is effective; the value can be obtained by user-defined algorithm directly in Flex-algo
  • the path detection of the forwarding path calculated by a custom-valued algorithm in the plane ensures that the path calculated by the algorithm selected by the user can be efficiently and accurately determined whether the path calculated by the algorithm selected by the user is valid.
  • the third embodiment of the present application relates to a path detection method.
  • This embodiment is roughly similar to the first embodiment.
  • the adjacent links are identified by the IGP algorithm corresponding to the Flex-algo plane.
  • the specific detection steps can refer to the first embodiment.
  • Step 101 Determine the target FEC element of the target node to be detected according to the forwarding path related to the algorithm in the network topology plane.
  • the root node determines the target FEC element of the target node that needs to be detected according to the forwarding path, the network topology plane where the path is located, and the path detection mode.
  • the SR-TE (Segment Routing Traffic Engineering) path in the network topology needs to be tested for LSPTraceroute, and then the corresponding segment list (Segment List) corresponding to the SR-TE instance is determined. Identify the list (SID List), and then determine the target FEC element according to the algorithm corresponding to each segment.
  • SID List Segment Routing Traffic Engineering
  • SR-TE instance path detection is performed.
  • ISIS is used as the control plane protocol of SR-MPLS in the IPv4 network to create two Flex -Algo plane, where the Algorithm corresponding to the Flex-algo 128 plane is 128, and the Algorithm corresponding to the Flex-algo 129 plane is 129.
  • the Flex-algo 128 plane includes nodes S1, A, B, and D and the bidirectional links connecting these nodes.
  • the Flex-algo 129 plane includes nodes S2, B, C, D and the bidirectional links connecting these nodes.
  • Both planes use IGPmetric (IGP metric) to calculate the shortest path, and the IGPmetric of the link (B-D) is 100, and the IGPmetric of the remaining links is 10.
  • the Prefix-SID related to Algorithm 128 allocated by node B for its loopback route Prefix-B is 1280.
  • Other nodes learn the FTN and ILM forwarding entries that will be established to Prefix-B in the future.
  • the MPLS label information included in the entries is generated according to the Prefix-SID 128 according to the existing technology, and node B allocates and distributes information to its local link (BD)
  • BD local link
  • the Adjacency-SID (adjacent segment identifier) related to the algorithm 128 is 1281, and other nodes will store it in the local link state database after learning.
  • An SR-TE instance in the Flex-algo 128 plane (denoted as sr-te-100) is created on node S1, then its Segment List is ⁇ Node-B, Link(BD) ⁇ , and the corresponding SID List is ⁇ 1280 ,1281 ⁇ .
  • the S1 node serves as the root node and sets the end node B of the first segment of the SR-TE and the end node D of the adjacent segment link (BD) of the second segment in the SR-TE
  • FEC element IGP-Adjacency Segment ID per Algorithm ⁇ link(BD) corresponding to the link (BD) ),128> as the target FEC element.
  • Step 102 Send the echo request message generated according to the target FEC element to the target node along the forwarding path related to the algorithm for the target node to verify.
  • the root node constructs an echo request message according to the FEC element to be detected, and hands the FEC element to be detected to the corresponding target node for verification.
  • the root node S1 reconstructs the echo request message according to the received echo reply message.
  • the target FEC element stack remains unchanged.
  • the TTL value of the top label is set to 2, and then it is sent to node A again, because the top label is 2, A After subtracting 1 from the TTL value, the message is directly forwarded to node B.
  • Node B replies to the S1 node with an echo reply message.
  • the echo reply message contains information about the successful verification and contains FEC Stack Change TLV, prompting the root node S1 to pop up the IPv4 IGP-Prefix Segment ID in the target FEC stack TLV. Algorithm Sub-TLV.
  • the TTL of the top label is set to 3. Forward to the next hop node A.
  • the TTL of the top label is 3, and after the TTL of the top label is reduced by 1, it is directly forwarded to node B.
  • the TTL of the top label is 2, and the prefix is terminated.
  • -SID 1280 corresponding label continue to check the ILM table according to the label corresponding to the lower Adjacency-SID 1281, subtract 1 from the top label and pop up the label, and put the label in the lower layer IP header of the TTL copy, and then forward the message to node D.
  • Node D replies to the S1 node with an echo reply message.
  • the echo reply message contains information about successful verification and FEC Stack Change TLV, prompting the head node to pop up the IGP-Adjacency Segment ID per Algorithm Sub in the target FEC stack TLV. -TLV.
  • the responding node can directly include the echo response message that the verification failed to the root node, and terminate the subsequent Path detection.
  • Step 103 Determine whether the forwarding path is valid according to the verification result of the target FEC element fed back by the target node.
  • the root node determines whether the path is valid according to the inspection result of the FEC element, and outputs the inspection result.
  • this embodiment provides a path detection method, which determines the target FEC element corresponding to the algorithm-related path in the SR-TE instance according to the network topology plane, path detection method, and forwarding path where the created SR-TE instance is located. , According to the target FEC element to realize whether the segment path related to the algorithm in the SR-TE instance is valid or not.
  • the fourth embodiment of the present application relates to a path detection method, including: receiving an echo request message, the echo request message including the target FEC element of the target node to be detected; wherein the target FEC element includes the network topology where the forwarding path is located The interior gateway protocol IGP algorithm information corresponding to the plane; verify the target FEC element, and generate an echo response message including the verification result of the target FEC element; feedback the echo response message to the root node for the root node according to the target The check result of the FEC element determines whether the forwarding path is valid.
  • FIG. 8 The specific process of the path detection method in this embodiment is shown in FIG. 8, and specifically includes the following steps:
  • Step 801 Receive an echo request message.
  • the responding node when checking whether the forwarding path is valid, receives an echo request message.
  • the echo request message includes the target FEC element of the target node to be detected, where the target FEC element includes the network topology where the forwarding path is located.
  • the interior gateway protocol IGP algorithm information corresponding to the plane determines the target FEC element to be verified according to the received echo request message.
  • the IGP algorithm information is included in the extension field of the target FEC element.
  • the IGP algorithm information in the extended field is indicated by the standard value assigned by the Internet digital distribution agency IANA for the algorithm or by the user-defined algorithm.
  • the type of the FEC element to which the extension field is added includes: IPv4 IGP-Prefix Segment ID Sub-TLV, IPv6 IGP-Prefix Segment ID Sub-TLV, or IGP-Adjacency Segment ID Sub-TLV.
  • Step 802 Verify the target FEC element contained in the echo request message, and generate an echo response message including the result of the target FEC element verification.
  • the responding node verifies the target FEC element, and generates a checksum including the target FEC element according to the verification result of the target FEC element. Echo response message of the inspection result.
  • the responding node when it performs the verification of the target FEC element, it can generally refer to the verification process of RFC8029.
  • the responding node verifies the target FEC element.
  • determine the type of the IGP protocol, and check the target FEC element according to the type of the IGP protocol that is, first determine the IGP protocol used when creating the algorithm-related path according to the protocol value in the target FEC element
  • the type of the target FEC element and label is determined according to the type of the IGP protocol.
  • the return code value indicating the FEC element verification result is set according to the verification result of the target FEC element, and the target FEC element is generated to include the target FEC Echo response message of element check result.
  • Step 803 Feed back an echo response message to the root node for the root node to determine whether the forwarding path is valid according to the verification result of the target FEC element.
  • the echo response message is fed back to the root node of the forwarding path, and the root node indicates the target FEC according to the echo response message
  • the return code value of the element check result determines the check result of the target FEC element, and then determines whether the forwarding path is valid according to the check result of the target FEC element.
  • this embodiment provides a path detection method, which implements the extension of the existing path detection protocol by adding an extension field including IGP algorithm information to the existing FEC element, and introduces the FEC element including the IGP algorithm information; Therefore, in the detection of whether the forwarding path calculated by the IGP algorithm is valid, the root node can call the target FEC element including the IGP algorithm information to initiate path detection, and the responding node can accurately calibrate the target FEC element containing the IGP algorithm information. The root node then determines whether the forwarding path is valid according to the verification result of the target FEC element, so as to achieve accurate and efficient detection of whether the forwarding path calculated by the IGP algorithm is valid.
  • the implementation of this application determines whether the forwarding path in the Flex-algo plane is valid or not, according to the IGP algorithm and forwarding path corresponding to the Flex-algo plane, the target node to be detected is determined and invoked
  • the target node is related to the target FEC element of the IGP algorithm, and constructs an echo request message for path detection for the target node to verify the target FEC element.
  • the Flex is accurately determined.
  • the forwarding path in the algo plane is valid, by extending the existing path detection protocol, pre-build FEC elements including IGP algorithm information, so that when the forwarding path is valid, it can be directly based on the algorithm corresponding to the Flex-algo plane. Calling the target FEC element containing the IGP algorithm information to perform path detection ensures that the validity of the forwarding path in each Flex-algo plane can be accurately detected.
  • the IGP algorithm information is included in the extended field of the target FEC element.
  • the path in the Flex-algo plane can be directly called when the path in the Flex-algo plane is detected.
  • the target FEC element ensures that it can accurately detect whether the path in the Flex-algo plane is effective.
  • the IGP algorithm information in the extended field is indicated by the algorithm value, where the algorithm value includes the standard value assigned by the Internet Digital Distribution Agency IANA for the algorithm and the user-defined algorithm value, and the IANA is the algorithm.
  • the assigned standard value can accurately identify the commonly used algorithm, which is convenient for detecting the path calculated by the commonly used IGP algorithm.
  • the forwarding path calculated by the algorithm that the user needs to be detected is guaranteed Perform testing.
  • FEC elements that add extension fields include: IPv4 IGP-Prefix Segment ID Sub-TLV, IPv6 IGP-Prefix Segment ID Sub-TLV, or IGP-Adjacency Segment ID Sub-TLV, making the implementation of this application broad Application scenarios.
  • determining the target FEC element of the target node to be detected includes: determining the path detection method of the forwarding path; if the path detection method is LSP Ping detection, the end of the forwarding path is determined The node serves as the target node to obtain the target FEC element; if the path detection method is LSP Traceroute detection, each route node in the forwarding path is used as the target node, and the target FEC element is obtained.
  • the target node is determined by the path detection method, and the target The FEC element of the node is used as the target element to ensure the efficiency of the detection and the accuracy of the path detection result.
  • the fifth embodiment of the present application relates to an electronic device. As shown in FIG. 9, it includes at least one processor 901; and a memory 902 communicatively connected to the at least one processor 901; The instructions executed by the processor 901 are executed by the at least one processor 901, so that the at least one processor 901 can execute the foregoing path detection method.
  • the memory and the processor are connected in a bus mode
  • the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors and various circuits of the memory together.
  • the bus can also connect various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all well-known in the art, and therefore, no further description will be given herein.
  • the bus interface provides an interface between the bus and the transceiver.
  • the transceiver may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on the transmission medium.
  • the data processed by the processor is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor.
  • the processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory can be used to store data used by the processor when performing operations.
  • the sixth embodiment of the present application relates to a computer-readable storage medium storing a computer program.
  • the computer program is executed by the processor, the above method embodiment is realized.
  • the program is stored in a storage medium and includes several instructions to enable a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

本申请实施例涉及通信领域，公开了一种路径检测方法、电子设备及存储介质。本发明中，方法包括：根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素；其中，目标FEC元素包括网络拓扑平面对应的内部网关协议IGP算法信息；将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点对目标FEC元素进行校验；其中，回显请求报文包括目标FEC元素；根据目标节点反馈的目标FEC元素的校验结果，确定转发路径是否有效。

Description

一种路径检测方法、电子设备及存储介质
相关申请的交叉引用
本申请基于申请号为202010123741.4、申请日为2020年2月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及通信领域，特别涉及一种路径检测方法、电子设备及存储介质。
背景技术
draft-ietf-lsr-flex-algo-05中提出了IGP(Interior Gateway Protocol内部网关协仪)灵活算法(Flex-algorithm)技术(简称Flex-algo)，在同一网络拓扑内运行多种IGP算法计算，得到多个Flex-Algo平面并在各平面内进行数据传输路径规划。在Flex-algo平面内，每个节点都会以自身为根节点采用相应的IGP算法计算至其它目的节点的最优转发路径，根据要到达的目的节点，本节点将获取并知晓至目的节点的下一跳节点是谁，而下一跳节点会以自身为根节点采用同样的IGP算法计算至该目的节点的最优转发路径，继续获取下一跳节点，依次类推形成逐跳的转发路径。Flex-algo可与SR-MPLS(Segment Routing MPLS分段路由应用于MPLS(多协议标签交换)转发平面)或SRv6(Segment Routing IPv6分段路由应用于IPv6转发平面)结合使用。
发明人发现相关技术中至少存在如下问题：当前的技术手段无法对Flex-algo平面内得到的转发路径是否有效进行准确的验证。
发明内容
本申请实施方式的目的在于提供一种路径检测方法。
为解决上述技术问题，本申请的实施方式提供了一种路径检测方法，包括：根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素；其中，目标FEC元素包括网络拓扑平面对应的内部网关协议IGP算法信息；将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点对目标FEC元素进行校验；其中，回显请求报文包括目标FEC元素；根据目标节点反馈的目标FEC元素的校验结果，确定转发路径是否有效。
本申请的实施方式还提供了一种路径检测方法，包括：接收回显请求报文，回显请求报文包括待检测的目标节点的目标FEC元素；其中，目标FEC元素包括转发路径所在网络拓扑平面对应的内部网关协议IGP算法信息；对目标FEC元素进行校验，并生成包括目标FEC元素的校验结果的回显应答报文；向根节点反馈回显应答报文，供根节点根据目标FEC元素的校验结果确定转发路径是否有效。
本申请的实施方式还提供了一种电子设备，包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行上述的路径检测方法。
本申请的实施方式还提供了一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时实现上述的路径检测方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定。
图1是根据本申请第一实施方式中的路径检测方法流程图；
图2是根据本申请第一实施方式中的网络拓扑示意图；
图3是根据本申请第一实施方式中的第一种FEC元素结构示意图；
图4是根据本申请第一实施方式中的第二种FEC元素结构示意图；
图5是根据本申请第一实施方式中的第三种FEC元素结构示意图；
图6是根据本申请第二实施方式中的网络拓扑示意图；
图7是根据本申请第三实施方式中的网络拓扑示意图；
图8是根据本申请第四实施方式中的路径检测方法流程图；
图9是根据本申请第五实施方式中的电子设备结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施方式进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施方式中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请实施方式的目的在于提供一种路径检测方法，实现对Flex-algo平面内与算法相关的转发路径是否有效的准确检测和验证，从而避免计算出的转发路径无效对数据传输和业务运行造成影响。
本申请的第一实施方式涉及一种路径检测方法，根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC(转发等价类)元素；其中，目标FEC元素包括网络拓扑平面对应的内部网关协议IGP算法信息；将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点对目标FEC元素进行校验；其中，回显请求报文包括目标FEC元素；根据目标节点反馈的目标FEC元素的校验结果，确定转发路径是否有效，通过扩展现有路径检测协议，预先构建包括IGP算法信息的FEC元素，从而在进行转发路径是否有效的检测时，能直接根据Flex-algo平面对应的算法，调用含有特定IGP算法信息的目标FEC元素进行路径检测，保证了能够对各Flex-algo平面内的转发路径是否有效进行准确的检测。
下面对本实施方式的路径检测方法的实现细节进行具体的说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。
本实施方式中的路径检测方法的具体流程如图1所示，本实施方式中的路径检测方法可以应用在多种转发路径是否有效的路径检测中，例如，分段路由架构中基于严格最短路径转发(strict SPF)算法计算出的分段路由转发路径、基于IGP灵活算法技术的分段路由转发路径、overlay业务转发路径和分段路由流量工程(SR-TE)实例等，本实施方式中以应用于基于IGP灵活算法技术的分段路由转发路径为例进行说明，具体包括以下步骤：
步骤101，根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素。
具体地说，在进行转发路径是否有效的检测时，转发路径的根节点根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素；其中，目标FEC元素包括网络拓扑平面对应的内部网关协议IGP算法信息。
在一个例子中，与算法相关的转发路径所在网络拓扑示意图如图2所示，在IPV4网络中，采用ISIS(Intermediate System to Intermediate System，中间系统到中间系统)作为SR-MPLS的控制面协议，创建了两个Flex-algo平面，其中Flex-algo 128平面对应的Algorithm取值为128，Flex-algo 129平面对应的Algorithm取值为129。Flex-algo 128平面中包含节点S、A、B、D以及这些节点间相连的双向链路。Flex-algo 129平面中包含节点S、B、C、D以及这些节点间相连的双向链路。若D节点为其路由回环接口(loopback)路由Prefix-D(前缀标识D)分配的与Algorithm 128、129相关的Prefix-SID分别为1280、1290。其它节点学习到以后将建立至Prefix-D的FTN(FEC to NHLFE Map，FEC至下一跳标签转发单元映射)与ILM(入标签映射)转发表项，表项中包括的MPLS标签信息根据Prefix-SID 1280或1290按照现有技术生成。假设在Flex-algo 128平面与Flex-algo 129平面中，源节点S至终节点D的最短转发路径均为S-B-D。根节点针对Flex-algo 128平面内至目的节点D的SR-BE(Segment Routing Best Effort分段路由尽力而为)路径S-B-D是否有效发起LSPPingSR-LSP Prefix-D Algorithm 128检测，则节点S将作为Initiator(根)节点，将节点D作为目标节点，将节点D的FEC元素作为目标FEC元素，其中，节点D的FEC元素包括Flex-algo 128平面对应的算法信息。
在实际应用中，根节点根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素时，确定转发路径的路径检测方式；若路径 检测方式为LSPPing检测，则将转发路径的终节点作为目标节点，得到目标FEC元素；若路径检测方式为LSPTraceroute检测，则将转发路径中的各航路节点均作为目标节点，得到目标FEC元素。其中，航路节点(Segment Node)为处于分段列表(Segment List)中的节点，目标FEC元素可能是IGP-Prefix Segment类型或IGP-Adjacency Segment类型。
步骤102，将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点进行校验。
具体地说，根节点在获取到目标节点的目标FEC元素后，根据目标FEC元素生成回显请求报文，将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点对目标FEC元素进行校验；其中，回显请求报文包括目标FEC元素。并且，IGP算法信息包括在目标FEC元素的扩展字段中。
在一个例子中，确定出待检测的目标FEC元素后，将包括算法信息的目标FEC元素添加进回显请求报文的目标FEC元素堆栈中，并与根据前缀标识生成的相关的标签信息一起封装在回显请求报文中，然后将回显请求报文沿与算法相关的转发路径发送到目标节点，由目标节点对目标FEC元素进行校验，从而对特定IGP算法计算出的路径是否有效进行的检测。
其中，目标FEC元素是由现有的IGP Segment FEC元素添加包括算法信息的扩展字段得到，添加扩展字段的FEC元素的类型包括：IPv4 IGP-Prefix Segment ID Sub-TLV、IPv6 IGP-Prefix Segment ID Sub-TLV或IGP-Adjacency Segment ID Sub-TLV，在现有IGP SegmentFEC元素的基础上添加包括IGP算法信息的扩展字段后，针对IPV4 IGP-Prefix、IPV6 IGP-Prefix和IGP-Adjacency的三类包含算法信息的FEC元素，IPv4 IGP-Prefix Segment ID per Algorithm Sub-TLV、IPv6 IGP-Prefix Segment ID per Algorithm Sub-TLV和IGP-Adjacency Segment ID per Algorithm Sub-TLV的结构示意图分别如图3、图4和图5所示。其中，算法字段外的其余字段的含义和生成方式均可参考RFC8287。算法字段中可以包括标识算法的算法取值。在实际应用中，可以根据需要调整扩展的算法字段的添加位置和取值，本实施方式对扩展字段的具体设置不做限制。
例如，根节点S在图2所示的网络拓扑中，针对算法取值为128的Flex-algo 128平面发起LSPPingSR-LSP Prefix-D Algorithm 128检测，则根节点S根据目 标节点D的FEC元素IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-D,Algorithm 128>，进行echo request(回显请求)报文的构建，设置Echo request PDU(回显请求报文协议数据单元)中的target FEC stack TLV(目标FEC元素堆栈)：{IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-D,Algorithm 128>}，并封装IP/UDP(用户数据报协议)头以及标签栈，栈顶标签为Prefix-SID 1280对应的标签，标签TTL＝255，封装的标签信息可以预先根据RFC8029按照Prefix-SID(前缀段标识)1280生成，具体的封装方式也可以参考RFC8029进行封装。
根节点S生成回显请求报文后，将报文先发送到Transit(传输节点)B，通过节点B将回显请求报文透传到目的节点D。按照RFC8029的定义，节点D根据将回显请求报文上送控制面的预设条件对自身进行检验，并根据校验结果进行后续的处理。其中，将回显请求报文上传控制面的预设条件可以为以下任何条件之一：MPLS标签栈的顶层标签TTL超时，MPLS标签栈的顶层标签是路由器告警标签(Router Alert Label)，IP头中的目的IP处于127/8的范围内，IP头中路由器告警选项(Router Alert Option)有效，IP头中的TTL超时。例如在本例中，节点D根据回显请求报文的目的IP处于127/8的范围内，将接收到的回显请求报文上送控制平面，D节点作为Responder(应答)节点，在控制平面根据目的UDPport为3503识别路径检测类型，并对目标FEC元素进行校验。
若节点D在控制面对FEC元素进行校验时，发现目标FEC元素的标签值是有效的，存在Prefix-SID 1280相应的ILM转发表项并且标签操作为POP；检查发现报文的标签栈与target FEC stack是一致的，即D节点确实通过ISIS对外通告了IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-D,Algorithm 128>且Prefix-SID为1280，则判定目标FEC元素校验成功，目的节点D根据校验结果构建echo reply(回显应答)报文，并在echo reply报文中包含校验成功的信息。
其中，目的节点进行FEC元素的校验时，大致上可以参考RFC8029的校验过程，为了保证对包括算法信息的FEC元素的准确校验，应答节点根据目标FEC元素，确定IGP协议的类型，并根据IGP协议的类型对目标FEC元素进行校验。即，先根据目标FEC元素中的Protocol值，确定与算法相关的路径创建时所采用的IGP协议的类型，根据IGP协议的类型确定对目标FEC元素与标签进行校验。
例如，预先将RFC8029中的section 4.4.1的step 4修改成如下，并按照修 改后的流程进行校验：
Step 4.
如果当前待校验的FEC元素所绑定的入标签为隐式空标签，则设置FEC-status为2，然后执行step 4.a。
否则，如果当前待校验的FEC元素绑定的入标签为Label-L，则执行step 4.a。
否则，设置FEC-return-code为10，表示“当前FEC元素映射的标签不是标签栈中当前顶层标签(Mapping for this FEC is not the given label at stack-depth)”，设置FEC-status为1，然后return。
Step 4.a SID的校验
CASE1：如果Label-stack-depth等于0，并且Target FEC Stack sub-TLV中处于FEC-stack-depth的是IPv4 IGP-Prefix Segment ID per Algorithm Sub-TLV，则：
首先确定IGP协议类型：
若IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV中的protocol为0，则使用任何本地使能的IGP协议；
若IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV中的protocol为1，则IGP协议为OSPF；
若IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV中的protocol为2，则IGP协议为ISIS；
若IPv4 IGP-Prefix Segment ID per Algorithm sub-TLV中的protocol的取值无法识别，则将protocol的取值当成0；
若以下任一校验失败，则设置Best-return-code为10,表示“当前FEC元素映射的标签不是标签栈中第<Return Subcode>层标签(Mapping for this FEC is not the given label at stack-depth<RSC>)”。
校验1：node-SID通告时设置了non-PHP标志：如果protocol是OSPF(Open Shortest Path First开放式最短路径优先)，则SR-OSPF中的NP-Flag应设置为0；如果protocol是ISIS，则SR-ISIS中的P-Flag应设置为0。
校验2：针对IPv4-prefix通告的Node-SID per Algorithm是通过IGP通告的：
若检测到Interface-I上没有IGP协议通告过当前待校验的FEC元素，则设置Best-return-code to 12,表示“FEC栈中当前元素没有与接口上的协议关联(Protocol not associated with interface at FEC-stack-depth)”，然后return。
设置FEC-Status为1，然后return。
CASE2：如果Label-stack-depth大于0，并且Target FEC Stack sub-TLV中处于FEC-stack-depth的是IPv4 IGP-Prefix Segment ID per Algorithm Sub-TLV，则：
首先确定IGP协议类型，确定IGP协议类型的方法与CASE1中的方法相似，在此就不再赘述。
若以下校验失败，则设置Best-return-code为10,表示“当前FEC元素映射的标签不是标签栈中第<Return Subcode>层标签(Mapping for this FEC is not the given label at stack-depth<RSC>)”。
校验1：针对IPv4-prefix通告的Node-SID per Algorithm是通过IGP通告的：
若检测到Interface-I上没有IGP协议通告过当前待校验的FEC元素，则设置Best-return-code to 12,表示“FEC栈中当前元素没有与接口上的协议关联(Protocol not associated with interface at FEC-stack-depth)”，然后return。
设置FEC-Status为1，然后return。
CASE3：如果Label-stack-depth等于0，并且Target FEC Stack sub-TLV中处于FEC-stack-depth的是IPv6 IGP-Prefix Segment ID per Algorithm Sub-TLV，则处理与上述CASE1类似，不再赘述。
CASE4：如果Label-stack-depth大于0，并且Target FEC Stack sub-TLV中处于FEC-stack-depth的是IPv6 IGP-Prefix Segment ID per Algorithm Sub-TLV，则处理与上述CASE2类似，不再赘述。
CASE5：如果Target FEC Stack sub-TLV中处于FEC-stack-depth的是IGP-Adjacency Segment ID per Algorithm Sub-TLV，则：
首先确定IGP协议类型：
若IGP-Adjacency Segment ID per Algorithm sub-TLV中的protocol为0，则使用任何本地使能的IGP协议；
若IGP-Adjacency Segment ID per Algorithm sub-TLV中的protocol为1，则 IGP协议为OSPF；
若IGP-Adjacency Segment ID per Algorithm sub-TLV中的protocol为2，则IGP协议为ISIS；
若IGP-Adjacency Segment ID per Algorithm sub-TLV中的protocol取值无法识别，则将protocol的取值当成0；
若以下任一校验失败，则设置Best-return-code为35,表示“当前FEC元素与本端入接口无关(Mapping for this FEC is not associated with the incoming interface)”
当Adj.Type等于1(Parallel Adjacency)时：
校验1：IGP-Adjacency Segment ID per Algorithm sub-TLV中的Receiving Node Identifier是本节点的Node-ID；
校验2：IGP-Adjacency Segment ID per Algorithm sub-TLV中的Advertising Node Identifier所表示的节点确实通告了该IGP-Adjacency Segment ID per Algorithm FEC，此验证只需在本节点维护的链路状态数据库中查询确认；
当Adj.Type等于4或6(IGP Adjacency或LAN Adjacency)时：
校验1：IGP-Adjacency Segment ID per Algorithm sub-TLV中的Remote Interface ID与Interface-I匹配；
校验2：IGP-Adjacency Segment ID per Algorithm sub-TLV中的Receiving Node Identifier是节点的Node-ID；
校验3：IGP-Adjacency Segment ID per Algorithm sub-TLV中的Advertising Node Identifier所表示的节点确实通告了该IGP-Adjacency Segment ID per Algorithm FEC，此验证只需在本节点维护的链路状态数据库中查询确认；
设置FEC-Status为1，然后return。
根据上述的校验流程对目标FEC元素进行校验后，生成包括目标FEC元素校验结果的回显应答报文，然后将包含目标FEC元素校验结果的回显应答报文反馈给根节点。
步骤103，根据目标节点反馈的目标FEC元素的校验结果确定转发路径是否有效。
具体地说，目的节点根据目标FEC元素的校验结果生成回显应答报文后， 将包括目标FEC元素校验结果的回显应答报文反馈给路径的根节点，根节点根据目标节点反馈的目标FEC元素的校验结果，确定转发路径是否有效。
在一个例子中，根节点接收到回显应答报文后，根据报文中表示目标FEC元素检测结果的返回码取值确定目标FEC元素的校验结果，进而根据目标FEC元素的校验结果确定转发路径是否有效。
例如，收到的回显请求报文中，表示目标FEC元素校验结果的是返回码Best-return-code的取值，接收到的回显应答报文中Best-return-code的取值为12，根节点根据预先为Best-return-code不同取值分配的对应含义确定目标FEC元素的校验结果，查询后得知取值为12对应的结果为；FEC栈中当前元素没有与接口上的协议关联(Protocol not associated with interface at FEC-stack-depth)，则，根节点可以判定目标FEC元素校验失败，进而根节点根据目标FEC元素校验失败的结果确定转发路径为无效路径，并显示转发路径无效的检测结果。
由此，本实施方式提供了一种路径检测方法，通过在现有FEC元素中添加包括IGP算法信息的扩展字段，重新定义出包括IGP算法信息的FEC元素；在需要对IGP算法计算出的转发路径是否有效进行检测的时候，确定出包括转发路径所在网络拓扑平面对应的算法信息的待检测的目标FEC元素，并根据目标FEC元素的校验结果确定出转发路径是否有效，通过对FEC元素和路径检测协议的扩展，保证了能够对Flex-algo平面内的转发路径是否有效进行准确的检测。
本申请的第二实施方式涉及一种路径检测方法，第二实施方式与第一实施方式大致相同，在本实施方式中，算法字段中标识算法的算法取值可以是通过IANA(Internet Assigned Numbers Authority互联网数字分配机构)为算法分配的标准值，也可以是用户自定义的算法取值。通过IANA为部分算法分配标准取值，实现对常用的部分算法计算出的路径是否有效的检测；通过用户为算法自定义算法取值，实现对用户选定的算法计算出的路径是否有效的高效检测，路径检测过程中的具体的检测步骤可以参考第一实施方式。
步骤101，根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素。
具体地说，根节点根据网络拓扑平面对应的算法和转发路径与检测方式，确定出目标节点的目标FEC元素，目标FEC元素添加有包括IGP算法信息的扩展字段，其中，扩展字段中的IGP算法信息通过算法取值指示，其中，算法 取值包括由互联网数字分配机构IANA为算法分配的标准取值及由用户自定义的算法取值。
在一个例子中FEC元素添加的算法字段中算法的取值及含义如下：0～127：由IANA分配的标准取值，例如，0表示“SPF algorithm based on link metric”基于link metric的最短路径转发算法，1表示“Strict SPF algorithm based on link metric”基于link metric的严格最短路径转发算法；128-255：用于标识IGP Flex-algo，由用户自定义。例如，用户可创建Algorithm为128的Flex-algo平面或Algorithm为129的Flex-algo平面等。在实际应用中，可以根据实际情况或需要对算法取值的范围设置，本实施方式对算法取值的设置不做限制。
例如，根节点R1在如图6所示的网络拓扑中，针对分段路由架构下基于严格最短路径算法计算出的路径进行检测，IANA为严格最短路径算法分配的算法标准取值为1，在IPv4网络中采用ISIS作为SR-MPLS的控制面协议，ingress(起始)节点R1建立至egress(出口)节点R3的基于Strict SPF(严格最短路径)算法的SR LSP(分段路由标签交换路径)，网络中各节点均对外泛洪自身的Strict SPF Prefix-SID，并且通告Prefix-SID时携带的Algorithm信息,标准取值1。例如，R3节点为其loopback路由Prefix-R3分配的Strict SPF Prefix-SID为300，R1节点与R2节点学习到以后将建立至Prefix-R3的FTN与ILM转发表项，表项中包括的MPLS标签信息根据Prefix-SID 300参考现有技术生成。
根节点R1发起LSP ping SR-LSP Prefix-R3 Algorithm 1检测时，根据转发路径及路径的检测方式，将节点R3作为目标节点，根据转发路径所在的网络拓扑平面对应的算法，将IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-R3,Algorithm 1>作为目标FEC元素。
步骤102，将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点进行校验。
在一个例子中，根节点R1确定出目标FEC元素后，确定设置Echo request PDU：target FEC stack TLV：{IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-R3,Algorithm 1>}，然后封装IP/UDP头以及标签栈，栈顶标签为Prefix-SID 300对应的标签，标签TTL＝255，生成回显请求报文。在实际应用中，target FEC stack TLV中除了包含目标FEC元素外，还可以包含标签栈中其余标签对应的FEC元素。
生成回显请求报文后，将报文发送到R2节点，R2节点将报文透传到节点R3，R3接收到回显请求报文后，根据将回显请求报文上送控制面的条件对自身进行检测，R3检测到自身满足预设条件，将报文上送控制面。R3节点作为应答节点，对目标FEC元素进行校验，若控制平面检查发现标签值是有效的，存在Prefix-SID 300相应的ILM转发表项并且标签操作为POP；检查发现报文的标签栈与target FEC stack是一致的，即R3节点确实通过ISIS对外通告了IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-R3,Algorithm 1>且Prefix-SID为300，则判定FEC元素的校验结果为校验通过。R3节点根据目标FEC元素的校验结果构建echo reply报文，并在echo reply报文中包含校验成功的信息，将回显应答报文反馈给根节点R1。
步骤103，根据目标节点反馈的目标FEC元素的校验结果确定转发路径是否有效。根节点根据目标FEC元素的检验结果，确定出路径是否有效，并输出检测结果。
由此，本实施方式提供了一种路径检测方法，FEC元素的扩展字段中的算法取值包括IANA为特定算法分配的标准取值或用户自定义的算法取值，通过IANA为部分特定的算法分配标准值，使得对部分算法计算出的路径进行检测时，能够调用包括特定算法信息的目标FEC元素对转发路径是否有效进行准确的检测；通过用户自定义算法取值，可以直接在Flex-algo平面内进行自定义取值的算法计算出的转发路径的路径检测，保证了能够高效准确的确定用户选定的算法计算出的路径是否有效。
本申请的第三实施方式涉及一种路径检测方法，本实施方式和第一实施方式大致相似，在本实施方式中，通过根据Flex-algo平面对应的IGP算法，对相邻的链路进行标识，并生成相邻链路的包括算法信息的FEC元素，从而在IGP平面内，对业务或分段路由流量工程实例的路径是否有效进行检测，具体的检测步骤可以参考第一实施方式。
步骤101，根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素。
具体地说，根节点根据转发路径、路径所在网络拓扑平面及路径检测方式，确定需要进行检测的目标节点的目标FEC元素。
在一个例子中，需要进行网络拓扑中的SR-TE(Segment Routing Traffic  Engineering分段路由流量工程)路径进行LSPTraceroute检测，则根据SR-TE实例对应的分段列表(Segment List)，确定出相应的标识列表(SID List)，然后根据各分段对应的算法，确定出目标FEC元素。
例如，在如图7所示的网络拓扑中进行SR-TE实例路径的检测，在图7所示的网络拓扑中，在IPv4网络中采用ISIS作为SR-MPLS的控制面协议，创建两个Flex-algo平面，其中Flex-algo 128平面对应的Algorithm取值为128，Flex-algo 129平面对应的Algorithm取值为129。Flex-algo 128平面中包含节点S1、A、B、D以及这些节点间相连的双向链路。Flex-algo 129平面中包含节点S2、B、C、D以及这些节点间相连的双向链路。两个平面均使用IGPmetric(IGP度量值)计算最短路径，并且，链路link(B-D)的IGPmetric为100，其余链路的IGPmetric为10。
其中，节点B为其loopback路由Prefix-B分配的与Algorithm 128相关的Prefix-SID为1280。其它节点学习到以后将建立至Prefix-B的FTN与ILM转发表项，表项中包括的MPLS标签信息根据Prefix-SID 128按照现有技术生成，节点B为其本地的link(B-D)分配与算法128相关的Adjacency-SID(临接段标识)为1281，其它节点学习到以后将存储在本地的链路状态数据库中。
在节点S1上创建了Flex-algo 128平面内的SR-TE实例(记为sr-te-100)，则其Segment List为{Node-B,Link(B-D)}，相应的SID List为{1280,1281}。在S1节点上发起LSP traceroute sr-te-100后，S1节点作为根节点，将SR-TE中的第一段终节点B和第二段的临接段链路link(B-D)的终节点D作为目标节点，将节点B的FEC元素IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-B,Algorithm 128>与链路link(B-D)对应的FEC元素IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>作为目标FEC元素。
步骤102，将根据目标FEC元素生成的回显请求报文沿与算法相关的转发路径发送到目标节点，供目标节点进行校验。
具体地说，根节点确定目标FEC元素后，根据待检测的FEC元素构建回显请求报文，将待检测的FEC元素交由对应的目标节点进行校验。
在一个例子中，根节点S1确定出目标FEC元素后，设置Echo request PDU：target FEC stack TLV：{IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-B,Algorithm 128>,IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>}，将 DDMAPTLV包括在其中，然后封装IP/UDP头以及标签栈，栈顶标签为Prefix-SID 1280对应的标签，标签TTL＝1，然后根据在Flex-algo 128平面内至节点B的最短路径将报文传输到节点A。
节点A接收到回显请求报文后，因顶层标签TTL为1而导致将回显请求报文上送控制平面，A将作为Responder节点。若在控制平面，检查发现标签值是有效的，存在Prefix-SID 1280相应的ILM转发表项并且标签操作为SWAP；检查发现DDMAP TLV中的下一跳信息与报文到达的入接口是匹配的；检查发现报文的标签栈与target FEC stack是一致的，即A节点为IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-B,Algorithm 128>绑定的标签与报文的顶层标签一致，则判定校验成功。A节点向S1节点回复echo reply报文，在echo reply报文中包含校验成功的信息。
根节点S1根据接收到的echo reply报文，重新构造回显请求报文，目标FEC元素堆栈不变，将顶层标签TTL值设置为2，然后重新发送到A节点，因为顶层标签为2，A将TTL的值减1后直接将报文转发到节点B。
B节点在接收到回显请求报文后，由于顶层标签TTL为1，将报文上送控制平面进行检测，若控制平面检查发现标签值是有效的，存在Prefix-SID 1280相应的ILM转发表项并且标签操作为POP；检查发现报文的标签栈与target FEC stack是一致的，即B节点确实通过ISIS对外通告了IPv4 IGP-Prefix Segment ID per Algorithm＝<Prefix-B,Algorithm 128>且Prefix-SID为1280，则判定校验成功。
B节点向S1节点回复echo reply报文，在echo reply报文中包含校验成功的信息，并且包含FEC Stack Change TLV，提示根节点S1要弹出target FEC stack TLV中的IPv4 IGP-Prefix Segment ID per Algorithm Sub-TLV。
根节点S1接收到B节点包含FEC元素校验成功的回显应答报文后，调整回显请求报文中的部分数据，将target FEC stack TLV变为：target FEC stack TLV：{IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>}。顶层标签TTL设置为3。向下一跳节点A转发。
节点A接收到回显请求报文时，顶层标签TTL为3，将顶层标签TTL减1后，直接转发到节点B，节点B接收到回显请求报文后，顶层标签TTL为2，终结Prefix-SID 1280对应的标签，继续根据下层Adjacency-SID 1281对应的标 签查ILM表，将顶层标签减1后弹出标签，并将标签TTL拷贝的下层IP头中，然后将报文转发到节点D。
节点D接收到回显请求报文后，由于回显请求报文的目的IP处于127/8并且IP TTL为1，将回显请求报文上送控制平面，若在控制平面，检查发现IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>中包含的Remote Interface ID与报文到达的入接口是匹配的；检查发现IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>中包含的Receiving Node Identifier是本节点的Node-ID；检查维护的链路状态数据库发现IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>中包含的Advertising Node Identifier所表示的节点确实通告了该IGP-Adjacency Segment ID per Algorithm＝<link(B-D),128>，则判定校验成功。
D节点向S1节点回复echo reply报文，在echo reply报文中包含校验成功的信息，并且包含FEC Stack Change TLV，提示头节点要弹出target FEC stack TLV中的IGP-Adjacency Segment ID per Algorithm Sub-TLV。
值得一提的是，在路径检测过程中，若任一节点的检测中，目标FEC元素校验失败，则应答节点可以直接向根节点包括反馈校验失败的回显应答报文，并且终止后续的路径检测。
步骤103，根据目标节点反馈的目标FEC元素的校验结果确定转发路径是否有效。根节点根据FEC元素的检验结果，确定出路径是否有效，并输出检测结果。
由此，本实施方式提供了一种路径检测方法，通过根据创建的SR-TE实例所在网络拓扑平面、路径检测方式及转发路径，确定SR-TE实例中与算法相关的路径对应的目标FEC元素，根据目标FEC元素实现对SR-TE实例中的与算法相关的分段路径是否有效的检测。
本申请的第四实施方式涉及一种路径检测方法，包括：接收回显请求报文，回显请求报文包括待检测的目标节点的目标FEC元素；其中，目标FEC元素包括转发路径所在网络拓扑平面对应的内部网关协议IGP算法信息；对目标FEC元素进行校验，并生成包括目标FEC元素的校验结果的回显应答报文；向根节点反馈回显应答报文，供根节点根据目标FEC元素的校验结果确定转发路径是否有效。
本实施方式的路径检测方法具体流程如图8所示，具体包括以下步骤：
步骤801，接收回显请求报文。
具体地说，在进行转发路径是否有效的检测时，应答节点接收回显请求报文，回显请求报文包括待检测的目标节点的目标FEC元素，其中，目标FEC元素包括转发路径所在网络拓扑平面对应的内部网关协议IGP算法信息，根据接收到的回显请求报文，确定出要进行校验的目标FEC元素。
在一个例子中，IGP算法信息包括在目标FEC元素的扩展字段中。在实际应用中，扩展字段中的IGP算法信息通过由互联网数字分配机构IANA为算法分配的标准取值指示或通过由用户自定义的算法取值指示。
在另一例子中，添加扩展字段的FEC元素的类型包括：IPv4 IGP-Prefix Segment ID Sub-TLV、IPv6 IGP-Prefix Segment ID Sub-TLV或IGP-Adjacency Segment ID Sub-TLV。
步骤802，对回显请求报文包含的目标FEC元素进行校验，并生成包括目标FEC元素校验结果的回显应答报文。
具体的说，在根据接收到的回显请求报文确定出待检测的目标FEC元素后，应答节点对目标FEC元素进行校验，并根据目标FEC元素的校验结果，生成包括目标FEC元素校验结果的回显应答报文。
在一个例子中，应答节点进行目标FEC元素的校验时，大致上可以参考RFC8029的校验过程，为了保证能够对包括IGP算法的FEC元素的准确校验，应答节点对目标FEC元素进行校验时，根据目标FEC元素，确定IGP协议的类型，根据IGP协议的类型对目标FEC元素进行校验，即，先根据目标FEC元素中的protocol值，确定与算法相关路径创建时所采用的IGP协议的类型，根据IGP协议的类型确定对目标FEC元素与标签进行校验，在校验完成后，根据目标FEC元素的校验结果设置表示FEC元素校验结果的返回码取值，生成包含目标FEC元素校验结果的回显应答报文。
步骤803，向根节点反馈回显应答报文，供根节点根据目标FEC元素的校验结果确定转发路径是否有效。
具体地说，在应答节点生成包含目标FEC元素的校验结果的回显应答报文后，将回显应答报文反馈给转发路径的根节点，根节点根据回显应答报文中表示目标FEC元素校验结果的返回码取值，确定目标FEC元素的校验结果，进而 根据目标FEC元素的校验结果确定转发路径是否有效。
由此，本实施方式提供了一种路径检测方法，通过在现有FEC元素中添加包括IGP算法信息的扩展字段，实现对现有的路径检测协议的扩展，引入包括IGP算法信息的FEC元素；从而在针对IGP算法计算出的转发路径是否有效的检测中，根节点能够调用包括IGP算法信息的目标FEC元素发起路径检测，并且应答节点能够准确的对包含有IGP算法信息的目标FEC元素进行校验，并进行校验结果的反馈，根节点再根据目标FEC元素的校验结果确定转发路径是否有效，从而实现对IGP算法计算出的转发路径是否有效的准确高效检测。
本申请实施方式相对于现有技术而言，在需要进行Flex-algo平面内转发路径是否有效的检测时，根据Flex-algo平面对应的IGP算法及转发路径，确定待检测的目标节点，并调用目标节点与IGP算法相关的目标FEC元素，构建用于路径检测的回显请求报文，供目标节点进行目标FEC元素的校验，根据目标节点反馈的FEC元素校验结果，准确的确定出Flex-algo平面内的转发路径是否有效，通过扩展现有路径检测协议，预先构建包括IGP算法信息的FEC元素，从而在进行转发路径是否有效的检测时，能直接根据Flex-algo平面对应的算法，调用含有IGP算法信息的目标FEC元素进行路径检测，保证了能够对各Flex-algo平面内的转发路径是否有效进行准确的检测。
另外，IGP算法信息包括在目标FEC元素的扩展字段中，通过将IGP算法信息包含在扩展字段中，使得对Flex-algo平面内的路径进行检测时，能够直接调用包含了平面对应的算法信息的目标FEC元素，保证了能够对Flex-algo平面内的路径是否有效进行准确的检测。
另外，扩展字段中的IGP算法信息通过算法取值指示，其中，所述算法取值包括由互联网数字分配机构IANA为算法分配的标准取值及由用户自定义的算法取值，通过IANA为算法分配的标准取值，准确的标识出常用的算法，便于对常用IGP算法计算出的路径进行检测，通过用户为算法自定义算法取值，保证了能够对用户需要检测的算法计算出的转发路径进行检测。
另外，添加扩展字段的FEC元素的类型包括：IPv4 IGP-Prefix Segment ID Sub-TLV、IPv6 IGP-Prefix Segment ID Sub-TLV或IGP-Adjacency Segment ID Sub-TLV，使得本申请的实施方式具备广泛的应用场景。
另外，根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节 点的目标FEC元素，包括：确定转发路径的路径检测方式；若路径检测方式为LSP Ping检测，则将转发路径的终节点作为目标节点，得到目标FEC元素；若路径检测方式为LSP Traceroute检测，则将转发路径中的各航路节点均作为目标节点，得到目标FEC元素，通过根据路径检测方式确定目标节点，并将目标节点的FEC元素作为目标元素，保证了检测的效率的同时，保证路径检测结果的准确性。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请第五实施方式涉及一种电子设备，如图9所示，包括至少一个处理器901；以及，与至少一个处理器901通信连接的存储器902；其中，存储器902存储有可被至少一个处理器901执行的指令，指令被至少一个处理器901执行，以使至少一个处理器901能够执行上述的路径检测方法。
其中，存储器和处理器采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器和存储器的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器。
处理器负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器可以被用于存储处理器在执行操作时所使用的数据。
本申请第六实施方式涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor) 执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (10)

  1. 一种路径检测方法，包括：
    根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素；其中，所述目标FEC元素包括所述网络拓扑平面对应的内部网关协议IGP算法信息；
    将根据所述目标FEC元素生成的回显请求报文沿与算法相关的所述转发路径发送到所述目标节点，供所述目标节点对所述目标FEC元素进行校验；其中，所述回显请求报文包括所述目标FEC元素；
    根据所述目标节点反馈的所述目标FEC元素的校验结果，确定所述转发路径是否有效。
  2. 根据权利要求1所述的路径检测方法，其中，所述IGP算法信息包括在所述目标FEC元素的扩展字段中。
  3. 根据权利要求2所述的路径检测方法，其中，所述扩展字段中的IGP算法信息通过算法取值指示，其中，所述算法取值包括由互联网数字分配机构IANA为算法分配的标准取值及由用户自定义的算法取值。
  4. 根据权利要求2所述的路径检测方法，其中，添加所述扩展字段的FEC元素的类型包括：
    IPv4 IGP-Prefix Segment ID Sub-TLV、IPv6 IGP-Prefix Segment ID Sub-TLV或IGP-Adjacency Segment ID Sub-TLV。
  5. 根据权利要求1所述的路径检测方法，其中，所述根据网络拓扑平面中与算法相关的转发路径，确定待检测的目标节点的目标FEC元素，包括：
    确定所述转发路径的路径检测方式；
    若所述路径检测方式为LSP Ping检测，则将所述转发路径的终节点作为所述目标节点，得到所述目标FEC元素；
    若所述路径检测方式为LSP Traceroute检测，则将所述转发路径中的各航路节点均作为所述目标节点，得到所述目标FEC元素。
  6. 一种路径检测方法，包括：
    接收回显请求报文，所述回显请求报文包括待检测的目标节点的目标FEC元素；其中，所述目标FEC元素包括转发路径所在网络拓扑平面对应的内部网关协议IGP算法信息；
    对所述目标FEC元素进行校验，并生成包括所述目标FEC元素的校验结果的回显应答报文；
    向根节点反馈所述回显应答报文，供所述根节点根据所述目标FEC元素的校验结果确定所述转发路径是否有效。
  7. 根据权利要求6所述的路径检测方法，其中，所述IGP算法信息包括在所述目标FEC元素的扩展字段中。
  8. 根据权利要求6所述的路径检测方法，其中，所述对所述目标FEC元素进行校验，包括：
    根据所述目标FEC元素，确定IGP协议的类型；
    根据所述IGP协议的类型对所述目标FEC元素进行校验。
  9. 一种电子设备，，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至5中任一项所述的路径检测方法，或，能够执行如权利要求6至8中任一项所述的路径检测方法。
  10. 一种计算机可读存储介质，存储有计算机程序，其中，所述计算机程序被处理器执行时实现权利要求1至5中任一项所述的路径检测方法，或，实现权利要求6至8中任一项所述的路径检测方法。
PCT/CN2020/137304 2020-02-27 2020-12-17 一种路径检测方法、电子设备及存储介质 WO2021169516A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010123741.4A CN113315701A (zh) 2020-02-27 2020-02-27 一种路径检测方法、电子设备及存储介质
CN202010123741.4 2020-02-27

Publications (1)

Publication Number Publication Date
WO2021169516A1 true WO2021169516A1 (zh) 2021-09-02

Family

ID=77370793

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/137304 WO2021169516A1 (zh) 2020-02-27 2020-12-17 一种路径检测方法、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN113315701A (zh)
WO (1) WO2021169516A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205188B (zh) * 2021-12-08 2023-08-29 中盈优创资讯科技有限公司 一种基于srte时延优化的隧道调度方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102136995A (zh) * 2010-08-09 2011-07-27 华为技术有限公司 Mpls与mpls-tp之间oam转换的方法及装置
CN102404145A (zh) * 2011-11-17 2012-04-04 华为技术有限公司 多协议标签交换环网的检测方法、装置及系统
CN102571601A (zh) * 2012-02-13 2012-07-11 中兴通讯股份有限公司 一种保证双向转发检测可靠性的方法及标记交换路径设备
CN107147508A (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 故障检测方法及装置
US20180026880A1 (en) * 2016-07-21 2018-01-25 Cisco Technology, Inc. Target fec (forwarding equivalence class) stack based fec query in segment routing environments

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7463591B1 (en) * 2001-06-25 2008-12-09 Juniper Networks, Inc. Detecting data plane liveliness of a label-switched path
CN101729391B (zh) * 2008-10-23 2012-09-19 华为技术有限公司 获取链路汇聚组信息的方法、节点和系统
CN102217235B (zh) * 2011-04-20 2013-11-06 华为技术有限公司 一种lsp路径检验方法及检测系统
CN103297340B (zh) * 2013-06-07 2017-02-08 杭州华三通信技术有限公司 Mpls和bgp组网中的路由收敛方法和设备
CN105337785B (zh) * 2014-07-18 2018-10-02 华为技术有限公司 一种路径连通性检测方法及装置
CN107645401A (zh) * 2016-07-22 2018-01-30 中兴通讯股份有限公司 多协议标签交换的检测、处理方法、装置及系统
CN109120449B (zh) * 2018-08-28 2022-04-22 新华三技术有限公司 一种链路故障的检测方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102136995A (zh) * 2010-08-09 2011-07-27 华为技术有限公司 Mpls与mpls-tp之间oam转换的方法及装置
CN102404145A (zh) * 2011-11-17 2012-04-04 华为技术有限公司 多协议标签交换环网的检测方法、装置及系统
CN102571601A (zh) * 2012-02-13 2012-07-11 中兴通讯股份有限公司 一种保证双向转发检测可靠性的方法及标记交换路径设备
CN107147508A (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 故障检测方法及装置
US20180026880A1 (en) * 2016-07-21 2018-01-25 Cisco Technology, Inc. Target fec (forwarding equivalence class) stack based fec query in segment routing environments

Also Published As

Publication number Publication date
CN113315701A (zh) 2021-08-27

Similar Documents

Publication Publication Date Title
US10855574B2 (en) Method and network device for computing forwarding path
US9832127B2 (en) LSP ping/trace over MPLS networks using entropy labels
US10965590B2 (en) Packet processing method and router
US10581732B2 (en) Target FEC (forwarding equivalence class) stack based FEC query in segment routing environments
KR102397232B1 (ko) 네트워크에서의 패킷을 송신하기 위한 방법 및 노드
US11431633B2 (en) Label forwarding entry generation method and apparatus, packet sending method and apparatus, and device
EP2911350B1 (en) Neighbor-label distribution with label distribution protocol
JP6622922B2 (ja) ＤＳＣＰ（Ｄｉｆｆｅｒｅｎｔｉａｔｅｄ Ｓｅｒｖｉｃｅｓ Ｃｏｄｅ Ｐｏｉｎｔ）およびＥＣＮ（Ｅｘｐｌｉｃｉｔ Ｃｏｎｇｅｓｔｉｏｎ Ｎｏｔｉｆｉｃａｔｉｏｎ）をモニタリングするデータプレーンのための方法および装置
US9667517B2 (en) Method and apparatus for checking connection of bi-directional LSP
US10764175B1 (en) Validating resource isolation between network slices in a mobile network
US8971195B2 (en) Querying health of full-meshed forwarding planes
WO2021232906A1 (zh) 报文转发备份路径确定方法及相关设备
CN103297340A (zh) Mpls和bgp组网中的路由收敛方法和设备
CN114650242A (zh) 路径故障检测方法、装置、相关设备及存储介质
US20210258242A1 (en) Loop detection in multiprotocol label switching
WO2021169516A1 (zh) 一种路径检测方法、电子设备及存储介质
US11165695B1 (en) Identifying egress of nil forward equivalency class (FEC) used for FEC hiding
CN114342334B (zh) 用于标签交换路径路由跟踪的方法和网络节点
CN110881006B (zh) 发送报文的方法、网络设备及计算机存储介质
CN113709033A (zh) 用于分段路由流量工程的分段跟踪路由
WO2022266905A1 (zh) 一种转发路径生成方法、装置、网络设备及存储介质
TW202029701A (zh) 通信鏈路檢查方法
WO2023173989A1 (zh) 转发表的生成方法及装置、存储介质、电子装置
WO2023030141A1 (zh) 探测公网转发设备的方法、公网转发设备和存储介质
WO2024001324A1 (zh) 网络路径的检测方法、系统及计算机设备

Legal Events

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

Ref document number: 20921275

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20921275

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21/02/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20921275

Country of ref document: EP

Kind code of ref document: A1