WO2018188464A1

WO2018188464A1 - Methods and devices for realizing ioam, and storage medium

Info

Publication number: WO2018188464A1
Application number: PCT/CN2018/079956
Authority: WO
Inventors: 胡方伟
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-04-13
Filing date: 2018-03-22
Publication date: 2018-10-18
Also published as: CN108737128A; CN108737128B

Abstract

Disclosed in the embodiment of the present invention is a method for realizing IOAM. The method comprises: extending IOAM capability information of a routing protocol-carrying device; and encapsulating the IOAM capability information in a routing protocol packet and sending same in a network. Further disclosed are a device for realizing IOAM and another method and device for realizing IOAM.

Description

Method, device and storage medium for realizing IOAM

Cross-reference to related applications

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

Technical field

The present invention relates to an OAM (Operations, Administration and Maintenance) technology, and more particularly to a method and apparatus for implementing in-band operation management and maintenance IOAM.

Background technique

IOAM (in-suit OAM, in-band OAM, in-band operation management and maintenance). In-band operation management and maintenance refers to directly encapsulating the OAM information and data to be carried in user data packets. Send together without sending additional control plane messages to send OAM data. IOAM can implement a variety of network fault detection functions, including path consistency detection, POT (intermediate transport node verification), SLA (Service-Level Agreement) and other complex OAM functions.

In the edge node of the IOAM domain, the IOAM data packet is embedded in the data packet, so the node is also called the IOAM encapsulation node, and the edge node leaving the IOAM domain removes the OAM data packet, which is also called the IOAM solution. Encapsulate the node. The path verification method of the IOAM is: in the encapsulated node of the IOAM domain, the IOAM data packet is embedded in the data packet, and the IOAM forwarding node fills the relevant OAM information into the OAM data according to a certain algorithm, and the IOAM decapsulation node is based on Whether the OAM information verification path filled in by the forwarding node is consistent with the configured path and the OAM data packet is removed.

Depending on the deployment, in-band OAM can be used in different scenarios, such as segment routing networks. Segment routing is a method based on source address routing through existing MPLS (Multiprotocol Label Switching) networks. The packet header or the IPv6 packet header carries a segment routing header (Segment Routing Header), and the segment routing packet header carries a series of indication operations (also called segment operations) for routing data in the network. transmission. Segment routing makes it easy to implement network load balancing and process engineering, as well as complex network functions such as fast rerouting. The segment operation indication can also be extended to implement a service or topology-based routing indication, and the segment routing can also implement service-based network virtualization. However, the existing segment routing network can only implement simple OAM functions such as layered service provider (LSP) ping and tracert (tracking routing), but cannot implement in-band OAM path verification and end-to-end logical path accessibility. Complex OAM functions such as detection.

However, in the existing technical solutions and IOAM technologies, the capability announcement of the IOAM node cannot be realized.

Summary of the invention

An embodiment of the present invention provides a method and apparatus for implementing in-band operation management and maintenance of an IOAM and a computer storage medium to implement notification of IOAM capabilities.

An embodiment of the present invention provides a method for implementing an IOAM, where the method includes:

The extended routing protocol carries the IOAM capability information of the device;

The IOAM capability information is encapsulated in a routing protocol message and sent in the network.

An embodiment of the present invention provides an apparatus for implementing an IOAM, including:

An extension module configured to extend IOAM capability information of the routing protocol carrying device;

The sending module is configured to encapsulate the IOAM capability information in a routing protocol packet and send the information in the network.

An embodiment of the present invention further provides an apparatus for implementing an IOAM, where the apparatus includes a memory and a processor, where

The memory stores executable instructions;

The processor, when executing the executable instructions stored by the memory, performs at least the following operations:

The extended routing protocol carries the in-band operation management and maintenance IOAM capability information of the device; the IOAM capability information is encapsulated in the routing protocol packet and sent in the network.

An embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the foregoing method for implementing IOAM.

An embodiment of the present invention further provides a method for implementing an IOAM, where the method includes:

Receiving a routing protocol packet, and parsing the IOAM capability information carried in the routing protocol packet;

After receiving the user data packet, the corresponding IOAM data is encapsulated according to the IOAM capability information.

An embodiment of the present invention further provides an apparatus for implementing an IOAM, where the apparatus includes:

The parsing module is configured to receive the routing protocol packet and parse the IOAM capability information carried in the routing protocol packet;

The encapsulating module is configured to encapsulate the corresponding IOAM data according to the IOAM capability information after receiving the user data packet.

The memory stores executable instructions;

After receiving the routing protocol packet, the IOAM capability information carried in the routing protocol packet is parsed; after receiving the user data packet, the corresponding IOAM data is encapsulated according to the IOAM capability information.

In summary, the method and device for implementing IOAM and the storage medium provided by the embodiments of the present invention, the IOAM node can advertise its IOAM capability and IOAM attribute information in the network, enhance the robustness of the network, and improve the operation and maintenance management capability of the network.

DRAWINGS

The drawings are intended to provide a further understanding of the invention, and are intended to be a In the drawing:

1 is a flowchart of a method for implementing an IOAM according to Embodiment 1 of the present invention;

2 is a schematic diagram of an ISIS routing capability TLV format according to an embodiment of the present invention;

3 is a schematic diagram of an IOAM capability sub-TLV format according to an embodiment of the present invention;

4 is a schematic diagram of an in-band OAM path option sub-sub-TLV format according to an embodiment of the present invention;

5 is a schematic diagram of an in-band OAM path verification option sub-sub-TLV format according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an apparatus for implementing an IOAM according to Embodiment 2 of the present invention; FIG.

FIG. 7 is a flowchart of a method for implementing an IOAM according to Embodiment 3 of the present invention;

FIG. 8 is a schematic diagram of an IOAM encapsulation of a segment routing network according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic diagram of an apparatus for implementing an IOAM according to Embodiment 4 of the present invention; FIG.

FIG. 10 is a structural diagram of a routing protocol advertisement IOAM capability attribute network according to an embodiment of the present invention.

FIG. 11 is a flowchart of forwarding a segment routing data packet carrying an IOAM according to an embodiment of the present invention.

detailed description

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

Embodiment 1

FIG. 1 is a flowchart of a method for implementing an IOAM according to an embodiment of the present invention. As shown in FIG. 1 , the method in this embodiment includes:

Step 11: The IOAM capability information of the extended routing protocol carrying device;

Step 12: The IOAM capability information is encapsulated in a routing protocol packet and sent in the network.

In an embodiment, the extended routing protocol carries the IOAM capability information of the device, including: when the routing protocol is an ISIS (Intermediate System-to-Intermediate System) protocol, the IS-IS routing capability is extended. TLV (type, length, value, type length value) carries the IOAM capability sub-TLV information of the IOAM capability attribute;

In an embodiment, the extended routing protocol carries the IOAM capability information of the device, including:

When the routing protocol is an OSPF (Open Shortest Path First) protocol, the OSPF RI Opaque LSA (Link-State Advertisement) is extended to carry the IOAM capability sub-TLV information of the IOAM capability attribute.

The IOAM capability includes one or more of the following: an in-suit OAM Tracing Option, an in-suit OAM Proof of Transit Option, and an In-situ OAM. Edge-to-Edge Option (option for in-band OAM end-to-end).

Specifically, the segment routing based segment routing encapsulation includes: an identifier bit, a flag field, a random number, an accumulated number, and the like.

The IETF (Internet Engineer Task Force) standard RFC 4971 defines a TLV structure called ISIS Routing Capability TLV (Intermediate System to Intermediate System Router Capability TLV), as shown in Figure 2, which is used in the TLV. The capability attributes of the router are advertised, such as the TE (Traffic Engineering) node capability description, the PCED (Path Computation Unit Database), and the like. The embodiment of the present invention requires the router to advertise its IOAM capability attribute, so that the ISIS routing capability TLV can be extended. Added support for IOAM capability sub-TLV. When the ISIS router advertises its capability attribute, it carries the IOAM capability sub-TLV and floods the segment routing network. When other ISIS routers receive the advertisement, it can determine that the ISIS route supports IOAM capability and IOAM attributes. Parameter information.

For the OSPF protocol, OSPFv2Router Information (Routing Information, RI) Opaque (opaque) LSA and OSPFv3RI opaque LSA are defined in the IETF (Internet Engineering Task Force) standard RFC 4970, which are used for OSPFv2 protocol and OSPFv3 advertisement respectively. Its router capability attribute information.

The IOAM capability attribute information of the router in the embodiment of the present invention extends the OSPFv2 routing information opaque LSA and the OSPFv3 routing information opaque LSA to carry the IOAM capability sub-TLV. When the OSPF router advertises the capability attribute to the neighbor, the OSPFv2 route information opaque LSA or the OSPFv3 route information opaque LSA fills the IOAM capability sub-TLV, and the encapsulated LSA advertises the OSPF link state advertisement packet flooding the network. After receiving the link state advertisement packet, the neighbor can determine the IOAM data processing capability and the supported IOAM type by using the encapsulated IOAM capability.

The format of the IOAM capability sub-TLV proposed by the embodiment of the present invention is as shown in FIG. 3, and the descriptions of the respective fields are as follows:

The Type field identifies the sub-TLV as an IOAM capability sub-TLV;

The Length field is the total length of the sub-TLV;

The Option field is the type of IOAM, and the three types defined by the IETF are: in-band OAM path option, in-band OAM path verification option, and in-band OAM end-to-end option;

Reserved field, reserved field, to be extended.

And define one or more option sub-TLVs, which can have in-band OAM path option sub-TLV, in-band OAM path verification sub-TLV and in-band OAM end-to-end authentication option sub-TLV;

Reserved field, reserved field.

Figure 4 is a schematic diagram of the format of the in-band OAM path option sub-sub-TLV. The F byte is used to indicate the type of path tracking. There are currently two types: Pre-allocated Trace Option and Incremental Trace Option. Incremental tracking option).

Figure 5 is a schematic diagram of the format of the in-band OAM path verification option sub-sub-TLV. Currently, three types, general POT, NSH (Network Service Host) metadata and SR POT are defined.

In the above solution, the IOAM node can advertise its IOAM capability and IOAM attribute information in the network, enhance the robustness of the network, and improve the operation and maintenance management capability of the network.

The embodiment of the present invention further provides a computer (readable) storage medium storing computer executable instructions, and the computer executable instructions are implemented by the processor to implement the foregoing method for implementing IOAM. The storage medium includes volatile random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk (CD-ROM), Digital versatile disc (DVD) or other medium that is accessed.

Embodiment 2

Figure 6 is a schematic diagram of an apparatus for implementing an IOAM according to an embodiment of the present invention. As shown in Figure 6, the apparatus of this embodiment includes:

The expansion module 601 is configured to extend IOAM capability information of the routing protocol carrying device;

The sending module 603 is configured to encapsulate the IOAM capability information in a routing protocol packet and send the information in the network.

In an embodiment, the extension module 601, the IOAM capability information of the extended routing protocol carrying device includes: when the routing protocol is an intermediate system to an intermediate system ISIS protocol, the extended ISIS routing capability type length value TLV carries an IOAM capability attribute. IOAM capability sub-TLV information.

In an embodiment, the extension module 601, the extended routing protocol carries the IOAM capability information of the device, including: when the routing protocol is the open shortest path first OSPF protocol, the extended OSPF routing information opaque link state LSA advertisement carries the IOAM IOAM capability sub-TLV information for capability attributes.

The IOAM capability information includes one or more of the following: an in-band OAM path option, an in-band OAM path verification option, and an in-band OAM end-to-end verification option.

An embodiment of the present invention further provides an apparatus for implementing an IOAM, including a memory and a processor, where

The memory stores (the first set of) executable instructions;

The processor, when executing the (first set) executable instructions stored by the memory, performs at least the following operations:

An apparatus for implementing an IOAM in this embodiment may be a router, or may be a broadband access server, a switch, or the like.

Embodiment 3

FIG. 7 is a flowchart of a method for implementing an IOAM according to an embodiment of the present invention. As shown in FIG. 7, the method in this embodiment includes:

Step 21: Receive a routing protocol packet, and parse the IOAM capability information carried in the routing protocol packet.

Step 22: After receiving the user data packet, the corresponding IOAM data is encapsulated according to the IOAM capability information.

In an embodiment, when the network is an SR network, the embodiment of the present invention proposes to use the specific MPLS (Multi-Protocol Label Switching) label value to identify the carried IOAM data of the segment routing message, after the MPLS label. Encapsulating the IOAM data.

FIG. 8 is a format diagram of an IOAM supporting an MPLS label as an SR data plane encapsulation POT type according to an embodiment of the present invention, and each field is described as follows:

Label: MPLS label field, which identifies that the SR carries IOAM data. The tag needs to be assigned a specific value by the Internet Assigned Numbers Authority (IANA);

COS: priority identifier;

S: The bottom label of the stack. When carrying IOAM data, this field is set to 1, indicating that the label is the lowest layer label;

TTL: Time to Live, used to encode the lifetime value. Similar to the TTL value function in the IP (Internet Protocol) packet, it also provides an anti-ring mechanism.

Type: indicates that the IOAM data of the POT type is carried, and the value needs to be allocated by the IANA;

Length: The value is 18, indicating the length of the IOAM data (excluding Label, COS, S, TTL fields);

RESERVED: 8bits, reserved field, cleared to 0 when sent, ignored when receiving;

F: flag bit, 1 bit, indicating which POT-profiles are active, 0 means that the even POT-profile is active, and 1 means that the odd POT-profile is active;

Flags: flag field, not defined yet;

Random: 64-bit random number;

Cumulative: a 64-bit accumulated number that is updated on each node of the path to be verified;

If the data plane of the SR network is IPv6, the IOAM POT parameter is carried in the optional Type Length Value object of the SRH (Segment Routing Header) in the form of a POT sub-TLV.

Embodiment 4

FIG. 9 is a schematic diagram of an apparatus for implementing an IOAM according to an embodiment of the present invention. As shown in FIG. 9, the apparatus of this embodiment includes:

The parsing module 901 is configured to receive the routing protocol packet and parse the IOAM capability information carried in the routing protocol packet.

The encapsulating module 903 is configured to encapsulate the corresponding IOAM data according to the IOAM capability information after receiving the user data packet.

In an embodiment, the encapsulating module 903, according to the IOAM capability information, encapsulating the corresponding IOAM data, includes: using a multi-protocol label switching label, the user data packet carries IOAM data, and the multi-protocol label switching The IOAM data is encapsulated after the tag.

The memory stores (the second set of) executable instructions;

The processor is configured to execute the (second set) executable instructions stored by the memory, and at least perform the following operations:

The embodiment of the present invention provides that the method for implementing the IOAM can be used not only for the segment routing network but also for other SFCs, VXLAN (Virtual eXtensible Local Area Network)-GPE (Generic Protocol Extension for VXLAN). Extensions and other technologies and protocols that support ISIS or OSPF routing protocol advertisements. Because their methods of extension are the same as those in the segment routing network, they are not explained here. The subsequent embodiments are also described in detail by taking a segment routing network as an example.

Embodiment 5

Embodiments of the present invention describe a detailed flow of advertising IOAM capability attributes using the ISIS protocol.

In Figure 10, I is an ingress SR node, which is responsible for the encapsulation of SR packets. E is an egress (egress) node, decapsulating the segment routing packets, and A, B, C, and D are intermediate transmission SR nodes. Responsible for the transmission of SR messages.

When the SR node encapsulates a link state packet data unit (LSPDU), the ISIS routing capability TLV is encapsulated, where the ISIS routing capability TLV carries the IOAM capability sub-TLV proposed by the embodiment of the present invention, and the SR After the LSPDU is encapsulated, the node floods the segment routing domain by using the ISIS flooding mechanism. When the neighboring SR router of the SR node in the SR domain receives the LDPDU, it can judge according to the carried IOAM capability sub-TLV. The SR router supports the IOAM capability.

In an optional embodiment below:

The detailed flow of the OSPF protocol advertised IOAM capability attribute in the embodiment of the present invention is still illustrated by using FIG. 10 as an example.

If the IGP (Interior Gateway Protocol) supported by the SR network is an OSPFv2 protocol, the OSPFv2 routing information opaque LSA needs to be encapsulated in the LSA of the OSPFv2 routing information. IOAM capability TLV. If the IGP protocol supported by the SR network is the OSPFv3 protocol, the segment routing node encapsulates the OSPFv3 routing information opaque LSA when the LSA packet is encapsulated. The OSPFv3 routing information opaque LSA carries the IOAM capability TLV proposed by the embodiment of the present invention.

Regardless of whether the SR network supports OSPFv2 or OSPFv3, the SR node uses the OSPF flooding mechanism to flood the SR domain. After the neighboring SR router of the SR node in the SR domain receives the LSA packet, it can carry it. The IOAM capability TLV determines that the segment routing node supports IOAM capabilities.

In an optional embodiment below:

This embodiment describes the process of forwarding a segment routing message carrying IOAM data according to an embodiment of the present invention.

As shown in FIG. 10, I is an SR node, E is an Egress SR node, and A, B, C, M, O, and P are SR network intermediate transmission SR nodes. The packet is encapsulated on the I node, and the SR message is decapsulated on the E node. The intermediate transmission SR node performs packet transmission according to the SID indication encapsulated in the packet. In Figure 8, the path that the service wants to go is I-A-B-O-P-E, where the Node B is assigned the prefix SID B, the O node is assigned the neighbor SID O, the E node is assigned the prefix SID E, and the IOAM data is encapsulated on the ingress node I. The forwarding process of packet encapsulation is as follows:

In step S101, after receiving the packet P, the ingress SR router 1 encapsulates the segment routing message. According to the needs of the service, the ingress node I encapsulates the SID E, the SID O, and the SID B respectively. Since the IOAM POT data needs to be encapsulated, the SID is in the SID. After the list is encapsulated with a specific MPLS label, the Label Y identifier carries the IOAM data, and then encapsulates the IOAM packet behind the MPLS label.

Step S102, the ingress SR router 1 sends the encapsulated SR message to the network, and the intermediate node A forwards the packet to the SR node B according to the SID B encapsulated in the packet;

Step S103, after receiving the packet, the SR node B removes the outer SID B encapsulation, processes and updates the IOAM data, re-encapsulates the IOAM packet, and then forwards the packet to the node O;

Step S104, after receiving the packet, the node O removes the outer SID O encapsulation, and processes and updates the IOAM data, and then re-encapsulates the IOAM packet and forwards it to the node P;

Step S105, the intermediate transit node P updates the IOAM data, and sends the packet to the node E according to the SID E encapsulated in the packet;

Step S106: After receiving the packet, the SR node E decapsulates the SR message, finds that the IOAM data is carried, decapsulates the IOAM data, and processes the IOAM data.

The IOAM capability notification method and the data forwarding process in the embodiment of the present invention are described in detail in the embodiment of the present invention. The IOAM capability advertisement in the embodiment of the present invention may also be applied to other networks, such as SFC, IPv6, and VXLAN- GPE and other networks that support ISIS/OSPF to advertise node attributes and capabilities are not elaborated here.

The embodiment of the present invention further provides a computer (readable) storage medium storing (computer) executable instructions, and the computer executable instructions are implemented by the processor to implement the foregoing method for implementing IOAM.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

The above is only a preferred embodiment of the present invention, and of course, the present invention may be embodied in various other embodiments without departing from the spirit and scope of the invention. Corresponding changes and modifications are intended to be included within the scope of the appended claims.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can 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 invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. 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.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

In the embodiment of the present invention, the extended routing protocol carries the IOAM capability information of the device; the IOAM capability information is encapsulated in the routing protocol packet, and is sent in the network. Therefore, the IOAM node can advertise its IOAM capability and IOAM attribute information in the network, which can greatly enhance the robustness of the network and improve the operation and maintenance management capability of the network.

Claims

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

The extended routing protocol carries the IOAM capability information of the device;

The IOAM capability information is encapsulated in a routing protocol message and sent in the network.
The method of claim 1, wherein the extended routing protocol carries IOAM capability information of the device, including:

When the routing protocol is an intermediate system to the intermediate system ISIS protocol, the extended ISIS routing capability type length value TLV carries the IOAM capability sub-TLV information of the IOAM capability attribute.
The method of claim 1, wherein the extended routing protocol carries IOAM capability information of the device, including:

When the routing protocol is the open shortest path first OSPF protocol, the extended OSPF routing information opaque link state LSA advertises the IOAM capability sub-TLV information carrying the IOAM capability attribute.
The method according to any one of claims 1 to 3, wherein the IOAM capability information comprises one or more of the following:

In-band OAM path option, in-band OAM path verification option, in-band OAM end-to-end authentication option.
A method according to any one of claims 1 to 3, wherein the network comprises any of the following networks:

Segment routing network, business function chain network, sixth edition network of Internet Protocol, virtual scalable local area network.
An apparatus for implementing in-band operation management and maintenance of an IOAM, the apparatus comprising:

An extension module configured to extend IOAM capability information of the routing protocol carrying device;

The sending module is configured to encapsulate the IOAM capability information in a routing protocol packet and send the information in the network.
The apparatus of claim 6 wherein

The expansion module, configured to extend the IOAM capability information of the routing protocol carrying device, includes: when the routing protocol is an intermediate system to the intermediate system ISIS protocol, the extended ISIS routing capability type length value TLV carries the IOAM capability sub-TLV information of the IOAM capability attribute. .
The apparatus of claim 6 wherein

The expansion module is configured to extend the IOAM capability information of the routing protocol carrying device, including: when the routing protocol is an open shortest path first OSPF protocol, the OSPF routing information opaque link state LSA is advertised to carry the IOAM capability of the IOAM capability attribute. Sub-TLV information.
The apparatus according to any one of claims 6 to 8, wherein

The IOAM capability information includes one or more of the following: an in-band OAM path option, an in-band OAM path verification option, and an in-band OAM end-to-end authentication option.
An apparatus for implementing in-band operation management and maintenance of an IOAM, the apparatus comprising a memory and a processor, wherein

The memory stores executable instructions;

The processor, when executing the executable instructions stored by the memory, may perform at least the following operations:

The extended routing protocol carries the in-band operation management and maintenance IOAM capability information of the device; the IOAM capability information is encapsulated in the routing protocol packet and sent in the network.
A method for implementing in-band operation management and maintenance IOAM, the method comprising:

Receiving a routing protocol packet, and parsing the IOAM capability information carried in the routing protocol packet;

After receiving the user data packet, the corresponding IOAM data is encapsulated according to the IOAM capability information.
The method of claim 11, wherein the encapsulating the corresponding IOAM data according to the IOAM capability information comprises:

The multi-protocol label switching label is used to identify that the user data packet carries IOAM data, and the IOAM data is encapsulated after the multi-protocol label switching label.
An apparatus for implementing in-band operation management and maintenance of an IOAM, the apparatus comprising:

The parsing module is configured to receive the routing protocol packet and parse the IOAM capability information carried in the routing protocol packet;

The encapsulating module is configured to encapsulate the corresponding IOAM data according to the IOAM capability information after receiving the user data packet.
The device of claim 13 wherein

The encapsulating module, configured to encapsulate the corresponding IOAM data according to the IOAM capability information, includes: using a multi-protocol label switching label, the user data packet carries IOAM data, and the multi-protocol label switching label is encapsulated IOAM data.
An apparatus for implementing in-band operation management and maintenance of an IOAM, the apparatus comprising a memory and a processor; wherein

The memory stores executable instructions;

The processor, when executing the executable instructions stored by the memory, performs at least the following operations:

After receiving the routing protocol packet, the IOAM capability information carried in the routing protocol packet is parsed; after receiving the user data packet, the corresponding IOAM data is encapsulated according to the IOAM capability information.
A computer storage medium having stored therein computer executable instructions for performing the method of implementing IOAM of any one of claims 1 to 5.
A computer storage medium having stored therein computer executable instructions for performing the method of implementing IOAM of claim 11 or 12.