[go: up one dir, main page]

WO2018210213A1 - Procédé et dispositif de mise en œuvre d'un conditionnement ioam et support de stockage - Google Patents

Procédé et dispositif de mise en œuvre d'un conditionnement ioam et support de stockage Download PDF

Info

Publication number
WO2018210213A1
WO2018210213A1 PCT/CN2018/086788 CN2018086788W WO2018210213A1 WO 2018210213 A1 WO2018210213 A1 WO 2018210213A1 CN 2018086788 W CN2018086788 W CN 2018086788W WO 2018210213 A1 WO2018210213 A1 WO 2018210213A1
Authority
WO
WIPO (PCT)
Prior art keywords
ioam
node
band oam
packet
service data
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/CN2018/086788
Other languages
English (en)
Chinese (zh)
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
Publication of WO2018210213A1 publication Critical patent/WO2018210213A1/fr
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/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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • 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

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a method and apparatus for implementing in-band operation management and maintenance (IOAM, In-situ Operations, Administration and Maintenance, or In-band Operations, Administration and Maintenance), and a storage medium.
  • IOAM in-band operation management and maintenance
  • In-situ Operations, Administration and Maintenance or In-band Operations, Administration and Maintenance
  • IOAM is a new data communication network operation management and maintenance (OAM) technology proposed by the industry. This technology is currently in the rapid development stage under the joint promotion of the industry, and is in the Internet Engineering Task Force (IETF). Carry out standardization work.
  • IETF Internet Engineering Task Force
  • IOAM is characterized in that IOAM data content is encapsulated into service data packets as service data packets. A part of the data is transmitted in the network, and the out-of-band OAM data content is encapsulated into a specially constructed OAM data message and transmitted as a separate protocol message in the network.
  • IOAM can implement functions that cannot be implemented by out-of-band OAM, such as detecting network nodes through which service data packets actually pass, verifying that the transmission path of service data is consistent with expectations, and adding traffic data packets. Serial number information to detect packet loss and out-of-order, etc. Accordingly, in order to implement the above functions, the network administrator needs to perform IOAM transmission nodes including an IOAM Transit Node and an IOAM Egress Node.
  • the IOAM transit node is a node that needs to process the IOAM data content on the service data packet transmission path. Given that IOAM includes a variety of optional features, as well as the type of traffic carried by the network and the variability of the transmission path, these configurations are often complex and easily changeable.
  • IOAM encapsulation is to insert an IOAM header (IOAM header) into the service data message.
  • Figure 1 is an IOAM header format diagram. As shown in Figure 1, the IOAM header is used to indicate the location of the IOAM data content (as in Figure 1). The IOAM header indication) and the length (such as the IOAM header length in Figure 1) also carry 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 the data required to complete the IOAM function.
  • TLVs IOAM function option type/lengths/values
  • the IOAM encapsulation in the network that is, the node inserted into the IOAM header is called an IOAM Ingress Node or an IOAM encapsulation node.
  • the IOAM ingress node can be either a network node such as a switch or a router, or a personal computer or server. And other network terminals. Since the IOAM ingress node needs to complete the insertion of the IOAM header, it is necessary to determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, which is determined by the network administrator according to the configuration on each IOAM transmission node. It is determined and sent to the IOAM ingress node.
  • the configuration on the IOAM transit node is usually complicated and easy to change. Therefore, the method of implementing IOAM encapsulation by manually sending information at the IOAM ingress node increases network management. The burden of the staff is easy to make mistakes.
  • an embodiment of the present disclosure provides a method and apparatus for implementing IOAM encapsulation.
  • the IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;
  • the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the sending unit is configured to send the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;
  • a receiving unit configured to receive a second out-of-band OAM message that carries the IOAM configuration information sent by the IOAM transmission node;
  • the encapsulating unit is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • an embodiment of the present invention further provides a storage medium storing a computer program configured to perform the above method for implementing IOAM encapsulation.
  • the IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path.
  • the IOAM ingress node receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information.
  • the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the method for implementing IOAM encapsulation by manually sending information at the IOAM ingress node in the related art is solved, which increases the burden on the network administrator and is prone to error, and also enables the IOAM ingress node to support Automatically obtain the information required for IOAM encapsulation triggered by traffic.
  • FIG. 1 is a format diagram of an IOAM header according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart diagram of a method for implementing IOAM encapsulation according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of implementing IOAM encapsulation in an IP network according to application example 1 of the present disclosure
  • FIG. 4 is a format diagram of an ICMP message according to the first application example of the present disclosure.
  • FIG. 5 is a format diagram of an IOAM configuration information TLV of Application Example 1 of the present disclosure
  • FIG. 6 is a schematic diagram of implementing IOAM encapsulation in an MPLS network according to application example 2 of the present disclosure
  • FIG. 7 is a format diagram of an LSP ping packet of the second application example of the present disclosure.
  • FIG. 8 is a schematic diagram of implementing IOAM encapsulation by using LoopBack in an Ethernet network according to application example 3 of the present disclosure
  • FIG. 9 is a schematic diagram of implementing IOAM encapsulation by using LinkTrace in an Ethernet network according to application example 3 of the present disclosure.
  • FIG. 10 is a format diagram of a LoopBack packet in the third application example of the present disclosure.
  • FIG. 11 is a format diagram of a LinkTrace message according to the third application example of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an apparatus for implementing an IOAM package according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic flowchart of a method for implementing IOAM encapsulation according to an embodiment of the present disclosure. As shown in FIG. 2, the method for implementing IOAM encapsulation includes the following steps:
  • Step 201 The IOAM ingress node sends a first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path.
  • the first out-of-band OAM packet is only used to distinguish the subsequent second out-of-band OAM packet, and has no special meaning.
  • the outband 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 with different forwarding technologies use different out-of-band OAM messages, for example, Internet Control Message Protocol (ICMP) packets defined by the IETF standard RFC 792 in the IP network as out-of-band OAM messages, in multi-protocol label switching ( In the MPLS network, the label switched path echo (LSP Ping) message defined by the IETF standard RFC 8029 is used as the outband OAM message, and the International Telecommunication Union (ITU) standard is used in the Ethernet (Ethernet) network.
  • LSP Ping label switched path echo
  • ITU International Telecommunication Union
  • a loopback packet or a link trace (LinkTrace) packet defined by the .1731 is used as an outband OAM packet.
  • the IOAM configuration request information can be used to ensure that the IOAM configuration request information reaches each IOAM transmission node on the service data packet transmission path, and the outband OAM has been deployed on the live network in large quantities. This method can be used. Very compatible with the live network.
  • the IOAM ingress node when the triggering operation of the network administrator is obtained, the IOAM ingress node sends the first out-of-band OAM message carrying the IOAM configuration request information; or, when obtaining the triggering instruction of the network management module or the control application, The IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information; or, when the service data packet is triggered, the IOAM ingress node sends the first out-of-band OAM that carries the IOAM configuration request information. Message.
  • the timing of sending the first out-of-band OAM message carrying the IOAM configuration request information by the IOAM ingress node is very flexible, can be sent by the network administrator, or can be sent under the trigger of the network management module/control application, or It can also be sent under the trigger of service data packets.
  • the node on the service data packet transmission path includes at least one of the following: an IOAM transmission node, and a non-IOAM transmission node, where the IOAM transmission node includes an IOAM intermediate node and an IOAM egress node.
  • Step 202 The IOAM ingress node receives the second out-of-band OAM packet that carries the IOAM configuration information sent by the IOAM transmission node.
  • the first out-of-band OAM packet that carries the IOAM configuration request information sent by the IOAM ingress node will arrive at each node on the service data packet transmission path. If the first out-of-band OAM packet is received, the node is an IOAM transit node. That is, the node needs to process the IOAM data content, and the second out-of-band OAM packet replied by the node to the IOAM ingress node carries the IOAM configuration information of the node, where the IOAM configuration information of the node includes the node support. Which IOAM capabilities and enablement of each IOAM capability and related parameter configurations.
  • the node that receives the first out-of-band OAM packet is not the IOAM transit node, that is, the node does not need to process the IOAM data content, the node does not carry the second out-of-band OAM packet replied to the IOAM ingress node.
  • the IOAM configuration information of the node is not the IOAM transit node, that is, the node does not need to process the IOAM data content, the node does not carry the second out-of-band OAM packet replied to the IOAM ingress node.
  • Step 203 The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the IOAM ingress node determines, according to the IOAM configuration information of each IOAM transmission node, the IOAM function option TLVs included in the IOAM data content, and the length of each IOAM function option TLV; according to the IOAM function option TLVs And the length of each IOAM function option TLV, inserting an IOAM header in the service data packet, that is, implementing IOAM encapsulation of the service data packet.
  • FIG. 3 is a schematic diagram of implementing IOAM encapsulation in an IP network.
  • the IOAM ingress node and the IOAM transit node perform the following steps:
  • Step 11 The IOM ingress node sends an ICMP request message carrying the IOAM configuration request information.
  • an ICMP message includes an 8-bit type field and an 8-bit code field.
  • the IETF standard defines some values of the two fields, for example, a 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.
  • the types and code values that have not been specified, for example, the type 19 code 0 indicates an IOAM configuration request, and the type 20 code 0 indicates an IOAM configuration response, the ICMP request message can be carried to carry the IOAM configuration request information.
  • Step 12 The IOAM transmission node responds to the request, and returns an ICMP response message carrying the IOAM configuration information of the local node to the IOAM ingress node.
  • the sending node can send the ICMP request message to each node on the transmission path in turn by changing the time-to-live (TTL) value of the IP header in the ICMP request message.
  • TTL time-to-live
  • the IOAM transmission node After receiving the ICMP request message carrying the IOAM configuration request information, the IOAM transmission node sends an ICMP Request message sending node, that is, an IOM ingress node, to the ICMP response message carrying the IOAM configuration information of the local node.
  • the IOAM configuration information is written in the option data field of the ICMP response message in the form of a TLV.
  • FIG. 5 is a format diagram of the IOAM configuration information TLV. As shown in FIG. 5, the Type field of the TLV indicates the IOAM configuration information.
  • the Length field indicates the length of the TLV
  • the Value field contains a set of sub-TLVs (Sub-TLVs).
  • Each Sub-TLV carries configuration information of an IOAM function, where the sub-type (Sub-Type)
  • the field indicates the code of an IOAM function supported by the node
  • the Length field indicates the length of the Sub-TLV
  • the Value field indicates the configuration information of the IOAM function represented by the Sub-Type field, including whether the IOAM function is enabled on the node.
  • the configuration parameter values related to the IOAM function when enabled for example, the configuration parameters related to the IOAM tracking (Tracing) function defined by the IETF proposal draft-brockners-inband-oam-data Including: inserting node information in Pre-allocated mode or Incremental mode, and the number of bytes required for node information.
  • the configuration parameters related to the IOAM tracking (Tracing) function defined by the IETF proposal draft-brockners-inband-oam-data Including: inserting node information in Pre-allocated mode or Incremental mode, and the number of bytes required for node information.
  • Step 13 After the IOAM ingress node obtains the IOAM configuration of each node on the IP service packet transmission path, the IOAM encapsulation is determined.
  • the IOAM ingress node After the IOAM ingress node obtains the IOAM configuration of each node on the IP service packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, and thus can determine the IP service packet. IOAM package.
  • FIG. 6 is a schematic diagram of implementing IOAM encapsulation in an MPLS network.
  • the IOAM ingress node and the IOAM transit node perform the following steps:
  • Step 21 The IOAM ingress node sends an LSP ping request message carrying the IOAM configuration request information.
  • FIG. 7 is a format diagram of an LSP ping packet.
  • an LSP ping request packet contains a set of TLVs.
  • the LSP ping request packet can be carried.
  • IOAM configuration request information IOAM configuration request information.
  • Step 22 The IOAM transmission node responds to the request, and returns an LSP Ping response message carrying the IOAM configuration information of the local node to the IOAM ingress node.
  • the sending node can send the LSP ping request message to each node on the transmission path in turn by changing the TTL value of the MPLS header in the LSP ping request message.
  • the IOAM transit node After receiving the LSP ping request message carrying the IOAM configuration request information, the IOAM transit node sends an LSP Ping response message to the LSP ping request packet sending node, that is, the IOAM ingress node, and carries the LSP Ping response packet carrying the IOAM configuration information of the local node.
  • the method may be that the IOAM configuration information is written into the TLVs field of the LSP Ping response message in the form of a TLV, and the TLV adopts the format shown in FIG.
  • Step 23 After the IOAM ingress node obtains the IOAM configuration of each node on the MPLS service packet transmission path, the IOAM encapsulation is determined.
  • the IOAM ingress node After the IOAM ingress node obtains the IOAM configuration of each node in the MPLS service packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, and thus can determine the MPLS service packet. IOAM package.
  • FIG. 8 is a schematic diagram of implementing IOAM encapsulation by using LoopBack in an Ethernet network
  • FIG. 9 is a schematic diagram of implementing IOAM encapsulation by using LinkTrace in an Ethernet network.
  • the IOAM ingress node and the IOAM transit node perform the following steps:
  • Step 31 The IOAM ingress node sends a LoopBack request message or a LinkTrace request message carrying the IOAM configuration request information.
  • FIG 10 is a format diagram of a LoopBack packet
  • Figure 11 is a format diagram of a LinkTrace packet.
  • a LoopBack request packet or a LinkTrace request packet contains a set of TLVs, which is represented by adding a Type field.
  • the IOAM configuration request new TLV can make the LoopBack request packet or the LinkTrace request packet carry the IOAM configuration request information.
  • Step 32 The IOAM transit node responds to the request and returns a LoopBack response packet or a LinkTrace response packet carrying the IOAM configuration information of the local node to the IOAM ingress node.
  • the sending node can send the LoopBack request packet to each node on the transmission path in turn by changing the destination medium access control (MAC) address of the Ethernet header in the LoopBack request message.
  • the IOAM transit node After receiving the loopback request message carrying the IOAM configuration request information, the IOAM transit node sends a loopback request message to the loopback request message sending node, that is, the IOAM ingress node, and the loopback response packet carrying the IOAM configuration information of the local node.
  • the IOAM configuration information is written in the TLVs field of the LoopBack response message in the form of a TLV, and the TLV adopts the format shown in FIG.
  • the sending node only needs to set the destination MAC address of the Ethernet header in the LinkTrace request message to a dedicated multicast address, so that the LinkTrace request message can reach each node in the transmission path in turn.
  • the IOAM transit node After receiving the LinkTrace request packet carrying the IOAM configuration request information, the IOAM transit node requests the packet sending node, that is, the IOAM ingress node, to reply to the LinkTrace response packet carrying the IOAM configuration information of the local node.
  • the IOAM configuration information is written into the TLVs field of the LinkTrace response message in the form of a TLV, and the TLV adopts the format shown in FIG.
  • Step 33 After the IOAM ingress node obtains the IOAM configuration of each node on the Ethernet service packet transmission path, the IOAM encapsulation is determined.
  • the IOAM ingress node After the IOAM ingress node obtains the IOAM configuration of each node on the Ethernet service packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, and thus can determine the service packet for the Ethernet service. IOAM package.
  • FIG. 12 is a schematic structural diagram of an apparatus for implementing an IOAM package according to an embodiment of the present disclosure. As shown in FIG. 12, the apparatus includes:
  • the sending unit 121 is configured to send a first out-of-band OAM message carrying the IOAM configuration request information, where the first out-of-band OAM message sequentially arrives at each node on the service data packet transmission path;
  • the receiving unit 122 is configured to receive a second out-of-band OAM message that carries the IOAM configuration information sent by the IOAM transmission node.
  • the encapsulating unit 123 is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the sending unit 121 is configured to: when the triggering operation of the network administrator is obtained, send the first out-of-band OAM message carrying the IOAM configuration request information; or, when obtaining the network management module or the control application When the command is triggered, the first out-of-band OAM packet carrying the IOAM configuration request information is sent; or when the service data packet is triggered, the first out-of-band OAM packet carrying the IOAM configuration request information is sent.
  • the node on the service data packet transmission path includes at least one of the following: an IOAM transmission node, and a non-IOAM transmission node, where the IOAM transmission node includes an IOAM intermediate node and an IOAM egress node.
  • the receiving unit 122 receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information. Text.
  • the encapsulating unit 123 is configured to determine, according to the IOAM configuration information of each IOAM transmission node, an IOAM function option TLVs included in the IOAM data content, and a length of each IOAM function option TLV; according to the IOAM The function option TLVs and the length of each IOAM function option TLV are inserted into the IOAM header in the service data packet, that is, the IOAM encapsulation of the service data packet is implemented.
  • the first out-of-band OAM packet and the second out-of-band OAM packet are ICMP packets.
  • the first out-of-band OAM packet and the second out-of-band OAM packet are LSP ping packets
  • the first out-of-band OAM packet and the second out-of-band OAM packet are LoopBack packets or LinkTrace packets.
  • the implementation functions of the units in the apparatus for implementing IOAM encapsulation shown in FIG. 12 can be understood by referring to the foregoing description of the method for implementing IOAM encapsulation.
  • the functions of the units in the apparatus for implementing the IOAM package shown in FIG. 12 can be implemented by a program running on the processor, or can be realized by a specific logic circuit.
  • each unit in the apparatus for implementing the IOAM package may be implemented by a central processing unit (CPU) or a microprocessor (MPU, Micro) located in a device implementing the IOAM package.
  • CPU central processing unit
  • MPU microprocessor
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure 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 and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • an embodiment of the present invention further provides a storage medium, wherein a computer program is configured, and the computer program is configured to perform the method for implementing IOAM encapsulation in the embodiment of the present invention.
  • the IOAM ingress node sends the first out-of-band OAM packet carrying the IOAM configuration request information, where the first out-of-band OAM packet sequentially arrives at each node on the service data packet transmission path;
  • the IOAM ingress node receives the second out-of-band OAM message that is sent by the IOAM transmission node and carries the IOAM configuration information.
  • the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the method for realizing IOAM encapsulation by manually sending information at the IOAM ingress node in the related art increases the burden on the network administrator and is prone to error, and also enables the IOAM ingress node to support automatic acquisition of the IOAM under the trigger of the service traffic. Encapsulate the required information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de mise en œuvre d'un conditionnement IOAM et un support de stockage. Le procédé comporte les étapes consistant à: faire émettre, par un nœud d'entrée IOAM, un premier message OAM hors bande transportant des informations de demande de configuration IOAM, le premier message OAM hors bande atteignant successivement divers nœuds sur un trajet de transmission de messages de données commerciales; faire recevoir, par le nœud d'entrée IOAM, un second message OAM hors bande transmis en provenance de nœuds de transmission IOAM et transportant des informations de configuration IOAM; et faire effectuer, par le nœud d'entrée IOAM, un conditionnement IOAM sur un message de données commerciales selon les informations de configuration IOAM des divers nœuds de transmission IOAM.
PCT/CN2018/086788 2017-05-18 2018-05-15 Procédé et dispositif de mise en œuvre d'un conditionnement ioam et support de stockage Ceased WO2018210213A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710352022.8 2017-05-18
CN201710352022.8A CN108964943B (zh) 2017-05-18 2017-05-18 一种实现ioam封装的方法及装置

Publications (1)

Publication Number Publication Date
WO2018210213A1 true WO2018210213A1 (fr) 2018-11-22

Family

ID=64273386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/086788 Ceased WO2018210213A1 (fr) 2017-05-18 2018-05-15 Procédé et dispositif de mise en œuvre d'un conditionnement ioam et support de stockage

Country Status (2)

Country Link
CN (1) CN108964943B (fr)
WO (1) WO2018210213A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020134564A1 (fr) * 2018-12-26 2020-07-02 中兴通讯股份有限公司 Procédé et dispositif de traitement d'informations ioam, et support de stockage lisible par ordinateur
CN112866042A (zh) * 2019-11-12 2021-05-28 中兴通讯股份有限公司 网络质量检测方法、装置、计算机设备和计算机可读介质
EP4030696A4 (fr) * 2019-10-26 2022-10-26 Huawei Technologies Co., Ltd. Procédé et dispositif de traitement de paquets de multidiffusion

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111327445B (zh) * 2018-12-17 2023-09-12 中兴通讯股份有限公司 报文采样方法及解封装方法、节点、系统及存储介质
CN111385121B (zh) * 2018-12-29 2021-08-03 华为技术有限公司 一种操作管理维护iOAM报文的传输方法及相应装置
CN112118147A (zh) * 2019-06-21 2020-12-22 烽火通信科技股份有限公司 一种基于mpls-tpoam的lb检测方法及系统
CN112448926B (zh) * 2019-08-30 2022-07-08 烽火通信科技股份有限公司 一种带内操作管理维护ioam的处理方法及系统
CN115733720A (zh) * 2019-11-14 2023-03-03 华为技术有限公司 发送报文、接收报文以进行oam的方法、装置及系统
CN112910773B (zh) * 2019-11-19 2024-07-05 华为技术有限公司 下发oam配置信息的方法及控制节点
CN114826952A (zh) * 2021-01-27 2022-07-29 中国移动通信有限公司研究院 一种用于oam检测的信息处理方法、装置和节点设备
CN117834342A (zh) * 2022-09-29 2024-04-05 中兴通讯股份有限公司 虚拟化隧道网络的ioam封装的实现方法及装置
CN121056511A (zh) * 2024-05-23 2025-12-02 中国电信股份有限公司技术创新中心 一种报文处理方法、装置和系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103580894A (zh) * 2012-07-31 2014-02-12 华为技术有限公司 操作、管理和维护oam配置的方法、设备及系统
WO2017070023A1 (fr) * 2015-10-20 2017-04-27 Cisco Technology, Inc. Fonctions d'exploitation, administration et maintenance (oam) intrabande déclenchées dans un environnement de réseau

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100396023C (zh) * 2005-09-30 2008-06-18 华为技术有限公司 维护多跳伪线的协商控制方法
CN101267363A (zh) * 2008-04-24 2008-09-17 杭州华三通信技术有限公司 环回测试方法、系统及装置
CN101478438B (zh) * 2009-01-13 2011-06-22 中兴通讯股份有限公司 一种以太网oam链路发现方法
CN101826990A (zh) * 2009-03-05 2010-09-08 华为技术有限公司 检测虚拟伪线连通性的方法、装置及系统
EP2341668A1 (fr) * 2010-01-05 2011-07-06 Alcatel Lucent Transport d'un flux de trafic dans un système de communication mobile
EP2595347A4 (fr) * 2010-07-12 2013-12-04 Zte Corp Procédé, système et terminal pour la configuration d'attributs oam pour une passerelle pseudowire
CN103609066B (zh) * 2011-04-28 2017-04-26 华为技术有限公司 操作、管理、维护配置信息查询的方法及节点
CN102916845B (zh) * 2011-08-01 2017-02-01 中兴通讯股份有限公司 一种多路径的环回检测方法及交换机设备
EP2880815B1 (fr) * 2012-08-01 2017-01-04 Telefonaktiebolaget LM Ericsson (publ) Fonctions d'exploitation, administration et gestion (oam)
CN105893061A (zh) * 2016-06-12 2016-08-24 杭州勒芒科技有限公司 应用程序开发方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103580894A (zh) * 2012-07-31 2014-02-12 华为技术有限公司 操作、管理和维护oam配置的方法、设备及系统
WO2017070023A1 (fr) * 2015-10-20 2017-04-27 Cisco Technology, Inc. Fonctions d'exploitation, administration et maintenance (oam) intrabande déclenchées dans un environnement de réseau

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
BROCKNERS, F. ET AL.: "Encapsulations for In-Band OAM Data Draft-Brockners-in Band-Oam-Transport-Ol", NETWORK WORKING GROUP INTERNET -DRAFT, 18 July 2016 (2016-07-18), pages 1 - 12, XP055548007 *
MIN, X. ET AL.: "Extended OAM to Carry In-Situ OAM Configuration Data Draft-Xiaoippm-Ioam-Conf-State-OO", IPPM WORKING GROUP INTERNET -DRAFT, 27 October 2017 (2017-10-27), pages 1 - 10, XP055547984 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020134564A1 (fr) * 2018-12-26 2020-07-02 中兴通讯股份有限公司 Procédé et dispositif de traitement d'informations ioam, et support de stockage lisible par ordinateur
EP4030696A4 (fr) * 2019-10-26 2022-10-26 Huawei Technologies Co., Ltd. Procédé et dispositif de traitement de paquets de multidiffusion
US11784915B2 (en) 2019-10-26 2023-10-10 Huawei Technologies Co., Ltd. Multicast packet processing method and device
CN112866042A (zh) * 2019-11-12 2021-05-28 中兴通讯股份有限公司 网络质量检测方法、装置、计算机设备和计算机可读介质

Also Published As

Publication number Publication date
CN108964943B (zh) 2022-01-28
CN108964943A (zh) 2018-12-07

Similar Documents

Publication Publication Date Title
CN108964943B (zh) 一种实现ioam封装的方法及装置
US11979322B2 (en) Method and apparatus for providing service for traffic flow
CN113411834B (zh) 报文处理方法、装置、设备及存储介质
CN105723657B (zh) 交换机、控制器、系统及链路质量检测方法
US10862793B2 (en) Centralized error telemetry using segment routing header tunneling
CN108965204B (zh) 一种自动实现ioam封装的方法及装置
EP2509261B1 (fr) Surveillance d'un élément de réseau dans un réseau commuté par paquets
CN103580894B (zh) 操作、管理和维护oam配置的方法、设备及系统
CN103078791B (zh) Oam报文处理方法、设备及系统
WO2015165212A1 (fr) Dispositif et procédé de traitement de paquets et support de stockage informatique
CN101459547B (zh) 标签转发路径故障的检测方法及系统
WO2015184771A1 (fr) Procédé et dispositif de nœud pour l'exploitation, l'administration et la maintenance d'un chaînage de fonctions de service
WO2021088813A1 (fr) Procédé et appareil d'encapsulation de paquets, et procédé et appareil de décapsulation de paquets
CN103716172A (zh) 一种基于多协议标签交换的oam方法及装置
CN101252528B (zh) 一种故障检测方法及设备
WO2021190009A1 (fr) Procédé et appareil de mesure de performance, dispositif, et support de stockage
WO2015184740A1 (fr) Procédé et dispositif de traitement d'informations de hiérarchie de détection
CN110224916B (zh) 报文的处理方法、装置及报文的封装方法、装置和系统
WO2013078873A1 (fr) Procédé et dispositif pour identifier un message de réponse
CN102843282B (zh) 一种报文处理方法及系统
CN104270280B (zh) 在路由器上实现LSP ping和tracert的系统及方法
CN111885433B (zh) 一种可实现端到端监测的网络系统、方法及设备
CN117319270A (zh) 一种网络测试方法以及相关装置
CN102624746B (zh) 检测隧道两端gre头配置的方法、源端、目的端和系统
CN105490906A (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: 18801598

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18801598

Country of ref document: EP

Kind code of ref document: A1