[go: up one dir, main page]

WO2009074057A1 - Procede de protection de nœud de tete, systeme et dispositif pour le trajet de commutation d'etiquettes point a multipoint - Google Patents

Procede de protection de nœud de tete, systeme et dispositif pour le trajet de commutation d'etiquettes point a multipoint Download PDF

Info

Publication number
WO2009074057A1
WO2009074057A1 PCT/CN2008/073184 CN2008073184W WO2009074057A1 WO 2009074057 A1 WO2009074057 A1 WO 2009074057A1 CN 2008073184 W CN2008073184 W CN 2008073184W WO 2009074057 A1 WO2009074057 A1 WO 2009074057A1
Authority
WO
WIPO (PCT)
Prior art keywords
mhn
bhn
head
node
lsp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2008/073184
Other languages
English (en)
Chinese (zh)
Inventor
Guoyi Chen
Wei Cao
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 WO2009074057A1 publication Critical patent/WO2009074057A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/403—Bus networks with centralised control, e.g. polling

Definitions

  • Head node protection method system and device for point-to-multipoint label switched path
  • the present invention relates to the field of communications technologies, and in particular, to a head node protection method, system, and device based on a point-to-multipoint label switching path (P2MP LSP).
  • P2MP LSP point-to-multipoint label switching path
  • Multicast is a one-to-many multiparty communication method. Different from the commonly used unicast technology, multicast technology can reduce the consumption of network resources by multi-party communication by establishing an optimal multicast forwarding path and reducing the replication of data content.
  • Multi-protocol label switching is a routing technology widely used in IP networks. Label distribution is generally used by Label Distribution Protocol (LDP). In the past, MPLS was mainly used for unicast IP forwarding. With the development of multicast technology and the rise of Internet Protocol Television (IPTV), MPLS multicast has gradually become a research hotspot. There are two main methods for constructing P2MP LSPs: LDP-based and Resource Reservation Protocol-Traffic Engineering (RSVP-TE). From the current technical development, RS VP-TE The way is gradually becoming mainstream.
  • LDP Label Distribution Protocol
  • RSVP-TE Resource Reservation Protocol-Traffic Engineering
  • MPLS-based multicasting currently offers a variety of protection schemes, the most common being path protection and local protection.
  • the path protection is implemented by establishing an additional standby P2MP LSP in parallel with the existing primary P2MP LSP.
  • the existing primary LSP fails, the traffic is directly switched to the standby LSP.
  • Both the primary LSP and the backup LSP are configured at the head end, and they are one-to-one.
  • Link protection is to establish a unicast backup LSP that bypasses the protected link in advance for the link to be protected, so that there is a problem when the protected link is faulty.
  • the data traffic can be switched to the standby LSP; the node protection is to establish a unicast backup LSP bypassing the protected node in advance, so as to data traffic when the protected node fails.
  • the backup LSP and the primary LSP can be one-to-many.
  • the backup LSP can protect multiple active LSPs.
  • bypass tunnel For a link or node that needs to be protected, a point-to-multipoint bypass tunnel that bypasses the protected link or node is established in advance. (P2MP Bypass Tunnel), which greatly reduces the replication of messages when the protected path or node fails.
  • the Applicant has found that the prior art has at least the following drawbacks: For P2MP LSPs, although there are multiple protection techniques, there is no scheme for protecting the head node. However, in actual deployments, especially in the deployment of IPTV, the protection requirements for the head node are getting stronger and stronger; because the failure of the head node means the interruption of all user services under the entire P2MP tree. Protection from the head node is more important than any other protection in terms of protection and in terms of protection.
  • the embodiments of the present invention provide a method, a system, and a device for protecting a head node of a point-to-multipoint label switching path to implement protection on a head node.
  • the embodiment of the invention provides a method for protecting a head node of a point-to-multipoint label switching path, the method comprising:
  • the backup head node BHN establishes itself in the process of forwarding data according to the LSP established by the MHN along its own and the aggregation node MP according to the point-to-multipoint head group identifier P2MP Head Group ID.
  • the BHN handover The primary head node forwards data along the backup LSP.
  • the embodiment of the present invention further provides a head node protection system for a point-to-multipoint label switching path of a backup head node BHN, including:
  • a primary head node MHN configured to forward data along an established LSP between the MHN and the aggregation node MP
  • the backup head node BHN is configured to establish a backup label switching path LSP to the aggregation node MP according to the P2MP Head Group ID, where the backup LSP does not include the primary head node MHN; when the head node switching condition is met, the host is switched to the primary head a node, and forwards data along the backup LSP.
  • the embodiment of the present invention further provides a backup head node BHN, including:
  • a backup LSP establishing unit configured to establish a backup LSP from the BHN to the MP according to the P2MP Head Group ID, where the backup LSP does not include the MHN;
  • a switching unit configured to: when the head node switching condition is met, switch the BHN as a primary head node, and notify the data transmission unit of the message that the BHN is switched to be a primary head node;
  • a data transmission unit configured to forward data along the backup LSP.
  • An embodiment of the present invention further provides a primary head node MHN, including:
  • a label switching path LSP establishing unit configured to establish an LSP from the MHN to the aggregation node MP, and a switching unit, configured to switch itself to a non-primary node when the head node switching condition is met, to generate a stop transmission notification;
  • a data transmission unit configured to forward data along the established LSP between the MHN and the MP; and, after receiving the stop transmission notification from the switching unit, stop forwarding data along the established LSP between the MHN and the MP.
  • the embodiment of the present invention provides a solution for protecting a head node.
  • the BHN establishes a backup LSP according to the P2MP Head Group ID.
  • the P2MP Head Group ID is globally unique. Therefore, the protected LSP established by the MHN and the backup LSP share the same P2MP. Head Group ID.
  • the backup LSP is considered as a backup path established for link protection between the MP and the MHN.
  • the message from the LSP or the backup LSP carries the same message.
  • P2MP Head Group ID therefore, even if the head node is switched, the node under the MP does not feel the change of the head node, which protects the head node well, and improves the protection mechanism of the P2MP LSP; Scale deployment.
  • FIG. 1 is a schematic diagram of a network structure for protecting a primary head node according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a process of protecting a head node of a P2MP LSP according to an embodiment of the present invention.
  • MHN (Master Head Node): For a given P2MP LSP, MHN is the head node that originally initiated the establishment of this P2MP LSP;
  • Aggregate node For a P2MP LSP, in this scheme, those leaf points or branch points directly connected to the MHN are called MP nodes, and the MP nodes may be one or more. ;
  • BHN Backup Head Node
  • Point-to-multiple head group Define one or more point-to-multipoint head nodes as point-to-multipoint head groups. Nodes in a point-to-multipoint head group can be used as the head of all P2MP LSPs in a P2MP tunnel. node.
  • FIG. 1 is a schematic diagram of a network structure for protecting a primary head node according to an embodiment of the present invention.
  • the thick solid line in the figure is the established P2MP LSP, and the line with the arrow is the LSP tunnel.
  • FIG. 2 is a schematic diagram of a process of protecting a head node of a P2MP LSP according to an embodiment of the present invention.
  • Step 201 The BHN establishes its own backup LSP to all MPs according to the P2MP Head Group ID, and the backup LSP does not include the MHN.
  • the P2MP Head Group ID can be obtained through static configuration or synchronization. You can manually configure the same P2MP Head Group ID on the MHN and BHN or configure it through the NMS.
  • the P2MP Head Group ID can also be obtained by synchronizing the MHN with the BHN.
  • ⁇ send the first ⁇ 2 ⁇ Head Group ID to the ⁇ through the synchronization message
  • BHN sends the second P2MP Head Group ID to the MHN through the synchronization message
  • MHN and The BHN selects one of the first P2MP Head Group ID and the second P2MP Head Group ID as the P2MP Head Group ID according to the same rule.
  • the first one of the first P2MP Head Group ID and the second P2MP Head Group ID is selected as the P2MP Head Group ID, or the first P2MP Head Group ID and the second P2MP Head Group ID are selected as the P2MP Head Group ID.
  • the P2MP Head Group ID is sent to the P2MP Head Group ID, which can correspond to the P2MP tunnel, in order to ensure the P2MP Head.
  • the P2MP Head Group ID can be one of the address of the MHN, the address of the BHN, the traffic engineering router identifier of the MHN, the TE Router ID, and the TE Router ID of the BHN. It can also be other globally unique addresses.
  • Step 202 Normally, the MHN forwards data along the established LSP between the MHN and the MP.
  • the backup LSP between the MPs forwards the data.
  • the MHN needs to obtain the basic information of the BHN, and then the MHN sends the path characteristic information of the P2MP LSP that needs to be protected by the head node to the BHN.
  • the path feature information that the MHN passes to the BHN can be carried through the RSVP-TE Path message, or a new message format can be defined to carry the information.
  • the manner in which the MHN needs to obtain the basic information of the BHN may include: the MHN obtains the basic information of the BHN by querying the network management; or, the MHN obtains the basic information of the BHN by using the received configuration information, or the MHN receives the received BHN from the BHN. Active notification, get basic information about BHN.
  • the basic information of the BHN includes address and capability information of the BHN.
  • the manner in which the foregoing MHN sends the path feature of the P2MP LSP that needs to be protected by the head node to the BHN includes: A path is established between the MHN and the BHN, and the path feature information of the P2MP LSP that needs to be protected by the head node is encapsulated in the newly defined message, and the path feature information is directly sent to the BHN by using the newly defined message; or,
  • the path information of the resource reservation protocol RSVP-TE based on the traffic engineering extension is extended, and the MHN directly sends the path feature information to the BHN through the extended Path message;
  • the MHN sends the path feature information to the MP through the extended Path message, and then the MP sends the received path feature information to the BHN; Or,
  • the MHN sends the path feature information to the BHN through the network management.
  • the foregoing method for extending the Path message of the RSVP-TE resource reservation protocol based on the traffic engineering extension includes: adding a new object (Object), or extending an existing object (Object).
  • the path feature information includes a point-to-multipoint session object (SESSION Object), a sender template object (SENDER_TEMPLATE Object), and all MP node address information; and may further include basic information of the BHN and other necessary information; or
  • the path feature information described above includes a point-to-multipoint identifier (P2MP ID) and an extended tunnel identifier (Extended Tunnel ID) in a point-to-multipoint session object, and a sender address (Sender Address) in the sender template object, Sub-Group Originator ID and point-to-multipoint (LSP ID LSP ID), and all MP node address information; and may further include basic information of the BHN and other necessary information.
  • the BHN When the BHN receives the Path message or the newly defined message, it analyzes the received message, extracts the path feature information from the BHN, and saves the path information. Then, the BHN uses the path feature information to establish one or more MHNs. Backup LSP from BHN to all MP nodes; these LSPs can be point-to-point LSPs or point-to-multipoint LSPs.
  • the path feature information includes a point-to-multipoint session object (SESSION Object), a sender template object (SENDER_TEMPLATE Object), and all MP node address information; or, the path feature information includes a point in a point-to-multipoint session object to Multi-point identifier (P2MP ID) and extended tunnel identifier (Extended Tunnel ID), sender address (Sender Address), sub-group Originator ID, and point-to-multipoint in the sender template object LSP ID (LSP ID), and all MP node address information.
  • P2MP ID point-to-multipoint session object to Multi-point identifier
  • Extended Tunnel ID Extended tunnel identifier
  • sender address Sender Address
  • sub-group Originator ID sub-group Originator ID
  • LSP ID point-to-multipoint in the sender template object LSP ID
  • the information received by the BHN may be from the MHN or the MP or the network management.
  • the foregoing path feature information should also include the basic information of the BHN
  • the steps for the BHN to establish a point-to-point LSP include:
  • the BHN generates a Path message for each MP, and sends the Path message to the MP.
  • the Path message carries the path feature information
  • the LSP is an identifier of the backup information of the P2MP LSP.
  • LSP establishment priority, retention priority, protection mode for example: node protection or link protection, whether local repair is allowed, whether some links should be included, whether certain links should be excluded, etc.
  • bandwidth requirements etc.
  • the MP After receiving the Path message, the MP allocates a label, reserves a resource, returns a response message to the BHN through a RESV message, and binds the LSP to the protected P2MP LSP (the binding here refers to the MP).
  • the path feature information carried in the Path message is compared with the path feature information of the existing LSP. If the Session Object and the LSP ID are the same, the backup LSP is associated with the protected P2MP LSP. Establishing; when receiving data from the backup LSP, the MP forwards the received data along a subtree with the MP as a root node, and the subtree is part of the protected P2MP LSP.
  • Point-to-point LSPs can be found in more detailed procedures for RFC3209 and RFC3471.
  • the steps for the BHN to establish a point-to-multipoint LSP include:
  • the BHN generates a Path message and sends it to the MP.
  • the Path message carries the path feature information, and the LSP is the identifier of the backup information of the P2MP LSP.
  • the Path message can also carry the backup LSP establishment priority and keep the priority. , protection mode (for example: node protection or link protection, whether local repair is allowed, whether some links should be included, whether some links should be excluded, etc.), bandwidth requirements, etc.;
  • the Path generated by BHN The message may be one or more. If the BHN generates a Path message, the Path message belongs to all the MPs. If the BHN generates multiple Path messages, the following two situations may occur: Each Path message corresponds to an MP. Or, a Path message corresponds to multiple MPs, which can be determined according to actual needs; BHN establishes a P2MP LSP with BHN as the root and all MP nodes as leaves;
  • the MP After receiving the Path message, the MP allocates a label, reserves a resource, returns a response message to the BHN through a RESV message, and binds the LSP to the protected P2MP LSP (here) Binding refers to the fact that the MP uses the path feature information carried in the received Path message and the path feature information of the existing LSP. If the Session Object and the LSP ID are the same, the backup LSP is associated with the protected P2MP LSP. And completing the establishment of a backup LSP; when receiving data from the backup LSP, the MP forwards the received data along a subtree with the MP as a root node, where the subtree is the Protect a part of the P2MP LSP.
  • Point-to-multipoint LSPs can be referred to the existing standard specification RFC4875 for a more detailed setup process.
  • the MHN can actively trigger the handover of the head node.
  • the MHN sends a notification message to the BHN to inform the BHN to perform the handover of the head node.
  • the BHN After receiving the handover notification message, the BHN starts to be established along the BHN and the MP. LSP forwards data.
  • BHN can also find MHN failure through some fault detection mechanisms (such as bidirectional forwarding detection (BFD), fast Hello message); if BHN detects MHN failure, BHN switches itself to the primary node and starts to move along between BHN and MP.
  • the established LSP forwards data. That is to say, satisfying the head node switching condition may include: MHN active triggering head node switching or BHN detecting MHN failure.
  • the specific establishment mode may be that the MHN independently establishes the P2MP LSP, or the BHN retransmits the path feature information of the P2MP LSP from the MHN that needs the protection of the head node to the MHN.
  • the manner in which the BHN retransmits the path characteristic information to the MHN is the same as the transmission mode in 1.
  • the BHN After the MHN returns to the normal state, the BHN notifies the MHN to perform the head node handover or the MHN notifies the BHN to actively request the handover back.
  • the BHN stops forwarding data along the established LSP between the BHN and the MP, and the MHN acts as a head node along the MNN.
  • the established LSP between the MP and the MP forwards the data.
  • the manner in which the BHN notifies the MHN to perform the head node handover includes: the BHN directly notifies the MHN to perform the head node handover; or the BHN notifies the MHN to perform the head node handover through the network management.
  • the SESSION Object In the process of establishing a backup LSP, the SESSION Object carried in the path message is the same.
  • the SESSION Object defines a P2MP ID, a P2MP tunnel ID, and an Extended Tunnel ID.
  • the address of the sender is used to replace the address of the sender (Ingress LSR), and the address of the sender is replaced by the P2MP Head Group ID in the extended tunnel ID.
  • the embodiment of the present invention further provides a head node protection system for a point-to-multipoint label switching path of a backup head node BHN, including:
  • a primary head node for forwarding data with established LSPs along the MHN and the MP
  • a backup head node for establishing a backup label switching path from itself to all the aggregation nodes MP according to the P2MP Head Group ID LSP, the backup LSP does not include the MHN.
  • the BHN switches to the primary node, and the data is forwarded along the established backup LSP between the BHN and the MP.
  • the head node switching conditions are met: MHN actively triggers the head node switching or the BHN detects the MHN failure.
  • the MHN When the MHN is restored to the working state, it is also used to re-establish the P2MP LSP.
  • the BHN is further configured to notify the MHN to perform head node handover after the MHN returns to a normal state. After the handover, the BHN stops forwarding data along the established backup LSP between the MN and the MP, and the MHN acts as a head node edge. The L SP that has been established between it and the MP forwards the data.
  • the MHN is further configured to notify the BHN line head node to switch after the MHN returns to a normal state.
  • the BHN stops forwarding data along the established backup LSP between the BHN and the MP, and the MHN acts as a head node along the MNN.
  • the established L SP between the MP and the MP forwards the data.
  • the embodiment of the present invention further provides a backup head node BHN, including:
  • the backup LSP establishing unit is configured to establish a backup LSP to all MPs according to the P2MP Head Group ID, and the backup LSP does not include the MHN;
  • the switching unit is configured to switch itself to the primary node when the head node switching condition is met, and notify the data transmission unit;
  • a data transmission unit configured to forward data along an established backup LSP between the BHN and the MP.
  • the BHN also includes:
  • the synchronization unit is used to synchronize the point-to-multipoint head group identifier of the primary head node MHN and the backup head node BHN, P2MP Head Group ID.
  • the synchronization unit includes:
  • a sending subunit configured to send a second P2MP Head Group ID to the MHN by using a synchronization message
  • a receiving subunit configured to receive a first P2MP Head Group ID from the MHN
  • the selecting subunit is configured to select one of the first P2MP Head Group ID and the second P2MP Head Group ID as the P2MP Head Group ID according to the same rule as the MHN.
  • the synchronization unit includes:
  • a configuration subunit configured to configure a P2MP Head Group ID
  • a sending subunit configured to send the P2MP Head Group ID to the MHN by using a synchronization message.
  • the BHN may further include: an information feedback unit, configured to resend path feature information of the P2MP LSP from the MHN that needs to be protected by the head node to the MHN, to assist the MHN to re-establish the P2MP LSP.
  • an information feedback unit configured to resend path feature information of the P2MP LSP from the MHN that needs to be protected by the head node to the MHN, to assist the MHN to re-establish the P2MP LSP.
  • the BHN may further include a notification unit, configured to notify the MHN to perform the switchover of the head node, and then notify the switching unit of the switching information;
  • the switching unit is further configured to switch to a non-primary node according to the received notification, and notify the data transmission unit;
  • the data transmission unit is further configured to stop forwarding data along the established backup LSP between the BHN and the MP.
  • the embodiment of the present invention further provides a primary head node MHN, including:
  • An LSP establishing unit configured to establish an LSP from the MHN to all MPs
  • the switching unit is configured to switch itself to a non-primary node when the head node switching condition is met, and notify the data transmission unit to stop transmitting data;
  • a data transmission unit configured to forward data along an established LSP between the MHN and the MP; and after receiving the stop transmission notification from the switching unit, stop forwarding data along the established LSP between the MHN and the MP.
  • the primary node MHN may also include:
  • the synchronization unit is used to synchronize the point-to-multipoint head group identifier of the primary head node MHN and the backup head node BHN, P2MP Head Group ID.
  • the LSP establishment unit is also used to re-establish the P2MP LSP when the MHN is restored to the working state.
  • the switching unit is further configured to notify the BHN to perform head node switching after determining that the MHN returns to a normal state.
  • Such as ROM/RAM, diskette, optical disk, etc. including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the various embodiments of the present invention or portions of the embodiments described herein. method.
  • a computer device which may be a personal computer, server, or network device, etc.

Landscapes

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

Abstract

L'invention concerne un procédé de protection de nœud de tête, un système et un dispositif pour le trajet de commutation d'étiquettes point à multipoint. Le procédé selon l'invention comprend les étapes suivante : un nœud de tête de sauvegarde établit un trajet de commutation d'étiquettes de sauvegarde allant dudit nœud à un point de fusion, en fonction d'un identificateur de groupe de tête point à multipoint, le trajet de commutation d'étiquettes ne contenant pas le nœud de tête maître ; pendant le processus de transmission par le nœud de tête maître de données le long du trajet de commutation d'étiquettes allant dudit nœud au point de fusion, le nœud de tête de sauvegarde est commuté sur le nœud de tête maître et les données sont transmises le long du trajet de commutation d'étiquettes de sauvegarde lorsque la condition de commutation de nœud de tête est remplie. Le nœud de tête de sauvegarde établit le trajet de commutation d'étiquettes de sauvegarde en fonction de l'identificateur de groupe de tête point à multipoint. Pour le nœud en aval du point de fusion, le même identificateur de groupe de tête point à multipoint commun du trajet de commutation d'étiquettes protégé établi par le nœud de tête maître et du trajet de commutation d'étiquettes de sauvegarde provient du même identificateur de groupe de tête point à multipoint transporté par le message du trajet de commutation d'étiquettes ou du trajet de commutation d'étiquettes de sauvegarde. Ainsi, la protection du nœud de tête est réalisée efficacement et le mécanisme de protection du trajet de commutation d'étiquettes point à multipoint est amélioré.
PCT/CN2008/073184 2007-11-30 2008-11-25 Procede de protection de nœud de tete, systeme et dispositif pour le trajet de commutation d'etiquettes point a multipoint Ceased WO2009074057A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101954977A CN101453414B (zh) 2007-11-30 2007-11-30 点到多点标签交换路径的头节点保护方法、系统和设备
CN200710195497.7 2007-11-30

Publications (1)

Publication Number Publication Date
WO2009074057A1 true WO2009074057A1 (fr) 2009-06-18

Family

ID=40735444

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073184 Ceased WO2009074057A1 (fr) 2007-11-30 2008-11-25 Procede de protection de nœud de tete, systeme et dispositif pour le trajet de commutation d'etiquettes point a multipoint

Country Status (2)

Country Link
CN (1) CN101453414B (fr)
WO (1) WO2009074057A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113905364A (zh) * 2021-10-25 2022-01-07 广州通则康威智能科技有限公司 路由器上行数据溯源方法、装置、计算机设备及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101827025A (zh) * 2010-04-02 2010-09-08 华为技术有限公司 一种通信网络组播保护方法、系统及设备
CN102571601B (zh) * 2012-02-13 2018-05-15 中兴通讯股份有限公司 一种保证双向转发检测可靠性的方法及标记交换路径设备
CN105635223A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 用于同步网络状态的方法及装置
CN106302165A (zh) * 2015-05-22 2017-01-04 中兴通讯股份有限公司 一种点到多点隧道的保护方法和装置
CN119830364B (zh) * 2024-11-29 2025-09-23 清华大学 标签计算机系统和内存保护方法、装置及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1394053A (zh) * 2001-06-27 2003-01-29 华为技术有限公司 多协议标签交换快速保护倒换方法
CN1816035A (zh) * 2005-02-02 2006-08-09 华为技术有限公司 基于数据通信网的主备传输路径实现方法
US20070183317A1 (en) * 2006-02-03 2007-08-09 Jean-Philippe Vasseur Technique for determining whether to reestablish fast rerouted primary tunnels based on backup tunnel path quality feedback
US20070201355A1 (en) * 2006-02-27 2007-08-30 Vasseur Jean P Method and apparatus for determining a preferred backup tunnel to protect point-to-multipoint label switch paths
US20080123524A1 (en) * 2006-11-27 2008-05-29 Jean-Philippe Vasseur Failure protection for P2MP tunnel head-end node

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6980537B1 (en) * 1999-11-12 2005-12-27 Itt Manufacturing Enterprises, Inc. Method and apparatus for communication network cluster formation and transmission of node link status messages with reduced protocol overhead traffic
CN1838606A (zh) * 2005-03-24 2006-09-27 华为技术有限公司 使用mpls建立信令传递网用于mesh网保护的方法
CN100414910C (zh) * 2005-09-19 2008-08-27 华为技术有限公司 一种业务流保护系统及方法
CN100546284C (zh) * 2006-09-13 2009-09-30 华为技术有限公司 标签交换路径保护方法及其系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1394053A (zh) * 2001-06-27 2003-01-29 华为技术有限公司 多协议标签交换快速保护倒换方法
CN1816035A (zh) * 2005-02-02 2006-08-09 华为技术有限公司 基于数据通信网的主备传输路径实现方法
US20070183317A1 (en) * 2006-02-03 2007-08-09 Jean-Philippe Vasseur Technique for determining whether to reestablish fast rerouted primary tunnels based on backup tunnel path quality feedback
US20070201355A1 (en) * 2006-02-27 2007-08-30 Vasseur Jean P Method and apparatus for determining a preferred backup tunnel to protect point-to-multipoint label switch paths
US20080123524A1 (en) * 2006-11-27 2008-05-29 Jean-Philippe Vasseur Failure protection for P2MP tunnel head-end node

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113905364A (zh) * 2021-10-25 2022-01-07 广州通则康威智能科技有限公司 路由器上行数据溯源方法、装置、计算机设备及存储介质
CN113905364B (zh) * 2021-10-25 2023-07-04 广州通则康威智能科技有限公司 路由器上行数据溯源方法、装置、计算机设备及存储介质

Also Published As

Publication number Publication date
CN101453414B (zh) 2011-08-10
CN101453414A (zh) 2009-06-10

Similar Documents

Publication Publication Date Title
CN101335695B (zh) 点到多点标签交换路径的头节点保护方法、装置和设备
CN101094175B (zh) 一种组播流量保护方法、装置及系统
CN101150587B (zh) 一种多协议标签交换流量工程流量切换的方法、设备及系统
US8218429B2 (en) Method and device for multicast traffic redundancy protection
CN101237409B (zh) Mpls vpn中实现快速重路由的方法及设备
CN104737502B (zh) 用于从次优主要的p2mp切换流量至备用p2mp的方法与系统
US6879594B1 (en) System and method for loop avoidance in multi-protocol label switching
US7792111B2 (en) Point-to-multipoint for multicast and unicast forwarding
EP3340550B1 (fr) Procédé et dispositif de multidiffusion de messages de service
CN104067573B (zh) 一种基于点到点的多播标签分发协议的网络节点
WO2009074043A1 (fr) Procédé et appareil de notification de défaillance
WO2008037198A1 (fr) Procédés de mise en oeuvre de réacheminement rapide multidiffusion et noeud
WO2011035699A1 (fr) Procédé, routeur et système de communication pour convergence de multidiffusion rapide
US20090016341A1 (en) Label assigning method, label replacing method and label switching router
WO2010111956A1 (fr) Procédé et système de convergence de trajet de relais multidiffusion
WO2009074057A1 (fr) Procede de protection de nœud de tete, systeme et dispositif pour le trajet de commutation d'etiquettes point a multipoint
CN101610200B (zh) 组播路由的切换方法及装置
CN101374106A (zh) 一种mpls lsp上转发数据包的方法、网络节点和系统
EP1201061B1 (fr) Systeme et procede d'evitement de boucle dans une commutation par etiquette multiprotocole
CN101771551B (zh) 一种虚拟专有组播业务中流媒体分发的方法、装置及系统
WO2012136062A1 (fr) Procédé de commutation de chemin de diffusion groupée et routeur
CN102136945B (zh) Lsp保护的建立方法和节点
CN101296153B (zh) 一种组播保护方法、系统和设备
CN101075842B (zh) 在共享网段上进行多播数据传输的方法
Le Roux et al. Requirements for point-to-multipoint extensions to the Label Distribution Protocol

Legal Events

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

Ref document number: 08859613

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

Country of ref document: EP

Kind code of ref document: A1