Tunnel detection method and network device

Abstract

The present application provides a tunnel detection method and network device, which is applied to a first network element in an MPLS network. The method includes: obtaining a pre-stored first tunnel operation parameter of the target tunnel according to a test instruction for the target tunnel, generating a first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter, generating an MPLS probe request message according to the first tunnel detection parameter, and sending an MPLS probe request message to a second network element through the target tunnel, so that the second network element performs a tunnel connectivity test on the target tunnel based on the MPLS probe request message, and when the tunnel connectivity test passes, extracting the first tunnel detection parameter from the MPLS probe request message to perform a parameter consistency test, and obtaining an MPLS probe response message returned by the second network element. By performing tunnel connectivity test and parameter consistency test, data plane connectivity test and control plane operation consistency test are achieved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a tunnel detection method and network equipment. Background Art

[0002] The Segment Routing Transport Profile (SR-TP) Label Switched Path (LSP) introduces the protocol-defined path segment identifier (SID) label. This adds a path label to the SR Multiple Protocols Label Switching (MPLS) label stack, providing SR-TP tunnels with operations, administration, and maintenance (OAM) functions similar to those of MPLS-TP.

[0003] In related technologies, since SR-TP LSPs are a type of MPLS LSP, LSP data plane connectivity can be checked using LSP ping or traceroute based on the protocol mechanism. However, the current protocol mechanism lacks consistency checking for control plane operations. Summary of the Invention

[0004] In view of this, an embodiment of the present application provides a tunnel detection method and a network device to perform parameter operation status detection while performing tunnel connectivity detection, thereby realizing data plane tunnel connectivity detection and control plane operation consistency detection.

[0005] In a first aspect, an embodiment of the present application provides a tunnel detection method, applied to a first network element in a multipath label switching (MPLS) network, the method comprising:

[0006] Obtaining, according to a test instruction for a target tunnel, a pre-stored first tunnel operating parameter of the target tunnel, wherein the target tunnel is any segment of a Routing Transport Protocol (SR-TP) tunnel starting from the first network element;

[0007] generating a first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter;

[0008] generating an MPLS probe request message for the target tunnel according to the first tunnel detection parameter;

[0009] Sending the MPLS probe request message to a second network element serving as an end point of the target tunnel through the target tunnel, so that the second network element performs a tunnel connectivity test on the target tunnel based on the MPLS probe request message, and extracting the first tunnel detection parameter from the MPLS probe request message to perform a parameter consistency test when the tunnel connectivity test passes;

[0010] Obtain an MPLS probe response message for the target tunnel returned by the second network element.

[0011] In an optional embodiment, the first tunnel operation parameter includes: path segment identifier SID label information of the label switched path LSP of the target tunnel;

[0012] Generating the first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter includes:

[0013] Generating a first detection parameter of the target tunnel according to the path SID label information of the LSP;

[0014] The generating, according to the first tunnel detection parameter, an MPLS probe request message for the target tunnel includes:

[0015] Acquire path SID label information of the adjacent segment link on the target tunnel according to the path SID label information of the LSP;

[0016] Carrying the path SID label information of the adjacent segment link and the path SID label information of the LSP in the label stack of the MPLS probe request message;

[0017] The first detection parameter is carried in a first subfield newly added in a target forwarding equivalence class (FEC) stack of the MPLS probe request message.

[0018] In an optional embodiment, the first tunnel operation parameter includes: bidirectional tunnel association group information and protection tunnel association group information of the target tunnel;

[0019] Generating the first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter includes:

[0020] generating a second detection parameter and a third detection parameter of the target tunnel respectively according to the bidirectional tunnel association group information and the protection tunnel association group information;

[0021] The generating, according to the first tunnel detection parameter, an MPLS probe request message for the target tunnel includes:

[0022] Carrying the second detection parameter in a second subfield newly added in the PCEP signaling of the MPLS probe request message;

[0023] The third detection parameter is carried in a third subfield newly added in the PCEP signaling of the MPLS probe request message.

[0024] In an optional embodiment, the first detection parameter includes: type information of the first subfield, a first byte length, address information of the first network element, address information of the second network element, a protocol type of the path SID label information of the LSP, and a first flag bit, where the first byte length is the sum of the byte length of the type information of the first subfield and the byte length of the path SID label information of the LSP, and the first flag bit is used to indicate the global-local attributes and allocation object of the path SID label information of the LSP;

[0025] The step of carrying the first detection parameter in a first subfield newly added in the target FEC stack of the MPLS probe request message includes:

[0026] Carrying the type information of the first subfield in the first byte to the second byte of the first subfield;

[0027] Carrying the first byte length in the third byte to the fourth byte of the first subfield;

[0028] Carrying the address information of the first network element in the fifth to eighth bytes of the first subfield;

[0029] Carrying the address information of the second network element in the ninth to twelfth bytes of the first subfield;

[0030] Carrying the protocol type of the path SID label information of the LSP in the thirteenth byte of the first subfield;

[0031] The first flag bit is carried in the fourteenth byte of the first subfield.

[0032] In an optional embodiment, the second detection parameter includes: an association group type corresponding to the bidirectional tunnel association group information, a second byte length, address information of the first network element, global identification information of the bidirectional tunnel association group information, and a second flag bit, where the second byte length is the sum of a byte length of the association group type corresponding to the bidirectional tunnel association group information and a byte length of the bidirectional tunnel association group information, and the second flag bit is used to indicate a tunnel direction corresponding to the bidirectional tunnel association group information and whether the tunnel is co-path.

[0033] The carrying of the second detection parameter in a second subfield newly added in the PCEP signaling of the MPLS probe request message includes:

[0034] Carrying the association group type corresponding to the bidirectional tunnel association group information in the first byte to the second byte of the second subfield;

[0035] Carrying the second byte length in the third byte to the fourth byte of the second subfield;

[0036] Carrying the address information of the first network element in the fifth to eighth bytes of the second subfield;

[0037] Carrying the global identification information of the bidirectional tunnel association group information in the ninth to tenth bytes of the second subfield;

[0038] The second flag bit is carried in the eleventh byte to the twelfth byte of the second subfield.

[0039] In an optional embodiment, the third detection parameter includes: an association group type corresponding to the protection tunnel association group information, a third byte length, address information of the first network element, global identification information of the protection tunnel association group information, and a third flag bit, where the third byte length is the sum of the byte length of the association group type corresponding to the protection tunnel association group information and the byte length of the protection tunnel association group information, and the third flag bit is used to indicate the tunnel master / slave status and protection type corresponding to the protection tunnel association group information;

[0040] The step of carrying the third detection parameter in a third subfield newly added in the PCEP signaling of the MPLS probe request message includes:

[0041] Carrying the association group type corresponding to the protection tunnel association group information in the first byte to the second byte of the third subfield;

[0042] Carrying the third byte length in the third byte to the fourth byte of the third subfield;

[0043] Carrying the address information of the first network element in the fifth to eighth bytes of the third subfield;

[0044] Carrying the global identification information of the protection tunnel association group information in the ninth byte to the tenth byte of the third subfield;

[0045] The third flag bit is carried in the eleventh byte to the twelfth byte of the third subfield.

[0046] In an optional implementation manner, obtaining the MPLS probe response message for the target tunnel returned by the second network element includes:

[0047] Obtaining the MPLS probe response message returned by the second network element through the address information of the first network element; or,

[0048] The MPLS probe response message returned by the second network element is obtained through the reverse tunnel corresponding to the target tunnel.

[0049] In a second aspect, an embodiment of the present application further provides a tunnel detection method, which is applied to a second network element in a multipath label switching (MPLS) network. The method includes:

[0050] Receiving an MPLS probe request message sent by a first network element through a target tunnel, and obtaining a reception result of the MPLS probe request message; the MPLS probe request message is generated according to a first tunnel detection parameter of the target tunnel, and the first tunnel detection parameter is generated based on a first tunnel operation parameter of the target tunnel pre-stored by the first network element;

[0051] Performing tunnel connectivity detection on the target tunnel based on a result of receiving the MPLS probe request message;

[0052] When the tunnel connectivity test passes, extracting the first tunnel detection parameter from the MPLS detection request message;

[0053] Acquiring a second tunnel detection parameter of the target tunnel according to a pre-stored second tunnel operation parameter;

[0054] Performing parameter consistency detection based on the first tunnel detection parameter and the second tunnel detection parameter to obtain a detection result;

[0055] An MPLS probe response message for the target tunnel is generated according to the detection result, and the MPLS probe response message is returned to the first network element.

[0056] In an optional implementation, generating an MPLS probe response message for the target tunnel according to the detection result includes:

[0057] The detection result is carried in the message header of the MPLS probe response message.

[0058] In a third aspect, an embodiment of the present application further provides a network device comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the network device is running, the processor communicates with the memory through the bus, and the processor executes the machine-readable instructions to execute the method described in any one of the first and second aspects.

[0059] The present application provides a tunnel detection method and network device, which is applied to a first network element in an MPLS network. The method includes: obtaining a pre-stored first tunnel operation parameter of the target tunnel according to a test instruction for the target tunnel, generating a first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter, generating an MPLS probe request message according to the first tunnel detection parameter, and sending an MPLS probe request message to a second network element through the target tunnel, so that the second network element performs a tunnel connectivity test on the target tunnel based on the MPLS probe request message, and when the tunnel connectivity test passes, extracting the first tunnel detection parameter from the MPLS probe request message to perform parameter consistency test, and obtaining an MPLS probe response message returned by the second network element. By performing tunnel connectivity test and parameter consistency test, data plane connectivity test and control plane operation consistency test are achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0061] Figure 1 A schematic diagram of the structure of the SR-TP tunnel path calculation network provided in an embodiment of the present application;

[0062] Figure 2 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 1 ;

[0063] Figure 3 A schematic diagram of a target tunnel provided in an embodiment of the present application;

[0064] Figure 4 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 2 ;

[0065] Figure 5 A schematic diagram of the MPLS probe request message structure provided in an embodiment of the present application;

[0066] Figure 6Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 3 ;

[0067] Figure 7 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 4 ;

[0068] Figure 8 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 5 ;

[0069] Figure 9 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 6 ;

[0070] Figure 10 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 7 ;

[0071] Figure 11 A schematic diagram of the MPLS probe response message structure provided in an embodiment of the present application;

[0072] Figure 12 A schematic diagram of the structure of the network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of this application.

[0074] Before introducing the technical solution of this application, the relevant terms involved in this application are first explained:

[0075] Segment Routing (SR) and Multiple Protocols Label Switching (MPLS) are extensions of traditional MPLS that enable segment routing in MPLS networks. SR is achieved through the use of Segment Identifiers (SIDs), which are unique identifiers associated with each node or link in a path. SR MPLS is a combination of SR and MPLS, using MPLS as the foundation for packet forwarding and SR for flexible path selection. SR MPLS can be used to implement various network functions, including traffic engineering, load balancing, and fault protection.

[0076] Segment Routing Transport Profile (SR-TP) is a variant of SR MPLS specifically designed for traffic engineering in packet networks. SR-TP uses SR labels to mark packets and SR routers to forward them. SR-TP implements various traffic engineering functions, including traffic classification, traffic prioritization, traffic load balancing, and traffic failover. SR-TP has been adopted by many network operators and is becoming the standard technology for traffic engineering in packet networks.

[0077] SR-TP's ping and traceroute features leverage and enhance IP network ping and traceroute technologies, testing the connectivity of Label Switched Path (LSP) tunnels by sending MPLS probe frames. Ping is a widely used network tool for testing connectivity between hosts and measuring round-trip latency. It works by sending Internet Control Message Protocol (ICMP) echo request packets to the destination host and waiting for echo replies. Traceroute is a network diagnostic tool that displays information about the path from a source host to a destination host. It does this by sending packets with increasing Time to Live (TTL) values and recording the ICMP Time Exceeded messages returned by each intermediate router, gradually revealing the nodes a packet traverses.

[0078] SR-TP LSPs introduce the protocol-defined path segment identifier (SID) label and add a path label to the SR MPLS label stack, providing MPLS-TP-like operations, administration, and maintenance (OAM) functions for SR-TP tunnels. Because SR-TP LSPs are a type of MPLS LSP, data plane connectivity can be verified using LSP ping or traceroute based on the protocol mechanism.

[0079] It is worth noting that the ping and traceroute processing process and message structure of SR-TP LSP are similar to those of Segment Routing Traffic Engineering (SR-TE), except that a path label is added to the tunnel payload.

[0080] SR-TP LSPs can be created in two ways: static manual configuration and dynamic protocol configuration. In the static manual configuration method, the SR-TP LSP path expressed in the segment list, the path SID label, the MPLS bidirectional tunnel consisting of forward and reverse LSPs, and the SR-TP LSP automatic protection switching group (APS group) consisting of the primary (working) LSP and the backup LSP are all manually created through the Command Line Interface (CLI) or the Network Configuration Protocol (NETCONF).

[0081] In dynamic protocol configuration, using the Path Computation Element Communication Protocol (PCEP) as an example, network elements (NEs) run the PCEP client function and obtain information about SR-TP tunnels, bidirectional tunnel association groups, and protection tunnel association groups automatically calculated by the Path Computation Element (PCE) server through PCEP. PCEP is a dynamic control protocol for path calculation. To achieve better network control, NEs and PCE servers can support PCEP and use it to deliver centralized path calculation results to NEs in real time. A protection tunnel association group is also known as an Automatic Protection Switching (APS) association group.

[0082] It is understandable that the dynamic management protocol of the SR-TP tunnel may be PCEP, or other protocols such as Border Gateway Protocol (BGP) that can dynamically configure SR-TP between the network element and the server.

[0083] The following combination Figure 1 Taking PCEP dynamic signaling as an example, the network application process of automatically creating and managing SR-TP tunnels through PCEP dynamic signaling is illustrated.

[0084] Figure 1 A schematic diagram of the structure of the SR-TP tunnel path calculation network provided in the embodiment of the present application is shown as follows: Figure 1 As shown in the figure, in a network where PCEP dynamic signaling SR-TP tunnels are deployed, users can configure the SR-TP tunnel from node A (network element) to node Z (network element) to be hosted by the PCE in the management and control system. This automatically calculates the SR-TP tunnel and its bidirectional tunnel association group and APS protection association group.

[0085] After the PCE calculates the tunnel path based on the topology information obtained from the network, it sends it to the relevant nodes of the network through the PCEP protocol, such as nodes A and Z above. When the network topology changes, the network element can send a new path calculation request to the PCE to update the SR-TP tunnel.

[0086] For example, when Tunnel 1 fails, the OAM alarm on node A triggers the policy and the Path Computing Client (PCC) initiates a path calculation request using a Path Computation Request (PCReq) message. The PCE calculates the path and responds to the PCC to create a new Tunnel 2.

[0087] It's worth noting that PCEP-based dynamic SR-TP management involves coordinated protocol operations across multiple network elements (NEs), resulting in a complex protocol flow. Furthermore, different vendors have subtle differences in their implementation of SR-TP dynamic management (i.e., different NEs implement inconsistent protocol states). Often, failures in SR-TP tunnel delegation networks based on dynamic signaling stem from protocol operations rather than equipment failures.

[0088] The current protocol mechanism lacks consistency checks on the control plane. The control plane maintains routing information, topology, and network status through various control protocols and passes this information to the data plane to guide packet forwarding. In other words, after the PCE server transmits the calculated information to different network elements, the current tunnel detection Ping protocol cannot perform parameter consistency checks on the information received by different network elements. This makes the deployment and operation and maintenance management of PCEP dynamic instruction SR-TP tunnels very difficult.

[0089] To enhance the maintainability and manageability of the network, this application proposes an SR-TP tunnel protocol verification scheme based on the MPLS LSP ping architecture, which realizes data plane connectivity detection and control plane operation consistency detection through tunnel connectivity detection and parameter consistency detection.

[0090] Figure 2 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 1 , the method is applied to a first network element in a multipath label switching MPLS network.

[0091] Among them, the network elements in the MPLS network can be 5G transport network equipment or other network equipment that supports SR-TP tunnels, including routers, switches, packet transport network (PTN), optical transport network (OTN) equipment, status monitoring firewall equipment, virtual private network (VPN) gateway equipment, etc.

[0092] like Figure 2 As shown, the method may include:

[0093] S101: Acquire a pre-stored first tunnel operation parameter of a target tunnel according to a test instruction for the target tunnel.

[0094] The target tunnel may be any SR-TP tunnel in the MPLS network, the test instruction for the target tunnel may be a ping instruction, and the first network element may be any network element in the target tunnel, such as the tunnel starting point network element (such as Figure 1 A node in ).

[0095] A test instruction for the target tunnel is input, and according to the test instruction, a pre-stored first tunnel operation parameter and a connectivity detection parameter of the target tunnel are obtained, wherein the pre-stored first tunnel operation parameter may be a tunnel operation parameter that the PCE pre-delivers to the first network element through a protocol, wherein the PCE calculates the tunnel operation parameter between the first network element and the second network element and may deliver it to the first network element and the second network element, wherein the second network element may be a network element other than the first network element in the target tunnel, such as a tunnel endpoint network element (such as Figure 1 Z node in ).

[0096] The first tunnel operation parameter may include at least one of: path segment identifier SID label information of the label switched path LSP of the target tunnel, bidirectional tunnel association group information, and protection tunnel association group information.

[0097] The SR-TP LSP Path SID Label information of the target tunnel LSP is used to indicate the path label of the target tunnel.

[0098] The bidirectional tunnel association group information is used to indicate the first tunnel with the same source and destination as the target tunnel for reverse transmission. The tunnel starting network element of the first tunnel can be the second network element, the tunnel ending network element of the first tunnel can be the first network element, and the target tunnel and the first tunnel are in a reverse relationship.

[0099] The protection tunnel association group information is used to indicate a second tunnel with the same source and destination as the target tunnel and performs unidirectional transmission. The tunnel starting network element of the second tunnel can be the first network element, and the tunnel ending network element of the second tunnel can be the second network element. The target tunnel and the second tunnel are in a primary-backup relationship.

[0100] S102: Generate first tunnel detection parameters of the target tunnel according to the first tunnel operation parameters.

[0101] The first network element generates a first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter, wherein the first tunnel detection parameter is a parameter generated based on the first tunnel operation parameter and provided to the second network element for parameter consistency detection.

[0102] S103: Generate an MPLS detection request message for the target tunnel according to the first tunnel detection parameter.

[0103] An MPLS probe request message for the target tunnel is generated according to the first tunnel detection parameter, wherein the MPLS probe request message carries the first tunnel detection parameter. The MPLS probe request message is also an MPLS Echo Request message.

[0104] In some embodiments, when a user configures a command to initiate a ping for a target tunnel, the network element operating system of the first network element may query the first tunnel operating parameters of the target tunnel pre-stored in the routing protocol or PCEP protocol module, and construct an MPLS Echo Request message, which is sent to the hardware data plane of the second network element via the hardware data plane of the first network element. The hardware data plane may be, for example, an application-specific integrated circuit (ASIC) chip or other hardware platform that supports the SR-TP tunnel mechanism, such as a network processor (NP), a field-programmable gate array (FPGA), a programmable switching chip, etc.

[0105] S104. Send an MPLS probe request message to the second network element serving as the end point of the target tunnel through the target tunnel, so that the second network element performs a tunnel connectivity test on the target tunnel based on the MPLS probe request message, and extracts a first tunnel detection parameter from the MPLS probe request message to perform a parameter consistency test when the tunnel connectivity test passes.

[0106] The second network element is the tunnel endpoint network element of the target tunnel, that is, as the endpoint of the target tunnel, the MLPS detection request message is sent to the second network element in sequence through the tunnel intermediate network elements on the target tunnel. The second network element receives the MPLS detection request message through the target tunnel and obtains the reception result of the MPLS detection request message. If the reception result indicates that the MPLS detection request message is successfully received, it is determined that the tunnel connectivity test of the target tunnel has passed. If the reception result indicates that the MPLS detection request message cannot be received, it is determined that the tunnel connectivity test of the target tunnel has failed.

[0107] When the tunnel connectivity test passes, the second network element extracts the first tunnel detection from the MPLS detection request message and obtains the pre-stored second tunnel operation parameters of the target tunnel. The second tunnel operation parameters are the tunnel operation parameters that the PCE pre-sends to the second network element through the protocol. The second network element generates the second tunnel detection parameters of the target tunnel according to the second tunnel operation parameters. The second tunnel detection parameters are generated based on the second tunnel operation parameters and are used to provide the parameters for parameter consistency detection to the second network element. The second network element performs parameter consistency detection based on the second tunnel detection parameters and the first tunnel detection parameters. If the second tunnel detection parameters are consistent with the first tunnel detection parameters, it means that the first tunnel operation parameters and the second tunnel operation parameters are consistent. If the second tunnel detection parameters are consistent with the first tunnel detection parameters, it means that the first tunnel operation parameters and the second tunnel operation parameters are inconsistent.

[0108] It is worth noting that parameter consistency detection can be understood as parameter consistency detection of tunnel operation parameters delivered to network elements through protocols, that is, parameter consistency detection of protocol allocation results (or protocol operation status).

[0109] S105: Obtain an MPLS probe response message for the target tunnel returned by the second network element.

[0110] The second network element performs a parameter consistency check on the first tunnel detection parameter to obtain a detection result, and generates an MPLS probe response message for the target tunnel based on the detection result. The MPLS probe response message carries the detection result. The second network element may return the MPLS probe response message to the first network element, so that the first network element can extract the detection results of the first network element and the second network element regarding the operating status of the tunnel operating parameters from the MPLS probe response message.

[0111] In some embodiments, when the hardware data plane of the second network element identifies that the local machine is the destination node of the MPLS Echo Request message, it extracts the MPLS Echo Request message from the first network element from the hardware data plane to the operating system control plane of the central processing unit (CPU). The operating system control plane of the CPU queries the second tunnel operating parameters of the target tunnel pre-saved in the routing protocol or PCEP protocol module, performs parameter consistency detection, constructs an MPLS probe response (MPLS Echo Reply) message based on the detection results, and sends it to the first network element through the hardware data plane.

[0112] For the first network element, after the hardware data plane of the first network element identifies that the local machine is the destination node of the MPLS Echo Reply message, it extracts the MPLS Echo Reply message from the second network element to the CPU's operating system control plane. The CPU's operating system control plane obtains the parameter consistency test result by parsing the test result carried in the MPLS Echo Reply message.

[0113] It is worth noting that if the tunnel operation information includes bidirectional tunnel association group information, the second network element can also perform reverse parameter consistency detection, that is, the second network element, as the first network element, constructs an MPLS Echo Request message based on the second tunnel detection parameter, and sends an MPLS Echo Request message to the first network element, so that the first network element performs tunnel connectivity detection on the target tunnel based on the MPLS probe request message, and when the tunnel connectivity detection passes, extracts the second tunnel detection parameter from the MPLS probe request message to perform parameter consistency detection. Since the user does not input the test instruction through the second network element, the first network element can also feed back the test results to the preset control system or push them to the first network element, thereby realizing bidirectional parameter consistency detection and improving detection accuracy. Among them, the preset control system can be deployed on the PCE server side.

[0114] In an optional implementation, the above step S105 of obtaining the MPLS probe response message for the target tunnel returned by the second network element includes:

[0115] Obtaining the MPLS probe response message returned by the second network element through the address information of the first network element; or,

[0116] The MPLS probe response message returned by the second network element is obtained through the reverse tunnel corresponding to the target tunnel.

[0117] The test instruction for the target tunnel also includes the return path of the MPLS Echo Reply message, such as the Internet Protocol Address (IP) of the first network element or information about the first tunnel in the bidirectional tunnel association group that has the same source and destination as the target tunnel and performs reverse transmission. The first tunnel is the reverse tunnel corresponding to the target tunnel.

[0118] The first network element can generate an MPLS probe request message based on the return path information and the first tunnel detection parameters. After the second network element extracts the return path from the MPLS probe request message, if the return path is the address information of the first network element, the second network element returns an MPLS probe response message to the first network element through the address information. The first network element obtains the MPLS probe response message returned by the second network element through the address information of the first network element.

[0119] If the return path is the information of the first tunnel in the bidirectional tunnel association group that has the same source and destination as the target tunnel and performs reverse transmission, the second network element can return the MPLS probe response message to the second network element through the reverse tunnel, and the first network element obtains the MPLS probe response message returned by the second network element through the reverse tunnel corresponding to the target tunnel.

[0120] In this embodiment, the user initiates a test instruction for the target tunnel on the tunnel starting point network element of the target tunnel to detect tunnel connectivity and parameter consistency, implement data plane connectivity detection and control plane operation consistency detection, and timely perceive the network and operation status through the return message, and perform fault location processing through the information carried in the return message when a fault occurs.

[0121] It is worth noting that in this solution, the MPLS LSP for protocol verification via the test command can be an SR-TPLSP, an SR-TE LSP, an MPLS-TP LSP, an LDP LSP, etc. Except for the allocation of path SID label information for the LSP without the target tunnel, the allocation of bidirectional tunnel association groups and protection tunnel association groups is consistent.

[0122] In an optional implementation manner, the first tunnel operation parameter includes: path segment identifier SID label information of a label switched path LSP of the target tunnel.

[0123] Figure 3 A schematic diagram of a target tunnel provided in an embodiment of the present application is shown in FIG. Figure 3 As shown in FIG, the starting point NE of the target tunnel is NE1, the intermediate NEs of the tunnel are NE2, NE3, NE4, and NE5, and the terminal NE of the tunnel is NE6.

[0124] Adjacency segment links are links between two adjacent NEs on the target tunnel, including the NE1 to NE2 link, the NE2 to NE3 link, the NE3 to NE4 link, the NE4 to NE5 link, and the NE5 to NE6 link. The path SID label information for the adjacency segment links is as follows:

[0125] 912 -->Adjacency Segment ID from NE1 to NE2.

[0126] 923 -->Adjacency Segment ID from NE2 to NE3;

[0127] 934 -->Adjacency Segment ID from NE3 to NE4;

[0128] 945 -->Adjacency segment ID from NE4 to NE5;

[0129] 956 -->Adjacency segment ID from NE5 to NE6;

[0130] The path SID label information of the LSP is:

[0131] 600-->Path SID of SR-TP LSP{912,923,934,945,956} on NE6.

[0132] In some embodiments, a test instruction for the target tunnel is generated based on the path SID label information of the adjacent segment link on the target tunnel and the path SID label information of the LSP. Taking the first network element as NE1 as an example, the test instruction for the target tunnel can be an instruction to ping SR-TP LSP {912,923,934,945,956,600} from NE1.

[0133] Figure 4 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 2 ,like Figure 4 As shown, in an optional embodiment, the above step S102, generating the first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter, may include:

[0134] S201: Generate a first detection parameter of a target tunnel according to the path SID label information of the LSP.

[0135] According to the path SID label information of the LSP of the target tunnel, the first detection parameter of the target tunnel is generated. The first tunnel detection parameter includes: a first detection parameter, which is generated based on the path SID label information of the LSP and is used to provide a parameter to the second network element for parameter consistency detection.

[0136] The above step S103, generating an MPLS probe request message for the target tunnel according to the first tunnel detection parameter, may include:

[0137] S202: Obtain path SID label information of the adjacent segment link on the target tunnel according to the path SID label information of the LSP.

[0138] The path SID label information of the LSP includes the path SID label information of the adjacent segment link on the target tunnel. Therefore, the path SID label information of the adjacent segment link can be determined from the path SID label information of the LSP.

[0139] The SID label of an SR-TP LSP is composed of multiple adjacent link SIDs and the LSP's path SID label information. For example, if the path SID label information of an LSP is 600 --> Path SID of SR-TP LSP{912,923,934,945,956} on NE6, the path SID labels of the adjacent link segments are determined to be 912, 923, 934, 945, and 956. 912, 923, 934, 945, and 956 represent the SID label information of the link from NE1 to NE2, the link from NE2 to NE3, the link from NE3 to NE4, the link from NE4 to NE5, and the link from NE5 to NE6, respectively.

[0140] S203: Carry the path SID label information of the adjacent segment link and the path SID label information of the LSP into the label stack of the MPLS probe request message.

[0141] The label stack of the MPLS probe request message is also called an MPLS label stack, which carries the path SID label information of the adjacent link segment and the path SID label information of the LSP in the label stack of the MPLS probe request message.

[0142] It is worth noting that the MPLS probe request message is forwarded according to the label stack. Every time it passes through an intermediate network element in a tunnel, the outermost SID label information is popped out and the message is forwarded to the next intermediate network element in the tunnel. Based on the standard protocol mechanism, the SID label information of the first adjacent link in the SID label information of the adjacent link can be deleted, and the path SID label information of the non-first adjacent segment link and the path SID label information of the LSP can be carried in the label stack of the MPLS probe request message.

[0143] In addition, based on the current protocol mechanism, the TTL (Time To Live) value can be set based on the path SID label information of non-first adjacent links and the path SID label information of the LSP. The TTL is the maximum number of routers (network elements) that a network packet can pass through during transmission. For example, if the TTL is set to 255, the TTL value is reduced by 1 after each router it passes through. When the TTL value reaches 0, the packet is discarded. When the outermost SID label information is popped out, the TTL value after 1 is assigned to the exposed outermost TTL. For details, refer to the existing protocol.

[0144] Figure 5 A schematic diagram of the MPLS probe request message structure provided in an embodiment of the present application is shown as follows: Figure 5 As shown in FIG. 1 , the label stack carries the path SID label information of the label adjacency link, the path SID label information of the LSP, and the TTL (such as 255).

[0145] S204: Carry the first detection parameter into a first subfield newly added in the target forwarding equivalence class FEC stack of the MPLS probe request message.

[0146] A first subfield is added to the target FEC stack, and the first detection parameter is carried in the first subfield, wherein the first subfield may be a TLV field, namely, SR-TP Path SID sub-TLV. Figure 5 , a new first subfield in the target FEC stack.

[0147] The Target FEC Stack (FEC) stands for Forwarding Equivalence Class. The Target FEC TLV field is a TLV field used to identify the target FEC stack. TLV (Type-Length-Value) is a coding standard widely used in electronic communications and data storage. Its basic structure consists of three parts: Type, Length, and Value. The first subfield exists in the target FEC stack as the payload.

[0148] This embodiment facilitates the forwarding of the MPLS probe request message by carrying the path SID label information of the adjacent segment link and the path SID label information of the LSP in the label stack of the MPLS probe request message. The first detection parameter is carried in the newly added first subfield in the target FEC stack of the MPLS probe request message. By adding the first subfield, the second network element can perform parameter consistency verification on the path SID label information of the dynamically automatically allocated LSP based on the first detection parameter through a test instruction, so as to verify the protocol of the dynamically allocated first tunnel operation parameter. The dynamic allocation scheme of the first tunnel operation parameter is flexible and involves complex protocol operations on multiple network elements and the PCE controller end. The allocation result of the first tunnel operation parameter can be verified through the test instruction, which facilitates the location and subsequent maintenance of protocol problems during automatic deployment after tunnel hosting.

[0149] In an optional implementation manner, the first tunnel operation parameter includes: bidirectional tunnel association group information and protection tunnel association group information of the target tunnel.

[0150] When the managed SR-TP is configured as a bidirectional tunnel, the PCE server automatically calculates the two tunnels in the forward and reverse directions (the target tunnel and the first tunnel), creates an association group, and sends it to the first and second NEs of the target tunnel.

[0151] When the managed SR-TP is configured as a protection tunnel association group consisting of primary and backup tunnels, the PCE server automatically calculates two tunnels in the same direction (the target tunnel and the second tunnel) and creates a bidirectional tunnel association group with one primary and one backup. The group is then sent to the first and second NEs of the target tunnel.

[0152] Figure 6 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 3 ,like Figure 6 As shown, in an optional embodiment, the above step S102, generating the first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter, may include:

[0153] S301: Generate a second detection parameter and a third detection parameter of a target tunnel according to bidirectional tunnel association group information and protection tunnel association group information.

[0154] According to the bidirectional tunnel association group information, a second detection parameter of the target tunnel is generated, and according to the protection tunnel association group information, a third detection parameter of the target tunnel is generated. The first tunnel detection parameter also includes: a second detection parameter and a third detection parameter. The second detection parameter is generated based on the bidirectional tunnel association group information and is used to provide a parameter for parameter consistency detection to the second network element. The third detection parameter is generated based on the protection tunnel association group information and is used to indicate a parameter for parameter consistency detection to the second network element.

[0155] The above step S103, generating an MPLS probe request message for the target tunnel according to the first tunnel detection parameter, includes:

[0156] S302: Carry the second detection parameter in a second subfield newly added in the PCEP signaling of the MPLS probe request message.

[0157] S303: Carry the third detection parameter in a third subfield newly added in the PCEP signaling of the MPLS probe request message.

[0158] The PCEP Signaling (PCEP Signalling) TLV is a data structure newly added in the MPLS Probe Request message, and the second subfield and the third subfield are subfields newly added in the PCEP Signaling TLV.

[0159] A PCEP signaling TLV is added to the MPLS detection request message, a second subfield and a third subfield are added to the PCEP signaling TLV, the second detection parameter is carried in the second subfield, and the third detection parameter is carried in the third sub-data field.

[0160] The PCEP Signaling TLV field (PCEP Signaling TLV) is a TLV field used to identify PCEP signaling. A new PCEP Signaling TLV field is added, and a second subfield and a third subfield are defined within the PCEP Signaling TLV field. The second subfield carries the second detection parameter, and the third detection parameter carries the third detection parameter in the third subfield. The second and third subfields can be TLV fields, namely, the Bidi Tunnel sub-TLV and APS Tunnel sub-TLV. The second and third subfields exist in the PCEP Signaling TLV as payloads.

[0161] See also Figure 5 In this message structure, a first subfield is added to the target FEC stack, a PCEP signaling field is added, and a second subfield and a third subfield are defined in the PCEP signaling field.

[0162] It is worth noting that other parts of the MPLS probe request message also follow the data structure defined by the current protocol, and this embodiment does not impose any special restrictions on this.

[0163] In some embodiments, the first network element sends an MPLS probe request message to the second network element according to the test instruction. If the second network element receives the message successfully, it extracts the second detection parameter and the third detection parameter from the MPLS probe request message, and obtains the second tunnel detection parameter of the pre-stored target tunnel. The second network element performs a consistency check on the second detection parameter and the third detection parameter in the second tunnel operation parameters with the second detection parameter and the third detection parameter extracted from the message. If the second detection parameter and the third detection parameter in the second tunnel operation parameters are consistent with the second detection parameter and the third detection parameter extracted from the message, the first tunnel operation parameters and the second tunnel operation parameters are consistent. If the second detection parameter and the third detection parameter in the second tunnel operation parameters are inconsistent with the second detection parameter and the third detection parameter extracted from the message, the first tunnel operation parameters and the second tunnel operation parameters are inconsistent.

[0164] In some embodiments, when the MPLS network delivers a binding SID (BSID) through the protocol, meaning the first tunnel operation parameters include the binding label, the first network element initiating node may further extend the BSID's corresponding subfield (sub-TLV) in PCEP signaling. This sub-TLV carries BSID allocation detection parameters, including the BSID allocation method (whether the PCE specifies the label value or the NE allocates the label value independently), the BSID binding type (whether only the first 20 bits of the label are valid, and how the TTL / EXP fields are used). When the MPLP probe request message sent by the first network element reaches the intermediate node, the intermediate node may verify the BSID signaling allocation result based on this sub-TLV, thereby diagnosing protocol-related issues in the dynamic BSID allocation process.

[0165] This embodiment provides a future-oriented, scalable architecture. It performs protocol verification on PCEP signaling results through control plane zero-configuration enhanced test instructions. By adding PCEP signaling, a universal verification architecture is provided for all dynamic automatic management functions provided by PCEP for SR-TP extension in the form of subfields of the target FEC stack and the second and third subfields of the PCEP signaling field. This architecture not only supports the dynamic allocation results of the currently defined first tunnel operating parameters, bidirectional tunnel association group information, and protection tunnel association group information, but also, as SR-TP technology evolves in the future and PCEP supports more SR-TP features, it can support new extensions that may appear in the future in a backward-compatible manner.

[0166] In an optional embodiment, the first detection parameter includes: type information of the first subfield, a first byte length, address information of the first network element, address information of the second network element, protocol type of the path SID label information of the LSP, and a first flag bit. The first byte length is the sum of the byte length of the type information of the first subfield and the byte length of the path SID label information of the LSP. The first flag bit is used to indicate the global local attributes and allocation objects of the path SID label information of the LSP.

[0167] The type information (Sub-type) of the first subfield is used to indicate the type of the first subfield assigned by the Internet Assigned Numbers Authority. It cannot conflict with the type of a subfield already assigned by the Internet Assigned Numbers Authority. The type information can be in the form of a type code, such as n.

[0168] Calculate the byte length of the type information of the first subfield and the byte length of the LSP path SID label information, and use the sum of these two byte lengths as the first byte length (Length).

[0169] The address information of the first network element is the IP address of the first network element, and the address information of the second network element is the IP address of the second network element. The first network element is also the source node of the SR-TP LSP, and the second network element is also the sink node of the SR-TP LSP.

[0170] The protocol type (Protocol-Origin) of the LSP's path SID label information refers to the protocol type used to allocate the LSP's path SID label information, such as PCEP, BGP, or Provisioned.

[0171] The first flag bit (Flags) indicates the global and local attributes of the LSP's path SID label information and the allocation target. The global and local attributes indicate whether the LSP's path SID label information is globally unique or locally unique. If globally unique, it is unique across all network elements (NEs), while if locally unique, it is unique only on the NE of the target tunnel. The allocation target refers to whether the dynamic allocation of the LSP's path SID label information originates from the PCC or PCE server on the first NE.

[0172] The first flag bit contains a bit-defined flag. The first bit is 1 or 0, indicating whether the path label is globally unique or locally unique. The second bit is 1 or 0, indicating whether the path SID label information of the LSP is dynamically allocated by the PCC or the PCE server.

[0173] Figure 7 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 4 ,like Figure 7 As shown, the above step S203, carrying the first detection parameter in the first subfield newly added in the target FEC stack of the MPLS probe request message, may include:

[0174] S401. Carry the type information of the first subfield in the first byte to the second byte of the first subfield.

[0175] S402. Carry the first byte length in the third byte to the fourth byte of the first subfield.

[0176] S403: Carry the address information of the first network element in the fifth to eighth bytes of the first subfield.

[0177] S404: Carry the address information of the second network element in the ninth byte to the twelfth byte of the first subfield.

[0178] S405: Carry the protocol type of the LSP path SID label information in the thirteenth byte of the first subfield.

[0179] S406: Carry the first flag bit in the fourteenth byte of the first subfield.

[0180] Table 1 shows the first subfield. As shown in Table 1, the type information of the first subfield (sub-type=n) occupies two bytes and is carried in the first and second bytes of the first subfield. The first byte length (Length) occupies two bytes and is carried in the third and fourth bytes of the first subfield. The address information of the first network element (headend) occupies four bytes and is carried in the fifth to eighth bytes of the first subfield. The address information of the second network element (endpoint) occupies four bytes and is carried in the ninth to twelfth bytes of the first subfield. The protocol type of the LSP path SID label information occupies one byte and is carried in the thirteenth byte of the first subfield. The first flag bit occupies one byte and is carried in the fourteenth byte of the first subfield. "Reserved" indicates that subsequent extended content can be carried in the fifteenth to sixteenth bytes.

[0181] Table 1

[0182]

[0183] The first flag bit may be carried in the first two bits of the fourteenth byte of the first subfield, and the last six bits of the second byte are used for subsequent extension.

[0184] It can be understood that the value of the first subfield includes the address information of the first network element, the address information of the second network element, the protocol type of the path SID label information of the LSP, and the first flag bit.

[0185] The message structure provided in this embodiment can carry the first detection parameter in the first subfield of the target FEC stack to perform protocol verification of the dynamically allocated first tunnel operating parameter based on the first detection parameter. The dynamic allocation scheme of the first tunnel operating parameter is flexible and involves complex protocol operations on multiple network elements and the PCE controller side. The allocation result of the first tunnel operating parameter can be verified through test instructions, which facilitates the location and subsequent maintenance of protocol problems during automatic deployment after tunnel hosting.

[0186] In an optional embodiment, the second detection parameter includes: the association group type corresponding to the bidirectional tunnel association group information, the second byte length, the address information of the first network element, the global identification information of the bidirectional tunnel association group information, and the second flag bit. The second byte length is the sum of the byte length of the association group type corresponding to the bidirectional tunnel association group information and the byte length of the bidirectional tunnel association group information. The second flag bit is used to indicate the tunnel direction corresponding to the bidirectional tunnel association group information and whether it is a common path.

[0187] Among them, the association group type corresponding to the bidirectional tunnel association group information is used to indicate the type (sub-Type) of the bidirectional tunnel association group and can be in the form of a type code, such as 1. Calculate the byte length of the association group type corresponding to the bidirectional tunnel association group information and the byte length of the bidirectional tunnel association group information, and use the sum of these two byte lengths as the second byte length (Length).

[0188] The global identifier (Association ID) of a bidirectional tunnel association group is used to globally identify a bidirectional tunnel association group delivered through the protocol. For bidirectional tunnel association group information delivered through the protocol, the triple {AssocationType, Association ID, Association Source} uniquely identifies a bidirectional tunnel association group across the entire network. The Assocation Type indicates the association group type, the Association Source indicates the address information of the first network element, that is, the source node IP address of the SR-TP LSP, and the Assocation Type indicates the type information of the bidirectional tunnel association group delivered through the protocol, that is, the sub-Type.

[0189] The second flag bit is used to indicate the tunnel direction corresponding to the bidirectional tunnel association group information and whether it is a common path, wherein the tunnel direction corresponding to the bidirectional tunnel association group information includes the tunnel direction of the first tunnel opposite to the target tunnel, and whether it is a common path refers to whether the network elements on the target tunnel and the first tunnel are consistent. If they are consistent, they are a common path; if they are inconsistent, they are not a common path.

[0190] The meanings of the 3 bits of the second flag from left to right are:

[0191] F (Forward LSP, 1 bit): When set, it indicates that the first tunnel is the forward tunnel in the bidirectional tunnel association group.

[0192] R (Reverse LSP, 1 bit): When set, it indicates that the first tunnel is the reverse tunnel in the bidirectional tunnel association group.

[0193] C (Co-routed LSP, 1 bit): When set, it indicates that the bidirectional tunnel association group created by the protocol is bidirectional co-routed.

[0194] Figure 8 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 5 ,like Figure 8 As shown, in an optional embodiment, the above step S302, carrying the second detection parameter in a second subfield newly added in the PCEP signaling of the MPLS probe request message, may include:

[0195] S501: Carry the association group type corresponding to the bidirectional tunnel association group information in the first byte to the second byte of the second subfield.

[0196] S502. Carry the second byte length in the third byte to the fourth byte of the second subfield.

[0197] S503: Carry the address information of the first network element in the fifth to eighth bytes of the second subfield.

[0198] S504: Carry the global identification information of the bidirectional tunnel association group information in the ninth byte to the tenth byte of the second subfield.

[0199] S505: Carry the second flag bit in the eleventh byte to the twelfth byte of the second subfield.

[0200] Table 2 shows the PCEP signaling field. The PCEP signaling field is a newly added TLV at the top level. The PCEP signaling field coexists with the target FEC field and is distinguished by the TLV Type. The PCEP signaling field can include multiple subfields in its value portion.

[0201] The type information (Type) of the PCEP signaling field is carried in the first and second bytes of the PCEP signaling field. The byte length of the type information of the PCEP signaling field and the sum of the byte lengths of all subfields of the PCEP signaling field (such as the sum of the second byte length and the third byte length) (such as 24) are carried in the third and fourth bytes of the PCEP signaling field. The type information of the subfields of the PCEP signaling field is carried in the fifth and sixth bytes of the PCEP signaling field. The second byte length is carried in the seventh and eighth bytes of the PCEP signaling field.

[0202] The value portion of the PCEP signaling field includes multiple sub-fields (sub-TLVs). The type information of the PCEP signaling field indicates the type of the PCEP signaling field assigned by the Internet Assigned Numbers Authority (IAN). This type information cannot conflict with the type of a field already assigned by the IAN. The type information can be in the form of a type code, such as x.

[0203] Table 2

[0204]

[0205] Table 3 shows the second subfield. As shown in Table 3, the association group type (Sub-Type = 1) corresponding to the bidirectional tunnel association group information occupies two bytes and is carried in the first and second bytes of the second subfield. The second byte length (Length) occupies two bytes and is carried in the third and fourth bytes of the second subfield. The address information of the first network element (Association Source) occupies four bytes and is carried in the fifth to eighth bytes of the second subfield. The global identifier information (Association ID) of the bidirectional tunnel association group information occupies two bytes and is carried in the ninth to tenth bytes of the second subfield. The second flag bit (Flags) occupies two bytes and is carried in the eleventh and twelfth bytes of the second subfield.

[0206] Among them, the second flag bit can be carried in the first three bits of the eleventh byte to the twelfth byte, and the remaining 13 bits are used for subsequent expansion.

[0207] Table 3

[0208]

[0209] It can be understood that the value of the second subfield includes the address information of the first network element, the global identification information of the bidirectional tunnel association group information, and the second flag bit.

[0210] This embodiment supports test instructions for bidirectional tunnel association group information and performs protocol verification on dynamically allocated bidirectional tunnel association group information. The dynamic allocation scheme for bidirectional tunnel association group information is flexible and involves complex protocol operations on multiple network elements and the PCE server. Based on the test instructions, the allocation results of the bidirectional tunnel association group information can be verified, which facilitates the location and subsequent maintenance of protocol problems during automatic deployment after tunnel hosting.

[0211] In an optional embodiment, the third detection parameter includes: the association group type corresponding to the protection tunnel association group information, the third byte length, the address information of the first network element, the global identification information of the protection tunnel association group information, and the third flag bit. The third byte length is the sum of the byte length of the association group type corresponding to the protection tunnel association group information and the byte length of the protection tunnel association group information. The third flag bit is used to indicate the tunnel master / slave status and protection type corresponding to the protection tunnel association group information.

[0212] Among them, the association group type corresponding to the protection tunnel association group information is used to indicate the type (sub-Type) of the protection tunnel association group, which can be in the form of a type code, such as 2. The byte length of the association group type corresponding to the protection tunnel association group information and the byte length of the protection tunnel association group information are calculated, and the sum of these two byte lengths is used as the third byte length (Length).

[0213] The global identification information (Association ID) of the protection tunnel association group information is used to globally identify the protection tunnel association group issued through the protocol. For the protection tunnel association group information issued through the protocol, the {Assocation Type, Association ID, Association Source} triple can uniquely identify a protection tunnel association group within the entire network. Among them, Assocation Type indicates the association group type, Association Source indicates the address information of the first network element, that is, the source node IP address of the SR-TP LSP, and Assocation Type is the type information of the bidirectional tunnel association group issued by the protocol, that is, the sub-Type.

[0214] The third flag is used to indicate the master / backup status of the protection tunnel association group information corresponding to the tunnel and the protection type, wherein the master / backup status of the protection tunnel association group information corresponding to the tunnel is used to indicate whether the second tunnel that transmits in the same direction as the target tunnel is a master tunnel (master LSP) or a slave tunnel (slave LSP), and the protection type refers to the protection type of the protection tunnel association group created by the protocol.

[0215] The meanings of the 8 bits of the third flag from left to right are:

[0216] P (Protection LSP, 1 bit) – When set, indicates that the first tunnel is the primary tunnel in the protection tunnel association group.

[0217] S (Secondary LSP, 1 bit) – When set, indicates that the primary tunnel is a secondary tunnel in the protection tunnel association group.

[0218] PT (Protection Type LSP, 6 bits) – When set, this bit indicates the protection type currently running on the protection tunnel association group.

[0219] The following types of protection are included:

[0220] 0x00 Unprotected: No protection

[0221] 0x01 (Full) Rerouting: Full rerouting

[0222] 0x02 Rerouting without Extra-Traffic: Rerouting without extra traffic

[0223] 0x04 1:N Protection with Extra-Traffic: 1:N protection with extra traffic

[0224] 0x08 1+1 Unidirectional Protection: 1+1 unidirectional protection

[0225] 0x10 1+1 Bidirectional Protection: 1+1 bidirectional protection

[0226] Unprotected means that there are no backup paths or protection measures in the network. If the primary path fails, traffic will be lost until the path is repaired.

[0227] Complete rerouting means that when the primary path fails, the network dynamically calculates a new path and reroutes traffic.

[0228] Rerouting without additional traffic means that when the primary path fails, traffic is switched to a pre-assigned backup path, and the backup path does not carry additional traffic.

[0229] 1:N protection with extra traffic means that one backup path protects multiple working paths and allows the backup path to carry extra traffic under normal conditions.

[0230] 1+1 unidirectional protection means that two paths (a working path and a protection path) operate simultaneously, but traffic is received only on one path. The protection path is unidirectional.

[0231] 1+1 bidirectional protection means that two paths operate simultaneously and traffic is transmitted in both directions simultaneously.

[0232] Figure 9 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 6 ,like Figure 9 As shown, in an optional embodiment, the above step S303, carrying the third detection parameter in a third subfield newly added in the PCEP signaling of the MPLS probe request message, may include:

[0233] S601: Carry the association group type corresponding to the protection tunnel association group information in the first byte to the second byte of the third subfield.

[0234] S602: Carry the third byte length in the third byte to the fourth byte of the third subfield.

[0235] S603: Carry the address information of the first network element in the fifth to eighth bytes of the third subfield.

[0236] S604: Carry the global identification information of the protection tunnel association group information in the ninth byte to the tenth byte of the third subfield.

[0237] S605: Carry the third flag bit in the eleventh byte to the twelfth byte of the third subfield.

[0238] Table 4 shows the third subfield. As shown in Table 4, the association group type (Sub-Type=2) corresponding to the protection tunnel association group information occupies two bytes and is carried in the first to second bytes of the third subfield. The third byte length (Length) occupies two bytes and is carried in the third to fourth bytes of the third subfield. The address information of the first network element (Association Source) occupies four bytes and is carried in the fifth to eighth bytes of the third subfield. The global identification information (Association ID) of the protection tunnel association group information occupies two bytes and is carried in the ninth to tenth bytes of the third subfield. The third flag bit (Flags) occupies two bytes and is carried in the eleventh to twelfth bytes of the third subfield.

[0239] Table 4

[0240]

[0241] This embodiment supports test instructions for protection tunnel association group information. Protocol verification is performed on dynamically allocated protection tunnel association group information based on a third test parameter to test tunnel connectivity and protocol consistency. The dynamic allocation of protection tunnel association group information is flexible and involves complex protocol operations across multiple network elements and the PCE server. This test instruction verifies the allocation results of protection tunnel association group information, facilitating the identification and subsequent maintenance of protocol issues during automatic deployment after tunnel hosting.

[0242] Figure 10 Schematic diagram of the process of the tunnel detection method provided in the embodiment of the present application Figure 7 , this method is applied to a second network element in a multipath label switching MPLS network.

[0243] like Figure 7 As shown, the method may include:

[0244] S701: Receive an MPLS probe request message sent by a first network element through a target tunnel, and obtain a reception result of the MPLS probe request message.

[0245] The reception result is used to indicate whether the second network element successfully receives the MPLS probe request message sent by the first network element through the target.

[0246] The MPLS detection request message is generated according to a first tunnel detection parameter of the target tunnel, and the first tunnel detection parameter is generated based on a first tunnel operation parameter of the target tunnel pre-stored in the first network element.

[0247] S702: Based on the reception result of the MPLS probe request message, perform tunnel connectivity detection on the target tunnel.

[0248] If the reception result indicates that the MPLS probe request message is successfully received, it is determined that the tunnel connectivity test of the target tunnel passes. If the reception result indicates that the MPLS probe request message cannot be received, it is determined that the tunnel connectivity test of the target tunnel fails.

[0249] S703: When the tunnel connectivity test passes, extract a first tunnel detection parameter from the MPLS detection request message.

[0250] S704: Obtain second tunnel detection parameters of the target tunnel according to pre-stored second tunnel operation parameters.

[0251] When the tunnel connectivity test passes, the first tunnel detection parameter is extracted from the MPLS detection request message, and the pre-stored second tunnel operation parameter is obtained, the second tunnel operation parameter is the tunnel operation parameter that the PCE pre-sents to the second network element through the protocol, and based on the second tunnel operation parameter, the second tunnel detection parameter of the target tunnel is generated, wherein the second tunnel detection parameter is generated based on the second tunnel operation parameter.

[0252] The second tunnel operation parameter may include at least one of: path segment identifier SID label information of the label switched path LSP of the target tunnel, bidirectional tunnel association group information, and protection tunnel association group information.

[0253] S705: Perform parameter consistency detection based on the first tunnel detection parameter and the second tunnel detection parameter to obtain a detection result.

[0254] The second network element performs a parameter consistency check based on the second tunnel detection parameters and the first tunnel detection parameters to obtain a detection result, wherein if the second tunnel detection parameters are consistent with the first tunnel detection parameters, the detection result is used to indicate that the first tunnel operation parameters and the second tunnel operation parameters are consistent; if the second tunnel detection parameters are consistent with the first tunnel detection parameters, the detection result is used to indicate that the first tunnel operation parameters and the second tunnel operation parameters are inconsistent.

[0255] In some embodiments, the detection result may include a return code and / or a return sub-code. The return code may be, for example, 3, indicating that the replying router is an egress for the FEC at stack-depth, and the return sub-code may be, for example, 10, indicating that the mapping for this FEC is not the given label at stack-depth. <rsc>.

[0256] S706: Generate an MPLS probe response message for the target tunnel according to the detection result, and return the MPLS probe response message to the first network element.

[0257] The second network element generates an MPLS probe response message according to the detection result and returns it to the first network element. The MPLS probe response message may include the detection result.

[0258] In an optional implementation, step S706, generating an MPLS probe response message for the target tunnel based on the detection result, may include:

[0259] The detection result is carried in the header of the MPLS probe response message.

[0260] Figure 11 A schematic diagram of the MPLS probe response message structure provided in an embodiment of the present application is shown in FIG. Figure 11 As shown, the detection result is carried in the message header of the MPLS probe response message, and the target FEC stack of the MPLS probe response message is copied from the MPLS probe request message.

[0261] It is worth noting that other parts of the MPLS probe response message also follow the data structure defined by the current protocol, and this embodiment does not impose any special restrictions on this.

[0262] In some embodiments, the second tunnel operation parameters may include: the path segment identifier SID label information of the label switched path LSP of the target tunnel, the bidirectional tunnel association group information and the protection tunnel association group information. The second network element may generate the fourth detection parameter, the fifth detection parameter and the sixth detection parameter of the target tunnel respectively according to the path SID label information, the bidirectional tunnel association group information and the protection tunnel association group information of the LSP in the second tunnel operation parameters.

[0263] Parameter consistency checks are then performed on each of the three groups of detection parameters (Group 1: Fourth Detection Parameter and First Detection Parameter, Group 2: Fifth Detection Parameter and Second Detection Parameter, and Group 3: Sixth Detection Parameter and Third Detection Parameter). This consistency check of the fourth detection parameter and the first detection parameter includes verifying the address information of the first network element, the protocol type of the LSP's path SID label information, and the first flag bit (global and local attributes and allocation object of the LSP's path SID label information).

[0264] Performing parameter consistency check on the fifth detection parameter and the second detection parameter includes checking the association group type corresponding to the bidirectional tunnel association group information, the second byte length, the address information of the first network element, the global identification information of the bidirectional tunnel association group information, and the second flag bit (the tunnel direction corresponding to the bidirectional tunnel association group information and whether it is a common path).

[0265] The parameter consistency check of the sixth detection parameter and the third detection parameter includes checking the association group type corresponding to the protection tunnel association group information, the third byte length, the address information of the first network element, the global identification information of the protection tunnel association group information, and the third flag bit (the protection tunnel association group information corresponds to the tunnel master-slave status and protection type).

[0266] In some embodiments, the second network element may also check the length of the received MPLS probe response message to verify whether the message length meets expectations, and perform basic verification processing according to the protocol definition. The specific details shall be subject to the protocol definition, and this embodiment does not specifically limit this.

[0267] In some embodiments, during the process of performing parameter verification, if at least one group of the fourth detection parameter and the first detection parameter, the fifth detection parameter and the second detection parameter, the sixth detection parameter and the third detection parameter fails to pass the verification, and / or the message length does not meet expectations, the detection result indicates that the first tunnel operation parameter and the second tunnel operation parameter are inconsistent, and an MPLS probe response message can be returned.

[0268] In this embodiment, the user initiates a test instruction for the target tunnel on the tunnel starting point network element of the target tunnel to detect tunnel connectivity and parameter consistency, implement data plane connectivity detection and control plane operation consistency detection, and timely perceive the network and operation status through the return message, and perform fault location processing through the information carried in the return message when a fault occurs.

[0269] Figure 12 A structural diagram of a network device provided in an embodiment of the present application, wherein the network device may be a first network element or a second network element.

[0270] like Figure 12 As shown, the device may include: a processor 801, a memory 802 and a bus 803. The memory 802 stores machine-readable instructions executable by the processor 801. When the network device is running, the processor 801 communicates with the memory 802 through the bus 803, and the processor 801 executes the machine-readable instructions to perform the above method.

[0271] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above method is executed.

[0272] In the embodiment of the present application, the computer program can also execute other machine-readable instructions when run by the processor to execute the methods described in other embodiments. For the specific execution method steps and principles, please refer to the description of the embodiment and will not be repeated here.

[0273] It should be noted that the terms “first”, “second”, “third”, etc. are only used to distinguish and describe, and should not be understood as indicating or implying relative importance.

[0274] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The scope of protection of the present application is not limited thereto. Although the present application has been described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-described embodiments within the technical scope disclosed in the present application, or make equivalent replacements for some of the technical features thereof. However, these modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application. They should all be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.< / rsc>

Claims

1. A tunnel detection method, characterized in that: Applied to a first network element in a multipath label switching (MPLS) network, the method comprises: Obtaining, according to a test instruction for a target tunnel, a pre-stored first tunnel operating parameter of the target tunnel, wherein the target tunnel is any segment of a Routing Transport Protocol (SR-TP) tunnel starting from the first network element; generating a first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter; generating an MPLS probe request message for the target tunnel according to the first tunnel detection parameter; Sending the MPLS probe request message to a second network element serving as an end point of the target tunnel through the target tunnel, so that the second network element performs a tunnel connectivity test on the target tunnel based on the MPLS probe request message, and extracting the first tunnel detection parameter from the MPLS probe request message to perform a parameter consistency test when the tunnel connectivity test passes; Obtaining an MPLS probe response message for the target tunnel returned by the second network element; The first tunnel operation parameter includes: bidirectional tunnel association group information and protection tunnel association group information of the target tunnel; Generating the first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter includes: generating a second detection parameter and a third detection parameter of the target tunnel respectively according to the bidirectional tunnel association group information and the protection tunnel association group information; The generating, according to the first tunnel detection parameter, an MPLS probe request message for the target tunnel includes: Carrying the second detection parameter in a second subfield newly added in the PCEP signaling of the MPLS probe request message; The third detection parameter is carried in a third subfield newly added in the PCEP signaling of the MPLS probe request message.

2. The method according to claim 1, characterized in that The first tunnel operation parameter includes: path segment identifier SID label information of the label switched path LSP of the target tunnel; Generating the first tunnel detection parameter of the target tunnel according to the first tunnel operation parameter includes: Generating a first detection parameter of the target tunnel according to the path SID label information of the LSP; The generating, according to the first tunnel detection parameter, an MPLS probe request message for the target tunnel includes: Acquire path SID label information of the adjacent segment link on the target tunnel according to the path SID label information of the LSP; Carrying the path SID label information of the adjacent segment link and the path SID label information of the LSP in the label stack of the MPLS probe request message; The first detection parameter is carried in a first subfield newly added in a target forwarding equivalence class (FEC) stack of the MPLS probe request message.

3. The method according to claim 2, characterized in that The first detection parameter includes: type information of the first subfield, a first byte length, address information of the first network element, address information of the second network element, a protocol type of the path SID label information of the LSP, and a first flag bit, wherein the first byte length is the sum of the byte length of the type information of the first subfield and the byte length of the path SID label information of the LSP, and the first flag bit is used to indicate the global-local attributes and allocation object of the path SID label information of the LSP; The step of carrying the first detection parameter in a first subfield newly added in the target FEC stack of the MPLS probe request message includes: Carrying the type information of the first subfield in the first byte to the second byte of the first subfield; Carrying the first byte length in the third byte to the fourth byte of the first subfield; Carrying the address information of the first network element in the fifth to eighth bytes of the first subfield; Carrying the address information of the second network element in the ninth to twelfth bytes of the first subfield; Carrying the protocol type of the path SID label information of the LSP in the thirteenth byte of the first subfield; The first flag bit is carried in the fourteenth byte of the first subfield.

4. The method according to claim 1, wherein The second detection parameter includes: an association group type corresponding to the bidirectional tunnel association group information, a second byte length, address information of the first network element, global identification information of the bidirectional tunnel association group information, and a second flag bit, where the second byte length is the sum of a byte length of the association group type corresponding to the bidirectional tunnel association group information and a byte length of the bidirectional tunnel association group information, and the second flag bit is used to indicate a tunnel direction corresponding to the bidirectional tunnel association group information and whether the tunnel is co-path. The carrying of the second detection parameter in a second subfield newly added in the PCEP signaling of the MPLS probe request message includes: Carrying the association group type corresponding to the bidirectional tunnel association group information in the first byte to the second byte of the second subfield; Carrying the second byte length in the third byte to the fourth byte of the second subfield; Carrying the address information of the first network element in the fifth to eighth bytes of the second subfield; Carrying the global identification information of the bidirectional tunnel association group information in the ninth to tenth bytes of the second subfield; The second flag bit is carried in the eleventh byte to the twelfth byte of the second subfield.

5. The method according to claim 1, wherein The third detection parameter includes: an association group type corresponding to the protection tunnel association group information, a third byte length, address information of the first network element, global identification information of the protection tunnel association group information, and a third flag bit, where the third byte length is the sum of the byte length of the association group type corresponding to the protection tunnel association group information and the byte length of the protection tunnel association group information, and the third flag bit is used to indicate the active / standby status and protection type of the tunnel corresponding to the protection tunnel association group information; The step of carrying the third detection parameter in a third subfield newly added in the PCEP signaling of the MPLS probe request message includes: Carrying the association group type corresponding to the protection tunnel association group information in the first byte to the second byte of the third subfield; Carrying the third byte length in the third byte to the fourth byte of the third subfield; Carrying the address information of the first network element in the fifth to eighth bytes of the third subfield; Carrying the global identification information of the protection tunnel association group information in the ninth byte to the tenth byte of the third subfield; The third flag bit is carried in the eleventh byte to the twelfth byte of the third subfield.

6. The method according to claim 1, wherein The obtaining of the MPLS probe response message for the target tunnel returned by the second network element includes: Obtaining the MPLS probe response message returned by the second network element through the address information of the first network element; or, The MPLS probe response message returned by the second network element is obtained through the reverse tunnel corresponding to the target tunnel.

7. A tunnel detection method, characterized in that: Applied to a second network element in a multipath label switching (MPLS) network, the method comprises: An MPLS probe request message sent by a first network element is received through a target tunnel, and a reception result of the MPLS probe request message is obtained; the MPLS probe request message is generated according to a first tunnel detection parameter of the target tunnel, and the first tunnel detection parameter is generated based on a first tunnel operation parameter of the target tunnel pre-stored by the first network element, and the first tunnel operation parameter includes: bidirectional tunnel association group information and protection tunnel association group information of the target tunnel, the first tunnel detection parameter includes a second detection parameter and a third detection parameter, the second detection parameter and the third detection parameter are respectively generated according to the bidirectional tunnel association group information and the protection tunnel association group information, the second detection parameter is carried in a second subfield newly added in the PCEP signaling of the MPLS probe request message, and the third detection parameter is carried in a third subfield newly added in the PCEP signaling of the MPLS probe request message; Performing tunnel connectivity detection on the target tunnel based on a result of receiving the MPLS probe request message; When the tunnel connectivity test passes, extracting the first tunnel detection parameter from the MPLS detection request message; Acquiring a second tunnel detection parameter of the target tunnel according to a pre-stored second tunnel operation parameter; Performing parameter consistency detection based on the first tunnel detection parameter and the second tunnel detection parameter to obtain a detection result; An MPLS probe response message for the target tunnel is generated according to the detection result, and the MPLS probe response message is returned to the first network element.

8. The method according to claim 7, characterized in that Generating an MPLS probe response message for the target tunnel according to the detection result includes: The detection result is carried in the message header of the MPLS probe response message.

9. A network device, characterized in that: include: A processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the network device is running, the processor and the memory communicate via the bus, and the processor executes the machine-readable instructions to perform the method described in any one of claims 1 to 8.

Images