WO2019165803A1

WO2019165803A1 - Message processing method and apparatus, and message encapsulating method, apparatus and system

Info

Publication number: WO2019165803A1
Application number: PCT/CN2018/116212
Authority: WO
Inventors: 罗鉴; 肖敏
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-03-01
Filing date: 2018-11-19
Publication date: 2019-09-06
Also published as: CN110224916A; CN110224916B

Abstract

A message encapsulating method, comprising: an encapsulation node adding address information of the encapsulation node to an in-band operations, administration, and maintenance (IOAM) message, and sending the IOAM message to a transmission node (S402); the encapsulation node receiving fault notification information sent by the transmission node, and stopping encapsulating the IOAM message according to the fault notification information (S404); and the encapsulation node receiving recovery notification information sent by the transmission node, and recovering encapsulation of a new IOAM message according to the recovery notification information (S406).

Description

Message processing method, device and message encapsulation method, device and system

Technical field

The present disclosure relates to, but is not limited to, the field of communications, and in particular, to a packet processing method, apparatus, and packet encapsulation method, apparatus, and system.

Background technique

In-band Operations, Administration, and Maintenance (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 working on standardization in the Internet Engineering Task Force (IETF) of the International Organization for Standardization.

IETF's IOAM series of proposals draft-brockners-inband-oam-requirements, draft-brockners-inband-oam-transport and draft-ietf-ippm-ioam-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 a service datagram. A part of the text 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 the out-of-band OAM, the IOAM can implement functions that cannot be implemented by the out-of-band OAM, such as detecting the network node through which the service data packet actually passes, verifying that the transmission path of the service data packet is consistent with the expected, and giving the service datagram. The serial number information is added to detect packet loss and out-of-order. Accordingly, in order to implement the above functions, the network administrator can configure the transit node, and the transport node needs to be the IOAM data content on the packet transmission path except the encapsulation node. The node to be processed.

The IOAM encapsulation operation is to insert the IOAM header into the service data packet. The encapsulation node is the node that performs the IOAM encapsulation operation. The encapsulation node can be a network node such as a switch or a router, or a terminal node such as a personal computer or a server. 1 is a format diagram of a related art IOAM header. As shown in FIG. 1, an IOAM header is used in addition to a location for indicating IOAM data content (ie, an IOAM header indication in FIG. 1) and a length (ie, in FIG. 1). The IOAM header length) also carries a set of IOAM function option types/lengths/values (TLVs) as IOAM data content, where each IOAM function option TLV corresponds to an IOAM function and carries The data needed to complete the IOAM function. Since the encapsulation node needs to complete the insertion of the IOAM header, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, which can be determined by the network administrator according to the configuration on each transmission node. The acknowledgment and delivery to the encapsulating node may also be obtained by the encapsulating node from each of the transmitting nodes by sending an outband OAM message, or may also be obtained by the encapsulating node by sending an IOAM configuration request message from the centralized configuration point.

In some cases, after determining the content of the IOAM data, the encapsulating node encapsulates the service data packet into an IOAM packet and transmits it in the network according to the IOAM data content. However, once the network fails, the transmission path of the IOAM packet changes, that is, the transmission node on the IOAM packet transmission path changes, and the IOAM data content determined by the encapsulation node is no longer applicable. However, in the case where the transmission path caused by the above network failure changes, how the encapsulation node encapsulates the IOAM message does not provide a more effective solution.

Summary of invention

The embodiments of the present disclosure provide a packet processing method, a device, and a packet encapsulation method, apparatus, and system, so as to avoid, at least in some cases, a transmission path of an in-band operation management and maintenance IOAM packet occurs due to a fault or the like. When the change occurs, the resulting IOAM packet encapsulation is no longer applicable.

The embodiment of the present disclosure provides a method for processing a packet, including: receiving, by the transmitting node, an in-band operation management and maintenance IOAM message, and saving an address of the encapsulating node in the IOAM packet; and detecting, by the transit node, the current network In the case of a failure, the failure notification information is sent to the encapsulation node, wherein the failure notification information is generated by the transmission node according to an address saved in the transmission node, to indicate that the encapsulation node stops encapsulating the The information of the IOAM message is sent to the encapsulating node after the protection node completes the protection switching or the route re-convergence; wherein the recovery notification information is saved by the transmission node according to the transmission node. The information generated by the address is used to instruct the encapsulating node to recover the encapsulated new IOAM message.

The embodiment of the present disclosure further provides a packet encapsulation method, including: the encapsulating node adds the address information of the encapsulation node in an in-band operation management and maintenance IOAM message, and sends the IOAM message to the transmission node; The encapsulating node receives the failure notification information sent by the transmission node, and stops encapsulating the IOAM message according to the failure notification information; the encapsulating node receives the recovery notification information sent by the transmission node, and recovers according to the recovery notification information. Encapsulating a new IOAM message; wherein the failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.

The embodiment of the present disclosure further provides a packet processing apparatus, including: a receiving module, configured to receive an in-band operation management and maintenance IOAM message, and save an address of the encapsulated node in the IOAM message; And configured to send, to the encapsulating node, fault notification information, where the fault notification information is generated by the transmitting node according to an address saved in the transmitting node, to indicate the The encapsulating node stops encapsulating the information of the IOAM packet; the second sending module is configured to send the recovery notification information to the encapsulating node after completing the protection switching or the route re-convergence; wherein the recovery notification information is the transmission The information generated by the node according to the address saved in the transit node is used to instruct the encapsulating node to recover the encapsulated new IOAM message.

The embodiment of the present disclosure further provides a packet encapsulating apparatus, including: a sending module, configured to add address information of the encapsulating node in an in-band operation management and maintenance IOAM message, and send the IOAM report to a transmitting node. The first receiving module is configured to receive the fault notification information sent by the transmitting node, and stop encapsulating the IOAM packet according to the fault notification information; and the second receiving module is configured to receive the recovery sent by the transmitting node by the encapsulating node. And notifying the information, and recovering the encapsulated new IOAM message according to the recovery notification information; wherein the failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.

The embodiment of the present disclosure further provides a packet encapsulation system, including a transmission node and an encapsulation node, where the transmission node is configured to receive an in-band operation management and maintenance IOAM message sent by the encapsulation node and save the Decoding an address of the node in the IOAM packet, and sending a failure notification message to the encapsulating node after detecting that the current network is faulty, and sending the recovery to the encapsulating node after completing the protection switching or the route re-convergence a notification information, the encapsulating node is configured to add the address information of the encapsulating node to the IOAM packet, and send the IOAM packet to the transmitting node; and receive the fault notification information sent by the transmitting node And stopping to encapsulate the IOAM message according to the fault notification information, and receiving the recovery notification information sent by the transmission node, and recovering the encapsulated new IOAM message according to the recovery notification information.

The embodiment of the present disclosure further provides a storage medium including a stored program, wherein the program runs the method of processing the message according to any one of the above items.

The embodiment of the present disclosure further provides another storage medium, where the storage medium includes a stored program, wherein the program is executed to perform a method of encapsulating the message according to any one of the above items.

Embodiments of the present disclosure also provide a processor configured to execute a program, wherein the program is operative to perform a method of processing the message of any of the above.

The embodiment of the present disclosure further provides a processor, the processor being configured to run a program, wherein the program is executed to perform a method of encapsulating the message according to any one of the above items.

BRIEF abstract

Figure 1 is a format diagram of an IOAM header in an existing IETF standard;

2 is a block diagram showing a hardware structure of a terminal for processing a message according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a method for processing a message according to an embodiment of the present disclosure; FIG.

4 is a flowchart of a method for encapsulating a message according to an embodiment of the present disclosure;

FIG. 5 is a structural block diagram of a method for encapsulating an IOAM message in an Internet Protocol (IP) network according to an embodiment of the present disclosure;

6 is a format diagram of an ICMP message according to an embodiment of the present disclosure;

7 is a structural block diagram of a method for encapsulating an IOAM message in a Multi-Protocol Label Switching (MPLS) network according to an embodiment of the present disclosure;

FIG. 8 is a format diagram of an LSP Ping message according to an embodiment of the present disclosure;

FIG. 9 is a structural block diagram of a method for encapsulating an IOAM message based on an Ethernet network according to an embodiment of the present disclosure;

FIG. 10 is a format diagram of an Ethernet OAM message according to an embodiment of the present disclosure;

11 is a structural block diagram of a processing apparatus for a message according to an embodiment of the present disclosure;

FIG. 12 is a structural block diagram of a packet encapsulating apparatus according to an embodiment of the present disclosure; FIG.

FIG. 13 is a structural block diagram of a package encapsulation system according to an embodiment of the present disclosure.

Detailed

Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

It may be noted that the terms "first", "second" and the like are used herein to distinguish similar objects, and are not necessarily used to describe a particular order or order.

First embodiment

The method embodiments provided by the first embodiment of the present disclosure may be executed in a mobile terminal, a computer terminal, or the like. Taking a mobile terminal as an example, FIG. 2 is a hardware structural block diagram of a terminal for processing a message according to an embodiment of the present disclosure. As shown in FIG. 2, terminal 10 may include one or more (only one shown) processor 202 (processor 202 may include, but is not limited to, a Micro Controller Unit (Micro Controller Unit) or may A processing device such as a Field Programmable Gate Array (FPGA), a memory 204 provided to store data, and a transfer device 206 configured to implement a communication function. It will be understood by those skilled in the art that the structure shown in FIG. 2 is merely illustrative and does not limit the structure of the above electronic device. For example, terminal 20 may also include more or fewer components than those shown in FIG. 2, or have a different configuration than that shown in FIG. 2.

The memory 204 may be configured as a software program and a module for storing application software, such as program instructions/modules corresponding to the processing method of the message in the embodiment of the present disclosure, and the processor 202 may be configured to run the software program stored in the memory 204 and The module, thus performing various functional applications and data processing, implements the above method. Memory 204 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, memory 204 may also include memory remotely located relative to processor 202, which may be connected to terminal 20 over a network. Examples of such networks may include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

Transmission device 206 can be arranged to receive or transmit data via a network. The network optional examples described above may include a wireless network provided by a communication provider of terminal 20. In one example, the transmission device 206 can include a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet. In one example, the transmission device 206 can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.

It can be noted that the encapsulation method of the message described in the following embodiments is also applicable to the hardware structure block diagram of the terminal shown in FIG. 2, and the optional implementation method is similar to the above description, and is not Do more than enough.

In this embodiment, a method for processing a packet running on the terminal 20 is provided. FIG. 3 is a flowchart of a method for processing a packet according to an embodiment of the present disclosure. As shown in FIG. 3, the process may be Including the following steps:

Step S302, the transmitting node receives the in-band operation management and maintenance IOAM message, and saves the address of the encapsulating node in the IOAM message;

Optionally, the transmitting node can receive the IOAM message in a learning manner.

Optionally, the IOAM packet formed by the encapsulating node after adding the IOAM header to the service data packet may arrive at each node in the packet transmission path, and when the node that receives the IOAM packet is the transit node, the transit node You can learn and save the encapsulation node address carried in the IOAM header.

After the receiving node receives the IOAM packet and saves the address of the encapsulating node in the IOAM packet, the transmitting node may further include: determining, by the transmitting node, whether a new one that includes the saving is received within a preset aging time The IOAM message of the address; if the judgment result is no, the transmission node may delete the saved address.

Optionally, in order to save the resource space of the transmission node and unnecessary resource waste, an aging mechanism is also introduced in the transmission node. That is, the transit node can periodically detect the address saved by the IOAM packet. When it is detected that a new message can be received among the addresses saved by the transmission node during the aging time, the transmission node may not delete the saved address. When it is detected that a new packet cannot be received in the address saved by the transmission node during the aging time, in order to save the resource space of the transmission node, the transmission node may delete the saved address. After the new IOAM packet is received, the address of the encapsulated node in the new IOAM packet is saved.

Step S304, in the case that the transmitting node detects that the current network is faulty, sending fault notification information to the encapsulating node, where the fault notification information is generated by the transmitting node according to an address saved in the transit node. Information for instructing the encapsulating node to stop encapsulating the IOAM message;

Since the IOAM data content is associated with the transmission path of the IOAM message, once the transmission path of the IOAM message fails, the content of the IOAM data contained in the IOAM header inserted by the encapsulating node into the service data message is no longer applicable. The encapsulation node can immediately stop the IOAM encapsulation operation.

Optionally, the fault notification information is set in a type and a code value that are not specified in the specified packet, and the specified packet includes at least one of the following: an Internet Control Message Protocol (ICMP) Packets, Label Switching Path Ping (LSP Ping) packets, and Ethernet OAM packets.

Optionally, the fault notification information carries a set of destination addresses, where the destination address is used to indicate that the transmission path of the service data packet destined for the destination address is faulty.

Alternatively, the node capable of performing the operation described in step S304 is a node whose transmission path has failed. For example, there are five transmission nodes A to E in the current network, and only A and D detect the failure of transmitting the transmission path between the transmission nodes A and D, then only A or D is possible to perform the operation in step S304. Operation, while other transmission nodes that do not detect the failure can also learn and message IOAM messages. However, the failure notification information will not be sent.

Optionally, in the IP network, the fault notification information may be transmitted in the form of an Internet Control Message Protocol (ICMP) message. At the same time, it can be set in the type and code value that are not specified in the ICMP message. For example, the specification type 21 code 0 indicates a path failure notification. In the MPLS network, the label switching path can be used to echo the LSP ping packet as the path fault notification information. Also set in the type and code value that is not specified in the ICMP message. For example, fixed message type 3 represents a path failure notification. At the same time, Ethernet OAM packets can be managed and maintained in the Ethernet Ethernet network as path fault notification information. At the same time, it can be set in the type and code value that are not specified in the Ethernet OAM message. For example, the operation code 56 represents a path failure notification.

In addition, in order to more accurately enable the encapsulation node to quickly obtain the location where the failure occurs, the failure notification information may also carry a set of destination addresses. The destination address may be used to indicate that the transmission path of the service data packet destined for the destination address is faulty. Therefore, after receiving the foregoing field, the encapsulating node may stop the encapsulation of the IOAM packet of the path corresponding to the service flow packet of the field, and the encapsulation of the IOAM packet corresponding to the other service flow packet may not be encapsulated. Subject to any influence. For example, if a failure of the transmission path is transmitted between the transmission nodes A and D, then a set of destination addresses transmitted by the encapsulation node are the transmission node A and the D address. Therefore, after the encapsulated node receives the destination address, it can be known that the path between the transit nodes A and D has failed. Therefore, when the IOAM is encapsulated, the encapsulation of the path between the transfer nodes A and D can be stopped. Other transmission paths can be received without any impact. This not only avoids the possibility of mispacking, but also clearly reflects the link failure.

Step S306, after the protection node completes protection switching or route re-convergence, sends recovery notification information to the encapsulation node, where the recovery notification information is generated by the transmission node according to an address saved in the transmission node. The information is used to instruct the encapsulating node to recover a new IOAM message.

Similarly, the node capable of performing the operation recited in step S306 may be a node whose transmission path has failed. For example, there are five transmission nodes A to E in the current network, wherein only A and D detect a failure of transmitting a transmission path between the transmission nodes A and D, then only A or D is possible to perform step S306. The operation in the middle, on the basis of not considering the specific connection relationship, only A or D is possible to perform the operation in step S306, and other transmission nodes that have not failed can realize the learning of the IOAM message. Message, but may not send recovery notification information.

Optionally, in the IP network, the fault notification information may be transmitted in the form of an Internet Control Message Protocol (ICMP) message. At the same time, it can be set in the type and code value that are not specified in the ICMP message. For example, the specification type 21 code 1 indicates a path failure notification. In the MPLS network, the label switching path can be used to echo the LSP ping packet as the path recovery notification information. At the same time, it can be set in the type and code value that are not specified in the ICMP message. For example, fixed message type 4 represents a path recovery notification. At the same time, Ethernet OAM packets can be managed and maintained in the Ethernet Ethernet network as path fault notification information. It can also be set in the type and code value that is not specified in the Ethernet OAM message. For example, the operation code 60 indicates a path recovery notification.

Optionally, the sending, to the encapsulating node, the resuming notification information, further comprising: instructing the encapsulating node to acquire the IOAM data content in the new IOAM packet; and instructing the encapsulating node to perform, according to the IOAM data content, Encapsulating the new IOAM message. The IOAM data content may include at least: IOAM data content associated with the new path.

Optionally, the recovery notification information is set in a type and code value that is not specified in the specified message.

Through the above steps, the IOAM packet encapsulation is no longer applicable due to the change of the transmission path of the in-band operation management and maintenance IOAM packet, so that the IOAM packet can be adjusted in time when the transmission path of the IOAM packet changes. Encapsulation of the text enhances the efficiency of IOAM packet encapsulation and the scope of application.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on such understanding, the technical solution of the embodiments of the present disclosure may be embodied in the form of a software product in essence or in some cases, and the computer software product is stored in a storage medium (such as ROM/RAM, disk). The optical disc includes a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method described in the embodiments of the present disclosure.

Second embodiment

In this embodiment, a method for encapsulating a packet running in the terminal 20 is provided. FIG. 4 is a flowchart of a method for encapsulating a packet according to an embodiment of the present disclosure. As shown in FIG. 4, the process may be Including the following steps:

Step S402, the encapsulating node adds the address information of the encapsulating node to the in-band operation management and maintenance IOAM message, and sends the IOAM message to the transmitting node.

Optionally, compared with the IOAM packet in some cases, the address information of the encapsulation node is added to the header in the IOAM packet described in this embodiment. Optionally, the address information includes two types of address type information of the encapsulation node and an encapsulation node address. The former, that is, the address type information is used to identify which type of address the encapsulating node uses, such as Media Access Control (MAC) address, IP version 4 (IPv4) address, and IP version 6 (IPv6). Address, or other addressable address. The address type is determined, and the length of the address is also determined. The latter, that is, encapsulating the node address, is used by the transmitting node to use the address to send protocol information to the encapsulating node.

Optionally, the address information of the encapsulation node includes at least one of the following: address type information of the encapsulation node and an address used to indicate that the transmission node sends information to the encapsulation node.

Step S404, the encapsulating node receives the failure notification information sent by the transmission node, and stops encapsulating the IOAM message according to the failure notification information.

Optionally, the encapsulating node receives the fault notification information sent by the transit node, and carries a set of destination addresses, and stops encapsulating the IOAM packets destined for the set of destination addresses according to the fault notification information.

Step S406, the encapsulating node receives the recovery notification information sent by the transit node, and recovers the encapsulated new IOAM packet according to the recovery notification information.

Optionally, when the IOAM packet is encapsulated according to the recovery notification information, the encapsulating node may first extract the IOAM data content corresponding to the restored transmission path from the packet sent by the transit node. Optionally, path information of the restored transmission path is included in the IOAM data content.

The failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.

Optionally, the encapsulating the new IOAM message according to the recovery notification information includes: the encapsulating node acquiring the IOAM data content in the new IOAM message; the encapsulating node is configured according to the IOAM data content The new IOAM message is encapsulated. The IOAM data content may include at least: IOAM data content associated with the new path.

It can be noted that the technical solutions described in the first embodiment and the second embodiment are better understood. In the present embodiment, the following scenarios are also provided in order to understand the technical solutions described in the above embodiments.

scene 1:

FIG. 5 is a structural block diagram of a method for encapsulating an IOAM message based on an IP network according to an embodiment of the present disclosure. Optionally, the encapsulation node and the transit node may perform the following operations:

In step 11, the encapsulation node 11 adds the IPv4 address of the encapsulation node 11 to the IOAM header when the IOAM encapsulation operation is performed. After receiving the IOAM packet encapsulated by the encapsulation node 11, the transit node 14 learns and saves the IPv4 address of the encapsulation node 11. When the IOAM encapsulation operation is performed, the encapsulation node 12 adds the IPv4 address of the encapsulation node 12 to the IOAM header. After receiving the IOAM packet encapsulated by the encapsulation node 12, the transit node 14 learns and saves the IPv4 address of the encapsulation node 12.

The transit node 14 ages the learned IPv4 address of the encapsulation node 11 and the IPv4 address of the encapsulation node 12 according to the default or configured aging time.

Step 12: After detecting the network failure between the node and the transmission node 15, the transmission node 14 sends the path failure notification information to the encapsulation node 11 and the encapsulation node 12 respectively. After the encapsulation node 11 and the encapsulation node 12 receive the path failure notification information, Stop the IOAM encapsulation operation separately.

An ICMP packet can be used as the path fault notification information in the IP network. FIG. 6 is a format diagram of an ICMP packet according to an embodiment of the present disclosure. As shown in FIG. 6, the ICMP packet includes an 8-bit type field and 8 The bit code field, which has been specified by the IETF standard, for example, type 8 code 0 indicates an ICMP Ping request, type 0 code 0 indicates an ICMP Ping response, and type 10 code 0 indicates a router request. , type 9 code 0 indicates router notification, and so on. By defining a type and a code value that have not been specified, for example, specifying that the type 21 code 0 indicates a path failure notification, the ICMP message can be made as a path failure notification information.

In order to achieve more precise control, the path failure notification information sent by the transmission node 14 may also carry service flow information in the option data field to indicate which service flows are affected by the network failure. For example, the option data field may include a group that needs to be forwarded to The IP prefix of the transport node 15. After receiving the path failure notification information carrying the service flow information, the encapsulating node 11 and the encapsulating node 12 may stop only the IOAM encapsulation operation for these service flows, and other service flows (for example, the traffic flow to the transit node 21 through the transit node 14) ) can be unaffected.

Step 13: After the protection node 14 completes the protection switching or the route re-convergence, the transmission node 14 and the encapsulation node 12 respectively send path recovery notification information, and the encapsulation node 11 and the encapsulation node 12 respectively receive the path recovery notification information, respectively triggering the acquisition and the new The path is associated with the IOAM data content and restores the IOAM encapsulation operation after acquiring the new IOAM data content.

Similar to the path failure notification information, the ICMP message can be used as the path recovery notification information in the IP network. By defining the type and code value that have not been specified yet, for example, the type 22 code 0 indicates the path recovery notification, and the ICMP can be made. The message serves as a path recovery notification message.

After the transmission node 14 completes the protection switching or the route re-convergence, the transmission path of the IOAM message to the transmission node 17 changes, and the transmission node 14, the transmission node 15, and the transmission node 16 become the transmission node 14, the transmission node 18, After receiving the path recovery notification information sent by the transmission node 14, the transmission node 19, the transmission node 20, the transmission node 16, the encapsulation node 11, and the encapsulation node 12 respectively trigger the acquisition of the IOAM data content associated with the new path, and acquire a new IOAM. The IOAM encapsulation operation is resumed after the data content.

Scene 2:

FIG. 7 is a structural block diagram of a method for encapsulating an IOAM message based on an MPLS network according to an embodiment of the present disclosure. Optionally, the encapsulating node and the transmitting node may perform the following steps:

Step 21: The encapsulation node 21 adds the IPv4 address of the encapsulation node 21 to the IOAM header when the IOAM encapsulation operation is performed. After receiving the IOAM packet encapsulated by the encapsulation node 21, the transit node 24 learns and saves the IPv4 address of the encapsulation node 21. When the IOAM encapsulation operation is performed, the encapsulation node 22 adds the IPv4 address of the encapsulation node 22 to the IOAM header. After receiving the IOAM packet encapsulated by the encapsulation node 22, the transit node 24 learns and saves the IPv4 address of the encapsulation node 22.

The transit node 24 may age the learned IPv4 address of the encapsulation node 21 and the IPv4 address of the encapsulation node 22 according to the default or configured aging time.

Step 22: After detecting the network failure between the transmission node and the transmission node 25, the transmission node 24 sends the path failure notification information to the encapsulation node 21 and the encapsulation node 22 respectively, and after the encapsulation node 21 and the encapsulation node 22 receive the path failure notification information, Stop the IOAM encapsulation operation separately.

The MPLS network can use the label switching path to display the LSP ping packet as the path fault notification information. FIG. 8 is a format diagram of an LSP ping packet according to an embodiment of the present disclosure. The LSP ping header may contain an 8-bit Message Type field. The IETF standard has already specified two values for the field, namely, message type 1 indicates an MPLS echo request, and message type 2 indicates MPLS echo response. By defining a message type that has not been specified, for example, specifying that the message type 3 indicates a path failure notification, the LSP ping packet can be used as the path failure notification information.

In order to achieve more precise control, the path failure notification information sent by the transmission node 24 may also carry service flow information in the TLVs field, indicating which service flows are affected by the network failure. For example, the TLVs field may include a group that needs to be forwarded to the transmission node. 25 IP prefix. After the encapsulating node 21 and the encapsulating node 22 receive the path failure notification information carrying the service flow information, only the IOAM encapsulation operation for the service flows may be stopped, and other service flows (for example, the traffic flow to the transit node 31 through the transit node 24) ) can be unaffected.

Step 23: After the protection node 24 completes the protection switching or the route re-convergence, the path recovery notification information is sent to the encapsulating node 21 and the encapsulating node 22 respectively, and the encapsulating node 21 and the encapsulating node 22 respectively receive the path recovery notification information, respectively triggering the acquisition and the new The path is associated with the IOAM data content and restores the IOAM encapsulation operation after acquiring the new IOAM data content.

Similar to the path fault notification information, the LSP ping packet can be used as the path recovery notification information in the MPLS network. The LSP ping packet can be made by defining the type of the message that has not been specified. As the path recovery notification information.

After the transmission node 24 completes the protection switching or the route re-convergence, the transmission path of the IOAM message to the transmission node 27 changes, and the transmission node 24, the transmission node 25, and the transmission node 26 become the transmission node 24 and the transmission node 28, After receiving the path restoration notification information sent by the transmission node 24, the transmission node 29, the transmission node 30, the transmission node 26, the encapsulation node 21, and the encapsulation node 22 respectively trigger the acquisition of the IOAM data content associated with the new path, and acquire a new IOAM. The IOAM encapsulation operation is resumed after the data content.

Scene 3:

FIG. 9 is a structural block diagram of a method for encapsulating an IOAM message based on an Ethernet network according to an embodiment of the present disclosure. Optionally, the encapsulating node and the transmitting node may perform the following steps:

In step 31, the encapsulating node 31 adds the MAC address of the encapsulating node 31 to the IOAM header when the IOAM encapsulation operation is performed. After receiving the IOAM packet encapsulated by the encapsulating node 31, the transmitting node 34 learns and saves the MAC address of the encapsulating node 31. When the IOAM encapsulation operation is performed, the encapsulation node 32 adds the MAC address of the encapsulation node 32 to the IOAM header. After receiving the IOAM packet encapsulated by the encapsulation node 32, the transit node 34 learns and saves the MAC address of the encapsulation node 32.

The transit node 34 may age the MAC address of the learned encapsulation node 31 and the MAC address of the encapsulation node 32 according to the default or configured aging time.

Step 32: After detecting the network fault between the node and the transmitting node 35, the transmitting node 34 sends the path fault notification information to the encapsulating node 31 and the encapsulating node 32 respectively. After the encapsulating node 31 and the encapsulating node 32 receive the path fault notification information, Stop the IOAM encapsulation operation separately.

The Ethernet network can be used to manage and maintain the Ethernet OAM packet as the path fault notification information. FIG. 10 is a format diagram of an Ethernet OAM packet according to an embodiment of the present disclosure, as shown in FIG. 10, an Ethernet OAM packet. The Ethernet OAM header may contain an 8-bit opcode (OpCode) field, and some values of the field have been specified by the IETF standard. For example, the operation code 1 indicates a connectivity detection message, and the operation code 2 indicates a loopback response. The message, opcode 3 represents a loopback request message, and so on. By defining the operation code that has not been specified, for example, the operation code 56 indicates the path failure notification, the Ethernet OAM message can be used as the path failure notification information.

In order to achieve more precise control, the path failure notification information sent by the transmission node 34 may also carry service flow information in the TLVs field, indicating which service flows are affected by the network failure. For example, the TLVs field may include a group that needs to be forwarded to the transmission node. 35 destination MAC address. After the encapsulating node 31 and the encapsulating node 32 receive the path failure notification information carrying the service flow information, only the IOAM encapsulation operation for the service flows may be stopped, and other service flows (for example, the traffic flow to the transit node 41 through the transit node 34) ) can be unaffected.

Step 33: After the protection node 34 completes the protection switching or the route re-convergence, the transmission node 34 sends the path recovery notification information to the encapsulating node 31 and the encapsulating node 32 respectively. After receiving the path recovery notification information, the encapsulating node 31 and the encapsulating node 32 respectively trigger the acquisition and the new The path is associated with the IOAM data content and restores the IOAM encapsulation operation after acquiring the new IOAM data content.

Similar to the path fault notification information, the Ethernet OAM packet can be used as the path recovery notification information in the Ethernet network. By defining the type of the message that has not been specified yet, for example, the type 57 indicates the path recovery notification, so that the Ethernet OAM packet can be made. As the path recovery notification information.

After the transmission node 34 completes the protection switching or the route re-convergence, the transmission path of the IOAM message to the transmission node 37 changes, and the transmission node 34, the transmission node 35, and the transmission node 36 become the transmission node 34 and the transmission node 38. After receiving the path restoration notification information sent by the transmission node 34, the transmission node 39, the transmission node 40, the transmission node 36, the encapsulation node 31, and the encapsulation node 32 respectively trigger the acquisition of the IOAM data content associated with the new path, and acquire a new IOAM. The IOAM encapsulation operation is resumed after the data content.

Third embodiment

In this embodiment, a device for processing a message is provided, and the device is configured to implement the foregoing embodiments and optional embodiments, and details are not described herein. As used hereinafter, the term "module" may implement software, hardware, or a combination of software and hardware for a predetermined function. Although the devices described in the following embodiments are optionally implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

11 is a structural block diagram of a message processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 11, the apparatus may include: a receiving module 1102, configured to receive an in-band operation management and maintenance IOAM message, and save the An address of the encapsulating node in the IOAM packet; the first sending module 1104 is configured to send, to the encapsulating node, fault notification information, where the current network is faulty, where the fault notification information is the transit node And the second sending module 1106 is configured to: after the protection switching or the route re-convergence, the encapsulation is performed, according to the information saved by the address saved in the transmitting node, where the encapsulating node stops encapsulating the IOAM message; The node sends the recovery notification information, where the recovery notification information is information generated by the transmitting node according to the address saved in the transmission node, used to instruct the encapsulating node to restore the encapsulated new IOAM message.

Optionally, the processing device of the packet further includes: a determining module, configured to determine whether a new IOAM packet including the saved address is received within a preset aging time; if the determination result is negative The transport node deletes the saved address.

Fourth embodiment

In this embodiment, a packet encapsulation device is further provided, and the device is configured to implement the foregoing embodiments and optional implementation manners, and details are not described herein. As used hereinafter, the term "module" may implement software, hardware or a combination of software and hardware for a predetermined function. Although the devices described in the following embodiments are optionally implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 12 is a structural block diagram of a packet encapsulating apparatus according to an embodiment of the present disclosure. As shown in FIG. 12, the apparatus may include: a sending module 1202, configured to add the in-band operation management and maintenance IOAM message. Encapsulating the address information of the node, and sending the IOAM packet to the transmitting node; the first receiving module 1204 is configured to receive the fault notification information sent by the transmitting node, and stop encapsulating the IOAM packet according to the fault notification information; The second receiving module 1206 is configured to receive, by the encapsulating node, the recovery notification information sent by the transmission node, and recover the encapsulated new IOAM message according to the recovery notification information; the failure notification information and the recovery notification information are the transmission The information generated by the node according to the address saved in the transit node.

Fifth embodiment

In this embodiment, a packet encapsulation system is further provided, and the system is configured to implement the foregoing embodiments and optional implementation manners, and details have been omitted for description.

FIG. 13 is a structural block diagram of a packet encapsulation system according to an embodiment of the present disclosure. As shown in FIG. 13, the system may include a transmission node 1302 and a transmission node 1304.

The transmitting node 1302 is configured to receive an in-band operation management and maintenance IOAM message sent by the encapsulating node, save an address of the encapsulating node in the IOAM packet, and send the encapsulation to the encapsulation if the current network is detected to be faulty. The node sends the failure notification information, and after the protection switching or the route re-convergence is completed, the recovery notification information is sent to the encapsulating node; the encapsulating node 1304 is configured to add the address information of the encapsulating node to the IOAM packet, and Sending the IOAM message to the transmitting node; receiving the fault notification information sent by the transmitting node, stopping the encapsulation of the IOAM message according to the fault notification information, and receiving the recovery notification sent by the transmitting node And recovering the encapsulated new IOAM message according to the recovery notification information; wherein the failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.

Sixth embodiment

An embodiment of the present disclosure further provides a storage medium, where the storage medium includes a stored program, wherein the program may perform the processing method of the message according to any one of the above items when the program is running.

Optionally, in this embodiment, the foregoing storage medium may be configured to store program code for performing the following steps: S1, the transmitting node receives the in-band operation management and maintenance IOAM message, and saves the encapsulation in the IOAM message. An address of the node; S2, in the case that the transmitting node detects that the current network is faulty, sending fault notification information to the encapsulating node, where the fault notification information is that the transmitting node saves according to the transmitting node The information generated by the address is used to indicate that the encapsulating node stops encapsulating the IOAM message; S3, after the protection node completes the protection switching or the route re-convergence, sends the recovery notification information to the encapsulating node; The recovery notification information is information generated by the transmitting node according to the address saved in the transmission node, used to instruct the encapsulating node to recover the encapsulated new IOAM message.

Optionally, in the embodiment, the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM). A variety of media that can store program code, such as a hard disk, a disk, or an optical disk.

Embodiments of the present disclosure also provide a processor configured to execute a program, wherein the program can execute the steps of any of the above methods when executed.

Optionally, in this embodiment, the foregoing procedure is used to perform the following steps: S1, the transmitting node receives the in-band operation management and maintenance IOAM message, and saves the address of the encapsulating node in the IOAM packet; S2, in the Transmitting, by the transmitting node, the fault notification information to the encapsulating node, where the fault notification information is generated by the transmitting node according to an address saved in the transit node, The encapsulating node stops the encapsulation of the information of the IOAM packet; S3, after the protection node completes the protection switching or the route re-convergence, sends the recovery notification information to the encapsulating node; wherein the recovery notification information is the transit node Generating information for instructing the encapsulating node to recover a new IOAM message according to the address saved in the transit node.

Seventh embodiment

The embodiment of the present disclosure further provides a storage medium, where the storage medium includes a stored program, wherein the program may perform the encapsulation method of the message according to any one of the above items.

Optionally, in this embodiment, the foregoing storage medium may be configured to store program code for performing the following steps: S1, the encapsulating node adds the address information of the encapsulation node in an in-band operation management and maintenance IOAM message, And sending the IOAM message to the transmitting node; S2, the encapsulating node receives the fault notification information sent by the transmitting node, and stops encapsulating the IOAM packet according to the fault notification information; S3, the encapsulating node receives Recovering the notification information sent by the node, and recovering the encapsulated new IOAM message according to the recovery notification information; wherein the failure notification information and the recovery notification information are addresses that are saved by the transmission node according to the transmission node Generated information.

Optionally, in this embodiment, the foregoing procedure is used to perform the following steps: S1: The encapsulating node adds the address information of the encapsulating node to the in-band operation management and maintenance IOAM message, and sends the IOAM report to the transmitting node. S2, the encapsulating node receives the failure notification information sent by the transmission node, and stops encapsulating the IOAM message according to the failure notification information; S3, the encapsulating node receives the recovery notification information sent by the transmission node, and And recovering the encapsulated new IOAM message according to the recovery notification information; wherein the failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.

For an alternative example in this embodiment, reference may be made to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

According to the embodiment of the present disclosure, the transmission node can generate the corresponding notification information according to the address information of the encapsulation node, in the case that the transmission path fails and the path is restored, so that the encapsulation path can perform the corresponding encapsulation operation according to the notified information. . Therefore, it is possible to prevent the IOAM packet encapsulation from being changed due to the change of the transmission path of the in-band operation management and maintenance IOAM packet, so that the IOAM packet can be adjusted in time when the transmission path of the IOAM packet changes. Encapsulation enhances the efficiency and scope of IOAM packet encapsulation.

Those skilled in the art will appreciate that the above-described modules or steps of the present disclosure may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices, optionally They may be implemented by program code executable by the computing device such that they may be stored in the storage device for execution by the computing device and, in some cases, may be performed in a different order than that illustrated herein. Or the steps described, either as separate circuit modules, or as a single integrated circuit module. As such, implementations of the embodiments of the present disclosure are not limited to any particular combination of hardware and software.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks/units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components work together. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media. Computer storage media include, but are not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), and Electrically Erasable Programmable Read-only Memory (EEPROM). Flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, disk storage or other magnetic storage device, or Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .

A person skilled in the art can understand that the technical solutions of the present disclosure may be modified or equivalent, without departing from the spirit and scope of the present disclosure, and should be included in the scope of the claims of the present disclosure.

Claims

A method for processing a message, comprising:

The transmitting node receives the in-band operation management and maintenance IOAM message, and saves the address of the encapsulation node in the IOAM message;

And sending, to the encapsulating node, failure notification information, where the transmission node detects that the current network is faulty, where the failure notification information is generated by the transmission node according to an address saved in the transmission node. Instructing the encapsulating node to stop encapsulating the information of the IOAM packet;

After the protection node completes protection switching or route re-convergence, sending, to the encapsulating node, recovery notification information, where the recovery notification information is generated by the transmitting node according to an address saved in the transmission node. The encapsulating node recovers information for encapsulating new IOAM messages.
The method according to claim 1, wherein after the transmitting node receives the IOAM message and saves the address of the encapsulating node in the IOAM message, the method includes:

Determining, by the transmitting node, whether a new IOMAM message including the saved address is received within a preset aging time;

In the case where the determination result is no, the transmission node deletes the saved address.
The method according to claim 1 or 2, wherein the sending the recovery notification information to the encapsulating node further comprises:

Instructing the encapsulating node to acquire IOAM data content in the new IOAM message, where the IOAM data content includes: IOAM data content associated with the new path;

Instructing the encapsulating node to encapsulate the new IOAM message according to the content of the IOAM data.
The method according to any one of claims 1 to 3, wherein the failure notification information is set in an unspecified type and code value in a specified message, the specified message including one of the following : Internet control message protocol ICMP packet, label switching path to echo LSP ping packet, and Ethernet operation management to maintain Ethernet OAM packet.
The method according to claim 4, wherein said restoration notification information is set in a type and code value that is not specified in said designated message.
The method according to any one of claims 1 to 5, wherein the fault notification information carries a set of destination addresses, wherein the destination address is used to indicate that the transmission path of the service data packet destined for the destination address is faulty. .
A packet encapsulation method, comprising:

The encapsulating node adds the address information of the encapsulating node to the in-band operation management and maintenance IOAM packet, and sends the IOAM packet to the transit node;

Receiving, by the encapsulating node, the fault notification information sent by the transit node, and stopping encapsulating the IOAM packet according to the fault notification information;

Receiving, by the encapsulating node, the recovery notification information sent by the transit node, and recovering the encapsulated new IOAM packet according to the recovery notification information;

The failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.
The method according to claim 7, wherein the recovering the new IOAM message according to the recovery notification information comprises:

The encapsulating node acquires IOAM data content in the new IOAM message, where the IOAM data content includes: IOAM data content associated with the new path;

The encapsulating node encapsulates the new IOAM packet according to the content of the IOAM data.
The method according to claim 7 or 8, wherein the address information of the encapsulation node comprises one of: address type information of the encapsulation node and an indication for the transmission node to send to the encapsulation node The address of the message.
The method according to any one of claims 7 to 9, wherein the encapsulating node receives the failure notification information sent by the transmission node, carries a set of destination addresses, and stops encapsulation to the group of destinations according to the failure notification information. The IOAM message of the address.
A packet processing device is located at a transmission node, and includes:

The receiving module is configured to: receive an in-band operation management and maintenance IOAM message, and save an address of the encapsulation node in the IOAM message;

The first sending module is configured to: when detecting that the current network is faulty, send fault notification information to the encapsulating node, where the fault notification information is generated by the transmitting node according to an address saved in the transit node Information for instructing the encapsulating node to stop encapsulating the IOAM message;

The second sending module is configured to: after completing the protection switching or the route re-convergence, sending the recovery notification information to the encapsulating node; wherein the recovery notification information is generated by the transmitting node according to the address saved in the transmitting node The information indicating that the encapsulating node recovers a new IOAM message is encapsulated.
The device according to claim 11, wherein the device further comprises:

The determining module determines whether a new IOAM message including the saved address is received within the preset aging time; if the determination result is no, the transmitting node deletes the saved address.
A packet encapsulating device, comprising:

The sending module is configured to: add the address information of the encapsulating node to the in-band operation management and maintenance IOAM message, and send the IOAM message to the transmitting node;

The first receiving module is configured to: receive the fault notification information sent by the transit node, and stop encapsulating the IOAM packet according to the fault notification information;

The second receiving module is configured to: the encapsulating node receives the recovery notification information sent by the transit node, and recovers the encapsulated new IOAM packet according to the recovery notification information;

The failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.
A packet encapsulation system, including a transmission node and a package node, wherein

The transmitting node is configured to: receive an in-band operation management and maintenance IOAM message sent by the encapsulating node, and save an address of the encapsulating node in the IOAM packet, and if it detects that the current network is faulty, The encapsulating node sends the failure notification information, and after completing the protection switching or the route re-convergence, sending the recovery notification information to the encapsulating node;

The encapsulating node is configured to: add the address information of the encapsulating node to the IOAM packet, and send the IOAM packet to the transmitting node; receive the fault notification information sent by the transmitting node, and And stopping to encapsulate the IOAM packet according to the fault notification information, and receiving the recovery notification information sent by the transit node, and recovering the encapsulated new IOAM packet according to the recovery notification information;

The failure notification information and the recovery notification information are information generated by the transmission node according to an address saved in the transmission node.
A storage medium, characterized in that the storage medium comprises a stored program, wherein the program is executed to perform the method of any one of claims 1 to 6.
A storage medium, characterized in that the storage medium comprises a stored program, wherein the program is executed to perform the method of any one of claims 7 to 10.
A processor, wherein the processor is configured to run a program, wherein the program is executed to perform the method of any one of claims 1 to 6.
A processor, wherein the processor is configured to run a program, wherein the program is executed to perform the method of any one of claims 7 to 10.