WO2009146622A1 - Procédé, routeur et système pour mettre en œuvre une multidiffusion - Google Patents

Procédé, routeur et système pour mettre en œuvre une multidiffusion Download PDF

Info

Publication number
WO2009146622A1
WO2009146622A1 PCT/CN2009/071597 CN2009071597W WO2009146622A1 WO 2009146622 A1 WO2009146622 A1 WO 2009146622A1 CN 2009071597 W CN2009071597 W CN 2009071597W WO 2009146622 A1 WO2009146622 A1 WO 2009146622A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
multicast
router
tunnel
downstream router
Prior art date
Application number
PCT/CN2009/071597
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 华为技术有限公司
Publication of WO2009146622A1 publication Critical patent/WO2009146622A1/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
    • 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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, a router, and a system for implementing multicast. Background technique
  • Multicast is a point-to-multipoint efficient data transmission technology in an Internet Protocol (IP) network.
  • IP Internet Protocol
  • PIM-SM Protocol Independent Multicast-Sparse Mode
  • RPF reverse path forwarding
  • the multicast routing table records all the PIM routing entries and sends them to the forwarding table.
  • the forwarding entries directly direct multicast packet forwarding.
  • the multicast routing table records all PIM routing entries and sends them to the forwarding table.
  • the forwarding entry directly directs multicast packet forwarding.
  • ( S, G ) is only applicable to multicast messages whose source address is S and whose group address is G.
  • a multicast packet whose source address is S and whose group address is G is represented as (S, G) packets.
  • the (S, G) entry guides the packet forwarding.
  • the (S, G) entry is created according to the (*, G) entry, and the (S, G) entry is used to guide the packet forwarding.
  • the outbound interface of a PIM routing entry can only be a physical interface.
  • the common IP routing and forwarding mode lacks a fast protection mechanism.
  • the convergence of multicast traffic will be slow.
  • the purpose of the embodiments of the present invention is to provide a method, a router, and a system for implementing multicast, which improve the service quality of a multicast service.
  • the embodiment of the present invention provides a method for implementing multicast.
  • a traffic engineering TE tunnel exists between a downstream router and an upstream router, and the method includes:
  • the embodiment of the present invention further provides an upstream router that implements a multicast, where the upstream router and the downstream router have a traffic engineering TE tunnel, and the upstream router includes:
  • a receiving unit configured to receive a Join message sent by the downstream router to the multicast group G, where the Join message includes a loopback address of the loopback interface of the downstream router;
  • a routing unit configured to add a physical interface that receives the Join message in the receiving unit to an outbound interface list of the multicast group G;
  • a searching unit configured to search for a matching TE tunnel according to the loop-back address in the Join message received by the receiving unit, and the physical interface; and replace the physics in the outbound interface list in the routing unit with the matched TE tunnel interface Interface, get a list of new outgoing interfaces;
  • a sending unit configured to send, according to the new outbound interface list in the routing unit, the multicast packet received by the receiving unit to the downstream router by using a matching TE tunnel.
  • the embodiment of the present invention further provides a downstream router that implements a multicast, where the downstream router and the upstream router have a traffic engineering TE tunnel, and the downstream router includes:
  • a message unit configured to generate a Join message for the multicast group G, where the Join message includes the downstream message Loopback address of the loopback of the router;
  • a sending unit configured to send a Join message generated by the message unit to the upstream router
  • a receiving unit configured to receive a multicast message sent by the upstream router by using a matching TE tunnel, where the matched TE tunnel is used by the
  • the upstream router adds the physical interface that receives the Join message to the outbound interface list of the multicast group G, and searches for the loop-back address and the physical interface.
  • the multicast packet is used by the upstream router.
  • the matching TE tunnel interface replaces the physical interface in the outbound interface list, and obtains a new outbound interface list, and sends the new outbound interface list according to the new outgoing interface list.
  • the embodiment of the present invention further provides a system for implementing multicast, including: an upstream router and a downstream router, where the downstream router and the upstream router have a traffic engineering TE tunnel, where
  • the downstream router is configured to send a Join message to the upstream router for the multicast group G, where the Join message includes a loopback address of the loopback interface of the downstream router;
  • the upstream router is configured to receive the Join message through a physical interface, add the physical interface to an outbound interface list of the multicast group G, and search for a matching TE according to the loop-back address and the physical interface.
  • the tunnel is replaced with a matching TE tunnel interface to obtain a new outbound interface list, and according to the new outgoing interface list, the multicast packet is sent to the Downstream router.
  • the TE tunnel is used to find the matching TE tunnel, and the TE tunnel interface is used to replace the physical outbound interface in the outbound interface list of the upstream router, so that the multicast forwarding can utilize the TE tunnel for fault protection, resource reservation, and tunnel encapsulation. , can improve the quality of service of the multicast service.
  • FIG. 1 is a schematic flowchart of implementing a multicast method according to Embodiment 1 of the present invention
  • FIG. 2 is a schematic structural diagram of implementing a multicast system according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic structural diagram of an upstream router implementing multicast in Embodiment 3 of the present invention
  • FIG. 4 is a schematic structural diagram of a downstream router implementing multicast in Embodiment 4 of the present invention.
  • the first embodiment is a method for implementing multicast.
  • a traffic engineering TE (Traffic Engineering) tunnel is used between the downstream router and the upstream router.
  • the TE tunnel is a Constraint-Based Label Switch Path.
  • the unidirectional tunnel encapsulation technology of the CR-LSP, the Multi-Protocol Label Switching (MPLS) TE in the process of establishing an LSP tunnel, can reserve resources to ensure the quality of service; MPLS TE also implements a mechanism for path backup and fast reroute, which can be switched in time when there is a problem with the link.
  • MPLS Multi-Protocol Label Switching
  • the method can include:
  • the downstream router sends a join message to the upstream router for the multicast group G.
  • the join message includes the loopback address of the loopback port of the downstream router.
  • the Join message can also include:
  • each of the multicast group addresses can be followed by:
  • n coded requirements The source address of the incoming Join Source Address; and the source address of the n coded pruning required Pruned Source Address (where n is a natural number).
  • the loop-back address of the downstream router may be included in the Join message in the following manner:
  • a multicast group Multicast Grou field is appended to the Join message; the Multicast Group field is followed by an encoded source address Joined Source Address and a source address that is encoded to require pruning.
  • the Runed Source Address is included in the Joined Source Address.
  • the loop-back address of the downstream router; the Pruned Source Address contains the identifier of the multicast group field.
  • the identifier of the multicast group field is used to indicate that the Join message contains the loop-back of the downstream router. The address, you can use the value that has not been defined in the current multicast protocol, for example, set all the bytes of the Pruned Source Address to zero.
  • the Multicast Grou field and the subsequent Joined Source Address have an address family Address family different from the Upstream Neighbor Address in the Join message of this embodiment.
  • the loop-back address can be obtained directly from the Joined Source Address of the Multicast Grou field; for the upstream router that does not support the multicast method in this embodiment, according to Currently, the multicast protocol RFC2362 stipulates that when the corresponding fields of the Address family and the Upstream neighbor address of a Multicast Group or a Joined Source Address are different, the upstream router ignores the Multicast Group field, so the method for implementing multicast in this embodiment is used. It can be compatible with current routers and achieve good interoperability with current technologies.
  • the upstream router receives the Join message through the physical interface.
  • the upstream router adds the physical interface that receives the Join message to the outbound interface list of the multicast group G entry.
  • the matching principle is that if the destination address and the outbound interface of a TE tunnel are the same as the loop-back address of the Join message and the physical interface of the Join message, the match is considered successful. :
  • Condition 2 Find out whether there is a TE tunnel with the same outbound interface as the physical interface.
  • the TE tunnels that meet the conditions 1 and 2 are matched TE tunnels.
  • the method may further include:
  • the upstream router receives the multicast packet.
  • the upstream router sends the multicast packet to the downstream router through the matched TE tunnel according to the new outbound interface list.
  • the method may further include establishing a mapping relationship between the label and the port (the first interface),
  • the specific implementation process can be:
  • the downstream router searches for the first interface, where the first interface is the outbound interface of the matching TE tunnel source address in the unicast routing table; the unicast routing table is on the downstream router.
  • the downstream router establishes a mapping relationship between the label of the multicast packet and the first interface.
  • the method may further include:
  • the downstream router determines the type of the received multicast packet.
  • the downstream router performs the reverse path forwarding check of the IP packet.
  • the downstream router checks whether the second interface is the same as the third interface. If the packets are inconsistent, the multicast packets are discarded.
  • the second interface is the interface that receives the multicast packets from the downstream router.
  • the third interface is the unicast routing table of the downstream router and multicast. The outbound interface corresponding to the source address of the source;
  • the downstream router When the multicast packet is an MPLS packet, the downstream router performs the reverse path forwarding check of the MPLS packet. Since the matched TE tunnel includes the primary tunnel and the protection tunnel, the multicast packet may reach through the primary tunnel or the protection tunnel. On the downstream router, the downstream router may receive multiple multicast packets. The path of the tunnel forwarding path and the reverse unicast route are inconsistent. The reverse path forwarding check fails. The mapping between the label of the multicast packet and the first interface is established. The reverse path forwarding check can also be performed when the multicast packet is an MPLS packet.
  • the specific check method is as follows:
  • the MPLS packet is sent from the primary tunnel or the protection tunnel.
  • the MPLS packet contains the same label when it reaches the destination address. Therefore, the multicast packet is a multi-protocol label distribution protocol.
  • the downstream router searches for the mapping according to the label of the multicast packet to obtain the corresponding first interface.
  • the downstream router checks whether the first interface is the same as the fourth interface. If the packets are consistent, the multicast packet is forwarded through the reverse path. If the packets are inconsistent, the multicast packets are discarded.
  • the fourth interface is the outbound interface corresponding to the source address of the multicast packet in the unicast routing table of the downstream router.
  • ⁇ Multicast in the above manner When a multicast packet is an MPLS packet, there is a premise that the router in the TE tunnel cannot use the penultimate hop popup when performing MPLS label distribution.
  • the so-called penultimate hop pop-up method is, according to the current MPLS transport protocol, when the MPLS packet is transmitted to the penultimate router, in order to reduce the work of the last router, the second to last The router removes the MPLS label of the MPLS packet. If the second-to-last hop is used, the TE tunnel also includes other protection paths. If the multicast packets received by the downstream router from the interface other than the fourth interface have been removed from the MPLS label, the mapping relationship cannot be searched. Therefore, the reverse path forwarding check cannot be performed. Therefore, in this embodiment, when the multicast packet is an MPLS packet, the penultimate hop popup mode is not used.
  • the technical solution of the embodiment is used to enable the multicast packet to be forwarded through the TE tunnel. Since the encapsulation technology is applied to the TE tunnel, the intermediate node of the tunnel does not need to reserve the multicast forwarding table, and the intermediate router may not even support the multicast protocol. Packet forwarding can be implemented across multicast domains.
  • the multicast packet is an MPLS packet
  • the multicast packet is encapsulated in the MPLS packet, and the intermediate router cannot identify the content, thus ensuring the security of the multicast content.
  • the TE tunnel has a large number of fault protection mechanisms, such as fast reroute, LSP (label switch path), and tunnel protection group.
  • LSP label switch path
  • tunnel protection group When the primary path fails, it can quickly detect and switch to the alternate path. This process is transparent to the outside world, so it can ensure that the multicast route does not need to re-converge when the path fails, and the multicast traffic is not interrupted.
  • the bandwidth guarantee and differential services of the TE tunnel provide a good guarantee for the quality of the multicast service.
  • this embodiment is a main body of a method for implementing an embodiment, and a system for implementing multicast.
  • the system may include: an upstream router 201 and a downstream router 202, and between a downstream router and an upstream router. Traffic engineering TE tunnel, where
  • the downstream router 202 is configured to send a Join message to the upstream router for the multicast group G, where the Join message includes a loopback address of the loopback port of the downstream router;
  • the upstream router 201 is configured to receive a Join message through the physical interface; add the physical interface to the outbound interface list of the multicast group G; and find a matching TE tunnel according to the loop-back address and the physical interface that receives the Join message; The TE tunnel interface replaces the physical interface in the outbound interface list to obtain a new outbound interface list.
  • the multicast tunnel is sent to the downstream router through the matching TE tunnel.
  • the downstream router 202 can include:
  • the message unit 202-1 is configured to generate a Join message for the multicast group G.
  • the sending unit 202-2 is configured to send a Join message generated by the message unit to the upstream router 201.
  • the upstream router 201 can include:
  • the receiving unit 201-1 is configured to receive a Join message and/or a multicast message.
  • the routing unit 201-2 is configured to add the physical interface that receives the Join message in the receiving unit 201-1 to the outbound interface list of the multicast group G.
  • the searching unit 201-3 is configured to search for a matching TE tunnel according to the loop-back address and the physical interface in the Join message received by the receiving unit 201-1; and replace the outbound interface list in the routing unit 201-2 with the matched TE tunnel port.
  • the physical interface in the middle get a list of new outgoing interfaces;
  • the sending unit 201-4 is configured to send the multicast message received by the receiving unit 201-1 to the downstream router 202 through the matched TE tunnel according to the new outbound interface list in the routing unit 201-2.
  • downstream router 202 may further include:
  • the mapping unit 202-3 is configured to find the outbound interface of the matched TE tunnel source address in the unicast routing table, and obtain the first interface; the unicast routing table is on the downstream router; and establish the label of the multicast packet and the first The mapping relationship of the interface.
  • downstream router 202 may further include:
  • the receiving unit 202-4 is configured to receive a multicast packet from the upstream router 201.
  • the determining unit 202-5 is configured to determine the type of the multicast packet received by the receiving unit 202-4.
  • the checking unit 202-6 is configured to: when the determining unit 202-5 determines that the multicast packet is an Internet Protocol IP packet, Check whether the second interface is the same as the third interface. If the packets are the same, the multicast packets are forwarded through the reverse path. If the packets are inconsistent, the multicast packets are discarded.
  • the second interface is the downstream router.
  • the third interface is the outbound interface corresponding to the multicast packet in the unicast routing table of the downstream router; this case is not shown in FIG. 2;
  • the mapping relationship between the mapping unit 202-3 of the multicast packet is obtained, and the corresponding first interface is obtained; Whether the interface is the same as the fourth interface. If the interface is consistent, the multicast packets are forwarded through the reverse path. If the packets are inconsistent, the multicast packets are discarded.
  • the fourth interface is the unicast routing table and group of the downstream router. The outgoing interface corresponding to the source address of the broadcast source.
  • the third embodiment is an upstream router that implements multicast in the second embodiment. A traffic engineering TE tunnel exists between the upstream router and the downstream router. Referring to FIG. 3, the upstream router may include:
  • the receiving unit 301 is configured to receive a Join message sent by the downstream router for the multicast group G, where the Join message includes a loopback address of the loopback port of the downstream router.
  • the routing unit 302 is configured to add the physical interface that receives the Join message in the receiving unit 301 to the outbound interface list of the multicast group G.
  • the searching unit 303 is configured to search for a matching TE tunnel according to the loop-back address and the physical interface in the Join message received by the receiving unit 301, and replace the physical interface in the outbound interface list in the routing unit 302 with the matched TE tunnel interface, New outgoing interface list;
  • the sending unit 304 is configured to send the multicast packet received by the receiving unit 301 to the downstream router through the matched TE tunnel according to the new outbound interface list in the routing unit 302.
  • the fourth embodiment is a downstream router that implements multicast in the second embodiment.
  • a traffic engineering TE tunnel exists between the downstream router and the upstream router.
  • the downstream router may include:
  • the message unit 401 is configured to generate a Join message for the multicast group G, where the Join message includes a loopback address of the loopback port of the downstream router.
  • the sending unit 402 is configured to send a Join message generated by the message unit 401 to the upstream router.
  • the receiving unit 403 is configured to receive the multicast message sent by the upstream router through the matched TE tunnel, and the matched TE tunnel receives the Join message by the upstream router.
  • the physical interface is added to the outbound interface list of the multicast group G, and is obtained based on the loop-back address and the physical interface.
  • the multicast router replaces the physical interface in the interface list with the matching TE tunnel interface.
  • the interface list is sent through the matching TE tunnel according to the new outgoing interface list.
  • downstream router may further include:
  • the mapping unit 404 is configured to search for an outbound interface of the matched TE tunnel source address in the unicast routing table, to obtain a first interface, where the unicast routing table is on the downstream router, and establish the multicast packet A mapping relationship between the label of the text and the first interface.
  • downstream router may further include:
  • the determining unit 405 is configured to determine a type of the multicast packet received by the receiving unit 403.
  • the checking unit 406 is configured to: when the determining unit 403 determines that the multicast packet is an Internet Protocol IP packet, check whether the second interface is consistent with the third interface, and if the consistency is the same, the multicast packet is forwarded through the reverse path. If the packets are inconsistent, the multicast packet is discarded; wherein the second interface is an interface that receives the multicast packet in the downstream router, and the third interface is a unicast of the downstream router. An outbound interface corresponding to the multicast packet in the routing table;
  • the mapping relationship in the mapping unit is searched according to the label of the multicast packet to obtain a corresponding first interface; Whether the first interface is consistent with the fourth interface. If the first interface is the same, the multicast packet is forwarded through the reverse path. If the packet is inconsistent, the multicast packet is discarded. An outbound interface corresponding to the source address of the multicast packet in the unicast routing table of the downstream router.

Landscapes

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

Abstract

L’invention porte sur un procédé, un routeur, et un système pour mettre en œuvre une multidiffusion, le procédé comprenant : la réception du message de ralliement à travers une interface physique, le message de ralliement comprenant l’adresse de bouclage d’un routeur en aval; le ralliement de l’interface physique dans la liste d’interfaces de sortie du groupe de multidiffusion G, et la recherche du tunnel TE mis en correspondance sur la base de l’adresse de bouclage et de l’interface physique; le remplacement de l’interface physique dans la liste d’interfaces de sortie par le port de tunnel TE mis en correspondance pour obtenir une nouvelle liste d’interfaces de sortie; selon la nouvelle liste d’interfaces de sortie, l’envoi du message de multidiffusion au routeur en aval à travers le tunnel TE mis en correspondance.
PCT/CN2009/071597 2008-06-03 2009-04-30 Procédé, routeur et système pour mettre en œuvre une multidiffusion WO2009146622A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA200810085933XA CN101599841A (zh) 2008-06-03 2008-06-03 实现组播的方法、路由器及系统
CN200810085933.X 2008-06-03

Publications (1)

Publication Number Publication Date
WO2009146622A1 true WO2009146622A1 (fr) 2009-12-10

Family

ID=41397727

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071597 WO2009146622A1 (fr) 2008-06-03 2009-04-30 Procédé, routeur et système pour mettre en œuvre une multidiffusion

Country Status (2)

Country Link
CN (1) CN101599841A (fr)
WO (1) WO2009146622A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101945117A (zh) * 2010-09-28 2011-01-12 杭州华三通信技术有限公司 防止源地址欺骗攻击的方法及设备
US20160345054A1 (en) * 2015-05-22 2016-11-24 Telefonaktiebolaget L M Ericsson (Publ) Quicker iptv channel with static group on igmp loopback interface

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102739521B (zh) * 2012-06-04 2016-03-02 杭州华三通信技术有限公司 一种组播业务实现方法及其设备
CN104283796B (zh) * 2014-10-23 2018-02-09 新华三技术有限公司 一种组播分发树建立方法和装置
CN108337158B (zh) * 2018-01-23 2020-12-04 新华三技术有限公司 单播报文转发方法和装置
CN111181855B (zh) * 2018-11-13 2021-06-04 北京华为数字技术有限公司 一种组播的方法及路由设备
CN111385213B (zh) * 2018-12-29 2021-10-22 华为技术有限公司 一种组播转发表项生成方法及装置
CN111917622B (zh) * 2019-09-23 2021-08-03 华为技术有限公司 一种反向路径转发rpf检查方法及装置
CN112737954B (zh) * 2019-10-14 2022-09-23 华为技术有限公司 报文处理方法、装置、系统、设备及存储介质
EP4030698A4 (fr) 2019-10-14 2022-11-09 Huawei Technologies Co., Ltd. Procédé, dispositif, système et appareil de traitement de paquets, et support de stockage
CN115442288B (zh) * 2022-08-19 2023-06-27 中国信息通信研究院 一种SRv6网络数据包检查方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848807A (zh) * 2005-11-29 2006-10-18 华为技术有限公司 一种组播业务实现方法
CN1852249A (zh) * 2005-12-01 2006-10-25 华为技术有限公司 一种实现组播业务的方法
CN101112058A (zh) * 2005-03-31 2008-01-23 松下电器产业株式会社 组播数据的隧道

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101112058A (zh) * 2005-03-31 2008-01-23 松下电器产业株式会社 组播数据的隧道
CN1848807A (zh) * 2005-11-29 2006-10-18 华为技术有限公司 一种组播业务实现方法
CN1852249A (zh) * 2005-12-01 2006-10-25 华为技术有限公司 一种实现组播业务的方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101945117A (zh) * 2010-09-28 2011-01-12 杭州华三通信技术有限公司 防止源地址欺骗攻击的方法及设备
US20160345054A1 (en) * 2015-05-22 2016-11-24 Telefonaktiebolaget L M Ericsson (Publ) Quicker iptv channel with static group on igmp loopback interface
US10291957B2 (en) * 2015-05-22 2019-05-14 Telefonaktiebolaget Lm Ericsson (Publ) Quicker IPTV channel with static group on IGMP loopback interface

Also Published As

Publication number Publication date
CN101599841A (zh) 2009-12-09

Similar Documents

Publication Publication Date Title
US10833989B2 (en) Methods, apparatus, and articles of manufacture to provide a multicast virtual private network (MVPN)
WO2009146622A1 (fr) Procédé, routeur et système pour mettre en œuvre une multidiffusion
US9860163B2 (en) MPLS traffic engineering for point-to-multipoint label switched paths
US9509590B2 (en) Method and apparatus for providing resiliency in multicast networks
US20070127477A1 (en) Method for implementing multicast based on multi-service transport platform
US10051022B2 (en) Hot root standby support for multicast
US20070025276A1 (en) Congruent forwarding paths for unicast and multicast traffic
WO2012003743A1 (fr) Procédé et appareil d'acheminement de trafic de diffusion groupée
WO2013139159A1 (fr) Procédé de transmission de paquet dans un réseau et dispositif côté fournisseur
EP3965368B1 (fr) Selection de mode de replication pour multidiffusion dans un evpn
WO2011103759A1 (fr) Procédé pour l'établissement d'un chemin à commutation d'étiquettes bidirectionnel associé, et système pour sa mise en œuvre
WO2012075832A1 (fr) Procédé de transmission de message de données multidiffusion et dispositif périphérique fournisseur
WO2012103748A1 (fr) Procédé de commande de multidiffusion, dispositif de routage et système de multidiffusion
Pointurier Link failure recovery for mpls networks with multicasting
US20240048483A1 (en) PCE for BIER-TE Ingress Protection
Rani et al. PERFORMANCE AND EVOLUTION OF MPLS L3 VPN BASED ON ISP ROUTERS & MULTICASTING VPN SUPPORT WITH PROTOCOL INDEPENDENT MULTICASTING (PIM-SPARSE DENSE MODE)
Qin et al. Research on RP Point Configuration Optimizing of the Communication Private Network

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

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

Country of ref document: EP

Kind code of ref document: A1