WO2012106915A1 - Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données - Google Patents

Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données Download PDF

Info

Publication number
WO2012106915A1
WO2012106915A1 PCT/CN2011/077470 CN2011077470W WO2012106915A1 WO 2012106915 A1 WO2012106915 A1 WO 2012106915A1 CN 2011077470 W CN2011077470 W CN 2011077470W WO 2012106915 A1 WO2012106915 A1 WO 2012106915A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
node
path
address
multicast
Prior art date
Application number
PCT/CN2011/077470
Other languages
English (en)
Chinese (zh)
Inventor
刘晖
白涛
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/077470 priority Critical patent/WO2012106915A1/fr
Priority to CN201180001332.6A priority patent/CN102726000B/zh
Publication of WO2012106915A1 publication Critical patent/WO2012106915A1/fr

Links

Classifications

    • 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/48—Routing tree calculation
    • 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/16—Multipoint routing
    • 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/28—Routing or path finding of packets in data switching networks using route fault recovery

Definitions

  • the present invention relates to the field of mobile communication network technologies, and in particular, to a fault notification method, a detection device, a forwarding device, a system, and a data structure. Background technique
  • Multicast technology is a one-to-many multi-party communication technology. Compared with the commonly used unicast technology, the multicast technology reduces the duplication of data content by establishing an optimal multicast forwarding path, thereby greatly reducing the consumption of network resources by multi-party communication, such as IP (Internet Protocol). Multicast tree.
  • An IP multicast tree is a forwarding path established from one (or more) source nodes to multiple receiving nodes. The multicast stream carrying the video service is transmitted on the multicast network through the IP multicast tree, which can improve the forwarding efficiency.
  • protection technology can be used in the multicast network.
  • a common implementation is to establish a primary forwarding path (or simply a primary path) and an alternate forwarding path (or simply an alternate path). Under normal circumstances, the multicast stream is forwarded through the primary path. When the primary path fails, the multicast stream is forwarded through the alternate path. This switching of primary and backup path forwarding can be performed on the switching node (upstream fusion node or downstream fusion node) of the primary and secondary paths.
  • the switch from the primary path to the alternate path can be triggered by the fault notification.
  • the fault is detected by the fault-aware node.
  • the fault-aware node encapsulates the fault information in the fault notification packet.
  • the fault notification packet is sent to all non-faulty nodes.
  • the other nodes that receive the fault advertise the fault notification packet to all non-incoming interfaces until the fault notification packet reaches the IP address. All nodes in the multicast network where the multicast tree is located. After the switching node (upstream merging node or downstream fused node) of the primary path and the standby path learns the failure notification packet, the primary path and the alternate path are switched, and the multicast stream is forwarded to the standby path.
  • the method for transmitting the fault notification by the fault-aware node is a flooding method, and the method for flooding the fault notification message can achieve the purpose of quickly notifying the fault, but this method increases the number of invalid packets.
  • the present invention discloses a fault notification method, a detection device, a forwarding device, a system, and a data structure, so as to solve the problem of flooding a failure notification message in the prior art to increase the number of invalid packets.
  • the specific plan is as follows:
  • a fault notification method including:
  • IP multicast tree forwarding path Detecting whether the primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on a protocol-independent multicast protocol
  • the non-switching point on the primary path detects that the primary path is faulty, the fault information is obtained, and the fault information is encapsulated into a fault notification message;
  • a detection apparatus comprising:
  • the fault detection module is configured to detect whether a primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established according to a protocol-independent multicast protocol;
  • a package module configured to acquire an error message that the fault detection module detects that the primary path is faulty Encapsulating the fault information into a fault notification message;
  • the transmitter is configured to send the fault notification message.
  • a forwarding device including:
  • a receiving unit configured to receive a fault notification message
  • the encapsulation unit is configured to re-encapsulate the failure notification report received by the receiving unit by using the address of the previous hop node as the source address in the fault notification packet.
  • a forwarder configured to send a re-encapsulated failure notification message.
  • a fault notification system including:
  • the detecting device is configured to detect whether the primary path of the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established according to a protocol-independent multicast protocol; acquiring fault information of the primary path fault, and packaging the fault information A failure notification message is sent, and the failure notification message is sent;
  • a first switching device configured to receive the fault notification message, and switch the multicast traffic on the primary path to the standby path according to the fault notification message;
  • the first switching device is the primary path and the The upstream fusion node of the alternate path.
  • a fault notification system including:
  • the detecting device is configured to detect whether the primary path of the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established according to a protocol-independent multicast protocol; acquiring fault information of the primary path failure, and packaging the fault information And generating a fault notification message, and sending the fault notification message to the downstream multicast;
  • a second switching device configured to receive the fault notification message, and switch the multicast traffic on the primary path to the standby path according to the fault notification message, where the second switching device is the primary path and the The downstream fusion node of the alternate path.
  • a data structure including a message header and a data portion, the data portion including: a type, an address list, a quantity, and a length; wherein:
  • the combination of the type and the address list indicates a manner in which the switching point performs an alternate path switch after receiving the fault notification message; the quantity and the address list are combined to indicate an address of any one of the address lists. The length and the address list are combined to indicate an address of any one of the faults in the address list.
  • the packet header includes a router alarm option, and the router alarm option indicates that the downstream convergence node is used as the switching point, the data layer of the downstream fusion node receives the failure notification message, and sends the failure notification message to its own control plane. Switching between the primary path and the alternate path by the control plane.
  • the fault notification method disclosed in the embodiment of the present invention when the non-switching point detects that the primary path in the IP multicast tree forwarding path is faulty, the fault information is encapsulated into the fault notification message. And sending a fault notification message to the switching node of the primary path.
  • the non-switching point detects that the primary path in the IP multicast tree forwarding path is faulty, it does not need to send a fault notification message to all nodes in the multicast network where the IP multicast tree is located, thereby reducing the invalid report. The number of texts.
  • FIG. 2 is a schematic diagram of a forwarding path in a multicast tree according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a fault notification message according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of an address list field in the fault notification message shown in FIG. 3.
  • FIG. 5 is another schematic diagram of an address list field in the fault notification message shown in FIG. 3.
  • FIG. 6 is an embodiment of the present invention. Another structural schematic diagram of the disclosed fault notification message;
  • FIG. 7 is another flowchart of the fault notification method disclosed in the embodiment of the present invention.
  • FIG. 8 is still another flowchart of a fault notification method according to an embodiment of the present invention.
  • FIG. 9 is still another flowchart of a fault notification method according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a fault notification message according to an embodiment of the present invention
  • FIG. 11 is a schematic structural diagram of a detecting apparatus according to an embodiment of the present invention
  • FIG. 12 is a schematic structural diagram of a transmitter in a detecting apparatus according to an embodiment of the present invention
  • FIG. 13 is a schematic structural diagram of a forwarding apparatus according to an embodiment of the present invention
  • FIG. 14 is another schematic structural diagram of a forwarding device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a fault notification system according to an embodiment of the present invention
  • FIG. 16 is another schematic structural diagram of a fault notification system according to an embodiment of the present invention. detailed description
  • the invention provides A fault notification method is provided.
  • the method is applicable to the failure of the primary path of the IP multicast tree, and the fault information is encapsulated in the fault notification packet, and the fault notification packet is sent to the convergence node to solve the prior art.
  • the method of flooding the fault notification packet increases the number of invalid packets and reduces the network security performance.
  • the forwarding path includes at least one primary path, and may also include at least one alternate path.
  • the forwarding path shown in FIG. 2 includes a primary path and an alternate path.
  • the main path in the IP multicast tree forwarding path shown in Figure 2 is A -> B -> C1 > D.
  • the alternate path is A—>E ⁇ >F—>D.
  • node A and node D are two fusion nodes of the primary path and the alternate path.
  • the fused node A that is close to the multicast source is called the upstream fused node
  • the fused node D that is far away from the multicast source is called the downstream fused node.
  • Node A includes two outgoing interfaces—the primary outgoing interface and the standby outgoing interface A 2 .
  • the primary outgoing interface is connected to the node B.
  • the standby interface A 2 is connected to the node E.
  • Node D includes two inbound interfaces—a primary inbound interface and a standby inbound interface D 2 .
  • the primary ingress interface is connected to node C, and the standby interface D 2 is connected to node F.
  • Any node in the primary path can detect whether the primary path is faulty.
  • Node B or upstream Fusion Node A detects whether the primary path is faulty.
  • the types of failures in which the primary path fails include node failures, link failures, and multicast flow failures.
  • Node A fault means that the node in the primary path fails and the multicast stream cannot be sent.
  • a link failure refers to a link failure between two nodes on the primary path constituting the link in the primary path, and the multicast stream cannot be sent.
  • Nodes and link faults can be detected by a detection protocol, such as the Bidirectional Forwarding Detection (BFD) protocol. Specifically, any two neighboring nodes on the primary path periodically send detection packets. If a node does not receive the response packet from the peer node, it indicates that an interface of the peer node or the link between the node and the peer node is faulty.
  • BFD Bidirectional Forwarding Detection
  • a multicast flow fault is a multicast outflow performance fault that is sent by the primary path when the nodes and links in the primary path are normal.
  • the multicast stream fault can be judged by whether the characteristics of packet loss and delay of the multicast stream detected by the node or the receiver exceed the normal threshold. When the node or the receiving end detects that the received packet loss, delay, and other characteristics exceed the normal threshold, it determines that the multicast stream is faulty.
  • Switching points can be determined based on local management policies.
  • the local management policy may be that the primary path and the alternate path are switched by the designated fusion node when it is detected that the primary path fails. For example, if the specified converged node is an upstream converged node, it indicates that when the primary path fails, the upstream converged node switches between the primary path and the alternate path.
  • the upstream fusion node A in the primary path performs the active/standby path switching when the primary path fails.
  • the upstream fusion node A is a switching point, and the other nodes are non-switching points.
  • the non-switching point B detects that the primary path is faulty, it sends a fault notification message to the switching point, that is, the upstream convergence node A.
  • the downstream fusion node D can also be used as a switching point when non-switching point A detection If the primary path fails, the faulty notification packet is sent to the downstream fusion node D.
  • the above fault information includes, for example, a fault type and an address list.
  • the fault type can be a node failure or a link failure or a multicast flow failure.
  • the address list is the IP address list of the interface connected to the faulty node on the non-switching node, and may also be the IP address list of the interface connected to the non-switching node on the faulty node.
  • the address list may be a list of interface IP addresses connected to the faulty link on the non-switching node, or a list of interface IP addresses of the nodes connected to the non-switching node through the faulty link.
  • the address list is the faulty multicast stream identifier.
  • the multicast stream identifier can be a multicast group address, and can also include the multicast group address and the multicast source address.
  • a multicast stream whose characteristics such as packet loss and delay of the received multicast stream exceed the normal threshold are detected for the node or the receiving end.
  • the fault information is encapsulated in a fault notification packet, and the fault notification packet may be a UDP (User Datagram Protocol) packet. See Figure 3 for the UDP packet format.
  • UDP packets include the UDP header and data portion, and the data portion includes a list of types, lengths, numbers, and addresses. among them:
  • the type indicates the fault type, which can be a node fault or a link fault or a multicast stream fault.
  • the fault type is node fault
  • the address list encapsulates the non-switching that detects the fault of the primary path.
  • the IP address list of the interface connected to the faulty node on the node may also be the IP address list of the interface connected to the non-switching node that detects the fault of the primary path on the faulty node.
  • the type indicates that the fault type is a link fault.
  • the address list encapsulates the IP address list of the interface connected to the faulty link on the non-switching node that detects the fault of the primary path. It can also detect the primary path.
  • the fault type is a multicast stream fault
  • the address list encapsulates the identifier of the faulty multicast stream. It can be a multicast group address, or a multicast group address and a multicast source address.
  • the length indicates the length of the data in the quantity field and the address list field, in bytes.
  • the quantity indicates the number of failures.
  • the fault type is a node fault
  • the quantity indicates the number of faulty nodes.
  • the fault type is a link fault
  • the quantity indicates the number of faulty links.
  • the fault type is a multicast flow failure
  • the quantity indicates the number of failed multicast flow identifiers. Since the non-switching point fails in the main path, each time the detected faulty node or the faulty link or the number of faulty multicast streams is not determined, the quantity field indicates the number of faults and improves versatility.
  • the address list indicates the address where the failure occurred.
  • the address list is a list of interface IP addresses connected to the faulty node on the non-switching node that detects the fault of the primary path, and may also be an interface connected to the non-switching node that detects the fault of the primary path on the faulty node.
  • the address list encapsulates the IP address list of the interface connected to the faulty link on the non-switching node that detects the fault of the primary path, and may also pass the fault chain for the non-switching node that detects the fault of the primary path.
  • a list of interface IP addresses of nodes connected to the road is a list of interface IP addresses connected to the faulty node on the non-switching node that detects the fault of the primary path.
  • the address list is the identifier of the faulty multicast stream, which can be a multicast group address, or a multicast group address and a multicast source address.
  • the address in the address list can be an IPv4 (Internet Protocol version 4) address or an IPv6 (Internet Protocol Version 6, Internet Protocol Version 6) address. Take IPv4 as an example.
  • the above-mentioned fault notification 4 can also be a Transmission Control Protocol (TCP) packet. See Figure 6 for the format of the packet.
  • the TCP message includes a TCP header and a data portion, and the data portion includes a list of types, lengths, numbers, and addresses. Where: type, length, quantity, and address columns
  • type, length, quantity, and address columns The information indicated in the table is the same as the information indicated by the type, length, quantity and address list in the UDP packet, and will not be described here.
  • the fault type is node fault or link fault
  • the format of the address list can be seen in Figure 4.
  • the format of the address list can be seen in Figure 5.
  • the non-switching point sends a fault notification message to the switching point of the primary path, so that the switching point switches the multicast traffic on the primary path to the alternate path.
  • the switchover point of the primary path switches the multicast stream on the primary path to the alternate path according to the fault notification packet.
  • the switch point determines whether the address list contains the address of a specific multicast stream after receiving the fault advertisement packet. When the switchover point determines that the address list contains the address of the specific multicast stream, obtains the address list of the specific multicast stream from the fault notification message, switches the specific multicast stream to the alternate path, and forwards the specific multicast stream through the alternate path.
  • the address list does not contain the address of a specific multicast stream, the multicast path continues to be forwarded by the primary path. The specific multicast stream needs to be switched to the multicast stream forwarded on the alternate path in time when the primary path fails.
  • the switch point receives the fault advertisement packet, obtains the address information in the address list in the fault notification packet, determines the faulty primary path, and further selects and fails.
  • the alternate path corresponding to the primary path switches the multicast stream on the primary path to the alternate path and forwards the multicast stream through the alternate path.
  • the upstream fusion node A detects that the primary path is faulty, and the upstream fusion node A does not send the fault information to any node in the primary path, and directly performs the primary backup path. Path switching.
  • the non-switching point when the non-switching point detects that the primary path in the IP multicast tree forwarding path is faulty, the fault information is encapsulated into the fault notification message. And send a fault notification message to the switching point of the primary path.
  • the non-switching point detects that the primary path in the IP multicast tree forwarding path is faulty, it does not need to send a fault notification message to all nodes in the multicast network where the IP multicast tree is located, thereby reducing the invalid report. The number of texts.
  • the embodiment of the present invention can also implement fault notification when the local management policy is specified to specify the upstream convergence node to perform the primary path and the alternate path switching.
  • FIG. 7 is another flowchart of a fault notification method according to an embodiment of the present invention, including:
  • S701 Detecting whether the primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on the PIM protocol.
  • a schematic diagram of the forwarding path can be omitted from Fig. 2 for further explanation.
  • the types of faults in which the primary path fails include link failure, node failure, and multicast flow failure.
  • the type of failure and the judgment of the type of failure are described in the previous embodiment.
  • the fault detection of the primary path may be detected by any non-switching point in the primary path. For example, in the forwarding path diagram shown in Figure 2, the non-switching point C detects whether the primary path is faulty.
  • the non-switching point After the non-switching point detects that the primary path has failed, it obtains fault information, such as the fault type and address list.
  • the fault type can be a node fault or a link fault or a multicast stream fault.
  • the address list is the IP address list of the interface connected to the faulty node on the non-switching node, and may also be the IP address list of the interface connected to the non-switching node on the faulty node.
  • the address list When the fault type is a link fault, the address list may be an interface connected to the faulty link on the non-switching node.
  • the IP address list may also be a list of interface IP addresses of nodes connected to the non-switching node through the faulty link.
  • the address list is the faulty multicast stream identifier.
  • the multicast stream identifier can be a multicast group address, and can also include the multicast group address and the multicast source address. A multicast stream whose characteristics such as packet loss and delay of the received multicast stream exceed the normal threshold are detected for the node or the receiving end.
  • the fault information is encapsulated in a fault notification packet.
  • the fault notification packet can be a UDP packet.
  • the fault notification packet can also be a TCP packet.
  • the format of the packet see Figure 6.
  • the format of the address list can be seen in Figure 4.
  • the format of the address list can be seen in Figure 5.
  • S703 Send the fault notification packet directly to the upstream convergence node. Specifically:
  • the non-switching point uses the local address as the source address and the address of the upstream fused node as the destination address to directly send the fault notification packet to the upstream fused node.
  • the upstream convergence node After receiving the fault notification packet, the upstream convergence node directly switches to the alternate path, and the multicast path forwards the multicast stream.
  • the method of obtaining the address of the upstream fused node in advance by the non-switching point may be: the non-switching point sends a request for obtaining the address information of the upstream fused node to the network management, and the network management query is configured by the network management to obtain the address information of the requested upstream fused node, and the encapsulation
  • the non-switching point receives the response message sent by the network management device, and obtains the address of the upstream fusion node from the response message.
  • the address of the upstream convergence node may also be: The network management periodically sends the address of the upstream fusion node to the node in the primary path. On The non-switching point may also obtain the address information of the upstream fusion node through the gateway configuration mode, but is not limited to the above manners.
  • the non-switching point may send the UDP packet to the upstream fusion node multiple times. • Multiple transmissions of the message can be sent periodically for non-switching points or irregularly. The number of transmissions can be different according to different application scenarios when ensuring reliable transmission of packets.
  • the upstream convergence node After detecting that the primary path fails, the upstream convergence node directly switches to the alternate path, and the multicast path is forwarded by the alternate path.
  • the upstream communication node may be configured to perform the primary path and the backup path switch by the local management policy.
  • the non-switching point detects that the primary path is faulty, the non-switching point sends a failure notification message to the upstream convergence node of the primary path. See Figure 8 for details.
  • FIG. 8 is still another flow chart of the fault notification method disclosed in the embodiment of the present invention. Includes:
  • S801 Detecting whether the primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on the PIM protocol.
  • a schematic diagram of the forwarding path can be seen in Figure 2, which will not be explained.
  • the types of faults in which the primary path fails include node faults, link faults, and multicast stream faults.
  • the fault detection of the primary path may be performed by any one of the primary paths, as shown in the forwarding path diagram shown in FIG. 2, It is detected by node D whether the primary path has failed.
  • the non-switching point After the non-switching point detects that the primary path has failed, it obtains fault information, such as the fault type and address list.
  • the fault type can be a node fault or a link fault or a multicast stream fault.
  • the address list is a list of interface IP addresses connected to the faulty node on the non-switching node, and may also be a list of interface IP addresses connected to the non-switching node on the faulty node.
  • the address list When the fault type is a link fault, the address list may be a list of interface IP addresses connected to the faulty link on the non-switching node, or may be a list of interface IP addresses of nodes connected to the non-switching node through the faulty link.
  • the address list When the fault type is a multicast stream fault, the address list is a faulty multicast stream identifier.
  • the multicast stream identifier can be a multicast group address, or both a multicast group address and
  • the IP multicast tree in which the forwarding path resides is a centrally distributed multicast system.
  • the faults of the main path in the distributed multicast system of the center also include node faults, link faults, and multicast stream faults.
  • the non-switching point detects that the primary path is faulty, the fault notification message can be sent in the primary path of the same forwarding path.
  • the node has an inbound interface and an outbound interface.
  • the multicast forwarding table is used to record the mappings between the interfaces of the two nodes that form each link in a forwarding path.
  • the node has a public inbound interface and a public outbound interface
  • the multicast forwarding table is a shared public forwarding table, which records two nodes constituting each link in a forwarding path. Correspondence of the public interface.
  • the fault information is encapsulated in a fault notification packet.
  • the fault notification packet can be a UDP packet.
  • the format of the packet see Figure 3.
  • the format of the UDP packet in the embodiment of the present invention is the same as in the previous embodiment.
  • the format of the UDP packet is the same.
  • the difference between the two is: The value of the type is different.
  • the type in the embodiment of the invention indicates the type of failure.
  • the type is 0x11, it indicates a fault.
  • the node is faulty.
  • the address list encapsulates the IP address list of the interface connected to the faulty node on the non-switching node that detects the fault of the primary path. It can also be the non-switching of the fault on the faulty node and the detection of the fault of the primary path.
  • a list of IP addresses of the interfaces connected to the node When the type is 0x12, it indicates that the fault type is the link fault advertised by the upstream hop-by-hop.
  • the address list encapsulates the IP address list of the interface connected to the faulty link on the non-switching node that detects the fault of the primary path.
  • a list of interface IP addresses of nodes connected to the failed link by the non-switching node that detected the primary path failure When the type is 0x13, the fault type is a single multicast stream fault advertised by the upstream hop-by-hop.
  • the address list encapsulates the identifier of the faulty multicast stream, which can be a multicast group address or a multicast group address. Multicast source address. When the type is 0x14, it indicates that the fault type is the upstream hop-by-hop advertised node fault in the centrally-distributed multicast system.
  • the address list encapsulates the interface connected to the faulty node on the non-switching node that detects the primary path fault.
  • the IP address list can also be a list of interface IP addresses on the faulty node that are connected to the non-switching node that detected the primary path failure.
  • the type is 0x15
  • the fault is of the upstream hop-by-hop advertised link failure in the centrally-distributed multicast system.
  • the address list encapsulates the non-switched node that detects the primary path fault and is connected to the faulty link.
  • the list of interface IP addresses may also be a list of interface IP addresses of nodes connected to the non-switching node that detected the failure of the primary path through the failed link.
  • the type is 0x16
  • it indicates that the fault type is the upstream hop-by-hop advertised multicast stream fault in the centrally-distributed multicast system.
  • the address list encapsulates the identifier of the faulty multicast stream, which can be the multicast group address. It can also be a multicast group address and a multicast source address.
  • the above types can be set to other different values as needed, as long as different fault types can be distinguished.
  • the meanings of the length, number, and address list fields have the same meanings as the length, number, and address list fields in the UDP message described in the previous embodiment.
  • the type value indicates that the fault type is the node hop-by-hop advertised node fault or link fault or the upstream hop-by-hop protocol in the centrally released multicast system
  • the format of the address list can be seen in Figure 4 when the node failure is reported or the link of the upstream hop-by-hop advertisement is faulty in the centrally distributed multicast system.
  • the format of the address list can be seen in Figure 5 when the type indicates that the fault type is a single multicast stream fault advertised by the upstream hop-by-hop or the upstream hop-by-hop advertised multicast stream fault in the centrally-published multicast system.
  • the non-switching point sends the fault notification message to the upstream fusion node hop by hop. Specifically, after detecting the primary path fault, the non-switching point searches for the multicast forwarding table, and uses its own address as the source address. The address of the previous hop node corresponding to the non-switching point in the multicast forwarding table is the destination address. The hop node sends a fault notification packet. When the last hop node receives the fault notification message, the node is used as the access node, and the address of the access node is the source address, and the address of the previous hop node corresponding to the access node is the destination address.
  • the previous hop node corresponding to the access node sends a failure notification message until the failure notification message reaches the upstream fusion node.
  • the upstream convergence node After receiving the fault notification packet, the upstream convergence node ends the fault notification packet transmission and directly performs the active/standby path switchover.
  • the last hop node is a node close to the multicast source.
  • the upstream convergence node is the upstream intersection of the two paths.
  • the upstream is the end of the forwarding path that is close to the multicast source when there are two fused nodes in the forwarding path.
  • the forwarding path diagram shown in Figure 2 has two outbound interfaces, the primary outbound interface, and one standby interface.
  • previous hop node determines When it is an upstream convergence node, it ends the sending of the fault notification packet.
  • the network management can also pre-configure the identifier to identify the upstream fusion node as the switching point.
  • the last hop node receives the fault notification message, it determines whether it has the identifier.
  • the previous hop node judges that it has an identifier, it determines that it is a swim convergence node, and ends the transmission of the fault notification message.
  • each node on the primary path may also obtain the address of the upstream fusion node in advance, and compare its own address with the address of the upstream fusion node. When the two addresses are the same, It is determined that it is an upstream fusion node, and the failure notification is transmitted. When the two addresses are different, it is determined that it is not the upstream convergence node, and the failure notification message is sent to the upstream hop node.
  • the obtaining, by the each node on the primary path, the address information of the upstream fusion node in advance may be performed according to step S303.
  • the shared common forwarding table is searched to determine the previous hop node corresponding to the public inbound interface of the non-switching point, and the non-switching point
  • the address is the source address
  • the address of the previous hop node corresponding to the public inbound interface of the non-switching point is the destination address.
  • the fault notification packet is sent to the upstream fused node hop by hop according to the above manner.
  • the fault notification packet is a UDP packet.
  • the non-switching point can send UDP packets to the upstream hop node multiple times. • Multiple transmissions of the message can be sent periodically for non-switching points or irregularly. The number of transmissions can be different according to different application scenarios when ensuring reliable transmission of packets.
  • the upstream convergence node may switch the multicast stream on the primary path to the alternate path according to the fault notification message according to the description of step S103.
  • the upstream convergence node After detecting the fault of the primary path, the upstream convergence node directly switches to the alternate path and forwards the multicast stream forwarded by the alternate path.
  • the embodiment of the present invention may further specify that the downstream convergence node performs the primary path and the alternate path switching by using the local management policy, and sends a fault to the downstream fusion node of the primary path when the primary path is detected to be faulty. Announcement message.
  • FIG. 9 is still another flowchart of the method for fault notification disclosed in the embodiment of the present invention. include:
  • S901 Detecting whether the primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on the PIM protocol.
  • a schematic diagram of the forwarding path can be seen in Figure 2, which will not be explained.
  • the types of faults in which the primary path fails include node faults, link faults, and multicast stream faults.
  • the fault detection of the primary path may be detected by any non-switching point in the primary path, such as: In the schematic diagram of the forwarding path shown in Figure 2, node D detects whether the primary path is faulty.
  • the non-switching point After the non-switching point detects that the primary path has failed, it obtains fault information, such as the fault type and address list.
  • the fault type can be a node fault or a link fault or a multicast stream fault.
  • the address list is a list of interface IP addresses connected to the faulty node on the non-switching node, and may also be a list of interface IP addresses connected to the non-switching node on the faulty node.
  • the address list When the fault type is a link fault, the address list may be a list of interface IP addresses connected to the faulty link on the non-switching node, or may be a list of interface IP addresses of nodes connected to the non-switching node through the faulty link.
  • the address list When the fault type is a multicast stream fault, the address list is a faulty multicast stream identifier.
  • the multicast stream identifier can be a multicast group address, or both a multicast group address and
  • the multicast source uses the central distribution structure, that is, the location of the multicast source is relatively centralized, different multicast flows are sent using the same forwarding path, that is, different multicast forwarding tables share the common inbound interface and outbound interface.
  • the IP multicast tree where the forwarding path resides is the centrally distributed multicast system.
  • the main road in the distributed multicast system of the center Path failures also include node failures, link failures, and multicast flow failures.
  • the non-switching point detects that the primary path is faulty, the fault notification packet can be sent in the primary path of the same forwarding path.
  • the node has an inbound interface and an outbound interface.
  • the multicast forwarding table is used to record the mappings between the interfaces of the two nodes that form each link in a forwarding path.
  • the node has a public inbound interface and a public outbound interface
  • the multicast forwarding table is a shared public forwarding table, which records two nodes constituting each link in a forwarding path. Correspondence of the public interface.
  • the fault information is encapsulated in a fault notification packet.
  • the fault notification packet can be a UDP packet.
  • Figure 10 shows the IPv4 fault notification packet, including: IP header, UDP header, and data part.
  • the data section includes a list of types, lengths, quantities, and addresses. among them:
  • the type indicates the type of failure.
  • the fault type is a single multicast stream fault that is advertised by the downstream multicast.
  • the address list encapsulates the identifier of the faulty multicast stream, which can be a multicast group address or a multicast group address. Multicast source address.
  • the type is 0x22, it indicates that the fault type is a node fault of the downstream multicast advertisement.
  • the address list encapsulates the IP address list of the interface connected to the faulty node on the non-switching node that detects the fault of the primary path. It can also be a faulty node. A list of interface IP addresses connected to non-switching nodes that have detected a primary path failure.
  • the fault type is the link fault of the downstream multicast advertisement.
  • the address list encapsulates the IP address list of the interface connected to the faulty link on the non-switching node that detects the fault of the primary path.
  • the type is 0x24, it indicates that the fault type is a node fault of the downstream multicast advertisement in the centrally distributed multicast system.
  • the address list encapsulates the interface connected to the faulty node on the non-switching node that detects the fault of the primary path.
  • the IP address list can also be a list of interface IP addresses on the faulty node that are connected to the non-switching node that detected the primary path failure.
  • the fault type is the central release type.
  • the link of the downstream multicast advertisement is faulty in the multicast system.
  • the address list encapsulates the IP address list of the interface connected to the faulty link on the non-switched node that detects the fault of the primary path. It can also detect the fault of the primary path.
  • the non-switching node is a list of interface IP addresses of the nodes connected through the failed link. If the type is 0x26, the fault is the multicast stream advertised by the downstream multicast system.
  • the address list encapsulates the identifier of the faulty multicast stream, which can be the multicast group address. It can also be a multicast group address and a multicast source address.
  • the above types can be set to other different values as needed, as long as different fault types can be distinguished.
  • the source address and destination address in the IP packet header are set according to the fault type.
  • the fault type is the fault of the downstream multicast advertised node or the downstream multicast advertised link fault or the downstream multicast advertised multicast flow fault
  • the source address is set as the source address of the faulty multicast stream
  • the destination address is set as the fault group.
  • the group address of the stream is the group address of the stream.
  • the fault type is the node of the downstream multicast advertisement in the centrally-distributed multicast system, or the link failure of the downstream multicast advertisement in the central-distributed multicast system or the downstream multicast advertisement under the central distribution system
  • the source address is the source address of one of the multiple multicast streams sharing the common forwarding entry
  • the destination address is the destination address of one of the multiple multicast streams sharing the common forwarding entry.
  • the source address and the destination address of the IP address header are set to the source address and the group address of the faulty multicast stream respectively.
  • the fault notification packet is forwarded as a data packet at the data plane of the node, and the data packet is forwarded according to the data packet.
  • the option field contains a router alarm option that indicates that the data layer of the downstream fusion node has received the failure.
  • the non-switching point sends the fault notification packet to the upstream fused node
  • the fault advertised packet is sent as the control packet at the control plane of the node. Therefore, the fault notification packet sent to the upstream fused node does not include the router. Alarm option.
  • the control plane of the upstream convergence node After receiving the fault notification packet, the control plane of the upstream convergence node performs the master/slave path switchover.
  • S903 Send the fault advertisement packet to the downstream convergence node.
  • the downstream convergence node may be a plurality of nodes, such as a leaf node of the multicast tree, and the method for multicast transmission is used to send the failure notification message to multiple downstream fusion nodes. Specifically:
  • the multicast forwarding table is searched for, and the fault notification packet is hop-by-hop to the downstream fusion node according to the mapping between the interfaces of the two nodes in the multicast forwarding table.
  • the shared common forwarding table can be searched for, according to the correspondence between the public interfaces of the two nodes in the shared public forwarding table.
  • the advertisement packet is sent to the downstream convergence node hop by hop.
  • the fault notification packet is a UDP packet.
  • the non-switching point can send UDP packets to the downstream converged node multiple times. Multiple transmissions of a message may be sent periodically for non-switching points, or may be sent irregularly. The number of transmissions can be different according to different application scenarios when ensuring reliable transmission of packets.
  • the downstream convergence node After receiving the fault notification packet, the downstream convergence node switches the multicast stream on the primary path to the alternate path according to the fault notification message according to the description of step S103.
  • the downstream fusion node detects that the primary path fails, the downstream fusion node does not send the fault information to any node in the primary path. After detecting that the primary path fails, the upstream convergence node directly switches to the alternate path, and the multicast path is forwarded by the alternate path.
  • the present invention discloses a detecting device.
  • the structural schematic diagram is as shown in FIG. 11, and includes: a fault detecting module 11, a packaging module 12, and a transmitter 13. among them:
  • the fault detection module 11 is configured to detect whether the primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on a protocol-independent multicast protocol.
  • a schematic diagram of the forwarding path can be seen in Figure 2, which will not be explained.
  • the types of faults in which the primary path fails include node faults, link faults, and multicast stream faults.
  • the fault detection of the primary path may be detected by any non-switching point in the primary path, such as: In the schematic diagram of the forwarding path shown in Figure 2, node C detects whether the primary path is faulty. Where: Non-switching point is the main path When the fault occurs, the node in the main path is not responsible for the active/standby path switching.
  • the encapsulation module 12 is configured to obtain the fault information that the fault detection module 11 detects that the main path is faulty, and encapsulates the fault information into a fault notification message.
  • the format of the fault notification packet and the fault notification packet refer to the description in the fault notification method shown in Figure 1.
  • the transmitter 13 is configured to send a fault notification message.
  • the structure of the transmitter 13 is shown in FIG. 12, and includes: a first transmitter 131, configured to directly send the fault advertisement packet to an upstream convergence node of the primary path, so that the upstream convergence node sends the multicast traffic on the primary path. Switch to the alternate path.
  • the transmitter 13 further includes: a second transmitter 132, configured to send the fault notification message to a forwarding device of the primary path, where the forwarding device sends the fault notification to the primary path Switching point so that the switching point switches multicast traffic on the primary path to the alternate path.
  • a second transmitter 132 configured to send the fault notification message to a forwarding device of the primary path, where the forwarding device sends the fault notification to the primary path Switching point so that the switching point switches multicast traffic on the primary path to the alternate path.
  • the determination of the switching point can be determined according to the local management policy.
  • the local management policy is to switch between the primary path and the alternate path by the designated fusion node when it is detected that the primary path fails. For example, if the specified fused node is an upstream fused node, it indicates that when the primary path fails, the upstream fused node performs the switch between the primary path and the alternate path.
  • the upstream Fusion Node A in the primary path switches between the primary and backup paths when the primary path fails.
  • the upstream fusion node A is a switching point, and the other nodes are non-switching points.
  • the non-switching point B detects that the primary path is faulty, it sends a fault notification message to the switching point, that is, the upstream convergence node A.
  • the downstream convergence node D can also serve as a switching point.
  • the non-switching point A detects that the primary path fails it sends a failure notification message to the downstream fusion node D.
  • the upstream fusion node A detects that the primary path fails, and the upstream fusion node A does not need to go to any of the primary paths.
  • the node sends a fault packet and directly switches the active and standby paths.
  • the multicast stream forwarded by the primary path is switched to the standby path, and the multicast stream is forwarded by the alternate path.
  • the encapsulating module 12 of the detecting device encapsulates the fault information of the main path failure into the fault notification message, and is directly sent by the first transmitter 131 to the upstream fusion node of the main path or sent by the second transmitter 132.
  • the forwarding device is sent to the switching point of the primary path by the forwarding device.
  • the present invention also discloses a forwarding device.
  • the schematic diagram of the structure is as shown in FIG. 13, and includes: a receiving unit 14, a packaging unit 15, and a repeater 16. among them:
  • the receiving unit 14 is configured to receive a fault notification message.
  • the repeater 16 is configured to send a re-encapsulated failure notification message.
  • the above forwarding device is applicable to a scenario in which an upstream fusion node in the primary path is used as a switching point.
  • the forwarding device further includes: a judging unit 17, as shown in FIG. Fig. 14 is a block diagram showing another structure of the forwarding device disclosed in Fig. 13 based on Fig. 13.
  • the determining unit 17 is configured to determine whether it is an upstream fusion node, that is, a switching point of the primary path, and notify the encapsulating unit to re-encapsulate the receiving unit when determining that it is not the upstream fusion node in the primary path. Fault notification message.
  • the judging unit 17 can judge whether it is the upstream fusion node according to the description in the failure notification method shown in Fig. 8.
  • the invention also discloses a fault notification system.
  • the structure diagram is as shown in FIG. 15, and includes: a detecting device 18 and a first switching device 20. among them:
  • the detecting device 18 is configured to detect whether the primary path in the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on the protocol-independent multicast protocol, and obtains fault information of the primary path fault, and encapsulates the fault information into The failure notification message is sent, and the failure notification message is sent.
  • the first switching device 20 is configured to receive the fault notification message, and switch the multicast traffic on the primary path to the standby path according to the fault notification message. Wherein: the first switching device 20 is an upstream fusion node of the primary path.
  • the fault notification system may further include a forwarding device 19, configured to receive the fault notification message, and use the address of the fault as the source address in the fault notification packet, and the address of the corresponding previous hop node as the fault notification packet.
  • the destination address re-encapsulating the received fault notification message and sending the re-encapsulated failure notification message.
  • the first switching device 20 is further configured to receive the re-encapsulated failure notification message, and switch the multicast traffic on the primary path to the alternate path according to the re-encapsulated failure notification message.
  • the message is a UDP message.
  • the detecting device 18 and the forwarding device 19 can send UDP packets to the corresponding upper hop nodes multiple times. • Multiple transmissions of the text can be sent periodically or irregularly. The number of transmissions can be different according to different application scenarios when ensuring reliable transmission of packets.
  • FIG. 16 is another fault notification system according to the present disclosure, including: a detecting device 21 and a second switching device 22. among them:
  • the detecting device 21 is configured to detect whether the primary path of the IP multicast tree forwarding path is faulty, and the IP multicast tree forwarding path is established based on the protocol-independent multicast protocol, and obtains fault information of the primary path, and encapsulates the fault information into
  • the fault notification packet is sent to the downstream multicast
  • the second switching device 22 is configured to receive the fault notification packet, and switch the multicast traffic on the primary path according to the fault notification packet. Go to the alternate path.
  • the second switching device 22 is a downstream fusion node of the primary path.
  • the message is a UDP message. In order to ensure reliable transmission of the message, the detecting device 21 and the forwarding device 22 can send the UDP message to the corresponding previous hop node multiple times.
  • the multiple transmissions of the message can be sent periodically or irregularly.
  • the number of transmissions can be different according to different application scenarios when ensuring reliable transmission of packets.
  • the downstream convergence node may switch the multicast stream on the primary path to the standby path according to the fault notification message according to the description of step S103.
  • the methods or steps described in connection with the embodiments disclosed herein may be implemented directly in a combination of hardware and software modules.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

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

Abstract

La présente invention concerne un procédé de notification d'incidents, un appareil de détection, un appareil de réacheminement, un système, et une structure de données. Le procédé de notification d'incidents consiste: à détecter si un incident se produit dans le chemin principal des chemins de réacheminement de l'arbre de multidiffusion du Protocole Internet (IP) établis sur la base du protocole de multidiffusion indépendant des protocoles; à obtenir une information d'incident quand un nœud de non-commutation détecte qu'un incident se produit dans le chemin principal, puis à encapsuler l'information d'incident dans un message de notification d'incident; et à transmettre à un nœud de commutation du chemin principal le message de notification d'incident. Avec la solution technique mentionnée, dans le procédé de notification d'incident, selon les modes de réalisation de la présente invention, quand le nœud de non-commutation détecte qu'un incident se produit dans le chemin principal des chemins de réacheminement de l'arbre de multidiffusion IP, un message de notification d'incident est transmis au nœud de commutation du chemin principal. Par comparaison avec l'état de la technique, quand le nœud de non-commutation détecte qu'un incident se produit dans le chemin principal des chemins de réacheminement de l'arbre de multidiffusion IP, il n'est plus nécessaire de transmettre les messages de notification d'incident à tous les nœuds du réseau de multidiffusion auquel appartient l'arbre de multidiffusion IP, ce qui réduit le nombre de messages invalides.
PCT/CN2011/077470 2011-07-22 2011-07-22 Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données WO2012106915A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/077470 WO2012106915A1 (fr) 2011-07-22 2011-07-22 Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données
CN201180001332.6A CN102726000B (zh) 2011-07-22 2011-07-22 故障通告方法、检测装置、转发装置及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/077470 WO2012106915A1 (fr) 2011-07-22 2011-07-22 Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données

Publications (1)

Publication Number Publication Date
WO2012106915A1 true WO2012106915A1 (fr) 2012-08-16

Family

ID=46638130

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077470 WO2012106915A1 (fr) 2011-07-22 2011-07-22 Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données

Country Status (2)

Country Link
CN (1) CN102726000B (fr)
WO (1) WO2012106915A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023202645A1 (fr) * 2022-04-22 2023-10-26 华为技术有限公司 Procédé de traitement de défaillance, dispositif de réseau, support d'enregistrement et système sur puce

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103973471B (zh) * 2013-01-31 2018-11-02 中兴通讯股份有限公司 一种trill分发树故障的通告方法和装置
CN103384164A (zh) * 2013-05-10 2013-11-06 上海斐讯数据通信技术有限公司 光线路终端业务防中断系统及防业务中断方法
CN103595507A (zh) * 2013-11-15 2014-02-19 烽火通信科技股份有限公司 分组网络系统中的内部信息传送装置及传送方法
CN104270298B (zh) * 2014-09-30 2018-10-09 新华三技术有限公司 一种vxlan网络中的报文转发方法及装置
CN105610708B (zh) 2014-10-31 2019-11-12 新华三技术有限公司 一种trill网络中组播frr的实现方法和rb设备
CN106301823B (zh) * 2015-05-19 2020-12-18 中兴通讯股份有限公司 一种关键组件的故障告警方法、装置及大数据管理系统
CN107171883B (zh) 2016-03-08 2020-04-28 华为技术有限公司 检测转发表的方法、装置和设备
CN107979499A (zh) * 2018-01-26 2018-05-01 福州大学 基于有状态数据平面的网络多点故障恢复方法
CN108600040B (zh) * 2018-03-16 2022-03-15 国电南瑞科技股份有限公司 一种基于高可用检测节点的分布式系统节点故障检测方法
CN108449276B (zh) * 2018-03-23 2021-01-26 新华三技术有限公司 路由收敛方法及装置
CN109361597B (zh) * 2018-12-14 2021-06-04 武汉光迅信息技术有限公司 一种多路由选择方法和装置
CN110113259B (zh) * 2019-04-26 2021-08-06 新华三技术有限公司 路径状态通知方法、路径切换方法、转发设备及系统
CN116827855A (zh) * 2020-11-23 2023-09-29 华为技术有限公司 一种通告网络设备处理能力的方法、设备和系统
CN113489626B (zh) * 2021-09-06 2021-12-28 网络通信与安全紫金山实验室 路径故障检测及通告的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101631043A (zh) * 2009-08-05 2010-01-20 杭州华三通信技术有限公司 组播故障恢复方法、组播路由器及系统
CN101656679A (zh) * 2009-09-25 2010-02-24 华为技术有限公司 一种组播快速收敛方法、路由器和通信系统
CN101753581A (zh) * 2010-01-15 2010-06-23 华为技术有限公司 一种不间断数据转发方法及装置
CN101777997A (zh) * 2010-01-21 2010-07-14 中兴通讯股份有限公司 一种实现网络链路流量切换的方法和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100454893C (zh) * 2005-03-21 2009-01-21 中兴通讯股份有限公司 一种快速组播的实现方法
CN101159681A (zh) * 2007-09-28 2008-04-09 杭州华三通信技术有限公司 实现快速重路由的方法和节点

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101631043A (zh) * 2009-08-05 2010-01-20 杭州华三通信技术有限公司 组播故障恢复方法、组播路由器及系统
CN101656679A (zh) * 2009-09-25 2010-02-24 华为技术有限公司 一种组播快速收敛方法、路由器和通信系统
CN101753581A (zh) * 2010-01-15 2010-06-23 华为技术有限公司 一种不间断数据转发方法及装置
CN101777997A (zh) * 2010-01-21 2010-07-14 中兴通讯股份有限公司 一种实现网络链路流量切换的方法和系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023202645A1 (fr) * 2022-04-22 2023-10-26 华为技术有限公司 Procédé de traitement de défaillance, dispositif de réseau, support d'enregistrement et système sur puce

Also Published As

Publication number Publication date
CN102726000B (zh) 2017-06-16
CN102726000A (zh) 2012-10-10

Similar Documents

Publication Publication Date Title
WO2012106915A1 (fr) Procédé de notification d'incidents, appareil de détection, appareil de réacheminement, système, et structure de données
JP6165850B2 (ja) ダウンストリーム通知パケットを用いたプロトコル独立マルチキャスト（ｐｉｍ）高速再ルーティング方法論の強化
EP2028768B1 (fr) Procédé, système et dispositif de protection de service, basés sur l'absence de connexion
US8218429B2 (en) Method and device for multicast traffic redundancy protection
KR102153019B1 (ko) 업스트림 활성화 패킷들에 의한 pim 고속 리라우팅에 대한 향상
US9059902B2 (en) Procedures, apparatuses, systems, and computer-readable media for operating primary and backup network elements
US20130021896A1 (en) Method, system, and device for protecting multicast in communication network
US20120236730A1 (en) Method, device and system for processing service traffic based on pseudo wires
WO2010069175A1 (fr) Procédé, système et équipement d'établissement d'une détection de réexpédition bidirectionnelle
US20060268729A1 (en) Methods and apparatus for monitoring link integrity for signaling traffic over a path traversing hybrid ATM/Ethernet infrastructure in support of packet voice service provisioning
WO2013071801A1 (fr) Procédé, dispositif et système pour détecter un réseau en anneau à commutation multiprotocole par étiquette
WO2012068996A1 (fr) Procédé et dispositif de détection d'état de liaisons
EP3217608B1 (fr) Méthodes et dispositifs de délai d'inversion de commutation
US8625406B2 (en) Multicast fast re-route
WO2009092257A1 (fr) Procédé de détection de défaut et dispositif pour réseau 'provider backbone transport'
KR20150033681A (ko) 연결 실패 시에 홈 네트워크에 대한 재라우팅을 인에이블시키는 방법 및 시스템
WO2012062164A1 (fr) Procédé, dispositif, et système pour commutation de voie
CN105338535A (zh) 一种使用移动终端进行无线组网的方法
CN101296105B (zh) 一种组播快速切换的方法、系统和三层网络设备
WO2010000158A1 (fr) Procédé, équipement et système de contrôle d'état de chemin
CN102281165A (zh) 一种基于服务质量的故障检测方法、系统和装置
CN102611566B (zh) 一种恢复用户业务的方法和装置
WO2014146541A1 (fr) Système de convergence de cdn et de réseau, procédé de sélection de module de planification et support de stockage informatique
WO2010006524A1 (fr) Procédé de multidiffusion fiable, appareil et système fournisseur de couche supérieure
CN101299722A (zh) 一种改进的快速重路由方法和一种网络设备

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001332.6

Country of ref document: CN

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

Ref document number: 11858182

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: 11858182

Country of ref document: EP

Kind code of ref document: A1