EP2557731B1 - Procédé et système de mise en uvre indépendante d'une localisation de dérangement par un n ud intermédiaire - Google Patents

Procédé et système de mise en uvre indépendante d'une localisation de dérangement par un n ud intermédiaire Download PDF

Info

Publication number
EP2557731B1
EP2557731B1 EP11783075.2A EP11783075A EP2557731B1 EP 2557731 B1 EP2557731 B1 EP 2557731B1 EP 11783075 A EP11783075 A EP 11783075A EP 2557731 B1 EP2557731 B1 EP 2557731B1
Authority
EP
European Patent Office
Prior art keywords
packet
end node
node
response
intermediate node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP11783075.2A
Other languages
German (de)
English (en)
Other versions
EP2557731A1 (fr
EP2557731A4 (fr
Inventor
Zhen CAO
Xiangdong Yin
Wenneng Huang
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP2557731A1 publication Critical patent/EP2557731A1/fr
Publication of EP2557731A4 publication Critical patent/EP2557731A4/fr
Application granted granted Critical
Publication of EP2557731B1 publication Critical patent/EP2557731B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/12—Network monitoring probes

Definitions

  • the present invention relates to the field of network transmission, and in particular, to a method and a system for an intermediate node in a link to locate a fault independently.
  • One aspect of ensuring data transmission quality is to detect a link fault quickly and locate the fault to facilitate maintenance of the link when the data transmission is faulty, for example, the voice of a call is not clear.
  • FIG. 1 shows a common composition of a link.
  • routers C, H, and E form a link.
  • the routers C and E are end nodes (End Node, EN) of the link
  • the router H is an intermediate node (Intermediate Node, IN) of the link.
  • a data transmission process begins with sending data from a source end node, and ends with receiving all data correctly at the destination end node.
  • the user discovers quality deterioration of an end-to-end link between the router C and the router E, such as data delay or packet loss, it is necessary to determine whether the link quality deterioration is related to the router H.
  • the router H may ping C and ping E respectively. Ping is a technology of checking whether a channel or device is normal.
  • the router H pings the node C, namely, the router H sends N ICMP ( Internet Control Message Protocol) packets A. After the packets A arrive at the node C, the node C sends N packets A' to the node H.
  • the router H pings the node E, namely, the router H sends M ICMP packets B. After the packets B arrive at the node E, the node E sends M packets B' to the node H, where N and M are natural numbers.
  • the path followed by the packets of the two ping operations in the router H may be not completely the same as the path followed by the packets, which are forwarded by the router H and between the node C and the node E, in the router H. Therefore, the ping result is not enough for determining whether the link quality deterioration is related to the router H.
  • US 2003/0145105 A1 discloses a method and apparatus for obtaining information about one or more paths terminating at a subject node for a group of packets by determining one or more nodes that are up line from the subject node for the group of packets and propagating a trace request to each node that is up line from the subject node for the group of packets until the trace request is received at all of the ingress nodes for the group of packets.
  • a trace reply responsive to each trace request is then created and sent. At least one trace reply is then received at the subject node.
  • the information about the one or more paths terminating at the subject node for the group of packets is obtained from the trace replies received at the subject node.
  • US 2008/0112331 A1 discloses a method for transmitting a Connectivity Fault Management (CFM) message of Ethernet.
  • the method includes: receiving a CFM message transmitted from a source node, the CFM message including identifier of a path and a connection maintenance target address; determining whether the connection maintenance target address matches address of a receiving node, and if yes, terminating the CFM message; otherwise forwarding the CFM message to a next hop based upon the path identifier of the path.
  • Another method and a system for transmitting a CFM message of Ethernet, a node for transmitting a CFM message of Ethernet, and a node for receiving a CFM message of Ethernet are also disclosed.
  • a CFM message may be forwarded according to information of MAC address and VLAN ID of identifier of a path where a monitored service is located, and thus may be forwarded correctly in a PBB-TE network.
  • US 2005/135363 A1 discloses a router supporting a packet relay function based on a routing table, and also a VPN (Virtual Private Network) function, an output port deciding portion decides an output port different from a normal output port indicated as an output port corresponding to a destination address of a communication confirming packet based on the routing table, and packet transmitter transmits the communication confirming packet through the decided output port.
  • a communication confirming packet determining portion determines a communicating state based on a response packet for the communication confirming packet received from the destination router of the communication confirming packet returned from another router connected to the output port and relayed by its own router.
  • Embodiments of the present invention provide a method and a system for an intermediate node to locate a fault independently, in which a single node can locate a fault independently so that the maintenance efficiency against a fault is improved and the data transmission quality is ensured.
  • the invention provides the method of claim 1 and the system of claim 6. Preferred embodiments are addressed in the dependent claims.
  • a test packet is generated under independent control of an intermediate node in a link without depending on end nodes of the link.
  • the test packet triggers the end node to generate a response packet directed to a peer node, and the intermediate node forwards the response packet.
  • the forwarding path followed by the response packet in the intermediate node is the same as the forwarding path followed by a corresponding end-to-end service packet in the intermediate node. Therefore, a result of analyzing the captured response packets is enough for determining whether the intermediate node is able to forward an end-to-end packet normally, thereby implementing the fault locating.
  • the technical solution of the present invention enables an intermediate node of a single vendor to locate a fault, thereby improving maintenance efficiency against faults and ensuring data transmission quality.
  • the technical solution of the present invention is applicable to link fault locating.
  • an end node End Node, EN
  • an intermediate node Intermediate Node, IN
  • the end nodes and the intermediate nodes collectively form a link.
  • a data transmission process begins with sending data from a source end node, and ends with receiving all data correctly at a destination end node.
  • An intermediate node provides data forwarding and route selecting service for end-to-end data transmission, namely, the data sent by the source end node is forwarded through the intermediate node to the destination end node.
  • the end nodes that form the link and the intermediate node that forms the link may be various network elements and/or a system which integrates network elements with terminals operating the network elements.
  • the network elements may include, but are not limited to, routers, hosts, gateways, and switches.
  • the packet capturing function when the intermediate node is a network element, the packet capturing function is integrated in the network element; when the intermediate node is a system that includes a network element and a terminal operating the network element, the packet capturing function may be integrated in the terminal operating the network element.
  • an embodiment of the present invention provides a method for an intermediate node to locate a fault independently.
  • the intermediate node serves to forward a packet between a first end node and a second end node.
  • the method may specifically include:
  • an intermediate node creates a test packet and sends the test packet to the first end node.
  • the test packet includes address information of the second end node.
  • the test packet is used to trigger the first end node to send a response packet to the second end node.
  • the response packet includes information of a destination address, and the destination address is the second end node address.
  • test packet may be a common type of packet in the existing IP network, and for example, may be, but is not limited to, a ping packet, or an Address Resolution Protocol (Address Resolution Protocol, ARP) packet.
  • ARP Address Resolution Protocol
  • the intermediate node may create many types of test packets.
  • the test packet includes information of the second end node address and a first end node address.
  • the second end node address serves as a source address of the test packet, and the first end node address serves as a destination address of the test packet.
  • the test packet includes information of the second end node address, and the second end node address serves as the destination address of the test packet.
  • the intermediate node may send the test packet in many modes.
  • the test packet when the destination address of the test packet is the first end node address, the test packet is sent to the first end node directly.
  • the destination address of the test packet when the destination address of the test packet is the second end node address, the test packet is sent to the first end node through a specified outgoing interface.
  • step 202 the intermediate node forwards the response packet from the first end node to the second end node.
  • the forwarding path that the response packet passed in the intermediate node is the same as the forwarding path that a corresponding end-to-end service packet passed in the intermediate node. That is, in this embodiment, the response packet is used to simulate an end-to-end service packet.
  • features of the response packet may be further set according to features of the end-to-end service packet.
  • the test packet may be configured to control the features of the response packet.
  • the features of the response packet may include, but are not limited to: priority, sending frequency, length, and/or 5-tuple.
  • the 5-tuple includes a source IP address, a source port, a destination IP address, a destination port, and a protocol type.
  • Configuring the test packet may include: configuring the content of the test packet, and configuring the sending of the test packet.
  • configuring the content of the test packet may include, but is not limited to: carrying desired features of the response packet in a type of service (Type Of Service, TOS) field of the test packet.
  • configuring the sending of the test packet may include, but is not limited to: setting the features such as size of the test packet, frequency of the test packet, and port number of the test packet to control the features of the response packet accordingly.
  • step 203 the intermediate node captures the response packet.
  • the packet may be captured according to the type of the response packet or the features of the response packet.
  • capturing the packet according to the type of the response packet is to capture a ping packet or an ARP packet, for example.
  • capturing the packet according to the features of the response packet is to perform capturing according to different lengths of the packets, for example.
  • the packets may be captured in many modes.
  • the intermediate node when the intermediate node supports a DEBUG mode, the corresponding DEBUG monitoring is enabled so that the specific packets such as data packets of packets can be captured.
  • the traffic of a port of the intermediate node when the intermediate node supports mirroring, the traffic of a port of the intermediate node may be mirrored to a port connected with a packet capturing module, and the packets are captured through the packet capturing module.
  • the traffic includes incoming traffic and outgoing traffic.
  • the packet capturing module refers to a module on which a packet capturing tool is installed.
  • the packet capturing module is integrated in the intermediate node.
  • the ports of the intermediate node include but are not limited to: a port that connects the intermediate node with the first end node, and the port that connects the intermediate node with the second end node.
  • step 204 the intermediate node analyzes, according to a result of packet capturing, whether the packet from the first end node to the second end node can be forwarded normally.
  • the intermediate node may forward the packet from the first end node to the second end node normally. In another embodiment of the present invention, according to the period of receiving and sending response packets, and so on, it may be determined whether the intermediate node can forward the packet from the first end node to the second end node normally.
  • the basis for determining may be preset.
  • the intermediate node can forward the packet from the first end node to the second end node normally; otherwise, the intermediate node cannot forward the packet normally; if the delay between receiving and sending the response packets falls within a normal delay range, the intermediate node can forward the packet from the first end node to the second end node normally; otherwise, the intermediate node cannot forward the packet normally, and so on.
  • the normal forwarding may be determined if one parameter meets a preset condition or if multiple parameters meet preset conditions respectively.
  • the result of capturing the response packets may be used to analyze whether the intermediate node can forward the packet from the first end node to the second end node normally.
  • the test packet may be captured in step 203; correspondingly, in step 204, the results of capturing the test packets and the response packets may be used to analyze whether a packet transmission delay exists on the link between the intermediate node and the first end node, and analyze whether any packet is distorted abnormally, thereby better ensuring the data transmission quality.
  • the method according to the embodiment of the present invention may be used to locate whether a fault of sending the packet from the first end node to the second end node is related to the intermediate node.
  • the method according to the embodiment of the present invention may be used to locate whether a fault of sending the packet from the second end node to the first end node is related to the intermediate node. The difference is: The test packet is sent to the second end node, but the response packet is forwarded from the second end node to the first end node.
  • the end nodes are network elements
  • the intermediate node is a system that includes a network element and a terminal operating the network element, where the network element is a router.
  • the intermediate node is a network element only, the principle is the same.
  • routers C, H, and E form a link, and routers C and E are end nodes of the link.
  • An intermediate node of the link includes the router H and a packet capturing module 301.
  • the packet capturing module 301 is a host on which a packet capturing function is installed.
  • the packet capturing module 301 is configured to capture packets on the router H.
  • a port that connects the router H with the router E is a port 302
  • a port that connects the router H with the router C is a port 303.
  • the router H initiates fault locating, and determines whether the link quality deterioration is related to the intermediate node (the router H).
  • this embodiment is implemented through a ping function supported by the network element, and a specific process is as follows:
  • the information such as the number and/or delay of ping reply packets received by the intermediate node may be compared with that of those sent by the intermediate node to determine whether the intermediate node can forward the packet from the router E to the router C normally. Further, the information such as the number and/or delay of ping packets sent through the intermediate node may be compared with that of the ping reply packets sent through the intermediate node to determine whether the router H can forward the packet from the router E to the router C normally. Likewise, it is verifiable whether the intermediate node can forward the packet from the router C to the router E normally.
  • the router H initiates fault locating, and uses a ping function supported by the network element to determine whether the link quality deterioration is related to the intermediate node (the router H). As shown in FIG. 5 , a specific process is as follows:
  • the router H initiates fault locating, and uses an ARP function supported by the network element to determine whether the link quality deterioration is related to the intermediate node (the router H). As shown in FIG. 6 , a specific process is as follows:
  • the technical solution provided in the foregoing embodiment enables an intermediate node of a single vendor to locate a fault. If the problem lies in an intermediate node, the fault can be quickly removed, thereby improving maintenance efficiency against faults and ensuring data transmission quality. If it is determined that the problem does not lie in the intermediate nodes, the maintenance costs of the intermediate node devices are reduced, and recognition on the intermediate node devices is improved.
  • An embodiment of the present invention provides a system for an intermediate node to locate a fault independently, where the system may be integrated in an intermediate node, and the intermediate node serves to forward a packet between a first end node and a second end node.
  • the system includes a creating unit 701, a forwarding unit 702, a packet capturing unit 703, and an analyzing unit 704.
  • the creating unit 701 is configured to create a test packet and send the test packet to the first end node.
  • the test packet includes address information of the second end node.
  • the test packet is used to trigger the first end node to send a response packet to the second end node.
  • the response packet includes destination address information.
  • the destination address is the second end node address.
  • the creating unit may further be configured to configure the test packet to control features of the response packet.
  • the forwarding unit 702 is configured to forward the response packet from the first end node to the second end node;
  • the packet capturing unit 703 is configured to capture the response packet.
  • the analyzing unit 704 is configured to analyze, according to a result of the packet capturing, whether the intermediate node is able to forward the packet from the first end node to the second end node normally.
  • the creating unit 701 may create the test packet and send the test packet to the first end node in many ways:
  • the test packet includes source address information and destination address information.
  • the source address is the second end node address
  • the destination address is the first end node address.
  • the creating unit 701 sends the test packet to the first end node directly.
  • the creating unit 701 may include a creating subunit 7011, an interface subunit 7012, and a sending subunit 7013.
  • the creating subunit 7011 is configured to create a test packet.
  • the test packet includes destination address information, and the destination address is the second end node address.
  • the interface subunit 7012 is configured to specify an outgoing interface for the test packet.
  • the sending subunit 7013 is configured to send the test packet to the first end node through the outgoing interface.
  • the packet capturing unit 703 may capture packets through DEBUG monitoring. In another embodiment of the present invention, the packet capturing unit 703 may capture packets through mirroring. In the implementation manner where packets are captured through mirroring, the packet capturing unit 703 may include:
  • the first packet capturing module may include: a first mirroring submodule, configured to capture a response packet by mirroring incoming traffic at a port connected to the first end node.
  • the first packet capturing module may further include: a second mirroring submodule, configured to capture test packets by mirroring outgoing traffic at the port connected to the first end node.
  • the second packet capturing module may include: a mirroring submodule, configured to capture a response packet by mirroring outgoing traffic at a port connected to the second end node.
  • a packet capturing tool may be installed on the intermediate node.
  • a module with an installed packet capturing tool on the intermediate node is called a packet capturing module.
  • the capturing function of the packet capturing unit and the analysis function of the analyzing unit may be integrated in the packet capturing module.
  • the creating unit creates a test packet
  • the test packet triggers an end node to generate a response packet directed to a peer node
  • the forwarding unit forwards the response packet.
  • the forwarding path that the response packet passed in the intermediate node is the same as the forwarding path that a corresponding end-to-end service packet passed in the intermediate node. Therefore, the analyzing unit performs analysis according to a result of packet capturing with respect to the response packets captured by the packet capturing unit to determine whether the intermediate node is able to forward the end-to-end packet normally, thereby implementing the fault locating.
  • the embodiments of the present invention may be implemented through hardware, or through software in addition to a necessary universal hardware platform. Therefore, all or part of the novelty of the present invention may be embodied in a software product.
  • the software product may be stored in a storage medium such as a ROM/RAM, a magnetic disk, or an optical disk, and incorporates several instructions causing a computer device (such as a personal computer, a server, or a network device) to execute the method specified in any embodiment of the present invention or a part of the embodiment.

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)

Claims (6)

  1. Procédé pour permettre à un noeud intermédiaire de déterminer indépendamment si une défaillance d'envoi d'un paquet d'un premier noeud d'extrémité à un deuxième noeud d'extrémité est liée ou pas au noeud intermédiaire, le noeud intermédiaire servant à acheminer le paquet entre le premier noeud d'extrémité et le deuxième noeud d'extrémité, le procédé comprenant :
    la création (201), par le noeud intermédiaire, d'un paquet d'essai et l'envoi du paquet d'essai au premier noeud d'extrémité, le paquet d'essai comprenant des informations d'adresse du deuxième noeud d'extrémité, et le paquet d'essai étant utilisé pour déclencher le premier noeud d'extrémité pour envoyer au noeud intermédiaire un paquet de réponse destiné au deuxième noeud d'extrémité ;
    l'acheminement (202), par le noeud intermédiaire, du paquet de réponse du premier noeud d'extrémité au deuxième noeud d'extrémité ;
    la capture (203), par le noeud intermédiaire, du paquet de réponse ; et
    l'analyse (204), par le noeud intermédiaire, conformément à un résultat de la capture de paquet, de si un paquet allant du premier noeud d'extrémité au deuxième noeud d'extrémité est capable ou pas d'être acheminé normalement, comprenant :
    la détermination que le noeud intermédiaire ne peut pas acheminer normalement le paquet du premier noeud d'extrémité au deuxième noeud d'extrémité, si le nombre de paquets de réponse reçus du premier noeud d'extrémité n'est pas le même que le nombre de paquets de réponse envoyés au deuxième noeud d'extrémité, ou si la différence entre le nombre des paquets de réponse reçus et le nombre de paquets de réponse envoyés est en dehors d'une plage d'erreur, ou si le retard entre la réception et l'envoi des paquets de réponse est en dehors d'une plage de retard normale ;
    dans lequel :
    le paquet d'essai comprend en outre les informations d'adresse du premier noeud d'extrémité, l'adresse du deuxième noeud d'extrémité sert comme adresse de source du paquet d'essai, et l'adresse du premier noeud d'extrémité sert comme adresse de destination du paquet d'essai ;
    dans lequel le paquet de réponse est généré conformément à l'adresse de source du paquet d'essai.
  2. Procédé selon la revendication 1, dans lequel :
    le paquet d'essai est un paquet ping ou un paquet de protocole de résolution d'adresse.
  3. Procédé selon la revendication 1, dans lequel :
    la création du paquet d'essai et l'envoi du paquet d'essai au premier noeud d'extrémité comprennent en outre :
    la configuration du paquet d'essai pour commander les caractéristiques du paquet de réponse.
  4. Procédé selon la revendication 3, dans lequel : la capture du paquet de réponse comprend :
    la capture des paquets conformément aux caractéristiques du paquet de réponse.
  5. Procédé selon la revendication 3 ou 4, dans lequel :
    les caractéristiques du paquet de réponse comprennent :
    priorité, fréquence d'envoi, longueur, et/ou 5-uplet.
  6. Système pour permettre à un noeud intermédiaire de déterminer indépendamment si une défaillance d'envoi d'un paquet d'un premier noeud d'extrémité à un deuxième noeud d'extrémité est liée ou pas au noeud intermédiaire, le noeud intermédiaire servant à acheminer le paquet entre le premier noeud d'extrémité et le deuxième noeud d'extrémité, le système comprenant :
    une unité de création (701), configurée de façon à créer un paquet d'essai et à envoyer le paquet d'essai au premier noeud d'extrémité, le paquet d'essai comprenant des informations d'adresse du deuxième noeud d'extrémité, et le paquet d'essai étant utilisé pour déclencher le premier noeud d'extrémité pour envoyer au noeud intermédiaire un paquet de réponse destiné au deuxième noeud d'extrémité ;
    une unité d'acheminement (702), configurée de façon à acheminer le paquet de réponse du premier noeud d'extrémité au deuxième noeud d'extrémité ;
    une unité de capture de paquet (703), configurée de façon à capturer le paquet de réponse ; et
    une unité d'analyse (704), configurée de façon à analyser, conformément à un résultat de la capture de paquet, si un paquet allant du premier noeud d'extrémité au deuxième noeud d'extrémité est capable ou pas d'être acheminé normalement, comprenant :
    la détermination que le noeud intermédiaire ne peut pas acheminer le paquet du premier noeud d'extrémité au deuxième noeud d'extrémité normalement, si le nombre de paquets de réponse reçus du premier noeud d'extrémité n'est pas le même que le nombre de paquets de réponse envoyés au deuxième noeud d'extrémité, ou si la différence entre le nombre des paquets de réponse reçus et le nombre de paquets de réponse envoyés est en dehors d'une plage d'erreur, ou si le retard entre la réception et l'envoi des paquets de réponse est en dehors d'une plage de retard normale ;
    dans lequel :
    le paquet d'essai comprend en outre les informations d'adresse du premier noeud d'extrémité, l'adresse du deuxième noeud d'extrémité sert comme adresse de source du paquet d'essai, et l'adresse du premier noeud d'extrémité sert comme adresse de destination du paquet d'essai ;
    dans lequel le paquet de réponse est généré conformément à l'adresse de source du paquet d'essai.
EP11783075.2A 2010-10-27 2011-06-02 Procédé et système de mise en uvre indépendante d'une localisation de dérangement par un n ud intermédiaire Active EP2557731B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 201010521265 CN101958810B (zh) 2010-10-27 2010-10-27 用于中间节点自主实现故障定位的方法及系统
PCT/CN2011/075189 WO2011144158A1 (fr) 2010-10-27 2011-06-02 Procédé et système de mise en œuvre indépendante d'une localisation de dérangement par un nœud intermédiaire

Publications (3)

Publication Number Publication Date
EP2557731A1 EP2557731A1 (fr) 2013-02-13
EP2557731A4 EP2557731A4 (fr) 2013-02-20
EP2557731B1 true EP2557731B1 (fr) 2018-08-29

Family

ID=43485932

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11783075.2A Active EP2557731B1 (fr) 2010-10-27 2011-06-02 Procédé et système de mise en uvre indépendante d'une localisation de dérangement par un n ud intermédiaire

Country Status (4)

Country Link
US (1) US9059904B2 (fr)
EP (1) EP2557731B1 (fr)
CN (1) CN101958810B (fr)
WO (1) WO2011144158A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101958810B (zh) * 2010-10-27 2013-01-23 华为数字技术有限公司 用于中间节点自主实现故障定位的方法及系统
CN104796298B (zh) * 2014-01-22 2019-06-07 新华三技术有限公司 一种sdn网络故障分析的方法及装置
CN103840976B (zh) * 2014-02-28 2017-06-20 华为技术有限公司 通信方法、光设备和网络设备
CN105141434B (zh) * 2014-05-26 2019-03-26 华为技术有限公司 业务链的故障检测方法及装置
CN107852346B (zh) * 2015-09-30 2019-02-15 英国电讯有限公司 分析包括多个网络节点的网络的网络性能的方法和设备
CN107925591B (zh) 2015-09-30 2018-12-18 英国电讯有限公司 分析包括多个网络节点的网络的网络性能的方法和设备
CN107852347B (zh) 2015-10-08 2019-02-15 英国电讯有限公司 分析包括多个网络节点的网络的网络性能的方法和设备
US10608912B2 (en) * 2016-05-20 2020-03-31 Volta Networks, Inc. Troubleshooting multi-layered networks using datapath analysis
US10379158B2 (en) * 2017-02-09 2019-08-13 Advantest Corporation Real-time capture of traffic upon failure for protocol debug
CN110290017B (zh) * 2019-07-26 2022-06-10 新华三大数据技术有限公司 故障节点定位方法及pe设备
CN112904758B (zh) * 2021-01-14 2022-04-26 北京经纬恒润科技股份有限公司 基于无人车辆的数据回传链路状态监测方法及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050135363A1 (en) * 2003-12-19 2005-06-23 Fujitsu Limited Router

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030145105A1 (en) * 2002-01-30 2003-07-31 Harikishan Desineni Method and apparatus for obtaining information about one or more paths terminating at a subject node for a group of packets
US7280486B2 (en) * 2004-01-07 2007-10-09 Cisco Technology, Inc. Detection of forwarding problems for external prefixes
CN100438452C (zh) 2004-08-29 2008-11-26 华为技术有限公司 下一代网络中检测信令或媒体路径故障的方法和设备
CN100433719C (zh) * 2005-12-13 2008-11-12 华为技术有限公司 一种边缘到边缘伪线仿真多跳伪线的检验方法
US7702816B2 (en) 2006-03-31 2010-04-20 Cisco Technology, Inc. Facilitating application synchronization with a reservation protocol at a sender without application receiver participation
CN101132319B (zh) * 2006-08-21 2010-11-03 华为技术有限公司 一种以太网操作与维护故障检测的方法
CN101155078A (zh) 2006-09-30 2008-04-02 中兴通讯股份有限公司 一种快速定位ip网络故障的方法
CN100454853C (zh) * 2006-10-25 2009-01-21 华为技术有限公司 检测业务通道的方法及提供检测业务通道方法的系统
CN101174975B (zh) * 2006-11-03 2010-05-12 华为技术有限公司 一种以太网中的链路故障定位方法及系统
CN101179479A (zh) * 2006-11-09 2008-05-14 华为技术有限公司 一种以太网的操作管理和维护报文的传输方法、系统和节点
CN101420335B (zh) 2007-10-26 2011-09-14 华为技术有限公司 对等网络节点故障检测/处理方法及装置
CN101232343B (zh) * 2008-01-21 2012-03-07 中兴通讯股份有限公司 一种定位嵌入控制通路故障的方法
CN101222370B (zh) * 2008-02-01 2010-09-22 华为技术有限公司 使用故障定位报文进行故障定位的方法及装置
CN101605063A (zh) 2008-06-10 2009-12-16 鸿富锦精密工业（深圳）有限公司 网络故障定位系统及方法
CN101640672A (zh) 2008-07-31 2010-02-03 华为技术有限公司 一种网际协议网络的故障定位检测方法、系统和装置
CN101431448B (zh) 2008-10-22 2011-12-28 华为技术有限公司 定位ip承载网故障的方法、设备和系统
CN101420342A (zh) 2008-11-25 2009-04-29 华为技术有限公司 一种定位故障网络的方法、装置及系统
CN101505242B (zh) * 2008-12-25 2012-10-17 华为技术有限公司 路由器故障检测方法及路由装置
CN101826989B (zh) 2009-03-02 2013-11-06 华为技术有限公司 一种故障处理方法和装置
CN101510849B (zh) * 2009-03-18 2011-05-18 中国电信股份有限公司 获取传输路径上节点传输信息的方法和系统
CN101958810B (zh) * 2010-10-27 2013-01-23 华为数字技术有限公司 用于中间节点自主实现故障定位的方法及系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050135363A1 (en) * 2003-12-19 2005-06-23 Fujitsu Limited Router

Also Published As

Publication number Publication date
US9059904B2 (en) 2015-06-16
CN101958810B (zh) 2013-01-23
WO2011144158A1 (fr) 2011-11-24
EP2557731A1 (fr) 2013-02-13
EP2557731A4 (fr) 2013-02-20
US20130100824A1 (en) 2013-04-25
CN101958810A (zh) 2011-01-26

Similar Documents

Publication Publication Date Title
EP2557731B1 (fr) Procédé et système de mise en uvre indépendante d'une localisation de dérangement par un n ud intermédiaire
EP3958521A1 (fr) Procédé et appareil permettant de fournir un service destiné à un flux de services
JP5846221B2 (ja) ネットワークシステム、及びトポロジー管理方法
US8081580B2 (en) Network verification system
US7852778B1 (en) Verification of network paths using two or more connectivity protocols
US7525922B2 (en) Duplex mismatch testing
US8451745B2 (en) Auto probing endpoints for performance and fault management
US8406143B2 (en) Method and system for transmitting connectivity fault management messages in ethernet, and a node device
EP3306871B1 (fr) Procédé et appareil permettant d'acquérir des informations de chemin
EP2698947B1 (fr) Procédé et dispositif de traitement de défaillance
WO2011110118A2 (fr) Procédé et système de détection d'incidents
WO2016082588A1 (fr) Procédé et appareil de vérification de connectivité de liaison
US7940658B2 (en) ERSPAN dynamic session negotiation
US20110299406A1 (en) Path detection in trill networks
WO2007073649A1 (fr) Procede et systeme pour obtenir une unite de transfert maximale de voie dans un reseau
US8107388B2 (en) Route tracing program configured to detect particular network element making type of service modification
EP2509262B1 (fr) Communication de dispositifs non adressés à l'intérieur d'un réseau MPLS
CN105429841B (zh) Nni ping的实现方法及装置
WO2012155817A1 (fr) Procédé, dispositif et système d'essai de bouclage
US20080298258A1 (en) Information transfer capability discovery apparatus and techniques
EP1943787B1 (fr) Procede et systeme pour boucle avec retour et continuite dans un reseau a paquets
US7324454B2 (en) Router
US20060280133A1 (en) Full duplex/half duplex mismatch detecting method and full duplex/half duplex mismatch detecting apparatus applicable with the method
WO2007025426A1 (fr) Methode de detection du protocole de la couche application d'un reseau ipv6
JP2005110038A (ja) 輻輳検知装置、ｔｃｐトラヒックの輻輳検知方法およびプログラム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20121106

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

A4 Supplementary search report drawn up and despatched

Effective date: 20130118

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101AFI20130114BHEP

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20160822

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011051557

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0012260000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101ALI20180305BHEP

Ipc: H04L 12/26 20060101AFI20180305BHEP

INTG Intention to grant announced

Effective date: 20180320

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1036452

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180915

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011051557

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180829

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181129

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181129

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181229

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181130

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1036452

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180829

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011051557

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20190531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602011051557

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200101

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190602

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181229

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20110602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180829

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230504

Year of fee payment: 13