WO2018210213A1

WO2018210213A1 - Method and device for implementing ioam packaging and storage medium

Info

Publication number: WO2018210213A1
Application number: PCT/CN2018/086788
Authority: WO
Inventors: 肖敏
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-05-18
Filing date: 2018-05-15
Publication date: 2018-11-22
Also published as: CN108964943B; CN108964943A

Abstract

Disclosed in the present disclosure is a method and device for implementing IOAM packaging and a storage medium. The method comprises: sending by an IOAM entry node a first out-of-band OAM message carrying IOAM configuration request information, the first out-of-band OAM message reaching in sequence various nodes on a business data message transmission path; receiving by the IOAM entry node a second out-of-band OAM message transmitted from IOAM transmission nodes and carrying IOAM configuration information; and performing by the IOAM entry node IOAM packaging on a business data message according to the IOAM configuration information of the various IOAM transmission nodes.

Description

Method and device for implementing IOAM package, storage medium

Cross-reference to related applications

The present application is based on a Chinese patent application filed on Jan. 18, 2017, the entire disclosure of which is hereby incorporated by reference.

Technical field

The present disclosure relates to the field of communications, and in particular, to a method and apparatus for implementing in-band operation management and maintenance (IOAM, In-situ Operations, Administration and Maintenance, or In-band Operations, Administration and Maintenance), and a storage medium.

Background technique

IOAM is a new data communication network operation management and maintenance (OAM) technology proposed by the industry. This technology is currently in the rapid development stage under the joint promotion of the industry, and is in the Internet Engineering Task Force (IETF). Carry out standardization work.

IETF's IOAM series of proposals draft-brockners-inband-oam-requirements, draft-brockners-inband-oam-transport and draft-brockners-inband-oam-data respectively describe the source of IOAM requirements, package format and data content, and Compared with Out-of-band Operations (Administration and Maintenance), which is standardized and widely deployed in data communication networks, IOAM is characterized in that IOAM data content is encapsulated into service data packets as service data packets. A part of the data is transmitted in the network, and the out-of-band OAM data content is encapsulated into a specially constructed OAM data message and transmitted as a separate protocol message in the network. As a supplement to out-of-band OAM, IOAM can implement functions that cannot be implemented by out-of-band OAM, such as detecting network nodes through which service data packets actually pass, verifying that the transmission path of service data is consistent with expectations, and adding traffic data packets. Serial number information to detect packet loss and out-of-order, etc. Accordingly, in order to implement the above functions, the network administrator needs to perform IOAM transmission nodes including an IOAM Transit Node and an IOAM Egress Node. The IOAM transit node is a node that needs to process the IOAM data content on the service data packet transmission path. Given that IOAM includes a variety of optional features, as well as the type of traffic carried by the network and the variability of the transmission path, these configurations are often complex and easily changeable.

IOAM encapsulation is to insert an IOAM header (IOAM header) into the service data message. Figure 1 is an IOAM header format diagram. As shown in Figure 1, the IOAM header is used to indicate the location of the IOAM data content (as in Figure 1). The IOAM header indication) and the length (such as the IOAM header length in Figure 1) also carry a set of IOAM function option types/lengths/values (TLVs, Type/Length/Value) as IOAM data content, where Each IOAM function option TLV corresponds to an IOAM function and carries the data required to complete the IOAM function. The IOAM encapsulation in the network, that is, the node inserted into the IOAM header is called an IOAM Ingress Node or an IOAM encapsulation node. The IOAM ingress node can be either a network node such as a switch or a router, or a personal computer or server. And other network terminals. Since the IOAM ingress node needs to complete the insertion of the IOAM header, it is necessary to determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, which is determined by the network administrator according to the configuration on each IOAM transmission node. It is determined and sent to the IOAM ingress node. As mentioned above, the configuration on the IOAM transit node is usually complicated and easy to change. Therefore, the method of implementing IOAM encapsulation by manually sending information at the IOAM ingress node increases network management. The burden of the staff is easy to make mistakes.

Summary of the invention

To solve the above technical problem, an embodiment of the present disclosure provides a method and apparatus for implementing IOAM encapsulation.

A method for implementing in-band IOAM encapsulation provided by an embodiment of the present disclosure includes:

The IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;

Receiving, by the IOAM ingress node, a second out-of-band OAM packet that carries the IOAM configuration information sent by the IOAM transmission node;

The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.

An apparatus for implementing an IOAM package provided by an embodiment of the present disclosure includes:

The sending unit is configured to send the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;

a receiving unit, configured to receive a second out-of-band OAM message that carries the IOAM configuration information sent by the IOAM transmission node;

The encapsulating unit is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.

In another aspect, an embodiment of the present invention further provides a storage medium storing a computer program configured to perform the above method for implementing IOAM encapsulation.

In the technical solution of the embodiment of the present disclosure, the IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path. The IOAM ingress node receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information. The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node. By adopting the technical solution of the embodiment of the present disclosure, the method for implementing IOAM encapsulation by manually sending information at the IOAM ingress node in the related art is solved, which increases the burden on the network administrator and is prone to error, and also enables the IOAM ingress node to support Automatically obtain the information required for IOAM encapsulation triggered by traffic.

DRAWINGS

The drawings generally illustrate the various embodiments discussed herein by way of example and not limitation.

1 is a format diagram of an IOAM header according to an embodiment of the present disclosure;

FIG. 2 is a schematic flowchart diagram of a method for implementing IOAM encapsulation according to an embodiment of the present disclosure;

3 is a schematic diagram of implementing IOAM encapsulation in an IP network according to application example 1 of the present disclosure;

4 is a format diagram of an ICMP message according to the first application example of the present disclosure;

5 is a format diagram of an IOAM configuration information TLV of Application Example 1 of the present disclosure;

6 is a schematic diagram of implementing IOAM encapsulation in an MPLS network according to application example 2 of the present disclosure;

7 is a format diagram of an LSP ping packet of the second application example of the present disclosure;

8 is a schematic diagram of implementing IOAM encapsulation by using LoopBack in an Ethernet network according to application example 3 of the present disclosure;

9 is a schematic diagram of implementing IOAM encapsulation by using LinkTrace in an Ethernet network according to application example 3 of the present disclosure;

10 is a format diagram of a LoopBack packet in the third application example of the present disclosure;

11 is a format diagram of a LinkTrace message according to the third application example of the present disclosure;

FIG. 12 is a schematic structural diagram of an apparatus for implementing an IOAM package according to an embodiment of the present disclosure.

detailed description

The embodiments of the present disclosure are described in detail with reference to the accompanying drawings.

2 is a schematic flowchart of a method for implementing IOAM encapsulation according to an embodiment of the present disclosure. As shown in FIG. 2, the method for implementing IOAM encapsulation includes the following steps:

Step 201: The IOAM ingress node sends a first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path.

Here, the first out-of-band OAM packet is only used to distinguish the subsequent second out-of-band OAM packet, and has no special meaning. The outband OAM packet follows the same transmission path as the service data packet, and is usually used to detect whether the transmission path between the sending node and the receiving node is normal. Networks with different forwarding technologies use different out-of-band OAM messages, for example, Internet Control Message Protocol (ICMP) packets defined by the IETF standard RFC 792 in the IP network as out-of-band OAM messages, in multi-protocol label switching ( In the MPLS network, the label switched path echo (LSP Ping) message defined by the IETF standard RFC 8029 is used as the outband OAM message, and the International Telecommunication Union (ITU) standard is used in the Ethernet (Ethernet) network. A loopback packet or a link trace (LinkTrace) packet defined by the .1731 is used as an outband OAM packet. The IOAM configuration request information can be used to ensure that the IOAM configuration request information reaches each IOAM transmission node on the service data packet transmission path, and the outband OAM has been deployed on the live network in large quantities. This method can be used. Very compatible with the live network.

In the embodiment of the present disclosure, when the triggering operation of the network administrator is obtained, the IOAM ingress node sends the first out-of-band OAM message carrying the IOAM configuration request information; or, when obtaining the triggering instruction of the network management module or the control application, The IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information; or, when the service data packet is triggered, the IOAM ingress node sends the first out-of-band OAM that carries the IOAM configuration request information. Message.

It can be seen that the timing of sending the first out-of-band OAM message carrying the IOAM configuration request information by the IOAM ingress node is very flexible, can be sent by the network administrator, or can be sent under the trigger of the network management module/control application, or It can also be sent under the trigger of service data packets.

In the embodiment of the present disclosure, the node on the service data packet transmission path includes at least one of the following: an IOAM transmission node, and a non-IOAM transmission node, where the IOAM transmission node includes an IOAM intermediate node and an IOAM egress node.

Step 202: The IOAM ingress node receives the second out-of-band OAM packet that carries the IOAM configuration information sent by the IOAM transmission node.

The first out-of-band OAM packet that carries the IOAM configuration request information sent by the IOAM ingress node will arrive at each node on the service data packet transmission path. If the first out-of-band OAM packet is received, the node is an IOAM transit node. That is, the node needs to process the IOAM data content, and the second out-of-band OAM packet replied by the node to the IOAM ingress node carries the IOAM configuration information of the node, where the IOAM configuration information of the node includes the node support. Which IOAM capabilities and enablement of each IOAM capability and related parameter configurations. If the node that receives the first out-of-band OAM packet is not the IOAM transit node, that is, the node does not need to process the IOAM data content, the node does not carry the second out-of-band OAM packet replied to the IOAM ingress node. The IOAM configuration information of the node.

Step 203: The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.

In the embodiment of the present disclosure, the IOAM ingress node determines, according to the IOAM configuration information of each IOAM transmission node, the IOAM function option TLVs included in the IOAM data content, and the length of each IOAM function option TLV; according to the IOAM function option TLVs And the length of each IOAM function option TLV, inserting an IOAM header in the service data packet, that is, implementing IOAM encapsulation of the service data packet.

The technical solutions of the embodiments of the present disclosure are further described in detail below with reference to specific application examples.

Application example one

3 is a schematic diagram of implementing IOAM encapsulation in an IP network. In this application example, the IOAM ingress node and the IOAM transit node perform the following steps:

Step 11: The IOM ingress node sends an ICMP request message carrying the IOAM configuration request information.

4 is a format diagram of an ICMP message. As shown in FIG. 4, an ICMP message includes an 8-bit type field and an 8-bit code field. The IETF standard defines some values of the two fields, for example, a type. 8 code 0 indicates an ICMP ping request, type 0 code 0 indicates an ICMP ping response, type 10 code 0 indicates a router request, type 9 code 0 indicates a router advertisement, and so on. By defining the types and code values that have not been specified, for example, the type 19 code 0 indicates an IOAM configuration request, and the type 20 code 0 indicates an IOAM configuration response, the ICMP request message can be carried to carry the IOAM configuration request information.

Step 12: The IOAM transmission node responds to the request, and returns an ICMP response message carrying the IOAM configuration information of the local node to the IOAM ingress node.

According to the mechanism of the ICMP, the sending node can send the ICMP request message to each node on the transmission path in turn by changing the time-to-live (TTL) value of the IP header in the ICMP request message. After receiving the ICMP request message carrying the IOAM configuration request information, the IOAM transmission node sends an ICMP Request message sending node, that is, an IOM ingress node, to the ICMP response message carrying the IOAM configuration information of the local node. The IOAM configuration information is written in the option data field of the ICMP response message in the form of a TLV. FIG. 5 is a format diagram of the IOAM configuration information TLV. As shown in FIG. 5, the Type field of the TLV indicates the IOAM configuration information. The Length field indicates the length of the TLV, and the Value field contains a set of sub-TLVs (Sub-TLVs). Each Sub-TLV carries configuration information of an IOAM function, where the sub-type (Sub-Type) The field indicates the code of an IOAM function supported by the node, the Length field indicates the length of the Sub-TLV, and the Value field indicates the configuration information of the IOAM function represented by the Sub-Type field, including whether the IOAM function is enabled on the node. (Enabled), and the configuration parameter values related to the IOAM function when enabled, for example, the configuration parameters related to the IOAM tracking (Tracing) function defined by the IETF proposal draft-brockners-inband-oam-data Including: inserting node information in Pre-allocated mode or Incremental mode, and the number of bytes required for node information.

Step 13: After the IOAM ingress node obtains the IOAM configuration of each node on the IP service packet transmission path, the IOAM encapsulation is determined.

After the IOAM ingress node obtains the IOAM configuration of each node on the IP service packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, and thus can determine the IP service packet. IOAM package.

Application example two

6 is a schematic diagram of implementing IOAM encapsulation in an MPLS network. In this application example, the IOAM ingress node and the IOAM transit node perform the following steps:

Step 21: The IOAM ingress node sends an LSP ping request message carrying the IOAM configuration request information.

Figure 7 is a format diagram of an LSP ping packet. As shown in Figure 7, an LSP ping request packet contains a set of TLVs. By adding a Type field to indicate a new TLV for the IOAM configuration request, the LSP ping request packet can be carried. IOAM configuration request information.

Step 22: The IOAM transmission node responds to the request, and returns an LSP Ping response message carrying the IOAM configuration information of the local node to the IOAM ingress node.

According to the LSP ping mechanism, the sending node can send the LSP ping request message to each node on the transmission path in turn by changing the TTL value of the MPLS header in the LSP ping request message. After receiving the LSP ping request message carrying the IOAM configuration request information, the IOAM transit node sends an LSP Ping response message to the LSP ping request packet sending node, that is, the IOAM ingress node, and carries the LSP Ping response packet carrying the IOAM configuration information of the local node. The method may be that the IOAM configuration information is written into the TLVs field of the LSP Ping response message in the form of a TLV, and the TLV adopts the format shown in FIG.

Step 23: After the IOAM ingress node obtains the IOAM configuration of each node on the MPLS service packet transmission path, the IOAM encapsulation is determined.

After the IOAM ingress node obtains the IOAM configuration of each node in the MPLS service packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, and thus can determine the MPLS service packet. IOAM package.

Application example three

FIG. 8 is a schematic diagram of implementing IOAM encapsulation by using LoopBack in an Ethernet network, and FIG. 9 is a schematic diagram of implementing IOAM encapsulation by using LinkTrace in an Ethernet network. In this application example, the IOAM ingress node and the IOAM transit node perform the following steps:

Step 31: The IOAM ingress node sends a LoopBack request message or a LinkTrace request message carrying the IOAM configuration request information.

Figure 10 is a format diagram of a LoopBack packet, and Figure 11 is a format diagram of a LinkTrace packet. As shown in Figure 10 and Figure 11, a LoopBack request packet or a LinkTrace request packet contains a set of TLVs, which is represented by adding a Type field. The IOAM configuration request new TLV can make the LoopBack request packet or the LinkTrace request packet carry the IOAM configuration request information.

Step 32: The IOAM transit node responds to the request and returns a LoopBack response packet or a LinkTrace response packet carrying the IOAM configuration information of the local node to the IOAM ingress node.

According to the LoopBack mechanism, the sending node can send the LoopBack request packet to each node on the transmission path in turn by changing the destination medium access control (MAC) address of the Ethernet header in the LoopBack request message. After receiving the loopback request message carrying the IOAM configuration request information, the IOAM transit node sends a loopback request message to the loopback request message sending node, that is, the IOAM ingress node, and the loopback response packet carrying the IOAM configuration information of the local node. The IOAM configuration information is written in the TLVs field of the LoopBack response message in the form of a TLV, and the TLV adopts the format shown in FIG.

According to the mechanism of LinkTrace, the sending node only needs to set the destination MAC address of the Ethernet header in the LinkTrace request message to a dedicated multicast address, so that the LinkTrace request message can reach each node in the transmission path in turn. After receiving the LinkTrace request packet carrying the IOAM configuration request information, the IOAM transit node requests the packet sending node, that is, the IOAM ingress node, to reply to the LinkTrace response packet carrying the IOAM configuration information of the local node. The IOAM configuration information is written into the TLVs field of the LinkTrace response message in the form of a TLV, and the TLV adopts the format shown in FIG.

Step 33: After the IOAM ingress node obtains the IOAM configuration of each node on the Ethernet service packet transmission path, the IOAM encapsulation is determined.

After the IOAM ingress node obtains the IOAM configuration of each node on the Ethernet service packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, and thus can determine the service packet for the Ethernet service. IOAM package.

12 is a schematic structural diagram of an apparatus for implementing an IOAM package according to an embodiment of the present disclosure. As shown in FIG. 12, the apparatus includes:

The sending unit 121 is configured to send a first out-of-band OAM message carrying the IOAM configuration request information, where the first out-of-band OAM message sequentially arrives at each node on the service data packet transmission path;

The receiving unit 122 is configured to receive a second out-of-band OAM message that carries the IOAM configuration information sent by the IOAM transmission node.

The encapsulating unit 123 is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.

In the embodiment of the present disclosure, the sending unit 121 is configured to: when the triggering operation of the network administrator is obtained, send the first out-of-band OAM message carrying the IOAM configuration request information; or, when obtaining the network management module or the control application When the command is triggered, the first out-of-band OAM packet carrying the IOAM configuration request information is sent; or when the service data packet is triggered, the first out-of-band OAM packet carrying the IOAM configuration request information is sent.

In the embodiment of the present disclosure, if the node that receives the first out-of-band OAM message is an IOAM transmission node, the receiving unit 122 receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information. Text.

In the embodiment of the present disclosure, the encapsulating unit 123 is configured to determine, according to the IOAM configuration information of each IOAM transmission node, an IOAM function option TLVs included in the IOAM data content, and a length of each IOAM function option TLV; according to the IOAM The function option TLVs and the length of each IOAM function option TLV are inserted into the IOAM header in the service data packet, that is, the IOAM encapsulation of the service data packet is implemented.

In the embodiment of the disclosure, when the service data packet transmission path is applicable to the IP network, the first out-of-band OAM packet and the second out-of-band OAM packet are ICMP packets.

When the service data packet transmission path is applicable to the MPLS network, the first out-of-band OAM packet and the second out-of-band OAM packet are LSP ping packets;

When the service data packet transmission path is applicable to the Ethernet network, the first out-of-band OAM packet and the second out-of-band OAM packet are LoopBack packets or LinkTrace packets.

Those skilled in the art should understand that the implementation functions of the units in the apparatus for implementing IOAM encapsulation shown in FIG. 12 can be understood by referring to the foregoing description of the method for implementing IOAM encapsulation. The functions of the units in the apparatus for implementing the IOAM package shown in FIG. 12 can be implemented by a program running on the processor, or can be realized by a specific logic circuit.

In practical applications, the functions implemented by each unit in the apparatus for implementing the IOAM package may be implemented by a central processing unit (CPU) or a microprocessor (MPU, Micro) located in a device implementing the IOAM package. Processor Unit), or digital signal processor (DSP, Digital Signal Processor), or Field Programmable Gate Array (FPGA).

Those skilled in the art will appreciate that embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Correspondingly, an embodiment of the present invention further provides a storage medium, wherein a computer program is configured, and the computer program is configured to perform the method for implementing IOAM encapsulation in the embodiment of the present invention.

The above description is only for the preferred embodiments of the present disclosure, and is not intended to limit the scope of the disclosure.

Industrial applicability

In the technical solution of the embodiment of the present disclosure, the IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path; The IOAM ingress node receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information. The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node. The method for realizing IOAM encapsulation by manually sending information at the IOAM ingress node in the related art increases the burden on the network administrator and is prone to error, and also enables the IOAM ingress node to support automatic acquisition of the IOAM under the trigger of the service traffic. Encapsulate the required information.

Claims

A method for implementing in-band operation management and maintenance IOAM encapsulation, the method comprising:

The IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;

Receiving, by the IOAM ingress node, a second out-of-band OAM packet that carries the IOAM configuration information sent by the IOAM transmission node;

The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
The method of claim 1 wherein

When the triggering operation of the network administrator is obtained, the IOAM ingress node sends a first out-of-band OAM packet carrying the IOAM configuration request information; or

When the triggering instruction of the network management module or the control application is obtained, the IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information; or

When the service data packet is triggered, the IOAM ingress node sends a first out-of-band OAM packet carrying the IOAM configuration request information.
The method according to claim 1, wherein the node on the service data message transmission path comprises at least one of: an IOAM transmission node, a non-IOAM transmission node, wherein the IOAM transmission node comprises an IOAM intermediate node and an IOAM Export node.
The method of claim 3, wherein the IOAM ingress node receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information, including:

And if the node that receives the first out-of-band OAM message is an IOAM transmission node, the IOAM ingress node receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information.
The method according to claim 1, wherein the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node, including:

The IOAM ingress node determines, according to the IOAM configuration information of each IOAM transmission node, the IOAM function option TLVs included in the IOAM data content, and the length of each IOAM function option TLV;

The IOAM header is inserted in the service data message according to the IOAM function option TLVs and the length of each IOAM function option TLV.
The method according to any one of claims 1 to 5, wherein

When the service data packet transmission path is applicable to the IP network, the first out-of-band OAM packet and the second out-of-band OAM packet are Internet Control Message Protocol (ICMP) packets;

When the service data packet transmission path is applicable to the multi-protocol label switching MPLS network, the first out-of-band OAM packet and the second out-of-band OAM packet are LSP ping packets.

When the service data packet transmission path is applicable to the Ethernet network, the first out-of-band OAM packet and the second out-of-band OAM packet are loopback loopback packets or link tracking LinkTrace packets.
An apparatus for implementing an IOAM package, the apparatus comprising:

The sending unit is configured to send the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;

a receiving unit, configured to receive a second out-of-band OAM message that carries the IOAM configuration information sent by the IOAM transmission node;

The encapsulating unit is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
The device according to claim 7, wherein the sending unit is configured to send a first out-of-band OAM message carrying the IOAM configuration request information when the triggering operation of the network administrator is obtained; or, when obtaining the network management module Or, when the triggering instruction of the application is controlled, the first out-of-band OAM packet carrying the IOAM configuration request information is sent; or when the service data packet is triggered, the first out-of-band OAM packet carrying the IOAM configuration request information is sent.
The apparatus according to claim 7, wherein the node on the traffic data message transmission path comprises at least one of: an IOAM transmission node, a non-IOAM transmission node, wherein the IOAM transmission node comprises an IOAM intermediate node and an IOAM Export node.
The apparatus according to claim 9, wherein if the node that receives the first out-of-band OAM message is an IOAM transmission node, the receiving unit receives a second that carries the IOAM configuration information sent by the IOAM transmission node. Out-of-band OAM message.
The apparatus according to claim 7, wherein the encapsulating unit is configured to determine, according to IOAM configuration information of each IOAM transmission node, IOAM function option TLVs included in the IOAM data content, and a length of each IOAM function option TLV; The IOAM header is inserted in the service data message according to the IOAM function option TLVs and the length of each IOAM function option TLV.
The apparatus according to any one of claims 7 to 11, wherein

When the service data packet transmission path is applicable to the IP network, the first out-of-band OAM packet and the second out-of-band OAM packet are ICMP packets;

When the service data packet transmission path is applicable to the MPLS network, the first out-of-band OAM packet and the second out-of-band OAM packet are LSP ping packets;

When the service data packet transmission path is applicable to the Ethernet network, the first out-of-band OAM packet and the second out-of-band OAM packet are LoopBack packets or LinkTrace packets.
A storage medium having stored therein computer executable instructions configured to perform the method of implementing in-band operation management and maintenance IOAM encapsulation of any one of claims 1 to 6.