WO2020052274A1

WO2020052274A1 - Method and apparatus for implementing mpls-based network detection, network device, and controller

Info

Publication number: WO2020052274A1
Application number: PCT/CN2019/088427
Authority: WO
Inventors: 詹双平; 柯明
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-09-13
Filing date: 2019-05-24
Publication date: 2020-03-19
Also published as: CN109525451A; CN109525451B

Abstract

Disclosed are a method and apparatus for implementing MPLS-based network detection, a network device, and a controller. The method comprises: a node in a detection domain determines information of a detection object and a detection task, wherein the information of the detection object comprises an object identifier; when the node is the header node of the detection domain, identify a service packet matching the detection object from a received service stream, add the object identifier to the MPLS tag of the service packet, and forward the service packet comprising the object identifier; when the node is the header node, intermediate node, or tail node of the detection domain, perform a detection operation on the service packet comprising the object identifier according to the detection task.

Description

Method, device, network equipment and controller for implementing MPLS network detection

Cross-reference to related applications

This application is based on a Chinese patent application with an application number of 201811070379.8 and an application date of September 13, 2018, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is incorporated herein by reference.

Technical field

The embodiments of the present application relate to, but are not limited to, a method, an apparatus, a network device, a controller, and a computer-readable storage medium for implementing an MPLS (Multi-Protocol Label Switching) network detection.

Background technique

IP (Internet Protocol) / MPLS is a layer network model, which can be divided into services (L3VPN (Layer 3 Virtual Private Networks, etc.), etc.) and pipes (tunnels, LSPs (Label Switching) Path, label switching path, etc.) The two levels are different for the performance detection of different levels of objects. For example, pipeline detection is generally achieved through the LM (Loss Measure, Loss Measure) and DM (Delay Measure, Delay Measurement) functions defined in RFC6374 or G.8113.1. The detection at the business level can be performed through Two-Way Active Measurement Protocol Two-way active measurement protocol).

For different detection objects, the current identification methods of detection mechanisms are also different. For example, for tunnels, MPLS labels are usually used to identify the tunnels to be counted. For service flows, flow characteristics (such as IP quintuples) are generally used to identify flows that need to be counted.

However, some tunnel types cannot be distinguished by MPLS labels. IP quintuples sometimes cannot be identified when there are a large number of MPLS label stack layers, which makes detection and deployment of MPLS networks difficult.

Summary of the Invention

The embodiments of the present application provide a method, an apparatus, a network device, a controller, and a computer-readable storage medium for implementing MPLS network detection.

In a first aspect, an embodiment of the present application provides a method for implementing MPLS network detection, which includes: determining, by a node in a detection domain, information of a detection object and a detection task, wherein the information of the detection object includes an object identifier; and the node When it is the head node of the detection domain, a service packet matching the detection object is identified in the received service flow, the object identifier is added to the MPLS label of the service packet, and the forwarding includes the object identifier. An object-identified service message; when the node is a head node, an intermediate node, or a tail node of the detection domain, a detection operation is performed on a service message containing the object identifier according to the detection task.

In a second aspect, an embodiment of the present application further provides a method for implementing multi-protocol label switching MPLS network detection, including: a controller assigning an object identifier to a detection object in the MPLS network; The information of the object is sent to each node in the detection domain corresponding to the detection object, so that the node performs a detection operation on a service packet matching the detection object according to the detection task according to the object identification.

In a third aspect, an embodiment of the present application further provides a method for implementing multi-protocol label switching MPLS network detection, including: a controller assigns an object identifier to a detection object in the MPLS network, and sends a detection task and information of a detection object including the object identifier. To each node in the detection domain corresponding to the detection object; the node in the detection domain determines the information of the detection object and the detection task; when the node is the head node of the detection domain, it receives A service packet matching the detection object is identified in the service flow of the service object, the object identifier is added to the MPLS label of the service packet, and the service packet containing the object identifier is forwarded; the node is the When detecting a head node, an intermediate node, or a tail node of a domain, a detection operation is performed on a service packet including the object identifier according to the detection task.

In a fourth aspect, an embodiment of the present application further provides a device for implementing multi-protocol label switching MPLS network detection, including:

A determination module configured to determine information of a detection object and a detection task, wherein the information of the detection object includes an object identifier;

A processing module configured to identify a service packet that matches the detection object in a received service flow when the device is located at a head node of a detection domain, and add the MPLS label to the service packet An object identifier, and forward a service message including the object identifier; and

The detection module is configured to perform a detection operation on a service packet including the object identifier according to the detection task.

In a fifth aspect, an embodiment of the present application further provides a device for implementing multi-protocol label switching MPLS network detection, including:

An assignment module configured to assign an object identifier to a detection object in the MPLS network;

A sending module configured to send information and detection tasks of a detection object including an object identifier to each node in a detection domain corresponding to the detection object, so that the node performs the detection task and Perform the detection operation on the service packets matching the detection object.

According to a sixth aspect, an embodiment of the present application further provides a network device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. The processor implements the program when the processor executes the program. Implementation method of MPLS network detection.

According to a seventh aspect, an embodiment of the present application further provides a controller, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. The processor implements the program when the processor executes the program. Implementation method of MPLS network detection.

In an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are used to implement the implementation method of the MPLS network detection.

The embodiment of the present application includes: a node in a detection domain determines information of a detection object and a detection task, wherein the information of the detection object includes an object identifier; and when the node is a head node of the detection domain, the received service A service packet matching the detection object is identified in the flow, the object identifier is added to the MPLS label of the service packet, and a service packet containing the object identifier is forwarded; the node is the detection domain When a head node, an intermediate node, or a tail node of the mobile terminal, perform a detection operation on a service packet including the object identifier according to the detection task. In the embodiment of the present invention, by adding an object identifier to an MPLS label, it is realized that the detection object at different levels adopts a universal identifier, reduces the analysis depth of the intermediate node, and can implement point-by-point performance detection.

BRIEF DESCRIPTION OF THE DRAWINGS

1 is a flowchart of a method for implementing MPLS network detection according to an embodiment of the present application;

2 is a schematic diagram of a frame format using a special-purpose label to represent an object identifier according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a frame format for representing an object identifier by using a combination of extended tags and extended special-purpose tags according to an embodiment of the present application;

4 is a flowchart of a method for implementing MPLS network detection according to another embodiment of the present application;

5 is a flowchart (controller side) of an implementation method of MPLS network detection according to an embodiment of the present application;

6 is a flowchart (controller side) of a method for implementing MPLS network detection according to another embodiment of the present application;

7 is a flowchart (node side) of a method for implementing MPLS network detection according to an embodiment of the present application;

8 is a flowchart (node side) of an implementation method of MPLS network detection according to another embodiment of the present application;

9 is a schematic diagram of an object tag deployment model according to an embodiment of the present application;

FIG. 10 is a schematic diagram of a frame format adopted by a service message in Application Example 1 of this application; FIG.

11 is a schematic diagram of an SR network path tracking scenario in Application Example 2 of this application;

FIG. 12 is a schematic diagram of a frame format used for service messages in Application Example 2 of this application; FIG.

FIG. 13 is a schematic diagram of a frame format used for service messages in Application Example 3 of this application; FIG.

FIG. 14 is a schematic diagram of a frame format used for a service message in Application Example 4 of this application; FIG.

15 is a schematic diagram of a TWAMP measurement principle;

FIG. 16 is a schematic diagram of a frame format used for a service message in Application Example 5 of this application; FIG.

FIG. 17 is a schematic diagram of a frame format used in a TWAMP message in Application Example 5 of this application; FIG.

18 is a schematic diagram of a frame format used by a pseudo wire message in Application Example 6 of this application;

19 is a schematic diagram of a device for implementing MPLS network detection according to an embodiment of the present application (applied to detecting nodes in a domain);

20 is a schematic diagram of a device for implementing MPLS network detection according to an embodiment of the present application (applied to a controller);

21 is a schematic diagram of a network device according to an embodiment of the present application;

22 is a schematic diagram of a controller according to an embodiment of the present application.

detailed description

The embodiments of the present application will be described in detail below with reference to the drawings.

The steps shown in the flowchart of the figures may be performed in a computer system such as a set of computer-executable instructions. And, although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

The current methods for detecting the identification of a mechanism are as follows:

Some tunnel types cannot be distinguished by MPLS labels. For example, SR (Segment Routing) tunnels require additional labels to indicate them; identifying IP quintuples at intermediate points requires more hardware resources, especially in MPLS. When the number of label stack layers is large, sometimes it is not even identifiable, which makes it impossible to deploy point-by-point performance measurement on most networks.

In view of the above, an embodiment of the present application proposes a method for implementing MPLS network detection. By adding a common Object ID to each detected object, the nodes in the detection domain only need to identify and count according to the object ID. That is, this identification method needs to be universal and extensible.

As shown in FIG. 1, the method for implementing MPLS network detection in the embodiment of the present application includes:

Step 101: The controller sends a detection task to each node in the detection domain corresponding to the detection object.

The detection object may include at least one of the following: a tunnel, a service flow, and a PW (Pseudo-Wire, pseudo wire). That is, the object identifier is a general object identifier, which can represent a service flow, and can also represent a tunnel, a PW, and the like. Among them, the tunnel includes an SR tunnel, a Label Distribution Protocol (LDP) tunnel, and the like.

The controller can send a detection task to each node in the detection domain through a configuration command.

The detection task may include: counting service packets, tracing tunnel paths, performing in-band performance statistics through alternating colored markers, TWAMP (Two-Way Active Measurement Protocol) message measurement, and the like.

Step 102: A node in the detection domain determines information of the detection object and the detection task.

The node may be a head node, an intermediate node, or a tail node of the detection domain.

The information of the detection object includes an object identifier, and according to different detection objects, it may further include a tunnel identifier, characteristic information of a service flow (such as an IP quintuple), a PW identifier, and the like.

The controller may assign an object identifier to the detection object, and information of the detection object including the object identifier is sent to each node in the detection domain.

The object identifier may be globally unique or node unique. In the case of global uniqueness, the detection object is identified by an object identifier; in the case of a node unique, the head node identifier and the object identifier are used as a tuple. Identifying the detection object.

In a case where the detection object is identified by a tuple of a head node identifier and an object identifier, the object identifier may be allocated by a head node in the detection domain.

Step 103: When the node is the head node of the detection domain, a service packet matching the detection object is identified in the received service flow, and the object is added to the MPLS label of the service packet. Identification, and forwards a service message containing the object identification.

The head node may identify a service packet matching the detection object according to the information of the detection object, for example:

When the detection object includes a tunnel, the information of the detection object further includes a tunnel identifier, and the head node identifies a service packet that matches the detection object in the received service flow according to the tunnel identifier.

When the detection object includes a service flow, the information of the detection object further includes characteristic information of the service flow, and the head node recognizes that the detection object matches the detection object in the received service flow according to the characteristic information of the service flow. Business message.

When the detection object includes a PW, the information of the detection object further includes a PW identifier, and the head node identifies a service packet that matches the detection object in the received service flow according to the PW identifier.

In an embodiment, the detection object is identified by a tuple of a node identifier and an object identifier. In this step, a tuple of a head node identifier and an object identifier is added to the MPLS label of the service packet. Forward a service message containing the two-tuple.

In an embodiment, the position of the object identifier in the MPLS label is determined according to the detection object, and the object identifier is added to the MPLS label according to the position. In other words, the position of the object identifier in the MPLS label stack is different according to the detection object.

For example, when the detection object includes a tunnel, the object identifier is placed after the tunnel label and before the service label; when the detection object includes a service flow, the object identifier is placed after the service label, that is, at the bottom of the MPLS label stack.

In an embodiment, a preset guide label and the object identifier are added to the MPLS label, and the guide label is located before the object identifier, and is used to indicate a position of the object identifier in the MPLS label.

In the MPLS label stack, in order not to conflict with other MPLS labels, a guide label can be used to indicate that the object identifier is followed, so that the object identifier can be placed anywhere in the label stack, and the value range of the object identifier is independent of MPLS. The label space can be duplicated with other MPLS forwarding labels. The guide label can be expressed in two ways:

Method one: use special purpose labels to indicate

RFC3032 defines reserved tags of 0-15 as special purposes. At present, there are still some unassigned tag values. Taking the unassigned tag value of 12 as an example, it represents the leading tag of the object identifier. Its frame format is shown in Figure 2. Among them, TC stands for Traffic Class, S is the identifier of the bottom position of the stack, when S = 1, it is at the bottom of the MPLS label stack, and TTL indicates the expiration time (Time To Live).

Method two: use a combination of extended tags and extended special-purpose tags to represent

RFC7274 defines an extended special-purpose label representation method. A label value of 15 indicates an extended label. The extended extended special-purpose label is a specific extension type. Here, a label value of 100 is used as an example to indicate a guide label for object identification. The frame format is Shown in Figure 3.

Which kind of guide label to use can be selected according to the actual situation.

In an embodiment, the object identifier includes a label domain, and adding the object identifier to an MPLS label of the service packet includes: setting the label domain according to a preset label rule, and An object identifier containing the label domain is added to the MPLS label. By setting the tag field, the object identifier can be extended to support carrying instructions to meet the requirements of more flexibility and scalability.

For example, the detection task includes performing in-band performance statistics through alternating coloring marks, and the tag domain includes alternating coloring marks, and achieving alternating coloring by using alternate coloring marks.

For example, the detection task includes measuring a TWAMP message, inserting a TWAMP message into the service flow, an MPLS label of the TWAMP message carrying an object identifier containing the tag domain, and indicating the report through the tag domain. The text type is TWAMP message. For TWAMP packets and service packets, the value of the tag field is different.

Step 104: When the node is a head node, an intermediate node, or a tail node of the detection domain, perform a detection operation on a service packet including the object identifier according to the detection task.

Among them, the operations performed are different depending on the detection task and the location of each node.

In one embodiment, the detection task includes: counting service packets, and the step 104 includes: when the node is a head node of the detection domain, counting and counting the service packets sent out; When the node is an intermediate node in the detection domain, count and count the received service packets and the service packets sent respectively; when the node is a tail node in the detection domain, count the received The received service packets are counted.

In an embodiment, the detection task includes: tunnel path tracking, and the step 104 includes: when the node is a head node of the detection domain, comparing the node information with the outbound interface information of the service packet and The object identifier is associated, and the associated information is recorded; when the node is an intermediate node in the detection domain, its own node information and the inbound interface information of the service message are associated with the object identifier, And, the self node information and the outbound interface information of the service message are associated with the object identifier, and the associated information is recorded; when the node is the tail node of the detection domain, the self node information, The inbound interface information of the service message is associated with the object identifier, and the associated information is recorded.

In an embodiment, the detection task includes: performing in-band performance statistics, the marker domain includes alternating coloring markers, and the step 104 includes: when the node is a head node of the detection domain, according to the The information of the alternately colored flags is used to count and count the service packets sent out. When the node is an intermediate node in the detection domain, the received and transmitted services are processed according to the information of the alternately colored flags. The packet is counted and counted; when the node is the tail node of the detection domain, the received service packet is counted and counted according to the information of the alternating coloring mark.

In an embodiment, the detection task includes: performing in-band performance statistics, the marker domain includes a delay measurement marker, and the step 104 includes: when the node is a head node of the detection domain, according to the The delay measurement mark information is used to time-stamp the service message and record the time stamp when the service message is sent. When the node is an intermediate node in the detection domain, the delay measurement mark is used. The service information is time stamped on the service message, and the time stamp when the service message arrives and is sent is recorded. When the node is the tail node of the detection domain, the marked information is measured according to the delay. Time stamping the service message and recording the time stamp when the service message arrives.

In an embodiment, the node performing a detection operation on a service packet containing the object identifier according to the detection task includes: when the node is a head node of the detection domain, the node sends the service packet The statistics are counted in the text, and the value of the counted statistics is carried in the TWAMP message and sent out; when the node is the tail node of the detection domain, the statistics of the received service packets are counted and the received The value of the counting statistics carried in the TWAMP message is compared with the value of the own counting statistics to obtain a TWAMP measurement result. In addition, for the tail node of the detection domain, the object identification and other labels in the MPLS label stack are also popped out to restore the original service packet.

As shown in FIG. 4, in an embodiment, after step 104, the method may further include:

In step 105, the node sends a detection result obtained by performing a detection operation to the controller.

The detection result may be a count value of service packets, a time stamp value of service packets, tunnel path information, and the like.

Step 106: The controller receives the detection result sent by the node, and performs statistics on the detection result.

In an embodiment, the detection task includes: counting service packets, and the step 106 includes: the controller performs traffic statistics, end-to-end packet loss statistics, and point-by-point packet loss according to the detection results. At least one of the statistics.

In an embodiment, the detection task includes: tunnel path tracking, and the step 106 includes: the controller statistics complete tunnel path information according to the detection result.

In one embodiment, the detection task includes: performing in-band performance statistics, and the step 106 includes: the controller performs traffic statistics, end-to-end packet loss statistics, and point-by-point packet loss based on the detection results. At least one of statistics, end-to-end delay statistics, and point-by-point delay statistics.

If the detection task is TWAMP packet measurement, the detection is performed between the head node and the tail node, and it is not necessary to perform steps 105 to 106.

In the embodiment of the present application, by adding an object identifier to an MPLS label, it is realized that the detection object at different levels adopts a universal identifier, reduces the analysis depth of the intermediate node, and can implement point-by-point performance detection. In addition, the object identifier can be extended to add a tag field, which can carry one or more types of information, and serves as an instruction, which can meet the requirements of more flexibility and scalability.

For the controller side, the controller assigns the object identifier as an example. As shown in FIG. 5, the method for implementing MPLS network detection in the embodiment of the present application includes:

Step 201: The controller assigns an object identifier to a detection object in the MPLS network.

The detection object may include at least one of the following: a tunnel, a service flow, and a PW. That is, the object identifier is a general object identifier, which can represent a service flow, and can also represent a tunnel, a PW, and the like.

In step 202, the controller sends the detection task and the information of the detection object including the object identifier to each node in the detection domain corresponding to the detection object, so that the node according to the detection task and according to the object identifier Perform a detection operation on the service packets matching the detection object.

The information of the detection object may include, in addition to the object identifier, a tunnel identifier, characteristic information of a service flow (such as an IP quintuple), a PW identifier, and the like according to different detection objects.

The detection task may include: counting service packets, tracking tunnel paths, performing in-band performance statistics by alternately colored markers, and measuring TWAMP packets.

As shown in FIG. 6, in an embodiment, after step 202, the method further includes: step 203: The controller receives a detection result sent by the node, and performs statistics on the detection result.

In an embodiment, the detection task includes: counting service packets, and the step 203 includes: the controller performs traffic statistics, end-to-end packet loss statistics, and point-by-point packet loss according to the detection results. At least one of the statistics.

In an embodiment, the detection task includes: tunnel path tracking, and the step 203 includes: the controller counts complete tunnel path information according to the detection result.

In an embodiment, the detection task includes: performing in-band performance statistics, and the step 203 includes: the controller performs traffic statistics, end-to-end packet loss statistics, and point-by-point packet loss according to the detection results. At least one of statistics, end-to-end delay statistics, and point-by-point delay statistics.

If the detection task is TWAMP packet measurement, detection is performed between the head node and the tail node, and step 203 need not be performed.

In the embodiment of the present application, by adding an object identifier to an MPLS label, detection objects at different levels are implemented with a universal identifier, and point-by-point performance detection can be implemented.

For the node side, it can be divided into head node, middle node and tail node. The controller sends routing information to the nodes in the detection domain, and the node learns whether it is a head node, an intermediate node, or a tail node according to the routing information.

The head node of the detection domain (Ingress, PE, Ingress, Provider Edge) identifies the service flow when the packet enters, and adds the corresponding object identifier to the service flow;

Intermediate nodes (P, Provider, and core device) in the detection domain can identify service flows and complete performance statistics based on the object identifiers in the MPLS label stack without further parsing the IP quintuple in the payload, reducing the packet Parsing depth.

The tail node of the detection domain (egress, PE, edge output device of the operator) pops up the object identification and other labels in the label stack, and restores the original service packet.

For the node side, as shown in FIG. 7, the method for implementing MPLS network detection in the embodiment of the present application includes:

Step 301: A node in a detection domain determines information of a detection object and a detection task, wherein the information of the detection object includes an object identifier.

In addition to the object identifier, the information of the detected object may include a tunnel identifier, characteristic information of a service flow (such as an IP quintuple), a PW identifier, and the like according to different detected objects.

The nodes in the detection domain may determine the detection task and the information of the detection object by receiving the detection task and the information of the detection object including the object identifier sent by the controller.

In a case where the detection object is identified by a tuple of a head node identifier and an object identifier, the object identifier may also be allocated by the head node in the detection domain, and no controller allocation is required. The detection task may include: counting service packets, tracking tunnel paths, performing in-band performance statistics by alternately colored markers, and measuring TWAMP packets.

Step 302: When the node is the head node of the detection domain, a service packet matching the detection object is identified in the received service flow, and the object is added to the MPLS label of the service packet. Identification, and forwards a service message containing the object identification.

When the detection object includes a tunnel, the information of the detection object further includes a tunnel identifier, and the head node identifies a service packet matching the detection object in the received service flow according to the tunnel identifier.

In one embodiment, the detection object is identified by a tuple of a node identifier and an object identifier. In this step, the object identifier is added to the MPLS label of the service packet, and the forwarding includes the object identifier. An object-identified service message includes: adding a head node identifier and an object identifier to a tuple in the MPLS label of the service message, and forwarding the service message containing the tuple.

In an embodiment, adding the object identifier to the MPLS label of the service packet includes: determining a position of the object identifier in the MPLS label according to the detection object, and according to the position, Adding the object identifier to the MPLS label.

In other words, the position of the object identifier in the MPLS label stack is different according to the detection object.

In an embodiment, adding the object identifier to the MPLS label of the service packet includes: adding a preset guidance label and the object identifier to the MPLS label, and the guidance label is located at all locations. Before the object identification, it is used to indicate the position of the object identification in the MPLS label.

Method one: use special purpose labels to indicate

RFC3032 defines reserved tags of 0-15 as special purposes. At present, there are still some unassigned tag values. Taking the unassigned tag value of 12 as an example, it represents the leading tag of the object identifier. Its frame format is shown in Figure 2.

Which guide label is used in the embodiments of the present application can be selected according to actual conditions.

In an embodiment, the object identifier includes a label domain, and adding the object identifier to an MPLS label of the service packet includes: setting the label domain according to a preset label rule, and An object identifier containing the label domain is added to the MPLS label. By setting the tag field, the object identifier can be extended to support carrying instructions, to meet the requirements of more flexibility and scalability, and to meet the needs of more scenarios.

For example, the detection task includes proactive bidirectional detection of TWAMP packet measurement, and after identifying a service packet matching the detection object in the received service flow, the method further includes: inserting a TWAMP packet into the service flow Text, the MPLS label of the TWAMP message carries an object identifier containing the tag domain. The value of the tag is different for TWAMP messages and service messages.

Step 303: When the node is a head node, an intermediate node, or a tail node of the detection domain, perform a detection operation on a service packet including the object identifier according to the detection task.

In an embodiment, the detection task includes: counting service packets, and the step 303 includes: performing counting and counting on the service packets sent when the node is a head node of the detection domain; When the node is an intermediate node in the detection domain, count and count the received service packets and the service packets sent respectively; when the node is a tail node in the detection domain, count the received The received service packets are counted.

In one embodiment, the detection task includes: tunnel path tracking, and the step 303 includes: when the node is a head node of the detection domain, the information of the node and the outbound interface information of the service packet are compared with The object identifier is associated, and the associated information is recorded; when the node is an intermediate node in the detection domain, its own node information and the inbound interface information of the service message are associated with the object identifier, And, the self node information and the outbound interface information of the service message are associated with the object identifier, and the associated information is recorded; when the node is the tail node of the detection domain, the self node information, The inbound interface information of the service message is associated with the object identifier, and the associated information is recorded.

In an embodiment, the detection task includes: performing in-band performance statistics, the marker domain includes alternating coloring markers, and the step 303 includes: when the node is a head node of the detection domain, according to the The information of the alternately colored flags is used to count and count the service packets sent out. When the node is an intermediate node in the detection domain, the received and transmitted services are processed according to the information of the alternately colored flags. The packet is counted and counted; when the node is the tail node of the detection domain, the received service packet is counted and counted according to the information of the alternating coloring mark.

In an embodiment, the detection task includes: performing in-band performance statistics, the marker domain includes a delay measurement marker, and the step 303 includes: when the node is a head node of the detection domain, according to the The delay measurement mark information is used to time-stamp the service message and record the time stamp when the service message is sent. When the node is an intermediate node in the detection domain, the delay measurement mark is used. The service information is time stamped on the service message, and the time stamp when the service message arrives and is sent is recorded. When the node is the tail node of the detection domain, the marked information is measured according to the delay. Time stamping the service message and recording the time stamp when the service message arrives.

In an embodiment, the performing a detection operation on a service packet containing the object identifier according to the detection task includes: when the node is a head node of the detection domain, the service packet is sent out. Counting statistics, carrying the value of the counting statistics in the TWAMP message and sending it out; when the node is the tail node of the detection domain, counting statistics of the received service packets, and The value of the counting statistics carried in the TWAMP message is compared with the value of the own counting statistics to obtain a TWAMP measurement result.

In addition, for the tail node of the detection domain, the object identification and other labels in the MPLS label stack are also popped out to restore the original service packet.

As shown in FIG. 8, in an embodiment, after step 303, the method may further include:

Step 304: The node sends a detection result obtained by performing a detection operation to the controller, so that the controller performs statistics.

The following uses some application examples to explain. In the application example, the user identification is called Object ID.

Application Example 1: Carrying Object IDs in SR Scenarios to Implement SR Tunnel Traffic Statistics and Packet Loss Statistics

Taking Figure 9 as an example, A (A is the head node of the detection domain, specifically the operator edge input device), B (B is the intermediate node of the detection domain, specifically the core device), and C (C is the tail node of the detection domain , Specifically the operator edge output device) is a network node in the SR domain, and a controller is deployed to centrally control the network. By using the method in the embodiment of the present application, during the configuration phase, a corresponding Object ID is assigned to an SR-TE (Traffic Engineering) tunnel that needs to be measured. Pass the Object ID in the MPLS label stack. As shown in Figure 9, the Object ID can be set anywhere in the MPLS label stack, either before or after the VPN label. Object ID can be globally unique or node unique. If a globally unique method is used, a specific detection object can be uniquely identified by Object ID. If a node unique method is used, the binary of {head node ID, Object ID} can be used. The group uniquely identifies a specific detection object. In this application example, a globally unique Object ID is used. The process is as follows:

The controller assigns a globally unique Object ID to the SR-TE tunnel of A-> C. In the SR domain, an SR-TE tunnel consists of a series of segments representing nodes or links, that is, a segment list. Object ID is used to identify a unique SR-TE tunnel, which is equivalent to Path ID in this embodiment.

The controller sends the information of the object to be detected to each device on the tunnel path, and the information includes SR tunnel information, such as a tunnel identifier (tunnel ID) and a globally unique Object ID assigned to the tunnel.

Node A identifies the incoming packets and adds the corresponding Object ID to the service packets that need to enter this SR-TE tunnel. Because the detected object is a tunnel, the Object ID is placed after the SR tunnel label and before the service label. Here, a special-purpose label is used as a guide label as an example. The complete frame format is shown in FIG. 10.

The node A sends the message from the corresponding port according to the outer SR label, and at the same time counts based on the Object ID to generate the node A sending counter A_Tx_Cnt.

After receiving the service packet, node B retrieves the MPLS label stack, extracts the object ID in the label stack, and counts based on the object ID to generate the reception counter B_Rx_Cnt of node B.

Node B sends the message from the corresponding port according to the outer SR label, and counts based on the Object ID to generate a node B sending counter B_Tx_Cnt.

After receiving the service packet, the node C retrieves the MPLS label stack, extracts the object ID in the label stack, and counts based on the object ID to generate a reception counter C_Rx_Cnt of the node C.

The C node strips the VPN (Virtual Private Network) label and the Object ID, restores the service packet, and sends it to the client device.

The controller collects the counter statistics of each node to implement SR tunnel traffic statistics.

The controller compares the counter statistics of each point to achieve end-to-end packet loss measurement or point-by-point packet loss measurement of the SR tunnel.

Application Example 2: Carrying Object ID in SR Scenario to Realize Path Tracking of SR Tunnel

The SR tunnel implements the restriction of the service path through the segment list, but the paths between the constrained nodes rely entirely on the shortest path principle of IGP (Interior Gateway Protocol) to implement routing. IGP routing results will also be caused by topology changes and other reasons. With this change, a method for obtaining the actual path of the business in real time is needed, and path tracking can be used to implement this method.

Taking Figure 11 as an example, A, B, C, D, E, and F are network nodes in the SR domain. An SR-TE tunnel from node A to node F is deployed, and the segment list used is {C, F}. There are multiple paths in the network to reach node C and node F, and the method of the embodiment of the present application is used to implement path tracking. During the configuration phase, the corresponding Object ID is assigned to the SR-TE tunnel of {C, F}. The Object ID is pushed into the MPLS label stack and passed. Object ID can be globally unique or node unique. If a globally unique method is used, a specific detection object can be uniquely identified by Object ID. If a node unique method is used, the binary of {head node ID, Object ID} can be used. The group uniquely identifies a specific detection object. In this embodiment, a unique Object ID of the node is used. The process is as follows:

Node A assigns a unique Object ID for the SR-TE tunnel of A-> F. In the SR domain, the SR-TE tunnel is composed of a series of segments representing nodes or links, that is, segment lists. In this application example, segment lists are {C, F}. Object ID is used to identify this SR-TE tunnel of {C, F}, which is equivalent to Path ID in this application example.

The controller sends the information of the object to be tracked to each device in the SR domain. The information includes SR tunnel information, such as tunnel ID.

Node A recognizes the incoming packet, and adds the corresponding {header ID, Object ID} two-tuple to the service packets that need to enter the SR-TE tunnel (in this application example, the two-tuple The head node ID is node A.) Because the detected object is a tunnel, the Object ID is placed after the SR tunnel label and before the service label. Here, a special-purpose label is used as a guide label as an example. The complete frame format is shown in Figure 12.

Node A sends the packet from the corresponding port according to the outer SR label. At the same time, it records the node and outbound interface information and associates it with the Object ID. The recorded information is {{Node A ID, Object ID}, Node A, Tx interface}.

After receiving the service packet, node B retrieves the MPLS label stack, extracts the {node AID, object ID} binary group in the label stack, records the node and incoming interface information at the same time, and associates it with the binary group. The recorded information is {{Node A ID, Object ID}, Node B, Rx interface}.

Node B sends the message from the corresponding port according to the outer SR label, and records the node and outbound interface information, and associates it with the {node AID, Object ID} tuple, and the recorded information is { {Node A ID, Object ID}, Node B, Tx interface}.

After receiving the business packet, node C retrieves the MPLS label stack, extracts the {node AID, object ID} binary group in the label stack, records the node and incoming interface information at the same time, and associates it with the binary group. The recorded information is {{Node A ID, Object ID}, Node C, Rx interface}.

The C node pops up the outermost Node C label, finds the next SR label, and sends the message from the corresponding port. At the same time, it records the node and outbound interface information, and it is binary with {Node A ID, Object ID} Groups are associated, and the recorded information is {{section APoint ID, Object ID}, Node C, Tx interface}.

After the E node receives the service packet, it retrieves the MPLS label stack, extracts the {node AID, Object ID} binary group in the label stack, records the node and incoming interface information at the same time, and associates it with the binary group. The recorded information is {{Node A ID, Object ID}, Node E, Rx interface}.

The E node sends the message from the corresponding port according to the outer SR label, and records the node and outbound interface information, and associates it with the {node AID, Object ID} tuple, and the recorded information is { {Node A ID, Object ID}, Node E, Tx interface}.

After the F node receives the service packet, it retrieves the MPLS label stack, extracts the {node AID, Object ID} binary group in the label stack, records the node and incoming interface information at the same time, and associates it with the binary group. The recorded information is {{Node A ID, Object ID}, Node F, Rx interface}.

The F node sends the message from the corresponding port according to the outer SR label, and records the node and outbound interface information, and associates it with the {node AID, Object ID} tuple, and the recorded information is { {Node A ID, Object ID}, Node F, Tx interface}.

The F node strips the VPN tag and the {node A ID, Object ID} tuple, restores the service packet, and sends it to the client device.

All nodes report the recorded path tracking information to the controller, and the controller summarizes the statistics of the complete tunnel path information.

Application Example 3: Carrying Object IDs in MPLS Scenarios to Implement Traffic Statistics and Packet Loss Measurement of Service Flows

Taking Figure 9 as an example, A (A is the head node of the detection domain, specifically the operator edge input device), B (B is the intermediate node of the detection domain, specifically the core device), and C (C is the tail node of the detection domain , Specifically the operator edge output device) is a network node in the MPLS domain, and a controller is deployed to centrally control the network. Using the method of the embodiment of the present application, in the configuration stage, the corresponding Object ID is assigned to the service flow that needs to be measured. The Object ID is pushed into the MPLS label stack and passed. Object ID can be globally unique or node unique. If a globally unique method is used, a specific detection object can be uniquely identified by Object ID. If a node unique method is used, the binary of {head node ID, Object ID} can be used. The group uniquely identifies a specific detection object. In this embodiment, a globally unique Object ID is used. The process is as follows:

The controller assigns a globally unique Object ID to a service flow of A-> C to be measured. Service flows are identified by IP 5-tuples, and Object ID is used to identify a unique service flow.

The controller sends the information of the object to be detected to each device on the tunnel path. The information includes the characteristic information of the service flow, such as the IP quintuple and the globally unique Object ID assigned to the service flow.

Node A identifies the incoming packets, and adds the corresponding Object ID to the service flows that match the characteristic information. Since the detected object is a service flow, the Object ID is placed behind the service label, which is the position at the bottom of the stack. The use label is taken as an example of the guide label. The complete frame format is shown in Figure 13.

Node A sends packets from the corresponding port according to the outer MPLS label, and counts based on the Object ID to generate a node A sending counter A_Tx_Cnt.

After receiving the service packet, node B retrieves the MPLS label stack, extracts the object ID in the label stack, and counts based on the object ID to generate the receiving counter B_Rx_Cnt of node B without identifying the IP quintuple in the user payload.

Node B sends packets from the corresponding port according to the outer MPLS label, and at the same time counts based on the Object ID to generate a Node B send counter B_Tx_Cnt.

Node C strips the VPN label and Object ID, restores the service packet, and sends it to the client device.

The controller collects the counter statistics results of each node to realize the traffic flow statistics.

The controller compares the counter statistics of each point to achieve end-to-end packet loss measurement or point-by-point packet loss measurement of the service flow.

Application Example Four: Extending Object ID to Implement Alternate Color Marking Function

Alternately colored markers are an in-band performance statistics method. Through alternately colored markers, performance measurements such as packet loss and delay can be achieved. For IP services, the tag field is generally located in the IP header. IPv4 uses reserved bits and IPv6 uses extension headers, which are not applicable to MPLS networks. In the MPLS scenario, you can implement the color marking function by extending the Object ID.

Taking Figure 9 as an example, A (A is the head node of the detection domain, specifically the operator edge input device), B (B is the intermediate node of the detection domain, specifically the core device), and C (C is the tail node of the detection domain , Specifically the operator edge output device) is a network node in the MPLS domain, and a controller is deployed to centrally control the network. By adopting the method of the embodiment of the present application, during the configuration phase, the corresponding Object ID is assigned to the service flow to be measured, and the Object ID carrying tag field is extended to realize the measurement of packet loss and delay. Object ID can be globally unique or node unique. If a globally unique method is used, a specific detection object can be uniquely identified by Object ID. If a node unique method is used, the binary of {head node ID, Object ID} can be used. The group uniquely identifies a specific detection object. In this application example, a globally unique Object ID is used. The process is as follows:

In the 20 bits used to represent the Object ID, 2 bits are reserved as a tag field, so that the remaining 18 bits can be used to indicate the identification of the measurement object. Alternating coloring schemes generally use the double labeling method, which uses two labeling domains, C bit and D bit, where C bit indicates the alternate coloring mark and D bit indicates the delay measurement mark.

Node A identifies the incoming packets, and adds the corresponding Object ID to the service flows that match the characteristic information. Since the detected object is a service flow, the Object ID should be placed after the service label, which is the bottom of the stack. As an example, the special-purpose label is used as the guide label. The complete frame format is shown in Figure 14.

The A node periodically flips C bits according to the set rules, such as setting C = 0 in the first cycle, setting C = 1 in the second cycle, setting C = 0 in the third cycle, etc., to implement the alternate coloring function. At the same time, the message is periodically sampled. Set the sampled message to D = 1 to indicate that the delay needs to be measured. The default setting of other messages is D = 0 to indicate that the delay is not required to be measured.

Node A sends the message from the corresponding port according to the outer MPLS label, and counts based on the object ID and C bit color information. For example, if the message C = 0, Cnt0 is used for counting, and C = 1, Cnt1 is used for counting. Count and generate A node sending counters A_Tx_Cnt0 and A_Tx_Cnt1.

The A node performs time stamp marking based on the object ID and D bit information. For a message of D = 1, the time stamp when the message is sent is recorded as A_Tx_Timestamp.

After receiving the service packet, node B retrieves the MPLS label stack, extracts the object ID in the label stack, and counts based on the object ID and the carried color information to generate the reception counters B_Rx_Cnt0 and B_Rx_Cnt1 of node B without identifying the user payload. IP quintuple in.

The B node performs timestamp marking based on the information of the Object ID and the D bit. For a message of D = 1, the timestamp of the arrival and departure of the message is recorded as B_Rx_Timestamp and B_Tx_Timestamp.

Node B sends the message from the corresponding port according to the outer MPLS label, and counts based on the Object ID and the color information carried by it, and generates Node B sending counters B_Tx_Cnt0 and B_Tx_Cnt1.

After receiving the service packet, the node C retrieves the MPLS label stack, extracts the object ID in the label stack, and counts based on the object ID and the color information carried by it, and generates the reception counters C_Rx_Cnt0 and C_Rx_Cnt1 of the node.

The C node performs timestamp marking based on the object ID and D bit information. For a message of D = 1, the timestamp when the message arrives is recorded as C_Rx_Timestamp.

The controller compares the statistical results of the counters at each point with the recorded time stamps, and implements functions such as end-to-end packet loss measurement, point-by-point packet loss measurement, end-to-end delay measurement, and point-by-point delay measurement.

Application Example 5: Extending Object ID to Distinguish Business Packets from TWAMP Packets

TWAMP is a widely used active measurement method, but it measures packet loss and delay of TWAMP packets, and cannot truly reflect the performance of the service. Therefore, TWAMP proposes an extension to achieve direct service measurement. The principle is shown in Figure 15. By inserting a series of TWAMP messages into the service message as a statistical delimitation frame, the head node counts the messages by identifying the service message and carries the count value in the TWAMP message. Pass to the tail node. The tail node can obtain the count of the packets sent by the head node and compare it with the count of the packets received at this point, to achieve end-to-end packet loss measurement. This method does not require the controller to perform centralized performance analysis, and the deployment is more flexible.

The direct measurement method of TWAMP requires that the network element can identify and distinguish the service flow to be counted and its corresponding TWAMP message. The traditional method is to identify the service message by the UDP (User Datagram Protocol) port number in the IP message. It is still a TWAMP message, but this method requires the network element to have deep message analysis capabilities. By adopting the method in the embodiment of the present application, it is possible to distinguish service packets and TWAMP packets by extending Obeject ID, and the network element can be identified in the MPLS label stack, which greatly reduces the depth of analysis.

Taking Figure 9 as an example, A (A is the head node of the detection domain, specifically the operator edge input device), B (B is the intermediate node of the detection domain, specifically the core device), and C (C is the tail node of the detection domain , Specifically the operator edge output device) is a network node in the MPLS domain, and a controller is deployed to centrally control the network. By using the method in the embodiment of the present application, during the configuration phase, the corresponding Object ID is assigned to the service flow to be measured, and the Object ID carrying tag field is extended to realize the measurement of packet loss and delay.

1 bit is reserved as a tag field among the 20 bits used to represent the Object ID, so that the identifier that can be used to represent the measurement object has 19 bits remaining. The TWAMP direct measurement solution reserves a Tbit for tagging services and TWAMP messages.

Node A identifies the incoming packets, and adds the corresponding Object ID to the service flows that match the characteristic information. Since the detected object is a service flow, the Object ID should be placed after the service label, which is the bottom of the stack. As an example, the special-purpose label is used as the guide label. The complete frame format is shown in Figure 16. T bit = 0 of the marked service flow.

Node A generates a TWAMP message according to a certain period and inserts it into the service flow. In order to correspond to the service message to be detected, the TWAMP message needs to have the same Object ID as the service message, but the tag field Tbit = 1. Its complete frame format is shown in Figure 17.

Node A sends the message from the corresponding port according to the outer MPLS label, and at the same time counts based on the Object ID, generates a node A sending counter A_Tx_Cnt, and carries this count value in the TWAMP message for transmission.

Node B forwards according to the MPLS label.

The C node recognizes that the message with Tbit = 1 is a TWAMP message, takes out the A_Tx_Cnt count value carried in the TWAMP message, and compares it with C_Rx_Cnt to complete end-to-end packet loss statistics.

Application Example 6: Implementing Object ID in MPLS Scenarios to Implement Point-by-Point Traffic Statistics and Packet Loss Measurement of Pseudo-Wires

In the MPLS scenario, pseudowires can be represented by pseudowire labels, but pseudowire labels are unique within a node and not globally unique. Therefore, the traditional mechanism based on pseudo-wire labels for traffic statistics and packet loss measurement can only achieve end-to-end measurement, but cannot support point-by-point measurement. Point-by-point measurement of pseudo-lines can be achieved by using Object ID.

Taking Figure 9 as an example, A (A is the head node of the detection domain, specifically the operator edge input device), B (B is the intermediate node of the detection domain, specifically the core device), and C (C is the tail node of the detection domain , Specifically the operator edge output device) is a network node in the MPLS domain, and a controller is deployed to centrally control the network. Using the method of the embodiment of the present application, in the configuration stage, the corresponding Object ID is assigned to the pseudo wire to be measured. The Object ID is pushed into the MPLS label stack and passed. Object ID can be globally unique or node unique. If a globally unique method is used, a specific detection object can be uniquely identified by Object ID. If a node unique method is used, the binary of {head node ID, Object ID} can be used. The group uniquely identifies a specific detection object. In this embodiment, a globally unique Object ID is used. The process is as follows:

The controller assigns a globally unique Object ID to a pseudo-wire of A-> C to be measured. The pseudo line is identified by a pseudo line ID, and the Object ID is used to identify a unique pseudo line.

The controller sends the information of the object to be detected to each device on the tunnel path. The information includes the characteristic information of the pseudowire, such as the pseudowire identification (PWID) and the globally unique ObjectID assigned to the pseudowire.

Node A identifies the incoming packets and adds the corresponding Object ID to the business packets that need to enter this pseudo-wire. Since the detected object is a pseudo-wire, the Object ID is placed after the PW tag. Here, the extension tag + extension As an example, the special-purpose label is used as the guide label. The complete frame format is shown in Figure 18.

Node C strips the PW label and Object ID, restores the service packet, and sends it to the client device.

The controller compares the counter statistics of each point to achieve end-to-end packet loss measurement or point-by-point packet loss measurement of the pseudowire.

As shown in FIG. 19, an embodiment of the present application further provides an apparatus for implementing MPLS network detection, which is applied to detecting a node in a domain and includes:

The determining module 41 is configured to determine information of a detection object and a detection task, wherein the information of the detection object includes an object identifier;

The processing module 42 is configured to, when the device is located at the head node of the detection domain, identify a service packet matching the detection object in the received service flow, and add the service packet to the MPLS label of the service packet. The object identifier is described, and a service message including the object identifier is forwarded; and

The detection module 43 is configured to perform a detection operation on a service packet including the object identifier according to the detection task.

The detection object includes at least one of the following: a tunnel, a service flow, and a PW.

In an optional embodiment of the present application, the processing module 42 is configured to identify a service packet that matches the detection object in the received service flow includes at least one of the following: the detection object includes When tunneling, the information of the detection object further includes a tunnel identifier, and the head node identifies a service packet that matches the detection object in the received service flow according to the tunnel identifier; the detection object includes a service flow At the time, the information of the detection object further includes characteristic information of the service flow, and the head node identifies a service packet matching the detection object in the received service flow according to the characteristic information of the service flow; the When the detection object includes a PW, the information of the detection object further includes a PW identifier, and the head node identifies a service packet that matches the detection object in the received service flow according to the PW identifier.

In an optional embodiment of the present application, the detection object is identified by a tuple of a node identifier and an object identifier, and the device for implementing MPLS network detection is applied to detect a head node in the domain, and the determining Module 41 is configured to allocate the object identifier.

In an optional embodiment of the present application, the detection object is identified by a tuple of a node identifier and an object identifier, and the processing module 42 is configured to add a header to the MPLS label of the service packet. The node identifier and the object identifier are a tuple, and a service packet including the tuple is forwarded.

In an optional embodiment of the present application, the processing module 42 is configured to determine a position of the object identifier in the MPLS label according to the detection object, and according to the position, in the MPLS label Add the object identifier.

In an optional embodiment of the present application, the processing module 42 is configured to add a preset guidance label and the object identifier to the MPLS label, where the guidance label is located before the object identifier, and To indicate the position of the object identifier in the MPLS label.

In an optional embodiment of the present application, the preset guide label includes at least one of the following: a special-purpose label; a combination of an extended label and an extended special-use label.

In an optional embodiment of the present application, the object identifier includes a tag field, and the processing module 42 is configured to set the tag field according to a preset tag rule, and add the tag field to the MPLS label. The object identifier of the tag field.

In an optional embodiment of the present application, the detection task includes active bidirectional detection of TWAMP packet measurement, and the processing module 42 is configured to identify a service matching the detection object in the received service flow. After the message, a TWAMP message is inserted into the service flow. The MPLS label of the TWAMP message carries an object identifier containing the tag field, and the tag type indicates that the message type is a TWAMP message.

In an optional embodiment of the present application, the detection module 43 is configured to count and count the service packets sent when the node applied by the device is the head node of the detection domain. The statistical value is carried in the TWAMP message and sent out; when the node applied by the device is the tail node of the detection domain, the received statistics of the service message are counted, and the received TWAMP message is counted. The value of the count statistics carried in the packet is compared with the value of its own count statistics to obtain the TWAMP measurement result.

In an optional embodiment of the present application, the detection task includes: performing in-band performance statistics, the flag field includes alternating coloring flags, and the detection module 43 is configured as a node applied by the device. When the head node of the detection domain is described, the service packets sent are counted and counted according to the information of the alternate coloring flag; when the node applied by the device is an intermediate node of the detection domain, the coloring is performed according to the alternate coloring. The marked information counts the received and sent service packets. When the node applied by the device is the tail node of the detection domain, the received colored information is used to calculate the received all the received messages. Count the business messages.

In an optional embodiment of the present application, the detection task includes: performing in-band performance statistics, the flag field includes a delay measurement flag, and the detection module 43 is configured as a node applied by the device as When the head node of the domain is detected, time stamping the service message according to the information of the delay measurement flag, and recording the time stamp when the service message is sent; the node applied by the device is the When detecting an intermediate node in the domain, the service message is time stamped according to the information of the delay measurement mark, and the time stamp of the service message arrival and sending is recorded; the node applied by the device is When the tail node of the detection domain is described, the service message is time stamped according to the information of the delay measurement mark, and the time stamp when the service message arrives is recorded.

In an optional embodiment of the present application, the detection task includes: counting service packets, and the detection module 43 is configured to: when a node applied by the device is a head node of the detection domain, Counting and counting of the service messages sent out; when the node applied by the device is an intermediate node in the detection domain, counting and counting the service messages received and the service messages sent out respectively; When the node applied by the device is a tail node of the detection domain, counting and statistics are received on the received service packets.

In an optional embodiment of the present application, the detection task includes: tunnel path tracing, and the detection module 43 is configured to: when a node applied by the device is a head node of the detection domain, self-node information 2. The outbound interface information of the service message is associated with the object identifier, and the associated information is recorded; when the node applied by the device is an intermediate node in the detection domain, the information of the own node and the service are recorded. The inbound interface information of the message is associated with the object identifier, and the own node information and the outbound interface information of the service message are associated with the object identifier to record the associated information; the device application When the node is the tail node of the detection domain, the node information and the inbound interface information of the service message are associated with the object identifier, and the associated information is recorded.

In an optional embodiment of the present application, the detection module 43 is configured to send a detection result obtained by performing the detection operation after performing a detection operation on a service packet including the object identifier according to the detection task. To the controller to enable the controller to perform statistics.

It should be noted that when implementing the MPLS network detection device provided in the foregoing embodiment, when performing the MPLS network detection, only the above-mentioned division of the program modules is used as an example. In actual applications, the above processing may be allocated by different The program module is completed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the device for implementing MPLS network detection provided in the foregoing embodiment belongs to the same concept as the method for implementing MPLS network detection. The specific implementation process is described in the method embodiment, and is not repeated here.

As shown in FIG. 20, an embodiment of the present application further provides a device for implementing MPLS network detection, which is applied to a controller and includes:

An allocation module 51 configured to allocate an object identifier to a detection object in the MPLS network;

The sending module 52 is configured to send information and a detection task of the detection object including the object identifier to each node in the detection domain corresponding to the detection object, so that the node performs the detection task on the basis of the object identifier. A service operation is performed on the service packets matching the detection object.

In an optional embodiment of the present application, the apparatus further includes a receiving module configured to receive a detection result sent by the node, and perform statistics on the detection result.

In an optional embodiment of the present application, the detection task includes: counting service packets, and the device further includes a processing module configured to perform traffic statistics and end-to-end packet loss according to the detection result. At least one of statistics and point-by-point packet loss statistics.

In an optional embodiment of the present application, the detection task includes: tunnel path tracking, and the device further includes a processing module configured to count complete tunnel path information according to the detection result.

In an optional embodiment of the present application, the detection task includes: performing in-band performance statistics, and the device further includes a processing module configured to perform traffic statistics and end-to-end packet loss according to the detection results. At least one of statistics, point-by-point packet loss statistics, end-to-end delay statistics, and point-by-point delay statistics.

It should be noted that when implementing the MPLS network detection device provided in the foregoing embodiment, when performing MPLS network detection, only the above-mentioned division of the program modules is used as an example. In actual applications, the above processing may be allocated by different The program module is completed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the device for implementing MPLS network detection provided in the foregoing embodiment belongs to the same concept as the method for implementing MPLS network detection. The specific implementation process is described in the method embodiment, and is not repeated here.

As shown in FIG. 21, an embodiment of the present application further provides a network device, including: a memory 61, a processor 62, and a computer program 63 stored on the memory 61 and executable on the processor 62. The processor 62 When the program is executed, an implementation method of MPLS network detection applied to a node in a detection domain in the embodiment of the present application is implemented.

As shown in FIG. 22, an embodiment of the present application further provides a controller, including: a memory 71, a processor 72, and a computer program 73 stored on the memory 71 and executable on the processor 72. The processor 72 When the program is executed, the method for implementing MPLS network detection applied to the controller in the embodiment of the present application is implemented.

An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions for performing MPLS network detection in a node or controller in a detection domain in the embodiments of the present application. Implementation method.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed components are coupled, or directly coupled, or communicated with each other through some interfaces. The indirect coupling or communication connection of the device or unit may be electrical, mechanical, or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, which may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above integration The unit can be implemented in the form of hardware, or in the form of hardware plus software functional units.

A person of ordinary skill in the art may understand that all or part of the steps of the foregoing method embodiments may be completed by a program instructing related hardware. The foregoing program may be stored in a computer-readable storage medium. Including the steps of the above method embodiment; and the foregoing storage medium includes: a mobile storage device, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, etc. A medium on which program code can be stored.

Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application that are essentially or contribute to the existing technology can be embodied in the form of software products. The computer software product is stored in a storage medium and includes several instructions for A computer device (which may be a personal computer, a server, or a network device) is caused to perform all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes: various types of media that can store program codes, such as a mobile storage device, a ROM, a RAM, a magnetic disk, or an optical disc.

The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflicts to obtain new method embodiments.

The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflicts to obtain new product embodiments.

The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict, to obtain a new method embodiment or device embodiment.

The above are only specific embodiments of the present invention, but the scope of protection of the present invention is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present invention. It should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

A method for implementing multi-protocol label switching MPLS network detection includes:

A node in the detection domain determines information of a detection object and a detection task, wherein the information of the detection object includes an object identifier;

When the node is the head node of the detection domain, a service packet that matches the detection object is identified in the received service flow, the object identifier is added to the MPLS label of the service packet, and the packet is forwarded. A business message including the object identifier;

When the node is a head node, an intermediate node, or a tail node of the detection domain, a detection operation is performed on a service packet including the object identifier according to the detection task.
The method according to claim 1, wherein the detection object comprises at least one of the following:

Tunnel, service flow, pseudo-wire PW.
The method according to claim 2, wherein the identifying a service packet matching the detection object in the received service flow comprises at least one of the following:

When the detection object includes a tunnel, the information of the detection object further includes a tunnel identifier, and the head node identifies a service packet matching the detection object in the received service flow according to the tunnel identifier;

When the detection object includes a service flow, the information of the detection object further includes characteristic information of the service flow, and the head node recognizes that the detection object matches the detection object in the received service flow according to the characteristic information of the service flow. Business messages;

When the detection object includes a PW, the information of the detection object further includes a PW identifier, and the head node identifies a service packet that matches the detection object in the received service flow according to the PW identifier.
The method according to claim 1, wherein the detection object is identified by a tuple of a node identifier and an object identifier, and the node in the detection domain determines information of the detection object and a detection task, comprising: the detection The head node in the domain allocates the object identifier.
The method according to claim 1, wherein the detection object is identified by a tuple of a node identifier and an object identifier, and the object identifier is added to an MPLS label of the service packet, and the forwarding includes all the identifiers. The business message describing the object identification includes:

Add a tuple of the head node identifier and the object identifier to the MPLS label of the service message, and forward the service message containing the double group.
The method according to claim 1, wherein the adding the object identifier to an MPLS label of the service packet comprises: determining a position of the object identifier in the MPLS label according to the detection object, According to the position, the object identifier is added to the MPLS label.
The method according to claim 1, wherein adding the object identifier to an MPLS label of the service message comprises: adding a preset guide label and the object identifier to the MPLS label, and The guide label is located before the object identifier, and is used to indicate the position of the object identifier in the MPLS label.
The method of claim 7, wherein the preset guide label comprises at least one of the following: a special-purpose label; a combination of an extended label and an extended special-use label.
The method according to claim 1, wherein the object identifier includes a tag field, and the adding the object identifier to an MPLS label of the service packet comprises:

The tag domain is set according to a preset tag rule, and an object identifier containing the tag domain is added to the MPLS label.
The method according to claim 9, wherein the detection task comprises proactive two-way detection of TWAMP packet measurement, and after identifying a service packet matching the detection object in the received service flow, further comprising:

A TWAMP message is inserted into the service flow. The MPLS label of the TWAMP message carries an object identifier including the tag field, and the tag field indicates that the message type is a TWAMP message.
The method according to claim 10, wherein the performing a detection operation on a service packet containing the object identifier according to the detection task comprises:

When the node is the head node of the detection domain, perform count statistics on the service packets sent, and carry the value of the count statistics in the TWAMP packet and send it out;

When the node is the tail node of the detection domain, perform count statistics on the received service packets, and compare the value of the count statistics carried in the received TWAMP packet with the value of its own count statistics To get TWAMP measurement results.
The method according to claim 9, wherein the detection task comprises: performing in-band performance statistics, the flag field includes alternating coloring flags, and according to the detection task, the service report containing the object identifier is reported. Perform detection operations, including:

When the node is the head node of the detection domain, counting and counting the sent service packets according to the information of the alternating coloring mark;

When the node is an intermediate node in the detection domain, counting and counting the received and transmitted service packets according to the information of the alternating coloring mark;

When the node is a tail node of the detection domain, the received service packets are counted and counted according to the information of the alternating coloring mark.
The method according to claim 9, wherein the detection task comprises: performing in-band performance statistics, the flag field includes a delay measurement flag, and according to the detection task, the service including the object identifier is performed. The packet performs detection operations, including:

When the node is the head node of the detection domain, time-stamp the service message according to the information of the delay measurement mark, and record the time stamp when the service message is sent;

When the node is an intermediate node in the detection domain, timestamp the service message according to the information of the delay measurement mark, and record the timestamp when the service message arrives and when it is sent;

When the node is the tail node of the detection domain, time stamping the service message according to the information of the delay measurement flag, and recording the time stamp when the service message arrives.
The method according to claim 1, wherein the detection task comprises: counting service packets, and performing the detection operation on the service packets containing the object identifier according to the detection task, comprising: When the node is the head node of the detection domain, counting and counting the service packets sent out;

When the node is an intermediate node in the detection domain, counting and counting the received service packets and the sent service packets respectively;

When the node is a tail node of the detection domain, perform counting and counting on the received service packets.
The method according to claim 1, wherein the detection task comprises: tracking a tunnel path, and performing the detection operation on a service packet containing the object identifier according to the detection task comprises: the node is the When detecting the head node of the domain, associate its own node information and the outbound interface information of the service message with the object identifier, and record the associated information;

When the node is an intermediate node in the detection domain, associate its own node information and inbound interface information of the service message with the object identifier, and associate its own node information and outbound interface of the service message. The information is associated with the object identifier, and the associated information is recorded;

When the node is the tail node of the detection domain, it associates its own node information and the incoming interface information of the service message with the object identifier, and records the associated information.
The method according to any one of claims 1 to 15, wherein after performing a detection operation on a service packet containing the object identifier according to the detection task, the method further comprises: The detection result obtained by performing the detection operation is sent to the controller, so that the controller performs statistics.
A method for implementing multi-protocol label switching MPLS network detection includes:

The controller assigns an object identifier to a detection object in the MPLS network;

The controller sends the detection task and the information of the detection object containing the object identifier to each node in the detection domain corresponding to the detection object, so that the node performs the detection task on the node according to the object identifier. The service packets that match the detected objects are detected.
The method according to claim 17, wherein after the controller sends the detection object information and the detection task including the object identifier to each node in the detection domain corresponding to the detection object, further comprising:

The controller receives a detection result sent by the node, and performs statistics on the detection result.
The method according to claim 18, wherein the detection task comprises: counting service packets, the controller receiving a detection result sent by the node, and counting the detection result, comprising: the control According to the detection result, the router performs at least one of traffic statistics, end-to-end packet loss statistics, and point-by-point packet loss statistics.
The method according to claim 18, wherein the detection task comprises: tunnel path tracking, the controller receiving the detection result sent by the node, and counting the detection result, comprising: the controller according to the The test result statistics complete tunnel path information.
The method according to claim 18, wherein the detection task comprises: performing in-band performance statistics, the controller receiving the detection result sent by the node, and performing statistics on the detection result, comprising: the control According to the detection result, the router performs at least one of traffic statistics, end-to-end packet loss statistics, point-by-point packet loss statistics, end-to-end delay statistics, and point-by-point delay statistics.
A method for implementing multi-protocol label switching MPLS network detection includes:

The controller assigns an object identifier to the detection object in the MPLS network, and sends the detection task and the information of the detection object containing the object identification to each node in the detection domain corresponding to the detection object;

A node in the detection domain determines information of the detection object and the detection task;

When the node is the head node of the detection domain, a service packet that matches the detection object is identified in the received service flow, the object identifier is added to the MPLS label of the service packet, and the packet is forwarded. A business message including the object identifier;

When the node is a head node, an intermediate node, or a tail node of the detection domain, a detection operation is performed on a service packet including the object identifier according to the detection task.
A device for implementing multi-protocol label switching MPLS network detection includes:

A determination module configured to determine information of a detection object and a detection task, wherein the information of the detection object includes an object identifier;

A processing module configured to identify a service packet that matches the detection object in a received service flow when the device is located at a head node of a detection domain, and add the MPLS label to the service packet An object identifier, and forward a service message including the object identifier; and

The detection module is configured to perform a detection operation on a service packet including the object identifier according to the detection task.
A device for implementing multi-protocol label switching MPLS network detection includes:

An assignment module configured to assign an object identifier to a detection object in the MPLS network;

A sending module configured to send information and detection tasks of a detection object including an object identifier to each node in a detection domain corresponding to the detection object, so that the node performs the detection task and Perform the detection operation on the service packets matching the detection object.
A network device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the processor implements any one of claims 1 to 16 Implementation method of MPLS network detection.
A controller includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the program according to any one of claims 17 to 21 when executing the program. Implementation method of MPLS network detection.
A computer-readable storage medium storing computer-executable instructions for performing a method for implementing MPLS network detection according to any one of claims 1 to 16; or the computer-executable instructions An implementation method for performing MPLS network detection according to any one of claims 17 to 21.