WO2018188663A1 - Method and device for information notification - Google Patents

Abstract

A method and device for information notification. The method for information notification comprises: an in-band operations, administration and maintenance (IOAM) node utilizes an extended path computation unit communication protocol (PCEP) to package IOAM capability information, or, utilizes an extended PCEP-link state (LS) to package IOAM capability information, or, utilizes the OpenFlow protocol to package IOAM capability information; and transmits a PCEP message, a PCEP-LS packet, or an OpenFlow protocol message carrying the IOAM capability information to a predetermined node.

Description

Information notification method and device Technical field

The present disclosure relates to the field of communication technologies, for example, to an information notification method and apparatus.

Background technique

The Internet Engineering Task Force (IETF) proposes In-situ Operation Administration and Maintenance (IOAM), in which IOAM is also called in-band OAM. In-band OAM is sent along with data packets, and no additional control plane messages are required to send OAM data. In-band OAM is generally deployed in a specific domain. IOAM can implement complex OAM functions such as multiple path tracking, path verification, and Service-Level Agreement (SLA) authentication.

Depending on the deployment, in-band OAM can be used in different scenarios, such as Internet Protocol Version 6, IPV6, and Virtual Extensible LAN-Generic Protocol Extension (VXLAN-GPE). In the scenario of service function chain (SFC) and segment routing (SR). However, in an IOAM scenario, the IOAM function cannot be implemented through a node outside the IOAM domain.

Summary of the invention

The embodiment of the present application provides an information notification method and apparatus, so as to implement node information collected by a predetermined node to support an IOAM function in an IOAM domain.

An embodiment of the present application provides an information notification method, including:

The IOAM node encapsulates IOAM capability information using one of the following protocols: Extended Path Computation Unit Communication Protocol (PCEP), Extended PCEP-Link State (LS), or OpenFlow OpenFlow Protocol;

The IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message carrying the IOAM capability information to a predetermined node.

An embodiment of the present application provides an information notification method, including:

The predetermined node receives the PCEP message, the PCEP-LS message, or the OpenFlow protocol message sent by the IOAM node;

The predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.

An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, and includes:

The processing module is configured to encapsulate the IOAM capability information by using one of the following protocols: an extended PCEP, an extended PCEP-LS, or an OpenFlow protocol;

The sending module is configured to: send the PCEP message, the PCEP-LS message, or the OpenFlow protocol message that carries the IOAM capability information to the predetermined node.

The embodiment of the present application provides an information notification apparatus, which is applied to a predetermined node, and includes:

The receiving module is configured to: receive a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node;

The parsing module is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.

An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed Any one of the above information notification methods is implemented when the reader reads execution.

An embodiment of the present application provides an information notification apparatus, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is read and executed by the processor , to implement any of the above information notification methods.

In addition, the embodiment of the present application further provides a machine readable medium, where a computer program is stored thereon, and when the computer program is executed by the processor, any one of the foregoing information notification methods is implemented.

The embodiment of the present application further provides a machine readable medium storing a computer program, where the computer program is executed by a processor to implement any of the above information notification methods.

In the embodiment of the present application, the node information supporting the IOAM function in the IOAM domain is collected by extending the PCEP, the PCEP-LS, or the OpenFlow protocol, so that the node that collects the IOAM function in the IOAM domain is collected by the predetermined node.

DRAWINGS

FIG. 1 is a flowchart of an information notification method according to an embodiment of the present application;

2 is a flowchart of an information notification method according to another embodiment of the present application;

FIG. 3 is a network connection diagram according to an embodiment of the present application;

4 is a flowchart of an information notification method according to another embodiment of the present application;

FIG. 5 is a network connection diagram according to another embodiment of the present application;

FIG. 6 is a flowchart of an information notification method according to another embodiment of the present application;

FIG. 7 is a network connection diagram according to another embodiment of the present application;

FIG. 8 is a flowchart of an information notification method according to another embodiment of the present application;

FIG. 9 is a schematic diagram of a format of an IOAM capability type length value according to an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of a format of a path tracking subtype length value according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of a format of a path verification subtype length value according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of an information notification apparatus according to an embodiment of the present application;

FIG. 13 is a schematic diagram of an information notification apparatus according to another embodiment of the present application.

detailed description

The embodiments of the present application are described below with reference to the accompanying drawings, and the embodiments described below are intended to illustrate and explain the present application.

The steps illustrated in the flowchart of the figures may be executed in a computer system such as a set of computer executable instructions. Also, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

In the edge nodes of the IOAM domain, the edge node that embeds the OAM data packet in the data packet is also called the IOAM encapsulation node. The edge node that leaves the IOAM domain removes the OAM data packet. Decapsulate the node for the IOAM. In an embodiment, the path verification method of the IOAM is: embedding the OAM data packet in the data packet in the IOAM encapsulation node, and the IOAM forwarding node fills the relevant OAM information into the OAM data packet according to a certain algorithm. The IOAM decapsulation node replaces the OAM information in the OAM data packet with the IOAM forwarding node to check whether the path is consistent with the configured path and removes the OAM data packet. Here, the node that implements the path check may be completed by a predetermined node set outside the IOAM domain, for example, the external predetermined node completes the path check based on the complete in-band OAM data message.

As shown in FIG. 1 , an embodiment of the present application provides an information notification method, including:

Step 101: The IOAM node encapsulates the IOAM capability information by using an extended Path Computation Element Protocol (PCEP), or encapsulates the IOAM capability by using an extended PCEP-link-state (PCEP-LS). Information, or, encapsulates IOAM capability information using the OpenFlow protocol.

Step 102: The IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message that carries the IOAM capability information to the predetermined node. In this embodiment, the IOAM node may use the extended PCEP to encapsulate the IOAM capability information, and send the PCEP message carrying the IOAM capability information to the predetermined node; or the IOAM node may encapsulate the IOAM capability information by using the extended PCEP-LS, and will carry The PCEP-LS packet of the IOAM capability information is sent to the predetermined node. Alternatively, the IOAM node may encapsulate the IOAM capability information by using the OpenFlow protocol, and send an OpenFlow protocol message carrying the IOAM capability information to the predetermined node.

In an exemplary embodiment, the predetermined node may be a Path Computation Element (PCE) or a controller or a network management system in the network management system.

The PCE is an entity capable of computing and knowing the path between any nodes in an autonomous system (AS). It can be integrated inside the router or exist as a separate entity in the network. Can be integrated with the network management system. PCE is more aware of network traffic and path selection within the AS and can therefore be used for better path computation. The nodes in the IOAM domain can work as a Path Computation Client (PCC), so the PCEP can be extended to notify the PCE of its own supported IOAM capabilities.

The OpenFlow protocol is used to describe the criteria used for the interaction between the controller and the switch, as well as the interface standards for the controller and switch. The core part of the protocol is a collection of information structures for the OpenFlow protocol. The OpenFlow protocol can be run between the nodes and controllers in the IOAM domain. In some scenarios using the OpenFlow protocol, the OpenFlow protocol can be extended to perform IOAM capability advertisement in the IOAM domain.

In an exemplary embodiment, the IOAM node encapsulates the IOAM capability information by using the extended PCEP, and may include:

The IOAM node extends the Open message in the PCEP to carry IOAM capability information.

In an exemplary embodiment, the IOAM node encapsulates the IOAM capability information by using the extended PCEP-LS, and may include:

The IOAM node adds a PCEP-LS object (Object); the IOAM capability information is encapsulated by the added PCEP-LS object.

In an exemplary embodiment, the added PCEP-LS object may include at least one of: Node Descriptors Type Length Value (TLV), Prefix Descriptors TLV, and Link Description Link Descriptors TLV.

In an exemplary embodiment, the IOAM capability information may be carried by at least one of a Node Descriptor TLV, a Prefix Descriptor TLV, and a Link Descriptor TLV.

In an exemplary embodiment, the IOAM node encapsulates the IOAM capability information by using the OpenFlow protocol, and may include: the IOAM node encapsulates the IOAM capability information in a flow table function response (table feature reply) message.

In an exemplary embodiment, the IOAM node encapsulating the IOAM capability information in the table feature reply message may include: adding one or more IOAM matching fields in the table feature reply message, and specifying to match the one or more IOAM matching fields. Subsequent operations, such as modifying or adding new entries, may be used to modify or add IOAM data.

In an exemplary embodiment, the IOAM capability information may include the following information: a type of IOAM. In an exemplary embodiment, the types of IOAM include: path tracking, path verification, and end-to-end verification.

In an exemplary embodiment, the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.

As shown in FIG. 2, the embodiment of the present application provides an information notification method, including:

Step 201: The predetermined node receives a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node.

Step 202: The predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message. In an exemplary embodiment, the predetermined node may be a controller or a network manager in the PCE or network management system.

In an exemplary embodiment, the predetermined node may receive the PCEP message sent by the IOAM node, and parse the IOAM capability information advertised by the IOAM node from the PCEP message; or, the predetermined node receives the PCEP-LS message sent by the IOAM node, and from the PCEP - The LSAM capability information advertised by the IOAM node is parsed in the LS packet; or the predetermined node receives the OpenFlow protocol message sent by the IOAM node, and parses the IOAM capability information advertised by the IOAM node from the OpenFlow protocol message.

In an exemplary embodiment, the IOAM capability information may be carried by an Open message in the PCEP, or encapsulated in an added PCEP-LS object, or carried by a table feature reply message of the OpenFlow protocol.

In an exemplary embodiment, the added PCEP-LS object may include at least one of the following: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV.

In an exemplary embodiment, the IOAM capability information may be carried by at least one of a Node Descriptor TLV, a Prefix Descriptor TLV, and a Link Descriptor TLV.

In an exemplary embodiment, the IOAM capability information may include: a type of IOAM; in an exemplary embodiment, the types of the IOAM include: path tracking, path verification, and end-to-end verification.

In an exemplary embodiment, the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.

The application is described below by means of a plurality of embodiments.

Embodiment 1

In this embodiment, as shown in FIG. 3, the Bit Indexed Explicit Replication (BIER) domain is an IOAM domain, and all BIER nodes in FIG. 3 are also nodes supporting IOAM technology at the same time. As shown in FIG. 3, a BIER-Forwarding Ingress Router (BFIR) is also called an IOAM encapsulation node, and a BIER egress router (BFER) is also called an IOAM decapsulation node, and a BIER forwarding node (Bit forwarding Router). , BFR) is also called the intermediate IOAM forwarding node. As shown in Figure 3, the data message is sent from the BIER ingress node to the BIER egress node. In Figure 3, only the BIER Ingress Node (BFIR)/IOAM encapsulation node interacts with the PCE.

FIG. 4 is a flowchart of an information notification method according to the embodiment. Referring to FIG. 4, the method provided in this embodiment includes:

In step 301, the BIER ingress node carries the IOAM capability TLV through the extended PCEP-LS object, and notifies the PCE that it supports the IOAM capability.

In an exemplary embodiment, the IOAM capability information may be carried by an extension node descriptor TLV (NODE Descriptors TLV), a link descriptor TLV (Link Descriptors TLV), and a prefix descriptor TLV (Prefix Descriptors TLV).

In this embodiment, the detailed format of the IOAM capability TLV can be seen in FIG. 9. In FIG. 9, the Type field identifies the TLV as the IOAM capability type length value (IOAM-capability TLV); the Length field is the total length of the TLV; and the Option type field is the type of the IOAM. The IETF defines three types of IOAM types: in-suit OAM Tracing Option, in-suit OAM Proof of Transit Option, and In-situ OAM Edge-to-Edge Option. The Reserved field is a reserved field to be expanded.

Also, one or more option sub-TLVs (Option Sub-TLVs) are defined. The one or more option sub-TLVs may include an in-suit OAM Tracing Option Sub-TLV, an in-suit OAM Proof of Transit Option Sub-TLV, and an end-to-end In-situ OAM Edge-to-Edge Option Sub-TLV.

FIG. 10 is a schematic diagram of a format of a path tracking subtype length value. As shown in FIG. 10, the F byte is used to indicate the type of path tracking, and currently includes the following two types: Pre-allocated Trace Option and Incremental Trace Option.

Figure 11 is a schematic diagram of the format of the path verification subtype length value. As shown in FIG. 11, the path verification subtype length value is defined as the following three types: universal proof of Transit (universal POT), network service header metadata (NSH metadata) path verification, and Proof of Transit of Segment Routing (SR POT).

In this embodiment, only the IOAM encapsulation node/BIER ingress node interacts with the PCE. In other implementations, the nodes supporting the IOAM and BIER technologies in the IOAM and BIER domains may interact with the PCE, or the designated IOAM node may interact with the PCE. This application is not limited to this, and which nodes the PCE interacts with depends on the actual deployment.

In this embodiment, only the IOAM encapsulation node/BIER ingress node interacts with the PCE, and the BIER ingress node/IOAM encapsulation node collects the supported IOAM of the relevant node in the IOAM domain through the Interior Gateway Protocol (IGP). The ability is uniformly reported to the PCE.

Step 302: After receiving the PCEP-LS packet, the PCE analyzes which nodes support the IOAM capability.

Embodiment 2

In this embodiment, as shown in FIG. 5, the segment routing (SR) domain is an IOAM domain, and all the SR nodes in FIG. 5 are also nodes supporting the IOAM technology at the same time. All of the SR nodes in Figure 5 interact with the PCE. As shown in FIG. 5, the SR ingress node is also called an IOAM encapsulation node, the SR egress node is also called an IOAM decapsulation node, and the SR forwarding node is also called an intermediate IOAM forwarding node; as shown in FIG. 5, the data packet is sent from the SR ingress node. Go to the SR exit node.

FIG. 6 is a flowchart of an information notification method provided by this embodiment. As shown in FIG. 6, the process of this embodiment includes:

In step 401, the IOAM-related node (such as the node supporting both the SR technology and the IOAM technology in FIG. 5) sends an Open message carrying the IOAM Capability TLV to the PCE, indicating that the IOAM node supports the IOAM. Features.

Step 402: After receiving the extended Open message, the PCE parses to know which nodes support the IOAM capability.

Embodiment 3

In this embodiment, as shown in FIG. 7, the VXLAN domain is an IOAM domain, and all nodes supporting the VXLAN technology in FIG. 7 also support IOAM. In Figure 7, the VXLAN domain and the nodes in the IOAM domain that support VXLAN and IOAM technologies interact with the controller. As shown in Figure 7, Network Virtual Edge (NVE) is also called IOAM encapsulation node. NVE is also called IOAM decapsulation node. VXLAN forwarding node is also called intermediate IOAM forwarding node. As shown in Figure 7, data packet. From the IOAM encapsulation node to the IOAM decapsulation node.

FIG. 8 is a flowchart of an information notification method provided by this embodiment. As shown in FIG. 8, the process of this embodiment includes:

Step 501: The IOAM node sends a table feature reply message carrying the IOAM capability information to the controller, indicating that the IOAM node supports the IOAM function.

In an exemplary embodiment, one or more IOAM matching fields may be added in the table feature reply message, and at the same time, an operation performed after matching the IOAM matching field may be specified, and may be an operation of modifying or adding a new item.

After receiving the table feature reply message, the controller calculates the forwarding path of the IOAM node according to the IOAM capability information carried in the table feature reply message, and processes the IOAM capability information, and obtains the IOAM node forwarding path and the processed IOAM capability information. Send to the IOAM node.

After receiving the data packet carrying the IOAM packet, the IOAM node matches the IOAM header according to the IOAM node forwarding path and the IOAM capability information received from the controller, and then performs operations on the IOAM data, such as modifying or adding a new entry. And forward the data packet after the operation.

Step 502: After receiving the extended flow table function response message, the controller parses to know which nodes support the IOAM capability.

As shown in FIG. 12, an embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, and includes:

The processing module 901 is configured to: encapsulate the IOAM capability information by using the extended PCEP, or encapsulate the IOAM capability information by using the extended PCEP-LS, or encapsulate the IOAM capability information by using the OpenFlow protocol;

The sending module 902 is configured to: send a PCEP message, a PCEP-LS message, or an OpenFlow protocol message that carries the IOAM capability information to the predetermined node. In an exemplary embodiment, the processing module 901 may be configured to encapsulate the IOAM capability information with the extended PCEP by:

The Open message in the PCEP is extended to carry IOAM capability information.

In an exemplary embodiment, the processing module 901 may be configured to encapsulate the IOAM capability information with the extended PCEP-LS by:

Add a PCEP-LS object; encapsulate the IOAM capability information with the added PCEP-LS object;

In an exemplary embodiment, the added PCEP-LS object may include at least one of the following: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV.

In an exemplary embodiment, the processing module 901 may be configured to encapsulate the IOAM capability information by using the OpenFlow protocol in the following manner:

The IOAM capability information is encapsulated in a flow table function reply (table feature reply) message.

In an exemplary embodiment, the IOAM capability information may include the following information: a type of IOAM; in an exemplary embodiment, the types of the IOAM include: path tracking, path verification, and end-to-end verification.

In an exemplary embodiment, the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.

As shown in FIG. 13, the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, and includes:

The receiving module 1001 is configured to: receive a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node;

The parsing module 1002 is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.

In an exemplary embodiment, the IOAM capability information may be carried by an Open message in the PCEP, or encapsulated in an added PCEP-LS object, or carried by a table feature reply message of the OpenFlow protocol.

In an exemplary embodiment, the IOAM capability information may include: a type of IOAM. In an exemplary embodiment, the types of the IOAM include: path tracking, path verification, and end-to-end verification.

In an exemplary embodiment, the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.

For the description of the information notification device, reference may be made to the description of the foregoing method embodiments, and thus no further details are provided herein.

An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed The information notification method of the above IOAM node side is implemented when the reader reads and executes.

The embodiment of the present application further provides an information notification apparatus, which is applied to an IOAM node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information is used for information notification. When the program is read and executed by the processor, the following operations are performed:

The IOAM node encapsulates the IOAM capability information by using the extended PCEP, or encapsulates the IOAM capability information by using the extended PCEP-LS, or encapsulates the IOAM capability information by using the OpenFlow protocol; and transmits the PCEP message carrying the IOAM capability information and the PCEP-LS packet through the transmission module. The text or OpenFlow protocol message is sent to the predetermined node.

The processor may include, but is not limited to, a processing device such as a Microcontroller Unit (MCU) or a Field-Programmable Gate Array (FPGA).

The memory may be set as a software program and a module for storing application software, such as a program instruction/module corresponding to the information notification method of the present application, and the processor executes various function applications and data processing by running a software program and a module stored in the memory. That is, the above method is implemented. The memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory can further include memory remotely located relative to the processor, which can be connected to the IOAM node over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission module can be arranged to receive or transmit data via a network. In one example, the transmission module can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.

An embodiment of the present application provides an information notification apparatus, which is applied to a predetermined node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed When the device reads and executes, the information notification method on the predetermined node side described above is implemented.

The embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information notification is used When the program is read and executed by the processor, the following operations are performed:

The IOAM capability information advertised by the IOAM node is parsed from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.

The processor may include, but is not limited to, a processing device such as an MCU or an FPGA.

In an embodiment, the predetermined nodes described above may also include more or fewer components or have different configurations. The memory may be configured as a software program and a module for storing application software, such as a program instruction/module corresponding to the information notification method in the embodiment of the present application, and the processor executes various functional applications by running a software program and a module stored in the memory. And data processing, that is, to achieve the above method. The memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory can further include memory remotely located relative to the processor, the remote memory being connectable to the predetermined node over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission module can be arranged to receive or transmit data via a network. In one example, the transmission module can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.

In addition, the embodiment of the present application further provides a machine readable medium storing a computer program, where the computer program is executed by the processor to implement the above information notification method on the IOAM node side or the predetermined node side.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware (e.g., a processor), which may be stored in a machine readable medium, such as a read only memory, disk or optical disk. Computer readable storage medium. In an exemplary embodiment, 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 above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function. This application is not limited to any specific combination of hardware and software.

The embodiments disclosed in the present application are as described above, but the description is only for the purpose of understanding the present application, and is not intended to limit the present application.

Industrial applicability

The present disclosure collects node information that supports the IOAM function in the IOAM domain by extending the PCEP, PCEP-LS, or OpenFlow protocol, thereby implementing node information that the predetermined node collects to support the IOAM function in the IOAM domain.

Claims (21)

An information notification method, including: The in-band operation management and maintenance IOAM node encapsulates the IOAM capability information by using one of the following protocols: an extended path computation unit communication protocol PCEP, an extended PCEP-link state LS, or an OpenFlow OpenFlow protocol; The IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message carrying the IOAM capability information to a predetermined node. The method of claim 1, wherein the predetermined node is a path computation unit, a controller in a network management system, or a network management system in a network management system. The method of claim 1, wherein the IOAM node encapsulates IOAM capability information by using extended PCEP, including: The IOAM node extends an Open Open message in the PCEP to carry the IOAM capability information. The method of claim 1, wherein the IOAM node encapsulates IOAM capability information by using extended PCEP-LS, including: Adding a PCEP-LS object to the IOAM node; The IOAM capability information is encapsulated with the added PCEP-LS object. The method of claim 3, wherein the PCEP-LS object comprises at least one of: a node descriptor type length value TLV, a prefix descriptor TLV, and a link descriptor TLV; the IOAM capability information is at least One carries: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV. The method of claim 1, wherein the IOAM node encapsulates IOAM capability information by using an OpenFlow protocol, including: The IOAM node encapsulates the IOAM capability information in a flow table function response table feature reply message. The method of claim 6, wherein the IOAM node encapsulates the IOAM capability information in a table feature reply message, including: Adding one or more IOAM matching fields to the table feature reply message, and specifying an operation performed after matching the one or more IOAM matching fields. The method according to any one of claims 1 to 7, wherein the IOAM capability information comprises: a type of IOAM; wherein the types of the IOAM include: path tracking, path verification, and end-to-end verification. The method of claim 8, wherein the IOAM capability information further comprises at least one of: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype. An information notification method, including: The predetermined node receives the path calculation unit communication protocol PCEP message, the PCEP-link state LS message or the OpenFlow OpenFlow protocol message sent by the in-band operation management and maintenance IOAM node; The predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message. The method of claim 10, wherein the predetermined node is a path computation unit, a controller in a network management system, or a network management system in a network management system. The method according to claim 10, wherein the IOAM capability information is carried by an Open Open message in the PCEP, or encapsulated in an added PCEP-LS object, or the table function reply is responded by a flow table function of the OpenFlow protocol. The message is carried. The method of claim 12, wherein the PCEP-LS object comprises at least one of: a node descriptor type length value TLV, a prefix descriptor TLV, and a link descriptor TLV; the IOAM capability information is at least One carries: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV. The method according to any one of claims 10 to 13, wherein the IOAM capability information comprises: a type of IOAM; wherein the types of the IOAM include: path tracking, path verification, and end-to-end verification. The method of claim 14, wherein the IOAM capability information further comprises at least one of: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype. An information notification device is applied to an in-band operation management and maintenance IOAM node, including: The processing module is configured to encapsulate the IOAM capability information by using one of the following protocols: an extended path computation unit communication protocol PCEP, an extended PCEP-link state LS, or an OpenFlow OpenFlow protocol; The sending module is configured to: send the PCEP message, the PCEP-LS message, or the OpenFlow protocol message that carries the IOAM capability information to the predetermined node. An information notification device is applied to a predetermined node, including: The receiving module is configured to: receive a path calculation unit communication protocol PCEP message, a PCEP-link state LS message, or an OpenFlow OpenFlow protocol message sent by the in-band operation management and maintenance IOAM node; The parsing module is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message. An information notification apparatus for in-band operation management and maintenance of an IOAM node, comprising: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed The information notifying method according to any one of claims 1 to 9 is implemented when the reading is performed. An information notifying apparatus, applied to a predetermined node, comprising: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is executed by the processor The information notification method according to any one of claims 10 to 15. A machine readable medium having stored thereon a computer program, the computer program being executed by a processor to implement the information notification method according to any one of claims 1 to 9. A machine readable medium having stored thereon a computer program, the computer program being executed by a processor to implement the information notification method according to any one of claims 10 to 15.

Images