WO2022033034A1

WO2022033034A1 - Oam detection method, device, and system

Info

Publication number: WO2022033034A1
Application number: PCT/CN2021/082058
Authority: WO
Inventors: 谢经荣; 辛方; 闫刚; 李振斌
Original assignee: 华为技术有限公司
Priority date: 2020-08-14
Filing date: 2021-03-22
Publication date: 2022-02-17

Abstract

The present application provides an operations, administration and maintenance (OAM) detection method, device, and system. The method comprises: a first network device receives a first packet from a second network device via a tunnel, the first packet comprising a tunnel header, a first Internet Protocol version 6 (IPv6) header, and an OAM packet, the second network device is an ingress device of the tunnel, and the first network device is an egress device of the tunnel; the first network device determines the type of OAM detection according to a destination address (DA) of the first IPv6 header; the first network device performs detection according to the type of the OAM detection. The technical solution provided by the present application causes the processing of an OAM detection packet (for example, the first packet) and the processing of a data packet by devices, other than a tunnel egress device, on a packet transmission path to be consistent.

Description

Method, device and system for OAM detection

This application claims the priority of the Chinese patent application with the application number 202010820465.7 and the invention titled "A method, equipment and system for OAM detection" filed with the State Intellectual Property Office on August 14, 2020, and filed on October 20, 2020 The priority of the Chinese patent application filed with the State Intellectual Property Office on the 16th with the application number of 202011109212.5 and the invention titled "A method, device and system for OAM detection", the entire contents of which are incorporated into this application by reference.

technical field

The present application relates to the field of network communication, and more particularly, to a method for OAM detection, a first network device, a second network device, and a system.

Background technique

In an Internet Protocol (IP) bearer network, operation, administration and maintenance (OAM) detection of IP services is a common technology.

Take OAM detection on a tunnel between two devices as an example. After receiving an OAM detection packet, the egress device of the tunnel needs to perform corresponding processing according to the type of OAM detection. Therefore, the OAM detection packet sent by the ingress device of the tunnel to the egress device of the tunnel needs to instruct the egress device of the tunnel to perform OAM detection, and the specific type of OAM detection, so that the egress device of the tunnel can forward the relevant OAM detection according to the instruction. action.

In a related technical solution, the tunnel header of the OAM detection packet includes OAM detection indication information, where the OAM detection indication information is used to instruct the device to perform OAM detection and a specific type of OAM detection. In some scenarios, through the above technical solutions, there may be a problem that the processing of OAM detection packets and data packets is inconsistent.

SUMMARY OF THE INVENTION

The present application provides an OAM detection method, device, and system, which can make the processing of OAM detection packets consistent with the processing of data packets by each device on the packet transmission path except the tunnel egress device.

In a first aspect, a method for OAM detection is provided, comprising: a first network device receiving a first packet sent by a second network device via a tunnel, where the first packet includes a tunnel header, a first Internet Protocol version 6 IPv6 header and operation management and maintenance OAM message, the second network device is the ingress device of the tunnel, and the first network device is the egress device of the tunnel; the first network device is based on the first The destination address DA of the IPv6 header determines the type of OAM detection; the first network device performs detection according to the type of OAM detection.

In the above technical solution, the destination address of the first IPv6 header instructs the egress device (eg, the first network device) of the tunnel to perform OAM detection. The tunnel header part, the first IPv6 header and the OAM packet part of the first packet are separated by means of "encapsulation". In this way, each device on the packet transmission path except the tunnel egress device only needs to process the tunnel header part of the first packet (also called the OAM detection packet), and does not need to process the first IPv6 header and the first IPv6 header after the tunnel header. OAM packet, so that the processing of the first packet (also referred to as the OAM detection packet) by each device on the packet transmission path except the tunnel egress device is consistent with the processing process of the data packet.

In a possible implementation manner, the first IPv6 header is located between the tunnel header and the OAM packet.

It should be understood that the tunnel header itself may contain an IPv6 header, that is, a tunnel header based on IPv6, but the first IPv6 header described in this document is not an IPv6 header in the tunnel header, but an IPv6 header located between the tunnel header and the OAM packet. head.

In another possible implementation manner, the first packet further includes a User Datagram Protocol UDP header, and the destination port number of the UDP header is used to indicate that the first packet includes the OAM packet, The method further includes: determining, by the first network device, that the first packet includes the OAM packet according to the destination port number in the UDP header.

It should be understood that if the first packet further includes a UDP header, the UDP header and the OAM packet may also be collectively referred to as an OAM packet encapsulated by UDP.

In another possible implementation manner, the Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet, and the method further includes: the first network device according to The value of the Next Header field determines that the first packet includes the OAM packet.

In another possible implementation manner, the first packet further includes a third IPv6 header, and the Next Header field of the third IPv6 header is used to indicate that the first packet includes the OAM packet.

It should be understood that if the first packet further includes a third IPv6 header and a UDP header, the third IPv6 header, the UDP header and the OAM packet may also be collectively referred to as an IP-encapsulated OAM packet.

In another possible implementation manner, the first network device determines that the DA of the first IPv6 header is the unicast IPv6 address of the first network device; the first network device determines according to the first IPv6 The DA of the header and the forwarding information base FIB determine the type of the OAM detection, wherein the FIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

In another possible implementation manner, the first network device determines that the DA of the first IPv6 header is a loopback unicast IPv6 address; the first network device determines according to the DA and the first IPv6 header of the first IPv6 header. The forwarding information base FIB determines the type of the OAM detection, wherein the FIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

In another possible implementation manner, the first network device determines that the DA of the first IPv6 header is a multicast IPv6 address; the first network device determines the DA of the first IPv6 header and multicast forwarding according to the DA of the first IPv6 header The information base MFIB determines the type of the OAM detection, wherein the MFIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

In another possible implementation manner, the first network device decapsulates the first packet to obtain the OAM packet; the first network device determines the second packet according to the OAM packet message; the first network device sends the second message to the second network device.

In another possible implementation manner, the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the second IPv6 header The DA indicates that the second message is an OAM detection response message.

In another possible implementation manner, the DA of the second IPv6 header is the source address SA of the first IPv6 header.

In another possible implementation manner, the type of the OAM detection includes any one of the following: simple bidirectional active measurement protocol STAMP detection, bidirectional active measurement protocol TWAMP detection, bidirectional forwarding detection BFD, seamless bidirectional forwarding detection S-BFD, Internet packet detector PING detection.

In another possible implementation manner, the tunnel includes any one of the following: a multi-protocol label switching MPLS tunnel, an Internet Protocol IP tunnel, a segment routing SRv6 tunnel using Internet Protocol version 6, a bit index-based display Explicitly replicated BIER tunnels, Bit-Indexed Explicitly replicated BIERv6 tunnels for Internet Protocol version 6.

In a second aspect, a method for OAM detection is provided, including: obtaining a first packet by a second network device, where the first packet includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM message, the destination address DA of the first IPv6 header is used to indicate the type of OAM detection;

The second network device sends the first packet to the first network device via the tunnel, the second network device is an ingress device of the tunnel, and the first network device is an egress device of the tunnel.

In another possible implementation manner, the first packet further includes a User Datagram Protocol UDP header, and the destination port number of the UDP header is used to indicate that the first packet includes the OAM packet.

In another possible implementation manner, the Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet.

In another possible implementation manner, the method further includes: receiving, by the second network device, a second packet, where the second packet includes a second IPv6 header, and a destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the DA of the second IPv6 header indicates that the second message is an OAM detection response message; The second packet is processed.

The beneficial effects of the second aspect and any possible implementation manner of the second aspect correspond to the beneficial effects of the first aspect and any possible implementation manner of the first aspect, which will not be repeated here.

In a third aspect, a first network device is provided, where the first network device is an egress device of a tunnel, and the first network device includes:

A receiving module, configured to receive a first message sent by a second network device via the tunnel, where the first message includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM message, so The second network device is an ingress device of the tunnel;

a processing module, configured to determine the type of OAM detection according to the destination address DA of the first IPv6 header;

The processing module is further configured to perform detection according to the type of the OAM detection.

In another possible implementation manner, the first packet further includes a User Datagram Protocol UDP header, and the destination port number of the UDP header is used to indicate that the first packet includes the OAM packet,

The processing module is further configured to: determine that the first packet includes the OAM packet according to the destination port number in the UDP header.

In another possible implementation manner, the Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet,

The processing module is further configured to: determine that the first message includes the OAM message according to the value of the Next Header field.

In another possible implementation manner, the processing module is specifically configured to: determine that the DA of the first IPv6 header is the unicast IPv6 address of the first network device; The forwarding information base FIB determines the type of the OAM detection, wherein the FIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

In another possible implementation manner, the processing module is specifically configured to: determine that the DA of the first IPv6 header is a multicast IPv6 address; determine according to the DA of the first IPv6 header and the multicast forwarding information base MFIB The type of the OAM detection, wherein the MFIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

In another possible implementation manner, the processing module is specifically configured to: decapsulate the first packet to obtain the OAM packet; determine a second packet according to the OAM packet; The second network device sends the second message.

In a fourth aspect, a first network device is provided, and the first network device has a function of implementing the behavior of the first network device in the above method. The functions can be implemented based on hardware, and can also be implemented based on hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In a possible design, the structure of the first network device includes a processor and an interface, and the processor is configured to support the first network device to perform corresponding functions in the above method. The interface is used to support the first network device to receive the first packet.

The first network device may also include a memory for coupling with the processor and storing necessary program instructions and data for the first network device.

In another possible design, the first network device includes: a processor, a transmitter, a receiver, a random access memory, a read only memory, and a bus. Wherein, the processor is respectively coupled to the transmitter, the receiver, the random access memory and the read only memory through the bus. Wherein, when the first network device needs to be run, the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to boot the system to start, and the first network device is guided to enter a normal operation state. After the first network device enters the normal operation state, the application program and the operating system are run in the random access memory, so that the processor executes the method in the first aspect or any possible implementation manner of the first aspect.

In a fifth aspect, a first network device is provided, the first network device includes: a main control board and an interface board, and may further include a switching network board. The first network device is configured to execute the method in the first aspect or any possible implementation manner of the first aspect. Specifically, the first network device includes a module for executing the third aspect or the method in any possible implementation manner of the third aspect.

In a sixth aspect, a first network device is provided, where the first network device includes a control module and a first forwarding sub-device. The first forwarding sub-device includes: an interface board, and further, may also include a switching network board. The first forwarding sub-device is configured to perform the function of the interface board in the fifth aspect, and further, may also perform the function of the switching network board in the fifth aspect. The control module includes a receiver, a processor, a transmitter, a random access memory, a read-only memory and a bus. Wherein, the processor is respectively coupled to the receiver, the transmitter, the random access memory and the read only memory through the bus. Wherein, when the control module needs to be run, the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to boot the system to start, and the control module is guided to enter a normal operation state. After the control module enters the normal operation state, the application program and the operating system are run in the random access memory, so that the processor performs the function of the main control board in the fifth aspect.

It can be understood that, in practical applications, the first network device may include any number of interfaces, processors or memories.

In a seventh aspect, a second network device is provided, where the second network device is an ingress device of a tunnel, and the second network device includes:

The processing module is configured to obtain a first message, where the first message includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM message, and the destination address DA of the first IPv6 header is to indicate the type of OAM detection;

A sending module, configured to send the first packet to a first network device via the tunnel, where the first network device is an egress device of the tunnel.

In another possible implementation manner, the second network device further includes:

A receiving module, configured to receive a second packet, where the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the second IPv6 header The DA indicates that the second message is an OAM detection response message;

The processing module is further configured to process the second packet according to the DA of the second IPv6 header.

In an eighth aspect, a second network device is provided, and the second network device has a function of implementing the behavior of the second network device in the above method. The functions can be implemented based on hardware, and can also be implemented based on hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In a possible design, the structure of the second network device includes a processor and an interface, and the processor is configured to support the second network device to perform the corresponding functions in the above method. The interface is used to support the second network device to obtain the first packet.

The second network device may also include a memory for coupling with the processor that stores necessary program instructions and data for the second network device.

In another possible design, the second network device includes: a processor, a transmitter, a receiver, a random access memory, a read only memory, and a bus. Wherein, the processor is respectively coupled to the transmitter, the receiver, the random access memory and the read only memory through the bus. Wherein, when the second network device needs to be operated, the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to boot the system to start, and the second network device is guided to enter a normal operation state. After the second network device enters the normal operating state, the application program and the operating system are run in the random access memory, so that the processor executes the method of the second aspect or any possible implementation manner of the second aspect.

In a ninth aspect, a second network device is provided, where the second network device includes: a main control board and an interface board, and further, may also include a switching network board. The second network device is configured to perform the method in the second aspect or any possible implementation manner of the second aspect. Specifically, the second network device includes a module for performing the method in the seventh aspect or any possible implementation manner of the seventh aspect.

A tenth aspect provides a second network device, where the second network device includes a control module and a first forwarding sub-device. The first forwarding sub-device includes: an interface board, and further, may also include a switching network board. The first forwarding sub-device is configured to perform the function of the interface board in the ninth aspect, and further, can also perform the function of the switching network board in the ninth aspect. The control module includes a receiver, a processor, a transmitter, a random access memory, a read-only memory and a bus. Wherein, the processor is respectively coupled to the receiver, the transmitter, the random access memory and the read only memory through the bus. Wherein, when the control module needs to be run, the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to boot the system to start, and the control module is guided to enter a normal operation state. After the control module enters the normal operation state, the application program and the operating system are run in the random access memory, so that the processor performs the function of the main control board in the ninth aspect.

It can be understood that, in practical applications, the second network device may include any number of interfaces, processors or memories.

In an eleventh aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run on a computer, the computer can execute the first aspect or any one of the first aspects. method of execution.

A twelfth aspect provides a computer program product, the computer program product comprising: computer program code, when the computer program code is run on a computer, the computer program code enables the computer to execute the second aspect or any one of the possibilities of the second aspect method of execution.

In a thirteenth aspect, a computer-readable medium is provided, and the computer-readable medium stores program codes, which, when the computer program codes are run on a computer, cause the computer to execute the first aspect or any one of the first aspects. possible methods. These computer-readable storages include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (erasable PROM, EPROM), Flash memory, electrical EPROM (electrically EPROM, EEPROM) and hard drive (hard drive).

In a fourteenth aspect, a computer-readable medium is provided, the computer-readable medium stores program codes, and when the computer program codes are executed on a computer, causes the computer to execute any one of the second aspect or the second aspect above possible methods. These computer-readable storages include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (erasable PROM, EPROM), Flash memory, electrical EPROM (electrically EPROM, EEPROM) and hard drive (hard drive).

A fifteenth aspect provides a chip, the chip includes a processor and a data interface, wherein the processor reads an instruction stored in a memory through the data interface to execute the first aspect or any possible implementation of the first aspect method in method. In the specific implementation process, the chip can be a central processing unit (CPU), a microcontroller (MCU), a microprocessor (microprocessing unit, MPU), a digital signal processor (digital signal processor) processing, DSP), system on chip (system on chip, SoC), application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or programmable logic device (programmable logic device) , PLD).

A sixteenth aspect provides a chip, which includes a processor and a data interface, wherein the processor reads an instruction stored in a memory through the data interface to execute the second aspect or any possible implementation of the second aspect method in method. In the specific implementation process, the chip can be a central processing unit (CPU), a microcontroller (MCU), a microprocessor (microprocessing unit, MPU), a digital signal processor (digital signal processor) processing, DSP), system on chip (system on chip, SoC), application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or programmable logic device (programmable logic device) , PLD).

In a seventeenth aspect, a system for OAM detection is provided, and the system includes the above-mentioned first network device and second network device.

Description of drawings

FIG. 1 is a schematic diagram of an application scenario applicable to the embodiment of the present application.

FIG. 2 is a schematic diagram of a possible scenario provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of another possible scenario provided by an embodiment of the present application.

FIG. 4 is a schematic flowchart of an OAM detection method provided by an embodiment of the present application.

FIG. 5 is a schematic flowchart of another OAM detection method provided by an embodiment of the present application.

FIG. 6 is a schematic diagram of a scenario of STAMP detection provided by an embodiment of the present application.

FIG. 7 is a schematic diagram of another possible scenario provided by an embodiment of the present application.

FIG. 8 is a schematic diagram of another possible scenario provided by an embodiment of the present application.

FIG. 9 is a schematic diagram of another possible scenario provided by an embodiment of the present application.

FIG. 10 is a schematic diagram of another STAMP detection scenario provided by an embodiment of the present application.

FIG. 11 is a schematic diagram of a scenario of S-BFD detection provided by an embodiment of the present application.

FIG. 12 is a schematic diagram of a scenario of Ping detection provided by an embodiment of the present application.

FIG. 13 is a schematic diagram of a scenario of BFD detection provided by an embodiment of the present application.

FIG. 14 is a schematic structural diagram of a first network device 1400 provided by an embodiment of the present application.

FIG. 15 is a schematic diagram of a hardware structure of a first network device 2000 according to an embodiment of the present application.

FIG. 16 is a schematic diagram of a hardware structure of another first network device 2100 according to an embodiment of the present application.

FIG. 17 is a schematic structural diagram of a second network device 1700 provided by an embodiment of the present application.

FIG. 18 is a schematic diagram of a hardware structure of a second network device 2200 according to an embodiment of the present application.

FIG. 19 is a schematic diagram of a hardware structure of another second network device 2400 according to an embodiment of the present application.

detailed description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

This application will present various aspects, embodiments or features in the context of a system comprising a plurality of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc., and/or may not include all of the devices, components, modules, etc. discussed in connection with the figures. In addition, combinations of these schemes can also be used.

In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to represent examples, illustrations or illustrations. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.

In the embodiments of the present application, "corresponding (corresponding, relevant)" and "corresponding (corresponding)" may sometimes be used interchangeably. It should be noted that, when the difference is not emphasized, the meanings to be expressed are the same.

The network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. The evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

References in this specification to "one embodiment" or "some embodiments" and the like mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in other embodiments," etc. in various places in this specification are not necessarily All refer to the same embodiment, but mean "one or more but not all embodiments" unless specifically emphasized otherwise. The terms "including", "including", "having" and their variants mean "including but not limited to" unless specifically emphasized otherwise.

In this application, "at least one" means one or more, and "plurality" means two or more. "And/or", which describes the relationship of the associated objects, means that there can be three relationships, for example, A and/or B, which can mean: including the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character "/" generally indicates that the associated objects are an "or" relationship. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one item (a) of a, b, or c may represent: a, b, c, ab, ac, bc, or abc, where a, b, and c may be single or multiple .

In an Internet Protocol (IP) bearer network, operation, administration and maintenance (OAM) detection of IP services is a common technology. It should be understood that the OAM detection refers to that, according to the actual needs of the operator's network operation, the network management work is usually divided into three categories: operation, administration, and maintenance. Operation mainly completes the analysis, prediction, planning and configuration of the daily network and services; maintenance is mainly the daily operation activities such as testing and fault management of the network and its services.

There are various types of OAM detection, which are not specifically limited in this embodiment of the present application. As an example, the OAM detection may be an internet packet groper (Ping). The above OAM detection may be a one-way active measurement, or may also be a two-way active measurement, for example, one-way active measurement protocol (one-way active measurement protocol, OWAMP), two-way active measurement protocol (two-way active measurement protocol, TWAMP) , Simple two-way active measurement protocol (simple two-way active measurement protocol, STAMP). The above OAM detection may also be bidirectional forwarding detection (BFD), or seamless bidirectional forwarding detection (S-BFD).

It should be understood that STAMP may also be referred to as TWAMP Light. S-BFD can also be called simple BFD.

An application scenario applicable to the embodiment of the present application is described below with reference to FIG. 1 .

FIG. 1 is a schematic diagram of an application scenario applicable to the embodiment of the present application. As shown in FIG. 1 , the scenario includes: device A, device B, device R1, device R2, and device R3.

Among them, device A serves as the ingress device of the tunnel, and device B serves as the egress device of the tunnel. Device R1, device R2, and device R3 are devices that forward packets in the tunnel.

It should be understood that the embodiments of the present application do not specifically limit the number of devices that forward packets in the tunnel. For ease of description, device R1, device R2, and device R3 are used as examples for description in FIG. 1 .

Device A can send an OAM detection packet to device B along the tunnel (tunnel between device A and device B), where the OAM detection packet is used to detect the connectivity and performance of the tunnel between device A and device B.

There may be multiple types of tunnels between device A and device B, which are not specifically limited in this application, and several possible tunnel types are introduced below.

As an example, the tunnel is a multi-protocol label switching (MPLS) tunnel, such as an MPLS point-to-point (MPLS P2P) tunnel, or an MPLS point-to-multipoint (MPLS) tunnel. point-to-multipoint, MPLS P2MP) tunnel, or MPLS segment routing (segment routing, SR-MPLS) tunnel.

As another example, the tunnel is an IP tunnel, such as an internet protocol version 6 (IPv6) tunnel, or a segment routing using ipv6 data plane (SRv6) tunnel, or an IPv6 Segment routing using ipv6 data plane traffic engineering (SRv6-TE) tunnels on the data plane.

It should be understood that IP tunnels, IPv6 tunnels, SRv6 tunnels, and SRv6-TE tunnels may generally be point-to-point (P2P) tunnels. For example, P2P tunnels for IP/IPv6/SRv6/SRv6-TE.

As another example, the tunnel may also be a point-to-point (P2MP) tunnel, for example, the P2MP tunnel may be a bit indexed explicit replication (BIER) P2MP tunnel, or P2MP tunnel for BIERv6.

The OAM detection packet sent by device A to device B may include: an OAM packet part and a part before the OAM packet. The part before the OAM packet in this embodiment of the present application may be referred to as a tunnel header, or an outer layer header, or an outer layer tunnel header, and the part of the OAM packet is referred to as an inner layer OAM packet.

The OAM message may be an original OAM message, or may be an OAM message encapsulated by the user datagram protocol (UDP), or may be an OAM message encapsulated by IP, which is not covered by this application. Make specific restrictions. The OAM packet encapsulated by UDP may include: UDP header and original OAM packet, and the OAM packet encapsulated by IP may include IP header, UDP header and original OAM packet.

Optionally, taking the OAM packet encapsulated by IPv6 as an example, the OAM packet may further include: an IPv6 extension header.

The embodiments of the present application specifically limit the IPv6 extension header. For example, the IPv6 extension header may be a destination option header (destination option header, DOH), and for another example, the IPv6 extension header may also be a routing header (routing header, RH).

The format of the tunnel header is determined according to different tunnel types. For example, for an MPLS tunnel, the tunnel header is the MPLS label stack. For another example, for an IP tunnel, the tunnel header is an IP/IPv6 header, or an IP/IPv6 header+UDP header, or an IP/IPv6 header+GRE header. For another example, for an SRv6-TE tunnel, the tunnel header is an IP/IPv6 header + a segment routing header (segment routing header, SRH). For another example, for a BIER tunnel, the tunnel header is a BIER header. For another example, for a BIERv6 tunnel, the tunnel header is a BIERv6 header.

As an example, the OAM detection packet sent by device A to device B can be expressed in any of the following formats:

1. The tunnel type between device A and device B is MPLS P2P tunnel or MPLS P2MP tunnel, and the OAM detection packet includes: {label stack, OAM packet};

2. The tunnel type between device A and device B is an IP/IPv6 tunnel, and the OAM detection packet includes: {outer IP/IPv6 header, OAM packet};

3. The tunnel type between device A and device B is an IP/IPv6 UDP tunnel, and the OAM detection message includes: {outer IP/IPv6 header, outer UDP header, OAM message};

4. The tunnel type between device A and device B is an IP/IPv6 GRE tunnel, and the OAM detection packet includes {outer IP/IPv6 header, outer GRE header, OAM packet};

5. The tunnel type between device A and device B is an SRv6 tunnel, and the OAM detection packet includes {outer IP/IPv6 header, optional RH header, OAM packet};

6. The tunnel type between device A and device B is a BIER tunnel, and the OAM detection packet includes {BIER header, OAM packet};

7. The tunnel type between device A and device B is a BIERv6 tunnel, and the OAM detection packet includes {BIERv6 header, OAM packet}.

After receiving the OAM detection packet, device B needs to perform corresponding processing according to the type of OAM detection. Therefore, the OAM detection packet sent by device A to device B needs to instruct device B to perform OAM detection and a specific type of OAM detection, so that device B can perform related forwarding actions of OAM detection according to the instruction.

In a related technical solution, the tunnel header of the OAM detection packet includes OAM detection indication information, and the OAM detection indication information is used to instruct device B to perform OAM detection and a specific type of OAM detection. In some scenarios, through the above technical solutions, there may be a problem that the processing of OAM detection packets and data packets is inconsistent.

As an example, in an IPv6 network, when OAM detection is performed on an SRv6 tunnel, an additional network function indication needs to be added to the tunnel header of the OAM detection packet. For example, add an endpoint timestamp and SRv6 SID of endpoint timestamp and forward (End.TSF) to the SRH header of the tunnel header of the OAM detection packet as a network function indication to instruct the corresponding device (for example, device B) to perform Relevant forwarding actions detected by OAM.

For example, in the scenario shown in Figure 2, for a data packet, the tunnel header of the data packet sent by device A to device B may not include the SRH header, and only the destination address of device B needs to be filled in the outer IPv6 in the destination address field of the header. In this way, for the data packet, the device B serving as the tunnel exit does not need to process the SRH header in the tunnel header of the data packet.

For the OAM detection packet, the tunnel header of the OAM detection packet sent by device A to device B needs to include an SRH header, and the SRH header contains both the address of device B and the address of an End.TSF of device B. Address (the address of End.TSF is used as a network function indication to instruct device B to perform the relevant forwarding action of OAM detection). For OAM detection packets, device B, which is the tunnel egress, needs to process the SRH header in the tunnel header of the OAM detection packets. If device B cannot process the SRH header, device B cannot determine that the received packet is an OAM detection packet, and therefore cannot perform OAM detection.

For another example, in the scenario shown in Figure 3, for a data packet, the tunnel header of the data packet sent by device A to device B may include an SRH header, and the SRH header includes two SRv6 SIDs, one is The destination address of device B, and the other is the destination address of device R2. When a data packet is forwarded from device A to device R2, device R2 will perform the penultimate segment pop (PSP) process, pop the SRH header in the data packet, and pop the SRH header in the data packet according to the destination address of the outer IPv6 header. For device B, forward the data packet without the SRH header from device R2 to device B. When the data packet reaches device B, the tunnel header does not contain the SRH header. In this way, for the data packet, the device B serving as the tunnel exit does not need to process the SRH header in the tunnel header of the data packet.

For the OAM detection packet, the tunnel header of the OAM detection packet sent by device A to device B needs to include an SRH header, and the SRH header needs to contain three SRv6 SIDs, which are the destination address of device R2 and device B. The destination address, the address of an End.TSF of device B. The PSP processing cannot be performed before the OAM detection packet reaches device B. Therefore, the tunnel header of the OAM detection packet received by device B also contains an SRH header and the SRH header contains three SRv6 SIDs. For OAM detection packets, device B, which is the tunnel egress, needs to process the SRH header in the tunnel header of the OAM detection packets. If device B cannot process the SRH header, device B cannot determine that the received packet is an OAM detection packet, and therefore cannot perform OAM detection.

Therefore, in the above-mentioned related technical solutions, the tunnel header of the OAM detection packet includes OAM detection indication information, so that in some scenarios, OAM detection occurs on each device except the tunnel egress device on the packet transmission path. The problem of inconsistent processing of packets and data packets.

In view of this, the embodiment of the present application provides an OAM detection method, which uses the destination address in the IPv6 header after the tunnel header of the OAM detection packet to instruct the egress device (eg, device B) of the tunnel to perform OAM detection. In this way, each device on the packet transmission path except the tunnel egress device only needs to process the tunnel header part of the OAM detection packet, so that each device on the packet transmission path except the tunnel egress device has no effect on the OAM detection packet. The processing is the same as the processing of data packets.

The following describes in detail an OAM detection method provided by an embodiment of the present application with reference to FIG. 4 .

FIG. 4 is a schematic flowchart of an OAM detection method provided by an embodiment of the present application. As shown in FIG. 4, the method may include steps 410-430, and the steps 410-430 will be described in detail below respectively.

Step 410: The first network device receives, via the tunnel, a first packet sent by the second network device, where the first packet includes a tunnel header, a first IPv6 header, and an OAM packet.

The second network device is the ingress device of the tunnel, corresponding to the device A above. The first network device is the egress device of the tunnel, corresponding to the device B above.

There may be multiple types of tunnels between the second network device and the first network device, which are not limited in this embodiment of the present application. For details, please refer to the description of the tunnel type between the device A and the device B above, which will not be repeated here.

The first packet sent by the second network device to the first network device via the tunnel may be the above OAM detection packet. The first packet may include: a tunnel header, a first IPv6 header, and an OAM packet.

The format of the tunnel header is determined according to different tunnel types. For example, for an MPLS tunnel, the tunnel header is an MPLS label stack. For another example, for an IP tunnel, the tunnel header is an IP/IPv6 header, or an IP/IPv6 header+UDP header, or an IP/IPv6 header+GRE header. For another example, for an SRv6-TE tunnel, the tunnel header is an IP/IPv6 header + a segment routing header (segment routing header, SRH). For another example, for a BIER tunnel, the tunnel header is a BIER header. For another example, for a BIERv6 tunnel, the tunnel header is a BIERv6 header. For details, please refer to the description of the tunnel header above, which will not be repeated here.

In the embodiment of the present application, the first IPv6 header is not the IPv6 header in the tunnel header, but the IPv6 header after the tunnel header. In one example, the first IPv6 header is located between the tunnel header and the OAM packet.

The OAM packet may be an original OAM packet, or may be an OAM packet encapsulated by UDP, or may be an OAM packet encapsulated by IP. Taking the OAM packet as an OAM packet encapsulated by UDP as an example, the first packet further includes a UDP header. Taking the OAM packet as an IP-encapsulated OAM packet as an example, the first packet further includes an IP header. For details, please refer to the description of the OAM packet above, which will not be repeated here.

Step 420: The first network device determines the type of OAM detection according to the destination address DA of the first IPv6 header.

In this embodiment of the present application, different destination addresses DA in the first IPv6 header are used to indicate different types of OAM detection. The first network device may determine the type of OAM detection according to the destination address DA of the first IPv6 header.

An example, if the first network device determines that the DA of the first IPv6 header is the unicast IPv6 address of the first network device, the first network device may, according to the DA of the first IPv6 header and the forwarding information base (FIB) Determines the type of OAM detection. The FIB includes the correspondence between the DA of the first IPv6 header and the type detected by the OAM.

In another example, the first network device determines that the DA of the first IPv6 header is a loopback unicast IPv6 address; the first network device determines the DA according to the first IPv6 header and the forwarding information base FIB. The type of the OAM detection, wherein the FIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

It should be understood that, for example, any address in 0:0:0:0:0:FFFF:7F00:0/104 belongs to the "loopback unicast IPv6 address".

Another example, if the first network device determines that the DA of the first IPv6 header is a multicast IPv6 address, the first network device may determine according to the DA of the first IPv6 header and the multicast forwarding information base (multicast forwarding information base, MFIB) Type of OAM detection. The MFIB includes the correspondence between the DA of the first IPv6 header and the type detected by the OAM.

Optionally, in some embodiments, the first network device may further determine that the first packet includes an OAM packet. In an example, the first network device may first determine that the first packet includes an OAM packet, and then determine the type of OAM detection according to the destination address DA of the first IPv6 header. In another example, the first network device may first determine the type of OAM detection according to the destination address DA of the first IPv6 header, and then perform verification to determine whether the first packet includes an OAM packet. Detection can be performed according to the type of OAM detection.

There are various specific implementation manners for the first network device to determine that the first packet includes the OAM packet, which is not specifically limited in this application.

For example, the first packet includes a UDP header, and the destination port number of the UDP header is used to indicate whether the first packet includes the OAM packet. The first network device may determine the first packet according to the destination port number of the UDP header. Whether the message includes the OAM message. Multiple different types of OAM detection packets can use the same UDP port number, that is, the UDP port number indicates that there is one of these types of OAM detection packets. The specific one is indicated by the destination address DA in the first IPv6 header, and different destination addresses DA are used to indicate different types of OAM detection. This can also reduce the number of UDP ports in the presence of multiple OAM detection types, thereby reducing the attack surface of the system and reducing the risk of being attacked.

For another example, the first IPv6 header of the first packet includes a next header (Next Header) field. The Next Header field can also be called the protocol (protocol, proto) field, and is used to indicate the type of payload behind the IPv6 header. For example, the Next Header field is used to indicate whether the first packet includes the OAM packet, and the first network device may determine whether the OAM packet is included in the first packet according to the value of the Next Header field of the first IPv6 header message.

It should be understood that the same Next Header value can be used for a variety of different types of OAM detection packets, that is, the Next Header port number indicates that there is one of these types of OAM detection packets. The specific one is indicated by the destination address DA in the first IPv6 header, and different destination addresses DA are used to indicate different types of OAM detection.

Step 430: The first network device performs detection according to the type of OAM detection.

After the first network device receives the first packet, as an egress device of the tunnel, it decapsulates the first packet, obtains the OAM packet in the first packet, and determines the OAM packet in the first packet according to the first IPv6 header in step 420. The type of OAM detection indicated by the destination address DA, and the corresponding processing of the OAM detection is performed.

Several possible types of OAM detection indicated by the destination address of the first IPv6 are listed below.

(1) The destination address of the first IPv6 header indicates "TWAMP" processing, the first network device performs TWAMP processing according to the indication information, determines the second packet according to the OAM packet, and sends the second packet to the second network. equipment;

(2) The destination address of the first IPv6 header indicates "STAMP" processing. The first network device performs STAMP processing according to the indication information, determines the second packet according to the OAM packet, and sends the second packet to the second network. equipment;

(3) The destination address of the first IPv6 header indicates "S-BFD" processing, the first network device performs S-BFD processing according to the indication information, determines the second packet according to the OAM packet, and sends the second packet to the second network device;

(4) The destination address of the first IPv6 header indicates "Ping" processing, the first network device performs Ping processing according to the indication information, determines the second packet according to the OAM packet, and sends the second packet to the second network. equipment.

The second packet may include a second IPv6 header, and the destination address DA of the second IPv6 header is the IPv6 address of the second network device.

It should be understood that the second packet may be a packet obtained by processing the OAM packet, for example, adding a timestamp to the OAM packet to obtain the second packet. Alternatively, the second packet may also be a packet obtained by reconstructing the OAM packet. This application does not specifically limit this.

Optionally, in some embodiments, the DA of the second IPv6 header may further indicate that the second packet is an OAM detection response packet. So that after receiving the second packet, the second network device can determine that the second packet is an OAM detection response packet according to the DA of the second IPv6 header, and perform corresponding processing.

Optionally, in some embodiments, the DA of the second IPv6 header is the source address SA of the first IPv6 header.

Optionally, in some embodiments, the DA of the second IPv6 header is the destination address DA of the first IPv6 header.

In the above technical solution, the destination address in the first IPv6 header after the tunnel header of the OAM detection packet (the first packet) instructs the egress device of the tunnel to perform OAM detection. Since the tunnel header of the OAM detection packet does not contain OAM detection indication information, the tunnel header of the OAM detection packet is the same as the tunnel header of the data packet. Each device on the packet transmission path except the tunnel egress device only needs to process the tunnel header part of the OAM detection packet, so that the forwarding of the OAM detection packet and the forwarding of the data packet are processed on each device on the packet transmission path. the same.

The following takes OAM detection as STAMP as an example, and with reference to FIG. 5 , the specific implementation of OAM detection is performed on the ingress device (for example, device A) of the tunnel instructing the egress device (for example, device B) of the tunnel through the destination address of the first IPv6 header. A detailed description.

It should be understood that the example in FIG. 5 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to specific numerical values or specific scenarios exemplified. Those skilled in the art can obviously make various equivalent modifications or changes according to the example of FIG. 5 given below, and such modifications and changes also fall within the scope of the embodiments of the present application.

FIG. 5 is a schematic flowchart of another OAM detection method provided by an embodiment of the present application. As shown in FIG. 5, the method may include steps 510-520, and the steps 510-520 will be described in detail below respectively.

Step 510: An ingress device (eg, device A) of the tunnel sends an OAM detection packet to an egress device (eg, device B) of the tunnel.

The STAMP detection in this embodiment of the present application can be understood as detecting the connectivity and performance of the tunnel between the device A and the device B by popping the loopback mode.

Figure 6 shows the OAM detection packet obtained by device A. Referring to FIG. 6 , the OAM detection packet includes: tunnel header+first IPv6 header+OAM packet encapsulated by IP (IPv6 header+UDP header+OAM packet).

There may be multiple tunnel headers, which are determined according to the tunnel type between device A and device B. This embodiment of the present application does not specifically limit the type of the tunnel between the device A and the device B. For details, please refer to the description of the tunnel and the tunnel header in the foregoing, which will not be repeated here.

In the OAM detection message shown in Figure 6, the source address (source address, SA) A2 of the first IPv6 header is the address of device A, and the destination address (DA) A1 of the first IPv6 header indicates "STAMP detection" . It can also be understood that the address A1 corresponds to the semantics of "OAM packet processing - OAM Pop and Loopback". As an example, an address A1 with this semantics can be identified with End.OPL.

"OAM packet processing - popping a loopback packet" means that device B, as the tunnel egress device, after receiving the OAM detection packet, pops the tunnel header and obtains the first IPv6 header, and performs Check the form and forward. It is equivalent to popping the first IPv6 header, and processing the packet after the first IPv6 header (the result of the processing is to send the packet to device A, which is equivalent to looping back the packet).

As shown in FIG. 6 , in this embodiment of the present application, when device A constructs an OAM packet encapsulated by IP, in order to realize that device B directly looks up and forwards the packet after the first IPv6 header, device A is opposite to the device. The packets after the first IPv6 header sent by B are "forged". A "forged" packet means that the source address A4 of the IPv6 header is the address of device B, and the destination address A3 is the address of device A. In this way, when device B loops back the packets, it is not necessary to reconstruct the source address and destination address of the OAM packet, that is, it does not need to modify the source address and destination address in the IPv6 header of the IP-encapsulated OAM packet. It directly uses the source address and destination address of the "forged" packet to directly look up the "forged" packet and forward it.

Optionally, in some embodiments, device B may also need to modify the content of the OAM packet, and perform table lookup and forwarding on the modified packet. As an example, device B may stamp the content of the OAM packet with a time stamp.

Step 520: The egress device (eg, device B) of the tunnel receives the OAM detection packet, and sends the OAM response packet to the ingress device (eg, device A) of the tunnel.

After receiving the OAM detection packet (for example, device B), the egress device of the tunnel (for example, device B) decapsulates the OAM detection packet, and obtains the part after the tunnel header of the OAM detection packet (including the first IPv6 header and the IP-encapsulated OAM packet). message section). According to the destination address A1 in the first IPv6 header is the local address, the device B looks up the table and obtains that the semantics corresponding to the address A1 is "OAM packet processing - pop-up loopback packet". Device B obtains the IP-encapsulated OAM packet after the first IPv6 header according to the instruction of "OAM packet processing - popup loopback packet", and directly sends the OAM packet to device A.

Specifically, according to DA=A3 in the IPv6 header of the OAM packet encapsulated by IP (destination address A3 is an address of device A), device B looks up the table to obtain the next hop and outgoing interface of destination address A3. And according to the next hop and outgoing interface, the packet is sent along the corresponding outgoing interface, and finally reaches device A.

In the embodiment of the present application, the correspondence between the destination address A1 of the above-mentioned first IPv6 header and the semantics of "OAM packet processing-OAM Pop and Loopback" indicated by this address can be determined by The implementation is configured on B and configured on Device A to use this address. There are various specific implementation manners, and several possible implementation manners are described in detail below.

As an example, a correspondence between a unicast IPv6 address and OAM detection may be configured on device B. For example, it can be configured on device B: Ipv6 address 2001:db1::1234 function oam-pop-loopback. Device A is configured to use the address "IPv6 address 2001:db1::1234" on device B when device B is required to perform STAMP detection and use the corresponding encapsulation.

Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address A1 on device B. "function oam-pop-loopback" means "OAM packet processing - pop-up loopback packet" function.

For another example, a loopback IPv6 address may also be configured on device B, for example, the loopback IPv6 address may be an address located in the 0:0:0:0:0:FFFF:7F00:0/104 address segment. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, this address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is the same as that in device B. The configuration above is similar. For example, the configuration on device B is as follows: Ipv6 address 0:0:0:0:0:FFFF:7F00:1234 function oam-pop-loopback. At the same time, you can also configure STAMP detection on device A to use this address.

It should be understood that the above two addresses are both unicast IPv6 addresses, and the semantics of the addresses and their indication information can be stored in a forwarding information base (FIB), that is, a unicast address and its corresponding indication information. After receiving the OAM detection packet, device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet. If the destination address A1 of the first IPv6 header is a unicast address, device B searches the FIB accordingly, obtains the destination address A1 indicating "OAM packet processing - popup loopback packet", and performs corresponding processing of OAM detection according to the instruction.

As another example, in this embodiment of the present application, a multicast address may also be configured on device B, that is, the address in the FFxx::/8 address segment identifies the above function. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address FF03::1234 function oam-pop-loopback. At the same time, you can also configure STAMP detection on A to use this address.

It should be understood that the above-mentioned address is a multicast IPv6 address, and the semantics of the address and its instruction information can be stored in a multicast forwarding information base (MFIB), that is, a multicast address and its corresponding instruction information. After receiving the OAM detection packet, device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet. If the destination address A1 of the first IPv6 header is a multicast address, device B searches the MFIB accordingly, obtains the destination address A1 indicating "OAM packet processing - popup loopback packet", and performs corresponding processing of OAM detection according to the instruction.

Optionally, in order to prevent network packet attacks, the egress device of the tunnel (for example, device B) may check the OAM detection packet after receiving the OAM detection packet. As an example, the egress device (eg, device B) of the tunnel may check the source address SA in the IPv6 header of the OAM packet to determine whether the SA in the IPv6 header is its own IP address. If device B determines that SA in the IPv6 header is its own IP address (for example, the source address SA=A4 in the IPv6 header of the OAM packet shown in Figure 6, A4 is an address of device B), device B will Corresponding processing of OAM detection, for example, directly sending the OAM packet to device A.

Optionally, in some embodiments, device B may further indicate that the packet received by device A is an OAM response packet, so that device A can perform corresponding processing on the OAM response packet. For example, the destination address DA in the IPv6 header of the response packet may be used to instruct device A to process the OAM response packet.

As an example, when device A sends an OAM detection packet to device B, it may carry the backhaul address in the backhaul address field. It should be understood that the address of the destination address of the OAM response packet used for the backhaul carried in the OAM detection packet is referred to herein as the "return address", and the field carrying the "return address" in the OAM detection packet is referred to as Return address field.

If the message sent by device A to device B is a "forged" message as shown above, the address is carried in the destination address field of the IPv6 header of the forged message. If the packet sent by device A to device B is an ordinary packet, the return address may be carried in the source address field of the IPv6 header.

For example, configure the following address on device A and carry it in the OAM detection packet as the return address: Ipv6 address 2001:db2::1234 function oam-reply-process. Among them, 2001:db2::1234" is the backhaul address, and "oam-reply-process" identifies the semantics corresponding to the backhaul address to process the OAM response message.

Taking the method shown in FIG. 5 as an example, the format of the OAM detection packet constructed in the embodiment of the present application will be described in detail in combination with different scenarios in FIGS. 7 to 9 .

An example, referring to Figure 7, for a data packet, the tunnel header of the data packet sent by device A to device B may not include the SRH header, and only the destination address of device B needs to be filled in the destination address of the outer IPv6 header. in the field. In this way, for the data packet, the device B serving as the tunnel exit does not need to process the SRH header in the tunnel header of the data packet.

For the OAM detection packet, the tunnel header of the OAM detection packet sent by device A to device B may not include the SRH header, and the address of an End.OPL of device B (the address of End.OPL is used as a network function indicator) , to instruct device B to perform the relevant forwarding action of OAM detection) is encapsulated in the first IPv6 header. The OAM detection packet has the same tunnel header as the data packet. Therefore, the processing of the OAM detection packet by each device on the packet transmission path is the same as that of the data packet.

For another example, referring to FIG. 8 , for a data packet, the tunnel header of the data packet sent by device A to device B may include an SRH header. When the data packet is forwarded from device A to device R2, device R2 will perform PSP processing, pop out the SRH header in the data packet, and according to the destination address of the outer IPv6 header is device B, the data that does not contain the SRH header will be removed. The packet is forwarded from device R2 to device B. When the data packet reaches device B, the tunnel header does not contain the SRH header. In this way, for the data packet, the device B serving as the tunnel exit does not need to process the SRH header in the tunnel header of the data packet.

For the OAM detection packet, the OAM detection packet sent by device A to device B also contains an SRH header, which contains two SRv6 SIDs, one is the destination address of device B, and the other is the destination of device R2 address. The address of an End.OPL of device B (the address of End.OPL is used as a network function indication to instruct device B to perform the relevant forwarding action of OAM detection) is encapsulated in the first IPv6 header. Therefore, when the OAM detection packet is sent from the device When A forwards it to device R2, device R2 will perform PSP processing, pop out the SRH header in the OAM detection packet, and according to the destination address of the outer IPv6 header as device B, send the data packet that does not contain the SRH header from device R2 Forward to device B. When the OAM detection packet reaches device B, the tunnel header does not contain the SRH header. The OAM detection packet has the same tunnel header as the data packet. Therefore, the processing of the OAM detection packet by each device on the packet transmission path is the same as that of the data packet.

For another example, see Figure 9, in the P2MP detection, for data packets, the tunnel header of the data packet sent by device A to device B may not include the SRH header, and only the destination address of device B needs to be filled in in the destination address field of the outer IPv6 header. In this way, for the data packet, the device B serving as the tunnel exit does not need to process the SRH header in the tunnel header of the data packet.

For the OAM detection packet, the tunnel header of the OAM detection packet sent by device A to device B may not include the SRH header, and the address of an End.OPL of device B (the address of End.OPL is used as a network function indicator) , to instruct device B to perform the relevant forwarding action of OAM detection) is encapsulated in the first IPv6 header. The destination address in the tunnel header of the OAM detection packet sent by device A is device R1 (as a segment in the entire P2MP path). Device R1 copies the OAM detection packet and sends it to device R2 and device B. The destination addresses in the tunnel header of the copied and sent message are R2 and B respectively, and none of these processes involve the processing of the End.OPL address and the first IPv6 header where it is located. The OAM detection packet has the same tunnel header as the data packet. Therefore, the processing of the OAM detection packet by each device on the packet transmission path is the same as that of the data packet.

The following takes OAM detection as STAMP, and the IPv6 header in the OAM packet encapsulated by IP is the first IPv6 header as an example, and in conjunction with FIG. The specific implementation of OAM detection performed by the exit device (for example, device B) of the device B will be described in detail.

It should be understood that the example in FIG. 10 is only for helping those skilled in the art to understand the embodiments of the present application, rather than limiting the embodiments of the present application to specific numerical values or specific scenarios exemplified. According to the example of FIG. 10 given below, those skilled in the art can obviously make various equivalent modifications or changes, and such modifications and changes also fall within the scope of the embodiments of the present application.

As shown in Figure 10, the OAM detection packet sent by device A to device B includes a tunnel header and an IP-encapsulated OAM packet (IPv6 header+UDP header+OAM packet). The source address A6 of the IPv6 header (also referred to as the first IPv6 header) of the OAM packet encapsulated by IP is the address of device A, the destination address A5 is an address on device B and the address A5 indicates "STAMP detection" ". It can also be understood that address A5 corresponds to the semantics of "STAMP detection".

"STAMP detection" means that device B, as the tunnel egress device, after receiving the OAM detection packet, pops up the tunnel header to obtain the OAM packet encapsulated by IP, and obtains the STAMP bounce packet according to the OAM packet encapsulated by IP. and sent to device A. As an example, the source address and the destination address in the IPv6 header of the IP-encapsulated OAM packet may be modified to obtain the STAMP bounce packet.

It should be understood that the above STAMP bounce message is equivalent to modifying the IPv6 header of the IP-encapsulated OAM message obtained after decapsulation, and finally sending the message to device A, which is equivalent to modifying the message. and loopback.

The process of performing STAMP detection on device B will be described in detail below.

1. Device B is the egress device of the tunnel, and decapsulates the received OAM detection packet shown in Figure 10.

2. Device B obtains the semantics corresponding to the destination address A5 in the IPv6 header.

Device B decapsulates the OAM detection packet, and obtains the part after the tunnel header of the OAM detection packet (the OAM packet encapsulated by IP). According to the destination address A5 of the IPv6 header of the OAM packet encapsulated by IP, it is the local device. Address, look up the table to obtain the semantics corresponding to the address A5 as "STAMP detection". That is, device B can determine that the OAM packet is a STAMP detection packet according to the address A5.

In the OAM detection packet shown in Figure 10, the IPv6 header is followed by a UDP header, and the UDP header is followed by the STAMP detection packet. In this case, the port number in the UDP header identifies an "OAM packet" or "Opaque packet", and the destination address in the IPv6 header identifies the "UDP-STAMP" detection packet.

Optionally, in some embodiments, the STAMP detection packet may be directly followed by the IPv6 header. At this time, the Next Header value of the IPv6 header can use 59 to identify an "Opaque message", and the destination address of the IPv6 header identifies the "NH59-STAMP" detection message.

In this embodiment of the present application, the correspondence between the address A5 and the "STAMP" indication information may be implemented by configuring on the device B. Different implementation manners are described in detail below.

An example, which can be configured on device B: Ipv6 address 2001:db1::1234 function oam-stamp. "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, and "function oam-stamp" means "STAMP" indicates the function, which can be followed by UDP+STAMP or NH59+STAMP.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-udp-stamp". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-udp-stamp" indicates the "UDP-STAMP" indication function, and the address is followed by UDP+STAMP.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-nh59-stamp". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-nh59-stamp" indicates the "NH59-STAMP" indication function, and the address is followed by NH59+STAMP.

As another example, a loopback IPv6 address can also be configured on device B. For example, the loopback IPv6 address can be an address located in the 0:0:0:0:0:FFFF:7F00:0/104 address segment. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address 0:0:0:0:0:FFFF:7F00:1234 function oam-stamp.

It should be understood that the above two addresses are both unicast IPv6 addresses, and the semantics of the addresses and their indication information can be stored in the FIB, that is, the unicast addresses and their corresponding indication information. For the received tunnel packet, after device B decapsulates the tunnel header and obtains the IPv6 header, according to the destination address of the IPv6 header is a unicast address, it searches the FIB table accordingly to obtain the indication information corresponding to the address as "STAMP detection packet". Arts".

As another example, in this embodiment of the present application, a multicast address, that is, the address of the FFxx::/8 address segment, may be configured on the device B to identify the above function. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address FF03::1234 function oam-stamp.

It should be understood that the above addresses are all multicast IPv6 addresses, and the semantics of the address and its indication information can be stored in the MFIB, that is, the multicast address and its corresponding indication information. After receiving the OAM detection packet, device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet. According to the destination address of the IPv6 header as the multicast address, the device B searches the MFIB table accordingly to obtain the indication information corresponding to the address as "STAMP detection message".

3. Device B performs corresponding processing of STAMP detection.

Device B determines that the IP-encapsulated OAM packet is a STAMP detection packet according to the destination address A5 of the IP-encapsulated IPv6 header. Therefore, Device B needs to perform STAMP detection on the IP-encapsulated OAM packet. Specifically, device B needs to modify and loopback the IP-encapsulated OAM packet, and construct a STAMP bounce packet.

For example, device B modifies the destination address of the IPv6 header of the IP-encapsulated OAM packet to the address of A (for example, address A7), and modifies the source address to the address of device B (for example, address A8), thereby constructing a STAMP Bounce message.

Device B can also send STAMP bounce packets to device A. Specifically, according to DA=A7 in the IPv6 header of the STAMP bounce packet (destination address A7 is an address of device A), device B looks up the table to obtain the next hop and outgoing interface of destination address A7. And according to the next hop and outgoing interface, the packet is sent along the corresponding outgoing interface, and finally reaches device A.

Optionally, in some embodiments, the source address A6 may also be a semantic IPv6 address, which is used to instruct device A to process the OAM response packet. The destination address A7 of the packet sent by device B to device A can be the same as address A6.

For example, configure the following address on device A and carry it in the detection packet as the return address: Ipv6 address 2001:db3::1234 function oam-reply-process. The address 2001:db3::1234 corresponds to the addresses of A7 and A6, and the OAM-reply-process identifies that the address is an instruction to process the OAM response message. When device A receives an IPv6 packet, and the destination address of the packet is an address with OAM-reply-process indication (or End.ORP) information, it determines that the packet is an OAM response packet, and performs corresponding processing.

The following takes OAM detection as S-BFD, and the IPv6 header in the IP-encapsulated OAM packet is the first IPv6 header as an example, and in conjunction with FIG. The specific implementation manner of instructing the egress device (eg, device B) of the tunnel to perform OAM detection will be described in detail.

It should be understood that the example in FIG. 11 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to specific numerical values or specific scenarios exemplified. According to the example of FIG. 11 given below, those skilled in the art can obviously make various equivalent modifications or changes, and such modifications and changes also fall within the scope of the embodiments of the present application.

As shown in Figure 11, the OAM detection packet sent by device A to device B includes a tunnel header and an IP-encapsulated OAM packet (IPv6 header+UDP header+OAM packet). Wherein, the source address A26 of the IPv6 header (also referred to as the first IPv6 header) of the OAM packet encapsulated by IP is the address of device A, the destination address A25 is an address on device B and the address A25 indicates "S- BFD Detection". It can also be understood that the address A25 corresponds to the semantics of "S-BFD detection".

The "S-BFD detection" here means that device B, as the tunnel egress device, after receiving the OAM detection packet, pops out the tunnel header to obtain the OAM packet encapsulated by IP. According to the OAM packet encapsulated by IP S-BFD The BFD response packet is sent to device A. As an example, the S-BFD response message may be obtained by modifying the source address and the destination address in the IPv6 header of the IP-encapsulated OAM message.

It should be understood that the above S-BFD response message is equivalent to modifying the IPv6 header of the IP-encapsulated OAM message obtained after decapsulation, and finally sending the message to device A, which is equivalent to doing Modification and loopback.

The process of processing OAM detection packets on device B is described in detail below.

1. Device B is the egress device of the tunnel, and decapsulates the received OAM detection packet shown in Figure 11.

2. Device B obtains the semantics corresponding to the destination address A25 in the inner IPv6 header.

Device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet (the part of the OAM packet encapsulated by IP). According to the destination address A25 of the IPv6 header of the IP-encapsulated OAM packet, this machine address, look up the table to obtain the semantics corresponding to the address A25 as "S-BFD detection". That is, device B can determine that the packet is an S-BFD detection packet according to the address A5.

In the OAM detection packet shown in Figure 11, the IPv6 header is followed by a UDP header, and the S-BFD detection packet is followed by the UDP header. In this case, the port number in the UDP header identifies an "OAM packet" or "Opaque packet", and the destination address in the IPv6 header identifies the "UDP-SBFD" detection packet.

Optionally, in some embodiments, an S-BFD detection packet may be directly followed by the IPv6 header. At this time, the Next Header value of the IPv6 header can use 59 to identify an "Opaque packet", and the destination address of the IPv6 header identifies the "NH59-SBFD" detection packet.

In this embodiment of the present application, the correspondence between the address A25 and the "S-BFD" indication information can be implemented by configuring on the device B. Different implementation manners are described in detail below.

An example, can be configured on device B: Ipv6 address 2001:db1::1234 function oam-sbfd. "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-sbfd" indicates the "S-BFD" indication function, and the address can be followed by UDP+SBFD, or NH59+ SBFD.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-udp-sbfd". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-udp-sbfd" indicates the "UDP-SBFD" indication function, and the address is followed by UDP+SBFD.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-nh59-sbfd". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-nh59-sbfd" indicates the "NH59-SBFD" indication function, and the address is followed by NH59+SBFD.

As another example, a loopback IPv6 address can also be configured on device B. For example, the loopback IPv6 address can be an address located in the 0:0:0:0:0:FFFF:7F00:0/104 address segment. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address 0:0:0:0:0:FFFF:7F00:1234 function oam-sbfd.

It should be understood that the above two addresses are both unicast IPv6 addresses, and the semantics of the addresses and their indication information can be stored in the FIB, that is, the unicast addresses and their corresponding indication information. For the received tunnel packet, after decapsulating the tunnel header and obtaining the IPv6 header, Device B searches the FIB table according to the destination address of the IPv6 header as a unicast address and obtains the corresponding indication information as "S-BFD". detection message".

As another example, in this embodiment of the present application, a multicast address, that is, the address of the FFxx::/8 address segment, may be configured on the device B to identify the above function. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address FF03::1234 function oam-sbfd.

It should be understood that the above addresses are all multicast IPv6 addresses, and the semantics of the address and its indication information can be stored in the MFIB, that is, the multicast address and its corresponding indication information. After receiving the OAM detection packet, device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet. According to the destination address of the IPv6 header as the multicast address, device B searches the MFIB table to obtain the indication information corresponding to the address as "S-BFD detection packet".

3. Device B performs corresponding processing of S-BFD detection.

Device B determines that the IP-encapsulated OAM packet is an S-BFD detection packet according to the indication of the destination address A25 in the IPv6 header of the IP-encapsulated OAM packet. Therefore, device B needs to detect the IP-encapsulated OAM packet. Corresponding processing for S-BFD detection is performed. Specifically, device B needs to modify and loop back the IP-encapsulated OAM packet, and construct an S-BFD response packet.

For example, device B modifies the destination address of the IPv6 header of the IP-encapsulated OAM packet to the address of A (for example, address A27), and modifies the source address to the address of device B (for example, address A28), thereby constructing an S -BFD response message.

Device B can also send an S-BFD response packet to device A. Specifically, according to DA=A27 in the IPv6 header of the S-BFD response packet (destination address A27 is an address of device A), device B looks up the table to obtain the next hop and outgoing interface of destination address A27. And according to the next hop and outgoing interface, the packet is sent along the corresponding outgoing interface, and finally reaches device A.

Optionally, in some embodiments, the source address A26 may also be a semantic IPv6 address, which is used to instruct the device A to process the OAM response packet. The destination address A27 of the packet sent by device B to device A can be the same as address A26.

For example, configure the following address on device A and carry it in the detection packet as the return address: Ipv6 address 2001:db3::1234 function oam-reply-process. The address 2001:db3::1234 corresponds to the addresses of A27 and A26, and the OAM-reply-process identifies that the address is an instruction to process the OAM response message. When device A receives an IPv6 packet, and the destination address of the packet is an address with OAM-reply-process indication (or End.ORP) information, it determines that the packet is an OAM response packet, and performs corresponding processing.

In the following, the OAM detection is used as Ping, and the IPv6 header in the OAM packet encapsulated by IP is the first IPv6 header as an example. In conjunction with FIG. 12 , the ingress device (for example, device A) of the tunnel indicates the tunnel through the destination address of the first IPv6 header. The specific implementation of OAM detection performed by the exit device (for example, device B) of the device B will be described in detail.

It should be understood that the example in FIG. 12 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to specific numerical values or specific scenarios exemplified. According to the example of FIG. 12 given below, those skilled in the art can obviously make various equivalent modifications or changes, and such modifications and changes also fall within the scope of the embodiments of the present application.

As shown in Figure 12, the OAM detection packet sent by device A to device B includes a tunnel header and an IP-encapsulated OAM packet (IPv6 header+UDP header+OAM packet). Among them, the source address A12 of the inner IPv6 header (also referred to as the first IPv6 header) of the IP-encapsulated OAM packet is the address of device A, and the destination address A11 is an address on device B, which corresponds to a Semantics of "Ping detection".

"Ping detection" here means that device B can determine that the OAM packet encapsulated by IP is a ping detection packet based on this address.

1. Device B is the egress device of the tunnel, and decapsulates the received OAM detection packet shown in Figure 12.

2. Device B obtains the semantics corresponding to the destination address A11 in the IPv6 header.

Device B decapsulates the OAM detection packet and obtains the part after the tunnel header of the OAM detection packet (the OAM packet encapsulated by IP). According to the destination address A11 of the IPv6 header of the OAM packet encapsulated by IP, it is the local device. Address, look up the table to obtain the semantic corresponding to the address A11 is "Ping detection". That is, device B can determine that the packet is a Ping detection packet according to the address A11.

In the OAM detection packet shown in Figure 12, the IPv6 header is followed by a UDP header, and the UDP header is followed by the Ping detection packet. At this time, the port number in the UDP header identifies an "OAM packet" or "Opaque packet", and the destination address in the IPv6 header identifies the "UDP-Ping" detection packet.

Optionally, in some embodiments, a Ping detection packet may be directly followed by the IPv6 header. At this time, the Next Header value of the IPv6 header can use 59 to identify an "Opaque packet", and the destination address of the IPv6 header identifies the "NH59-Ping" detection packet.

In this embodiment of the present application, the correspondence between the address A11 and the "Ping detection" indication information can be implemented by configuring on the device B. Different implementation manners are described in detail below.

An example, which can be configured on device B: Ipv6 address 2001:db1::1234 function oam-Ping. "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-Ping" indicates the "Ping detection" indication function, and the address can be followed by UDP+Ping, or NH59+Ping .

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-udp-Ping". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-udp-Ping" indicates the "UDP-Ping" indication function, and the address is followed by UDP+Ping.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-nh59-Ping". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-nh59-Ping" indicates the "NH59-Ping" indication function, and the address is followed by NH59+Ping.

As another example, a loopback IPv6 address can also be configured on device B. For example, the loopback IPv6 address can be an address located in the 0:0:0:0:0:FFFF:7F00:0/104 address segment. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address 0:0:0:0:0:FFFF:7F00:1234 function oam-Ping.

It should be understood that the above two addresses are both unicast IPv6 addresses, and the semantics of the addresses and their indication information can be stored in the FIB, that is, the unicast addresses and their corresponding indication information. For the received tunnel packet, after device B decapsulates the tunnel header and obtains the IPv6 header, according to the destination address of the IPv6 header as a unicast address, it searches the FIB table accordingly to obtain the indication information corresponding to the address as "Ping detection packet". Arts".

As another example, in this embodiment of the present application, a multicast address, that is, the address of the FFxx::/8 address segment, may be configured on the device B to identify the above function. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address FF03::1234 function oam-Ping.

It should be understood that the above addresses are all multicast IPv6 addresses, and the semantics of the address and its indication information can be stored in the MFIB, that is, the multicast address and its corresponding indication information. After receiving the OAM detection packet, device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet. According to the destination address of the IPv6 header as the multicast address, the device B searches the MFIB table accordingly to obtain the indication information corresponding to the address as "Ping detection packet".

3. Device B constructs an Echo Reply message and sends it to device A.

Device B determines that the OAM packet encapsulated by IP is an Echo Request packet according to the "Ping detection" instruction, and constructs an Echo Reply packet. For example, device B modifies the destination address of the IPv6 header of the IP-encapsulated OAM packet to the address of A (for example, address A13), and modifies the source address to the address of device B (for example, address A14), thereby constructing an Echo Reply reply message.

It should be understood that the above Echo Reply response message is equivalent to modifying the IPv6 header of the IP-encapsulated OAM message obtained after decapsulation, and finally sending the message to device A, which is equivalent to doing Modification and loopback.

Specifically, according to the DA=A13 in the IPv6 header of the Echo Reply reply packet (the destination address A13 is an address of the device A), the device B looks up the table to obtain the next hop and outgoing interface of the destination address A13. And according to the next hop and outgoing interface, the packet is sent along the corresponding outgoing interface, and finally reaches device A.

Optionally, in some embodiments, the source address A12 may also be a semantic IPv6 address, which is used to instruct the device A to process the OAM response packet. The destination address A13 of the packet sent by device B to device A can be the same as address A12.

For example, configure the following address on device A and carry it in the detection packet as the return address: Ipv6 address 2001:db3::1234 function oam-reply-process. The address 2001:db3::1234 corresponds to the addresses of A12 and A13, and the OAM-reply-process identifies that the address is an instruction to process the OAM response message. When device A receives an IPv6 packet, and the destination address of the packet is an address with OAM-reply-process indication (or End.ORP) information, it determines that the packet is an OAM response packet, and performs corresponding processing.

The following takes OAM detection as BFD, and the IPv6 header in the IP-encapsulated OAM packet is the first IPv6 header as an example, and in conjunction with FIG. The specific implementation of OAM detection performed by the exit device (for example, device B) of the device B will be described in detail.

It should be understood that the example in FIG. 13 is only for helping those skilled in the art to understand the embodiments of the present application, but is not intended to limit the embodiments of the present application to specific numerical values or specific scenarios exemplified. According to the example of FIG. 13 given below, those skilled in the art can obviously make various equivalent modifications or changes, and such modifications and changes also fall within the scope of the embodiments of the present application.

As shown in Figure 13, the OAM detection packet sent by device A to device B includes a tunnel header and an IP-encapsulated OAM packet (IPv6 header+UDP header+OAM packet). Among them, the source address A16 of the IPv6 header of the IP-encapsulated OAM packet is the address of device A, the destination address A15 is an address on device B and the address A15 indicates "BFD detection", which can also be understood as the address A15 corresponds to " BFD detection" semantics.

The "BFD detection" here means that device B can determine that the OAM packet encapsulated by IP is a BFD detection packet based on this address.

1. Device B is the egress device of the tunnel, and decapsulates the received OAM detection packet shown in Figure 13.

2. Device B obtains the semantics corresponding to the destination address A15 in the IPv6 header.

Device B decapsulates the OAM detection packet and obtains the part after the tunnel header of the OAM detection packet (the OAM packet encapsulated by IP). According to the destination address A15 of the IPv6 header of the OAM packet encapsulated by IP, it is the local device. Address, look up the table to obtain the semantic corresponding to the address A15 is "BFD detection message". That is, device B can determine that the packet is a BFD detection packet based on the address A15.

In the OAM detection packet shown in Figure 13, the IPv6 header is followed by a UDP header, and the BFD detection packet is followed by the UDP header. In this case, the port number in the UDP header identifies an "OAM packet" or "Opaque packet", and the destination address in the IPv6 header identifies the "UDP-BFD" detection packet.

Optionally, in some embodiments, the IPv6 header may be directly followed by a BFD detection packet. At this time, the Next Header value of the IPv6 header can use 59 to identify an "Opaque packet", and the destination address of the IPv6 header identifies the "NH59-BFD" detection packet.

In this embodiment of the present application, the correspondence between the address A15 and the "BFD" indication information may be implemented by configuring on the device B. Different implementation manners are described in detail below.

An example, can be configured on device B: Ipv6 address 2001:db1::1234 function oam-bfd. "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, and "function oam-bfd" indicates the "BFD" indication function, which can be followed by UDP+BFD or NH59+BFD.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-udp-bfd". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-udp-bfd" indicates the "UDP-BFD" indication function, and the address is followed by UDP+BFD.

Another example, can also be configured on device B: "Ipv6 address 2001:db1::1234 function oam-nh59-bfd". Among them, "IPv6 address 2001:db1::1234" is a unicast IPv6 address on device B, "function oam-nh59-bfd" indicates the "NH59-BFD" indication function, and the address is followed by NH59+BFD.

As another example, a loopback IPv6 address can also be configured on device B. For example, the loopback IPv6 address can be an address located in the 0:0:0:0:0:FFFF:7F00:0/104 address segment. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address 0:0:0:0:0:FFFF:7F00:1234 function oam-bfd.

It should be understood that the above two addresses are both unicast IPv6 addresses, and the semantics of the addresses and their indication information can be stored in the FIB, that is, the unicast addresses and their corresponding indication information. For the received tunnel packet, after device B decapsulates the tunnel header and obtains the IPv6 header, according to the destination address of the IPv6 header as a unicast address, it searches the FIB table accordingly to obtain the indication information corresponding to the address as "BFD detection packet". Arts".

As another example, in this embodiment of the present application, a multicast address, that is, the address of the FFxx::/8 address segment, may be configured on the device B to identify the above function. The address of this address segment is not unique to device B, but an address that can be used by all devices. Therefore, the address usually does not need to be configured on device B, but is specified by the protocol, but its meaning is similar to that configured on device B. The configuration on device B is as follows: Ipv6 address FF03::1234 function oam-bfd.

It should be understood that the above addresses are all multicast IPv6 addresses, and the semantics of the address and its indication information can be stored in the MFIB, that is, the multicast address and its corresponding indication information. After receiving the OAM detection packet, device B decapsulates the OAM detection packet to obtain the part after the tunnel header of the OAM detection packet. According to the destination address of the IPv6 header as the multicast address, the device B searches the MFIB table accordingly to obtain the indication information corresponding to the address as "BFD detection packet".

3. Device B performs corresponding processing of BFD detection.

Device B processes the OAM packet according to the destination address A15 in the inner IPv6 header indicating "BFD detection". Specifically, device B may determine that the packet is a BFD session established, and detect the status (eg, DOWN/UP) of the BFD session.

An OAM detection method provided by an embodiment of the present application is described in detail above with reference to FIGS. 1 to 13 , and an embodiment of the apparatus of the present application will be described in detail below with reference to FIGS. 14 to 19 . It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, for the parts not described in detail, reference may be made to the foregoing method embodiments.

FIG. 14 is a schematic structural diagram of a first network device 1400 provided by an embodiment of the present application. The first network device 1400 shown in FIG. 14 may perform the corresponding steps performed by the first network device in the methods of the foregoing embodiments. As shown in FIG. 14 , the first network device 1400 includes: a receiving module 1410, a processing module 1420,

a receiving module 1410, configured to receive, via the tunnel, a first packet sent by a second network device, where the first packet includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM packet, The second network device is an ingress device of the tunnel;

a processing module 1420, configured to determine the type of OAM detection according to the destination address DA of the first IPv6 header;

The processing module 1420 is further configured to perform detection according to the type of the OAM detection.

Optionally, the first IPv6 header is located between the tunnel header and the OAM packet.

Optionally, the first packet further includes a User Datagram Protocol UDP header, and the destination port number of the UDP header is used to indicate that the first packet includes the OAM packet,

The processing module 1420 is further configured to: determine that the first packet includes the OAM packet according to the destination port number in the UDP header.

Optionally, the Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet.

The processing module 1420 is further configured to: determine that the first packet includes the OAM packet according to the value of the Next Header field.

Optionally, the processing module 1420 is specifically configured to: determine that the DA of the first IPv6 header is the unicast IPv6 address of the first network device; determine according to the DA of the first IPv6 header and the forwarding information base FIB The type of the OAM detection, wherein the FIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection.

Optionally, the processing module 1420 is specifically configured to: determine that the DA of the first IPv6 header is a multicast IPv6 address; determine the DA detected by the OAM according to the DA of the first IPv6 header and the multicast forwarding information base MFIB. type, wherein the MFIB includes the correspondence between the DA of the first IPv6 header and the type detected by the OAM.

Optionally, the processing module 1420 is specifically configured to: decapsulate the first packet to obtain the OAM packet; determine a second packet according to the OAM packet; Send the second message.

Optionally, the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the DA of the second IPv6 header indicates the second IPv6 address. The packet is an OAM detection response packet.

Optionally, the DA of the second IPv6 header is the source address SA of the first IPv6 header.

Optionally, the type of the OAM detection includes any one of the following: Simple Bidirectional Active Measurement Protocol STAMP Detection, Bidirectional Active Measurement Protocol TWAMP Detection, Bidirectional Forwarding Detection BFD, Seamless Bidirectional Forwarding Detection S-BFD, Internet Packet Detector PING detection.

Optionally, the tunnel includes any one of the following: a multi-protocol label-switched MPLS tunnel, an Internet Protocol IP tunnel, a segment routing SRv6 tunnel using Internet Protocol version 6, an explicit replication BIER tunnel based on a bit index, the Internet Bit-indexed explicit replication of BIERv6 tunnels for version 6 of the protocol.

FIG. 15 is a schematic diagram of a hardware structure of a first network device 2000 according to an embodiment of the present application. The first network device 2000 shown in FIG. 15 may perform the corresponding steps performed by the first network device in the methods of the foregoing embodiments.

As shown in FIG. 15 , the first network device 2000 includes a processor 2001, a memory 2002, an interface 2003 and a bus 2004. The interface 2003 may be implemented in a wireless or wired manner, and may specifically be a network card. The above-mentioned processor 2001 , memory 2002 and interface 2003 are connected through a bus 2004 .

The interface 2003 may specifically include a transmitter and a receiver, which are used by the first network device to implement the above-mentioned transceiving. For example, the interface 2003 is configured to receive the first packet sent by the second network device through the tunnel.

The processor 2001 is configured to execute the processing performed by the first network device in the foregoing embodiment. For example, for determining the type of OAM detection based on the destination address DA of the first IPv6 header; detecting based on the type of OAM detection; and/or for other processes of the techniques described herein. The memory 2002 includes an operating system 20021 and an application program 20022 for storing programs, codes or instructions. When the processor or hardware device executes these programs, codes or instructions, the processing process involving the first network device in the method embodiment can be completed. Optionally, the memory 2002 may include read-only memory (ROM) and random access memory (RAM). Wherein, the ROM includes a basic input/output system (basic input/output system, BIOS) or an embedded system; the RAM includes an application program and an operating system. When the first network device 2000 needs to be run, the system is booted through the BIOS solidified in the ROM or the bootloader in the embedded system, and the first network device 2000 is guided into a normal operation state. After the first network device 2000 enters the normal running state, the application program and the operating system running in the RAM, thus, the processing process involving the first network device 2000 in the method embodiment is completed.

It can be understood that FIG. 15 only shows a simplified design of the first network device 2000 . In practical applications, the first network device may contain any number of interfaces, processors or memories.

FIG. 16 is a schematic diagram of a hardware structure of another first network device 2100 according to an embodiment of the present application. The first network device 2100 shown in FIG. 16 may perform the corresponding steps performed by the first network device in the methods of the foregoing embodiments.

As shown in FIG. 16 , the first network device 2100 includes: a main control board 2110 , an interface board 2130 , a switching network board 2120 and an interface board 2140 . The main control board 2110, the interface boards 2130 and 2140, and the switching network board 2120 are connected to the system backplane through the system bus to realize intercommunication. Among them, the main control board 2110 is used to complete functions such as system management, equipment maintenance, and protocol processing. The switch fabric board 2120 is used to complete data exchange between interface boards (interface boards are also called line cards or service boards). The interface boards 2130 and 2140 are used to provide various service interfaces (eg, POS interface, GE interface, ATM interface, etc.), and realize data packet forwarding.

The interface board 2130 may include a central processing unit 2131 , a forwarding table entry memory 2134 , a physical interface card 2133 and a network processor 2132 . Among them, the central processing unit 2131 is used to control and manage the interface board and communicate with the central processing unit on the main control board. The forwarding entry storage 2134 is used to store entries. The physical interface card 2133 is used to receive and transmit traffic.

It should be understood that the operations on the interface board 2140 in the embodiment of the present application are consistent with the operations on the interface board 2130, and for brevity, details are not repeated here.

It should be understood that the first network device 2100 in this embodiment may correspond to the functions and/or various steps performed by the foregoing method embodiments, and details are not described herein again.

In addition, it should be noted that there may be one or more main control boards, and when there are multiple main control boards, they may include an active main control board and a backup main control board. There may be one or more interface boards, and the stronger the data processing capability of the first network device, the more interface boards provided. There can also be one or more physical interface cards on the interface board. There may be no switch fabric boards, or there may be one or more boards. When there are multiple boards, load sharing and redundancy backup can be implemented together. Under the centralized forwarding architecture, the first network device may not need to switch the network board, and the interface board undertakes the processing function of the service data of the entire system. Under the distributed forwarding architecture, the first network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the first network device in the distributed architecture are greater than those in the centralized architecture. The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

FIG. 17 is a schematic structural diagram of a second network device 1700 provided by an embodiment of the present application. The second network device 1700 shown in FIG. 17 may perform the corresponding steps performed by the second network device in the methods of the foregoing embodiments. As shown in FIG. 17 , the second network device 1700 includes: a processing module 1710, a sending module 1720,

The processing module 1710 is configured to obtain a first packet, where the first packet includes a tunnel header, a first Internet Protocol version 6 IPv6 header and an operation management and maintenance OAM packet, and the destination address DA of the first IPv6 header Used to indicate the type of OAM detection;

The sending module 1720 is configured to send the first packet to a first network device via the tunnel, where the first network device is an egress device of the tunnel.

Optionally, the first packet further includes a User Datagram Protocol UDP header, and the destination port number of the UDP header is used to indicate that the first packet includes the OAM packet.

Optionally, the second network device 1700 further includes:

A receiving module 1730, configured to receive a second packet, where the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the second IPv6 header The DA of the header indicates that the second message is an OAM detection response message;

The processing module 1710 is further configured to process the second packet according to the DA of the second IPv6 header.

FIG. 18 is a schematic diagram of a hardware structure of a second network device 2200 according to an embodiment of the present application. The second network device 2200 shown in FIG. 18 may perform the corresponding steps performed by the second network device in the methods of the foregoing embodiments.

As shown in FIG. 18 , the second network device 2200 includes a processor 2201 , a memory 2202 , an interface 2203 and a bus 2204 . The interface 2203 may be implemented in a wireless or wired manner, and may specifically be a network card. The above-mentioned processor 2201 , memory 2202 and interface 2203 are connected through a bus 2204 .

The interface 2203 may specifically include a transmitter and a receiver, which are used by the second network device to implement the above-mentioned transceiving. For example, the interface is used to support sending the first packet to the first network device via the tunnel.

The processor 2201 is configured to perform the processing performed by the second network device in the foregoing embodiment. For example, for obtaining the first message; and/or for other processes of the techniques described herein. The memory 2202 includes an operating system 22021 and an application program 22022, which are used to store programs, codes or instructions. When the processor or the hardware device executes these programs, codes or instructions, the processing process involving the second network device in the method embodiment can be completed. Optionally, the memory 2202 may include read-only memory (ROM) and random access memory (RAM). Wherein, the ROM includes a basic input/output system (basic input/output system, BIOS) or an embedded system; the RAM includes an application program and an operating system. When the second network device 2200 needs to be run, the system is booted through the BIOS solidified in the ROM or the bootloader in the embedded system, and the second network device 2200 is guided to enter a normal operation state. After the second network device 2200 enters the normal running state, the application program and the operating system running in the RAM, thus, the processing process involving the second network device 2200 in the method embodiment is completed.

It can be understood that FIG. 18 only shows a simplified design of the second network device 2200 . In practical applications, the second network device may contain any number of interfaces, processors or memories.

FIG. 19 is a schematic diagram of a hardware structure of another second network device 2400 according to an embodiment of the present application. The second network device 2400 shown in FIG. 19 may perform the corresponding steps performed by the second network device in the methods of the foregoing embodiments.

As shown in FIG. 19 , the second network device 2400 includes: a main control board 2410 , an interface board 2430 , a switching network board 2420 and an interface board 2440 . The main control board 2410, the interface boards 2430 and 2440, and the switching network board 2420 are connected to the system backplane through the system bus to realize intercommunication. Among them, the main control board 2410 is used to complete functions such as system management, equipment maintenance, and protocol processing. The switch fabric board 2420 is used to complete data exchange between interface boards (interface boards are also called line cards or service boards). The interface boards 2430 and 2440 are used to provide various service interfaces (eg, POS interface, GE interface, ATM interface, etc.), and realize data packet forwarding.

The interface board 2430 may include a central processing unit 2431 , a forwarding table entry memory 2434 , a physical interface card 2433 and a network processor 2432 . Among them, the central processing unit 2431 is used to control and manage the interface board and communicate with the central processing unit on the main control board. The forwarding entry storage 2434 is used to store entries. The physical interface card 2433 is used to complete the reception and transmission of traffic.

It should be understood that the operations on the interface board 2440 in the embodiment of the present application are the same as the operations on the interface board 2430, and for brevity, details are not repeated here. It should be understood that the second network device 2400 in this embodiment may correspond to the functions and/or various steps performed by the foregoing method embodiments, and details are not described herein again.

In addition, it should be noted that there may be one or more main control boards, and when there are multiple main control boards, they may include an active main control board and a backup main control board. There may be one or more interface boards, and the stronger the data processing capability of the second network device, the more interface boards provided. There can also be one or more physical interface cards on the interface board. There may be no switch fabric boards, or there may be one or more boards. When there are multiple boards, load sharing and redundancy backup can be implemented together. Under the centralized forwarding architecture, the second network device may not need a switching network board, and the interface board undertakes the processing function of the service data of the entire system. Under the distributed forwarding architecture, the second network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the second network device in the distributed architecture are greater than those in the centralized architecture. The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

Embodiments of the present application further provide a computer-readable medium, where program codes are stored in the computer-readable medium, and when the computer program codes are run on a computer, the computer executes the method performed by the first network device. These computer-readable storages include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (erasable PROM, EPROM), Flash memory, electrical EPROM (electrically EPROM, EEPROM) and hard drive (hard drive).

Embodiments of the present application further provide a computer-readable medium, where program codes are stored in the computer-readable medium, and when the computer program codes are run on a computer, the computer executes the method performed by the second network device. These computer-readable storages include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (erasable PROM, EPROM), Flash memory, electrical EPROM (electrically EPROM, EEPROM) and hard drive (hard drive).

An embodiment of the present application further provides a chip system, which is applied to the first network device, the chip system includes: at least one processor, at least one memory, and an interface circuit, where the interface circuit is responsible for information between the chip system and the outside world interaction, the at least one memory, the interface circuit and the at least one processor are interconnected by a wire, and the at least one memory stores instructions; the instructions are executed by the at least one processor to perform the above aspects The operation of the first network device in the method.

In the specific implementation process, the chip can be a central processing unit (CPU), a microcontroller (MCU), a microprocessor (microprocessing unit, MPU), a digital signal processor (digital signal processor) processing, DSP), system on chip (system on chip, SoC), application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or programmable logic device (programmable logic device) , PLD).

The embodiment of the present application further provides another chip system, which is applied to a second network device, the chip system includes: at least one processor, at least one memory, and an interface circuit, where the interface circuit is responsible for the communication between the chip system and the outside world. Information exchange, the at least one memory, the interface circuit and the at least one processor are interconnected by lines, and the at least one memory stores instructions; the instructions are executed by the at least one processor to perform the above Operations of the second network device in the method of the aspect.

Embodiments of the present application further provide a computer program product, which is applied to a first network device, where the computer program product includes a series of instructions, when the instructions are executed, to perform the methods described in the above aspects. Operation of the first network device.

Embodiments of the present application further provide a computer program product, which is applied to a second network device, where the computer program product includes a series of instructions, when the instructions are executed, to perform the methods described in the above aspects. Operation of the second network device.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for OAM detection, characterized in that the method comprises:

The first network device receives, via the tunnel, a first packet sent by the second network device, where the first packet includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation, management and maintenance OAM packet, and the second The network device is an ingress device of the tunnel, and the first network device is an egress device of the tunnel;

The first network device determines the type of OAM detection according to the destination address DA of the first IPv6 header;

The first network device performs detection according to the type of the OAM detection.
The method according to claim 1, wherein the first IPv6 header is located between the tunnel header and the OAM packet.
The method according to claim 1 or 2, wherein the first packet further includes a User Datagram Protocol UDP header, and a destination port number of the UDP header is used to indicate that the first packet includes the Describe the OAM message,

The method also includes:

The first network device determines that the first packet includes the OAM packet according to the destination port number in the UDP header.
The method according to claim 1 or 2, wherein a Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet,

The method also includes:

The first network device determines that the first packet includes the OAM packet according to the value of the Next Header field.
The method according to any one of claims 1 to 4, wherein the first network device determines the type of OAM detection according to the destination address DA of the first IPv6 header, comprising:

The first network device determines that the DA of the first IPv6 header is the unicast IPv6 address of the first network device;

The first network device determines the type of the OAM detection according to the DA of the first IPv6 header and the forwarding information base FIB, wherein the FIB includes the DA of the first IPv6 header and the type of the OAM detection. Correspondence between.
The method according to any one of claims 1 to 4, wherein the first network device determines the type of OAM detection according to the destination address DA of the first IPv6 header, comprising:

The first network device determines that the DA of the first IPv6 header is a multicast IPv6 address;

The first network device determines the type of the OAM detection according to the DA of the first IPv6 header and the multicast forwarding information base MFIB, wherein the MFIB includes the DA of the first IPv6 header and the DA of the OAM detection. Correspondence between types.
The method according to any one of claims 1 to 6, wherein the first network device performs detection according to the type of the OAM detection, comprising:

The first network device decapsulates the first packet to obtain the OAM packet;

determining, by the first network device, a second packet according to the OAM packet;

The first network device sends the second packet to the second network device.
The method according to claim 7, wherein the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the second IPv6 header is the IPv6 address of the second network device. The DA in the IPv6 header indicates that the second message is an OAM detection response message.
The method according to claim 8, wherein the DA of the second IPv6 header is the source address SA of the first IPv6 header.
The method according to any one of claims 1 to 9, wherein the type of the OAM detection includes any one of the following: simple bidirectional active measurement protocol STAMP detection, bidirectional active measurement protocol TWAMP detection, bidirectional forwarding Detection of BFD, seamless bidirectional forwarding detection S-BFD, Internet packet detector PING detection.
The method according to any one of claims 1 to 10, wherein the tunnel comprises any one of the following: a multi-protocol label switched MPLS tunnel, an Internet Protocol IP tunnel, a segment using Internet Protocol version 6 Routed SRv6 Tunnels, Bit-Indexed-Based Explicit Replication BIER Tunnels, Bit-Indexed-Based Explicit Replication BIERv6 Tunnels for Internet Protocol Version 6.
A method for OAM detection, characterized in that the method comprises:

The second network device obtains a first packet, where the first packet includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM packet, and the destination address DA of the first IPv6 header is used for Indicates the type of OAM detection;

The second network device sends the first packet to the first network device via the tunnel, the second network device is an ingress device of the tunnel, and the first network device is an egress device of the tunnel.
The method according to claim 12, wherein the first IPv6 header is located between the tunnel header and the OAM packet.
The method according to claim 12 or 13, wherein the first packet further includes a User Datagram Protocol UDP header, and a destination port number of the UDP header is used to indicate that the first packet includes the Describe the OAM message.
The method according to any one of claims 12 to 14, wherein the Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet.
The method according to any one of claims 12 to 15, wherein the method further comprises:

The second network device receives a second packet, the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the second IPv6 header The DA of the header indicates that the second message is an OAM detection response message;

The second network device processes the second packet according to the DA of the second IPv6 header.
The method according to claim 16, wherein the DA of the second IPv6 header is the source address SA of the first IPv6 header.
The method according to any one of claims 12 to 17, wherein the type of the OAM detection includes any one of the following: simple bidirectional active measurement protocol STAMP detection, bidirectional active measurement protocol TWAMP detection, bidirectional forwarding Detection of BFD, seamless bidirectional forwarding detection S-BFD, Internet packet detector PING detection.
The method according to any one of claims 12 to 18, wherein the tunnel comprises any one of the following: a multi-protocol label switching MPLS tunnel, an Internet Protocol IP tunnel, a segment using Internet Protocol version 6 Routed SRv6 Tunnels, Bit-Indexed-Based Explicit Replication BIER Tunnels, Bit-Indexed-Based Explicit Replication BIERv6 Tunnels for Internet Protocol Version 6.
A first network device, wherein the first network device is an egress device of a tunnel, and the first network device includes:

A receiving module, configured to receive a first message sent by a second network device via the tunnel, where the first message includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM message, so The second network device is an ingress device of the tunnel;

a processing module, configured to determine the type of OAM detection according to the destination address DA of the first IPv6 header;

The processing module is further configured to perform detection according to the type of the OAM detection.
The first network device according to claim 20, wherein the first IPv6 header is located between the tunnel header and the OAM packet.
The first network device according to claim 20 or 21, wherein the first packet further includes a User Datagram Protocol (UDP) header, and a destination port number of the UDP header is used to indicate the first packet including the OAM message,

The processing module is further configured to: determine that the first packet includes the OAM packet according to the destination port number in the UDP header.
The first network device according to claim 20 or 21, wherein a Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet,

The processing module is further configured to: determine that the first message includes the OAM message according to the value of the Next Header field.
The first network device according to any one of claims 20 to 23, wherein the processing module is specifically configured to:

Determine that the DA of the first IPv6 header is the unicast IPv6 address of the first network device;

The type of the OAM detection is determined according to the DA of the first IPv6 header and the forwarding information base FIB, wherein the FIB includes a correspondence between the DA of the first IPv6 header and the type of the OAM detection.
The first network device according to any one of claims 20 to 23, wherein the processing module is specifically configured to:

Determine that the DA of the first IPv6 header is a multicast IPv6 address;

The type of the OAM detection is determined according to the DA of the first IPv6 header and the multicast forwarding information base MFIB, wherein the MFIB includes the correspondence between the DA of the first IPv6 header and the type of the OAM detection .
The first network device according to any one of claims 20 to 25, wherein the processing module is specifically configured to:

decapsulating the first message to obtain the OAM message;

determining the second message according to the OAM message;

Send the second packet to the second network device.
The first network device according to claim 26, wherein the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the The DA of the second IPv6 header indicates that the second message is an OAM detection response message.
The first network device according to claim 27, wherein the DA of the second IPv6 header is the source address SA of the first IPv6 header.
The first network device according to any one of claims 20 to 28, wherein the type of the OAM detection includes any one of the following: simple bidirectional active measurement protocol STAMP detection, bidirectional active measurement protocol TWAMP detection , Bidirectional forwarding detection BFD, seamless bidirectional forwarding detection S-BFD, Internet packet detector PING detection.
The first network device according to any one of claims 20 to 29, wherein the tunnel comprises any one of the following: a multi-protocol label switching (MPLS) tunnel, an Internet Protocol (IP) tunnel, a Version 6 of the segment routing SRv6 tunnel, bit-index-based explicit replication BIER tunnel, Internet Protocol version 6 bit-index-based explicit replication BIERv6 tunnel.
A second network device, characterized in that the second network device is an ingress device of a tunnel, and the second network device includes:

The processing module is configured to obtain a first message, where the first message includes a tunnel header, a first Internet Protocol version 6 IPv6 header, and an operation management and maintenance OAM message, and the destination address DA of the first IPv6 header is to indicate the type of OAM detection;

A sending module, configured to send the first packet to a first network device via the tunnel, where the first network device is an egress device of the tunnel.
The second network device according to claim 31, wherein the first IPv6 header is located between the tunnel header and the OAM packet.
The second network device according to claim 31 or 32, wherein the first packet further includes a User Datagram Protocol (UDP) header, and a destination port number of the UDP header is used to indicate the first packet including the OAM message.
The second network device according to any one of claims 31 to 33, wherein a Next Header field of the first IPv6 header is used to indicate that the first packet includes the OAM packet Arts.
The second network device according to any one of claims 31 to 34, wherein the second network device further comprises:

A receiving module, configured to receive a second packet, where the second packet includes a second IPv6 header, the destination address DA of the second IPv6 header is the IPv6 address of the second network device, and the second IPv6 header The DA indicates that the second message is an OAM detection response message;

The processing module is further configured to process the second packet according to the DA of the second IPv6 header.
The second network device according to claim 35, wherein the DA of the second IPv6 header is the source address SA of the first IPv6 header.
The second network device according to any one of claims 31 to 36, wherein the type of the OAM detection includes any one of the following: simple bidirectional active measurement protocol STAMP detection, bidirectional active measurement protocol TWAMP detection , Bidirectional forwarding detection BFD, seamless bidirectional forwarding detection S-BFD, Internet packet detector PING detection.
The second network device according to any one of claims 31 to 37, wherein the tunnel comprises any one of the following: a multi-protocol label switching (MPLS) tunnel, an Internet Protocol (IP) tunnel, a Version 6 of the segment routing SRv6 tunnel, bit-index-based explicit replication BIER tunnel, Internet Protocol version 6 bit-index-based explicit replication BIERv6 tunnel.
A first network device, comprising: a processor and a memory, the memory is used to store a program, and the processor is used to call and run the program from the memory to execute any one of claims 1 to 11 method described in item.
A second network device, comprising: a processor and a memory, wherein the memory is used to store a program, and the processor is used to call and run the program from the memory to execute any one of claims 12 to 19 method described in item.
A system for OAM detection, comprising the first network device according to any one of claims 20 to 30 and the second network device according to any one of claims 31 to 38.