WO2012103748A1 - Procédé de commande de multidiffusion, dispositif de routage et système de multidiffusion - Google Patents

Procédé de commande de multidiffusion, dispositif de routage et système de multidiffusion Download PDF

Info

Publication number
WO2012103748A1
WO2012103748A1 PCT/CN2011/079003 CN2011079003W WO2012103748A1 WO 2012103748 A1 WO2012103748 A1 WO 2012103748A1 CN 2011079003 W CN2011079003 W CN 2011079003W WO 2012103748 A1 WO2012103748 A1 WO 2012103748A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing device
join request
request
upstream neighbor
network segment
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/CN2011/079003
Other languages
English (en)
Chinese (zh)
Inventor
范树学
陈重
赵大赫
徐旭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
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 WO2012103748A1 publication Critical patent/WO2012103748A1/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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing

Definitions

  • the present invention claims to be submitted to the Chinese Patent Office on February 1, 2011, and the application number is 201110034461.7, and the invention name is "a multicast control method, a routing device, and a multicast system.”
  • the priority of the Chinese Patent Application the entire contents of which is incorporated herein by reference.
  • TECHNICAL FIELD The present invention relates to the field of network communication technologies, and in particular, to a multicast control method, a routing device, and a multicast system.
  • IP Internet Protocol
  • the IP multicast protocol includes a protocol between the router and the receiver and a protocol between the router and the router, and the combination is used to construct a multicast forwarding tree from the multicast source to the multicast data receiver.
  • the protocol between the router and the receiver host is usually IGMP (Internet Group Management Protocol).
  • the protocol independent multicast (PIM) protocol is usually used between the router and the router.
  • PIM-SM Protocol Independent Multicast-Sparse Mode
  • the process of establishing a multicast forwarding tree is as shown in FIG. 1 , where 101 to 105 are five routers, 106 is a first receiving device, 107 is a second receiving device, and 108 is a multicast source.
  • the router 104 After receiving the IGMP join request from the first receiving device 106, the router 104 calculates the route to the multicast source 108 according to the unicast, and sends the PIM join message to the upstream router hop by hop, and routes the device 104-> Routing device 102->Routing device 101 establishes a multicast join tree, and then the multicast source along the PIM The reverse direction of the message is forwarded from the routing device 101 -> routing device 102 -> routing device 104 to the first receiving device 106.
  • the direction in which the PIM sends the join message to the upstream is calculated according to the unicast route. Then, if the routing device 105 receives the same as the first receiving device 106 from the second receiving device 107.
  • the IGMP join request calculates the route from the routing device 105 to the multicast source 108 through the routing device 103 based on the unicast route, and thus establishes a multicast forwarding tree from the routing device 101->the routing device 103->the routing device 105. At this time, it can be found that the routing device 102 and the routing device 103 simultaneously forward the same multicast data stream to the shared network segment.
  • Assert competition occurs when duplicate multicast data is generated in the shared network segment, as shown in Figure 2.
  • one of the prior art solutions is to select a router with low overhead to continue to forward the multicast data stream according to the cost of each router to the multicast source.
  • the routers with large overheads stop forwarding multicast data streams, and the routers with low overheads periodically broadcast Assert packets carrying their own overhead information on the shared network segment to avoid re-generation of duplicate multicast data, thus eliminating the shared network segment.
  • Double traffic on. It can be seen in the process that the AsSert competition is performed after repeated multicast data has appeared on the shared network segment, and during the Assert competition, the data received by the user through the shared network segment will have an impact. For example, a large number of mosaics appear in the received video image, and the user experience is poor. At the same time, the Assert message is sent periodically, which also increases the network load.
  • an embodiment of the present invention provides a multicast control method, a routing device, and a multicast system, so as to avoid repeated multicast data on a shared network segment.
  • the embodiment of the invention provides a multicast control method, and the method includes:
  • the second routing device on the shared network segment receives the first joining request periodically sent by the first routing device on the shared network segment, where the first joining request carries the reverse path of the first routing device.
  • the path forwards the RPF upstream neighbor information and the address information of the multicast source.
  • the second routing device determines that the RPF upstream neighbor is not the first routing device according to the RPF upstream neighbor information, and determines that it is the downstream routing device in the shared network segment according to the address information of the multicast source. After receiving the second join request sent by the downstream receiving device, the second join request is not forwarded to the RPF upstream neighbor that is obtained according to the unicast route and receives the second join request.
  • the second routing device When the second routing device receives the first joining request again or receives the leaving request sent by the first routing device, the RPF upstream neighbor that receives the second joining request according to the unicast route The RPF upstream neighbor that is carried in the first join request is sent, and the second join request is sent to the RPF upstream neighbor that is carried in the first join request.
  • a routing device the routing device is located on a shared network segment, and the router includes: a receiving module, configured to receive a first joining request periodically sent by a first routing device on the shared network segment, where the first The RSP carries the reverse path of the first routing device to forward the RPF upstream neighbor information and the address information of the multicast source.
  • a device identification module configured to determine, according to the RPF upstream neighbor information, whether it is an RPF upstream neighbor of the first routing device, and determine, according to the address information of the multicast source, whether it is a downstream in the shared network segment. Routing device
  • a request processing module configured to: when determining that it is a downstream routing device in the shared network segment, and receiving a second joining request sent by the downstream receiving device, temporarily not forwarding the second joining request to the unicast routing Obtaining an RPF upstream neighbor that receives the second join request, and when the receiving module receives the first join request or receives the leave request sent by the first routing device, obtain the self according to the unicast route.
  • the RPF upstream neighbor that receives the second join request is set to be the RPF upstream neighbor carried in the first join request, and sends the second join request to the RPF upstream neighbor carried in the first join request.
  • a multicast system the system includes: at least one first routing device that is located on a shared network segment, and at least one second routing device that is located on the shared network segment, where
  • the first routing device is configured to periodically send a first join request to the second routing device, where the first join request carries a reverse path of the first routing device to forward the RPF upstream neighbor information, and Address information of the multicast source;
  • the second routing device is configured to receive the first join request, and determine that the RPF upstream neighbor is not the first routing device according to the RPF upstream neighbor information, and determine according to the address information of the multicast source.
  • the second routing request sent by the downstream receiving device is received, the second joining request is not forwarded to the receiving second according to the unicast route.
  • the second RPF upstream neighbor is configured to be the RPF upstream neighbor that is carried in the first join request, and sends the second join request to the RPF upstream neighbor that is carried in the first join request.
  • the downstream routing device on the shared network segment in the embodiment of the present invention does not directly forward the join request to the upstream routing device obtained by the unicast path after receiving the join request sent by the downstream receiving device.
  • the upstream routing device that is consistent with the other joining requests that exist in the shared network segment is forwarded, and the access request is forwarded to the same upstream routing device, so as to avoid multiple different multicast data for the same multicast data in the shared network segment. Multicast data transmission path.
  • Figure 1 is a schematic diagram of a process of establishing a multicast forwarding tree in the PIM-SM protocol
  • FIG. 2 is a schematic diagram of a traffic conflict when a duplicate multicast data is generated in a shared network segment;
  • FIG. 3 is a schematic flowchart of a multicast control method according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a topology of a multicast network according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a routing device on a shared network segment according to an embodiment of the present invention.
  • the embodiment of the present invention provides a multicast control method, a routing device, and a multicast system.
  • the embodiment of the invention provides a multicast control method. As shown in FIG. 3, the method may include:
  • the second routing device on the shared network segment receives the first join request periodically forwarded by the first routing device on the shared network segment, where the first join request carries the RPF of the first routing device.
  • RPF Reverse-path forwarding, reverse path forwarding
  • the destination address corresponding to the join request is all the routing devices loaded with PIM-SM in the network segment.
  • join request is sent for an upstream routing device on the shared network segment
  • all other routing devices on the network segment except the specific upstream routing device that load the PIM-SM protocol are also Can receive the join request.
  • the other routing device includes not only other upstream routing devices, but also all downstream routing devices in the shared network segment except the routing device that sends the join request.
  • all the routing devices that have received the above-mentioned join request on the shared network segment in order to confirm whether they need to respond to the join request, first whether they are the above-mentioned shared network.
  • the upstream device or the downstream device in the segment is identified to perform different operations.
  • the join request initiated by a receiver is assumed to be the first join request, and the routing device that sends the first join request is set as the first routing device, and the routing device that receives the first join request on the shared network segment is set.
  • the second routing device determines, according to the RPF upstream neighbor information, that the RPF is not the upstream neighbor of the first routing device, and determines that it is the downstream of the shared network segment according to the address information of the multicast source. After the device is routed, after receiving the second join request sent by the downstream receiving device, the second join request is not forwarded to the RPF upstream neighbor that is obtained according to the unicast route and receives the second join request.
  • the second routing device may obtain the RPF upstream neighbor information of the first routing device carried in the first join request, so as to determine whether the first join message is sent to itself. of.
  • the RPF upstream neighbor information of the first routing device that is carried in the first join request does not match the self-information, the first join message is not sent to the user, and the second routing device may directly The packet carrying the first join request is discarded.
  • the second routing device in the shared network segment has not received the join request initiated by the downstream receiving device, but it can receive the multicast data forwarded to the first routing device in the shared network segment, thereby creating a corresponding entry. . Since the second routing device does not receive the join request initiated by the downstream receiving device, the entry cannot guide the forwarding of the received multicast data, and the corresponding multicast data is terminated on the second routing device.
  • the second routing device When receiving the second join request sent by the downstream receiving device, the second routing device finds that the data active entry exists, and adds the corresponding outgoing interface to forward the multicast data, but the second routing device does not immediately forward the second
  • the request message is added to the RPF upstream neighbor that is obtained by the unicast route and receives the second join request, but waits for a period of time and then forwards.
  • the waiting time may be the period of the second join request.
  • the second routing device receives the first join request or receives the leave request sent by the first routing device, the RPF upstream neighbor that receives the second join request obtained according to the unicast route The RPF upstream neighbor that is carried in the first join request is sent, and the second join request is sent to the RPF upstream neighbor that is carried in the first join request.
  • the second routing device When the second routing device receives the first joining request sent by the first routing device, or the leaving request sent by the first routing device, obtains the RPF upstream neighbor information carried in the corresponding packet, and sets the self-acquisition obtained according to the unicast route. Receiving the RPF upstream neighbor information of the second join request, which is consistent with the RPF upstream neighbor information carried in the first join request or the leave request message sent by the first routing device, and sends the second neighbor to the RPF upstream neighbor. Join the request to avoid the out of the shared network segment There are a number of different multicast data transmission paths for the same multicast data.
  • the downstream routing device on the shared network segment after receiving the join request sent by the downstream receiving device, the downstream routing device on the shared network segment does not immediately forward the join request to the upstream routing device calculated by the unicast path, but keeps the join request.
  • An upstream routing device that is consistent with other join requests that are already in the shared network segment forwards the access request to the same upstream routing device, thereby preventing multiple different multicast data transmissions for the same multicast data in the shared network segment. path.
  • the information is retained to maintain an upstream routing device that is consistent with other joining requests already existing in the shared network segment.
  • the second routing device determines that it is the upstream routing device in the shared network segment according to the address information of the multicast source, and determines whether it is the RPF upstream neighbor carried in the first joining request, if And sending, according to the address information of the multicast source, the first join request to the upper-level network segment of the shared network segment; if not, discarding the first join request.
  • FIG. 4 is a schematic diagram of a topology structure of a multicast network according to an embodiment of the present invention.
  • the routing device 102, the routing device 103, the routing device 104, and the routing device 105 are directly connected to the same shared network segment, and the routing device 102 and the routing device 103 are upstream routing devices on the shared network segment, and the routing device 104 and the routing device 105 are
  • the shared network segment is a downstream routing device, and the routing device 102 and the routing device 103 have a common upstream routing device 101.
  • the routing device 101 directly connects to the multicast source 108.
  • the first receiving device 106 and the second receiving device 107 are respectively configured as routes.
  • the device 104 and the downstream receiving device of the routing device 105 are respectively configured as routes.
  • the first receiving device 106 and the second receiving device 107 are host devices that request to receive the multicast source 108 to send a data packet.
  • the downstream routing device 104 if it receives the join request (Joinl(S, G)) sent by the first receiving device 106, and queries the RPF upstream neighbor as the routing device 102, it sends a join request to the routing device 102. (Joinl (S, G)).
  • all other routing devices on the shared network segment that is, the routing device 103 and the routing device 105, will receive the join request (Joinl(S, G)).
  • the routing device 103 and the routing device 105 respectively identify whether the upstream routing device or the downstream routing device on the shared network segment and whether it is a join request according to the join request (Join(S, G)) (Joinl(S, G) The RPF upstream neighbor specified in ).
  • routing device 105 For routing device 105, assume that it is in the first receiving device When the standby 106 sends a join request (Joinl(S, G)) to the routing device 104, the second receiving device 107 does not send a join request (Join2(S, G)) to the routing device 105 to join the same source group, and therefore, the route The device 105 does not join the source group that the first receiving device 106 sends the join request to establish, and does not include the routing entry, and directly discards the join message.
  • the routing device 105 detects that the multicast data (Joinl(S, G)) request already exists on the shared network segment (S , G), so it does not immediately send (Join2(S, G)) to the upstream neighbor calculated according to the unicast route, but delays the sending (Join2(S, G)) message and shares the shared network segment (Joinl (S, G))
  • the requested multicast data waiting for the next cycle join message sent by the routing device 104, and obtaining the information of the RPF upstream routing device 102 from the corresponding join request (Joinl(S, G)), And correcting the RPF upstream neighbor obtained by the unicast route as the routing device 102, and sending the join request (Join2(S, G)) to the routing device 102.
  • the routing device 102 and the routing device 103 if it is identified as an upstream routing device on the shared network segment according to the join request (Joinl(S, G)), it continues to determine whether it is a join request (Joinl(S, G) The RPF upstream neighbor carried in the ), if yes, continues to send a join request (Joinl(S, G)) to the upper-level network segment of the shared network segment according to the address information of the multicast source; , then discard the join request (Joinl(S, G)).
  • the join request Joinl(S, G)
  • the routing device 102 is the RPF upstream neighbor determined in the join request (Join1 (S, G)), and the routing device 102 continues to the upper network segment of the shared network segment, that is, the routing device 101.
  • Sending a join request (Joinl(S, G)) and the routing device 103 is not joining the RPF upstream neighbor determined in the request (Joinl(S, G)), the routing device 103 will receive the join request (Joinl(S, G) ))throw away.
  • the join request sent by the receiving device may be a (S, G) type join request of the specified multicast source S, or a (*, G) type join request indicating all multicast sources of the specified multicast group G.
  • the join request is a (S, G) join request
  • the downstream device on the shared network segment determines the RPF upstream neighbor by finding the unicast route to the multicast source S; for the (*, G) type join request, it finds The route of the RP (Rendezvous Point) is used to determine the RPF upstream neighbor.
  • the routing device 105 shares the data forwarded by the multicast forwarding tree created by the routing device 104 before sending the PIM join message of the local device, and listens to the shared network segment in a sending period. After the request packet of the routing device of the multicast forwarding tree is added to the existing multicast forwarding tree, you can avoid creating different multicast forwardings on the shared network segment. The situation of double traffic is caused by the tree, and the occurrence of Assert can also be avoided.
  • the embodiment of the present invention further provides a routing device on a shared network segment, as shown in FIG. 5, which is a schematic structural diagram of the routing device.
  • the receiving module 501 is configured to receive a first join request that is periodically sent by the first routing device on the shared network segment, where the first join request carries the reverse path of the first routing device to forward the RPF upstream neighbor Information, and address information of the multicast source;
  • the device identification module 502 is configured to determine, according to the RPF upstream neighbor information, whether it is an RPF upstream neighbor of the first routing device, and determine, according to the address information of the multicast source, whether it is in the shared network segment.
  • Downstream routing device
  • the request processing module 503 is configured to: when determining that the user is the downstream routing device in the shared network segment, and receiving the second joining request sent by the downstream receiving device, temporarily not forwarding the second joining request to the unicast according to the unicast Obtaining, by the route, the RPF upstream neighbor that receives the second join request, when the receiving module receives the first join request again or receives the leave request sent by the first routing device, obtains the self-unicast route according to the unicast route.
  • the RPF upstream neighbor that receives the second join request is set as the RPF upstream neighbor that is carried in the first join request, and sends the second join request to the RPF upstream neighbor that is carried in the first join request.
  • the request processing module 503 is further configured to determine, if it is the upstream routing device in the shared network segment, whether it is the RPF upstream neighbor carried in the first join request, and if yes, And sending, according to the address information of the multicast source, the first join request to the upper-level network segment of the shared network segment; if not, discarding the first join request.
  • the first join request includes: (S, G) join request of the specified multicast source S forwarded by the first routing device, or all multicast sources of the specified multicast group G (*, G ) Join the request.
  • the upstream routing device obtained by the unicast path calculation does not directly forward the join request, but remains in the shared network segment.
  • An existing upstream routing device with the same join request, the access request It is forwarded to the same upstream routing device, so that multiple different multicast data transmission paths for the same multicast data can be avoided in the shared network segment.
  • the embodiment of the present invention further provides a multicast system, where the system includes: at least one first routing device located on a shared network segment, and at least one second routing device located on the shared network segment. , among them,
  • the first routing device is configured to: forward, to the second routing device, a first join request, where the join request carries a reverse path of the first routing device to forward RPF upstream neighbor information, and a multicast source Address information;
  • the second routing device is configured to: receive the first join request, determine, according to the RPF upstream neighbor information, that the RPF upstream neighbor is not the first routing device, and determine, according to the address information of the multicast source, When the second routing request sent by the downstream receiving device is received, the second joining request is not forwarded to the receiving second according to the unicast route. Adding the requested RPF upstream neighbor; when the second routing device receives the first joining request again or receives the leaving request sent by the first routing device, receiving the self-receiving according to the unicast route
  • the second RPF upstream neighbor is configured to be the RPF upstream neighbor that is carried in the first join request, and sends the second join request to the RPF upstream neighbor that is carried in the first join request.
  • system may further include: a multicast source, configured to send multicast data according to the first join request of the first routing device or the second join request of the second routing device.
  • a multicast source configured to send multicast data according to the first join request of the first routing device or the second join request of the second routing device.
  • the second routing device is further configured to: determine, according to the address information of the multicast source, that it is an upstream routing device in the shared network segment, determine whether it is the first joining request.
  • the RPF upstream neighbor if yes, continues to send the first join request to the upper-level network segment of the shared network segment according to the address information of the multicast source; if not, discard the first One join request.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method and the device embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located One place, or it can be distributed to multiple network elements. Can be based on actual needs Some or all of the modules are selected to achieve the objectives of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

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 commande de multidiffusion, un dispositif de routage et un système de multidiffusion. Le procédé comprend les étapes au cours desquelles : un second dispositif de routage dans un segment de réseau de partage reçoit une première demande de participation envoyée périodiquement par un premier dispositif de routage dans le segment de réseau de partage, la demande véhiculant des informations d'un routeur voisin amont au sens RPF du premier dispositif de routage ; lorsqu'il est déterminé que le second dispositif de routage lui-même n'est pas un routeur voisin amont au sens RPF du premier dispositif de routage mais un dispositif de routage en aval dans le segment de réseau de partage, le second dispositif de routage, après avoir reçu une seconde demande de participation envoyée par un dispositif de réception en aval, ne rediffuse temporairement pas la seconde demande de participation vers un routeur voisin amont au sens RPF qui reçoit la seconde demande de participation et est acquis selon un routage en monodiffusion ; et, lorsqu'il reçoit à nouveau la première demande de participation, ou lorsqu'il reçoit une demande de sortie, envoyée par le premier dispositif de routage, le second dispositif de routage paramètre le routeur voisin amont au sens RPF qui reçoit la seconde demande de participation et est acquis par le second dispositif de routage lui-même selon le routage en monodiffusion à destination d'un routeur voisin amont au sens RPF véhiculé dans la première demande de participation, puis envoie la seconde demande de participation au routeur voisin amont au sens RPF.
PCT/CN2011/079003 2011-02-01 2011-08-26 Procédé de commande de multidiffusion, dispositif de routage et système de multidiffusion Ceased WO2012103748A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110034461.7 2011-02-01
CN201110034461.7A CN102624604B (zh) 2011-02-01 2011-02-01 一种组播控制方法、路由设备及组播系统

Publications (1)

Publication Number Publication Date
WO2012103748A1 true WO2012103748A1 (fr) 2012-08-09

Family

ID=46564295

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079003 Ceased WO2012103748A1 (fr) 2011-02-01 2011-08-26 Procédé de commande de multidiffusion, dispositif de routage et système de multidiffusion

Country Status (2)

Country Link
CN (1) CN102624604B (fr)
WO (1) WO2012103748A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103209134B (zh) * 2013-04-22 2017-02-15 杭州华三通信技术有限公司 一种组播转发的方法和设备
CN103354524B (zh) * 2013-07-03 2016-08-10 杭州华三通信技术有限公司 一种基于pim-ssm的实现三层组播按需选路的方法和设备
WO2015196361A1 (fr) * 2014-06-24 2015-12-30 华为技术有限公司 Procédé, appareil et système de multidiffusion pour un réseau défini par logiciel
CN105337746B (zh) * 2015-09-23 2018-11-13 浙江宇视科技有限公司 一种组播数据的传输方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330448A (zh) * 2007-06-21 2008-12-24 华为技术有限公司 一种通告链路状态信息及确定组播转发路径的方法及装置
US20100135294A1 (en) * 2008-12-03 2010-06-03 Cisco Technology, Inc. Any-to any multicasting in a tunnel based virtual private network
CN101800742A (zh) * 2010-01-28 2010-08-11 华为技术有限公司 路由设备上游信息的更新处理方法、路由设备及网络系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330448A (zh) * 2007-06-21 2008-12-24 华为技术有限公司 一种通告链路状态信息及确定组播转发路径的方法及装置
US20100135294A1 (en) * 2008-12-03 2010-06-03 Cisco Technology, Inc. Any-to any multicasting in a tunnel based virtual private network
CN101800742A (zh) * 2010-01-28 2010-08-11 华为技术有限公司 路由设备上游信息的更新处理方法、路由设备及网络系统

Also Published As

Publication number Publication date
CN102624604B (zh) 2015-01-07
CN102624604A (zh) 2012-08-01

Similar Documents

Publication Publication Date Title
CN101656679B (zh) 一种组播快速收敛方法、路由器和通信系统
US7839850B2 (en) Forming equal cost multipath multicast distribution structures
US11509572B2 (en) Optimizing IP multicast delivery with use of local source nodes and the propagation of advertisements therefor
US9077551B2 (en) Selection of multicast router interfaces in an L2 switch connecting end hosts and routers, which is running IGMP and PIM snooping
US8009671B2 (en) Multicast method and multicast routing method
CN100442776C (zh) 在三层交换机上实现组播转发的方法
CN102137000B (zh) 一种建立切换组播分发树的方法、装置及系统
US8953446B1 (en) Load balancing multicast join requests over interior and exterior BGP paths in a MVPN
EP3226491A1 (fr) Support d'attente segment racine chaud pour multidiffusion
CN104509073A (zh) 在软件定义的网络中发现ip多播组成员
CN103348630A (zh) 用于在组播网络中控制选择的方法
CN101394358B (zh) 提高组播转发可靠性的方法和装置
US10225091B2 (en) Method for implementing point-to-multipoint multicast, network node, and system
WO2018014767A1 (fr) Procédé et dispositif de détermination d'informations, et support de stockage
WO2011020346A1 (fr) Procédé et appareil de réacheminement de données de diffusion groupée
US11018886B1 (en) Methods and apparatus for selectively filtering an IP multicast data stream for selected group members of a multicast group
WO2020168982A1 (fr) Procédé permettant d'envoyer et d'obtenir un message d'assertion et nœud de réseau
CN100417141C (zh) 一种组播业务实现方法
WO2012103748A1 (fr) Procédé de commande de multidiffusion, dispositif de routage et système de multidiffusion
WO2015014197A1 (fr) Méthode de sélection de trajet dans un scénario de charge de multidiffusion, et routeur
WO2014169856A1 (fr) Procédé de communication en multidiffusion et commutateur d'agrégation
WO2016131359A1 (fr) Procédé et dispositif de commutation de ligne de multidiffusion pour un réseau en forme d'anneau
WO2013044740A1 (fr) Procédé et dispositif de mise en œuvre de diffusion groupée prenant en charge plus d'un seul vlan
WO2012136062A1 (fr) Procédé de commutation de chemin de diffusion groupée et routeur
CN107276774B (zh) 一种组播报文传输方法以及转发设备

Legal Events

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

Ref document number: 11857474

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

Country of ref document: EP

Kind code of ref document: A1