Fault detection method, device and equipment and computer readable storage medium

Abstract

The invention discloses a fault detection method, device and equipment and a computer readable storage medium, and belongs to the technical field of communication. The method comprises the steps that a first node generates a first detection message based on first path information determined by a received first user message, the first detection message comprises the first path information and first service level agreement (SLA) information, and the first path information indicates a transmission path of the first user message and the first detection message; the first node sends a first detection message to a second node on the transmission path; the second node generates a second detection message including second network side state information according to the first SLA information in the first detection message, the second detection message is sent to the first node, and the second network side state information indicates whether a fault exists between the first node and the second node or not. Since the path transmission of the first detection message is the same as that of the first user message, the fault on the transmission path can be detected in time based on the first SLA information in the first detection message.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a fault detection method, apparatus, device and computer-readable storage medium. Background Art

[0002] With the continuous development of communication technology, the scale of networks has gradually increased, and there are more and more unstable factors in the network, and failures are occurring more and more frequently. Therefore, it is necessary to perform fault detection on the network that transmits business flows, monitor the network in real time to see if there are any failures, and perceive network failures in a timely manner to ensure that the network can provide high-quality, stable and reliable network services and achieve normal transmission of business flows. Summary of the invention

[0003] The present application provides a fault detection method, apparatus, device and computer-readable storage medium to timely detect faults on the transmission path of user messages. The technical solution is as follows:

[0004] In a first aspect, a fault detection method is provided, which is applied to a first node, and the method includes: generating a first detection message based on first path information, the first path information is determined based on a first user message received by the first node, the first detection message includes first path information and first service level agreement (SLA) information, and the first path information is used to indicate a transmission path of the first user message and the first detection message; sending the first detection message to a second node, the second node is a node on the transmission path, and the first SLA information included in the first detection message is used by the second node to determine whether there is a fault between the first node and the second node.

[0005] The first detection message in the present application includes the first path information, so that the first detection message and the first user message are transmitted along the same transmission path, and the detection of the fault on the transmission path of the first user message is realized, and the detection is more accurate. By carrying the first SLA information in the first detection message, there is no need for the second node to obtain the first SLA information by other means, so that the second node can quickly detect the fault based on the first SLA information in the first detection message.

[0006] In a possible implementation, the first detection message also includes first indication information, first device-side status information, and first network-side status information, the first indication information is used to indicate the fault direction corresponding to the first device-side status information and the first network-side status information, the first device-side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends a first user message to the first node, the first network-side status information indicates whether there is a fault between the first node and the second node, and the first network-side status information is perceived by the first node. By combining the first indication information, the first device-side status information, and the first network-side status information, the detailed fault situation perceived by the first node can be sent to the second node.

[0007] In a possible implementation, the first detection message further includes a detection type identifier, which is used to indicate a detection type of the first detection message, and the detection type includes one of connectivity detection, packet loss rate detection, delay detection, and jitter detection. Different detection types can be distinguished by the detection type identifier, so that detection based on the detection type can be more accurate and detailed.

[0008] In a possible implementation, when the detection type is connectivity detection, the first SLA information includes a detection period, which indicates the time interval between two consecutive first detection messages; or, when the detection type is packet loss rate detection, the first SLA information includes the number of first detection messages sent by the first node within the first time period; or, when the detection type is delay detection or jitter detection, the first SLA information includes the first timestamp of the first node sending the first detection message. Different first SLA information ensures that detection of different detection types can be implemented.

[0009] In a possible implementation, the first SLA information is located in a first load field in the first detection message, and the first detection message also includes length information, and the length information indicates the length of the first load field. By carrying the first SLA information in the first load field and indicating the length of the first load field by the length information, the second node can quickly and accurately obtain the first SLA information based on the first detection message.

[0010] In a possible implementation, the first detection message also includes a detection identifier, which is used to indicate that the type of the first detection message is a detection message. The detection identifier can clearly identify the type of the first detection message, so that the second node can identify the first detection message after receiving the first detection message and detect the fault based on the first detection message, thereby improving the detection efficiency.

[0011] In a possible implementation, after sending the first detection message to the second node, the method further includes: receiving a second detection message sent by the second node based on the first detection message, the second detection message including second network side status information, the second network side status information indicating whether there is a fault between the first node and the second node, and the second network side status information is determined by the second node based on the first SLA information. By receiving the second detection message, the first node can determine whether there is a fault between the first node and the second node based on the second network side status information in the second detection message.

[0012] In a possible implementation, the second detection message also includes second indication information and first device side status information, and the second indication information is used to indicate the fault direction corresponding to the first device side status information and the second network side status information. By combining the second indication information, the first device side status information and the second network side status information, the first node can perceive the detailed fault situation.

[0013] In a possible implementation, when the second network side status information indicates that a fault exists between the first node and the second node, the second network side status information is further used to indicate the type of fault. The second network side status information indicates the type of fault so that the first node can not only clearly identify the presence of a fault between the first node and the second node, but also the type of fault, so that the fault situation perceived by the first node is more detailed.

[0014] In a possible implementation, after receiving the second detection message sent by the second node based on the first detection message, it also includes: if the second detection message satisfies the first condition, sending the first fault information to the first user device, the first condition including at least one of the first device side status information indicating that there is a fault between the first user device and the first node and the second network side status information indicating that there is a fault between the first node and the second node. If there is a fault between the first node and the first user device, or between the first node and the second node, the first fault information is sent to the first user device, so that the first user device knows that there is a fault on the transmission path of the first user message, so that the first user device can subsequently perform path switching and other operations.

[0015] In a possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type. By sending the fault location and the fault type to the first user equipment, the first fault information obtained by the first user equipment is more detailed and accurate.

[0016] In a possible implementation, before generating the first detection message based on the first path information, it also includes: generating a first detection message template based on the first path information, the first detection message template includes the first path information, and the first detection message template is used to generate the first detection message. The first detection message template is generated by the first path information in the first user message, so that the first node can continuously generate the first detection message based on the first detection message template, and the efficiency is high. In addition, by continuously sending multiple first detection messages to the second node, the fault condition of the transmission path is continuously detected, so as to timely discover and locate the fault.

[0017] In a possible implementation, an active maintenance association end point (MEP) is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range. By deploying the source MEP and the sink MEP to specify the detection range, the first node and the second node are prevented from performing fault detection on the part beyond the range, the detection pressure of the first node and the second node is reduced, and resource waste is avoided.

[0018] In a second aspect, a fault detection method is provided, which is applied to a second node, and includes: receiving a first detection message sent by a first node, the first detection message including first path information and first service level agreement SLA information, the first path information is determined based on a first user message received by the first node, and the first path information is used to indicate a transmission path of the first detection message; based on the first SLA information, determining second network side status information, the second network side status information indicating whether there is a fault between the first node and the second node; generating a second detection message according to the second network side status information, the second detection message including the second network side status information; and sending the second detection message to the first node. The second node determines the second network side status information that can indicate whether there is a fault between the first node and the second node according to the first SLA information in the first detection message, and returns it to the first node to implement fault detection.

[0019] In a possible implementation, the first detection message also includes first indication information, first device-side status information, and first network-side status information, the first indication information is used to indicate the fault direction corresponding to the first device-side status information and the first network-side status information, the first device-side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends a first user message to the first node, the first network-side status information indicates whether there is a fault between the first node and the second node, and the first network-side status information is perceived by the first node. By combining the first indication information, the first device-side status information, and the first network-side status information, the detailed fault situation perceived by the first node can be sent to the second node.

[0020] In a possible implementation, the second detection message also includes first device-side status information and second indication information, and the second indication information is used to indicate the fault direction corresponding to the first device-side status information and the second network-side status information; when the second network-side status information indicates that there is a fault between the first node and the second node, the second network-side status information is also used to indicate the fault type. By combining the second indication information, the first device-side status information and the second network-side status information, the first node can perceive the detailed fault situation.

[0021] In a possible implementation, after generating the second detection message according to the second network side status information, it also includes: when the second detection message satisfies the first condition, sending the first fault information to the second user device, the first condition includes at least one of the first device side status information indicating that there is a fault between the first user device and the first node and the second network side status information indicating that there is a fault between the first node and the second node, and the second user device is a device that interacts with the first user device. If there is a fault between the first node and the first user device, or there is a fault between the first node and the second node, the second fault information is sent to the second user device, so that the second user device knows that there is a fault on the transmission path of the first user message, so that the second user device can subsequently perform operations such as path switching.

[0022] In a possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type. The fault location and the fault type are sent to the second user equipment, so that the second fault information obtained by the second user equipment is more detailed.

[0023] In a possible implementation, there are multiple second nodes, and a protocol channel is established between every two second nodes among the multiple second nodes. The protocol channel is used for the multiple second nodes to send the first SLA information to each other, and the second network side state information is determined by at least one second node among the multiple second nodes. The multiple second nodes send the first SLA information to each other, so that the multiple second nodes can sense whether multiple paths have faults to perform path switching.

[0024] In a possible implementation, an active maintenance endpoint MEP is deployed on the first node, a sink MEP is deployed on the second node, the source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range. By deploying the source MEP and the sink MEP to specify the detection range, the first node and the second node are prevented from performing fault detection on the part beyond the range, the detection pressure of the first node and the second node is reduced, and resource waste is avoided.

[0025] In a third aspect, a fault detection device is provided, which is applied to a first node and includes:

[0026] a first processing module, configured to generate a first detection message based on first path information, where the first path information is determined based on a first user message received by the first node, the first detection message including the first path information and first service level agreement SLA information, and the first path information is used to indicate a transmission path of the first user message and the first detection message;

[0027] The first transceiver module is used to send a first detection message to a second node, where the second node is a node on a transmission path. The first SLA information included in the first detection message is used by the second node to determine whether there is a fault between the first node and the second node.

[0028] In a possible implementation, the first detection message also includes first indication information, first device side status information and first network side status information, the first indication information is used to indicate the fault direction corresponding to the first device side status information and the first network side status information, the first device side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends a first user message to the first node, the first network side status information indicates whether there is a fault between the first node and the second node, and the first network side status information is perceived by the first node.

[0029] In a possible implementation, the first detection message further includes a detection type identifier, where the detection type identifier is used to indicate a detection type of the first detection message, and the detection type includes one of connectivity detection, packet loss rate detection, delay detection, and jitter detection.

[0030] In one possible implementation, when the detection type is connectivity detection, the first SLA information includes a detection period, which indicates the time interval between two consecutive sending of first detection messages; or, when the detection type is packet loss rate detection, the first SLA information includes the number of first detection messages sent by the first node within a first time period; or, when the detection type is delay detection or jitter detection, the first SLA information includes a first timestamp when the first node sends the first detection message.

[0031] In a possible implementation manner, the first SLA information is located in a first payload field in a first detection message, and the first detection message further includes length information, where the length information indicates the length of the first payload field.

[0032] In a possible implementation manner, the first detection message further includes a detection identifier, and the detection identifier is used to indicate that the type of the first detection message is a detection message.

[0033] In one possible implementation, the first transceiver module is also used to receive a second detection message sent by the second node based on the first detection message, the second detection message includes second network side status information, the second network side status information indicates whether there is a fault between the first node and the second node, and the second network side status information is determined by the second node based on the first SLA information.

[0034] In a possible implementation, the second detection message also includes second indication information and first device side status information, and the second indication information is used to indicate a fault direction corresponding to the first device side status information and the second network side status information.

[0035] In a possible implementation manner, when the second network-side status information indicates that a fault exists between the first node and the second node, the second network-side status information is further used to indicate the type of fault.

[0036] In one possible implementation, the first transceiver module is also used to send first fault information to the first user device when the second detection message satisfies the first condition, and the first condition includes at least one of the first device side status information indicating that there is a fault between the first user device and the first node and the second network side status information indicating that there is a fault between the first node and the second node.

[0037] In one possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type.

[0038] In a possible implementation manner, the first processing module is further used to generate a first detection message template based on the first path information, the first detection message template includes the first path information, and the first detection message template is used to generate the first detection message.

[0039] In a possible implementation, an active maintenance endpoint MEP is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range.

[0040] In a fourth aspect, a fault detection device is provided, which is applied to a second node and includes:

[0041] A second transceiver module is used to receive a first detection message sent by the first node, where the first detection message includes first path information and first service level agreement SLA information, where the first path information is determined based on a first user message received by the first node, and the first path information is used to indicate a transmission path of the first detection message;

[0042] A second processing module, configured to determine second network side status information based on the first SLA information, where the second network side status information indicates whether there is a fault between the first node and the second node;

[0043] The second processing module is further used to generate a second detection message according to the second network side state information, where the second detection message includes the second network side state information;

[0044] The second transceiver module is further used to send a second detection message to the first node.

[0045] In a possible implementation, the first detection message also includes first indication information, first device side status information and first network side status information, the first indication information is used to indicate the fault direction corresponding to the first device side status information and the first network side status information, the first device side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends a first user message to the first node, the first network side status information indicates whether there is a fault between the first node and the second node, and the first network side status information is perceived by the first node.

[0046] In a possible implementation, the second detection message also includes first device side status information and second indication information, and the second indication information is used to indicate the fault direction corresponding to the first device side status information and the second network side status information; when the second network side status information indicates that there is a fault between the first node and the second node, the second network side status information is also used to indicate the fault type.

[0047] In one possible implementation, the second transceiver module is also used to send first fault information to the second user device when the second detection message satisfies the first condition, the first condition including at least one of the first device side status information indicating that there is a fault between the first user device and the first node and the second network side status information indicating that there is a fault between the first node and the second node, and the second user device is a device that interacts the first user message with the first user device.

[0048] In one possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type.

[0049] In one possible implementation, there are multiple second nodes, and a protocol channel is established between every two of the multiple second nodes. The protocol channel is used for the multiple second nodes to send first SLA information to each other, and the second network side status information is determined by at least one second node among the multiple second nodes.

[0050] In a possible implementation, an active maintenance endpoint MEP is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range.

[0051] In a fifth aspect, another communication device is provided, the device comprising: a network interface, a memory, and a processor. The network interface, the memory, and the processor communicate with each other through an internal connection path, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the network interface to receive signals and control the network interface to send signals, and when the processor executes the instructions stored in the memory, the processor executes the method in the first aspect or any possible implementation of the first aspect and the method in the second aspect or any possible implementation of the second aspect.

[0052] Optionally, there are one or more processors and one or more memories.

[0053] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0054] In a sixth aspect, a communication system is provided, the system comprising the fault detection device in the third aspect or any possible implementation of the third aspect and the fault detection device in the fourth aspect or any possible implementation of the fourth aspect.

[0055] In the seventh aspect, a computer program (product) is provided, which includes: computer program code, which, when executed by a computer, enables the computer to execute the method in the first aspect or any possible implementation of the first aspect and the method in the second aspect or any possible implementation of the second aspect.

[0056] In an eighth aspect, a computer-readable storage medium is provided, which stores a program or instruction. When the program or instruction runs on a computer, the method in the above-mentioned first aspect or any possible implementation of the first aspect and the method in the second aspect or any possible implementation of the second aspect are executed.

[0057] In the ninth aspect, a chip is provided, comprising a processor for calling and executing instructions stored in a memory from the memory, so that a computer equipped with the chip executes the method in the first aspect or any possible implementation of the first aspect and the method in the second aspect or any possible implementation of the second aspect.

[0058] In the tenth aspect, another chip is provided, comprising: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, a computer equipped with the chip executes the method in the first aspect or any possible implementation of the first aspect and the method in the second aspect or any possible implementation of the second aspect.

[0059] It should be understood that the beneficial effects achieved by the technical solutions of the third to tenth aspects of the present application and the corresponding possible implementation methods can be referred to the technical effects of the first and second aspects and their corresponding possible implementation methods mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 A schematic diagram of an implementation scenario of a fault detection method provided in an embodiment of the present application;

[0061] Figure 2 A flowchart of a fault detection method provided in an embodiment of the present application;

[0062] Figure 3 A schematic diagram of the structure of a first detection message provided in an embodiment of the present application;

[0063] Figure 4 A schematic diagram of the expanded structure of a stream instruction identification field provided in an embodiment of the present application;

[0064] Figure 5A schematic diagram of the expanded structure of a stream instruction header field provided in an embodiment of the present application;

[0065] Figure 6 A schematic diagram of the expanded structure of a stream instruction extension header field provided in an embodiment of the present application;

[0066] Figure 7 A schematic diagram of the structure of another first detection message provided in an embodiment of the present application;

[0067] Figure 8 A schematic diagram of the structure of an extended field provided in an embodiment of the present application;

[0068] Fig. 9 A schematic diagram of a multi-homing network structure provided in an embodiment of the present application;

[0069] Fig.10 A schematic diagram of a single-homing networking scenario provided in an embodiment of the present application;

[0070] Fig.11 A schematic diagram of a fault detection process in a single-homing networking scenario provided in an embodiment of the present application;

[0071] Fig.12 A schematic diagram of a fault detection process in a multi-homing networking scenario provided in an embodiment of the present application;

[0072] Fig.13 A schematic diagram of the structure of a fault detection device provided in an embodiment of the present application;

[0073] Fig.14 A schematic diagram of the structure of another fault detection device provided in an embodiment of the present application;

[0074] Fig.15 A schematic diagram of the structure of a fault detection device provided in an embodiment of the present application;

[0075] Fig.16 A schematic diagram of the structure of another fault detection device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0077] With the development of communication technology, in order to ensure the normal transmission of messages, it is necessary to perform fault detection on the message transmission network. When performing fault detection on the transmission network, the relevant technology usually uses two detection methods: flow detection and protocol message detection. Flow detection requires inserting a detection message header into the user message so that the user message has a detection function, and realizes the fault detection of the transmission network by transmitting the user message with the detection function in the transmission network. However, this flow detection method depends on the user message sent by the user device. During the time period when the user device does not send the user message, it is impossible to perform fault detection on the transmission network, and it is difficult to ensure the timeliness of fault detection.

[0078] Protocol message detection needs to generate detection messages based on the protocol types supported by network devices in the transmission network, and realize transmission network fault detection through the transmission of detection messages. However, it is difficult to determine the transmission path of the detection message in the transmission network, and it is difficult to ensure that the transmission path of the detection message is consistent with the path of the user message sent by the user device. Therefore, it is difficult to switch the transmission path of the user message according to the detection result, and it is difficult to ensure the normal transmission of the user message.

[0079] The embodiment of the present application provides a fault detection method, which can realize fault detection based on user messages, and can still realize fault detection on the transmission network during the time period when the user equipment does not send user messages, so as to ensure the timeliness of fault detection. In addition, the method can also ensure that the transmission path of the detection message and the user message in the transmission network is consistent, thereby improving the accuracy of detection.

[0080] For example, see Figure 1, a schematic diagram of an implementation scenario of a fault detection method is shown. The implementation scenario includes a first user device 11, a transmission network and a second user device 14, the transmission network includes a first node 12 and a second node 13, the transmission network is a network composed of network devices that can be used to implement message transmission, and the transmission network can be, for example, a packet transport network (PTN), an access transport network (ATN), an optical smart network (OSN) or an optical transport network (OTN). The first node 12 can be connected to the first user device 11 and the second node 13 through wired or wireless communication, and the second node 13 can also be connected to the second user device 14 through wired or wireless communication. The first node 12 and the second node 13 are network devices in the transmission network, for example, they can be devices such as routers or switches that can implement message forwarding. Other network devices can be connected between the first node 12 and the second node 13, between the first node 12 and the first user device 11, and between the second node 13 and the second user device 14.

[0081] In a possible implementation, for the first direction (the direction from the first node 12 to the second node 13), an active MEP is deployed on the first node 12, and a sink MEP is deployed on the second node 13. The source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message exchanged between the first node 12 and the second node 13, and the detection range indicates that the first node and the second node perform fault detection within the detection range. Optionally, for the second direction (the direction from the second node 13 to the first node 12), a sink MEP may be deployed on the first node 12, and an active MEP may be deployed on the second node 13. By deploying the source MEP and the sink MEP to specify the detection range, the first node and the second node are prevented from performing fault detection on the part beyond the range, the detection pressure of the first node and the second node is reduced, and resource waste is avoided. In addition, the direction of the transmission network can be clearly identified, so that fault detection is more accurate.

[0082] See also Figure 2 , shows a schematic diagram of a fault detection method, in which the method is applied to Figure 1 Taking the first node and the second node in as an example, the method is not limited to the following S201 to S206.

[0083] S201, a first node generates a first detection message based on first path information, the first path information is determined based on a first user message received by the first node, the first detection message includes first path information and first SLA information, and the first path information is used to indicate a transmission path of the first user message and the first detection message.

[0084] The first path information is information that can indicate the transmission path of the first user message, and the first path information includes but is not limited to the source address (source address, SA), destination address (destination address, DA), source media access control (media access control, MAC) address, destination MAC address, source port number, destination port number and virtual local area network (virtual local area network, VLAN) identifier and other information of the transmission path, wherein the source address and the destination address may be Internet protocol (internet protocol, IP) addresses. The first path information may be determined based on the first user message sent by the first user device received by the first node, for example, the first path information may be included in the message header of the first user message.

[0085] After acquiring the first path information, the first node may generate a first detection message based on the first path information. The embodiment of the present application does not limit the method for generating the first detection message based on the first path information. Exemplarily, a first detection message template may be generated based on the first path information, and the first detection message template is used to generate the first detection message. Afterwards, the first detection message is generated based on the first detection message template. Optionally, the first detection message template may include the first path information.

[0086] Taking the first node as the source node for the first user device to access the transmission network as an example, after the forwarding channel is deployed on the transmission network, the first user device sends the first user message to the first node. The first user message enters the transmission network for the first time through the first node. The first node learns the characteristic rules of the first user message, determines the first path information, and generates a first detection message template including the first path information. The structure of the first detection message template can be found in Figure 3 , Figure 3 This is a message structure obtained by expanding the in-band operation administration and maintenance (IOAM) message. Figure 3Different cells in represent different fields. The first node adds the learned characteristic rule of the first user message to the multi-protocol label switching payload (multi-protocol labelswitching payload, Mpls payload) field of the first detection message template. The Mpls payload field can be an IP message header or an Ethernet (ether, ETH) message header. The Mpls field can also be called a detection message header. The first node can generate the first path information according to the learned characteristic rule of the first user message, and the first path information can be located in the transmission network forwarding message header of the first detection message template. Figure 3 The first path information shown in includes DA / SA / VLAN, port number 0x8847, segment routing list (segment routing list, SR list), segment routing path label (segment routing path label, SRpath label) and virtual routing and forwarding label (virtual routing and forwarding label, VRF label). The first detection template is used to encapsulate the first detection message, that is, the message header of the first detection message is encapsulated according to the first detection message template.

[0087] In addition, the first node can also generate a feature flow instance based on the first user message, and the feature flow instance includes a flow identification (flow identification, flow ID). The first node can also add the feature flow instance to the first detection message template, so that the first detection message generated based on the first detection message template can also carry the feature flow instance, and the binding of the feature flow instance and the first detection message is realized. The embodiment of the present application generates the first detection message template, so that the first node can continuously generate multiple first detection messages based on the first detection message template, rather than only being able to generate the first detection message when receiving the first user message, so that the first node can still detect the transmission network by sending the first detection message in the time period when the first user device does not send the first user message, and timely detect the fault in the transmission network, and ensure the timeliness of detection. In addition, the efficiency of generating the first detection message based on the first detection template is higher.

[0088] After the first node generates the first detection message template, the first SLA information and other information used for fault detection may be added to the first detection message template to generate the first detection message.

[0089] In one possible implementation, in addition to the first path information and the first SLA information, the first detection message may also include first indication information, first device side status information and first network side status information, the first device side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends the first user message to the first node, the first network side status information indicates whether there is a fault between the first node and the second node, and the first network side status information is perceived by the first node.

[0090] The first indication information may also be referred to as back-insertion information or direction information. The first indication information can indicate that the detection message is a detection message inserted from the source node to the transmission network or that the detection message is a detection message inserted from the destination node to the transmission network, and can also be used to indicate the fault direction corresponding to the first device-side status information and the first network-side status information. For example, if the first indication information is 0, it means that the first detection message is a detection message inserted from the first node where the active MEP is deployed, and that the fault indicated by the first device-side status information is a fault between the first node and the first user device, and that the fault indicated by the first network-side status information is whether there is a fault between the first node and the second node as sensed by the first node.

[0091] By combining the first indication information, the first device-side status information and the first network-side status information, the detailed fault condition perceived by the first node can be sent to the second node.

[0092] Optionally, the first detection message may further include a detection identifier, which is used to indicate that the type of the first detection message is a detection message. The detection identifier can clearly identify the type of the first detection message, so that the second node can identify the first detection message after receiving the first detection message and detect the fault based on the first detection message, thereby improving the detection efficiency.

[0093] In addition, the first detection message may further include a detection type identifier, which is used to indicate the detection type of the first detection message. Exemplarily, the detection type includes one of connectivity detection, packet loss rate detection, delay detection, and jitter detection.

[0094] The first SLA information carried in the first detection message is different due to different detection types. Exemplarily, in the case where the detection type is connectivity detection, the first SLA information may include a detection period, and the detection period indicates the time interval between two consecutive transmissions of the first detection message. For example, if the detection period is 10 seconds, the time interval between the first node transmitting the first detection message of the connectivity detection type for the first time and the second node transmitting the first detection message of the connectivity detection type for the second time is 10 seconds.

[0095] In the case where the detection type is packet loss rate detection, the first SLA information includes the number of first detection messages sent by the first node within the first time period. The size of the first time period can be set according to the detection granularity or user demand. If the user demand is high or the detection granularity is fine, the first time period can be set to a shorter period of time. If the user demand is low or the detection granularity is coarse, the first time period can be set to a longer period of time. The number of first detection messages sent by the first node within the first time period can also be called the number of packets sent. The number of packets sent can be included in the first detection message whose detection type is packet loss rate detection and sent within the first time period, and can also be included in each first detection message whose detection type is packet loss rate detection and sent within the first time period.

[0096] In the case where the detection type is delay detection or jitter detection, the first SLA information includes a first timestamp when the first node sends the first detection message. The first timestamp can be used by the second node to determine the time when the first node sends the first detection message, so that the second node can determine the time required for the first detection message to be transmitted in the transmission path according to the first timestamp and the time when the first detection message is received, so as to determine the transmission delay of the first detection message between the first node and the second node.

[0097] Different detection types are distinguished by detection type identifiers, so that detection based on the detection type can be more accurate and detailed. Different first SLA information ensures that detection of different detection types can be implemented.

[0098] In a possible implementation, the first SLA information is located in a first load field in the first detection message, and the first detection message also includes length information, and the length information indicates the length of the first load field. By carrying the first SLA information in the first load field and indicating the length of the first load field by the length information, the second node can quickly and accurately obtain the first SLA information based on the first detection message.

[0099] For example, see Figures 4 to 6 , both show schematic diagrams of partial structures of the first detection message. Figures 4 to 6 for Figure 3 The expansion of some fields in Figures 4 to 6 The numbers in each field represent bits. Figure 4 for Figure 3The expanded diagram of the flow instruction indicator (FII) field in FIG. 1 includes the FII label (Label) field, the expansion (EXP) field, the stack bottom label field, and the survival time (TTL) field. The value of FII Label can be a to be determined (TBD), such as 12. The stack bottom label field is 1, which means that the field is the stack bottom label.

[0100] Figure 5 for Figure 3 The expansion of the flow instruction header (FIH) field in the flow instruction header. Before the expansion, the FIH field includes a flow ID field, an L field, a D field, an R field, an R / S field, and an HTI field. After the expansion, the R field is expanded to a detect (detect, D) field. The detect field can also be called a feature field or a specific field for carrying a detection identifier. The detection field can reflect the difference between the first detection message and the first user message. For example, if the content of the field is 1, it represents that the message type of the message including the field is a detection message rather than a first user message or other types of messages. After receiving the message and identifying the detection field, each node will extract and analyze the SLA information carried by the message and terminate the message. The embodiment of the present application does not limit the method for terminating the detection message. For example, the detection message can be discarded.

[0101] Figure 6 for Figure 3 The expansion of the flow instruction extension header (FIEH) field. Before the expansion, the FIEH field is an optional field, including the flow identification extension (extend, Ext) field, the reserved 1 field, the V field, the period field, the destination IP mask (destination IP mask, DIPMask) field, the source IP mask (source IP mask, SIP Mask) field and the reserved 2 field. After the expansion, the reserved 1 field is expanded into the operation field, and the reserved 2 field is expanded into the flags field, the length field and the first load field. The first load field can be, for example, Figure 6 The detection protocol data unit payload (Detect PDU Payload) field in the.

[0102] The content of the operation field can be used to indicate the detection type of the detection message. If the detection type is connectivity detection, the content of this field can be a continuity check message (CCM); if the detection type is packet loss rate detection, the content of this field can be a loss measurement message (LMM); if the detection type is delay detection or jitter detection, the content of this field can be a delay measurement message (DMM).

[0103] The Flags field is used to fill in the insertion indication information, that is, the first indication information. If the insertion indication information is 0, it means that the detection message is the first detection message sent by the first node of the forward deployed active MEP. In addition, if the detection type of the first detection message is connectivity detection, the Flags field can also be used to fill in the detection period, that is, the CCM period.

[0104] The length field is used to fill in the length of the first payload field to indicate the end position of the detection information header. The detection information header includes the FII field, the FIH field, and the FIEH field.

[0105] The first load field can be used to edit and fill in fault information, which includes the first indication information, the first device side status information, and the first network side status information mentioned above. For example, in a normal scenario, the first node as a source node can fill in the first load field as: 0_00_00, indicating forward_device side normal_network side normal, that is, in the transmission direction from the first node to the second node, there is no fault between the first node and the first user device, and there is no fault between the first node and the second node.

[0106] In addition, the second node, as the source node in the other direction, can also fill in the first load field as: 0_00_00, indicating forward_device side normal_network side normal, that is, in the transmission direction from the second node to the first node, there is no fault between the second node and the second user device, and there is no fault between the first node and the second node.

[0107] In a scenario where a fault occurs between the first node and the first user device, the first node can determine that there is a fault between the first node and the first user device through information such as the status of the access port, then the first node fills in the field as: 0_01_00, indicating forward_device side fault_network side normal, that is, in the transmission direction from the first node to the second node, there is a fault between the first node and the first user device, and there is no fault between the first node and the second node.

[0108] In a scenario where there is a connectivity failure, a delay failure, or a packet loss rate failure between the first node and the second node, the first node may not be able to perceive the existence of a failure between the first node and the second node before sending the first detection message. Therefore, the first load field may also be filled in as: 0_00_00, indicating forward_device side normal_network side normal, that is, in the transmission direction from the first node to the second node, there is no failure between the first node and the first user device, and there is no failure between the first node and the second node.

[0109] In a possible implementation, if the transmission network does not need to encapsulate the first user message, the first node can directly forward the first user message according to the message header of the first user message. In this case, the first detection message template determined by the first node is the message header of the first user message obtained by learning, and the first node only needs to expand some fields in the first detection message template to obtain the first detection message.

[0110] For example, see Figure 7 , shows a schematic diagram of the format of another first detection message, which is obtained based on extending the message header of the fourth version of the Internet Protocol (internet protocol version 4, IPv4) message. Figure 7 The numbers in brackets in each field represent the size of each field or the number of bits occupied by each field. The number of bits occupied by each field can be found in Figure 7 0 to 31, a total of 32 bits are marked. Before extension, the IPv4 message header includes a version field, a header length (HLEN) field, a service type field, a total length field, an identification field, a flag field, a fragment offset field, a time to live field, a protocol field, a header checksum field, a source IP address field, a destination IP address field, an IP options field, a padding field, and a data field.

[0111] The embodiment of the present application can expand the IP optional field and the padding field. The size of the IP optional field is any size (If Any), which means that if the IP optional field needs to be filled in, the IP optional field can be any required size. The size of the padding field can be 32 bits or any size (32-If Any). Figure 8 , showing a schematic diagram of the structure of the extended field, the embodiment of the present application can expand the IP optional field and the padding field as follows Figure 8 The detection field, operation field, flag field, length field, flow identification field and first load field shown in the figure can be referred to in the previous text for the description of each field. Figure 3 and Figure 4 The description of each field in is not repeated here.

[0112] In addition, after the first user message enters the transmission network, the first node forwards the first user message according to the service model deployed on the first node. For example, if the first node is configured with a level 3 (L3) VPN for IP messages to enter the transmission network, and a model for forwarding in a segment routing transport profile (SR-TP) tunnel on the transmission network, and the features of the message header of the first user message hit the forwarding model deployed on the first node, the first node forwards the first user message according to the forwarding model.

[0113] Since the first detection message constructed by the first node is consistent with the outermost transmission network forwarding message header of the first user message, or in other words, the first detection message is consistent with the first path information included in the message header of the first user message, it is ensured that the forwarding path of the first detection message and the first user message in the transmission network is consistent.

[0114] S202, the first node sends a first detection message to the second node, the second node is a node on the transmission path, and the first SLA information included in the first detection message is used by the second node to determine whether there is a fault between the first node and the second node.

[0115] After generating the first detection message, the first node can periodically send the first detection message to the second node. The period can be set according to experience or configured according to user needs, and the embodiment of the present application does not limit this. In addition to the detection period, the first timestamp and the number of packets sent in S201, the first SLA information in the first detection message can also include information used by the second node to calculate SLA indicators, such as the packet loss rate threshold, delay threshold or jitter threshold negotiated between the transmission network and the first user device or the second user device. In this case, the second node can determine the network status between the first node and the second node based on the first SLA information, and can also determine whether the network status between the first node and the second node meets the requirements of the first user device or the second user device for network quality based on various thresholds to determine whether there is a fault between the first node and the second node.

[0116] Optionally, the first SLA information may be included in a first load field of the first detection message.

[0117] S203, the second node receives a first detection message sent by the first node, the first detection message includes first path information and first SLA information, the first path information is determined based on a first user message received by the first node, and the first path information is used to indicate a transmission path of the first detection message.

[0118] After the first node sends the first detection message to the second node, the first detection message is transmitted to the second node along the same transmission path as the first user message, and the second node receives the first detection message.

[0119] Optionally, after receiving the first detection message, the second node may identify the first detection message, and if the second node identifies that the message type of the first detection message is a detection message, extract the first SLA information in the first detection message to determine whether there is a fault between the first node and the second node. The process of the second node determining whether there is a fault between the first node and the second node according to the first SLA information can refer to the description in S204, which will not be repeated here.

[0120] S204: The second node determines second network-side status information based on the first SLA information, where the second network-side status information indicates whether there is a fault between the first node and the second node.

[0121] The detection type of the first detection message is different, and the method for the second node to determine whether there is a fault between the first node and the second node is different. Below, different determination methods corresponding to different detection types are explained respectively, including but not limited to the following situations.

[0122] Case 1: When the detection type is connectivity detection, the first SLA information includes a detection period, and the detection period indicates the time interval between two consecutive transmissions of the first detection message. In this case, the second node can calculate the SLA indicator according to the number of first detection messages of the connectivity detection type received within N times the detection period to determine whether there is a fault between the first node and the second node, where N is a positive integer.

[0123] For example, if the second node receives N first detection messages of the detection type of connectivity detection within an N-fold period, it means that the first node and the second node can be connected normally and there is no connectivity failure. If the second node does not receive the first detection message of the detection type of connectivity detection within an N-fold period, or the number of first detection messages of the detection type of connectivity detection received by the second node within an N-fold period is less than the first threshold, it means that a connectivity failure occurs between the first node and the second node, and the transmission network between the first node and the second node is interrupted. The first threshold is determined based on the SLA between the transmission network and the first user equipment, or based on the SLA between the transmission network and the second user equipment. The first threshold may also be included in the first SLA information.

[0124] In case 2, when the detection type is packet loss rate detection, the first SLA information includes the number of first detection messages sent by the first node in the first time period. In this case, the second node can calculate the SLA indicator based on the number of packets sent included in the first SLA information and the number of packets received by the second node in the first time period to determine whether there is a fault between the first node and the second node.

[0125] For example, if the first SLA information in the first detection message indicates that the number of packets sent by the first node in the first time period is x, and the number of first detection messages of the detection type of packet loss rate detection received by the second node in the first time period is y, that is, the number of packets received by the second node in the first time period is y, then the second node can determine the packet loss rate between the first node and the second node according to the ratio of the difference between the number of packets received y and the number of packets sent x to the number of packets sent x. And the packet loss rate and the packet loss rate threshold can be compared. If the packet loss rate is greater than the packet loss rate threshold, it means that the packet loss rate between the first node and the second node exceeds the packet loss rate threshold negotiated by the transmission network and the first user equipment or the second user equipment. It can be considered that the packet loss between the first node and the second node is serious, and there is a packet loss fault between the first node and the second node. If the packet loss rate is less than the packet loss rate threshold, it means that the packet loss between the first node and the second node is within the range that the user can tolerate, and it can be considered that there is no packet loss fault between the first node and the second node.

[0126] Case 3: When the detection type is delay detection or jitter detection, the first SLA information includes the first timestamp when the first node sends the first detection message. In this case, the second node can record the second timestamp when receiving the first detection message, and calculate the SLA indicator according to the time interval between the first timestamp and the second timestamp to determine whether there is a fault between the first node and the second node.

[0127] If the time interval between the first timestamp and the second timestamp is greater than the delay threshold, it means that the delay between the first node and the second node exceeds the delay threshold negotiated between the transmission network and the first user equipment or the second user equipment, and it can be considered that the transmission delay between the first node and the second node is serious, and there is a delay fault between the first node and the second node. If the time interval between the first timestamp and the second timestamp is less than the delay threshold, it means that the delay between the first node and the second node is within the user's tolerable range, and it can be considered that there is no delay fault between the first node and the second node.

[0128] The second node can also analyze the delay calculated multiple times, determine the average value of the delay in the second time period, and compare the difference between the time interval between the first timestamp and the second timestamp and the average value of the delay. If the difference between the time interval and the average value of the delay is greater than the jitter threshold, it means that the jitter between the first node and the second node exceeds the jitter threshold negotiated by the transmission network and the first user device or the second user device. It can be considered that the delay between the first node and the second node is unstable and there is a jitter fault between the first node and the second node. If the difference is less than the jitter threshold, it means that the jitter size between the first node and the second node is within the user's tolerable range, and it can be considered that there is no jitter fault between the first node and the second node.

[0129] In a possible implementation, there are multiple second nodes, and a protocol channel is established between every two second nodes among the multiple second nodes. The protocol channel is used for the multiple second nodes to send first SLA information to each other, and the second network side status information is determined by at least one second node among the multiple second nodes. The protocol channel is established between the multiple second nodes, so that the multiple second nodes can be treated as one second node to achieve collaborative processing. At least one second node among the multiple second nodes can determine whether there is a fault on each path in the transmission network by comprehensively calculating the first SLA information included in the first detection message received by each second node.

[0130] For example, in a multi-homing network (one source, multiple sinks) scenario, Fig. 9Taking the one-source-two-destination scenario shown as an example, a protocol channel for exchanging SLA information is established between the second node 1 and the second node 2. In the first direction (first node-intermediate device 1-second node 1) and the third direction (first node-intermediate device 2-second node 2), the second node 1 and the second node 2 can determine the device for processing the first SLA information according to the master-slave status of the second node 1 and the second node 2. For example, if the second node 1 is the master node and the second node 2 is the backup node, the second node 2 can synchronize the number of first detection messages received within N times the period to the second node 1 through the protocol channel, and the second node 1 calculates the sum of the number of first detection messages received by the second node 1 and the second node 2 within N times the period. If the sum of the number of first detection messages received by the second node 1 and the second node 2 within N times the period is 0, the second node 1 can determine that the transmission network between the first node and the second node 1 and the first node and the second node 2 is interrupted.

[0131] In addition, the second node 2 can also synchronize the first SLA information included in the received first detection message with detection type of packet loss detection and the first detection message with detection type of delay detection to the second node 1 through the protocol channel, and the second node 1 determines whether there is a network failure on each path.

[0132] In a possible implementation, for a reverse service transmission channel, multiple forward second nodes are multiple reverse first nodes, the forward first node is the reverse second node, the reverse first nodes are all deployed with reverse source MEPs, and the reverse second nodes are all deployed with reverse sink MEPs. In this scenario, multiple first nodes will send detection messages to the second node, and the second node needs to count the detection messages sent by multiple second nodes, extract the SLA information carried in the detection messages sent by each second node, and calculate the SLA index.

[0133] After calculating the SLA indicator and determining whether there is a fault between the first node and the second node, the second node may generate second network-side status information to indicate whether there is a fault between the first node and the second node.

[0134] In the embodiment of the present application, the first detection message carries the first SLA information, so that the second node can calculate the SLA index without obtaining the first SLA information in other ways, and determine whether there is a fault on the transmission path, thereby improving the efficiency of fault detection. Since the embodiment of the present application can deploy both the source MEP and the sink MEP on the same node, that is, for different transmission directions of the transmission network, the network node can serve as the first node or the second node accordingly, therefore, a network node can determine the unidirectional SLA index of a certain transmission direction, and can also determine the bidirectional SLA index of two different transmission directions.

[0135] S205: The second node generates a second detection message according to the second network side status information, where the second detection message includes the second network side status information.

[0136] Among them, the second detection message may be the same as the format of the first detection message, or may be different from the format of the second detection message, and the embodiment of the present application does not limit this. In a possible implementation, the second node may generate a second detection message template according to the second user message sent by the received second user equipment, and the process of the second node generating the second detection message template according to the second user message can refer to the process of the first node generating the first detection message template according to the first user message, which will not be repeated here. For example, the second node can add the determined second network side state information to the second detection message template to generate a second detection message.

[0137] In the case where the received first detection message includes the first indication information, the first device-side status information and the first network-side status information, the second detection message also includes the first device-side status information and the second indication information, and the second indication information is used to indicate the fault direction corresponding to the first device-side status information and the second network-side status information; in the case where the second network-side status information indicates that there is a fault between the first node and the second node, the second network-side status information is also used to indicate the type of fault. By combining the second indication information, the first device-side status information and the second network-side status information, the first node can perceive the detailed fault situation. The second network-side status information indicates the type of fault, so that the first node can not only clearly identify the existence of a fault between the first node and the second node, but also the type of fault, so that the fault situation perceived by the first node is more detailed.

[0138] Exemplarily, if the second indication information is 1, it means that the second detection message is a detection message inserted by the host MEP deployed at the second point, the fault indicated by the first device side status information is a fault between the first node and the first user equipment, and the fault indicated by the second network side status information is whether there is a fault between the first node and the second node perceived by the first node.

[0139] In a normal scenario, that is, in a fault-free scenario, the second node as a host node will not send a second detection message carrying the second indication information and the first device side status information to the first node, but if the first device side status information indicates that there is a fault between the first user device and the first node or the second network side status information indicates that there is a fault between the first node and the second node, the second node may send a second detection message carrying the second indication information and the first device side status information to the first node.

[0140] The second detection message may carry the second indication information, the first device side status information, and the second network side status information in the same manner as the first detection message carries the first indication information, the first device side status information, and the first network side status information. The second node may fill in the second indication information, the first device side status information, and the second network side status information in the second load field of the second detection message. The second load field has the same structure and function as the first load field, which will not be described here. By combining the second indication information, the first device side status information, and the second network side status information, the first node can perceive the detailed fault situation.

[0141] For example, in a scenario where a fault occurs between the first node and the first user device, the first device side status information received by the second node is 01, indicating that there is a fault between the first node and the first user device. The second node fills in the second load field as: 1_01_00, indicating reverse_device side fault_network side normal, that is, in the reverse direction of the transmission direction from the first node to the second node, there is a fault between the first node and the first user device, and there is no fault between the first node and the second node.

[0142] In a scenario where there is a connectivity failure between the first node and the second node, the second node can fill in the second load field as: 1_00_01, indicating reverse_device side normal_network side failure, that is, in the reverse direction of the transmission direction from the first node to the second node, there is no failure between the first node and the first user device, there is a failure between the first node and the second node, and the failure type is a connectivity failure, and the transmission network side is blocked.

[0143] In a scenario where there is a packet loss failure between the first node and the second node, the second node can fill in the second load field as: 1_00_02, indicating reverse_device side normal_network side failure, that is, in the reverse direction of the transmission direction from the first node to the second node, there is no failure between the first node and the first user device, there is a failure between the first node and the second node, and the failure type is a packet loss failure, and the packet loss rate on the transmission network side exceeds the standard.

[0144] In the scenario where there is a delay failure between the first node and the second node, the second node can fill in the second load field as: 1_00_03, indicating reverse_device side normal_network side failure, that is, in the reverse direction of the transmission direction from the first node to the second node, there is no failure between the first node and the first user device, there is a failure between the first node and the second node, and the failure type is a delay failure, and the delay on the transmission network side exceeds the standard.

[0145] In a possible implementation, the second detection message may also include the number of first detection messages of packet loss detection type received by the second node within the first time period, or include a second timestamp of the first detection message of delay detection type received by the second node.

[0146] Exemplarily, the second detection message may further include a second flow identifier generated by the second node based on the second user message.

[0147] S206: The second node sends a second detection message to the first node.

[0148] After generating the second detection message, the second node sends the second detection message to the first node. The transmission path of the second detection message may be the same as or different from the transmission path of the first detection message, which is not limited in the embodiment of the present application.

[0149] After the second node sends the second detection message to the first node, the first node, as the destination node of the second detection message, can receive the second detection message sent by the second node based on the first detection message. By receiving the second detection message, the first node can determine whether there is a fault between the first node and the second node according to the second network side status information in the second detection message, and can identify and analyze the second detection message. When the analysis result indicates that the second detection message meets the first condition, the first node sends the first fault information to the first user device, and the second node sends the first fault information to the second user device, and the second user device is a device that interacts with the first user device The first condition includes at least one of the first device side status information indicating that there is a fault between the first user device and the first node and the second network side status information indicating that there is a fault between the first node and the second node.

[0150] If the second detection message meets the first condition, it means that there is a fault on the complete transmission path from the first user device to the second user device. Then, it is necessary to inform the first user device and the second user device of the fault so that the first user device and the second user device can perform protection switching measures such as path switching to avoid long-term damage to user services.

[0151] In a possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type. The fault type can be determined based on the value of the second network side state information. By sending the fault location and the fault type to the first user equipment and the second user equipment, the first fault information obtained by the first user equipment is more detailed and accurate.

[0152] In addition, by changing the bidirectional forwarding detection (BFD) protocol state between the first node and the first user device and the BFD protocol state between the second node and the second user device, the first user device and the second user device can sense the presence of a fault on the transmission path through the BFD protocol state, or closing the port between the first node and the first user device and the port between the second node and the second user device, so that the first user device and the second user device can sense the fault through the physical state of the port.

[0153] For example, see Fig.10 , shows a schematic diagram of a single-homing networking scenario. The transmission network includes 5 nodes from node A to node E, node A is connected to user equipment A, and node E is connected to user equipment B. If the transmission direction from node A to node E is specified as forward, the transmission direction from node E to node A is reverse. In the forward transmission path, user equipment A is the first user equipment, user equipment B is the second user equipment, the first node may be node A, and the second node may be node E. In the reverse transmission path, user equipment B is the first user equipment, user equipment A is the second user equipment, the first node may be node E, and the second node may be node A.

[0154] See also Fig.11 , showing the Fig.10 Schematic diagram of the fault detection process in a single-homing networking scenario. For the forward direction, node A deploys an active MEP. The fault detection process includes but is not limited to Fig.10 Steps a1 to a5 shown in .

[0155] Step a1, after receiving the first user message for the first time, node A (source node) learns the characteristic flow instance for the first time and generates a forward flow identifier 1. And according to the learned characteristic rule of the first user message, a first detection message template is generated.

[0156] In step a2, node A encapsulates the message header (indicated by the black rectangle) according to the learned features, that is, constructs the first detection message according to the first detection message template, and periodically inserts the first detection message into the transmission network, and the first detection message carries the first SLA information.

[0157] Afterwards, the first detection message is forwarded in the transmission network according to the forwarding service channel, and the forwarding path of the first detection message is consistent with that of the first user message.

[0158] Step a3: The node where the sink MEP is deployed (may also be directly referred to as the sink MEP) identifies and terminates the first detection message, and extracts the first SLA information.

[0159] Step a4: Calculate the SLA index of the transmission network according to the first SLA information. If the index exceeds a threshold, set the node where the sink MEP is deployed to a fault state.

[0160] Step a5, if the node where the sink MEP is deployed sets the fault state, the node where the sink MEP is deployed transmits the fault information downstream, that is, sends the first fault information to the second user equipment, and inserts the fault information back to the reverse service channel through the reverse second detection message, and the inserted fault information is the second network side status information in this application. Afterwards, the upstream user equipment and the downstream user equipment of the forward service channel, that is, the first user equipment and the second user equipment, can perform protection switching through the fault information, for example, switch the transmission path of the user message or stop sending the user message to the transmission network, etc.

[0161] In the reverse direction, the source node E deploys an active MEP. The fault detection process includes but is not limited to Fig.10 Steps b1 to b5 shown in the figure correspond one-to-one with steps a1 to a5 described above, and are not described again here.

[0162] See also Fig. 9 , showing a schematic diagram of the structure of a multi-homing network. The transmission network includes a path 1 and a path 2, the path 1 includes a first node, an intermediate device 1 and a second node 1, the number of the intermediate devices 1 can be one or more, and the path 2 includes a first node, an intermediate device 2 and a second node 2, the number of the intermediate devices 2 can also be one or more. Fig.12 Shown based on Fig. 9 The fault detection process diagram in the multi-homing networking scenario. The steps on each path can refer to Fig.11 Steps a1 to a5 in the multi-homing scenario are not repeated here. The difference between the fault detection process in the multi-homing scenario and the fault detection process in the single-homing scenario is that the first detection message sent by the first node with the active MEP deployed will be sent to the second node 1 with the sink MEP1 deployed or the second node 2 with the sink MEP2 deployed according to the service forwarding path of the first node's bottom layer. After the determination, the first node sends the first detection message to the determined second node.

[0163] Below, the beneficial effects of the fault detection method of the present application are explained by comparing the relevant technology with the present application.

[0164] Related technology 1 provides an in-situ flow information telemetry (IFIT) method, which inserts a message header for in-situ flow information telemetry into the service message sent by the received user equipment to detect the feature mark of the message. The message with the feature mark can be used to detect the performance indicators such as delay, packet loss, and jitter of the transmission network along with the transmission of the service message. Related technology 1 also uses network telemetry technology to upload the detected data in real time, and presents the detection results through the visual interface of the management and control system.

[0165] Although the related technology 1 can realize fault detection, there are still technical problems that are difficult to solve during the implementation process. Below, the technical problems of the related technology 1 and the methods of solving each technical problem in this application are described respectively.

[0166] Technical Problem 1: Each detection of Related Technology 1 needs to be implemented based on the service message sent by the user equipment. Therefore, if the service message sent by the user equipment is not continuous, for example, the user equipment does not send a service message for a long period of time, Related Technology 1 cannot detect the fault of the transmission network during this period of time, that is, it cannot detect the abnormalities such as delay, packet loss or jitter of the transmission network in time. In addition, since the detection based on the service message is not coherent, Related Technology 1 cannot detect the connectivity of the transmission network.

[0167] After receiving the first user message for the first time, the present application learns the characteristics of the first user message, obtains the first path information and generates the first detection message template, and then can continuously generate multiple detection messages according to the first detection message template, and can continuously send the first detection message during the time period when the first user device does not send the first user message, so as to solve the situation where the user devices at both ends of the transmission network have no messages to send to the transmission network, and the transmission network can actively and quickly detect the fault in time according to the unidirectional and bidirectional SLA information or indicators of the service path. And the fault detection of the present application has coherence, and can realize the connectivity detection of the transmission network.

[0168] Technical Problem 2: Related Technology 1 requires that the equipment in the transmission network periodically upload the detection data to the management and control system. The management and control system perceives the SLA information of the transmission network and combines the detection data to determine whether there is a fault in the transmission network. This method is difficult to ensure the real-time perception of faults.

[0169] In the present application, the first detection message itself carries the first SLA information, and there is no need to perceive the SLA information of the transmission network through the management and control system, so that the second node can immediately determine whether there is a fault in the transmission network after receiving the first detection message, thereby ensuring the real-time perception of the fault.

[0170] Technical Problem Three: Related Technology 1 cannot allow the upstream user equipment and downstream user equipment of the transmission network to perceive the fault conditions of the transmission network, resulting in the upstream user equipment and downstream user equipment being unable to adjust the sending of service messages according to the fault conditions.

[0171] In the present application, if the detection result indicates that there is a fault in the transmission network or between the user equipment and the transmission network, the fault information can be sent to the upstream user equipment and downstream user equipment of the transmission network, so that the upstream user equipment and the downstream user equipment can perceive the fault in time and respond quickly according to the fault situation to avoid long-term damage to user services.

[0172] Technical issue 4: In dual-homing or multi-homing scenarios, related technology 1 cannot collaboratively process the SLA information of different instances. For user devices at both ends, the SLA indicators of the transmission network cannot be truly reflected. Therefore, related technology 1 can only detect single-homing scenarios, which means that the application scenarios of related technology 1 are limited.

[0173] In the dual-homing or multi-homing scenario, the present application establishes a protocol channel between multiple second nodes, and multiple second nodes can communicate SLA information through the protocol channel to achieve collaborative processing or collaborative management, making the fault detection method provided by the present application more scenario-universal. Regardless of whether the user message flows into the transmission network from one or more nodes, or flows out of the transmission network from one or more nodes, the corresponding transmission network SLA indicators can be calculated to determine the fault.

[0174] Related technology 2 provides a performance measurement technology for IP links based on a two-way active measurement protocol (TWAMP), which can perform bidirectional performance statistics in both the forward and reverse directions. TWAMP uses user datagram protocol (UDP) data packets as measurement probe frames to count the bidirectional delay and jitter of the transmission network. In addition, the protocol is secure and can ensure the separation of control and measurement functions. Through the cooperation between network devices that have deployed TWAMP, IP performance statistics between devices can be effectively obtained.

[0175] There are also unresolved technical problems in the implementation of related technology 2. For example, related technology 2 cannot perform detection based on service messages sent by user equipment, which may result in the transmission path of the protocol message used for detection in the transmission network being inconsistent with the path of the message sent by the user equipment in the transmission network, thereby making it impossible to ensure the accuracy of fault perception.

[0176] The present application adds the first path information in the first detection message, so that the first detection message can be transmitted in the transmission network along the same transmission path as the first user message, thereby ensuring the accuracy of fault perception.

[0177] In summary, the present application can ensure that the first detection message and the first user message are transmitted along the same path, and detect faults on the transmission path in a timely manner. In addition, for silent failures of internal equipment in the transmission network, which results in the inability to switch within the transmission network, and thus leads to degradation of the SLA indicators of the transmission network, the fault detection method provided by the present application can be used to link the forced switching of the lower layer (such as the tunnel layer) protection based on the service layer detection, thereby preventing the user equipment at both ends from perceiving the failure of the transmission network.

[0178] The above describes the fault detection method provided by the embodiment of the present application. Corresponding to the above method, the embodiment of the present application also provides a fault detection device. The device is applied to the first node. The device is used to Fig.13 The modules shown above perform the Figure 2 The fault detection method performed by the first node in Fig.13 As shown, the fault detection device provided in the embodiment of the present application includes the following modules.

[0179] A first processing module 1301 is configured to generate a first detection message based on first path information, where the first path information is determined based on a first user message received by the first node, the first detection message includes the first path information and first service level agreement SLA information, and the first path information is used to indicate a transmission path of the first user message and the first detection message;

[0180] The first transceiver module 1302 is used to send a first detection message to a second node, where the second node is a node on the transmission path. The first SLA information included in the first detection message is used by the second node to determine whether there is a fault between the first node and the second node.

[0181] In a possible implementation, the first detection message also includes first indication information, first device side status information and first network side status information, the first indication information is used to indicate the fault direction corresponding to the first device side status information and the first network side status information, the first device side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends a first user message to the first node, the first network side status information indicates whether there is a fault between the first node and the second node, and the first network side status information is perceived by the first node.

[0182] In a possible implementation, the first detection message further includes a detection type identifier, where the detection type identifier is used to indicate a detection type of the first detection message, and the detection type includes one of connectivity detection, packet loss rate detection, delay detection, and jitter detection.

[0183] In one possible implementation, when the detection type is connectivity detection, the first SLA information includes a detection period, which indicates the time interval between two consecutive sending of first detection messages; or, when the detection type is packet loss rate detection, the first SLA information includes the number of first detection messages sent by the first node within a first time period; or, when the detection type is delay detection or jitter detection, the first SLA information includes a first timestamp when the first node sends the first detection message.

[0184] In a possible implementation manner, the first SLA information is located in a first payload field in a first detection message, and the first detection message further includes length information, where the length information indicates the length of the first payload field.

[0185] In a possible implementation manner, the first detection message further includes a detection identifier, and the detection identifier is used to indicate that the type of the first detection message is a detection message.

[0186] In one possible implementation, the first transceiver module 1302 is also used to receive a second detection message sent by the second node based on the first detection message, the second detection message includes second network side status information, the second network side status information indicates whether there is a fault between the first node and the second node, and the second network side status information is determined by the second node based on the first SLA information.

[0187] In a possible implementation, the second detection message also includes second indication information and first device side status information, and the second indication information is used to indicate a fault direction corresponding to the first device side status information and the second network side status information.

[0188] In a possible implementation manner, when the second network-side status information indicates that a fault exists between the first node and the second node, the second network-side status information is further used to indicate the type of fault.

[0189] In one possible implementation, the first transceiver module 1302 is also used to send first fault information to the first user equipment when the second detection message satisfies the first condition, and the first condition includes at least one of the first device side status information indicating that there is a fault between the first user equipment and the first node and the second network side status information indicating that there is a fault between the first node and the second node.

[0190] In one possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type.

[0191] In a possible implementation, the first processing module 1301 is further configured to generate a first detection message template based on the first path information, where the first detection message template includes the first path information and is used to generate a first detection message.

[0192] In a possible implementation, an active maintenance endpoint MEP is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range.

[0193] The present application also provides a fault detection device, wherein the device is applied to the second node. Fig.14 The modules shown above perform the Figure 2 The fault detection method performed by the second node in Fig.14 As shown, the fault detection device provided in the embodiment of the present application includes the following modules.

[0194] The second transceiver module 1401 is used to receive a first detection message sent by the first node, where the first detection message includes first path information and first service level agreement SLA information, where the first path information is determined based on a first user message received by the first node, and the first path information is used to indicate a transmission path of the first detection message;

[0195] The second processing module 1402 is used to determine second network side status information based on the first SLA information, where the second network side status information indicates whether there is a fault between the first node and the second node;

[0196] The second processing module 1402 is further configured to generate a second detection message according to the second network side state information, where the second detection message includes the second network side state information;

[0197] The second transceiver module 1401 is further configured to send a second detection message to the first node.

[0198] In a possible implementation, the first detection message also includes first indication information, first device side status information and first network side status information, the first indication information is used to indicate the fault direction corresponding to the first device side status information and the first network side status information, the first device side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends a first user message to the first node, the first network side status information indicates whether there is a fault between the first node and the second node, and the first network side status information is perceived by the first node.

[0199] In a possible implementation, the second detection message also includes first device side status information and second indication information, and the second indication information is used to indicate the fault direction corresponding to the first device side status information and the second network side status information; when the second network side status information indicates that there is a fault between the first node and the second node, the second network side status information is also used to indicate the fault type.

[0200] In one possible implementation, the second transceiver module 1401 is also used to send first fault information to the second user device when the second detection message satisfies the first condition, the first condition including at least one of the first device side status information indicating that there is a fault between the first user device and the first node and the second network side status information indicating that there is a fault between the first node and the second node, and the second user device is a device that interacts the first user message with the first user device.

[0201] In one possible implementation, the first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type.

[0202] In one possible implementation, there are multiple second nodes, and a protocol channel is established between every two of the multiple second nodes. The protocol channel is used for the multiple second nodes to send first SLA information to each other, and the second network side status information is determined by at least one second node among the multiple second nodes.

[0203] In a possible implementation, an active maintenance endpoint MEP is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate the detection range of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range.

[0204] It should be understood that the above Fig.13 and Fig.14 The device provided has the following beneficial effects when achieving its function: Figure 2The provided fault detection method has the same beneficial effects, which will not be described here. Fig.13 and Fig.14 When the device provided realizes its functions, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0205] See also Fig.15 , Fig.15 A schematic structural diagram of an exemplary fault detection device 1500 of the present application is shown. The fault detection device 1500 includes at least one processor 1501 , a memory 1503 , and at least one network interface 1504 .

[0206] Processor 1501 is, for example, a general-purpose central processing unit (CPU), a digital signal processor (DSP), a network processor (NP), a GPU, a neural-network processing unit (NPU), a data processing unit (DPU), a microprocessor or one or more integrated circuits or application-specific integrated circuits (ASICs) for implementing the solution of the present application, a programmable logic device (PLD), other general-purpose processors or other programmable logic devices, discrete gates, transistor logic devices, discrete hardware components or any combination thereof. PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting an advanced RISC machines (ARM) architecture. It may implement or execute various logic blocks, modules and circuits described in conjunction with the disclosure of the present application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

[0207] Optionally, the fault detection device 1500 further includes a bus 1502. The bus 1502 is used to transmit information between the components of the fault detection device 1500. The bus 1502 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus 1502 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 The fact that only one line is used in the diagram does not mean that there is only one bus or only one type of bus.

[0208] The memory 1503 is, for example, a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache.

[0209] By way of example but not limitation, many forms of ROM and RAM are available. For example, ROM is a compact disc read-only memory (CD-ROM). RAM includes, but is not limited to, static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

[0210] The memory 1503 may also be other types of storage devices that can store static information and instructions. Or it may be other types of dynamic storage devices that can store information and instructions. Or it may be other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, blue-ray disk, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by the computer, but is not limited to this. The memory 1503, for example, exists independently and is connected to the processor 1501 through the bus 1502. The memory 1503 may also be integrated with the processor 1501.

[0211] The network interface 1504 uses any transceiver-like device to communicate with other devices or communication networks, and the communication network can be Ethernet, radio access network (RAN) or wireless local area network (WLAN), etc. The network interface 1504 may include a wired network interface and may also include a wireless network interface. Specifically, the network interface 1504 may be an Ethernet interface, such as a fast Ethernet (FE) interface, a gigabit Ethernet (GE) interface, an asynchronous transfer mode (ATM) interface, a WLAN interface, a cellular network interface or a combination thereof. The Ethernet interface may be an optical interface, an electrical interface or a combination thereof. In some embodiments of the present application, the network interface 1504 may be used for the fault detection device 1500 to communicate with other devices.

[0212] In a specific implementation, as some embodiments, the processor 1501 may include one or more CPUs, such as Fig.15 0 and CPU1 shown in FIG. Each of these processors may be a single-core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0213] In a specific implementation, as some embodiments, the fault detection device 1500 may include multiple processors, such as Fig.15 1 and 1505. Each of these processors may be a single-core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0214] In some implementations, the memory 1503 is used to store program instructions 1510 for executing the solution of the present application, and the processor 1501 can execute the program instructions 1510 stored in the memory 1503. That is, the fault detection device 1500 can implement the method provided in the method embodiment through the processor 1501 and the program instructions 1510 in the memory 1503, that is, Figure 2 The program instruction 1510 may include one or more software modules. Optionally, the processor 1501 itself may also store program instructions for executing the solution of the present application.

[0215] In a specific implementation process, the fault detection device 1500 of the present application may correspond to the first node and the second node for executing the above method. The processor 1501 in the fault detection device 1500 reads the instruction in the memory 1503, so that Fig.15 The fault detection device 1500 shown can execute all or part of the steps in the method embodiment.

[0216] The fault detection device 1500 may also correspond to the above Fig.13 or Fig.14 The device shown, Fig.13 or Fig.14 Each functional module in the apparatus shown is implemented using software of the fault detection device 1500. In other words, Fig.13 or Fig.14 The functional modules included in the apparatus shown are generated after the processor 1501 of the fault detection device 1500 reads the program instructions 1510 stored in the memory 1503 .

[0217] in, Figure 2 Each step of the method shown is completed by an integrated logic circuit of hardware or software instructions in the processor of the fault detection device 1500. The steps of the method embodiment disclosed in the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method embodiment in combination with its hardware. To avoid repetition, it is not described in detail here.

[0218] See also Fig.16 , Fig.16 The schematic diagram of the structure of an exemplary fault detection device 1600 of the present application is shown. The fault detection device 1600 includes: a main control board 1610 and an interface board 1630 . Fig.16 The fault detection device 1600 shown is used to perform the above Figure 2 The operations involved in the fault detection method shown. The fault detection device 1600 is, for example, a switch, a router, a controller, etc. The fault detection device 1600 may be an example of the fault detection device 1500.

[0219] The main control board 1610 is also called a main processing unit (MPU) or a route processor card. The main control board 1610 is used to control and manage various components in the fault detection device 1600, including route calculation, device management, device maintenance, and protocol processing functions. The main control board 1610 includes: a central processing unit 1611 and a memory 1612.

[0220] The interface board 1630 is also called a line processing unit (LPU), a line card or a service board. The interface board 1630 is used to provide various service interfaces and implement data packet forwarding. Service interfaces include but are not limited to Ethernet interfaces, POS (Packet over SONET / SDH) interfaces, etc., and Ethernet interfaces are, for example, flexible Ethernet clients (FlexE Clients). The interface board 1630 includes: a central processor 1631, a network processor 1632, a forwarding table entry memory 1634 and a physical interface card (PIC) 1633.

[0221] The central processor 1631 on the interface board 1630 is used to control and manage the interface board 1630 and communicate with the central processor 1611 on the main control board 1610 .

[0222] The network processor 1632 is used to implement the forwarding processing of the message. The network processor 1632 can be in the form of a forwarding chip. Specifically, the network processor 1632 is used to forward the received message based on the forwarding table stored in the forwarding table entry memory 1634. If the destination address of the message is the address of the fault detection device 1600, the message is sent to the CPU (such as the central processor 1611) for processing; if the destination address of the message is not the address of the fault detection device 1600, the next hop and the output interface corresponding to the destination address are found from the forwarding table according to the destination address, and the message is forwarded to the output interface corresponding to the destination address. Among them, the processing of the uplink message includes: processing of the message input interface, forwarding table search; processing of the downlink message: forwarding table search, etc.

[0223] The physical interface card 1633 is used to implement the connection function of the physical layer, and the original traffic enters the interface board 1630 from it, and the processed message is sent from the physical interface card 1633. The physical interface card 1633 is also called a daughter card, which can be installed on the interface board 1630 and is responsible for converting the optical signal into a message and forwarding the message to the network processor 1632 for processing after checking the legitimacy of the message. In some embodiments, the central processor can also perform the functions of the network processor 1632, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1632 is not required in the physical interface card 1633.

[0224] Optionally, the fault detection device 1600 includes a plurality of interface boards. For example, the fault detection device 1600 further includes an interface board 1640 . The interface board 1640 includes a central processor 1641 , a network processor 1642 , a forwarding table entry memory 1644 , and a physical interface card 1643 .

[0225] Optionally, the fault detection device 1600 further includes a switching fabric board 1620. The switching fabric board 1620 may also be referred to as a switch fabric unit (SFU). In the case where the fault detection device has multiple interface boards 1630, the switching fabric board 1620 is used to complete data exchange between the interface boards. For example, the interface board 1630 and the interface board 1640 may communicate through the switching fabric board 1620.

[0226] The main control board 1610 is coupled to the interface board 1630. For example, the main control board 1610, the interface board 1630, the interface board 1640, and the switching network board 1620 are connected to the system backplane through a system bus to achieve intercommunication. In a possible implementation, an inter-process communication (IPC) channel is established between the main control board 1610 and the interface board 1630, and the main control board 1610 and the interface board 1630 communicate through the IPC channel.

[0227] Logically, the fault detection device 1600 includes a control plane and a forwarding plane. The control plane includes a main control board 1610 and a central processing unit 1631. The forwarding plane includes various components for performing forwarding, such as a forwarding table entry memory 1634, a physical interface card 1633, and a network processor 1632. The control plane performs functions such as a router, generating a forwarding table, processing signaling and protocol messages, and configuring and maintaining the status of the device. The control plane sends the generated forwarding table to the forwarding plane. On the forwarding plane, the network processor 1632 forwards the message received by the physical interface card 1633 based on the forwarding table sent by the control plane. The forwarding table sent by the control plane can be stored in the forwarding table entry memory 1634. In some embodiments, the control plane and the forwarding plane can be completely separated and not on the same device.

[0228] It is worth noting that there may be one or more main control boards, and when there are multiple boards, they may include a primary main control board and a backup main control board. There may be one or more interface boards. The stronger the data processing capability of the fault detection device, the more interface boards are provided. There may also be one or more physical interface cards on the interface board. There may be no switching network board, or there may be one or more switching network boards. When there are multiple switching network boards, they can jointly realize load sharing and redundant backup. In a centralized forwarding architecture, the fault detection device may not need a switching network board, and the interface board is responsible for the processing function of the service data of the entire system. In a distributed forwarding architecture, the fault detection device may have at least one switching network board, and the switching network board is used to realize data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the fault detection device with a distributed architecture are greater than those of the device with a centralized architecture. Optionally, the fault detection device may also be in the form of only one board, that is, without a switching network board, and the functions of the interface board and the main control board are integrated on the board. In this case, the central processor on the interface board and the central processor on the main control board can be combined into one central processor on the board to perform the functions of the two superimposed. The data exchange and processing capabilities of this type of device are relatively low (for example, low-end switches or communication devices such as routers). The specific architecture to be adopted depends on the specific networking deployment scenario, and no limitation is made here.

[0229] In an exemplary embodiment, a fault detection system is provided, the system comprising a first node and a second node, the first node being configured to execute Figure 2 The method executed by the first node in the second node is used to execute Figure 2 The method executed by the second node in .

[0230] In an exemplary embodiment, a computer program (product) is provided, the computer program (product) comprising: a computer program code, when the computer program code is executed by a computer, the computer executes Figure 2 The method shown.

[0231] In an exemplary embodiment, a computer-readable storage medium is provided, the computer-readable storage medium storing a program or instruction, when the program or instruction is executed on a computer, the computer executes the above Figure 2 The method shown.

[0232] In an exemplary embodiment, a chip is provided, including a processor for calling and executing instructions stored in a memory, so that a computer equipped with the chip executes Figure 2 The method shown.

[0233] In an exemplary embodiment, another chip is provided, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected through an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the computer equipped with the chip executes Figure 2 The method shown.

[0234] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in this application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk), etc.

[0235] In this application, the terms "first", "second", etc. are used to distinguish between identical or similar items with substantially the same effects and functions. It should be understood that there is no logical or temporal dependency between "first", "second", and "nth", nor is there a limitation on the quantity and execution order. It should also be understood that although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another element.

[0236] It should also be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0237] The term "at least one" in this application means one or more, and the term "multiple" in this application means two or more, for example, multiple second devices means two or more second devices. The terms "system" and "network" are often used interchangeably herein.

[0238] It should be understood that the terms used in the description of the various examples herein are only for describing specific examples and are not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0239] It should also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The term "and / or" is a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0240] It should also be understood that the terms "if" and "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" may be interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]" or "in response to detecting [a stated condition or event]," depending on the context.

[0241] The above description is only an embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A fault detection method, characterized in that: The method is applied to a first node, and the method comprises: generating a first detection message based on first path information, where the first path information is determined based on a first user message received by the first node, where the first detection message includes the first path information and first service level agreement SLA information, where the first path information is used to indicate a transmission path of the first user message and the first detection message; The first detection message is sent to a second node, where the second node is a node on the transmission path, and the first SLA information included in the first detection message is used by the second node to determine whether there is a fault between the first node and the second node.

2. The method according to claim 1, characterized in that: The first detection message also includes first indication information, first device-side status information and first network-side status information, the first indication information is used to indicate the fault direction corresponding to the first device-side status information and the first network-side status information, the first device-side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends the first user message to the first node, the first network-side status information indicates whether there is a fault between the first node and the second node, and the first network-side status information is perceived by the first node.

3. The method according to claim 1 or 2, characterized in that: The first detection message also includes a detection type identifier, where the detection type identifier is used to indicate a detection type of the first detection message, and the detection type includes one of connectivity detection, packet loss rate detection, delay detection, and jitter detection.

4. The method according to claim 3, characterized in that When the detection type is the connectivity detection, the first SLA information includes a detection period, and the detection period indicates the time interval between two consecutive sending of the first detection messages; or, when the detection type is the packet loss rate detection, the first SLA information includes the number of the first detection messages sent by the first node within a first time period; or, when the detection type is the delay detection or the jitter detection, the first SLA information includes a first timestamp when the first node sends the first detection message.

5. The method according to any one of claims 1 to 4, characterized in that: The first SLA information is located in a first load field in the first detection message. The first detection message also includes length information, and the length information indicates the length of the first load field.

6. The method according to any one of claims 1 to 5, characterized in that: The first detection message further includes a detection identifier, and the detection identifier is used to indicate that the type of the first detection message is a detection message.

7. The method according to any one of claims 1 to 6, characterized in that: After sending the first detection message to the second node, the method further includes: Receive a second detection message sent by the second node based on the first detection message, the second detection message includes second network side status information, the second network side status information indicates whether there is a fault between the first node and the second node, and the second network side status information is determined by the second node based on the first SLA information.

8. The method according to claim 7, characterized in that The second detection message also includes second indication information and first device-side status information, where the second indication information is used to indicate a fault direction corresponding to the first device-side status information and the second network-side status information.

9. The method according to claim 7 or 8, characterized in that: In a case where the second network-side status information indicates that a fault exists between the first node and the second node, the second network-side status information is further used to indicate a fault type.

10. The method according to any one of claims 7 to 9, characterized in that: After the receiving the second detection message sent by the second node based on the first detection message, the method further includes: When the second detection message satisfies the first condition, first fault information is sent to the first user equipment, and the first condition includes at least one of first device-side status information indicating that a fault exists between the first user equipment and the first node and second network-side status information indicating that a fault exists between the first node and the second node.

11. The method according to claim 10, characterized in that The first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type.

12. The method according to any one of claims 1 to 11, characterized in that: Before generating the first detection message based on the first path information, the method further includes: A first detection message template is generated based on the first path information, where the first detection message template includes the first path information, and the first detection message template is used to generate the first detection message.

13. The method according to any one of claims 1 to 12, characterized in that: An active maintenance endpoint MEP is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate detection ranges of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range.

14. A fault detection method, characterized in that: The method is applied to the second node, and the method includes: receiving a first detection message sent by a first node, where the first detection message includes first path information and first service level agreement SLA information, where the first path information is determined based on a first user message received by the first node, and the first path information is used to indicate a transmission path of the first detection message; Determine, based on the first SLA information, second network side status information, where the second network side status information indicates whether there is a fault between the first node and the second node; Generate a second detection message according to the second network side state information, where the second detection message includes the second network side state information; Send the second detection message to the first node.

15. The method according to claim 14, characterized in that The first detection message also includes first indication information, first device-side status information and first network-side status information, the first indication information is used to indicate the fault direction corresponding to the first device-side status information and the first network-side status information, the first device-side status information indicates whether there is a fault between the first user device and the first node, the first user device is a device that sends the first user message to the first node, the first network-side status information indicates whether there is a fault between the first node and the second node, and the first network-side status information is perceived by the first node.

16. The method according to claim 15, characterized in that The second detection message also includes the first device side status information and second indication information, the second indication information is used to indicate the fault direction corresponding to the first device side status information and the second network side status information; when the second network side status information indicates that there is a fault between the first node and the second node, the second network side status information is also used to indicate the fault type.

17. The method according to any one of claims 14 to 16, characterized in that: After the second detection message is generated according to the second network side state information, the method further includes: When the second detection message satisfies the first condition, the first fault information is sent to the second user equipment, the first condition including at least one of the first device side status information indicating that there is a fault between the first user equipment and the first node and the second network side status information indicating that there is a fault between the first node and the second node, and the second user equipment is a device that interacts the first user message with the first user equipment.

18. The method according to claim 17, characterized in that The first fault information includes a fault location, and the fault location includes at least one of between the first node and the first user equipment or between the first node and the second node; when the fault location includes between the first node and the second node, the first fault information also includes a fault type.

19. The method according to any one of claims 14 to 18, characterized in that: There are multiple second nodes, and a protocol channel is established between every two of the multiple second nodes. The protocol channel is used for the multiple second nodes to send the first SLA information to each other, and the second network side status information is determined by at least one second node among the multiple second nodes.

20. The method according to any one of claims 14 to 19, characterized in that: An active maintenance endpoint MEP is deployed on the first node, and a sink MEP is deployed on the second node. The source MEP and the sink MEP indicate detection ranges of the first detection message and the second detection message, and the detection range indicates that the first node and the second node perform fault detection within the detection range.

21. A fault detection device, characterized in that: The device is applied to a first node, and includes: A first transceiver module, configured to perform the reception and / or transmission related operations performed by the first node in the method described in any one of claims 1 to 13; The first processing module is used to perform other operations other than the reception and / or transmission related operations performed by the first node in any one of the methods described in claims 1-13.

22. A fault detection device, characterized in that: The device is applied to a second node, and includes: A second transceiver module, used to perform the reception and / or transmission related operations performed by the second node in any of the methods described in claims 14-20; The second processing module is used to perform other operations besides the receiving and / or sending related operations performed by the second node in any one of the methods described in claims 14-20.

23. A fault detection system, the system comprising a first node and a second node, the first node being used to execute the method executed by the first node in the fault detection method described in any one of claims 1-20, and the second node being used to execute the method executed by the second node in the fault detection method described in any one of claims 1-20.

24. A fault detection device, characterized in that: The device includes a processor coupled to a memory; the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor so that the fault detection device implements the fault detection method described in any one of claims 1-20.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, and the instruction is loaded and executed by the processor to implement the fault detection method as described in any one of claims 1-20.

26. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and the computer program or instructions are executed by a processor to enable a computer to implement the fault detection method according to any one of claims 1 to 20.

Images