CN108964943B - Method and device for realizing IOAM packaging - Google Patents
Method and device for realizing IOAM packaging Download PDFInfo
- Publication number
- CN108964943B CN108964943B CN201710352022.8A CN201710352022A CN108964943B CN 108964943 B CN108964943 B CN 108964943B CN 201710352022 A CN201710352022 A CN 201710352022A CN 108964943 B CN108964943 B CN 108964943B
- Authority
- CN
- China
- Prior art keywords
- ioam
- node
- band oam
- message
- oam message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
- H04L41/344—Out-of-band transfers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/20—Hop count for routing purposes, e.g. TTL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
Abstract
The invention discloses a method and a device for realizing IOAM packaging, wherein the method comprises the following steps: an IOAM entrance node sends a first out-of-band OAM message carrying IOAM configuration request information, wherein the first out-of-band OAM message sequentially reaches each node on a service data message transmission path; the IOAM entry node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries IOAM configuration information; and the IOAM entrance node performs IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node.
Description
Technical Field
The invention relates to the field of communication, In particular to a method and a device for realizing In-band operation, Administration and Maintenance (IOAM) encapsulation.
Background
IOAM is a new data communication network operation, administration and maintenance (OAM) technology proposed in the industry, which is currently in a rapid development stage under the common promotion of the industry, and is performing standardization work by the Internet Engineering Task Force (IETF).
The IOAM is characterized in that IOAM data contents are encapsulated into service data messages and transmitted in the network as a part of the service data messages, and the OAM data contents are encapsulated into specially constructed OAM data messages and transmitted in the network as separate protocol messages, compared with Out-of-band Operations (Out-of-band Operations, Administration and Maintenance) which are standardized and widely deployed in a data communication network, the IOAM is characterized in that IOAM data contents are respectively described in IOAM series proposals draft-clocks-bands-OAM-requirements, draft-clocks-inband OAM-transport and draft-clocks-OAM-data of the IETF. As a supplement to the out-of-band OAM, the IOAM may implement some functions that the out-of-band OAM cannot implement, such as detecting a network Node through which a service data packet actually passes, verifying whether a transmission path of the service data packet is consistent with an expectation, and adding sequence number information to the service data packet to detect packet loss and disorder, and accordingly, in order to implement the above functions, a network administrator needs to configure an IOAM transmission Node including an IOAM Transit Node and an IOAM Egress Node (IOAM Egress Node), and the IOAM transmission Node is a Node that needs to process IOAM data content on the transmission path of the service data packet. Given the many optional functions that an IOAM contains, as well as the types of traffic carried by the network and the variability of the transmission paths, the above-described configuration is typically relatively complex and subject to change.
The IOAM encapsulation is to insert an IOAM Header (IOAM Header) into a service data packet, fig. 1 is an IOAM Header format diagram, and as shown in fig. 1, the IOAM Header is used to indicate a position (indicated by the IOAM Header in fig. 1) and a Length (indicated by the IOAM Header in fig. 1) of IOAM data content, and also carries a set of IOAM function option types/lengths/values (TLVs, Type/Length/Value) as IOAM data content, where each IOAM function option TLV corresponds to an IOAM function and carries data required for completing the IOAM function. The Node in the network that is responsible for IOAM encapsulation, i.e., the Node inserted into the IOAM header, is called an IOAM entry Node (IOAM Ingress Node) or IOAM encapsulation Node, and the IOAM entry Node may be a network Node such as a switch or a router, or a network terminal such as a personal computer or a server. The IOAM entry node needs to determine which IOAM function options TLVs and the length of each IOAM function option TLV are included in IOAM data content because the IOAM entry node needs to complete insertion of an IOAM header, and these pieces of information are determined by a network administrator according to the configuration conditions on each IOAM transmission node and are issued to the IOAM entry node.
Disclosure of Invention
To solve the foregoing technical problem, embodiments of the present invention provide a method and an apparatus for implementing IOAM encapsulation.
The method for realizing the in-band IOAM encapsulation provided by the embodiment of the invention comprises the following steps:
an IOAM entrance node sends a first out-of-band OAM message carrying IOAM configuration request information, wherein the first out-of-band OAM message sequentially reaches each node on a service data message transmission path;
the IOAM entry node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries IOAM configuration information;
and the IOAM entrance node performs IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node.
In the embodiment of the invention, when the trigger operation of a network administrator is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information; alternatively, the first and second electrodes may be,
when a triggering instruction of a network management module or a control application is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information; alternatively, the first and second electrodes may be,
and when the trigger of the service data message is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information.
In this embodiment of the present invention, the nodes on the service data packet transmission path include at least one of the following: an IOAM transport node, a non-IOAM transport node, wherein the IOAM transport node comprises an IOAM intermediate node and an IOAM egress node.
In this embodiment of the present invention, the receiving, by the IOAM ingress node, a second out-of-band OAM message that carries IOAM configuration information and is sent by an IOAM transmission node includes:
and if the node receiving the first out-of-band OAM message is an IOAM transmission node, the IOAM entry node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries IOAM configuration information.
In this embodiment of the present invention, the IOAM ingress node performs IOAM encapsulation on a service data packet according to IOAM configuration information of each IOAM transmission node, including:
the IOAM entry node determines IOAM function options TLVs included in IOAM data content and the length of each IOAM function option TLV according to the IOAM configuration information of each IOAM transmission node;
and inserting an IOAM header into the service data message according to the IOAM function options TLVs and the length of each IOAM function option TLV.
In the embodiment of the invention, when the service data message transmission path is suitable for an IP network, the first out-of-band OAM message and the second out-of-band OAM message are Internet control message protocol ICMP messages;
when the service data message transmission path is suitable for a multi-protocol label switching (MPLS) network, the first out-of-band OAM message and the second out-of-band OAM message are label switching path echo Label Switching (LSP) Ping messages;
when the service data message transmission path is applicable to an ethernet network, the first out-of-band OAM message and the second out-of-band OAM message are LoopBack messages or LinkTrace messages.
The device for realizing IOAM encapsulation provided by the embodiment of the invention comprises:
a sending unit, configured to send a first out-of-band OAM message carrying IOAM configuration request information, where the first out-of-band OAM message sequentially reaches each node on a service data message transmission path;
the receiving unit is used for receiving a second out-of-band OAM message which is sent by the IOAM transmission node and carries the IOAM configuration information;
and the encapsulation unit is used for carrying out IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node.
In this embodiment of the present invention, the sending unit is specifically configured to: when the trigger operation of a network administrator is obtained, a first out-of-band OAM message carrying IOAM configuration request information is sent; or when a triggering instruction of the network management module or the control application is obtained, sending a first out-of-band OAM message carrying IOAM configuration request information; or when the trigger of the service data message is obtained, sending a first out-of-band OAM message carrying the IOAM configuration request information.
In this embodiment of the present invention, the nodes on the service data packet transmission path include at least one of the following: an IOAM transport node, a non-IOAM transport node, wherein the IOAM transport node comprises an IOAM intermediate node and an IOAM egress node.
In this embodiment of the present invention, if the node that receives the first out-of-band OAM message is an IOAM transmission node, the receiving unit receives a second out-of-band OAM message that carries IOAM configuration information and is sent by the IOAM transmission node.
In an embodiment of the present invention, the encapsulation unit is specifically configured to: determining IOAM function options TLVs included in IOAM data content and the length of each IOAM function option TLV according to the IOAM configuration information of each IOAM transmission node; and inserting an IOAM header into the service data message according to the IOAM function options TLVs and the length of each IOAM function option TLV.
In the embodiment of the present invention, when the service data packet transmission path is applicable to an IP network, the first out-of-band OAM packet and the second out-of-band OAM packet are ICMP packets;
when the service data message transmission path is applicable to the MPLS network, the first out-of-band OAM message and the second out-of-band OAM message are LSP Ping messages;
when the service data message transmission path is applicable to an ethernet network, the first out-of-band OAM message and the second out-of-band OAM message are LoopBack messages or LinkTrace messages.
In the technical scheme of the embodiment of the invention, an IOAM entrance node sends a first out-of-band OAM message carrying IOAM configuration request information, wherein the first out-of-band OAM message sequentially reaches each node on a service data message transmission path; the IOAM entry node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries IOAM configuration information; and the IOAM entrance node performs IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node. By adopting the technical scheme of the embodiment of the invention, the problems that the burden of a network administrator is increased and errors are easy to occur in a method for realizing IOAM encapsulation by manually issuing information at an IOAM entrance node in the related technology are solved, and the IOAM entrance node can support automatic acquisition of information required by IOAM encapsulation under the triggering of service flow.
Drawings
The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed herein.
FIG. 1 is a diagram of an IOAM header format according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for implementing IOAM encapsulation according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating IOAM encapsulation in an IP network according to an exemplary embodiment of the present invention;
fig. 4 is a format diagram of an ICMP message according to a first application example of the present invention;
FIG. 5 is a format diagram of IOAM configuration information TLV according to application example one of the present invention;
fig. 6 is a schematic diagram of implementing IOAM encapsulation in an MPLS network according to application example two of the present invention;
fig. 7 is a format diagram of an LSP Ping packet of application example two of the present invention;
fig. 8 is a schematic diagram of IOAM encapsulation implemented by using LoopBack in an Ethernet network according to a third application example of the present invention;
fig. 9 is a schematic diagram of IOAM encapsulation implemented by using LinkTrace in an Ethernet network according to a third application example of the present invention;
fig. 10 is a format diagram of a LoopBack message of application example three of the present invention;
FIG. 11 is a format diagram of a LinkTrace message of application example three of the present invention;
fig. 12 is a schematic structural diagram of a device for implementing IOAM packaging according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.
Fig. 2 is a schematic flowchart of a method for implementing IOAM encapsulation according to an embodiment of the present invention, and as shown in fig. 2, the method for implementing IOAM encapsulation includes the following steps:
step 201: and the IOAM entrance node sends a first out-of-band OAM message carrying IOAM configuration request information, wherein the first out-of-band OAM message sequentially reaches each node on a service data message transmission path.
Here, the first out-of-band OAM message is only used to distinguish a subsequent second out-of-band OAM message, and has no special meaning. The out-of-band OAM packet follows the same transmission path as the service data packet and is usually used to detect whether the transmission path between the sending node and the receiving node is normal. Networks using different forwarding technologies use different out-of-band OAM messages, for example, an Internet Control Message Protocol (ICMP) message defined in IETF standard RFC 792 is used as the out-of-band OAM message in an IP network, a label switched path echo (LSP Ping) message defined in IETF standard RFC 8029 is used as the out-of-band OAM message in a multiprotocol label switching (MPLS) network, and a LoopBack (LoopBack) message or a link trace (LinkTrace) message defined in International Telecommunication Union (ITU) standard y.1731 is used as the out-of-band OAM message in an Ethernet (Ethernet) network. The method has the advantages that the out-of-band OAM message is used for carrying the IOAM configuration request information, the IOAM configuration request information can be guaranteed to reach each IOAM transmission node on a service data message transmission path, the out-of-band OAM is already deployed in a large scale in the existing network, and the method can be well compatible with the existing network.
In the embodiment of the invention, when the trigger operation of a network administrator is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information; or when a trigger instruction of a network management module or a control application is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information; or, when the trigger of the service data packet is obtained, the IOAM entry node sends a first out-of-band OAM packet carrying IOAM configuration request information.
Therefore, the time for sending the first out-of-band OAM message carrying the IOAM configuration request information by the IOAM ingress node is very flexible, and the first out-of-band OAM message can be sent under the trigger of a network administrator, or under the trigger of a network management module/control application, or under the trigger of a service data message.
In this embodiment of the present invention, the nodes on the service data packet transmission path include at least one of the following: an IOAM transport node, a non-IOAM transport node, wherein the IOAM transport node comprises an IOAM intermediate node and an IOAM egress node.
Step 202: and the IOAM entrance node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries the IOAM configuration information.
Here, a first out-of-band OAM message that is sent by an IOAM entry node and carries IOAM configuration request information may sequentially reach each node on a service data message transmission path, and if a node that receives the first out-of-band OAM message is an IOAM transmission node, that is, the node needs to process IOAM data content, a second out-of-band OAM message that the node replies to the IOAM entry node carries IOAM configuration information of the node, where the IOAM configuration information of the node includes which IOAM capabilities the node supports, enabling conditions of each IOAM capability, and related parameter configurations. If the node receiving the first out-of-band OAM message is not an IOAM transmission node, that is, the node does not need to process the data content of the IOAM, the second out-of-band OAM message replied by the node to the IOAM entry node does not carry the IOAM configuration information of the node.
Step 203: and the IOAM entrance node performs IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node.
In the embodiment of the present invention, the IOAM entry node determines IOAM function options TLVs included in IOAM data content and the length of each IOAM function option TLV according to IOAM configuration information of each IOAM transmission node; and inserting an IOAM header into the service data message according to the IOAM function options TLVs and the length of each IOAM function option TLV, namely realizing IOAM encapsulation of the service data message.
The technical solutions of the embodiments of the present invention are further described in detail below with reference to specific application examples.
Application example 1
Fig. 3 is a schematic diagram of implementing IOAM encapsulation in an IP network. In this application example, the IOAM ingress node and the IOAM transport node execute the following steps:
step 11: and the IOAM entrance node sends an ICMP request message carrying IOAM configuration request information.
Fig. 4 is a format diagram of an ICMP message, and as shown in fig. 4, the ICMP message includes an 8-bit type field and an 8-bit code field, and the IETF standard specifies values of the two fields, for example, type 8 code 0 indicates an ICMP Ping request, type 0 code 0 indicates an ICMP Ping response, type 10 code 0 indicates a router request, type 9 code 0 indicates a router advertisement, and so on. By defining the type and the code value which are not defined, for example, defining type 19 code 0 to represent the IOAM configuration request and type 20 code 0 to represent the IOAM configuration response, the ICMP request message can be made to carry the IOAM configuration request information.
Step 12: and the IOAM transmission node responds to the request and replies an ICMP response message carrying the IOAM configuration information of the node to the IOAM entry node.
According to the ICMP mechanism, the sending node may send the ICMP request message to each node on the transmission path in sequence by changing the Time To Live (TTL) value of the IP header in the ICMP request message. After receiving the ICMP request packet carrying the IOAM configuration request information, the IOAM transmission node replies an ICMP response packet carrying the IOAM configuration information of this node to an ICMP request packet sending node, that is, an IOAM ingress node, where the ICMP response packet carrying the IOAM configuration information of this node is carried in a manner of writing the IOAM configuration information into an option data field of the ICMP response packet in a form of a TLV, fig. 5 is a format diagram of an IOAM configuration information TLV, as shown in fig. 5, where a Type (Type) field of the TLV indicates the IOAM configuration information, a Length (Length) field indicates the Length of the TLV, a Value (Value) field includes a set of Sub-TLVs (Sub-TLVs), each Sub-TLV carries configuration information of one IOAM function, where a Sub-Type (Sub-Type) field indicates a code of one IOAM function supported by this node, a Length field indicates the Length of the Sub-TLV, and a Value field indicates the configuration information of the IOAM function represented by the Sub-Type field, including whether the IOAM function is Enabled (Enabled) in the node and, if Enabled, configuration parameter values associated with the IOAM function, such as those associated with the IOAM tracking (tracking) function defined by the IETF proposal draft-bridges-inband-oam-data, include: the node information is inserted in a Pre-allocated (Pre-allocated) mode or an Incremental (Incremental) mode, and the number of bytes occupied by the node information.
Step 13: and after the IOAM entrance node acquires the IOAM configuration of each node on the IP service message transmission path, determining IOAM encapsulation.
After the IOAM entry node acquires the IOAM configuration of each node on the IP service packet transmission path, it can determine which IOAM function options TLVs are included in the IOAM data content and the length of each IOAM function option TLV, and can also determine IOAM encapsulation for the IP service packet.
Application example two
Fig. 6 is a schematic diagram of implementing IOAM encapsulation in an MPLS network. In this application example, the IOAM ingress node and the IOAM transport node execute the following steps:
step 21: and the IOAM entrance node sends an LSP Ping request message carrying IOAM configuration request information.
Fig. 7 is a format diagram of an LSP Ping request packet, and as shown in fig. 7, the LSP Ping request packet includes a group of TLVs, and a new TLV indicating an IOAM configuration request is added in a Type field, so that the LSP Ping request packet can carry IOAM configuration request information.
Step 22: and the IOAM transmission node responds to the request and replies an LSP Ping response message carrying the IOAM configuration information of the node to the IOAM entry node.
According to the mechanism of LSP Ping, the transmitting node can sequentially transmit the LSP Ping request message to each node on the transmission path by changing the TTL value of the MPLS header in the LSP Ping request message. After receiving the LSP Ping request packet carrying the IOAM configuration request information, the IOAM transmission node replies an LSP Ping response packet carrying the IOAM configuration information of the present node to the LSP Ping request packet sending node, that is, the IOAM ingress node, in a manner of writing the IOAM configuration information into a TLVs field of the LSP Ping response packet in a form of TLV, where the TLV is in a format as shown in fig. 5.
Step 23: and after the IOAM entrance node acquires the IOAM configuration of each node on the MPLS service message transmission path, determining IOAM encapsulation.
After the IOAM entry node acquires the IOAM configuration of each node on the MPLS service packet transmission path, it can determine which IOAM function options TLVs are included in the IOAM data content and the length of each IOAM function option TLV, and can also determine IOAM encapsulation for the MPLS service packet.
Application example three
Fig. 8 is a schematic diagram of IOAM encapsulation by using LoopBack in an Ethernet network, and fig. 9 is a schematic diagram of IOAM encapsulation by using LinkTrace in an Ethernet network. In this application example, the IOAM ingress node and the IOAM transport node execute the following steps:
step 31: and the IOAM entrance node sends a LoopBack request message or a LinkTrace request message carrying IOAM configuration request information.
Fig. 10 is a format diagram of a LoopBack message, fig. 11 is a format diagram of a LinkTrace message, and as shown in fig. 10 and fig. 11, a LoopBack request message or a LinkTrace request message both include a group of TLVs, and by adding a new TLV in which a Type field indicates an IOAM configuration request, the LoopBack request message or the LinkTrace request message can carry IOAM configuration request information.
Step 32: and the IOAM transmission node responds to the request and replies a LoopBack response message or a LinkTrace response message carrying the IOAM configuration information of the node to the IOAM entrance node.
According to the mechanism of the LoopBack, the sending node can sequentially send the LoopBack request message to each node on the transmission path by changing the destination Media Access Control (MAC) address of the Ethernet header in the LoopBack request message. After receiving the LoopBack request message carrying the IOAM configuration request information, the IOAM transmission node replies a LoopBack response message carrying the IOAM configuration information of the node to the LoopBack request message sending node, that is, the IOAM entry node, and the carrying manner may be that the IOAM configuration information is written into a TLVs field of the LoopBack response message in a form of TLV, where the TLV is in a format shown in fig. 5.
According to the LinkTrace mechanism, the sending node can enable the LinkTrace request message to sequentially reach each node on the transmission path only by setting the destination MAC address of the Ethernet head in the LinkTrace request message as a special multicast address. After receiving the LinkTrace request message carrying the IOAM configuration request information, the IOAM transmission node replies a LinkTrace response message carrying the IOAM configuration information of the node to the LinkTrace request message sending node, that is, the IOAM entry node, where the carrying manner may be that the IOAM configuration information is written into a TLVs field of the LinkTrace response message in a form of TLV, and the TLV is in a format as shown in fig. 5.
Step 33: and after the IOAM entrance node acquires the IOAM configuration of each node on the Ethernet service message transmission path, determining IOAM encapsulation.
After the IOAM entry node acquires the IOAM configuration of each node on the Ethernet service packet transmission path, it can determine which IOAM function options TLVs are contained in the IOAM data content and the length of each IOAM function option TLV, and can also determine IOAM encapsulation for the Ethernet service packet.
Fig. 12 is a schematic structural component diagram of an apparatus for implementing IOAM encapsulation according to an embodiment of the present invention, and as shown in fig. 12, the apparatus includes:
a sending unit 121, configured to send a first out-of-band OAM message carrying IOAM configuration request information, where the first out-of-band OAM message sequentially reaches each node on a service data message transmission path;
a receiving unit 122, configured to receive a second out-of-band OAM message that carries IOAM configuration information and is sent by an IOAM transmission node;
an encapsulating unit 123, configured to perform IOAM encapsulation on the service data packet according to IOAM configuration information of each IOAM transmission node.
In this embodiment of the present invention, the sending unit 121 is specifically configured to: when the trigger operation of a network administrator is obtained, a first out-of-band OAM message carrying IOAM configuration request information is sent; or when a triggering instruction of the network management module or the control application is obtained, sending a first out-of-band OAM message carrying IOAM configuration request information; or when the trigger of the service data message is obtained, sending a first out-of-band OAM message carrying the IOAM configuration request information.
In this embodiment of the present invention, the nodes on the service data packet transmission path include at least one of the following: an IOAM transport node, a non-IOAM transport node, wherein the IOAM transport node comprises an IOAM intermediate node and an IOAM egress node.
In this embodiment of the present invention, if the node that receives the first out-of-band OAM message is an IOAM transmission node, the receiving unit 122 receives a second out-of-band OAM message that carries IOAM configuration information and is sent by the IOAM transmission node.
In an embodiment of the present invention, the encapsulating unit 123 is specifically configured to: determining IOAM function options TLVs included in IOAM data content and the length of each IOAM function option TLV according to the IOAM configuration information of each IOAM transmission node; and inserting an IOAM header into the service data message according to the IOAM function options TLVs and the length of each IOAM function option TLV, namely realizing IOAM encapsulation of the service data message.
In the embodiment of the present invention, when the service data packet transmission path is applicable to an IP network, the first out-of-band OAM packet and the second out-of-band OAM packet are ICMP packets;
when the service data message transmission path is applicable to the MPLS network, the first out-of-band OAM message and the second out-of-band OAM message are LSP Ping messages;
when the service data message transmission path is applicable to an ethernet network, the first out-of-band OAM message and the second out-of-band OAM message are LoopBack messages or LinkTrace messages.
It will be understood by those skilled in the art that the implementation functions of each unit in the apparatus for implementing an IOAM package shown in fig. 12 can be understood by referring to the related description of the method for implementing an IOAM package. The functions of the units in the apparatus for implementing an IOAM package shown in fig. 12 may be implemented by a program running on a processor, or may be implemented by a specific logic circuit.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (10)
1. A method for implementing in-band operation administration maintenance (IOAM) encapsulation, the method comprising:
an IOAM entrance node sends a first out-of-band OAM message carrying IOAM configuration request information, wherein the first out-of-band OAM message sequentially reaches each node on a service data message transmission path;
the IOAM entry node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries IOAM configuration information;
the IOAM entrance node performs IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node;
the IOAM entrance node performs IOAM encapsulation on the service data message according to the IOAM configuration information of each IOAM transmission node, and the method comprises the following steps:
the IOAM entry node determines IOAM function options TLVs included in IOAM data content and the length of each IOAM function option TLV according to the IOAM configuration information of each IOAM transmission node;
and inserting an IOAM header into the service data message according to the IOAM function options TLVs and the length of each IOAM function option TLV.
2. The method of claim 1,
when the trigger operation of a network administrator is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information; alternatively, the first and second electrodes may be,
when a triggering instruction of a network management module or a control application is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information; alternatively, the first and second electrodes may be,
and when the trigger of the service data message is obtained, the IOAM entry node sends a first out-of-band OAM message carrying IOAM configuration request information.
3. The method of claim 1, wherein the nodes on the traffic data packet transmission path comprise at least one of: an IOAM transport node, a non-IOAM transport node, wherein the IOAM transport node comprises an IOAM intermediate node and an IOAM egress node.
4. The method according to claim 3, wherein the IOAM ingress node receiving a second out-of-band OAM packet carrying IOAM configuration information sent by an IOAM transport node comprises:
and if the node receiving the first out-of-band OAM message is an IOAM transmission node, the IOAM entry node receives a second out-of-band OAM message which is sent by the IOAM transmission node and carries IOAM configuration information.
5. The method according to any one of claims 1 to 4,
when the service data message transmission path is suitable for an IP network, the first out-of-band OAM message and the second out-of-band OAM message are Internet Control Message Protocol (ICMP) messages;
when the service data message transmission path is suitable for a multi-protocol label switching (MPLS) network, the first out-of-band OAM message and the second out-of-band OAM message are label switching path echo Label Switching (LSP) Ping messages;
when the service data message transmission path is applicable to an ethernet network, the first out-of-band OAM message and the second out-of-band OAM message are LoopBack messages or link trace line messages.
6. An apparatus that implements IOAM encapsulation, the apparatus comprising:
a sending unit, configured to send a first out-of-band OAM message carrying IOAM configuration request information, where the first out-of-band OAM message sequentially reaches each node on a service data message transmission path;
the receiving unit is used for receiving a second out-of-band OAM message which is sent by the IOAM transmission node and carries the IOAM configuration information;
an encapsulation unit, configured to perform IOAM encapsulation on the service data packet according to IOAM configuration information of each IOAM transmission node;
the encapsulation unit is specifically configured to: determining IOAM function options TLVs included in IOAM data content and the length of each IOAM function option TLV according to the IOAM configuration information of each IOAM transmission node; and inserting an IOAM header into the service data message according to the IOAM function options TLVs and the length of each IOAM function option TLV.
7. The apparatus according to claim 6, wherein the sending unit is specifically configured to: when the trigger operation of a network administrator is obtained, a first out-of-band OAM message carrying IOAM configuration request information is sent; or when a triggering instruction of the network management module or the control application is obtained, sending a first out-of-band OAM message carrying IOAM configuration request information; or when the trigger of the service data message is obtained, sending a first out-of-band OAM message carrying the IOAM configuration request information.
8. The apparatus of claim 6, wherein the nodes on the traffic data packet transmission path comprise at least one of: an IOAM transport node, a non-IOAM transport node, wherein the IOAM transport node comprises an IOAM intermediate node and an IOAM egress node.
9. The apparatus of claim 8, wherein the receiving unit is configured to receive a second out-of-band OAM message sent by the IOAM transport node and carrying IOAM configuration information, if the node that receives the first out-of-band OAM message is an IOAM transport node.
10. The device according to any one of claims 6 to 9,
when the service data message transmission path is suitable for an IP network, the first out-of-band OAM message and the second out-of-band OAM message are ICMP messages;
when the service data message transmission path is applicable to the MPLS network, the first out-of-band OAM message and the second out-of-band OAM message are LSP Ping messages;
when the service data message transmission path is applicable to an ethernet network, the first out-of-band OAM message and the second out-of-band OAM message are LoopBack messages or LinkTrace messages.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710352022.8A CN108964943B (en) | 2017-05-18 | 2017-05-18 | Method and device for realizing IOAM packaging |
| PCT/CN2018/086788 WO2018210213A1 (en) | 2017-05-18 | 2018-05-15 | Method and device for implementing ioam packaging and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710352022.8A CN108964943B (en) | 2017-05-18 | 2017-05-18 | Method and device for realizing IOAM packaging |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108964943A CN108964943A (en) | 2018-12-07 |
| CN108964943B true CN108964943B (en) | 2022-01-28 |
Family
ID=64273386
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710352022.8A Active CN108964943B (en) | 2017-05-18 | 2017-05-18 | Method and device for realizing IOAM packaging |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108964943B (en) |
| WO (1) | WO2018210213A1 (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111327445B (en) * | 2018-12-17 | 2023-09-12 | 中兴通讯股份有限公司 | Message sampling method, message unpacking method, node, system and storage medium |
| CN111371736B (en) * | 2018-12-26 | 2022-12-06 | 中兴通讯股份有限公司 | iOAM information processing method, iOAM information processing device and computer readable storage medium |
| CN111385121B (en) * | 2018-12-29 | 2021-08-03 | 华为技术有限公司 | Transmission method of operation administration maintenance (iOAM) message and corresponding device |
| CN112118147A (en) * | 2019-06-21 | 2020-12-22 | 烽火通信科技股份有限公司 | MPLS-TPOAM-based LB detection method and system |
| CN112448926B (en) * | 2019-08-30 | 2022-07-08 | 烽火通信科技股份有限公司 | Processing method and system for in-band operation, management and maintenance (IOAM) |
| CN115695248A (en) * | 2019-10-26 | 2023-02-03 | 华为技术有限公司 | Method and device for processing multicast message |
| CN112866042B (en) * | 2019-11-12 | 2023-07-18 | 中兴通讯股份有限公司 | Network quality detection method, device, computer equipment and computer readable medium |
| CN112804075B (en) * | 2019-11-14 | 2022-10-11 | 华为技术有限公司 | Method, device and system for sending message and receiving message for OAM (operation administration and maintenance) |
| CN112910773A (en) * | 2019-11-19 | 2021-06-04 | 华为技术有限公司 | Method for issuing OAM configuration information and control node |
| CN114826952A (en) * | 2021-01-27 | 2022-07-29 | 中国移动通信有限公司研究院 | Information processing method and device for OAM detection and node equipment |
| CN117834342A (en) * | 2022-09-29 | 2024-04-05 | 中兴通讯股份有限公司 | Method and device for realizing IOAM encapsulation of virtualized tunnel network |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848775A (en) * | 2005-09-30 | 2006-10-18 | 华为技术有限公司 | Multi-jumping pseudo-line fault detecting reporting and maintenance protocol controlling method |
| CN101267363A (en) * | 2008-04-24 | 2008-09-17 | 杭州华三通信技术有限公司 | Loop testing method, system and device |
| CN101478438A (en) * | 2009-01-13 | 2009-07-08 | 中兴通讯股份有限公司 | Ethernet OAM link discovery method |
| CN101826990A (en) * | 2009-03-05 | 2010-09-08 | 华为技术有限公司 | Method, device and system for detecting connectedness of virtual pseudo wires |
| CN102916845A (en) * | 2011-08-01 | 2013-02-06 | 中兴通讯股份有限公司 | Multi-path loopback detecting method and exchanger equipment |
| CN103609066B (en) * | 2011-04-28 | 2017-04-26 | 华为技术有限公司 | Method and node for querying operation administration maintenance configuration information |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2341668A1 (en) * | 2010-01-05 | 2011-07-06 | Alcatel Lucent | Transport of a traffic flow in a mobile communication system |
| WO2012006825A1 (en) * | 2010-07-12 | 2012-01-19 | 中兴通讯股份有限公司 | Method, system and terminal for pseudo wire oam attribute configuration |
| CN103580894B (en) * | 2012-07-31 | 2017-09-29 | 华为技术有限公司 | Method, equipment and the system of Operations, Administration and Maintenance OAM configurations |
| CN104509032B (en) * | 2012-08-01 | 2018-04-03 | 瑞典爱立信有限公司 | For operating, supervising and managing the methods, devices and systems of (OAM) function in a network |
| US9992056B2 (en) * | 2015-10-20 | 2018-06-05 | Cisco Technology, Inc. | Triggered in-band operations, administration, and maintenance in a network environment |
| CN105893061A (en) * | 2016-06-12 | 2016-08-24 | 杭州勒芒科技有限公司 | Application program development method and system |
-
2017
- 2017-05-18 CN CN201710352022.8A patent/CN108964943B/en active Active
-
2018
- 2018-05-15 WO PCT/CN2018/086788 patent/WO2018210213A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848775A (en) * | 2005-09-30 | 2006-10-18 | 华为技术有限公司 | Multi-jumping pseudo-line fault detecting reporting and maintenance protocol controlling method |
| CN101267363A (en) * | 2008-04-24 | 2008-09-17 | 杭州华三通信技术有限公司 | Loop testing method, system and device |
| CN101478438A (en) * | 2009-01-13 | 2009-07-08 | 中兴通讯股份有限公司 | Ethernet OAM link discovery method |
| CN101826990A (en) * | 2009-03-05 | 2010-09-08 | 华为技术有限公司 | Method, device and system for detecting connectedness of virtual pseudo wires |
| CN103609066B (en) * | 2011-04-28 | 2017-04-26 | 华为技术有限公司 | Method and node for querying operation administration maintenance configuration information |
| CN102916845A (en) * | 2011-08-01 | 2013-02-06 | 中兴通讯股份有限公司 | Multi-path loopback detecting method and exchanger equipment |
Non-Patent Citations (2)
| Title |
|---|
| Encapsulations for In-band OAM Data draft-brockners-inband-oam-transport-01;F.Brockners et.al;《https://datatracker.ietf.org/drafts》;20160718;第1-12页 * |
| Proof of Transit ；draft-brockners-proof-of-transit-03;F.Brockners et.al;《https://datatracker.ietf.org/drafts》;20170313;第1-22页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108964943A (en) | 2018-12-07 |
| WO2018210213A1 (en) | 2018-11-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108964943B (en) | Method and device for realizing IOAM packaging | |
| CN108965204B (en) | Method and device for automatically realizing IOAM packaging | |
| CN111953604B (en) | Method and device for providing business service for business flow | |
| CN110034971B (en) | Method and device for detecting service chain | |
| US20170201435A1 (en) | Switch, controller, system, and link quality detection method | |
| EP4054126A1 (en) | Transmission quality test method and apparatus, system, and storage medium | |
| US9059905B2 (en) | Methods and arrangements in an MPLS-TP network | |
| EP4207685A1 (en) | Message header processing method and apparatus, storage medium and electronic device | |
| EP3917097A1 (en) | Bier-based bidirectional forwarding detection session creation method, bfir, bfer, system, and storage medium | |
| EP2498453B1 (en) | Node, monitoring and administration method used thereupon, and transfer system, input circuit, and output circuit using same | |
| CN101826990A (en) | Method, device and system for detecting connectedness of virtual pseudo wires | |
| WO2015184771A1 (en) | Method and node device for operation, administration, and maintenance of service function chaining | |
| CN111490933B (en) | Bidirectional forwarding detection switching method and edge device | |
| CN103580894A (en) | Method, device and system for operation, administration and maintenance (OAM) configuration | |
| CN112350934A (en) | Data transmission method, network node and data transmission system | |
| WO2021088813A1 (en) | Packet encapsulating method and apparatus, and packet decapsulating method and apparatus | |
| CN110959272B (en) | Defect detection in IP/MPLS network tunnels | |
| CN107370654B (en) | Pseudo wire data message encapsulation and decapsulation methods and related devices | |
| CN102055619A (en) | Method and system for realize fault detection in bidirectional path segment | |
| CN110224916B (en) | Message processing method and device and message packaging method, device and system | |
| CN102611631A (en) | Method, device and system for protecting protocol under pseudo-wire scene | |
| CN102301647B (en) | Virtual Circuit Configuration Method | |
| CN114629843A (en) | Message processing method and device | |
| CN108111327B (en) | Network operation management maintenance method and device | |
| CN114221867A (en) | Operation, administration and maintenance (OAM) message processing method and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |