Detection configuration, processing method, system and control, communication equipment, storage medium

Abstract

The embodiment of the present invention provides a detection configuration, processing method, system and control, communication equipment, and storage medium. The detection control equipment only needs to configure the encapsulation nodes and decapsulation nodes in the target IOAM domain corresponding to the target business flow. The detection control equipment does not need to configure the transmission nodes in the target IOAM domain, and does not even need to care about which are the transmission nodes of the target business flow. Therefore, the requirements for the computing power of the detection control equipment are reduced, and the configuration burden of the detection control equipment is reduced. Moreover, because the transmission nodes in the target IOAM domain generate detection reporting instances according to the IOAM header in the target message after the target business flow reaches the node, if the target business flow does not flow through the node, the node will not generate a detection reporting instance for the target business flow and allocate detection resources, so there will be no waste of detection resources, which is conducive to the optimization configuration of network resources.

Description

Technical Field

[0001] The embodiments of the present invention relate to, but are not limited to, the field of communication technology. Specifically, they relate to, but are not limited to, detection configuration, processing method, system and control, communication equipment, storage medium, etc. Background Art

[0002] IOAM (in-suit OAM, also known as in-band OAM) refers to encapsulating the required OAM (Operation Administration and Maintenance) information and data into user data packets and sending them together with the user data, without the need for additional control plane packets to send OAM data. IOAM is a technology that directly detects service flows. It has the advantages of real-time, high measurement accuracy, and true reflection of the actual service message network forwarding quality. It can quickly identify faulty nodes or faulty links in the operating network, and is strongly favored by mobile 5G networks.

[0003] When performing IOAM detection in the related art, the centralized controller needs to configure each node through which the target business flow flows, and then these nodes can generate detection reporting instances according to the configuration, and perform statistics and reporting of detection data based on the detection reporting instances. Therefore, the related art requires the centralized controller to accurately calculate the transmission path of the target business flow, otherwise, the centralized controller will not be able to configure the nodes through which the target business flow actually flows, and it will not be possible for these nodes to perform IOAM detection for the target business flow. Moreover, if a large number of protection paths are set for a business flow in the network, and the centralized controller cannot determine the actual transmission path of the target business flow before the target business flow is transmitted, therefore, in order to ensure the normal execution of IOAM detection of the target business flow, the centralized controller needs to configure all nodes that the target business flow may flow through, which not only leads to a large workload for the centralized controller to configure, but also leads to many nodes being configured by the centralized controller to generate detection reporting instances to allocate detection resources for the target business flow, but ultimately causes a waste of resources because the target business flow does not flow through. Summary of the invention

[0004] The detection configuration, processing method, system and control, communication equipment, and storage medium provided by the embodiments of the present invention mainly solve the following technical problems: the IOAM detection of the target business flow in the related technology depends on the accuracy of the centralized controller's calculation of the transmission path, which easily leads to IOAM detection failure, as well as the large workload of the centralized controller configuration and serious waste of resources.

[0005] In order to solve the above technical problems, an embodiment of the present invention provides an IOAM detection configuration method, including:

[0006] The detection control device sends configuration information to the node that needs to be configured in the target IOAM domain. The target IOAM domain is the IOAM domain that performs IOAM detection on the target business flow. The node that needs to be configured is composed of the encapsulation node and the decapsulation node in the target IOAM domain; the configuration information sent to the encapsulation node is the first configuration information, which includes the flow identifier of the target business flow, the business flow identification feature, and the marking period. The business flow identification feature is used by the encapsulation node to identify the target business flow from the business flow entering the node, and the marking period is used to instruct the encapsulation node to mark the message arriving in the target business flow within the marking period as the target message; the configuration information sent to the decapsulation node is the second configuration information, which includes the flow identifier of the target business flow.

[0007] The embodiment of the present invention further provides an IOAM detection and processing method, including:

[0008] The encapsulation node receives first configuration information sent by the detection control device, where the first configuration information includes a flow identifier, a business flow identification feature, and a marking period of a target business flow;

[0009] The encapsulation node identifies the target service flow from the service flow entering the node according to the service flow identification feature, and performs IOAM encapsulation on the message of the target service flow. The IOAM header added by the encapsulation carries the flow identifier of the target service flow, and the IOAM header of the message arriving in the target service flow within the marking period also carries the target mark indicating that the message is the target message. The IOAM header can be used by the node through which the target message flows to automatically generate a detection reporting instance without receiving the instance configuration information sent by the detection control device;

[0010] The encapsulation node sends the target message to the next node.

[0011] The embodiment of the present invention further provides an IOAM detection and processing method, including:

[0012] The transmission node determines that the message is a target message of a target service flow that needs to be detected by IOAM according to the flow identifier and the target tag in the IOAM header of the received message;

[0013] The transmission node generates a detection and reporting instance of the target service flow at the local node according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows at the local node, wherein the detection and reporting instance includes at least one of an inbound detection and reporting instance and an outbound detection and reporting instance;

[0014] The transmission node sends the target message to the next node.

[0015] The embodiment of the present invention further provides an IOAM detection and processing method, including:

[0016] The decapsulation node determines, based on the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of the target service flow that needs to be detected by the IOAM;

[0017] The decapsulation node generates a detection reporting instance of the target service flow at the node according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows at the node, wherein the detection reporting instance includes at least one of an inbound detection reporting instance and an outbound detection reporting instance;

[0018] The decapsulation node performs IOAM decapsulation on the message of the target service flow according to the instruction of the second configuration information and sends the IOAM decapsulated message to the next node. The second configuration information is sent by the detection control device and includes the flow identifier of the target service flow.

[0019] An embodiment of the present invention further provides a detection control device, the detection control device comprising a first processor, a first memory and a first communication bus;

[0020] The first communication bus is used to realize the connection and communication between the first processor and the first memory;

[0021] The first processor is used to execute one or more programs stored in the first memory to implement the steps of the aforementioned IOAM detection configuration method.

[0022] An embodiment of the present invention further provides a communication device, the communication device comprising a second processor, a second memory and a second communication bus;

[0023] The second communication bus is used to realize the connection and communication between the second processor and the second memory;

[0024] The second processor is used to execute the first IOAM detection processing program stored in the second memory to implement the steps of the aforementioned first IOAM detection processing method; or, the second processor is used to execute the second IOAM detection processing program stored in the second memory to implement the steps of the aforementioned second IOAM detection processing method; or, the second processor is used to execute the third IOAM detection processing program stored in the second memory to implement the steps of the aforementioned third IOAM detection processing method.

[0025] An embodiment of the present invention also provides an IOAM detection and processing system, including an encapsulation node, a decapsulation node, a transmission node and the aforementioned detection control device, the encapsulation node is communicatively connected with the transmission node and the decapsulation node in sequence; the transmission encapsulation node is a communication device for the aforementioned second processor to execute a first IOAM detection processing program, the transmission node is a communication device for the aforementioned second processor to execute a second IOAM detection processing program, and the decapsulation node is a communication device for the aforementioned second processor to execute a third IOAM detection processing program.

[0026] An embodiment of the present invention also provides a storage medium, which stores at least one of an IOAM detection configuration program, a first IOAM detection processing program, a second IOAM detection processing program and a third IOAM detection processing program. The IOAM detection configuration program can be executed by one or more processors to implement the steps of the aforementioned IOAM detection configuration method; the first IOAM detection processing program can be executed by one or more processors to implement the steps of the aforementioned first IOAM detection processing method; the second IOAM detection processing program can be executed by one or more processors to implement the steps of the aforementioned second IOAM detection processing method; the third IOAM detection processing program can be executed by one or more processors to implement the steps of the aforementioned third IOAM detection processing method.

[0027] According to the detection configuration, processing method, system and control, communication equipment, and storage medium provided by the embodiments of the present invention, when it is necessary to detect the target business flow, the detection control device only sends the first configuration information to the encapsulation node in the target IOAM domain and sends the second configuration information to the decapsulation node, without sending the configuration information to the transmission node in the target IOAM domain. After the encapsulation node identifies the target business flow according to the first configuration information, it will perform IOAM encapsulation on the message of the target business flow, and mark the message that arrives at the encapsulation node within the marking period in the IOAM header as the target message. Subsequently, the encapsulation node can send the target message to the next node. Although the transmission node in the target IOAM domain has not received the configuration of the detection control device and cannot generate a detection reporting instance according to the instance configuration information sent by the detection control device, according to the solution provided by the embodiments of the present invention, the transmission node can automatically generate a detection reporting instance of the target business flow at this node according to the information in the IOAM header of the received target message to realize IOAM detection. After the target message is transmitted to the decapsulation node of the target IOAM domain, the decapsulation node can also automatically generate a detection reporting instance of the target service flow at this node according to the information in the IOAM header of the received target message. At the same time, the decapsulation node can also perform IOAM decapsulation on the message of the target service flow according to the flow identifier carried by the detection control device in the second configuration information, so that the message of the target service flow flows out of the IOAM domain. It can be seen that according to the scheme provided by the embodiment of the present invention, the detection control device only needs to configure the encapsulation node and the decapsulation node in the target IOAM domain corresponding to the target service flow. For the transmission nodes in the target IOAM domain, the detection control device does not need to be configured, and does not even need to care about which are the transmission nodes of the target service flow. Therefore, the detection control device does not need to accurately calculate the transmission nodes of the target service flow, let alone consider the working path and the nodes on the protection path of the target service flow, which reduces the requirements for the computing power of the detection control device and reduces the configuration burden of the detection control device. Moreover, because the transmission nodes in the target IOAM domain generate detection reporting instances according to the IOAM header in the target message after the target business flow arrives at the node, that is, detection resources are allocated after the target business flow arrives at the node, if the target business flow does not flow through the node, the node will not generate a detection reporting instance for the target business flow and allocate detection resources, so there will be no waste of detection resources, which is conducive to the optimal configuration of network resources.

[0028] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a schematic diagram of performing IOAM detection on a service flow shown in Embodiment 1 of the present invention;

[0030] Figure 2 A flow chart of an IOAM detection and processing solution provided by an embodiment of the present invention;

[0031] Figure 3 A schematic diagram of a reporting cycle shown in Embodiment 1 of the present invention;

[0032] Figure 4 A flow chart of a communication device determining that a detection and reporting instance is an aging detection and reporting instance provided in Embodiment 1 of the present invention;

[0033] Figure 5 Another flow chart of the communication device provided in the first embodiment of the present invention determining that the detection and reporting instance is an aging detection and reporting instance;

[0034] Figure 6 Another flow chart of the communication device provided in the first embodiment of the present invention determining that the detection and reporting instance is an aging detection and reporting instance;

[0035] Figure 7 A schematic diagram of an IOAM detection and processing solution implemented by the IOAM detection and processing system provided in the second embodiment of the present invention;

[0036] Figure 8 A flow chart of the IOAM detection control solution provided in the second embodiment of the present invention;

[0037] Fig. 9 This is a schematic diagram of the format of an IOAM data header provided in the second embodiment of the present invention;

[0038] Fig.10 A schematic diagram of the functional modules in the IOAM detection and processing system shown in the second embodiment of the present invention;

[0039] Fig.11 A schematic diagram of a flow direction of a target service flow in a core network shown in Embodiment 3 of the present invention;

[0040] Fig.12 A schematic diagram of a hardware structure of a detection control device provided in Embodiment 4 of the present invention;

[0041] Fig.13 A schematic diagram of the hardware structure of the communication device provided in the fourth embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0043] Embodiment 1:

[0044] In related technologies, when a centralized controller performs IOAM detection on a service flow, it will add the network nodes that need to participate in the detection to the IOAM domain corresponding to the target service flow, that is, the target IOAM domain. Figure 1 , the network nodes in the target IOAM 10 can be divided into three roles: encapsulation node (edge ​​node where the service flow enters the IOAM domain) 11, decapsulation node (edge ​​node leaving the IOAM domain) 12, and transmission node (node ​​in the IOAM domain) 13. Then the centralized controller 14 sends configuration information to each network node that is expected to participate in IOAM. The configuration information includes instance configuration information. The instance configuration information is actually issued by the centralized controller 14 for the specific interface of the network node. The centralized controller 14 will indicate the corresponding interface and the flow direction of the target service flow on the interface in the instance configuration information. Each network node generates a detection and reporting instance of the target service flow at the node according to the configuration information, including an inbound detection and reporting instance and an outbound detection and reporting instance, and allocates detection resources for the detection and reporting instance to perform IOAM detection on the target service flow. The encapsulation node 11 performs IOAM encapsulation processing on the message of the target service flow, and encapsulates the information with IOAM detection capability at the bottom of the stack of the MPLS (Multi-Protocol Label Switching) label of the user data message. Subsequently, the nodes through which the target service flow flows measure the network packet loss rate and delay of the messages with IOAM detection capability, and actively report the detection data to the centralized controller 14 through the high-speed information collector. The centralized controller 14 integrates and analyzes the detection data reported by each network node and then presents the analysis results. When the message of the target service flow flows through the decapsulation node 13, the decapsulation node 13 will perform IOAM decapsulation processing on the message.

[0045] It can be seen that whether the IOAM detection for the target business flow can be successfully initiated in the relevant technology depends to a large extent on the correctness of the centralized controller configuration. However, if the target business flow has multiple protection superposition layers and the business volume carried by each node interface is huge in the IOAM domain, the centralized controller calculates the business path of the target business flow based on the routing of the entire network. This work is very complicated and difficult, and the correctness of the IOAM detection configuration is naturally difficult to guarantee.

[0046] Moreover, if there are multiple protection paths (i.e., backup forwarding paths) for a target service flow, the centralized controller will send the IOAM detection configuration to the nodes and interfaces on all possible paths, resulting in the resources allocated to the network element nodes in the entire IOAM domain for implementing IOAM detection being several times more than the actually required IOAM detection, thereby wasting IOAM detection resources in the network nodes.

[0047] In order to solve the above problems, this embodiment provides an IOAM detection and processing solution. The IOAM detection and processing solution is implemented by the cooperation of the detection control device, the encapsulation node, the transmission node and the decapsulation node. Figure 2 A flow chart of the IOAM detection processing scheme is shown:

[0048] S202: The detection control device sends first configuration information to the encapsulation node in the target IOAM domain, and sends second configuration information to the decapsulation node.

[0049] In this embodiment, the detection and control device may be a centralized controller or an IOAM detection and analysis platform. The detection and control device may be deployed on one physical entity or may be deployed on at least two physical entities in a distributed manner.

[0050] During the configuration phase of IOAM detection, the detection control device can send configuration information to the nodes that need to be configured in the target IOAM domain. The so-called target IOAM domain refers to the IOAM domain that performs IOAM detection on the target business flow. According to the IOAM detection processing scheme provided in this embodiment, the detection control device can only configure the encapsulation nodes and decapsulation nodes in the target IOAM domain, so the encapsulation nodes and decapsulation nodes constitute the nodes that need to be configured. It should be understood that during the configuration phase of IOAM detection, the detection control device does not need to configure the transmission nodes between the encapsulation nodes and the decapsulation nodes, so the detection control device does not even need to care about which transmission nodes exist between the encapsulation nodes and the decapsulation nodes, and which interfaces of these transmission nodes the target business flow will flow through.

[0051] The configuration information sent by the detection control device to the encapsulation node is the first configuration information, and the first configuration information includes the flow identifier of the target service flow, the service flow identification feature and the marking period.

[0052] Among them, the service flow identification feature is used to instruct the encapsulation node to identify the target service flow from the service flows flowing into the node. In some examples of this embodiment, the service flow identification feature can be a five-tuple of IP packets, including the destination IP (Internet Protocol), source IP, destination UDP (User Datagram Protocol) port number, source UDP port number and IP DSCP (Differentiated Services Code Point). In some other examples of this embodiment, the service flow identification feature can also be the content of the Layer 2 Ethernet header, including the destination MAC (Media Access Control) and source MAC.

[0053] The marking period is used to instruct the encapsulation node to mark the message of the target service flow that arrives at the encapsulation node within the marking period as the target message. The marking period and the non-marking period are arranged alternately. The encapsulation node marks the message of the target service flow that arrives within the marking period as the target message. The IOAM header of the target message carries the target mark, while the IOAM header of the non-target message does not have the target mark. Therefore, the node in the target IOAM domain can determine whether the message is the target message according to whether the target mark exists in the IOAM header of the message of the target service flow. In some examples of this embodiment, the duration of the non-marking period can be pre-agreed between the detection and control device and each node, or the duration of the non-marking period can be determined according to the length of the marking period, for example, the marking period is equal to the non-marking period, or the length of the non-marking period is an integer multiple of the length of the marking period, etc.

[0054] The flow identifier is used to allow each node in the target IOAM domain to uniquely identify the target business flow, generate a detection and reporting instance, and provide a basis for data statistics reporting based on the detection and reporting instance.

[0055] In some other examples of this embodiment, the first configuration information may also include the inbound interface information of the target service flow entering the encapsulation node, and the inbound interface information may indicate to the encapsulation node the inbound interface of the target service flow entering the encapsulation node. On this basis, when the encapsulation node identifies the target service flow, it does not need to monitor all its interfaces, but only performs matching and identification at the interface indicated by the inbound interface information, which is conducive to reducing the workload of the encapsulation node in identifying the target service flow.

[0056] Considering that the IOAM detection scheme provided in the related art may be occasionally used in the network, and in this scheme, if a node is not configured and does not receive the instance configuration information sent by the detection control device, the node will not detect the corresponding service flow. In this embodiment, the transmission nodes in the target IOAM domain are not configured, but according to the scheme requirements, they also need to generate detection reporting instances for the target service flow, allocate IOAM detection resources, and perform IOAM detection on the target service flow in the subsequent process. Therefore, in order to allow the nodes in the network to determine whether they need to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device, that is, whether they need to automatically detect the target message, the encapsulation node can indicate it in the IOAM header of the target message. In order to allow the encapsulation node to determine whether it needs to indicate the subsequent node, the detection control device can indicate the encapsulation node through the first configuration information: the detection control device carries an automatic detection start indication in the first configuration information, and the automatic detection start indication is used to instruct the encapsulation node to carry an automatic detection identifier in the IOAM header of the target message when performing IOAM encapsulation on the target message. The automatic detection flag is used in the IOAM header of the target message to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device. If the first configuration information does not carry the automatic detection start indication, the encapsulation node does not need to carry the automatic detection flag in the IOAM header of the target message when performing IOAM encapsulation on the target message.

[0057] S204: The encapsulation node identifies the target service flow from the service flows entering the node according to the service flow identification feature, and performs IOAM encapsulation on the message of the target service flow.

[0058] After the encapsulation node receives the first configuration information sent by the detection control device, it can extract the business flow identification feature from it and match the business flow identification feature with the business flow identification feature of each business flow entering this node. If the business flow identification feature of a certain business flow successfully matches the business flow identification feature in the first configuration information, it means that the business flow needs to be detected by IOAM as the target business flow, and the encapsulation node can perform IOAM encapsulation on the message of the target business flow.

[0059] It can be understood that the encapsulation node encapsulates the messages of the target business flow, which is actually to add an IOAM header to these messages. The IOAM header contains the flow identifier of the business flow to which the message belongs, that is, the flow identifier of the target business flow. At the same time, because not all messages in the target business flow need to be detected, usually, a part of the messages in the target business flow is selected as a sample, and then this part of the sample is detected and counted, so as to characterize the overall transmission of the target business flow based on the transmission of the sample. This is somewhat similar to the "mark-recapture method" in biology: the encapsulation tag selects part from the message of the target business flow, and marks these selected messages as "target messages" through the target tag. Subsequently, the target message will continue to be transmitted with the target tag. In this way, for other nodes in the IOAM domain, only the situation of the target message needs to be detected and counted. Therefore, in some examples of this embodiment, the encapsulation node will carry the target tag in the IOAM header selected as the target message. Optionally, in this embodiment, the encapsulation node determines the target message according to the marking period in the first configuration information: the encapsulation node determines the message of the target service flow that arrives at the node within the marking period as the target message, and identifies it with the target tag in the IOAM header of the message.

[0060] In addition, combined with the above introduction, it can be known that if the first configuration information carries an automatic detection start indication, the IOAM header of the target message will also include an automatic detection identifier to indicate whether the node in the target IOAM domain needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device. It can be understood that there are two types of automatic detection identifiers, one is a valid automatic detection identifier, which is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device; the other is an invalid automatic detection identifier. If a node receives a message carrying an invalid automatic detection identifier, although it is determined to be a target message, it will no longer perform IOAM detection on the message. In some examples of this embodiment, the validity of the automatic detection identifier changes with the presence or absence of the target tag.

[0061] S206: The encapsulation node sends the target message to the next node.

[0062] After performing IOAM encapsulation on the message of the target business flow, the encapsulation node can send the target message to the next node. It can be understood that the next node of the encapsulation node may be a transmission node or a decapsulation node, because in some cases, the encapsulation node and the decapsulation node are adjacent in the transmission path of the target business flow.

[0063] In this embodiment, the encapsulation node also needs to perform IOAM detection on the target business flow and report the detection data to the detection control device, so the encapsulation node also needs to generate a detection reporting instance for the target business flow, allocate detection resources and count the detection data. It can be understood that the encapsulation node can only detect the target business flow when it enters from this node, so in this case, the encapsulation node can only generate an inbound detection reporting instance; in some other examples of this embodiment, the encapsulation node can only detect the target business flow when it flows out of this node, so in this case, the encapsulation node can only generate an outbound detection reporting instance. Of course, in some other cases, the encapsulation node needs to detect the target business flow flowing into and out of this node at the same time, so the encapsulation node will generate an inbound detection reporting instance and an outbound detection reporting instance for the target business flow at the same time.

[0064] In some examples of the present embodiment, when the encapsulation node generates an inbound detection reporting instance for the target service flow, it can be generated directly according to the first configuration information. In this case, the first configuration information includes not only the flow identifier of the target service flow, but also the inbound interface information of the target service flow on the encapsulation node. For example, the encapsulation node extracts the flow identifier "11" and the inbound interface information "port1" in the first configuration information, and generates an inbound detection reporting instance "flow id = 11, port1, inbound". For the outbound detection reporting instance of the target service flow on the encapsulation node, the encapsulation node needs to monitor the outbound interface of the target service flow on this node, and "learn" the monitoring results and the IOAM header of the target message to generate: for example, after determining that the target message is at the outbound interface port2 of this node, the encapsulation node generates an inbound detection reporting instance "flow id = 11, port2, outbound" in combination with the flow identifier "11" in the IOAM header of the target message. In some other examples of this embodiment, the inbound detection reporting instance and the outbound detection reporting instance of the encapsulation node are both generated through learning, based on the flow identifier in the IOAM header of the target message and the interface through which the target business flow flows at this node, that is, the inbound interface and the outbound interface.

[0065] In some examples of this embodiment, the IOAM header of the target message carries an automatic detection flag. Therefore, before the encapsulation node generates a detection reporting instance of the target business flow at this node based on the flow identifier in the target message and the interface through which the target business flow flows at this node, the encapsulation node will first determine that the IOAM header of the target message also includes a valid automatic detection flag. The valid automatic detection flag is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device.

[0066] After the encapsulation node generates the detection report instance, it will naturally allocate corresponding detection resources for these detection report instances, such as registers, etc. In addition, the encapsulation node will also report its own detection data to the detection control device, including at least one of the following: the number of target packets counted, the timestamp of the target packet arriving at the inbound interface of this node, and the timestamp of the target packet arriving at the outbound interface of this node.

[0067] The following are several ways for encapsulation nodes to report detection data to the detection control device:

[0068] Method 1: The encapsulation node can send the detection data of the detection reporting instance to the detection control device according to the marking period. For example, the encapsulation node always reports the detection data to the detection control device once after the marking period ends. The reporting period for the encapsulation node to report the detection data is equal to the sum of the marking period and the non-marking period. Figure 3 As shown: the reporting period 30 of the encapsulation node can be divided into a detection period 31 and an idle period 32. Because the encapsulation node does not need to detect non-target messages in the non-marking period, the detection period 31 is equal to the marking period, and the idle period 32 is equal to the non-marking period. Therefore, the reporting period 30 is actually the sum of the marking period and the non-marking period. Therefore, in a reporting period 30, the encapsulation node can start timing from the receipt of the first target message that requires IOAM detection. After the timing length reaches the marking period, it can start preparing to report the detection data to the detection control device.

[0069] Method 2: There is no doubt that because the marking of the target message is carried out according to the marking period, the encapsulation node can also determine whether it is necessary to report the detection data according to whether the message of the target service flow is switched from the target message to the non-target message. If the message of the target service flow is still the target message, it proves that the current detection period has not ended. After the message of the target service flow is switched from the target message to the non-target message, the encapsulation node can determine that it has entered the idle period, so it can start to prepare to report the detection data to the detection control device.

[0070] In addition to the encapsulation nodes, the transmission nodes and decapsulation nodes will also perform IOAM detection and report the detection data of the corresponding detection reporting instance to the detection control device. In order to facilitate the detection control device to integrate and analyze the detection data reported by the three, it should be ensured that the encapsulation nodes, transmission nodes and decapsulation nodes report data to the detection control device at basically the same periodic interval. It should be understood that this does not require the encapsulation nodes, transmission nodes and decapsulation nodes to report data at the same time, but requires that the detection data reported by the three in the same batch is for the same detection object, that is, the same batch of target messages. Therefore, if the encapsulation node reports the detection data to the detection control device based on the marking period, then the transmission node and the decapsulation node should also report the detection data based on the marking period.

[0071] In some examples of this embodiment, the IOAM header of the target message also includes a marking period, so that the transmission node or the decapsulation node can also start timing from the receipt of the first target message that requires IOAM detection. After the timing length reaches the marking period, it starts preparing to report the detection data to the detection control device.

[0072] When encapsulating the target message, the encapsulation node will carry a target tag in the IOAM header to indicate that the message is the target message, and the IOAM header of the target message will not change in the target IOAM domain. Therefore, in this case, the encapsulation node and the transmission node can determine how to report the detection data to the detection control device according to the target tag in the IOAM header of the target service flow message. For example, the encapsulation node and the decapsulation node detect that the message of the target service flow switches from the target message to the non-target message according to the target tag in the IOAM header, and then report the detection data to the detection control device.

[0073] Mode 3: In some other examples of this embodiment, the IOAM header includes an automatic detection flag. Similarly, if the IOAM header of a message carries a certain automatic detection flag (valid automatic detection flag or invalid automatic detection flag), the automatic detection flag of the IOAM header of the message will not change in the target IOAM domain. In this case, the encapsulation node can determine how to report the detection data to the detection control device according to the automatic detection flag. For example, the encapsulation node can report the detection data of the corresponding detection reporting instance to the detection control device after determining that the automatic detection stops according to the automatic detection flag in the IOAM header of the target message.

[0074] Correspondingly, the transmission node and the decapsulation node may also report the detection data after determining that the automatic detection is stopped according to the automatic detection identifier in the IOAM header of the target message.

[0075] S208: The transmission node determines, based on the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of the target service flow that needs to be detected by the IOAM.

[0076] When there is a transmission node between the encapsulation node and the decapsulation node, the transmission node or nodes will receive the target service flow transmitted by the previous node. After receiving a message, if the transmission node finds that the message carries an IOAM header and the IOAM header carries a target tag, it can be determined that the message is the target message, and the target service flow to which the target message belongs can be determined based on the flow identifier in the IOAM header.

[0077] S210: The transmission node generates a detection reporting instance of the target service flow at the local node according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows at the local node.

[0078] In some examples, the transmission node may only detect the target service flow entering from the node, so in this case, the transmission node may only generate an inbound detection report instance; in other examples of this embodiment, the transmission node may only detect the target service flow flowing out of the node, so in this case, the transmission node may only generate an outbound detection report instance. However, in this embodiment, the transmission node detects the target service flow flowing into and out of the node at the same time, so the transmission node will generate an inbound detection report instance and an outbound detection report instance for the target service flow at the same time.

[0079] In this embodiment, the incoming detection reporting instance and the outgoing detection reporting instance of the transmission node are generated by learning, based on the flow identifier in the IOAM header of the target message and the incoming interface and outgoing interface of the target business flow at this node.

[0080] In some examples of this embodiment, the IOAM header of the target message carries an automatic detection flag. Therefore, before the transmission node generates a detection reporting instance of the target business flow at this node based on the flow identifier in the target message and the interface through which the target business flow flows at this node, the transmission node will first determine whether the IOAM header of the target message also includes a valid automatic detection flag.

[0081] After the transmission node generates the detection report instance, it will naturally allocate corresponding detection resources, such as registers, for these detection report instances. In addition, the transmission node will also report its own detection data to the detection control device, including at least one of the following: the number of target messages counted, the timestamp of the target message arriving at the inbound interface of this node, and the timestamp of the target message arriving at the outbound interface of this node. The way in which the transmission node reports its own detection data to the detection control device can be referred to the above introduction, which will not be repeated here.

[0082] S212: The transmission node sends the target message to the next node.

[0083] After the transmission node detects the target message, it can transmit the target message to the next node. It should be understood that the next node of the transmission node can be another transmission node or a decapsulation node. If the next node of the current transmission node is another transmission node, the other transmission node can continue the process of S208-S212 until the next node is a decapsulation node.

[0084] S214: The decapsulation node determines, based on the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of a target service flow that needs to be detected by the IOAM.

[0085] After receiving a message, the decapsulation node finds that the message carries an IOAM header, and the IOAM header carries a target tag, then it can determine that the message is a target message, and can determine the target service flow to which the target message belongs based on the flow identifier in the IOAM header.

[0086] S216: The decapsulation node generates a detection reporting instance of the target service flow at the local node according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows at the local node.

[0087] In some examples, the decapsulation node may only detect the target service flow entering from the node, so in this case, the decapsulation node may only generate an inbound detection report instance; in other examples of this embodiment, the decapsulation node may only detect the target service flow flowing out of the node, so in this case, the decapsulation node may only generate an outbound detection report instance. However, in this embodiment, the decapsulation node detects the target service flow flowing into and out of the node at the same time, so the decapsulation node will generate an inbound detection report instance and an outbound detection report instance for the target service flow at the same time.

[0088] In this embodiment, the inbound detection reporting instance and the outbound detection reporting instance of the decapsulation node are both generated through learning, based on the flow identifier in the IOAM header of the target message and the inbound interface and outbound interface of the target service flow at this node.

[0089] In some examples of this embodiment, the IOAM header of the target message carries an automatic detection identifier. Therefore, before the decapsulation node generates a detection reporting instance of the target business flow at this node based on the flow identifier in the target message and the interface through which the target business flow flows at this node, the decapsulation node will first determine whether the IOAM header of the target message also includes a valid automatic detection identifier.

[0090] After the decapsulation node generates the detection reporting instance, it will naturally allocate corresponding detection resources, such as registers, for these detection reporting instances. In addition, the decapsulation node will also report its own detection data to the detection control device, including at least one of the following: the number of target messages counted, the timestamp of the target message arriving at the inbound interface of this node, and the timestamp of the target message arriving at the outbound interface of this node. The way in which the decapsulation node reports its own detection data to the detection control device can be referred to the aforementioned introduction, which will not be repeated here.

[0091] S218: The decapsulation node performs IOAM decapsulation on the message of the target service flow according to the instruction of the second configuration information and sends the IOAM decapsulated message to the next node.

[0092] It should be understood that the decapsulation node will receive the second configuration information sent by the detection control device in S202, and the second configuration information carries the flow identifier of the target business flow. According to the second configuration information, the decapsulation node can determine that it needs to perform IOAM decapsulation processing on the target business flow. Therefore, before the decapsulation node sends the message of the target business flow to the next node, it is necessary to first strip off the IOAM header of each message of the target business flow, which includes not only the IOAM header of the target message, but also the IOAM header of the non-target business flow. The decapsulation node performs IOAM decapsulation on the message of the target business flow and sends the IOAM decapsulated message to the next node. At this point, the message of the target business flow flows out of the target IOAM domain.

[0093] In some examples of this embodiment, the second configuration information sent by the detection control device to the decapsulation node also includes egress verification information, which can indicate to the decapsulation node the egress interface of the target service flow expected by the detection control device on the decapsulation node, that is, the expected egress interface. Therefore, after the decapsulation node sends the message of the target service flow to the next node, it can determine the actual egress interface of the target service flow, and then match the actual egress interface with the expected egress interface, and feed back the matching result to the detection control device, so that the detection control device can determine whether its expectation is correct based on the matching result.

[0094] According to the above introduction, the encapsulation node, decapsulation node and transmission node will generate detection and reporting instances of the target business flow at this node, and these detection and reporting instances are each allocated detection resources. However, if the transmission path of the target business flow changes, or the automatic IOAM detection of the target business flow ends, or the detection control device re-indicates the marking period, the detection corresponding to these detection and reporting instances will end. In other words, these detection and reporting instances become useless detection and reporting instances. In this case, it is unreasonable to continue to allow these detection and reporting instances to continue to exist and occupy the detection resources of the node. Therefore, in some examples of this embodiment, these nodes can perform aging detection on the detection and reporting instances on this node, determine the aged detection and reporting instances, and then delete these aged detection and reporting instances to release the detection resources. The following provides several ways for nodes to determine aging detection and reporting instances. Since the communication equipment in the network can be used as an encapsulation node, a transmission node, and a decapsulation node, here we take the communication equipment performing aging management on the detection and reporting instances on it as an example for explanation:

[0095] Method 1, see Figure 4 :

[0096] S402: The communication device determines a first duration corresponding to each detection reporting instance on the device.

[0097] The so-called first duration here is actually the time distance from the last time the message of the target business flow corresponding to the detection reporting instance appeared on the communication device to the current time, that is, the time difference between the current time and the last time the message of the target business flow was received.

[0098] S404: The communication device determines whether the first duration is greater than a first preset duration.

[0099] The preset first duration can be pre-set on the communication device by the administrator. In some other examples of this embodiment, the preset first duration can be configured by the detection and control device and sent to the encapsulation node, which is carried to other nodes by the encapsulation node in the IOAM header of the target business flow message. In this case, the detection and control device can set different first preset durations according to different target business flows.

[0100] S406: The communication device determines that the detection and reporting instance is an aged detection and reporting instance.

[0101] If the communication device determines that the first duration is greater than the first preset duration, it may be determined that the detection reporting instance has aged; otherwise, the communication device will continue to execute S402.

[0102] For method 2, see Figure 5 :

[0103] S502: The communication device determines a second duration corresponding to each detection reporting instance on the device.

[0104] The so-called second duration here is actually the duration that the communication device continues to receive invalid target messages of the target service flow corresponding to the detection reporting instance. For example, if the encapsulation node determines that the transmission node does not need to automatically detect the message of a certain target service flow, the invalid automatic detection identifier can be carried in the IOAM header of the target service flow message. For any node in the target IOAM domain, if it has been receiving invalid target messages for a long time, the node can determine that it does not need to automatically perform IOAM detection on the message of the corresponding target service flow.

[0105] S504: The communication device determines whether the second duration is greater than a second preset duration.

[0106] The preset second duration can be pre-set on the communication device by the administrator. In some other examples of this embodiment, the preset second duration can be configured by the detection and control device and sent down to the encapsulation node, which is carried to other nodes by the encapsulation node in the IOAM header of the target business flow message. In this case, the detection and control device can set different second preset durations according to different target business flows.

[0107] S506: The communication device determines that the detection and reporting instance is an aged detection and reporting instance.

[0108] If the communication device determines that the second duration is greater than the second preset duration, it may be determined that the detection reporting instance has aged; otherwise, the communication device will continue to execute S502.

[0109] Method 3, see Figure 6 :

[0110] S602: The communication device receives instance change control information sent by the detection control device.

[0111] In this embodiment, the instance change control information may be instruction information of the detection control device instructing to delete the detection reporting instance of a certain target service flow, or may be instance change control information issued due to a change in the marking period of the target service flow.

[0112] S604: The communication device determines the detection and reporting instance corresponding to the instance change control information as an aged detection and reporting instance.

[0113] When the communication device receives the instance change control information, it can delete the detection report instance on the device corresponding to the corresponding instance change control information. It can be understood that the instance change control information usually carries the flow identifier of the corresponding target service flow, so the communication device can determine which detection report instances on the device correspond to the instance change control information according to the flow identifier in the instance change control information, that is, which detection report instances are aged detection report instances.

[0114] In the IOAM detection processing solution provided by the embodiment of the present invention, the encapsulation node, the transmission node, and the decapsulation node can generate the detection reporting instance corresponding to the target business flow based on learning without receiving the instance configuration information of the detection control device, and automatically perform IOAM detection on the target message in the target business flow. The detection control device does not need to determine the specific transmission path of the target business flow in each node, the inbound interface and the outbound interface on each node, which reduces the requirements for the calculation accuracy of the detection control device when starting the IOAM detection. At the same time, because the detection control device does not need to configure the transmission node, the configuration burden of the detection control device is reduced.

[0115] Furthermore, the decapsulation node can match the expected outgoing interface of the target business flow with the actual outgoing interface, and send the matching result to the detection and control device, so that the detection and control device can detect the network nodes that the target business flow actually passes through and verify whether the actual transmission path of the target business flow is consistent with the expectation.

[0116] Moreover, the encapsulation node, transmission node and decapsulation node can automatically perform aging management on the detection reporting instances generated by themselves, delete the aged detection reporting instances in time, release the detection resources, thereby avoiding resource waste and promoting the realization of resource optimization configuration.

[0117] Embodiment 2:

[0118] In order to make those skilled in the art more aware of the advantages and details of the aforementioned IOAM detection and processing solution, this embodiment will continue to explain the aforementioned solution with examples:

[0119] See also Figure 7 , Figure 7 What is shown is a schematic diagram of the IOAM detection and processing system implementing the IOAM detection and processing solution in this embodiment:

[0120] The IOAM detection and processing system 7 includes a detection control device 70, an encapsulation node 71, a decapsulation node 72 and at least one transmission node 73. Each transmission node 73 forms a link in series between the encapsulation node 71 and the decapsulation node 72. Of course, those skilled in the art can understand that there may be other links between the encapsulation node 71 and the decapsulation node 72.

[0121] In this embodiment, the detection control device 70 only needs to send configuration information to the encapsulation node 71 and the decapsulation node 72, and the information exchange between each transmission node 73 and the detection control device 70 is one-way. The transmission node 73 does not need to accept the configuration of the detection control device 70, but only needs to report the detection data to the detection control device 70. Figure 1 Come and see, Figure 1 The interaction between the centralized controller 14 and the encapsulation node 11, the decapsulation node 12 and the transmission node 13 is bidirectional. Figure 1 In the IOAM detection scheme shown, the centralized controller 14 not only needs to know which transmission nodes are, but also needs to determine how the target service flow flows through these transmission nodes. However, in this embodiment, the detection control device 70 not only does not need to know which interfaces of the transmission node 73 the target service flow flows through, but does not even need to know which transmission nodes are.

[0122] Combine the following Figure 8 The flowchart of the IOAM detection control scheme shown in the figure explains the details of the IOAM detection processing method implemented by the IOAM detection processing system 7:

[0123] S802: The detection control device sends first configuration information to the encapsulation node in the target IOAM domain, and sends second configuration information to the decapsulation node.

[0124] In this embodiment, the first configuration information includes the flow identifier of the target service flow, the service flow identification feature, and the marking period, and further includes the inbound interface information and the automatic detection start indication.

[0125] S804: The encapsulation node identifies the target service flow from the service flows entering the node according to the inbound interface information and the service flow identification feature.

[0126] After receiving the first configuration information, the encapsulation node identifies the business flow entering the node from the inbound interface indicated by the inbound interface information, and determines whether there is a business flow whose business flow identification characteristics match the business flow identification characteristics in the first configuration information. If the match is successful, the business flow with the successful match is used as the target business flow.

[0127] In some examples of this embodiment, the service flow identification feature may be at least one of an IP packet quintuple, layer 2 Ethernet header information, a VLAN (Virtual Local Area Network), a protocol type of a non-IP packet, and the like.

[0128] S806: The encapsulation node generates an inbound detection reporting instance corresponding to the target service flow.

[0129] In this embodiment, the encapsulation node may generate an inbound detection instance reporting instance according to the first configuration information, because the first configuration information already carries the Flow id of the target service flow and the inbound interface information. It is understandable that the encapsulation node may generate an inbound detection reporting instance according to the first configuration information immediately after receiving the first configuration information, for example, before the target service flow reaches the node.

[0130] S808: The encapsulation node performs IOAM encapsulation on the message of the target service flow.

[0131] The encapsulation node performs IOAM encapsulation on the messages of the target service flow, which actually adds an IOAM header to these messages.

[0132] Fig. 9 A schematic diagram of the format of an IOAM data header is shown: wherein "L" is the location of the target mark. If "L" is set to "1" in a message IOAM header, it indicates that the message is a target message. In related technologies, the locations of "H" and "T" in the IOAM header are reserved fields. In this embodiment, the encapsulation node sets an automatic detection flag in the reserved field, i.e., "H". If "H" is set to "1" in a target message IOAM header, it indicates that the target message carries a valid automatic detection flag. The node that receives the target message needs to automatically perform IOAM detection on the target message even if it has not received the instance configuration information of the detection control device. On the contrary, if "H" is set to "0" in a message IOAM header, it indicates that the message carries an invalid automatic detection flag. "T" carries the marking period. In Fig. 9 Among them, T occupies 3 bytes. According to binary system, these 3 bytes can show 8 different marking periods.

[0133] S810: The encapsulation node sends the message of the target service flow to the next node, and automatically generates an outbound detection reporting instance of the target service flow at this node.

[0134] In this embodiment, after the encapsulation node completes the packet encapsulation of the target service flow, the packet of the target service flow can be sent to the next node. After determining how to send the packet of the target service flow, the encapsulation node can learn the outbound interface of the target service flow on the local node. Therefore, the encapsulation node can generate an outbound detection reporting instance of the target service flow on the local node according to the flow identifier in the IOAM header of the target message and the outbound interface of the target service flow on the local node.

[0135] S812: The transmission node determines, based on the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of the target service flow that needs to be detected by the IOAM.

[0136] After receiving a message, the transmission node finds that the message carries an IOAM header, and the IOAM header carries a target tag, then it can determine that the message is a target message, and can determine the target service flow to which the target message belongs based on the flow identifier in the IOAM header.

[0137] S814: The transmission node generates an inbound detection reporting instance of the target service flow at the inbound interface of the node according to the flow identifier in the IOAM header of the target message and the target service flow.

[0138] The transmission node can determine the inbound interface when the target message enters this node, and based on the flow identifier in the IOAM header of the target message, it can generate an inbound detection reporting instance of the target service flow at this node without receiving the instance configuration information of the detection control device.

[0139] S816: The transmission node sends the message of the target service flow to the next node, and automatically generates an outbound detection reporting instance of the target service flow at this node.

[0140] In this embodiment, it is assumed that the next node of the transmission node is the decapsulation node, but those skilled in the art can understand that in more scenarios, there are multiple transmission nodes between the encapsulation node and the decapsulation node, so the next node of a transmission node may also be another transmission node.

[0141] The transmission node can determine the outbound interface when the target message flows out of this node. At the same time, based on the flow identifier in the IOAM header of the target message, it can generate an outbound detection reporting instance of the target service flow at this node without receiving the instance configuration information of the detection control device.

[0142] S818: The decapsulation node determines, based on the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of the target service flow that needs to be detected by the IOAM.

[0143] After receiving a message, the decapsulation node finds that the message carries an IOAM header, and the IOAM header carries a target tag, then it can determine that the message is a target message, and can determine the target service flow to which the target message belongs based on the flow identifier in the IOAM header.

[0144] S820: The decapsulation node generates an inbound detection reporting instance of the target service flow at the inbound interface of the node according to the flow identifier in the IOAM header of the target message and the target service flow.

[0145] The decapsulation node can determine the inbound interface when the target message enters this node, and based on the flow identifier in the IOAM header of the target message, it can generate an inbound detection reporting instance of the target service flow at this node without receiving the instance configuration information of the detection control device.

[0146] S822: The decapsulation node performs IOAM decapsulation on the message of the target service flow.

[0147] The decapsulation node receives the second configuration information sent by the detection control device in S802, and the second configuration information carries the flow identifier of the target service flow. According to the second configuration information, the decapsulation node can determine that it needs to perform IOAM decapsulation processing on the target service flow. Therefore, before the decapsulation node sends the message of the target service flow to the next node, the IOAM header of each message of the target service flow will be stripped off.

[0148] S824: The decapsulation node sends the message of the target service flow to the next node, and automatically generates an outbound detection reporting instance of the target service flow at this node.

[0149] After the decapsulation node sends the message of the target service flow to the next node, the decapsulation node can determine the outbound interface when the target message flows out of this node. At the same time, based on the flow identifier in the IOAM header of the target message, it can generate an outbound detection reporting instance of the target service flow at this node without receiving the instance configuration information of the detection control device.

[0150] In some examples of this embodiment, the second configuration information sent by the detection and control device to the decapsulation node also includes export verification information. Therefore, after the decapsulation node sends the message of the target service flow to the next node, it can determine the actual outbound interface of the target service flow, and then match the actual outbound interface with the expected outbound interface, and feed back the matching result to the detection and control device, so that the detection and control device can determine whether its expectations are correct based on the matching result.

[0151] In addition, in this embodiment, the encapsulation node, transmission node and decapsulation node can also report the detection data of each detection reporting instance on the node to the detection control device, and perform aging management on the detection reporting instance. For the specific detection data reporting method and the aging management of the detection reporting instance, please refer to the introduction of Example 1, which will not be repeated here.

[0152] See also Fig.10 The IOAM detection and processing system provided in this embodiment can be functionally divided into the following modules: a centralized control module 101, a resource allocation module 102, a hardware module 103, a learning module 104, a data reporting module 105 and an aging management module 106.

[0153] The centralized control module 101 is located in a detection control device, such as a centralized controller, and is responsible for configuring encapsulation nodes and decapsulation nodes and receiving IOAM detection data reports.

[0154] Resource allocation module 102 This module is located on the service node and is responsible for generating IOAM detection and reporting instances and allocating hardware resources corresponding to the detection and reporting instances, including marking resources, message monitoring resources and subscription data reporting resources.

[0155] The hardware module 103 is located on the service node and is responsible for executing message marking, traffic start monitoring, and statistics and measurement of network quality data.

[0156] The learning module 104 is located on the business node and is responsible for collecting the traffic monitoring results in the hardware module 103, analyzing the demand for new detection reporting instances based on the traffic monitoring results, and sending the request to the resource allocation module 102 to allow the resource allocation module 102 to generate corresponding detection reporting instances.

[0157] The data reporting module 105 is located in the service node and is responsible for collecting various network quality data information in the hardware module 103, and generating detection data corresponding to each detection reporting instance and sending it to the centralized control module 101. In addition, the aging detection reporting instance is analyzed according to the content of the reported data and sent to the aging management module 106.

[0158] The aging management module 106 is located in the service node, and is responsible for receiving the aging detection and reporting instance information sent by the data reporting module 105 , and sending a resource release request to the resource allocation module 102 .

[0159] The IOAM detection and processing system provided in this embodiment can greatly reduce the routing calculation burden of detection and control equipment, such as centralized controllers, and simplify the configuration complexity. At the same time, it saves the hardware resources required for equipment network quality measurement, maximizing resource utilization. Moreover, the IOAM detection and processing system can also achieve the effect of detecting the network nodes that the service flow message actually passes through and verifying whether the transmission path of the service data is consistent with the expectation, providing a fast, accurate and effective detection method for the actual service forwarding path for engineering operation and maintenance.

[0160] Embodiment three:

[0161] In a core network composed of PTN (Packet Transport Network) devices, all PTN devices are added to the target IOAM domain. In this network, a L3VPN (Layer 3 Virtual Private Network) service is deployed through three devices: PE1, P2, and PE3. Fig.11 As shown. Assume that a service flow in the L3VPN (source ip = 192.168.10.50, destination ip = 192.155.20.60) enters the target IOAM domain from interface 1 of the PE1 device, is forwarded by the intermediate device PE2, and finally leaves the target IOAM domain through interface 2 of the PE3 device. At the same time, assume that a layer of link-level protection is configured between the two nodes PE1 and P2, in which "PE1 interface 2-->P2 interface 1" is the working link and "PE1 interface 3-->P2 interface 2" is the protection link. The initial target service flow is forwarded on the working link. In order to detect the network forwarding quality of the service flow, the centralized controller controls to enable the IOAM automatic detection function:

[0162] In step 1, the centralized controller sends the service identification characteristics ("source ip = 192.168.10.50, destination ip = 192.155.20.60"), flow identifier (flow id = X), inbound interface information (port1) and marking period (T1) of the target service flow to the encapsulation node PE1 device, and sends the flow identifier (flow id = X), marking period (T1), and egress verification information (port2) to the decapsulation node PE3 device.

[0163] Step 2, PE1 device:

[0164] The IP service packets coming from interface 1 are matched and identified. Once the match is successful, the marking process is performed according to the basic IOAM method, with the marking period and the unmarking period alternating. The packets are then forwarded from interface 2 according to the L3VPN service forwarding rules. Fig. 9 The IOAM header is shown at the bottom of the MPLS label stack.

[0165] PE3 device: receives the decapsulation indication and egress verification information for the service flow with flow id = X, and automatically generates an IOAM decapsulation verification instance "flow id = X, marking period = T1, egress interface = port2" to the hardware verifier.

[0166] Step 3: After receiving the configuration information from the centralized controller, PE1 automatically generates a detection report instance "flowid=X, port1, inbound". When the hardware module of PE1 detects that a service packet carrying an IOAM data header with valid H and T fields is forwarded out of interface 2, it automatically learns and generates a detection report instance "flowid=X, port2, outbound".

[0167] Step 4: When the P2 device interface 1 receives a message with flow ID X, it automatically learns and generates a detection and reporting instance "flowid=X, port1, inbound". When the message is forwarded through interface 3, it automatically learns and generates a detection and reporting instance "flowid=X, port3, outbound".

[0168] Step 5: When PE3 receives a message with flow ID X and forwards it from the network element, it automatically learns and generates a detection report instance "flowid=X, port1, inbound". When the message is forwarded through interface 2, it automatically learns and generates a detection report instance "flowid=X, port2, outbound".

[0169] In step 6, the three network elements PE1, P2, and PE3 report the detection of the inbound / outbound detection reporting instance to the centralized controller at the frequency corresponding to the marking period T. The centralized controller calculates and analyzes the packet loss rate and delay within the node, and the packet loss rate and delay of each link between nodes, and presents them to the network maintenance personnel.

[0170] In step 7, when the working link between PE1 and P2 fails and the service is switched to the protection link, interface 3 on PE1 and interface 2 on P2 will automatically learn and generate the corresponding detection reporting instance and detect the detection reporting instance.

[0171] In step 8, because the service flow is switched to the protection link, the IOAM reporting instance "flowid=X, port2, outbound" of PE1 detects data as 0 in the next marking cycle after the service flow is switched, which is considered invalid data and is not reported to the centralized controller. When the number of consecutive cycles in which the detection data is invalid reaches the set aging cycle value, the aging detection reporting instance "flowid=X, port2, outbound" begins, and the hardware resources corresponding to the instance are released. Similarly, the IOAM reporting instance "flowid=X, port1, inbound" of P2 also enters the same aging process.

[0172] In step 9, when the network maintenance personnel want to cancel the automatic detection of service flow X, the centralized controller sends the instance change control information carrying the flow ID to PE1 and PE3. PE1 immediately and quickly ages out the detection reporting instance "flowid = X, port1, inbound", and PE3 immediately and quickly deletes the IOAM decapsulation verification resources of the hardware verifier for this instance. Other reporting instances related to the detection instance X will also age out quickly as there is no IOAM data header in the message.

[0173] The IOAM detection and processing solution provided in this embodiment overcomes the problems in related technologies such as heavy computing load of the centralized controller, serious waste of forwarding plane resources, and inability to perform IOAM detection when the actual underlying forwarding path is inconsistent with the expected one, and achieves the effect of automatically detecting the network forwarding quality within the IOAM domain, and adds correctness verification of the network outbound interface, thereby improving the rational utilization of forwarding plane resources and the stability of the entire system.

[0174] Embodiment 4:

[0175] This embodiment provides a storage medium, which can store one or more computer programs that can be read, compiled and executed by one or more processors. In this embodiment, the storage medium can store at least one of an IOAM detection configuration program, a first IOAM detection processing program, a second IOAM detection processing program and a third IOAM detection processing program, wherein the IOAM detection configuration program can be executed by one or more processors to implement the steps of the IOAM detection configuration method on the detection control device side in any of the aforementioned embodiments; the first IOAM detection processing program can be executed by one or more processors to implement the steps of the IOAM detection processing method on the encapsulation node side in any of the aforementioned embodiments; the second IOAM detection processing program can be executed by one or more processors to implement the steps of the IOAM detection processing method on the transmission node side in any of the aforementioned embodiments; the third IOAM detection processing program can be executed by one or more processors to implement the steps of the IOAM detection processing method on the decapsulation node side in any of the aforementioned embodiments.

[0176] This embodiment further provides a computer program product, including a computer readable device, on which the computer program as shown above is stored. In this embodiment, the computer readable device may include the computer readable storage medium as shown above.

[0177] This embodiment also provides a detection control device, such as Fig.12As shown, the detection control device 12 includes a first processor 121, a first memory 122 and a first communication bus 123; the first communication bus 123 is used to realize the connection and communication between the first processor 121 and the first memory 122; the first memory 122 can be the storage medium storing the IOAM detection configuration program. The first processor 121 is used to execute the IOAM detection configuration program stored in the first memory 122 to implement the steps of the IOAM detection configuration method on the detection control device side in any of the above embodiments:

[0178] The first processor 121 sends configuration information to the node that needs to be configured in the target IOAM domain. The target IOAM domain is the IOAM domain that performs IOAM detection on the target business flow. The node that needs to be configured is composed of the encapsulation node and the decapsulation node in the target IOAM domain; the configuration information sent to the encapsulation node is the first configuration information, which includes the flow identifier of the target business flow, the business flow identification feature, and the marking period. The business flow identification feature is used by the encapsulation node to identify the target business flow from the business flow entering the node, and the marking period is used to instruct the encapsulation node to mark the message arriving in the target business flow within the marking period as the target message; the configuration information sent to the decapsulation node is the second configuration information, which includes the flow identifier of the target business flow.

[0179] In some examples of this embodiment, the first configuration information also includes inbound interface information of the target service flow entering the encapsulation node.

[0180] In some examples of this embodiment, the first configuration information also includes an automatic detection start indication, which is used to instruct the encapsulation node to carry an automatic detection identifier in the IOAM header of the target message when performing IOAM encapsulation on the target message, and the automatic detection identifier is used to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device.

[0181] This embodiment also provides a communication device, such as Fig.13 The communication device 13 includes a second processor 131, a second memory 132, and a second communication bus 133 for connecting the second processor 131 and the second memory 132.

[0182] In some examples of this embodiment, the communication device 13 may be an encapsulation node, and the second memory 132 is the storage medium storing the first IOAM detection processing program. The second processor 131 is used to execute the first IOAM detection processing program stored in the second memory 132 to implement the steps of the encapsulation node side IOAM detection processing method in any of the above embodiments:

[0183] The second processor 131 receives the first configuration information sent by the detection control device, and the first configuration information includes the flow identifier, the business flow identification feature, and the marking period of the target business flow. Subsequently, the second processor 131 identifies the target business flow from the business flow entering the communication device 13 according to the business flow identification feature, and performs IOAM encapsulation on the message of the target business flow. The encapsulated IOAM header carries the flow identifier of the target business flow, and the IOAM header of the message arriving in the target business flow within the marking period also carries a target mark indicating that the message is a target message. The IOAM header can be used for the node through which the target message flows to automatically generate a detection reporting instance without receiving the instance configuration information sent by the detection control device. Then, the second processor 131 sends the target message to the next node.

[0184] In some examples of this embodiment, the IOAM header also includes an automatic detection flag, which is used to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving instance configuration information of the detection control device.

[0185] Optionally, the IOAM header also includes a marking period, and the marking period is used to indicate the time for each node in the target domain to report data to the detection control device.

[0186] In some scenarios, the first configuration information also includes inbound interface information of the target service flow entering the encapsulation node;

[0187] When the second processor 131 identifies the target service flow from the service flow entering the communication device 13 according to the service flow identification feature, it can monitor the service flow entering the communication device 13 from the inbound interface corresponding to the inbound interface information to identify the target service flow corresponding to the service flow identification feature.

[0188] In some examples of this embodiment, the second processor 131 also generates an outbound detection reporting instance of the target service flow in the communication device 13 according to the flow identifier in the target message and the outbound interface of the target service flow in the communication device 13.

[0189] Optionally, before the second processor 131 generates an outbound detection reporting instance of the target business flow at the outbound interface of the communication device 13 based on the flow identifier in the target message and the target business flow at the outbound interface of the communication device 13, it will first determine that the IOAM header of the target message also includes a valid automatic detection identifier. The valid automatic detection identifier is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device.

[0190] In some examples of this embodiment, the communication device 13 may be a transmission node, and the second memory 132 is the storage medium storing the second IOAM detection processing program. The second processor 131 is used to execute the second IOAM detection processing program stored in the second memory 132 to implement the steps of the transmission node side IOAM detection processing method in any of the above embodiments:

[0191] The second processor 131 determines that the message is a target message of the target service flow that needs to be detected by IOAM according to the flow identifier and the target tag in the IOAM header of the received message. Then, the second processor 131 generates a detection report instance of the target service flow in the communication device 13 according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows in the communication device 13, and the detection report instance includes at least one of an inbound detection report instance and an outbound detection report instance. Then, the second processor 131 sends the target message to the next node.

[0192] In some examples of this embodiment, the second processor 131 generates the target service flow based on the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows on the communication device 13 before generating a detection reporting instance of the communication device 13. It will also first determine that the IOAM header of the target message also includes a valid automatic detection identifier. The valid automatic detection identifier is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device.

[0193] In some examples of this embodiment, the communication device 13 may be a second processor 131, and the second memory 132 is the aforementioned storage medium storing the third IOAM detection processing program. The second processor 131 is used to execute the third IOAM detection processing program stored in the second memory 132 to implement the steps of the IOAM detection processing method on the second processor 131 side in any of the aforementioned embodiments:

[0194] The second processor 131 determines that the message is a target message of the target service flow that needs to be detected by IOAM according to the flow identifier and target tag in the IOAM header of the received message, and then generates a detection report instance of the target service flow in the communication device 13 according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows in the communication device 13. The detection report instance includes at least one of an inbound detection report instance and an outbound detection report instance. Subsequently, the second processor 131 performs IOAM decapsulation on the message of the target service flow according to the instruction of the second configuration information and sends the IOAM decapsulated message to the next node. The second configuration information is sent by the detection control device, which includes the flow identifier of the target service flow.

[0195] In some examples of this embodiment, the second processor 131 generates the target service flow based on the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows on the communication device 13 before generating a detection reporting instance of the communication device 13. It will also first determine that the IOAM header of the target message also includes a valid automatic detection identifier. The valid automatic detection identifier is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device.

[0196] Optionally, the second configuration information further includes egress verification information, where the egress verification information is used to indicate to the second processor 131 an egress interface of the target service flow expected by the detection control device on the second processor 131;

[0197] After the second processor 131 performs IOAM decapsulation on the target message and sends it to the next node, it will also match the actual outbound interface of the target message on the second processor 131 with the expected outbound interface indicated by the egress verification information, and report the matching result to the detection control device.

[0198] In some examples, no matter the communication device 13 is an encapsulation node, a decapsulation node or a transmission node, the second processor 131 may perform the following process:

[0199] The second processor 131 determines an aged detection and reporting instance in the communication device 13, and deletes the aged detection and reporting instance.

[0200] In some examples of this embodiment, the second processor 131 determines that the detection and reporting instance of aging in the communication device includes at least one of the following methods:

[0201] Method 1:

[0202] For each detection reporting instance on the communication device 13, the second processor 131 determines a first duration from the time when the message of the target service flow corresponding to the detection reporting instance last appeared on the communication device 13 to the current time. If the first duration is greater than the first preset duration, the second processor 131 determines that the detection reporting instance is an aged detection reporting instance;

[0203] Method 2:

[0204] For each detection reporting instance on the communication device 13, the second processor 131 determines a second duration of continuously receiving an invalid target message, where the invalid target message is a target message carrying an invalid automatic detection identifier, and the invalid automatic detection identifier is used to indicate that the node through which the target message flows does not need to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device; if the second duration is greater than the second preset duration, the second processor 131 determines that the detection reporting instance is an aged detection reporting instance;

[0205] Method 3:

[0206] The second processor 131 receives the instance change control information sent by the detection control device, and then determines the detection reporting instance corresponding to the instance change control information as an aged detection reporting instance.

[0207] In some examples of this embodiment, the second processor 131 is further configured to report the detection data corresponding to the detection reporting instance to the detection control device data according to the information in the IOAM header in any one of the following ways:

[0208] Mode 1: The second processor 131 detects that the message of the target service flow is switched from the target message to the non-target message according to the target tag in the IOAM header, and then reports the detection data corresponding to the detection reporting instance to the detection control device;

[0209] Mode 2: The IOAM header also includes an automatic detection flag, which is used to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device. The second processor 131 determines that the automatic detection is stopped according to the automatic detection flag in the IOAM header, and then reports the detection data corresponding to the detection reporting instance to the detection control device;

[0210] Mode three: the IOAM header also includes a marking period, and the second processor 131 reports the detection data corresponding to the detection reporting instance to the detection control device according to the marking period in the IOAM header.

[0211] This embodiment also provides an IOAM detection processing system, including an encapsulation node, a decapsulation node, a transmission node, and a detection control device, wherein the encapsulation node is sequentially connected to the transmission node and the decapsulation node; the detection control device is Fig.12 The transmission encapsulation node is the communication device 13 where the second processor 131 executes the first IOAM detection processing program, the transmission node is the communication device 13 where the second processor 131 executes the second IOAM detection processing program, and the decapsulation node is the communication device 13 where the second processor 131 executes the third IOAM detection processing program.

[0212] For details of the IOAM detection and processing solution implemented by the encapsulation node, decapsulation node, transmission node and detection control device, please refer to the introduction of the aforementioned embodiment, which will not be repeated here.

[0213] According to the scheme provided in the embodiment, the detection and control device only needs to configure the encapsulation nodes and decapsulation nodes in the target IOAM domain corresponding to the target business flow. The detection and control device does not need to configure the transmission nodes in the target IOAM domain, and does not even need to care about which are the transmission nodes of the target business flow. Therefore, the detection and control device does not need to accurately calculate the transmission nodes of the target business flow, let alone consider the working path and the nodes on the protection path of the target business flow, which reduces the requirements for the computing power of the detection and control device and reduces the configuration burden of the detection and control device. Moreover, because the transmission nodes in the target IOAM domain generate detection reporting instances according to the IOAM header in the target message only after the target business flow reaches the node, that is, they allocate detection resources, if the target business flow does not flow through the node, the node will not generate a detection reporting instance for the target business flow and allocate detection resources, so there will be no waste of detection resources, which is conducive to the optimization of network resources.

[0214] It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the above disclosed methods can be implemented as software (which can be implemented with computer program code executable by a computing device), firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be performed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit.

[0215] In addition, it is well known to those skilled in the art that communication media generally contain computer readable instructions, data structures, computer program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery media. Therefore, the present invention is not limited to any specific hardware and software combination.

[0216] The above contents are further detailed descriptions of the embodiments of the present invention in combination with specific implementation methods, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. An in-band operation management and maintenance IOAM detection configuration method, comprising: The detection control device sends configuration information to a node that needs to be configured in a target IOAM domain, the target IOAM domain is an IOAM domain that performs IOAM detection on a target service flow, and the node that needs to be configured is composed of an encapsulation node and a decapsulation node in the target IOAM domain: the configuration information sent to the encapsulation node is first configuration information, which includes a flow identifier of the target service flow, a service flow identification feature, and a marking period, the service flow identification feature is used by the encapsulation node to identify the target service flow from the service flow entering the node, and the marking period is used to instruct the encapsulation node to mark a message arriving in the target service flow within the marking period as a target message: the configuration information sent to the decapsulation node is second configuration information, which includes a flow identifier of the target service flow, and the flow identifier is used to allow each node in the target IOAM domain to uniquely identify the target service flow; The first configuration information also includes inbound interface information and an automatic detection start indication; the automatic detection start indication is used to instruct the encapsulation node to carry an automatic detection identifier in the IOAM header of the target message when performing IOAM encapsulation on the target message, and the automatic detection identifier is used to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device.

2. An IOAM detection and processing method, comprising: The encapsulation node receives first configuration information sent by the detection control device, wherein the first configuration information includes a flow identifier, a flow identification feature, and a marking period of a target service flow; wherein the flow identifier is used to allow the encapsulation node to uniquely identify the target service flow; The encapsulation node identifies the target service flow from the service flow entering the node according to the service flow identification feature, and performs IOAM encapsulation on the message of the target service flow, wherein the IOAM header added by the encapsulation carries the flow identifier of the target service flow, and the IOAM header of the message arriving in the target service flow within the marking period also carries a target mark indicating that the message is a target message, and the IOAM header can be used by the node through which the target message flows to automatically generate a detection reporting instance without receiving the instance configuration information sent by the detection control device; the encapsulation node sends the target message to the next node; The IOAM header also includes an automatic detection flag and a marking period. The automatic detection flag is used to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device; the marking period is used to indicate the time for each node in the IOAM target domain to report data to the detection control device.

3. The IOAM detection and processing method according to claim 2, characterized in that: The first configuration information also includes inbound interface information of the target service flow entering the encapsulation node; The encapsulation node identifies the target service flow from the service flow entering the node according to the service flow identification feature, including: The encapsulation node monitors the service flow entering the node from the inbound interface corresponding to the inbound interface information, and identifies the target service flow corresponding to the service flow identification feature.

4. The IOAM detection and processing method according to any one of claims 2 to 3, characterized in that: Also includes: The encapsulation node generates an outbound detection reporting instance of the target service flow at the local node according to the flow identifier in the target message and the outbound interface of the target service flow at the local node.

5. The IOAM detection and processing method according to claim 4, characterized in that: Before the encapsulation node generates an outbound detection reporting instance of the target service flow at the outbound interface of the node according to the flow identifier in the target message and the target service flow, the encapsulation node further includes: The encapsulation node determines that the IOAM header of the target message also includes a valid automatic detection identifier, and the valid automatic detection identifier is used to instruct the node through which the target message flows to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device.

6. An IOAM detection and processing method, comprising: The transmission node determines, according to the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of the target service flow that needs to be detected by the IOAM; The flow identifier is used to allow the transmission node to uniquely identify the target service flow; The transmission node determines that the IOAM header of the target message also includes a valid automatic detection flag, and the valid automatic detection flag is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device; The transmission node generates a detection reporting instance of the target service flow at the local node according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows at the local node, wherein the detection reporting instance includes at least one of an inbound detection reporting instance and an outbound detection reporting instance; The transmission node sends the target message to the next node.

7. An IOAM detection and processing method, comprising: The decapsulation node determines, according to the flow identifier and the target tag in the IOAM header of the received message, that the message is a target message of the target service flow that needs to be detected by the IOAM; The flow identifier is used to allow the decapsulation node to uniquely identify the target service flow; The decapsulation node determines that the IOAM header of the target message also includes a valid automatic detection flag, and the valid automatic detection flag is used to indicate that the node through which the target message flows automatically performs IOAM detection on the target message without receiving the instance configuration information of the detection control device; The decapsulation node generates a detection reporting instance of the target service flow at the local node according to the flow identifier in the IOAM header of the target message and the interface through which the target service flow flows at the local node, wherein the detection reporting instance includes at least one of an inbound detection reporting instance and an outbound detection reporting instance; The decapsulation node performs IOAM decapsulation on the message of the target service flow according to the instruction of the second configuration information and sends the IOAM decapsulated message to the next node. The second configuration information is sent by the detection control device and includes the flow identifier of the target service flow.

8. The IOAM detection and processing method according to claim 7, characterized in that: The second configuration information also includes egress verification information, where the egress verification information is used to indicate to the decapsulation node that the detection control device expects the target service flow to be on the egress interface of the decapsulation node; After the decapsulation node performs IOAM decapsulation on the target message and sends it to the next node, the method further includes: the decapsulation node matches the actual outbound interface of the target message on the decapsulation node with the expected outbound interface indicated by the egress verification information; The decapsulation node reports the matching result to the detection control device.

9. A detection control device, comprising a first processor, a first memory and a first communication bus; The first communication bus is used to realize the connection communication between the first processor and the first memory; the first processor is used to execute one or more programs stored in the first memory to implement the steps of the IOAM detection configuration method as described in claim 1.

10. A communication device, comprising a second processor, a second memory and a second communication bus; the second communication bus is used to realize connection communication between the second processor and the second memory; the second processor is used to execute a first IOAM detection processing program stored in the second memory to implement the steps of the IOAM detection processing method as described in any one of claims 2 to 5; or, the second processor is used to execute a second IOAM detection processing program stored in the second memory to implement the steps of the IOAM detection processing method as described in claim 6; or, the second processor is used to execute a third IOAM detection processing program stored in the second memory to implement the steps of the IOAM detection processing method as described in any one of claims 7 to 8.

11. The communication device according to claim 10, characterized in that The communication device is further used to determine an aged detection and reporting instance in the device, and delete the aged detection and reporting instance.

12. The communication device according to claim 11, characterized in that The communication device determines that the detection and reporting instance of aging in the device includes at least one of the following methods: Method 1: For each detection and reporting instance on the device, determine the first time duration between the last time a message of the target service flow corresponding to the detection and reporting instance appeared on the device and the current time; If the first duration is greater than a first preset duration, determining that the detection reporting instance is an aged detection reporting instance; Method 2: For each detection reporting instance on the device, determining a second duration of continuously receiving an invalid target message, wherein the invalid target message is a target message carrying an invalid automatic detection identifier, and the invalid automatic detection identifier is used to indicate that a node through which the target message flows does not need to automatically perform IOAM detection on the target message without receiving instance configuration information of the detection control device; If the second duration is greater than a second preset duration, determining that the detection reporting instance is an aged detection reporting instance; Method 3: Receive instance change control information sent by the detection control device; The detection and reporting instance corresponding to the instance change control information is determined as an aged detection and reporting instance.

13. The communication device according to any one of claims 11 to 12, characterized in that: The communication device is further configured to report the detection data corresponding to the detection reporting instance to the detection control device according to the information in the IOAM header in any one of the following ways: Mode 1: After the communication device detects that the message of the target service flow is switched from a target message to a non-target message according to the target tag in the IOAM header, the communication device reports the detection data corresponding to the detection reporting instance to the detection control device; Method 2: The IOAM header also includes an automatic detection flag, which is used to indicate whether the node through which the target message flows needs to automatically perform IOAM detection on the target message without receiving the instance configuration information of the detection control device. The communication device determines that the automatic detection stops according to the automatic detection flag in the IOAM header, and then reports the detection data corresponding to the detection reporting instance to the detection control device; Method 3: The IOAM header also includes a marking period, and the communication device reports the detection data corresponding to the detection reporting instance to the detection control device according to the marking period in the IOAM header.

14. An IOAM detection and processing system, comprising an encapsulation node, a decapsulation node, a transmission node and the detection control device as described in claim 9, wherein the encapsulation node is communicatively connected with the transmission node and the decapsulation node in sequence: the encapsulation node is a communication device for the second processor as described in any one of claims 10 to 13 to execute a first IOAM detection processing program, the transmission node is a communication device for the second processor as described in any one of claims 10 to 13 to execute a second IOAM detection processing program, and the decapsulation node is a communication device for the second processor as described in any one of claims 10 to 13 to execute a third IOAM detection processing program.

15. A storage medium, characterized in that: The storage medium stores at least one of an IOAM detection configuration program, a first IOAM detection processing program, a second IOAM detection processing program and a third IOAM detection processing program. The IOAM detection configuration program can be executed by one or more processors to implement the steps of the IOAM detection configuration method as described in claim 1; the first IOAM detection processing program can be executed by one or more processors to implement the steps of the IOAM detection processing method as described in any one of claims 2 to 5; the second IOAM detection processing program can be executed by one or more processors to implement the steps of the IOAM detection processing method as described in claim 6; the third IOAM detection processing program can be executed by one or more processors to implement the steps of the IOAM detection processing method as described in any one of claims 7 to 8.

Images