WO2020114083A1 - 一种ioam信息的处理方法和装置 - Google Patents

一种ioam信息的处理方法和装置 Download PDF

Info

Publication number
WO2020114083A1
WO2020114083A1 PCT/CN2019/110790 CN2019110790W WO2020114083A1 WO 2020114083 A1 WO2020114083 A1 WO 2020114083A1 CN 2019110790 W CN2019110790 W CN 2019110790W WO 2020114083 A1 WO2020114083 A1 WO 2020114083A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
ioam information
tunnel
header
ioam
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.)
Ceased
Application number
PCT/CN2019/110790
Other languages
English (en)
French (fr)
Inventor
王同乐
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to EP19893323.6A priority Critical patent/EP3893435B1/en
Publication of WO2020114083A1 publication Critical patent/WO2020114083A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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

Definitions

  • the embodiments of the present application relate to, but are not limited to, network communication technology, and particularly refer to an in-band operation management (OAM, Operations, Administration and Maintenance) (IOAM, In-band OAM, or In-situ OAM) information processing method and device.
  • OAM In-band operation management
  • IOAM Operations, Administration and Maintenance
  • In-band OAM In-band OAM
  • In-situ OAM In-situ OAM
  • the data center network puts forward higher requirements on delay, packet loss, forwarding path and reliability.
  • a network visualization technology that can continuously obtain the operating data of the network, so as to troubleshoot the network, network planning and traffic adjustment. Excellent to provide decision-making guidance.
  • In-band OAM is an in-band OAM technology that solves the data center network visualization.
  • P4 programming protocol independent packet processors
  • In-band OAM technology has also been gradually proposed and applied.
  • the technical draft is mainly the In-situ OAM of the International Internet Engineering Task Force (IETF, The Internet Engineering Task Force), or In-band OAM, hereinafter referred to as IOAM.
  • IOAM related drafts are for the use of Generic Routing Encapsulation (GRE, Generic Routing Encapsulation), Internet Protocol Version 6 (IPV6, Internet Protocol Version 6), Virtual Extended Local Area Network (VXLAN, Virtual Extensible Local Area Network (LAN, Local Area Area Network)) ), Network Service Host (NSH), Network Service (Host), Segment Routing (SR, Segment) Routing as the method of transmission protocol has been described, but the current draft has not yet proposed a IOAM solution for the scene of tunnel splicing.
  • GRE Generic Routing Encapsulation
  • IPV6 Internet Protocol Version 6
  • VXLAN Virtual Extended Local Area Network
  • LAN Virtual Extensible Local Area Network
  • NSH Network Service Host
  • Host Network Service Routing
  • SR Segment Routing
  • the embodiments of the present application provide a method and a device for processing IOAM information, which can realize the transmission of IOAM information in a tunnel splicing scenario and avoid the loss of IOAM information caused by the end of a tunnel.
  • An embodiment of the present application provides a method for processing IOAM information, including:
  • the original outer tunnel header of the data packet is stripped to determine the exit tunnel type
  • a new outer tunnel header corresponding to the tunnel type of the egress tunnel encapsulated in the data packet is sent to the next node.
  • An embodiment of the present application provides an apparatus for processing IOAM information, including:
  • Receiver module configured to receive data packets
  • the processing module is configured to strip the original outer tunnel header of the data packet to determine the exit tunnel type when the local node is determined to be the end point of the current tunnel according to the original outer tunnel header of the data packet; Add IOAM information in the data packet and IOAM information in the node to the data packet according to whether the node's tunnel type supports egress to the data packet; encapsulate the egress tunnel type corresponding to the data packet The new outer tunnel header is sent to the next node.
  • An embodiment of the present application provides an apparatus for processing IOAM information, including a processor and a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the instructions are executed by the processor, the foregoing Any kind of IOAM information processing method.
  • An embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the foregoing IOAM information processing methods are implemented.
  • Embodiments of the present application include: receiving a data packet; stripping off the original outer tunnel header of the data packet when it is determined that the current node is the end point of the current tunnel based on the original outer tunnel header of the data packet To determine the type of egress tunnel; add the IOAM information in the data packet and the IOAM information of the node to the data packet according to whether the node supports the addition of IOAM information to the egress tunnel type; for the data packet The new outer tunnel header corresponding to the encapsulated tunnel type is sent to the next node.
  • the IOAM information in the data packet and the IOAM information of the own node are added to the data according to whether the node supports the addition of IOAM information to the exit tunnel type
  • the transmission of IOAM information in the tunnel splicing scenario is realized, and the loss of IOAM information caused by the end of the tunnel is avoided, so that the IOAM information is continuously obtained to provide decision guidance for the network.
  • FIG. 1(a) is a schematic diagram 1 of a topology of similar tunnels spliced at an egress gateway according to an embodiment of the present application;
  • FIG. 1(b) is a topological schematic diagram 1 of splicing heterogeneous tunnels at an egress gateway according to an embodiment of the present application;
  • FIG. 2 is a flowchart of a method for processing IOAM information proposed by an embodiment of the present application
  • FIG. 3(a) is a schematic diagram 2 of topology of similar tunnels spliced at an egress gateway according to an embodiment of the present application;
  • FIG. 3(b) is a second schematic topology diagram of splicing heterogeneous tunnels at an egress gateway according to an embodiment of the present application
  • FIG. 4 is a schematic structural composition diagram of an apparatus for processing IOAM information according to another embodiment of the present application.
  • FIG. 1(a) is a schematic diagram of a topology of similar tunnels spliced at an egress gateway according to an embodiment of the present application.
  • the egress gateway is connected to two tunnels of the same type.
  • the internal overlay network tunnel type in the data center (DC, Data) is tunnel type 1
  • the tunnel type between DCs is still tunnel type 1.
  • the egress gateway needs to terminate the original tunnel and then re-encapsulate the new one. Tunnel, so it is still called tunnel splicing.
  • the transmission of IOAM information between tunnels also needs to be supported.
  • FIG. 1(b) is a schematic topology diagram of splicing heterogeneous tunnels at an egress gateway according to an embodiment of the present application.
  • two different types of tunnels are connected to the egress gateway.
  • the DC internal overlay network tunnel type is tunnel type 1
  • the inter-DC network tunnel type is tunnel type 2.
  • the nodes within the two DCs need to perform tunnel splicing at the DC egress gateway when transmitting IOAM messages across DCs.
  • the tunnel splicing needs to support the transfer of IOAM information between different tunnels.
  • the embodiment of the present application uses the data center network as an example to illustrate the scenario of tunnel splicing.
  • the embodiment of the present application is not limited to the application in the data center network, but is applicable to the network scenario including all tunnel splicing; at the same time, the present application
  • the embodiments are not limited to tunnel splicing between two networks. Tunnel splicing within the same network and tunnel splicing between more than two networks are also within the protection scope of the embodiments of the present application.
  • the IOAM information is discarded, so that the IOAM information is lost during the transmission process, so that the IOAM information cannot be continuously obtained to provide decision guidance for the network.
  • an embodiment of the present application proposes a method for processing IOAM information, including:
  • Step 200 Receive a data message.
  • Step 201 When it is determined that the current node is the end point of the current tunnel according to the original outer tunnel header of the data packet, strip the original outer tunnel header of the data packet to determine the exit tunnel type.
  • the forwarding table may be checked according to the inner packet header to obtain the exit tunnel encapsulation information, and the exit tunnel type may be determined according to the tunnel feature field in the exit tunnel encapsulation information.
  • the exit tunnel type can be stored in a custom field in the exit tunnel encapsulation information, and the exit tunnel type can be determined according to the exit tunnel type of the exit tunnel encapsulation information; or, based on other existing fields in the exit tunnel encapsulation information Determine the exit tunnel type.
  • the method further includes: The original outer tunnel header of the packet obtains the IOAM information; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the local node.
  • Step 202 Add the IOAM information in the data packet and the IOAM information of the local node to the data packet according to whether the local node supports adding IOAM information to the exit tunnel type.
  • adding IOAM information in the data packet and IOAM information in the data packet to the data packet includes at least one of the following according to whether the node's exit tunnel type supports adding IOAM information.
  • the IOAM information in the original outer tunnel header or the inner packet header of the data packet and the IOAM information of the local node are added Added to the new outer tunnel header corresponding to the tunnel type of the egress of the data packet.
  • determining whether the local node supports the addition of IOAM information to the egress tunnel type includes at least one of the following:
  • the pre-configured tunnel type that supports the addition of IOAM information determine whether the node's exit tunnel type supports the addition of IOAM information; as an embodiment, the pre-configured tunnel type that supports the addition of IOAM information includes the exit tunnel type of the node In the case of, it is determined that the local node supports the addition of IOAM information to the tunnel type of the exit; if the pre-configured tunnel type that supports IOAM information does not include the tunnel type of the exit of the node, the tunnel type of the local node to the exit is determined Does not support adding IOAM information; Among them, the pre-configured tunnel type that supports adding IOAM information can be manually configured;
  • the pre-configured tunnel type that does not support the addition of IOAM information determine whether the node's exit tunnel type supports the addition of IOAM information; as an embodiment, the pre-configured tunnel type that does not support the addition of IOAM information includes the exit of the node In the case of the tunnel type, it is determined that the node does not support adding IOAM information to the egress tunnel type; when the pre-configured tunnel type that does not support IOAM information does not include the egress tunnel type of the node, it is determined that the node is The exit tunnel type supports adding IOAM information; among them, the pre-configured tunnel type that does not support adding IOAM information can be manually configured;
  • the packet type specified in draft-brockners-inband-oam-transport or draft-brockners-ippm-ioam-geneve of IOAM draft determine whether the node supports the addition of IOAM information to the type of egress tunnel; as an implementation method, in IOAM If the packet type specified in the draft includes the packet type of the data packet, it is determined that the local node supports adding IOAM information to the egress tunnel type; the packet type specified in the IOAM draft does not include the packet of the data packet In the case of the type, it is judged that the local node does not support adding IOAM information to the exit tunnel type.
  • adding the IOAM information in the original outer tunnel header of the data packet and the IOAM information of the local node to the inner packet header of the data packet includes:
  • step 201 In the case of buffering the IOAM information in the outer tunnel header of the data packet in step 201, add the cached IOAM information and the IOAM information of the local node to the inner packet header of the data packet;
  • step 201 when the IOAM information in the outer tunnel header of the data packet is cached and the IOAM information of the local node, the cached IOAM information is added to the inner packet header of the data packet.
  • the specific location where the IOAM information is added to the inner packet header can be customized, such as custom private user datagram protocol (UDP, User Datagram Protocol) and transmission control protocol (TCP, Transmission Control Protocol) port number.
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • the specific location where the IOAM information is added to the inner packet header can be defined according to the format of the IOAM draft draft-brockners-inband-oam-transport for the message format of various types of messages carrying IOAM information .
  • the IOAM information in the original outer tunnel header of the data packet and the local node is added to the inner header of the data packet, which realizes the transmission of IOAM information in the tunnel splicing scenario, avoids the loss of IOAM information caused by the end of the tunnel, and thus continuously obtains IOAM information to provide decision-making for the network guide.
  • adding IOAM information to the specific location of the new outer tunnel header of the data packet can be carried according to the IOAM draft draft-brockners-inband-oam-transport or draft-brockners-ippm-ioam-geneve
  • the message format definition of IOAM information can be carried according to the IOAM draft draft-brockners-inband-oam-transport or draft-brockners-ippm-ioam-geneve.
  • Step 203 The new outer tunnel header corresponding to the tunnel type of the egress encapsulated in the data packet is sent to the next node.
  • the local node is the end point of the current tunnel, and the IOAM information in the data packet and the IOAM information of the local node are added to the data according to whether the local node supports the addition of IOAM information to the exit tunnel type
  • the transmission of IOAM information in the tunnel splicing scenario is realized, and the loss of IOAM information caused by the end of the tunnel is avoided, so that the IOAM information is continuously obtained to provide decision guidance for the network.
  • the method when it is determined that the local node is not the end point of the current tunnel according to the original outer tunnel header of the data packet, the method further includes at least one of the following:
  • the original outer tunnel header of the data packet contains the IOAM information
  • the data packet is sent to the next node.
  • the egress gateway 1 of the data center network 1 and the egress gateway 2 of the data center network 2 are respectively spliced with different types of tunnels, and the egress gateway 1 does not support adding IOAM information to the tunnel type 2.
  • the method includes:
  • Step 300 The egress gateway 1 receives the data message carrying the IOAM information sent from the access gateway 1, the original outer tunnel header is encapsulated into the tunnel header corresponding to the tunnel type 1, and the original outer tunnel header carries the IOAM information.
  • Step 301 The egress gateway 1 determines whether the egress gateway 1 is the end point of the current tunnel (that is, a tunnel of type 1 tunnel) according to the original outer tunnel header of the data packet.
  • the IOAM information is obtained from the original outer tunnel header of the data packet; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the egress gateway 1 are obtained.
  • Step 302 The egress gateway 1 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is a tunnel of type 2 tunnel.
  • Step 303 The egress gateway 1 determines whether the egress gateway 1 supports adding IOAM information to the tunnel type 2. If the egress gateway 1 does not support adding IOAM information to the tunnel type 2, the egress gateway 1 compares the cached IOAM information or the cached IOAM The information and the IOAM information of the egress gateway 1 are added to the inner packet header, and are sent from the egress gateway 1 after the outer layer encapsulates the new outer tunnel header corresponding to the tunnel type 2.
  • Step 304 During the process of the data packet passing through the tunnel between the egress gateway 1 and the egress gateway 2, the experienced network node no longer adds IOAM information.
  • Step 305 The egress gateway 2 receives the data message carrying the IOAM information sent by the egress gateway 1, and the original outer tunnel header is encapsulated into the tunnel header corresponding to the tunnel type 2.
  • the original outer tunnel header does not carry the IOAM information.
  • Step 306 The egress gateway 2 determines whether the egress gateway 2 is the end point of the current tunnel (that is, the tunnel type 2 tunnel) according to the original outer tunnel header of the data packet, and the egress gateway 2 determines the egress gateway 2 according to the original outer tunnel header of the data packet. When it is determined that the egress gateway 2 is the end point of the current tunnel, the egress gateway 2 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is a tunnel of tunnel type 1.
  • Step 307 The egress gateway 2 determines whether the egress gateway 2 supports the addition of IOAM information to the tunnel type 1. If the egress gateway 2 supports the addition of IOAM information to the tunnel type 1, the egress gateway 2 encapsulates the new outer layer corresponding to the tunnel type 1 in the outer layer When the tunnel header is obtained, the IOAM information is obtained from the inner packet header, the obtained IOAM information and the IOAM information of the egress gateway 2 are added to the new outer tunnel header, and the data packet after encapsulating the new outer tunnel header is exported from the egress gateway 2 issue.
  • the egress gateway 1 of the data center network 1 and the egress gateway 2 of the data center network 2 are respectively spliced with different types of tunnels, and the egress gateway 1 supports adding IOAM information to the tunnel type 2.
  • the method includes:
  • Step 400 The egress gateway 1 receives the data message carrying the IOAM information sent from the access gateway 1, the original outer tunnel header is encapsulated into a tunnel head corresponding to the tunnel type 1, and the original outer tunnel header carries the IOAM information.
  • Step 401 The egress gateway 1 determines whether the egress gateway 1 is the end point of the current tunnel (that is, a tunnel of type 1 tunnel) according to the original outer tunnel header of the data packet, and the egress gateway 1 determines the original outer tunnel header according to the data packet.
  • the IOAM information is obtained from the original outer tunnel header of the data packet; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the egress gateway 1 are obtained.
  • Step 402 The egress gateway 1 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is a tunnel of type 2 tunnel.
  • Step 403 The egress gateway 1 determines whether the egress gateway 1 supports adding IOAM information to the tunnel type 2. If the egress gateway 1 supports adding IOAM information to the tunnel type 2, the egress gateway 1 encapsulates the new outer layer corresponding to the tunnel type 2 in the outer layer When the tunnel header is added, the cached IOAM information, or the cached IOAM information and the IOAM information of the egress gateway 1 are added to the new outer tunnel header, and the data message encapsulated by the new outer tunnel header is sent from the egress gateway 1.
  • Step 404 When the data packet passes through the tunnel between the egress gateway 1 and the egress gateway 2, the experienced network node continues to add IOAM information.
  • Step 405 The egress gateway 2 receives the data message carrying the IOAM information sent from the egress gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to tunnel type 2, and the original outer tunnel header carries the IOAM information.
  • Step 406 The egress gateway 2 determines whether the egress gateway 2 is the end point of the current tunnel (that is, the tunnel type 2 tunnel) according to the original outer tunnel header of the data packet, and the egress gateway 2 determines the egress gateway 2 according to the original outer tunnel header of the data packet.
  • the exit gateway 2 obtains IOAM information from the original outer tunnel header of the data packet; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the exit gateway 2 , Strip the original outer tunnel header of the data packet, and check the forwarding table according to the inner packet header to determine that the exit is a tunnel of tunnel type 1.
  • Step 407 The egress gateway 2 judges whether the egress gateway 2 supports adding IOAM information to the tunnel type 1, and in the case that the egress gateway 2 supports adding IOAM information to the tunnel type 1, the egress gateway 2 encapsulates the new outer layer corresponding to the tunnel type 1 in the outer layer
  • the tunnel header is added, the cached IOAM information, or the cached IOAM information and the IOAM information of the egress gateway 2 are added to the new outer tunnel header, and the data packet after encapsulating the new outer tunnel header is sent from the egress gateway 2.
  • the egress gateway 1 of the data center network 1 and the egress gateway 2 of the data center network 2 are respectively spliced with different types of tunnels, that is, the tunnel type between the access gateway and the egress gateway is VXLAN tunnel type.
  • the tunnel type between egress gateways is Multi-Protocol Labeling (MPLS) Multi-Protocol Labeling (Switching) tunnel type, and egress gateway 1 does not support adding IOAM information to MPLS tunnels.
  • MPLS Multi-Protocol Labeling
  • Switchching Multi-Protocol Labeling
  • Step 500 The egress gateway 1 receives the data message carrying the IOAM information sent by the access gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to the VXLAN tunnel type, and the original outer tunnel header carries the IOAM information.
  • Step 501 The egress gateway 1 determines whether the egress gateway 1 is the end point of the current tunnel (that is, a VXLAN tunnel type tunnel) according to the original outer tunnel header of the data packet.
  • the IOAM information is obtained from the original outer tunnel header of the data packet; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the egress gateway 1 are obtained.
  • Step 502 The egress gateway 1 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is of the MPLS tunnel type.
  • Step 503 The egress gateway 1 determines whether the egress gateway 1 supports adding IOAM information to the MPLS tunnel type. When the egress gateway 1 does not support adding IOAM information to the MPLS tunnel type, the egress gateway 1 compares the cached IOAM information or the cached IOAM The information and the IOAM information of the egress gateway 1 are added to the inner packet header, and the new outer tunnel header corresponding to the MPLS tunnel type is encapsulated in the outer layer and sent out from the egress gateway 1.
  • Step 504 When the data packet passes through the tunnel between the egress gateway 1 and the egress gateway 2, the intermediate network node performs MPLS forwarding, and the experienced network node no longer adds IOAM information.
  • Step 505 The egress gateway 2 receives the data message carrying the IOAM information sent from the egress gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to the MPLS tunnel type, and the original outer tunnel header does not carry the IOAM information.
  • Step 506 The egress gateway 2 determines whether the egress gateway 2 is the end point of the current tunnel (that is, an MPLS tunnel type tunnel) according to the original outer tunnel header of the data packet. At the egress gateway 2 according to the original outer tunnel header of the data packet When it is determined that the egress gateway 2 is the end point of the current tunnel, the egress gateway 2 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is a VXLAN tunnel type tunnel.
  • Step 507 The egress gateway 2 determines whether the egress gateway 2 supports the addition of IOAM information to the VXLAN tunnel type. When the egress gateway 2 supports the addition of IOAM information to the VXLAN tunnel type, the egress gateway 2 encapsulates the new outer layer corresponding to the VXLAN tunnel type When the tunnel header is obtained, the IOAM information is obtained from the inner packet header, the obtained IOAM information and the IOAM information of the egress gateway 2 are added to the new outer tunnel header, and the data packet after encapsulating the new outer tunnel header is exported from the egress gateway 2 issue.
  • Step 508 During the VXLAN tunnel between the egress gateway 2 and the access gateway 2, the data packet adds the IOAM information of the local node to the IOAM information part of the outer tunnel header (that is, the VXLAN tunnel header).
  • Step 509 The access gateway 2 in the data center network 2 receives the data packet encapsulated by the VXLAN tunnel header carrying the IOAM information sent from the egress gateway 2 direction.
  • the access gateway 2 is an IOAM termination point.
  • the access gateway 2 strips the data packet of the outer tunnel header and the inner packet header and forwards it normally, and the data packet is forwarded to the server 2.
  • Step 510 Since the access gateway 2 is the IOAM termination point in this example, the access gateway 2 will obtain the IOAM information from the data packet and add the IOAM information of the access gateway 2, which is agreed with the collector Transmission method, send IOAM information to the collector for processing.
  • the egress gateway 1 of the data center network 1 and the egress gateway 2 of the data center network 2 are respectively spliced with different types of tunnels, that is, the tunnel type between the access gateway and the egress gateway is VXLAN tunnel type, the tunnel type between egress gateways is Multi-Protocol Label Switching (MPLS), and egress gateway 1 supports adding IOAM information to MPLS tunnels.
  • the method includes:
  • Step 600 The egress gateway 1 receives the data message carrying the IOAM information sent from the access gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to the VXLAN tunnel type, and the original outer tunnel header carries the IOAM information.
  • Step 601 The egress gateway 1 determines whether the egress gateway 1 is the end point of the current tunnel (that is, a VXLAN tunnel type tunnel) according to the original outer tunnel header of the data packet.
  • the IOAM information is obtained from the original outer tunnel header of the data packet; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the egress gateway 1 are obtained.
  • Step 602 The egress gateway 1 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is of the MPLS tunnel type.
  • Step 603 The egress gateway 1 determines whether the egress gateway 1 supports adding IOAM information to the MPLS tunnel type. In the case that the egress gateway 1 supports adding IOAM information to the MPLS tunnel type, the egress gateway 1 encapsulates the new outer layer corresponding to the MPLS tunnel type in the outer layer When the tunnel header is added, the cached IOAM information, or the cached IOAM information and the IOAM information of the egress gateway 1 are added to the new outer tunnel header, and the data message encapsulated by the new outer tunnel header is sent from the egress gateway 1.
  • Step 604 During the process of the data packet passing through the tunnel between the egress gateway 1 and the egress gateway 2, the intermediate network node performs MPLS forwarding, and the experienced network node adds the IOAM information of the local node to the outer tunnel header.
  • Step 605 The egress gateway 2 receives the data message carrying the IOAM information sent by the egress gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to the MPLS tunnel type, and the original outer tunnel header carries the IOAM information.
  • Step 606 The egress gateway 2 determines whether the egress gateway 2 is the end point of the current tunnel (that is, an MPLS tunnel type tunnel) according to the original outer tunnel header of the data packet.
  • the exit gateway 2 obtains IOAM information from the original outer tunnel header; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the exit gateway 2, strip the datagram
  • the original outer tunnel header of the document, and the forwarding table is checked according to the inner packet header to determine that the exit is a VXLAN tunnel type tunnel.
  • Step 607 The egress gateway 2 determines whether the egress gateway 2 supports adding IOAM information to the VXLAN tunnel type. In the case that the egress gateway 2 supports adding IOAM information to the VXLAN tunnel type, the egress gateway 2 will cache the IOAM information or the cached IOAM information. Add the IOAM information of the egress gateway 2 to the new outer tunnel header, encapsulate the new outer tunnel header corresponding to the VXLAN tunnel type in the outer layer of the data packet, and encapsulate the data packet after the new outer tunnel header from the egress gateway 2 issue.
  • Step 608 When the data packet passes through the VXLAN tunnel between the egress gateway 2 and the access gateway 2, the intermediate network node adds the IOAM information of the node to the IOAM information portion in the outer tunnel header (that is, the VXLAN tunnel header).
  • Step 609 The access gateway 2 in the data center network 2 receives the data message encapsulated by the VXLAN tunnel header carrying the IOAM information sent from the direction of the egress gateway 2.
  • the access gateway 2 is an IOAM termination point.
  • the access gateway 2 strips the data packet of the outer tunnel header and the inner packet header and forwards it normally, and the data packet is forwarded to the server 2.
  • Step 610 In this example, because the access gateway 2 is the IOAM termination point, the access gateway 2 will obtain the IOAM information from the data packet, and add the IOAM information of the access gateway 2, through the agreement with the collector Transmission method, send IOAM information to the collector for processing.
  • the egress gateway 1 of the data center network 1 and the egress gateway 2 of the data center network 2 are respectively spliced with the same type of tunnel, that is, the tunnel type between the access gateway and the egress gateway is VXLAN tunnel type, the tunnel type between egress gateways is still VXLAN tunnel type, and egress gateway 1 supports adding IOAM information to VXLAN tunnels.
  • the method includes:
  • Step 700 The egress gateway 1 receives the data message carrying the IOAM information sent by the access gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to the VXLAN tunnel type, and the original outer tunnel header carries the IOAM information.
  • Step 701 The egress gateway 1 determines whether the egress gateway 1 is the end point of the current tunnel (that is, a VXLAN tunnel type tunnel) according to the original outer tunnel header of the data packet.
  • the IOAM information is obtained from the original outer tunnel header of the data packet; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the egress gateway 1 are obtained.
  • Step 702 The egress gateway 1 strips the original outer tunnel header of the data packet, and checks the forwarding table according to the inner packet header to determine that the egress is still of the VXLAN tunnel type. Therefore, the tunnel header corresponding to the new VXLAN tunnel type needs to be encapsulated.
  • Step 703 The egress gateway 1 determines whether the egress gateway 1 supports adding IOAM information to the VXLAN tunnel type. When the egress gateway 1 supports adding IOAM information to the MPLS tunnel type, the egress gateway 1 encapsulates the new outer layer corresponding to the VXLAN tunnel type in the outer layer When the tunnel header is added, the cached IOAM information, or the cached IOAM information and the IOAM information of the egress gateway 1 are added to the new outer tunnel header, and the data message encapsulated by the new outer tunnel header is sent from the egress gateway 1.
  • Step 704 During the process of the data packet passing through the tunnel between the egress gateway 1 and the egress gateway 2, the intermediate network node performs VXLAN forwarding, and the experienced network node adds the IOAM information of the local node to the outer tunnel header.
  • Step 705 The egress gateway 2 receives the data message carrying the IOAM information sent from the egress gateway 1, the original outer tunnel header is encapsulated into a tunnel header corresponding to the VXLAN tunnel type, and the original outer tunnel header carries the IOAM information.
  • Step 706 The egress gateway 2 determines whether the egress gateway 2 is the end point of the current tunnel (that is, a VXLAN tunnel type tunnel) according to the original outer tunnel header of the data packet, and the egress gateway 2 determines the egress gateway 2 according to the original outer tunnel header of the data packet.
  • the exit gateway 2 obtains IOAM information from the original outer tunnel header; the IOAM information obtained by the cache, or the IOAM information obtained by the cache and the IOAM information of the exit gateway 2, strip the datagram
  • the original outer tunnel header of the document, and the forwarding table is checked according to the inner packet header to determine that the exit is a VXLAN tunnel type tunnel.
  • Step 707 The egress gateway 2 determines whether the egress gateway 2 supports adding IOAM information to the VXLAN tunnel type. In the case where the egress gateway 2 supports adding IOAM information to the VXLAN tunnel type, the egress gateway 2 will cache the IOAM information or the cached IOAM information The IOAM information of the egress gateway 2 is added to the new outer tunnel header, the tunnel header corresponding to the VXLAN tunnel type is encapsulated in the new outer layer of the data packet, and the data message after encapsulating the new outer tunnel header is sent from the egress gateway 2.
  • Step 708 During the process of the data packet passing through the VXLAN tunnel between the egress gateway 2 and the access gateway 2, the intermediate network node adds the IOAM information of the local node to the IOAM information part in the outer tunnel header (that is, the VXLAN tunnel header).
  • Step 709 The access gateway 2 in the data center network 2 receives the data message encapsulated by the VXLAN tunnel header carrying the IOAM information sent from the egress gateway 2 direction.
  • the access gateway 2 is an IOAM termination point.
  • the access gateway 2 strips the data packet of the outer tunnel header and the inner packet header and forwards it normally, and the data packet is forwarded to the server 2.
  • Step 710 the access gateway 2 will obtain the IOAM information from the data packet, and add the IOAM information of the access gateway 2, through the agreement with the collector Transmission method, send IOAM information to the collector for processing.
  • FIG. 4 another embodiment of the present application provides an apparatus for processing IOAM information, including:
  • the receiving module 801 is configured to receive data packets
  • the processing module 802 is configured to strip the original outer tunnel header of the data packet to determine the tunnel type of the egress if the local node is determined to be the end point of the current tunnel according to the original outer tunnel header of the data packet ; According to whether this node supports adding IOAM information to the exit tunnel type, add the IOAM information in the data packet and the IOAM information of this node to the data packet; corresponding to the tunnel type of the data packet encapsulation exit The new outer tunnel header is sent to the next node.
  • the processing module 802 may check the forwarding table according to the inner packet header to obtain the exit tunnel encapsulation information, and determine the exit tunnel type according to the tunnel feature field in the exit tunnel encapsulation information.
  • the processing module 802 may store the exit tunnel type in a custom field in the exit tunnel encapsulation information, and the exit tunnel type may be determined according to the exit tunnel type of the exit tunnel encapsulation information; or, according to the Other existing fields determine the exit tunnel type.
  • the processing module 802 is configured to use at least one of the following methods to implement the addition of IOAM information according to whether the node's exit tunnel type supports adding IOAM information in the data packet to the node's IOAM Information is added to the data message:
  • the IOAM information in the original outer tunnel header or the inner packet header of the data packet and the IOAM information of the local node are added Added to the new outer tunnel header corresponding to the tunnel type of the egress of the data packet.
  • the processing module 802 is further configured to: obtain the IOAM information from the original outer tunnel header of the data packet; cache the obtained IOAM information, and combine the cached IOAM information with the local node IOAM information is added to the inner header of the data packet; or, the IOAM information is obtained from the original outer tunnel header of the data packet; the obtained IOAM information is cached and the IOAM of the local node Information; add the cached IOAM information to the inner packet header of the data packet.
  • the processing module 802 is configured to implement at least one of the following ways to determine whether the local node supports the addition of IOAM information to the type of the tunnel:
  • the pre-configured tunnel type that supports the addition of IOAM information determine whether the node's exit tunnel type supports the addition of IOAM information; as an embodiment, the pre-configured tunnel type that supports the addition of IOAM information includes the exit tunnel type of the node In the case of, it is determined that the local node supports the addition of IOAM information to the tunnel type of the exit; if the pre-configured tunnel type that supports IOAM information does not include the tunnel type of the exit of the node, the tunnel type of the local node to the exit is determined Does not support adding IOAM information; Among them, the pre-configured tunnel type that supports adding IOAM information can be manually configured;
  • the pre-configured tunnel type that does not support the addition of IOAM information determine whether the node's exit tunnel type supports the addition of IOAM information; as an embodiment, the pre-configured tunnel type that does not support the addition of IOAM information includes the exit of the node In the case of the tunnel type, it is determined that the node does not support adding IOAM information to the egress tunnel type; when the pre-configured tunnel type that does not support IOAM information does not include the egress tunnel type of the node, it is determined that the node is The exit tunnel type supports adding IOAM information; among them, the pre-configured tunnel type that does not support adding IOAM information can be manually configured;
  • the packet type specified in draft-brockners-inband-oam-transport or draft-brockners-ippm-ioam-geneve of IOAM draft determine whether the node supports the addition of IOAM information to the type of egress tunnel; as an implementation method, in IOAM If the packet type specified in the draft includes the packet type of the data packet, it is determined that the local node supports adding IOAM information to the egress tunnel type; the packet type specified in the IOAM draft does not include the packet of the data packet In the case of the type, it is judged that the local node does not support adding IOAM information to the exit tunnel type.
  • the IOAM information in the original outer tunnel header of the data packet and the local node IOAM information is added to the inner header of the data packet, which realizes the transmission of IOAM information in the tunnel splicing scenario, avoids the loss of IOAM information caused by the end of the tunnel, and thus continuously obtains IOAM information to provide decision-making for the network guide.
  • the local node when the local node is the end point of the current tunnel and the local node supports the addition of IOAM information to the exit tunnel type, the IOAM information and the IOAM information in the outer tunnel header or inner packet header of the data packet are added.
  • the IOAM information of this node is added to the outer tunnel header of the data packet, which realizes the transmission of IOAM information in the tunnel splicing scenario, avoids the loss of IOAM information caused by the end of the tunnel, and thus continuously obtains IOAM information for the network Provide decision-making guidance.
  • the processing module 802 is further configured to: if it is determined that the local node is not the end point of the current tunnel according to the original outer tunnel header of the data packet, execute at least one of the following One:
  • the outer tunnel header of the data packet contains the IOAM information
  • the data packet is sent to the next node.
  • the specific implementation process of the foregoing IOAM information processing apparatus is the same as the specific implementation process of the IOAM information processing method of the foregoing embodiment, and details are not described herein again.
  • Another embodiment of the present application provides an apparatus for processing IOAM information, including a processor and a computer-readable storage medium.
  • the computer-readable storage medium stores instructions, and when the instructions are executed by the processor, Implement any of the above IOAM information processing methods.
  • Another embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the foregoing IOAM information processing methods are implemented.
  • computer storage media includes both 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 RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium for storing desired information and accessible by a computer.
  • the communication medium generally contains computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种带内操作管理维护(IOAM)信息的处理方法和装置，所述IOAM信息的处理方法包括：接收到数据报文；在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。

Description

一种IOAM信息的处理方法和装置
本申请要求在2018年12月05日提交中国专利局、申请号为201811482361.9的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及但不限于网络通信技术，尤指一种带内操作管理维护(OAM，Operations Administration and Maintenance)(IOAM，In-band OAM或In-situ OAM)信息的处理方法和装置。
背景技术
数据中心网络对时延、丢包、转发路径及可靠性等提出更高要求的同时，也迫切需要一种网络可视化技术能够持续获取网络的运行数据，从而为网络排障、网络规划和流量调优等提供决策指导。
In-band OAM正是解决数据中心网络可视化的一种带内OAM技术，随着大容量、高速、编程芯片、编程协议独立包处理器(P4，Programming Protocol-Independent Packet Processors)等技术的发展，带内OAM技术也逐渐被提出并得到应用。目前在技术草案上主要是国际互联网工程任务组(IETF，The Internet Engineering Task Force)的In-situ OAM，或称为In-band OAM，后面简称IOAM。
IOAM相关草案对在网络中使用通用路由封装协议(GRE，Generic Routing Encapsulation)、互联网协议第6版(IPV6，Internet Protocol Version 6)、虚拟扩展局域网(VXLAN，Virtual Extensible局域网(LAN，Local Area Network))、网络服务主机(NSH，Network Service Host)、分段路由(SR，Segment Routing)作为传输协议的方法做了说明，但目前草案尚未对隧道拼接的场景提出IOAM的解决方案。
发明内容
本申请实施例提供了一种IOAM信息的处理方法和装置，能够实现隧道拼接场景下IOAM信息的传递，避免隧道终结时造成的IOAM信息的丢失。
本申请实施例提供了一种IOAM信息的处理方法，包括：
接收到数据报文；
在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情 况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；
根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；
对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。
本申请实施例提供了一种IOAM信息的处理装置，包括：
接收模块，配置为接收到数据报文；
处理模块，配置为在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。
本申请实施例提供了一种IOAM信息的处理装置，包括处理器和计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令被所述处理器执行时，实现上述任一种IOAM信息的处理方法。
本申请实施例提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任一种IOAM信息的处理方法的步骤。
本申请实施例包括：接收到数据报文；在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。本申请实施例在本节点为当前隧道的终结点，根据本节点对出口的隧道类型是否支持添加IOAM信息，将将所述数据报文中的IOAM信息和本节点的IOAM信息添加到所述数据报文中，实现了隧道拼接场景下IOAM信息的传递，避免了隧道终结时造成的IOAM信息的丢失，从而持续获取IOAM信息来为网络提供决策指导。
本申请实施例的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请实施例而了解。本申请实施例的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请实施例技术方案的进一步理解，并且构成说明书的一部分，与本申请实施例的实施例一起用于解释本申请实施例的技术方案，并不构成对本申请实施例技术方案的限制。
图1(a)为本申请实施例同类隧道在出口网关进行拼接的拓扑示意图一；
图1(b)为本申请实施例异类隧道在出口网关进行拼接的拓扑示意图一；
图2为本申请一个实施例提出的IOAM信息的处理方法的流程图；
图3(a)为本申请实施例同类隧道在出口网关进行拼接的拓扑示意图二；
图3(b)为本申请实施例异类隧道在出口网关进行拼接的拓扑示意图二；
图4为本申请另一个实施例提出的IOAM信息的处理装置的结构组成示意图。
具体实施方式
下文中将结合附图对本申请实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
在数据中心应用场景中，有两种隧道拼接的情况。一种情况是同类隧道在出口网关进行拼接，另一种情况是异类隧道在出口网关进行拼接。
图1(a)为本申请实施例同类隧道在出口网关进行拼接的拓扑示意图。如图1(a)所示，出口网关连接的是两个相同类型的隧道。例如数据中心(DC，Data Center)内部覆盖(overlay)网络隧道类型为隧道类型1，DC间的隧道类型仍为隧道类型1，但这时候出口网关需要做原有隧道终结后再重新封装新的隧道，所以仍然称作隧道拼接。此时也需要支持IOAM信息在隧道间的传递。
图1(b)为本申请实施例异类隧道在出口网关进行拼接的拓扑示意图。如图1(b)所示，出口网关连接的是两个不同类型的隧道。例如DC内部overlay网络隧道类型为隧道类型1，DC间的网络隧道为隧道类型2。这种场景下，两个DC内部的节点在跨DC进行IOAM报文传输时在DC出口网关需要进行隧道拼接，隧道拼接的同时需要支持IOAM信息在不同隧道间的传递。
需要说明的是本申请实施例以数据中心网络为例来说明隧道拼接的场景，实际上本申请实施例不局限于应用在数据中心网络，适用于包含所有隧道拼接的网络场景；同时，本申请实施例也不仅仅局限于两个网络之间的隧道拼接， 同一个网络内部的隧道拼接以及两个以上网络之间的隧道拼接也在本申请实施例的保护范围内。
相关技术中在IOAM信息的传输过程中如遇到隧道终结，则丢弃IOAM信息，使得IOAM信息在传输过程中丢失，从而无法持续获取IOAM信息来为网络提供决策指导。
参见图2，本申请一个实施例提出了一种IOAM信息的处理方法，包括：
步骤200、接收到数据报文。
步骤201、在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型。
在本申请实施例中，可以根据内层报文头查转发表获取出口隧道封装信息，根据出口隧道封装信息中的隧道特征字段确定出口的隧道类型。
其中，可以在出口隧道封装信息中自定义字段存储出口的隧道类型，根据出口隧道封装信息的出口的隧道类型即可确定出口的隧道类型；或者，根据出口隧道封装信息中的其他现有字段来确定出口的隧道类型。
在本申请实施例中，在所述数据报文的原外层隧道头包含所述IOAM信息的情况下，所述剥离数据报文的外层隧道头之前，该方法还包括：从所述数据报文的原外层隧道头获取所述IOAM信息；缓存获得的IOAM信息，或缓存获得的IOAM信息和所述本节点的IOAM信息。
步骤202、根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中。
在本申请实施例中，根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中包括以下至少之一：
在判断出本节点对出口的隧道类型不支持添加IOAM信息的情况下，将所述数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的内层报文头中；
在判断出所述本节点对所述出口的隧道类型支持添加IOAM信息的情况下，将所述数据报文的原外层隧道头或内层报文头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的出口的隧道类型对应的新外层隧道头中。
在本申请实施例中，判断本节点对出口的隧道类型是否支持添加IOAM信息包括以下至少之一：
根据预先配置的支持添加IOAM信息的隧道类型判断本节点对出口的隧道 类型是否支持添加IOAM信息；作为一种实施方式，在预先配置的支持添加IOAM信息的隧道类型包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型支持添加IOAM信息；在预先配置的支持IOAM信息的隧道类型不包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型不支持添加IOAM信息；其中，预先配置的支持添加IOAM信息的隧道类型可以手动配置；
根据预先配置的不支持添加IOAM信息的隧道类型判断本节点对出口的隧道类型是否支持添加IOAM信息；作为一种实施方式，在预先配置的不支持添加IOAM信息的隧道类型包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型不支持添加IOAM信息；在预先配置的不支持IOAM信息的隧道类型不包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型支持添加IOAM信息；其中，预先配置的不支持添加IOAM信息的隧道类型可以手动配置；
根据IOAM草案draft-brockners-inband-oam-transport或draft-brockners-ippm-ioam-geneve中规定的报文类型判断本节点对出口的隧道类型是否支持添加IOAM信息；作为一种实施方式，在IOAM草案中规定的报文类型包括数据报文的报文类型的情况下，判断出本节点对出口的隧道类型支持添加IOAM信息；在IOAM草案中规定的报文类型不包括数据报文的报文类型的情况下，判断出本节点对出口的隧道类型不支持添加IOAM信息。
在本申请实施例中，将数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到数据报文的内层报文头中包括：
在步骤201中缓存数据报文的外层隧道头中的IOAM信息的情况下，将缓存的IOAM信息和所述本节点的IOAM信息添加到所述数据报文的内层报文头中；
或者，在步骤201中缓存数据报文的外层隧道头中的IOAM信息和本节点的IOAM信息的情况下，将缓存的IOAM信息添加到所述数据报文的内层报文头中。
在本申请一个实施例中，将IOAM信息添加到内层报文头的具体位置可以自定义，如自定义的私有的用户数据报协议(UDP，User Datagram Protocol)和传输控制协议(TCP，Transmission Control Protocol)端口号。
在本申请另一个实施例中，将IOAM信息添加到内层报文头的具体位置可以按照IOAM草案draft-brockners-inband-oam-transport中对各种类型报文承载IOAM信息的报文格式定义。
本申请实施例在本节点为当前隧道的终结点，且本节点对出口的隧道类型不支持添加IOAM信息时，将将所述数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的内层报文头中，实现了隧道拼接场景下IOAM信息的传递，避免了隧道终结时造成的IOAM信息的丢失，从而持续获取IOAM信息来为网络提供决策指导。
其中，将IOAM信息添加到数据报文的新外层隧道头的具体位置可以按照IOAM草案draft-brockners-inband-oam-transport或draft-brockners-ippm-ioam-geneve中对各种类型报文承载IOAM信息的报文格式定义。
步骤203、对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。
本申请实施例在本节点为当前隧道的终结点，且根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到所述数据报文中，实现了隧道拼接场景下IOAM信息的传递，避免了隧道终结时造成的IOAM信息的丢失，从而持续获取IOAM信息来为网络提供决策指导。
在本申请另一个实施例中，在根据所述数据报文的原外层隧道头确定所述本节点不是当前隧道的终结点的情况下，该方法还包括以下至少之一：
在所述数据报文的原外层隧道头包含所述IOAM信息的情况下，将本节点的IOAM信息添加到所述数据报文的原外层隧道头中，将所述数据报文发送给下一个节点；
在所述数据报文的外层隧道头不包含所述IOAM信息的情况下，将所述数据报文发送给下一个节点。
下面通过具体示例详细说明本申请实施例的具体实现过程，所举的例子不用于限定本申请实施例的IOAM信息的处理方法的保护范围。
示例1
本示例中，如图1(b)所示，数据中心网络1的出口网关1和数据中心网络2的出口网关2分别拼接不同类型的隧道，并且出口网关1不支持对隧道类型2添加IOAM信息。该方法包括：
步骤300、出口网关1接收到了接入网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为隧道类型1对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在接入网关1和出口网关1之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤301、出口网关1根据数据报文的原外层隧道头确定出口网关1是否为当前隧道(即隧道类型1的隧道)的终结点，在出口网关1根据数据报文的原外层隧道头确定出口网关1为当前隧道的终结点的情况下，从数据报文的原外层隧道头中获取IOAM信息；缓存获得的IOAM信息，或缓存获得的IOAM信息和出口网关1的IOAM信息。
步骤302、出口网关1剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为隧道类型2的隧道。
步骤303、出口网关1判断出口网关1对隧道类型2是否支持添加IOAM信息，在出口网关1对隧道类型2不支持添加IOAM信息的情况下，出口网关1把缓存的IOAM信息、或缓存的IOAM信息和出口网关1的IOAM信息添加到内层报文头，并在外层封装隧道类型2对应的新外层隧道头后从出口网关1发出。
步骤304、数据报文在经过出口网关1和出口网关2之间的隧道的过程中，所经历的网络节点不再添加IOAM信息。
步骤305、出口网关2接收到了出口网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为隧道类型2对应的隧道头，原外层隧道头中不携带IOAM信息。
本步骤中，在出口网关1和出口网关2之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤306、出口网关2根据数据报文的原外层隧道头确定出口网关2是否为当前隧道(即隧道类型2的隧道)的终结点，在出口网关2根据数据报文的原外层隧道头确定出口网关2为当前隧道的终结点的情况下，出口网关2剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为隧道类型1的隧道。
步骤307、出口网关2判断出口网关2对隧道类型1是否支持添加IOAM信息，在出口网关2对隧道类型1支持添加IOAM信息的情况下，出口网关2在外层封装隧道类型1对应的新外层隧道头时，从内层报文头获取IOAM信息，将获得的IOAM信息和出口网关2的IOAM信息添加到新外层隧道头，将封装新外层隧道头后的数据报文从出口网关2发出。
示例2
本示例中，如图1(b)所示，数据中心网络1的出口网关1和数据中心网 络2的出口网关2分别拼接不同类型的隧道，并且出口网关1支持对隧道类型2添加IOAM信息。该方法包括：
步骤400、出口网关1接收到了接入网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为隧道类型1对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在接入网关1和出口网关1之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤401、出口网关1根据数据报文的原外层隧道头确定出口网关1是否为当前隧道(即隧道类型1的隧道)的终结点，在出口网关1根据数据报文的原外层隧道头确定出口网关1为当前隧道的终结点的情况下，从数据报文的原外层隧道头中获取IOAM信息；缓存获得的IOAM信息，或缓存获得的IOAM信息和出口网关1的IOAM信息。
步骤402、出口网关1剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为隧道类型2的隧道。
步骤403、出口网关1判断出口网关1对隧道类型2是否支持添加IOAM信息，在出口网关1对隧道类型2支持添加IOAM信息的情况下，出口网关1在外层封装隧道类型2对应的新外层隧道头时，把缓存的IOAM信息、或缓存的IOAM信息和出口网关1的IOAM信息添加到新外层隧道头，将封装新外层隧道头后的数据报文从出口网关1发出。
步骤404、数据报文在经过出口网关1和出口网关2之间的隧道时，所经历的网络节点继续添加IOAM信息。
步骤405、出口网关2接收到了出口网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为隧道类型2对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在出口网关1和出口网关2之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤406、出口网关2根据数据报文的原外层隧道头确定出口网关2是否为当前隧道(即隧道类型2的隧道)的终结点，在出口网关2根据数据报文的原外层隧道头确定出口网关2为当前隧道的终结点的情况下，出口网关2从数据报文的原外层隧道头获取IOAM信息；缓存获得的IOAM信息、或缓存获得的IOAM信息和出口网关2的IOAM信息，剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为隧道类型1的隧道。
步骤407、出口网关2判断出口网关2对隧道类型1是否支持添加IOAM信 息，在出口网关2对隧道类型1支持添加IOAM信息的情况下，出口网关2在外层封装隧道类型1对应的新外层隧道头时，将缓存的IOAM信息、或缓存的IOAM信息和出口网关2的IOAM信息添加到新外层隧道头，将封装新外层隧道头后的数据报文从出口网关2发出。
示例3
本示例中，如图3(b)所示，数据中心网络1的出口网关1和数据中心网络2的出口网关2分别拼接不同类型的隧道，即接入网关和出口网关之间的隧道类型为VXLAN隧道类型，出口网关之间的隧道类型为多协议标签交换(MPLS，Multi-Protocol Label Switching)隧道类型，并且出口网关1不支持对MPLS隧道添加IOAM信息。该方法包括：
步骤500、出口网关1接收到了接入网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为VXLAN隧道类型对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在接入网关1和出口网关1之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤501、出口网关1根据数据报文的原外层隧道头确定出口网关1是否为当前隧道(即VXLAN隧道类型的隧道)的终结点，在出口网关1根据数据报文的原外层隧道头确定出口网关1为当前隧道的终结点的情况下，从数据报文的原外层隧道头中获取IOAM信息；缓存获得的IOAM信息，或缓存获得的IOAM信息和出口网关1的IOAM信息。
步骤502、出口网关1剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为MPLS隧道类型。
步骤503、出口网关1判断出口网关1对MPLS隧道类型是否支持添加IOAM信息，在出口网关1对MPLS隧道类型不支持添加IOAM信息的情况下，出口网关1把缓存的IOAM信息、或缓存的IOAM信息和出口网关1的IOAM信息添加到内层报文头，并在外层封装MPLS隧道类型对应的新外层隧道头后从出口网关1发出。
步骤504、数据报文在经过出口网关1和出口网关2之间的隧道时，中间网络节点进行MPLS转发，所经历的网络节点不再添加IOAM信息。
步骤505、出口网关2接收到了出口网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为MPLS隧道类型对应的隧道头，原外层隧道头中不携带IOAM信息。
本步骤中，在出口网关1和出口网关2之间存在其他网络设备节点的情况， 也在本申请实施例的保护范围之内。
步骤506、出口网关2根据数据报文的原外层隧道头确定出口网关2是否为当前隧道(即MPLS隧道类型的隧道)的终结点，在出口网关2根据数据报文的原外层隧道头确定出口网关2为当前隧道的终结点的情况下，出口网关2剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为VXLAN隧道类型的隧道。
步骤507、出口网关2判断出口网关2对VXLAN隧道类型是否支持添加IOAM信息，在出口网关2对VXLAN隧道类型支持添加IOAM信息的情况下，出口网关2在外层封装VXLAN隧道类型对应的新外层隧道头时，从内层报文头获取IOAM信息，将获得的IOAM信息和出口网关2的IOAM信息添加到新外层隧道头，将封装新外层隧道头后的数据报文从出口网关2发出。
步骤508、数据报文在经过出口网关2和接入网关2之间的VXLAN隧道过程中，中间网络节点添加本节点的IOAM信息到外层隧道头(即VXLAN隧道头)中IOAM信息部分。
步骤509、数据中心网络2中的接入网关2收到出口网关2方向发过来的携带IOAM信息的VXLAN隧道头封装的数据报文。
在本示例中接入网关2为IOAM的终结点，接入网关2对数据报文剥去外层隧道头和内层报文头后正常转发，数据报文被转发给服务器2。
步骤510、因为在本示例中接入网关2为IOAM的终结点，接入网关2会从数据报文获取IOAM信息，并增加接入网关2的IOAM信息，通过和收集器之间约定好的传输方式，把IOAM信息发送给收集器处理。
示例4
本示例中，如图3(b)所示，数据中心网络1的出口网关1和数据中心网络2的出口网关2分别拼接不同类型的隧道，即接入网关和出口网关之间的隧道类型为VXLAN隧道类型，出口网关之间的隧道类型为多协议标签交换(MPLS，Multi-Protocol Label Switching)隧道类型，并且出口网关1支持对MPLS隧道添加IOAM信息。该方法包括：
步骤600、出口网关1接收到了接入网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为VXLAN隧道类型对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在接入网关1和出口网关1之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤601、出口网关1根据数据报文的原外层隧道头确定出口网关1是否为当前隧道(即VXLAN隧道类型的隧道)的终结点，在出口网关1根据数据报文的原外层隧道头确定出口网关1为当前隧道的终结点的情况下，从数据报文的原外层隧道头中获取IOAM信息；缓存获得的IOAM信息，或缓存获得的IOAM信息和出口网关1的IOAM信息。
步骤602、出口网关1剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为MPLS隧道类型。
步骤603、出口网关1判断出口网关1对MPLS隧道类型是否支持添加IOAM信息，在出口网关1对MPLS隧道类型支持添加IOAM信息的情况下，出口网关1在外层封装MPLS隧道类型对应的新外层隧道头时，把缓存的IOAM信息、或缓存的IOAM信息和出口网关1的IOAM信息添加到新外层隧道头，将封装新外层隧道头后的数据报文从出口网关1发出。
步骤604、数据报文在经过出口网关1和出口网关2之间的隧道的过程中，中间网络节点进行MPLS转发，所经历的网络节点添加本节点的IOAM信息到外层隧道头中。
步骤605、出口网关2接收到了出口网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为MPLS隧道类型对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在出口网关1和出口网关2之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤606、出口网关2根据数据报文的原外层隧道头确定出口网关2是否为当前隧道(即MPLS隧道类型的隧道)的终结点，在出口网关2根据数据报文的原外层隧道头确定出口网关2为当前隧道的终结点的情况下，出口网关2从原外层隧道头获取IOAM信息；缓存获得的IOAM信息、或缓存获得的IOAM信息和出口网关2的IOAM信息，剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为VXLAN隧道类型的隧道。
步骤607、出口网关2判断出口网关2对VXLAN隧道类型是否支持添加IOAM信息，在出口网关2对VXLAN隧道类型支持添加IOAM信息的情况下，出口网关2将缓存的IOAM信息、或缓存的IOAM信息和出口网关2的IOAM信息添加到新外层隧道头，在数据报文的外层封装VXLAN隧道类型对应的新外层隧道头，将封装新外层隧道头后的数据报文从出口网关2发出。
步骤608、数据报文在经过出口网关2和接入网关2之间的VXLAN隧道时，中间网络节点添加本节点的IOAM信息到外层隧道头(即VXLAN隧道头)中 IOAM信息部分。
步骤609、数据中心网络2中的接入网关2收到出口网关2方向发过来的携带IOAM信息的VXLAN隧道头封装的数据报文。
在本示例中接入网关2为IOAM的终结点，接入网关2对数据报文剥去外层隧道头和内层报文头后正常转发，数据报文被转发给服务器2。
步骤610、因为在本示例中接入网关2为IOAM的终结点，接入网关2会从数据报文获取IOAM信息，并增加接入网关2的IOAM信息，通过和收集器之间约定好的传输方式，把IOAM信息发送给收集器处理。
示例5
本示例中，如图3(a)所示，数据中心网络1的出口网关1和数据中心网络2的出口网关2分别拼接相同类型的隧道，即接入网关和出口网关之间的隧道类型为VXLAN隧道类型，出口网关之间的隧道类型仍然为VXLAN隧道类型，并且出口网关1支持对VXLAN隧道添加IOAM信息。
该方法包括：
步骤700、出口网关1接收到了接入网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为VXLAN隧道类型对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在接入网关1和出口网关1之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤701、出口网关1根据数据报文的原外层隧道头确定出口网关1是否为当前隧道(即VXLAN隧道类型的隧道)的终结点，在出口网关1根据数据报文的原外层隧道头确定出口网关1为当前隧道的终结点的情况下，从数据报文的原外层隧道头中获取IOAM信息；缓存获得的IOAM信息，或缓存获得的IOAM信息和出口网关1的IOAM信息。
步骤702、出口网关1剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口仍为VXLAN隧道类型，因此需要封装新的VXLAN隧道类型对应的隧道头。
步骤703、出口网关1判断出口网关1对VXLAN隧道类型是否支持添加IOAM信息，在出口网关1对MPLS隧道类型支持添加IOAM信息的情况下，出口网关1在外层封装VXLAN隧道类型对应的新外层隧道头时，把缓存的IOAM信息、或缓存的IOAM信息和出口网关1的IOAM信息添加到新外层隧道头，将封装新外层隧道头后的数据报文从出口网关1发出。
步骤704、数据报文在经过出口网关1和出口网关2之间的隧道的过程中，中间网络节点进行VXLAN转发，所经历的网络节点添加本节点的IOAM信息到外层隧道头中。
步骤705、出口网关2接收到了出口网关1方向发来的携带IOAM信息的数据报文，原外层隧道头封装为VXLAN隧道类型对应的隧道头，原外层隧道头中携带IOAM信息。
本步骤中，在出口网关1和出口网关2之间存在其他网络设备节点的情况，也在本申请实施例的保护范围之内。
步骤706、出口网关2根据数据报文的原外层隧道头确定出口网关2是否为当前隧道(即VXLAN隧道类型的隧道)的终结点，在出口网关2根据数据报文的原外层隧道头确定出口网关2为当前隧道的终结点的情况下，出口网关2从原外层隧道头获取IOAM信息；缓存获得的IOAM信息、或缓存获得的IOAM信息和出口网关2的IOAM信息，剥离数据报文的原外层隧道头，根据内层报文头查转发表确定出口为VXLAN隧道类型的隧道。
步骤707、出口网关2判断出口网关2对VXLAN隧道类型是否支持添加IOAM信息，在出口网关2对VXLAN隧道类型支持添加IOAM信息的情况下，出口网关2将缓存的IOAM信息、或缓存的IOAM信息和出口网关2的IOAM信息添加到新外层隧道头，在数据报文的新外层封装VXLAN隧道类型对应的隧道头，将封装新外层隧道头后的数据报文从出口网关2发出。
步骤708、数据报文在经过出口网关2和接入网关2之间的VXLAN隧道的过程中，中间网络节点添加本节点的IOAM信息到外层隧道头(即VXLAN隧道头)中IOAM信息部分。
步骤709、数据中心网络2中的接入网关2收到出口网关2方向发过来的携带IOAM信息的VXLAN隧道头封装的数据报文。
在本示例中接入网关2为IOAM的终结点，接入网关2对数据报文剥去外层隧道头和内层报文头后正常转发，数据报文被转发给服务器2。
步骤710、因为在本示例中接入网关2为IOAM的终结点，接入网关2会从数据报文获取IOAM信息，并增加接入网关2的IOAM信息，通过和收集器之间约定好的传输方式，把IOAM信息发送给收集器处理。
参见图4，本申请另一个实施例提出了一种IOAM信息的处理装置，包括：
接收模块801，配置为接收到数据报文；
处理模块802，配置为在根据所述数据报文的原外层隧道头确定本节点为当 前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。
在本申请一种可选实施例中，所述处理模块802可以根据内层报文头查转发表获取出口隧道封装信息，根据出口隧道封装信息中的隧道特征字段确定出口的隧道类型。
其中，所述处理模块802可以在出口隧道封装信息中自定义字段存储出口的隧道类型，根据出口隧道封装信息的出口的隧道类型即可确定出口的隧道类型；或者，根据出口隧道封装信息中的其他现有字段来确定出口的隧道类型。
在本申请实施例中，所述处理模块802配置为采用以下至少之一方式实现根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中：
在判断出本节点对出口的隧道类型不支持添加IOAM信息的情况下，将所述数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的内层报文头中；
在判断出所述本节点对所述出口的隧道类型支持添加IOAM信息的情况下，将所述数据报文的原外层隧道头或内层报文头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的出口的隧道类型对应的新外层隧道头中。
在本申请实施例中，所述处理模块802还配置为：从所述数据报文的原外层隧道头获取所述IOAM信息；缓存获得的IOAM信息，将缓存的IOAM信息和所述本节点的IOAM信息添加到所述数据报文的内层报文头中；或者，从所述数据报文的原外层隧道头获取所述IOAM信息；缓存获得的IOAM信息和所述本节点的IOAM信息；将缓存的IOAM信息添加到所述数据报文的内层报文头中。
在本申请实施例中，所述处理模块802配置为采用以下至少之一方式实现判断本节点对出口的隧道类型是否支持添加IOAM信息：
根据预先配置的支持添加IOAM信息的隧道类型判断本节点对出口的隧道类型是否支持添加IOAM信息；作为一种实施方式，在预先配置的支持添加IOAM信息的隧道类型包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型支持添加IOAM信息；在预先配置的支持IOAM信息的隧道类型不包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型不支持添加IOAM信息；其中，预先配置的支持添加IOAM信息的隧道类型可 以手动配置；
根据预先配置的不支持添加IOAM信息的隧道类型判断本节点对出口的隧道类型是否支持添加IOAM信息；作为一种实施方式，在预先配置的不支持添加IOAM信息的隧道类型包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型不支持添加IOAM信息；在预先配置的不支持IOAM信息的隧道类型不包含本节点的出口的隧道类型的情况下，判断出本节点对出口的隧道类型支持添加IOAM信息；其中，预先配置的不支持添加IOAM信息的隧道类型可以手动配置；
根据IOAM草案draft-brockners-inband-oam-transport或draft-brockners-ippm-ioam-geneve中规定的报文类型判断本节点对出口的隧道类型是否支持添加IOAM信息；作为一种实施方式，在IOAM草案中规定的报文类型包括数据报文的报文类型的情况下，判断出本节点对出口的隧道类型支持添加IOAM信息；在IOAM草案中规定的报文类型不包括数据报文的报文类型的情况下，判断出本节点对出口的隧道类型不支持添加IOAM信息。
本申请实施例在本节点为当前隧道的终结点，且本节点对出口的隧道类型不支持添加IOAM信息时，将将所述数据报文的原外层隧道头头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的内层报文头中，实现了隧道拼接场景下IOAM信息的传递，避免了隧道终结时造成的IOAM信息的丢失，从而持续获取IOAM信息来为网络提供决策指导。
本申请实施例在本节点为当前隧道的终结点，且本节点对出口的隧道类型支持添加IOAM信息时，将所述数据报文的外层隧道头或内层报文头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的外层隧道头中，实现了隧道拼接场景下IOAM信息的传递，避免了隧道终结时造成的IOAM信息的丢失，从而持续获取IOAM信息来为网络提供决策指导。
在本申请另一个实施例中，所述处理模块802还配置为：在根据所述数据报文的原外层隧道头确定所述本节点不是当前隧道的终结点的情况下，执行以下至少之一：
在所述数据报文的外层隧道头包含所述IOAM信息的情况下，将本节点的IOAM信息添加到所述数据报文的原外层隧道头中，将所述数据报文发送给下一个节点；
在所述数据报文的原外层隧道头不包含所述IOAM信息的情况下，将所述数据报文发送给下一个节点。
上述IOAM信息的处理装置的具体实现过程与前述实施例IOAM信息的处 理方法的具体实现过程相同，这里不再赘述。
本申请另一个实施例提出了一种IOAM信息的处理装置，包括处理器和计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令被所述处理器执行时，实现上述任一种IOAM信息的处理方法。
本申请另一个实施例提出了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任一种IOAM信息的处理方法的步骤。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本申请所提供的几个方法实施例中所揭露的方法，在不冲突的情况下可以任意组合，得到新的方法实施例。
本申请所提供的几个产品实施例中所揭露的特征，在不冲突的情况下可以任意组合，得到新的产品实施例。
本申请所提供的几个方法或设备实施例中所揭露的特征，在不冲突的情况下可以任意组合，得到新的方法实施例或设备实施例。
虽然本申请实施例所揭露的实施方式如上，但所述的内容仅为便于理解本申请实施例而采用的实施方式，并非用以限定本申请实施例。任何本申请实施例所属领域内的技术人员，在不脱离本申请实施例所揭露的精神和范围的前提 下，可以在实施的形式及细节上进行任何的修改与变化，但本申请实施例的专利保护范围，仍须以所附的权利要求书所界定的范围为准。

Claims (8)

  1. 一种带内操作管理维护IOAM信息的处理方法，包括：
    接收到数据报文；
    在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；
    根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；
    对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。
  2. 根据权利要求1所述的处理方法，其中，在根据所述数据报文的原外层隧道头确定所述本节点不是当前隧道的终结点的情况下，该方法还包括以下至少之一：
    在所述数据报文的原外层隧道头包含所述IOAM信息时，将本节点的IOAM信息添加到所述数据报文的原外层隧道头的情况下，将所述数据报文发送给下一个节点；
    在所述数据报文的原外层隧道头不包含所述IOAM信息的情况下，将所述数据报文发送给下一个节点。
  3. 根据权利要求1所述的处理方法，其中，所述根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中包括以下至少之一：
    在判断出本节点对出口的隧道类型不支持添加IOAM信息的情况下，将所述数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的内层报文头中；
    在判断出所述本节点对所述出口的隧道类型支持添加IOAM信息的情况下，将所述数据报文的原外层隧道头或内层报文头中的IOAM信息和本节点的IOAM信息添加到所述数据报文的出口的隧道类型对应的新外层隧道头中。
  4. 根据权利要求3所述的处理方法，其中，所述剥离数据报文的原外层隧道头之前，该方法还包括：
    从所述数据报文的原外层隧道头获取所述IOAM信息，缓存获得的IOAM信息；
    所述将数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到数据报文的内层报文头中包括：
    将缓存的IOAM信息和所述本节点的IOAM信息添加到所述数据报文的内层报文头中。
  5. 根据权利要求3所述的处理方法，其中，所述剥离数据报文的原外层隧道头之前，该方法还包括：
    从所述数据报文的原外层隧道头获取所述IOAM信息，缓存获得的IOAM信息和所述本节点的IOAM信息；
    所述将数据报文的原外层隧道头中的IOAM信息和本节点的IOAM信息添加到数据报文的内层报文头中包括：
    将缓存的IOAM信息添加到所述数据报文的内层报文头中。
  6. 一种带内操作管理维护IOAM信息的处理装置，包括：
    接收模块，配置为接收到数据报文；
    处理模块，配置为在根据所述数据报文的原外层隧道头确定本节点为当前隧道的终结点的情况下，剥离所述数据报文的原外层隧道头，确定出口的隧道类型；
    根据本节点对出口的隧道类型是否支持添加IOAM信息，将所述数据报文中的IOAM信息和本节点的IOAM信息添加到数据报文中；对所述数据报文封装出口的隧道类型对应的新外层隧道头后发送给下一个节点。
  7. 一种带内操作管理维护IOAM信息的处理装置，包括处理器和计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令被所述处理器执行时，实现如权利要求1至5任一项所述的IOAM信息的处理方法。
  8. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至5任一项所述的IOAM信息的处理方法的步骤。
PCT/CN2019/110790 2018-12-05 2019-10-12 一种ioam信息的处理方法和装置 Ceased WO2020114083A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19893323.6A EP3893435B1 (en) 2018-12-05 2019-10-12 Method and apparatus for processing ioam information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811482361.9A CN111277426B (zh) 2018-12-05 2018-12-05 一种ioam信息的处理方法和装置
CN201811482361.9 2018-12-05

Publications (1)

Publication Number Publication Date
WO2020114083A1 true WO2020114083A1 (zh) 2020-06-11

Family

ID=70974862

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/110790 Ceased WO2020114083A1 (zh) 2018-12-05 2019-10-12 一种ioam信息的处理方法和装置

Country Status (3)

Country Link
EP (1) EP3893435B1 (zh)
CN (1) CN111277426B (zh)
WO (1) WO2020114083A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20230005369A (ko) * 2021-03-25 2023-01-09 뉴 에이치3씨 테크놀로지스 코., 엘티디. Ioam 방법 및 전자 기기
EP4167506A4 (en) * 2020-07-17 2023-08-02 Huawei Technologies Co., Ltd. IN SITU FLOW DETECTION METHOD AND RELATED APPARATUS
US12395412B2 (en) 2021-11-30 2025-08-19 Cisco Technology, Inc. Method and apparatus for cross-layer, in-band monitoring of tunnels by insertion of telemetry data into a packet

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737124A (zh) * 2017-04-13 2018-11-02 中兴通讯股份有限公司 一种信息通告方法及装置
CN108737128A (zh) * 2017-04-13 2018-11-02 中兴通讯股份有限公司 一种实现带内操作管理维护ioam的方法及装置
CN108781171A (zh) * 2016-02-29 2018-11-09 思科技术公司 用于在ipv6环境中用数据平面信号通知分组捕获的系统和方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9350605B2 (en) * 2013-10-11 2016-05-24 Ciena Corporation Method and apparatus for multi-instance control plane for dynamic MPLS-TP tunnel management via in-band communication channel (G-ACH)
CN108011837B (zh) * 2017-11-21 2021-06-29 新华三技术有限公司 报文处理方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108781171A (zh) * 2016-02-29 2018-11-09 思科技术公司 用于在ipv6环境中用数据平面信号通知分组捕获的系统和方法
CN108737124A (zh) * 2017-04-13 2018-11-02 中兴通讯股份有限公司 一种信息通告方法及装置
CN108737128A (zh) * 2017-04-13 2018-11-02 中兴通讯股份有限公司 一种实现带内操作管理维护ioam的方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
BROCKNERS F ET AL: ""Encapsulations for In-Situ OAM Data Draft-Brockners-Inband-Oam-Transport-05"", IPPM INTERNET-DRAFT, 2 July 2017 (2017-07-02), pages 1 - 30, XP015120710 *
See also references of EP3893435A4
SONG H ET AL: ""In-Situ OAM Processing in Tunnels Draft-Song-Ippm-Ioam-Tunnel-Mode-00"", IPPM INTERNET-DRAFT, 25 June 2018 (2018-06-25), pages 1 - 8, XP015127129 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4167506A4 (en) * 2020-07-17 2023-08-02 Huawei Technologies Co., Ltd. IN SITU FLOW DETECTION METHOD AND RELATED APPARATUS
KR20230005369A (ko) * 2021-03-25 2023-01-09 뉴 에이치3씨 테크놀로지스 코., 엘티디. Ioam 방법 및 전자 기기
EP4152658A4 (en) * 2021-03-25 2023-05-03 New H3C Technologies Co., Ltd. OAM PROCEDURES ON SITE AND ELECTRONIC DEVICE
JP2023531987A (ja) * 2021-03-25 2023-07-26 新華三技術有限公司 インサイチュフロー検出方法及び電子デバイス
JP7446489B2 (ja) 2021-03-25 2024-03-08 新華三技術有限公司 インサイチュフロー検出方法及び電子デバイス
US12095662B2 (en) 2021-03-25 2024-09-17 New H3C Technologies Co., Ltd. In-situ flow detection method and electronic device
KR102755356B1 (ko) 2021-03-25 2025-01-21 뉴 에이치3씨 테크놀로지스 코., 엘티디. Ioam 방법 및 전자 기기
US12395412B2 (en) 2021-11-30 2025-08-19 Cisco Technology, Inc. Method and apparatus for cross-layer, in-band monitoring of tunnels by insertion of telemetry data into a packet

Also Published As

Publication number Publication date
EP3893435B1 (en) 2023-05-31
CN111277426B (zh) 2022-08-19
EP3893435A1 (en) 2021-10-13
EP3893435A4 (en) 2022-09-07
CN111277426A (zh) 2020-06-12

Similar Documents

Publication Publication Date Title
US12309064B2 (en) Method for forwarding packet in SRv6 service function chain, SFF, and SF device
US11979322B2 (en) Method and apparatus for providing service for traffic flow
US20210377173A1 (en) Data forwarding method and related apparatus
US20240154902A1 (en) Packet forwarding method and system, storage medium, and electronic device
EP2945330B1 (en) Route management method, route method, network controller and router
US10554542B2 (en) Label distribution method and device
US12542690B2 (en) Message header processing method and apparatus, storage medium and electronic device
US11627070B2 (en) Data packet processing method and apparatus, storage medium, and electronic device
US12395572B2 (en) Packet processing method
WO2017215401A1 (zh) 报文处理的方法及设备
US11477114B2 (en) Packet forwarding method and apparatus
US12341661B2 (en) Traffic message forwarding method, and client, controller and storage medium
WO2021258823A1 (zh) 路径创建方法、装置及系统
US11343173B2 (en) Systems and methods to implement path aware networking
CN113055293B (zh) 软件定义广域网中的选路方法及装置、通信系统
CN111669422A (zh) 报文的传输方法和设备
CN108234314B (zh) 业务调度方法和装置
WO2021073357A1 (zh) 报文处理方法、装置、系统、设备及存储介质
US12537760B2 (en) Packet forwarding method and apparatus, network device, and storage medium
WO2020114083A1 (zh) 一种ioam信息的处理方法和装置
CN109768929B (zh) 一种基于vpws的报文传输方法及装置
WO2025102691A1 (zh) 报文处理方法、电子设备和存储介质
WO2024027378A1 (zh) 数据传输方法、装置、网络设备及存储介质
WO2024002101A1 (zh) 报文传输方法、装置、相关设备及存储介质
CN112671646B (zh) 一种信息处理方法、装置、设备及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19893323

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019893323

Country of ref document: EP

Effective date: 20210705