WO2011035699A1 - 一种组播快速收敛方法、路由器和通信*** - Google Patents
一种组播快速收敛方法、路由器和通信*** Download PDFInfo
- Publication number
- WO2011035699A1 WO2011035699A1 PCT/CN2010/077022 CN2010077022W WO2011035699A1 WO 2011035699 A1 WO2011035699 A1 WO 2011035699A1 CN 2010077022 W CN2010077022 W CN 2010077022W WO 2011035699 A1 WO2011035699 A1 WO 2011035699A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- primary
- multicast
- path
- standby
- next hop
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
- H04L12/1877—Measures taken prior to transmission
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a multicast fast convergence method, a router, and a communication system. Background technique
- IP Internet Protocol
- Multicast group IP multicast technology
- IP multicast technology can be used to implement some network services, such as live broadcast, IPTV, distance education, and real-time video conferencing.
- IP Internet Protocol
- IP multicast technology can be used to implement some network services, such as live broadcast, IPTV, distance education, and real-time video conferencing.
- packet loss will seriously affect these services.
- the impact therefore, in order to ensure the normal transmission of business data, in the event of a network failure, the path needs to be quickly converge.
- PIM Protocol Independent Multicast
- a backup link is pre-assigned to the active link, and PIM join is configured.
- the upstream interface of the primary link and the upstream interface of the standby link are respectively configured.
- the upstream interface of the primary link and the upstream interface of the standby link send PIM Joins to their respective upper hop nodes to establish
- the multicast tree to the multicast source finally forms the primary path to the multicast source (that is, the primary multicast tree) and the alternate path (that is, the standby multicast tree).
- the multicast source passes through the primary path and the alternate path simultaneously.
- a multicast stream is sent. Normally, each node receives only the multicast stream on the active path and discards the multicast stream on the alternate path.
- the forwarding entry When the primary path fails, the forwarding entry is switched to the standby.
- the path receives the multicast stream on the alternate path and forwards the multicast stream.
- the convergence performance of the PIM protocol is far less than that of unicast convergence. This is because unicast convergence only needs to spread a fault message, and then each network node completes the route calculation locally. You can converge all routes to the new path, but multicast does not. Of course, unicast requires each route to be forwarded, so performance bottlenecks are mainly calculated and delivered.
- the PIM protocol is equivalent to a tunneling protocol. Each multicast route is equivalent to a tunnel. Therefore, after the local route is processed and forwarded, the upstream node needs to be notified by hop-by-hop route.
- the upstream node also needs to perform calculation.
- the process of forwarding and forwarding is performed at a time. Therefore, the transmission volume of the PIM Join message is an important overhead, and since this part of the overhead occurs between the network nodes, it is much larger than the overhead of forwarding the device itself.
- the inventors of the present invention have found that the solution provided by the prior art is required to statically configure the primary and secondary inbound interfaces and the next hop of the multicast on the device, so that the network cannot be adapted to the network.
- the dynamic topology changes, and the scenario of multicast stream protection is greatly limited. Summary of the invention
- the embodiments of the present invention provide a multicast fast convergence method, a router, and a communication system, which can adapt to dynamic topology changes of the network.
- a method for fast convergence of multicast including:
- the primary outbound interface, the standby outbound interface, the primary next hop, and the alternate next hop of each unicast route that arrives at the multicast source are calculated.
- the master outbound interface is configured as the primary inbound interface of the multicast to send PIM Join messages to the primary next hop to establish the primary path.
- the standby outbound interface is configured as a standby inbound interface to send a PIM Join message to the backup next hop to establish an alternate path.
- the multicast stream delivered by the multicast source is received through the alternate path and the multicast stream is forwarded.
- a router that includes:
- a calculation unit configured to calculate a primary outbound interface, a standby outbound interface, a primary next hop, and an alternate next hop for each unicast route that arrives at the multicast source;
- the primary sending unit is configured to send the PIM Join message to the primary next hop to establish the primary path by using the primary outbound interface calculated by the computing unit as the primary inbound interface of the multicast;
- the standby sending unit is configured to send the PIM Join message to the standby next hop as the standby inbound interface calculated by the computing unit to establish an alternate path.
- the first processing unit is configured to: when the primary path initiated by the primary sending unit fails, receive the multicast stream delivered by the multicast source and forward the multicast stream by using the standby path initiated by the standby sending unit.
- a communication system including any of the routers provided by the embodiments of the present invention, for example, includes:
- the first router is configured to calculate a primary outbound interface, a standby outbound interface, a primary next hop, and an alternate next hop for each unicast route that arrives at the multicast source.
- the calculated primary outgoing interface is used as the multicast.
- the primary inbound interface sends a protocol-independent multicast to the PIM Join message to the primary next hop to establish the primary path.
- the calculated outbound interface is used as the standby inbound interface of the multicast to send PIM Join messages to the local interface.
- the standby next hop is set up to establish an alternate path; when the primary path fails, the multicast stream delivered by the multicast source is received through the alternate path and the multicast stream is forwarded;
- the second router as the primary next hop, is configured to receive the PIM Join message sent by the first router, send the PIM Join message to the fourth router to establish the primary path, and receive the multicast stream sent by the fourth router. Afterwards, forwarding the multicast stream to the first router;
- the third router as the standby next hop, is configured to receive the PIM Join message sent by the first router, send the PIM Join message to the fourth router to establish an alternate path, and after receiving the multicast stream sent by the fourth router, Forwarding the multicast stream to the first router;
- the fourth router is configured to receive the PIM Join message sent by the second router, and receive the PIM Join message sent by the third router, and send the multicast stream to the first path after the primary path and the backup path are established.
- the second router sends the multicast stream to the third router through the alternate path.
- the primary and secondary outbound interfaces and the next hop of each unicast route to the multicast source are calculated, and then the primary and secondary hops are respectively constructed according to the calculated primary and secondary outgoing interfaces and the next hop, and the primary path is used.
- the multicast stream delivered by the multicast source is received through the alternate path and the multicast stream is forwarded.
- the node in the solution can dynamically calculate the primary and secondary outgoing interfaces and the next hop according to the routing result.
- the PIM Join message is sent to construct the primary and backup paths. Therefore, the primary and secondary BGP interfaces of the PIM and the next hop are not required to be statically configured on the device. This can be adapted to the dynamic topology changes of the network. Multicast stream protection scenario.
- DRAWINGS 1 is a flowchart of a method of a method according to Embodiment 1 of the present invention.
- Embodiment 2 is a schematic diagram of a network topology provided by Embodiment 2 of the present invention.
- Embodiment 3 is a schematic diagram of a network topology scenario provided by Embodiment 2 of the present invention.
- FIG. 4 is a schematic diagram of a network topology scenario according to Embodiment 3 of the present invention.
- FIG. 5 is a schematic structural diagram of a router according to an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
- the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
- Embodiment 1 provides a multicast fast convergence method, a router and a communication system. The following is a detailed description. Embodiment 1
- a sink node refers to a node that directly connects to a receiver
- a source node refers to a node that directly connects to a multicast source, and, in addition, a unicast route
- the outgoing interface is an ingress interface for multicast applications.
- a multicast fast convergence method includes: calculating a primary outbound interface, a standby outbound interface, a primary next hop, and an alternate next hop for each unicast route that arrives at the multicast source;
- the interface serves as the primary inbound interface of the multicast to send PIM Join messages to the primary next hop to establish the primary path.
- the calculated outbound interface sends the PIM Join message to the alternate next hop.
- the PIM Join message described in the embodiment of the present invention refers to a PIM Join message, which is hereinafter referred to as a PIM Join message.
- the specific process can be as follows:
- the primary outbound interface, the standby outbound interface, the primary next hop, and the alternate next hop of each unicast route that arrives at the multicast source can be calculated by starting unicast IP Fast Reroute (FRR, Fast Reroute).
- FRR Fast Reroute
- the primary outbound interface, the standby outbound interface, the primary next hop, and the alternate next hop of each unicast route that arrives at the multicast source can be calculated by starting unicast IP Fast Reroute (FRR, Fast Reroute).
- FRR Fast Reroute
- IP FRR refers to the effect of uninterrupted service on the router adjacent to the faulty link or the faulty node by directly changing the next hop of the forwarding entry to bypass the faulty node when the fault occurs, and Requiring forwarding traffic does not result in loop related techniques. This method does not require convergence at the control level, and only depends on the fault-aware time and the time of switching the next hop. Therefore, the purpose of the fast re-routing can be achieved.
- the present invention is mainly applied to the unicast field.
- the PIM bidirectional join (Join) application is applied to the multicast to adapt to the dynamic topology changes of the network. In this regard, it will be described in detail in the following embodiments.
- the primary outbound interface sends a PIM Join message to the primary next hop to trigger the protocol-independent multicast-sparse mode (PIM-SM, Protocol Independent).
- PIM-SM protocol-independent multicast-sparse mode
- Multicast-Sparse Mode constructs a main shared tree (RPT, Rendezvous Point Tree), where the main shared tree includes an active path; or
- PIM-SSM or Protocol Independent Multicast-Source-Specific Multicast is configured to send PIM-SSM packets to the primary next-hop.
- a shortest path tree (SPT), where the main shortest path tree includes an active path.
- the PIM-SM is configured to send the PIM-SM to the standby next-hop by using the calculated outbound interface.
- the shortest path tree is generated by the PIM-SM or PIM-SSM.
- the shortest path tree includes the alternate path.
- step 102 and step 103 may be in no particular order.
- the multicast stream delivered by the multicast source is received through the standby path. And forward the multicast stream.
- the multicast stream delivered by the multicast source is received through the alternate path, and then the multicast stream is forwarded according to the forwarding entry and the outbound interface.
- the primary path when the primary path is used normally, the multicast stream delivered by the multicast source is received by the primary path and the multicast stream is forwarded, and the multicast stream on the alternate path is discarded. That is, when there is no failure in the network, generally only the multicast stream from the primary path is received, and the multicast stream from the alternate path is discarded, only when the network fails, and the failure is when the primary path fails.
- the primary path is switched to the alternate path, and the multicast stream is received from the alternate path and the multicast stream is forwarded.
- a fast fault detection such as bidirectional forwarding detection (BFD), can be used to quickly detect whether a fault occurs. If the primary path fails, step 104 is performed.
- BFD bidirectional forwarding detection
- the IP FRR recalculates the primary outbound interface, the primary next hop, the standby outbound interface, and the alternate next hop.
- the PIM routing result will also change dynamically.
- the sink node will send PIM Join to establish a new one based on the newly calculated primary outbound interface, primary next hop, alternate outbound interface, and alternate next hop.
- the primary path and the alternate path enable flexible adaptation to different situations of network deployment.
- the primary and secondary outbound interfaces and the next hop of each unicast route that arrives at the multicast source are calculated, that is, the primary outbound interface, the primary next hop, the standby outbound interface, and the standby hop are used.
- One hop the following is abbreviated as the primary and secondary outgoing interfaces and the next hop, and then the primary and secondary paths to the multicast source are constructed according to the calculated primary and secondary outgoing interfaces and the next hop respectively (ie, the primary path and the alternate path, the following are all
- the primary path receives the multicast stream delivered by the multicast source and forwards the multicast stream.
- the node in the solution can dynamically calculate the primary and secondary outgoing interfaces and The next hop (that is, according to the result of the routing) sends a PIM Join message to construct the primary and backup paths. Therefore, the primary and secondary hops of the multicast that send PIM Join messages and the next hop cannot be statically configured on the device.
- the dynamic topology change greatly expands the scenario of multicast stream protection.
- the PIM bidirectional join technology is used in the embodiment of the present invention, the one-way comparison with the prior art is In the case of Join, it is advantageous to reduce the transmission overhead between nodes.
- the unicast FRR can calculate the primary outbound interface, the primary next hop, the standby outbound interface, and the alternate next hop for each unicast route, according to the calculated primary hop. Use the outbound interface, the primary next hop, the standby outbound interface, and the alternate next hop to send two-way links with unicast
- PIM join establishes the primary and backup paths to the multicast source, and directs the dual multicast stream.
- the nodes in the multicast network only receive the multicast stream of the primary path.
- the multicast stream on the network is discarded.
- the switch directly switches to the alternate path, receives the multicast stream on the alternate path, and forwards the multicast stream.
- the IP FRR recalculates the primary and secondary outgoing interfaces and the next hop, and then sends PIM Joins based on the recalculated primary and secondary outgoing interfaces and the next hop.
- the new primary alternate path if the network topology changes, after the unicast route converges, the IP FRR recalculates the primary and secondary outgoing interfaces and the next hop, and then sends PIM Joins based on the recalculated primary and secondary outgoing interfaces and the next hop. The new primary alternate path.
- node C is a sink node
- node A is a source node
- node B and node C are intermediate nodes, wherein node B is connected to node A, node C, and node D, respectively, node D and node respectively.
- C is connected to node B.
- the sink node C starts the IP FRR, and calculates that the primary outbound interface of the sink node C to the source node A is E0/0/0, the primary next hop is the node B, and the standby outgoing interface is E0/0/1.
- the alternate next hop is node D.
- the sink node C sends the PIM Join message from E0/0/0 to the node B and from E0/0/1 to the node D according to the multicast PIM protocol, and establishes the primary path to the source node A hop by hop.
- the group will be The broadcast stream is copied into two copies and then sent through the primary path and the alternate path, respectively.
- node C discards the multicast stream received by E0/0/1 directly.
- the node C directly switches the primary path C - B - A to the alternate path C - D - B - A, and receives the multicast stream from E0/0/1. , the alternate path takes effect at this time.
- this embodiment will further describe the scheme in which the PIM-SM RPT sends the bidirectional PIM Join for protection.
- node E is the source node, directly connected to the multicast source
- node D1 is the sink node
- the receiver is directly connected.
- the aggregation point is configured on node A1
- node B1 and node C1 are intermediate nodes. It can be a router (RT, Rerouter), and PIM-SM is running on these nodes.
- Node D1 is directly connected to the receiver's interface running group management protocol (IGMP, Internet Group).
- IGMP group management protocol
- the node D1 starts the unicast IP FRR, and calculates the primary outgoing interface and the primary for each unicast route. With the next hop, the standby outbound interface, and the alternate next hop, the primary route to the RP is determined to be D1 - C1 - A1, and the alternate route is D1 - B1 - A1; at this point, node D1 can also establish a fast failure to node C1.
- the detection mechanism for example, uses BFD and other technologies to establish the fast fault detection mechanism.
- the receiver connected to the node D1 for example, a user sends an IGMP (*, G) report (report) message to the node D1, requests the data of the multicast group G (ie, the multicast stream), and the node D1 receives the IGMP ( *, G) After the report, the PIM (*, G) entry is generated, the outbound interface is added, and the upstream node of the node D1 is searched according to the aggregation point, that is, the address of the node A1.
- the PIM search result is the upstream node on the primary path (that is, the primary next hop in the embodiment of the present invention) is the node C1, and the upstream node on the standby path (that is, the standby next hop in the embodiment of the present invention) For the node Bl.
- the node D1 sends a PIM (*, G) Join message to the node C1 and the node Bl respectively, and triggers the PIM SM to construct a primary shared tree and a standby shared tree.
- the node C1 After receiving the PIM (*, G) Join, the node C1 generates a (*, G) entry, adds the outbound interface, and continues to hop to the convergence point, that is, the node A1 sends a PIM (*, G) Join message; Similarly, after receiving the PIM (*, G) Join, the node B1 also generates a (*, G) entry, adds the outbound interface, and continues to hop to the convergence point, that is, the node A1 sends a PIM (*, G) Join message.
- Node A1 receives PIM(*, G) Join from both node C1 and node B1, and then generates (*, G) entries and adds two outbound interfaces.
- the node E1 registers the packet with the RP unicast, creates a PIM (S, G) entry, and adds the outbound interface of the (*, G) interface to the outbound interface of the (S, G).
- the multicast stream is forwarded to the downstream node B1 and the node C1 of the node E1.
- Node C1 and Node B1 both receive the multicast stream, and create a PIM (S, G) entry according to the received multicast stream, and add the existing (*, G) outgoing interface as (S, G).
- the outbound interface continues to forward the multicast stream to the downstream. For example, in this embodiment, the multicast stream is forwarded to the node D.
- the node D1 is directly connected to the receiver, receives the multicast stream from the node C1 on the primary path, and creates a PIM (S, G) forwarding entry according to the received multicast stream, and the existing (*, G)
- the outbound interface is added as the outbound interface of (s, G) to forward the multicast stream to its downstream receivers.
- Node D For multicast streams from Node B on the alternate path, Node D is preemptively discarded. 208.
- the node D1 quickly perceives according to technologies such as BFD, directly switches to the standby path, receives the multicast stream from the node B1 on the standby path, and receives the received stream.
- the multicast stream is forwarded to its downstream receiver.
- the unicast IP FRR of the node D1 recalculates the new route, including the primary outbound interface, the primary next hop, and the standby outbound of each route, including the address of the aggregation point.
- the interface and the standby next hop are used to find the upstream node on the primary path of the convergence point and the upstream node on the alternate path according to the calculated new route, and the primary shared tree and the standby shared tree are re-triggered.
- the solid arrow indicates a PIM Join message
- the dotted arrow indicates a multicast stream.
- the PIM-SM is used on each node, and the primary and secondary outbound interfaces and the next hop of each unicast route to the multicast source are calculated by using the unicast IP FRR, and then calculated according to the calculation.
- the primary and secondary outgoing interfaces and the next hop are configured to send the primary and secondary paths by sending PIM Join messages.
- the node in the solution can dynamically calculate the primary and secondary outgoing interfaces and the next one.
- the hop (that is, according to the routing result) configures the multicast primary and secondary inbound interfaces that send PIM Join messages, and sends the PIM Join message to construct the primary and backup paths. Therefore, you do not need to statically configure the device to send PIM Join messages.
- the multicast master-slave interface and the next hop can adapt to the dynamic topology change of the network, greatly expand the scenario of multicast stream protection, and the PI is used in the embodiment of the present invention.
- M bidirectional join technology therefore, compared with the prior art one-way join, the transmission overhead between nodes can be reduced, which is beneficial to ensure the multicast forwarding performance after the fault occurs.
- node A2 is a source node, directly connected to a multicast source
- node D2 is a sink node, and a direct connection receiver
- node B2 and node C2 are intermediate nodes, and these nodes may specifically be routers (RT, Rerouter).
- PIM-SSM runs on these nodes, and node D2 directly connects to the receiver's interface to run IGMP.
- the process can be as follows:
- the node D2 starts the unicast IP FRR, and calculates the primary outbound interface, the primary next hop, the standby outbound interface, and the standby next hop for each unicast route, and determines that the primary route to the source node A2 is D2 - B2 - A2, the alternate route is D2 - C2 - A2; at this point, node D2 can also be established to node B2
- the fast fault detection mechanism for example, uses BFD and other technologies to establish the fast fault detection mechanism.
- the receiver connected to the node D2 for example, a user sends an IGMP (S, G) report message, requests the data of the specified multicast source group (S, G), and the node D2 receives the IGMP (S, G) report.
- the PIM (S, G) forwarding entry is generated, the outbound interface is added, and the upstream node of the node D is searched according to the address of the source node A.
- the PIM search result is the upstream node on the primary path (that is, the primary next hop in the embodiment of the present invention) is the node B2, and the upstream node on the standby path (that is, the standby next hop in the embodiment of the present invention) For node C2.
- Node D2 sends a PIM (S, G) join message to both the node C2 and the node B2, and triggers the PIM SSM to construct a primary shortest path tree and a shortest path tree.
- the node C2 After receiving the PIM (S, G) Join, the node C2 generates the (S, G) entry, adds the outbound interface, and continues to send the PIM (S, G) Join message to the upstream node hop by hop; similarly, the node After receiving the PIM (S, G) Join, B2 also generates the (S, G) entry, adds the outbound interface, and continues to send PIM (S, G) Join to the upstream node hop by hop; node A2 slave node C2 Both node B2 and P2 receive PIM (S, G) Join, and then generate (S, G) entries and add two outbound interfaces.
- the node A2 directly connects to the multicast source, and forwards the multicast stream to the downstream node B2 and the node C2 of the node A2 according to the created PIM (S, G) entry.
- Both the node C2 and the node B2 receive the multicast stream, and continue to forward the multicast stream to the downstream according to the outbound interface of the existing (S, G) entry.
- Node D2 is directly connected to the receiver, receives the multicast stream from node B2 on the primary path, and forwards to the receiver downstream of node (ie, node D2); for the multicast stream from node C on the alternate path, Then node D2 is directly discarded.
- the node D2 quickly perceives according to technologies such as BFD, directly switches to the standby path, receives the multicast stream from the standby path node C2, and forwards the packet to the downstream receiving.
- technologies such as BFD
- the unicast IPFRR of the node D2 recalculates the new route, including the primary outbound interface, the primary next hop, and the standby outbound of each route to the multicast source address. The interface and the alternate next hop, and then use the PIM protocol to find the new route based on the calculation.
- the upstream node on the primary path of the multicast source and the upstream node on the alternate path are retriggered to build the primary shortest path tree and the standby shortest path tree.
- the solid arrow indicates a PIM Join message
- the dotted arrow indicates a multicast stream.
- the embodiment of the present invention is used to run PIM-SSM on each node, and utilizes unicast.
- the IP FRR calculates the primary and secondary outgoing interfaces and the next hop of each unicast route to the multicast source, and then constructs the primary and secondary outgoing interfaces and the next hop to send the PIM Join message to the multicast source.
- the network When the network is running normally, it only receives the multicast stream on the active path and discards the multicast stream on the alternate path.
- the primary path fails, it switches to the alternate path and receives the multicast through the alternate path.
- the multicast stream sent by the source and forwards the multicast stream.
- the node in the scheme can dynamically send PIM Join messages according to the calculated primary and secondary outgoing interfaces and the next hop (that is, according to the routing result) to construct the primary backup.
- the path is not required to statically configure the primary and secondary inbound interfaces of the multicast that sends the PIM Join message on the device.
- the dynamic topology change of the network can be adapted to the network, and the multicast stream protection scenario is greatly expanded.
- the embodiment of the present invention further provides a router.
- the router includes a computing unit 401, a main sending unit 402, a standby sending unit 403, and a first processing unit 404.
- the calculating unit 401 is configured to calculate a primary outbound interface, a standby outbound interface, a primary next hop, and an alternate next hop for each unicast route that arrives at the multicast source; for example, the initial unicast IP FRR can be used to calculate The primary outbound interface, the standby outbound interface, the primary next hop, and the alternate next hop of the unicast route to the multicast source;
- the main sending unit 402 is configured to send the PIM Joi message to the primary next hop by using the primary outbound interface calculated by the calculating unit 401 as the primary ingress interface of the multicast to establish the primary path; for example, by calculating the primary
- the outbound interface sends a PIM Join message to the primary next hop to trigger the PIM-SM to construct the primary shared tree.
- the primary shared tree includes the primary path.
- the primary outbound interface sends the PIM Join message.
- the primary shortest path tree is triggered by the PIM-SM or the PIM-SSM, where the primary shortest path tree includes the primary path;
- the standby sending unit 403 is configured to send the PIM Join message to the standby next hop as the primary inbound interface calculated by the calculating unit 401 to establish an alternate path; for example, sending the calculated outbound interface
- the PIM Join message is sent to the standby next hop to trigger the PIM-SM to construct the standby shared tree.
- the standby shared tree includes the alternate path.
- the PIM Join message is sent to the standby next hop through the calculated outbound interface.
- the PIM-SM or PIM-SSM is triggered to construct a shortest path tree, where the shortest path tree includes an alternate path.
- the first processing unit 404 is configured to receive the multicast stream delivered by the multicast source and forward the multicast stream by using the standby path initiated by the standby sending unit 403 when the primary path initiated by the primary sending unit 402 is faulty.
- the first processing unit 404 may include a receiving subunit and a forwarding subunit.
- the receiving subunit is configured to receive the multicast stream delivered by the multicast source by using the alternate path initiated by the standby sending unit.
- the forwarding subunit is configured to forward the multicast stream received by the receiving subunit.
- the router may further include a second processing unit 405;
- the second processing unit 405 is configured to: when the primary path initiated by the primary sending unit 402 is used normally, receive the multicast stream delivered by the multicast source through the primary path, forward the multicast stream, and discard the multicast on the alternate path. flow.
- the router may further include a sensing unit 406;
- the sensing unit 406 is configured to detect that the primary path is faulty by the fast fault detection.
- the first processing unit 404 is further configured to: when the sensing unit 406 senses that the primary path is faulty, initiate the established alternate path receiving by using the standby sending unit 403.
- the multicast stream delivered by the multicast source forwards the multicast stream.
- the calculating unit 401 recalculates the primary outgoing interface, the primary next hop, the standby outgoing interface, and the standby next hop, thereby selecting the PIM.
- the result of the path will also change dynamically.
- the primary sending unit 402 and the standby sending unit 403 respectively send PIMs according to the newly calculated primary outgoing interface, primary next hop, alternate outgoing interface, and alternate next ⁇ . Join to establish new primary and alternate paths to achieve flexible adaptation to different scenarios of network deployment.
- the computing unit 401 of the router in the embodiment of the present invention can calculate the primary and secondary outgoing interfaces and the next hop of the unicast route to the multicast source, and then the primary sending unit 402 and the standby sending list.
- the element 403 constructs a primary and secondary path according to the calculated primary and secondary outbound interfaces and the next hop respectively.
- the sensing unit 406 senses that the primary path is faulty
- the first processing unit 404 receives the multicast delivered by the multicast source through the alternate path.
- the embodiment of the present invention further provides a communication system, which includes any router provided by the embodiment of the present invention.
- the router may include a computing unit 401, a primary transmitting unit 402, a standby transmitting unit 403, and a first processing unit 404, and may further include a second processing unit 405 and a sensing unit 406, where the first processing unit 404 may include a receiving subunit and For details, refer to the fourth embodiment, and details are not described herein again.
- the unicast FRR of the router in the communication system can calculate the primary outgoing interface, the primary next hop, the standby outgoing interface, and the standby next hop for each unicast route, and then according to the calculated primary outgoing interface, the primary Use the next hop, the standby outbound interface, and the alternate next hop to send a two-way PIM Join with the unicast to establish the primary and backup paths to the multicast source, and then direct the dual multicast stream.
- the router in the communication system only receives the multicast stream of the primary path, and discards the multicast stream on the alternate path. When the primary path fails, the router directly switches to the alternate path and receives the group on the alternate path.
- the multicast stream is streamed and forwarded. For details, refer to the previous embodiment, and details are not described herein again.
- the IP FRR of the router recalculates the primary and secondary outgoing interfaces and the next hop, and then sends PIM Joins based on the recalculated primary and secondary outgoing interfaces and the next hop. To establish a new primary alternate path.
- the communication system may include a first router 501, a second router 502, a third router 503, and a fourth router 504; assuming that the first router 501 is here a sink node;
- the first router 501 is configured to calculate a primary outgoing connection of each unicast route that reaches the multicast source.
- the port, the standby outbound interface, the active next hop, and the standby next hop; the calculated primary outbound interface is used as the primary inbound interface of the multicast to send the protocol-independent multicast to the PIM.
- One hop to establish an active path; the calculated outbound interface is used as a multicast inbound interface to send a PIM Join message to the alternate next hop to establish an alternate path; when the primary path fails, Receiving, by the standby path, the multicast stream delivered by the multicast source and forwarding the multicast stream;
- the second router 502 as the primary next hop, is configured to receive the PIM Join message sent by the first router 501, send a PIM Join message to the fourth router 504 to establish an active path, and send the fourth router 504. After the multicast stream, the multicast stream is forwarded to the first router 501;
- the third router 503, as the standby next hop, is configured to receive the PIM Join message sent by the first router 501, send the PIM Join message to the fourth router 504 to establish an alternate path, and receive the group sent by the fourth router 504. After the broadcast, the multicast stream is forwarded to the first router 501;
- the fourth router 504 is configured to receive the PIM Join message sent by the second router 502, and receive the PIM Join message sent by the third router 503, and send the multicast through the primary path after the primary path and the backup path are established. The flow is sent to the second router 502, and the multicast stream is sent to the third router 503 through the alternate path.
- the communication system of the embodiment of the present invention uses the unicast IP FRR to calculate the primary and secondary outgoing interfaces and the next hop of each unicast route to the multicast source, and then according to the calculated primary and secondary outgoing interfaces respectively. And the next hop is configured to establish a primary and secondary path by sending a PIM Join message.
- the network is running normally, only the multicast stream on the primary path is received, and the multicast stream on the alternate path is discarded.
- the node in the solution can dynamically calculate the primary and secondary outgoing interfaces and the next hop according to the route (ie, according to the routing) As a result, the PIM Join message is sent to construct the primary and backup paths. Therefore, the primary and secondary BGP interfaces that send PIM Join messages are not statically configured on the device. This can be adapted to the dynamic topology changes of the network.
- the multicast stream protection scenario and because the PIM bidirectional join technology is used in the embodiment of the present invention, the inter-node transmission can be reduced compared to the prior art one-way Join.
- the overhead is beneficial to ensure the multicast forwarding performance after the fault occurs.
- the storage medium may include: a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
一种组播快速收敛方法、 路由器和通信*** 本申请要求于 2009 年 09 月 25 日提交中国专利局、 申请号为 200910177834.9、 发明名称为 "一种组播快速收敛方法、 路由器和通信系 统" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域, 具体涉及一种组播快速收敛方法、 路由器 和通信***。 背景技术
网际协议( IP, Internet Protocol )组播是指在 IP网络中将数据包以尽 力传送(best-effort ) 的形式发送到网络中的某个确定节点子集的技术, 其 中, 这个子集称为组播组 ( multicast group ) 。 利用 IP组播技术可以实现 一些网络业务, 比如在线直播、 网络电视、 远程教育和实时视频会议等等, 但是, 由于这些业务对实时性的要求都较高, 丟包将会对这些业务产生严 重的影响, 所以, 为了保证业务数据的正常传输, 在网络发生故障时, 需 要对路径进行快速收敛。 目前组播的收敛一般釆用协议无关组播 ( PIM, Protocol Independent Multicast) 协议, 在现有的方案中, 一般会预先为主用链路指定一条备用 链路, 同时分别配置 PIM加入( Join ) 的接口, 即分别配置主用链路的上 游接口和备用链路的上游接口, 此后, 主用链路的上游接口和备用链路的 上游接口分别发送 PIM Join给各自的上一跳节点以建立到组播源的组播 树, 最终分别形成到组播源的主用路径 (即主组播树) 和备用路径 (即备 组播树), 组播源通过主用路径和备用路径同时下发组播流, 正常情况下, 各节点均只会接收主用路径上的组播流, 而丟弃备用路径上的组播流, 当 主用路径出现故障时, 则将转发表项切换到备用路径以接收备用路径上的 组播流, 并将该组播流进行转发。 需说明的是, 该 PIM协议的收敛性能远不如单播收敛, 这是因为单播 收敛只需要扩散一个故障消息, 然后每个网络节点本地完成路由计算, 就
可以把所有路由收敛到新的路径上,而组播却不然。 当然, 单播需要每条路 由下发转发, 因此性能瓶颈主要在计算和下发。 而 PIM协议相当于是一个 建隧道的协议, 每条组播路由相当于是一条隧道, 这样, 当本地处理完路 由变化并下发转发后, 还需要逐跳路由通知上游节点, 上游节点同样要进 行计算一次并下发转发的过程, 因此, PIM Join报文的传输量是重要开销, 而且由于这部分开销发生在网络节点之间, 所以要远大于设备本身下发转 发的开销。 在对现有技术的研究和实践过程中, 本发明的发明人发现, 现有技术所 提供的方案, 由于需要在设备上静态配置组播的主备入接口和下一跳, 因此 无法适应网络的动态拓朴变化, 组播流保护的场景受到较大限制。 发明内容
本发明实施例提供一种组播快速收敛方法、 路由器和通信***, 可以 适应网络的动态拓朴变化。
一种组播快速收敛方法, 包括:
计算出到达组播源的每条单播路由的主用出接口、 备用出接口、 主用 下一跳和备用下一跳;
将计算出的主用出接口作为组播的主用入接口发送 PIM Join报文给主 用下一跳以建立主用路径;
将计算出的备用出接口作为组播的备用入接口发送 PIM Join报文给备 用下一跳以建立备用路径;
当主用路径发生故障时, 通过备用路径接收组播源下发的组播流并转 发组播流。
一种路由器, 包括:
计算单元, 用于计算出到达组播源的每条单播路由的主用出接口、 备 用出接口、 主用下一跳和备用下一跳;
主发送单元, 用于将计算单元计算出的主用出接口作为组播的主用入 接口发送 PIM Join报文给主用下一跳以建立主用路径;
备发送单元, 用于将计算单元计算出的备用出接口作为组播的备用入 接口发送 PIM Join报文给备用下一跳以建立备用路径;
第一处理单元, 用于当主发送单元发起建立的主用路径发生故障时, 通过备发送单元发起建立的备用路径接收组播源下发的组播流并转发组播 流。
一种通信***, 包括本发明实施例提供的任意一种路由器, 例如, 包 括:
第一路由器, 用于计算出到达组播源的每条单播路由的主用出接口、 备用出接口、 主用下一跳和备用下一跳; 将计算出的主用出接口作为组播 的主用入接口发送协议无关组播加入 PIM Join报文给所述主用下一跳以建 立主用路径; 将计算出的备用出接口作为组播的备用入接口发送 PIM Join 报文给所述备用下一跳以建立备用路径; 当所述主用路径发生故障时, 通 过所述备用路径接收组播源下发的组播流并转发组播流;
第二路由器, 作为主用下一跳, 用于接收第一路由器发送的 PIM Join 报文, 发送 PIM Join报文给第四路由器以建立主用路径, 在接收到第四路 由器发送的组播流后, 将组播流转发给第一路由器;
第三路由器, 作为备用下一跳, 用于接收第一路由器发送的 PIM Join 报文, 发送 PIM Join报文给第四路由器以建立备用路径, 在接收到第四路 由器发送的组播流后, 将组播流转发给第一路由器;
第四路由器, 用于接收第二路由器发送的 PIM Join报文, 以及接收第 三路由器发送的 PIM Join报文, 在主用路径和备用路径建立完成后, 通过 主用路径发送组播流给第二路由器, 通过备用路径发送组播流给第三路由 器。
本发明实施例釆用计算出到达组播源的每条单播路由的主备用出接口和 下一跳, 然后分别根据计算出的主备用出接口和下一跳构建主备用路径, 当 主用路径发生故障时, 通过备用路径接收组播源下发的组播流并转发组播流; 由于该方案中的节点可以动态地根据计算出的主备用出接口和下一跳(即根 据选路结果)发送 PIM Join报文以构建主备用路径, 因此无需在设备上静态配 置发送 PIM Joii^艮文的组播的主备入接口和下一跳,可以适应网络的动态拓朴 变化, 大大扩充了组播流保护的场景。
附图说明
图 1是本发明实施例一所提供的方法的方法流程图;
图 2是本发明实施例二提供的网络拓朴示意图;
图 3是本发明实施例二提供的网络拓朴场景示意图;
图 4是本发明实施例三提供的网络拓朴场景示意图;
图 5是本发明实施例所提供的路由器的结构示意图;
图 6是本发明实施例所提供的通信***的结构示意图。 具体实施方式 下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进 行清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没 有作出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的 范围。
本发明实施例提供一种组播快速收敛方法、 路由器和通信***。 以下 分别进行详细说明。 实施例一、
本实施例将从宿节点的角度来描述, 在本发明实施例中, 宿节点指的 是直连接收者的节点, 源节点指的是直连组播源的节点, 另外, 单播路由 的出接口对于组播应用来说为入接口。
一种组播快速收敛方法, 包括: 计算出到达组播源的每条单播路由的 主用出接口、 备用出接口、 主用下一跳和备用下一跳; 将计算出的主用出 接口作为组播的主用入接口发送 PIM Join报文给主用下一跳以建立主用路 径; 将计算出的备用出接口作为组播的备用入接口发送 PIM Join报文给备 用下一跳以建立备用路径; 当主用路径发生故障时, 通过备用路径接收组 播源下发的组播流并转发组播流。其中,本发明实施例中所描述的 PIM Join 报文, 均指的是 PIM双向 Join报文, 以下均简称 PIM Join报文。 如图 1 所示, 具体流程可以如下:
101、 计算出到达组播源的每条单播路由的主用出接口、 备用出接口、 主用下一跳和备用下一跳;
例如, 可以利用启动单播 IP快速重路由 ( FRR, Fast Reroute )计算出
到达组播源的每条单播路由的主用出接口、 备用出接口、 主用下一跳和备 用下一跳。 一般的, 到达特定的组播源只有一条最优的单播路由, 但是, 如果启动单播 IP FRR, 则还会存在其他的备用单播路由, 即存在备用出接 口和下一跳, 因此, 此时, 可以计算出到达组播源的每条单播路由的主用 出接口、 备用出接口、 主用下一跳和备用下一跳。
其中, IP FRR指的是在故障发生时, 在和故障链路或故障节点相邻的 路由器上通过直接更改转发表项的下一跳使其绕过故障节点而达到业务不 中断的效果, 并且要求转发流量不会造成环路的相关技术。 这种做法不要 求在控制层面进行收敛, 仅仅依赖于故障感知时间和切换下一跳的时间, 因此可以实现快速重路由的目的, 目前主要应用于单播领域, 本发明实施 例将该技术结合 PIM 双向加入 ( Join )应用在组播中, 以适应网络的动态 拓朴变化, 关于这一点, 在以下的实施例中将会进行详细地描述。
102、 将计算出的主用出接口作为组播的主用入接口发送 PIM Join报文 给主用下一跳以建立主用路径;
例如, 通过计算出的主用出接口发送 PIM Join报文给主用下一跳, 以 触发协议无关组播 -稀松模式 ( PIM-SM, Protocol Independent
Multicast- Sparse Mode ) 构建主共享树 ( RPT, Rendezvous Point Tree ) , 其中, 主共享树包括主用路径; 或者,
通过计算出的主用出接口发送 PIM Join报文给主用下一跳, 以触发 PIM-SM或协议无关组播-特定源组播 (PIM-SSM, Protocol Independent Multicast- Source- Specific Multicast)构建主最短路径树 ( SPT, Shortest Path Tree ) , 其中, 主最短路径树包括主用路径。
103、 将计算出的备用出接口作为组播的备用入接口发送 PIM Join报文 给备用下一跳以建立备用路径;
例如, 通过计算出的备用出接口发送 PIM Join报文给备用下一跳, 以 触发 PIM-SM构建备共享树, 其中, 备共享树包括备用路径; 或者,
通过计算出的备用出接口发送 PIM Join报文给备用下一跳, 以触发 PIM-SM或 PIM-SSM构建备最短路径树, 其中, 备最短路径树包括备用路 径。
其中, 步骤 102和步骤 103的执行顺序可以不分先后。
104、 当主用路径发生故障时, 通过备用路径接收组播源下发的组播流
并转发组播流。
例如, 通过备用路径接收组播源下发的组播流, 然后根据转发表项和 出接口转发组播流。
需说明的是, 当主用路径使用正常时, 通过主用路径接收组播源下发 的组播流并转发组播流, 丟弃备用路径上的组播流。 即, 在网络没有发生 故障时, 一般只接收来自主用路径上的组播流, 而丟弃来自备用路径上的 组播流, 只有在网络出现故障, 且该故障是主用路径发生故障时, 才将主 用路径切换到备用路径, 从备用路径上接收组播流并进行组播流的转发。 其中, 可以通过快速故障检测, 比如双向转发检测 (BFD, Bidirectional Forwarding Detection) 等技术来快速感知是否发生故障, 如果主用路径发 生故障, 则执行步骤 104。
另外, 还需说明的是, 若网络拓朴发生变化, 则单播路由收敛以后, IP FRR会重新计算出主用出接口、主用下一跳、备用出接口和备用下一跳, 由此 PIM选路结果也会随之动态变化, 那么, 此时宿节点会根据新计算出 来的主用出接口、主用下一跳、备用出接口和备用下一跳分别发送 PIM Join 以建立新的主用路径和备用路径,从而实现灵活适应网络部署的不同情况。
由上可知, 本发明实施例釆用计算出到达组播源的每条单播路由的主 备用出接口和下一跳 (即主用出接口、 主用下一跳、 备用出接口和备用下 一跳, 以下均简称主备用出接口和下一跳) , 然后分别根据计算出的主备 用出接口和下一跳构建到达组播源的主备用路径(即主用路径和备用路径, 以下均简称主备用路径) , 当主用路径发生故障时, 通过备用路径接收组 播源下发的组播流并转发组播流; 由于该方案中的节点可以动态地根据计 算出的主备用出接口和下一跳 (即根据选路结果)发送 PIM Join报文以构 建主备用路径, 因此无需在设备上静态配置发送 PIM Join报文的组播的主 备入接口和下一跳, 可以适应网络的动态拓朴变化, 大大扩充了组播流保 护的场景; 而且由于本发明实施例釆用了 PIM双向 Join的技术, 因此相对于 现有技术的单向 Join来说, 可以减少节点间的传输开销, 有利于。 实施例二、
根据实施例一所描述的方法可知,单播 FRR可以为每条单播路由计算 出主用出接口、 主用下一跳、 备用出接口和备用下一跳, 根据计算出的主
用出接口、 主用下一跳、 备用出接口和备用下一跳, 与单播联动发送双向
PIM Join建立到组播源的主用路径和备用路径, 引下双份组播流, 在网络 运行正常的情况下, 组播网络中的节点只接收主用路径的组播流, 对于备 用路径上的组播流则予以丟弃, 当主用路径发生故障时, 则直接切换到备 用路径, 接收备用路径上的组播流并转发该组播流。
当然, 若网络拓朴发生变化, 则单播路由收敛以后, IP FRR会重新计 算主备用出接口和下一跳, 然后根据重新计算出来的主备用出接口和下一 跳分别发送 PIM Join以建立新的主备用路径。
例如, 如图 2所示, 节点 C为宿节点, 节点 A为源节点, 节点 B和节点 C 为中间节点, 其中, 节点 B分别和节点 A、 节点 C和节点 D相连, 节点 D分别 和节点 C和节点 B相连。 则可以如下:
( 1 )宿节点 C启动 IP FRR, 计算出宿节点 C到源节点 A的主用出接 口为 E0/0/0 , 主用下一跳为节点 B、 备用出接口为 E0/0/1 , 备用下一跳为 节点 D。
( 2 )宿节点 C根据组播 PIM协议将 PIM Join报文分别从 E0/0/0发向 节点 B和从 E0/0/1发向节点 D, 逐跳建立到源节点 A的主用路径 C - B - A和备用路径 C - D - B - A, 以便源节点 A下发组播流, 需说明的是, 当 节点 B接收到接收 A下发的组播流后, 将会把组播流复制成两份, 然后分 别通过主用路径和备用路径进行发送。
( 3 ) 网络正常运行情况下, 节点 C对于 E0/0/1接收的组播流直接丟 弃。 当节点 B和节点 C之间的链路发生故障时, 节点 C直接将主用路径 C - B - A切换到备用路径 C - D - B - A上, 从 E0/0/1接收组播流, 此时备 用路径生效。
为了更清楚地说明以上方法, 本实施例将以 PIM-SM RPT发送双向 PIM Join以进行保护的方案为例作进一步详细说明。
如图 3所示, 假设节点 E为源节点, 直连组播源, 节点 D1为宿节点, 直连接收者, 在节点 A1上配置汇聚点, 节点 B1和节点 C1为中间节点, 这些节点具体可以为路由器( RT , Rerouter ),且这些节点上均运行 PIM-SM, 节点 D 1直连接收者的接口运行组管理协议( IGMP , Internet Group
Management Protocol Internet ) 。 则 ¾ΐ程可以 ^口下:
201、 节点 D1启动单播 IP FRR, 为每条单播路由计算主用出接口、 主
用下一跳、 备用出接口和备用下一跳, 确定到 RP的主路由为 D1 - C1 - A1, 备用路由为 D1 - B1 - A1; 此时, 节点 D1还可以建立到节点 C1的快 速故障检测机制, 例如利用 BFD等技术建立该快速故障检测机制。
202、节点 D1所连接收者比如某个用户发送 IGMP( *, G )报告( report ) 报文给节点 D1 ,请求组播组 G的数据(即组播流 ),节点 D1接收到该 IGMP (*, G) report后, 生成 PIM (*, G)表项, 添加出接口, 并根据汇聚点, 即节点 A1的地址查找节点 D1的上游节点。 PIM查找结果为主用路径上的 上游节点(即本发明实施例所说的主用下一跳)为节点 C1, 备用路径上的 上游节点 (即本发明实施例所说的备用下一跳) 为节点 Bl。
203、 节点 Dl向节点 C1和节点 Bl分别发送 PIM ( *, G) Join报文, 触发 PIM SM构建主共享树和备共享树。
204、 节点 C1收到 PIM (*, G) Join以后, 生成( *, G)表项, 添加 出接口, 并继续逐跳向汇聚点, 即节点 A1发送 PIM ( * , G) Join报文; 同理, 节点 B1收到 PIM (*, G) Join以后, 也生成 (*, G )表项, 添加出接口, 并继续逐跳向汇聚点, 即节点 A1发送 PIM ( * , G) Join报 文;
节点 A1从节点 C1和节点 B1均收到 PIM( *, G) Join, 于是生成( *, G)表项并添加两个出接口。
205、 节点 E1向 RP单播注册(register)报文, 创建 PIM (S, G)表 项, 并将(*, G) 的出接口添加为 (S, G) 的出接口, 通过该出接口向节 点 E1的下游节点 B1和节点 C1转发组播流。
206、 节点 C1和节点 B1均接收组播流, 并根据接收到的组播流创建 PIM ( S, G)表项, 并将已有( *, G)的出接口添加为 ( S, G)的出接口, 继续向下游转发组播流, 比如在本实施例中即为向节点 D转发组播流。
207、 节点 D1直连接收者, 接收来自主路径上的节点 C1的组播流, 根据接收到的组播流创建 PIM (S, G)转发表项, 并将已有(*, G)的出 接口添加为 (s, G) 的出接口, 向其下游的接收者转发组播流;
对于来自备用路径上的节点 B的组播流, 则节点 D予于直接丟弃。 208、当节点 D1与节点 C1之间的链路发生故障时,节点 D1根据 BFD 等技术快速感知, 直接切换至备用路径上, 从备用路径上的节点 B1接收 组播流, 并将接收到的组播流转发给其下游的接收者。
需说明的是, 单播路由收敛后, 节点 D1的单播 IP FRR会重新计算新的 路由, 包括到汇聚点地址在内的每条路由的主用出接口、 主用下一跳、 备 用出接口和备用下一跳, 然后利用 PIM协议根据计算出来的新的路由查找 到汇聚点的主用路径上的上游节点和备用路径上的上游节点, 重新触发构 建主共享树和备共享树。
另外, 需说明的是, 在图 3 , 实线箭头表示 PIM Join报文, 虚线箭头表 示组播流。
由上可知, 本发明实施例釆用在各个节点上运行 PIM-SM, 利用单播 IP FRR计算出到达组播源的每条单播路由的主备用出接口和下一跳, 然后分 别根据计算出的主备用出接口和下一跳通过发送 PIM Join报文构建主备用 路径, 在网络运行正常时, 只接收主用路径上的组播流, 丟弃备用路径上 的组播流, 当主用路径发生故障时, 则切换至备用路径, 通过备用路径接 收组播源下发的组播流并转发组播流; 由于该方案中的节点可以动态地根 据计算出的主备用出接口和下一跳 (即根据选路结果)对发送 PIM Join报 文的组播的主备入接口进行配置, 并发送 PIM Joii^艮文以构建主备用路径, 因此无需在设备上静态配置发送 PIM Join报文的组播的主备入接口和下一 跳, 可以适应网络的动态拓朴变化, 大大扩充了组播流保护的场景, 而且 由于本发明实施例釆用了 PIM双向 Join的技术,因此相对于现有技术的单向 Join来说, 可以减少节点间的传输开销, 有利于保证在故障发生后的组播 转发性能。 实施例三、
本实施例将以 PIM-SSM SPT发送双向 PIM Join以进行保护的方案为 例作进一步详细说明。
如图 4所示, 假设节点 A2为源节点, 直连组播源, 节点 D2为宿节点, 直连接收者, 节点 B2和节点 C2为中间节点, 这些节点具体可以为路由器 ( RT, Rerouter ) , 且这些节点上均运行 PIM-SSM, 节点 D2直连接收者 的接口运行 IGMP。 则流程可以如下:
301、 节点 D2启动单播 IP FRR, 为每条单播路由计算主用出接口、 主用 下一跳、 备用出接口和备用下一跳, 确定到源节点 A2的主路由为 D2 - B2 - A2, 备用路由为 D2 - C2 - A2; 此时, 节点 D2还可以建立到节点 B2
的快速故障检测机制, 例如利用 BFD等技术建立该快速故障检测机制。
302、 节点 D2所连接收者比如某个用户发送 IGMP ( S, G) report报文, 请求指定组播源组( S, G )的数据, 节点 D2接收到该 IGMP ( S, G ) report 报文后, 生成 PIM (S, G)转发表项, 添加出接口, 并根据源节点 A的地 址查找节点 D的上游节点。 PIM查找结果为主用路径上的上游节点(即本 发明实施例所说的主用下一跳)为节点 B2, 备用路径上的上游节点(即本 发明实施例所说的备用下一跳) 为节点 C2。
303、 节点 D2向节点 C2和节点 B2均发送 PIM ( S , G) join报文, 触 发 PIM SSM构建主最短路径树和备最短路径树。 304、 节点 C2收到 PIM (S, G) Join以后, 生成 ( S, G )表项, 添加 出接口, 并继续逐跳向上游节点发送 PIM ( S, G) Join报文; 同理, 节点 B2收到 PIM (S, G) Join以后, 也生成 ( S, G )表项, 添 加出接口, 并继续逐跳向上游节点发送 PIM ( S, G) Join才艮文; 节点 A2从节点 C2和节点 B2均收到 PIM ( S, G) Join, 于是生成( S, G)表项并添加两个出接口。
305、 节点 A2直连组播源, 根据创建的 PIM (S, G)表项, 向节点 A2 的下游节点 B2和节点 C2转发组播流。
306、 节点 C2和节点 B2均接收组播流, 并根据已有的 (S, G)表项的 出接口继续向下游转发组播流。
307、 节点 D2直连接收者, 接收来自主用路径上的节点 B2的组播流, 并向其 (即节点 D2) 下游的接收者转发; 对于来自备用路径上的节点 C的组播流, 则节点 D2予于直接丟弃。
308、 当节点 D2和节点 B2之间的链路发生故障后, 节点 D2根据 BFD 等技术快速感知, 直接切换至备用路径上, 从备路径节点 C2接收组播流, 并转发到其下游的接收者。 需说明的是, 单播路由收敛后, 节点 D2的单播 IPFRR会重新计算新的 路由, 包括到组播源地址在内的每条路由的主用出接口、 主用下一跳、 备 用出接口和备用下一跳, 然后利用 PIM协议根据计算出来的新的路由查找
到组播源的主用路径上的上游节点和备用路径上的上游节点, 重新触发构 建主最短路径树和备最短路径树。 另外, 需说明的是, 在图 4 , 实线箭头表示 PIM Join报文, 虚线箭头表 示组播流。
由上可知, 本发明实施例釆用在各个节点上运行 PIM-SSM, 利用单播
IP FRR计算出到达组播源的每条单播路由的主备用出接口和下一跳, 然后 分别根据计算出的主备用出接口和下一跳通过发送 PIM Join报文构建到达 组播源的主备用路径, 在网络运行正常时, 只接收主用路径上的组播流, 丟弃备用路径上的组播流, 当主用路径发生故障时, 则切换至备用路径, 通过备用路径接收组播源下发的组播流并转发组播流; 由于该方案中的节 点可以动态地根据计算出的主备用出接口和下一跳 (即根据选路结果)发 送 PIM Join报文以构建主备用路径, 因此无需在设备上静态配置发送 PIM Join报文的组播的主备用入接口, 可以适应网络的动态拓朴变化, 大大扩 充了组播流保护的场景, 而且由于本发明实施例釆用了 PIM双向 Join的技 术, 因此相对于现有技术的单向 Join来说, 可以减少节点间的传输开销, 有利于保证在故障发生后的组播转发性能。 实施例四、
为了更好地实施以上方法, 本发明实施例还相应地提供一种路由器, 如图 5所示, 该路由器包括计算单元 401、 主发送单元 402、 备发送单元 403 和第一处理单元 404;
计算单元 401 , 用于计算出到达组播源的每条单播路由的主用出接口、 备用出接口、 主用下一跳和备用下一跳; 例如, 可以利用启动单播 IP FRR 计算出到达组播源的单播路由的主用出接口、 备用出接口、 主用下一跳和 备用下一跳;
主发送单元 402 , 用于将计算单元 401计算出的主用出接口作为组播的 主用入接口发送 PIM Joi 艮文给主用下一跳以建立主用路径; 例如, 通过 计算出的主用出接口发送 PIM Join报文给主用下一跳, 以触发 PIM-SM构建 主共享树, 其中, 主共享树包括主用路径; 或者, 通过计算出的主用出接 口发送 PIM Join报文给主用下一跳,以触发 PIM-SM或 PIM-SSM构建主最短 路径树, 其中, 主最短路径树包括主用路径;
备发送单元 403 , 用于将计算单元 401计算出的备用出接口作为组播的 主用入接口发送 PIM Join报文给备用下一跳以建立备用路径; 例如, 通过 计算出的备用出接口发送 PIM Join报文给备用下一跳, 以触发 PIM-SM构建 备共享树, 其中, 备共享树包括备用路径; 或者, 通过计算出的备用出接 口发送 PIM Join报文给备用下一跳,以触发 PIM-SM或 PIM-SSM构建备最短 路径树, 其中, 备最短路径树包括备用路径;
第一处理单元 404 , 用于当主发送单元 402发起建立的主用路径发生故 障时,通过备发送单元 403发起建立的备用路径接收组播源下发的组播流并 转发组播流。
其中, 第一处理单元 404可以包括接收子单元和转发子单元; 接收子单元, 用于通过备发送单元发起建立的备用路径接收组播源下 发的组播流;
转发子单元, 用于转发接收子单元接收到的组播流。
如图 5所示, 该路由器还可以包括第二处理单元 405;
第二处理单元 405 , 用于当主发送单元 402发起建立的主用路径使用正 常时, 通过主用路径接收组播源下发的组播流并转发组播流, 丟弃备用路 径上的组播流。
如图 5所示, 该路由器还可以包括感知单元 406;
感知单元 406, 用于通过快速故障检测来感知主用路径发生故障; 第一处理单元 404 , 还用于当感知单元 406感知主用路径发生故障时, 通过备发送单元 403发起建立的备用路径接收组播源下发的组播流并转发 组播流。
需说明的是, 若网络拓朴发生变化, 则单播路由收敛以后, 计算单元 401会重新计算出主用出接口、 主用下一跳、 备用出接口和备用下一跳, 由 此 PIM选路结果也会随之动态变化, 那么, 此时主发送单元 402和备发送单 元 403会根据新计算出来的主用出接口、主用下一跳、备用出接口和备用下 一 ϋ 分别发送 PIM Join以建立新的主用路径和备用路径, 从而实现灵活适 应网络部署的不同情况。
以上各个单元的具体实施可参见前面实施例, 在此不再赘述。
由上可知,本发明实施例的路由器的计算单元 401可以计算出到达组播 源的单播路由的主备用出接口和下一跳,然后由主发送单元 402和备发送单
元 403分别根据计算出的主备用出接口和下一跳构建主备用路径,当感知单 元 406感知到主用路径发生故障时, 第一处理单元 404通过备用路径接收组 播源下发的组播流并转发组播流; 由于该方案中的节点可以动态地根据计 算出的主备用出接口和下一跳 (即根据选路结果)发送 PIM Join报文以构 建主备用路径, 因此无需在设备上静态配置发送 PIM Join报文的组播的主 备入接口和下一跳, 可以适应网络的动态拓朴变化, 大大扩充了组播流保 护的场景; 而且由于本发明实施例釆用了 PIM双向 Join的技术, 因此相对于 现有技术的单向 Join来说, 可以减少节点间的传输开销, 有利于。 实施例五、
相应地, 本发明实施例还提供一种通信***, 包括本发明实施例提供 的任意一种路由器。
该路由器可以包括计算单元 401、 主发送单元 402、备发送单元 403和第 一处理单元 404 , 还可以包括第二处理单元 405和感知单元 406 , 其中, 第一 处理单元 404可以包括接收子单元和转发子单元, 具体可参见实施例四,在 此不再赘述。
该通信***中的路由器的单播 FRR可以为每条单播路由计算出主用 出接口、 主用下一跳、 备用出接口和备用下一跳, 然后根据计算出的主用 出接口、主用下一跳、备用出接口和备用下一跳,与单播联动发送双向 PIM Join建立到组播源的主用路径和备用路径, 引下双份组播流, 在网络运行 正常的情况下, 该通信***中的路由器只接收主用路径的组播流, 对于备 用路径上的组播流则予以丟弃, 当主用路径发生故障时, 则直接切换到备 用路径, 接收备用路径上的组播流并转发该组播流。 具体可参见前面的实 施例, 在此不再赘述。
当然, 若网络拓朴发生变化, 则单播路由收敛以后, 路由器的 IP FRR 会重新计算主备用出接口和下一跳, 然后根据重新计算出来的主备用出接 口和下一跳分别发送 PIM Join以建立新的主备用路径。
以下将举例作简略说明, 如图 6所示, 该通信***可以包括第一路由 器 501、 第二路由器 502、 第三路由器 503和第四路由器 504; 假设第一路 由器 501在此作为宿节点;
第一路由器 501 , 用于计算出到达组播源的每条单播路由的主用出接
口、 备用出接口、 主用下一跳和备用下一跳; 将计算出的主用出接口作为 组播的主用入接口发送协议无关组播加入 PIM Joii^艮文给所述主用下一跳 以建立主用路径; 将计算出的备用出接口作为组播的备用入接口发送 PIM Join报文给所述备用下一跳以建立备用路径; 当所述主用路径发生故障时, 通过所述备用路径接收组播源下发的组播流并转发组播流;
第二路由器 502 ,作为主用下一跳,用于接收第一路由器 501发送的 PIM Join报文, 发送 PIM Join报文给第四路由器 504以建立主用路径, 在接收到 第四路由器 504发送的组播流后, 将组播流转发给第一路由器 501;
第三路由器 503 ,作为备用下一跳,用于接收第一路由器 501发送的 PIM Join报文, 发送 PIM Join报文给第四路由器 504以建立备用路径, 在接收到 第四路由器 504发送的组播流后, 将组播流转发给第一路由器 501;
第四路由器 504, 用于接收第二路由器 502发送的 PIM Join报文, 以 及接收第三路由器 503发送的 PIM Join报文, 在主用路径和备用路径建立 完成后, 通过主用路径发送组播流给第二路由器 502, 通过备用路径发送 组播流给第三路由器 503。
以上实施具体可参见前面实施例, 在此不再赘述。
由上可知, 本发明实施例的通信***釆用利用单播 IP FRR计算出到达 组播源的每条单播路由的主备用出接口和下一跳, 然后分别根据计算出的 主备用出接口和下一跳通过发送 PIM Join报文构建主备用路径, 在网络运 行正常时, 只接收主用路径上的组播流, 丟弃备用路径上的组播流, 当主 用路径发生故障时, 则切换至备用路径, 通过备用路径接收组播源下发的 组播流并转发组播流; 由于该方案中的节点可以动态地根据计算出的主备 用出接口和下一跳(即根据选路结果)发送 PIM Join报文以构建主备用路 径, 因此无需在设备上静态配置发送 PIM Join报文的组播的主备入接口和 下一跳, 可以适应网络的动态拓朴变化, 大大扩充了组播流保护的场景, 而且由于本发明实施例釆用了 PIM双向 Join的技术,因此相对于现有技术的 单向 Join来说, 可以减少节点间的传输开销, 有利于保证在故障发生后的 组播转发性能。 本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分 步骤是可以通过程序来指令相关的硬件来完成, 该程序可以存储于一计算
机可读存储介质中, 存储介质可以包括: 只读存储器 (ROM, Read Only Memory ) 、 随机存取记忆体 ( RAM, Random Access Memory) 、 磁盘或 光盘等。
以上对本发明实施例所提供的一种组播快速收敛方法、 路由器和通信 进行了阐述, 以上实施例的说明只是用于帮助理解本发明的方法及其核心 思想; 同时, 对于本领域的一般技术人员, 依据本发明的思想, 在具体实 施方式及应用范围上均会有改变之处, 综上所述, 本说明书内容不应理解 为对本发明的限制。
Claims
1、 一种组播快速收敛方法, 其特征在于, 包括:
计算出到达组播源的每条单播路由的主用出接口、 备用出接口、 主用 下一跳和备用下一跳;
将计算出的所述主用出接口作为组播的主用入接口发送协议无关组播 加入 PIM Joii^艮文给所述主用下一跳以建立主用路径;
将计算出的所述备用出接口作为组播的备用入接口发送 PIM Join报文 给所述备用下一跳以建立备用路径;
当所述主用路径发生故障时, 通过所述备用路径接收组播源下发的组 播流并转发组播流。
2、 根据权利要求 1所述的方法, 其特征在于, 所述计算出到达组播源 的每条单播路由的主用出接口、 备用出接口、 主用下一跳和备用下一跳, 具体包括:
利用启动单播网际协议快速重路由 IP FRR, 计算出到达组播源的每条 单播路由的主用出接口、 备用出接口、 主用下一跳和备用下一跳。
3、 根据权利要求 1或 2所述的方法, 其特征在于,
所述将计算出的所述主用出接口作为组播的主用入接口发送 PIM Join 报文给所述主用下一跳以建立主用路径, 具体包括:
通过计算出的所述主用出接口发送 PIM Join报文给所述主用下一跳, 以触发协议无关组播 -稀松模式 PIM-SM构建主共享树,所述主共享树包括 主用路径;
所述将计算出的所述备用出接口作为组播的备用入接口发送 PIM Join 报文给所述备用下一跳以建立备用路径包括:
通过计算出的备用出接口发送 PIM Join报文给备用下一跳, 以触发 PIM-SM构建备共享树, 所述备共享树包括备用路径。
4、 根据权利要求 1或 2所述的方法, 其特征在于,
所述根据计算出的所述主用出接口发送 PIM Join报文给所述主用下一 跳以建立主用路径, 具体包括:
通过计算出的所述主用出接口发送 PIM Join报文给主用下一跳, 以触 发 PIM-SM或协议无关组播 -特定源组播 PIM-SSM构建主最短路径树, 所 述主最短路径树包括主用路径;
所述将计算出的备用出接口作为组播的备用入接口发送 PIM Join报文 给备用下一跳以建立备用路径包括:
通过计算出的备用出接口发送 PIM Join报文给备用下一跳, 以触发
PIM-SM或 PIM-SSM构建备最短路径树, 所述备最短路径树包括备用路径。
5、 根据权利要求 1或 2所述的方法, 其特征在于, 还包括:
当主用路径使用正常时, 通过主用路径接收组播源下发的组播流并转 发组播流, 丟弃备用路径上的组播流。
6、 根据权利要求 1或 2所述的方法, 其特征在于,
通过快速故障检测 B F D来感知主用路径发生故障。
7、 一种路由器, 其特征在于, 包括:
计算单元, 用于计算出到达组播源的每条单播路由的主用出接口、 备 用出接口、 主用下一跳和备用下一跳;
主发送单元, 用于将计算单元计算出的所述主用出接口作为组播的主 用入接口发送 PIM Joii^艮文给所述主用下一跳以建立主用路径;
备发送单元, 用于将计算单元计算出的所述备用出接口作为组播的备 用入接口发送 PIM Joii^艮文给所述备用下一跳以建立备用路径;
第一处理单元, 用于当所述主发送单元发起建立的所述主用路径发生 故障时, 通过所述备发送单元发起建立的所述备用路径接收组播源下发的 组播流并转发组播流。
8、 根据权利要求 7所述的路由器, 其特征在于, 还包括第二处理单元; 第二处理单元, 用于当所述主发送单元发起建立的所述主用路径使用 正常时, 通过所述主用路径接收组播源下发的组播流并转发组播流, 丟弃 所述备用路径上的组播流。
9、 根据权利要求 7或 8所述的路由器, 其特征在于, 还包括感知单元; 感知单元, 用于通过快速故障检测 BFD来感知主用路径发生故障; 第一处理单元,还用于当所述感知单元感知所述主用路径发生故障时, 通过所述备发送单元发起建立的所述备用路径接收组播源下发的组播流并 转发组播流。
10、 一种通信***, 其特征在于, 包括:
第一路由器, 用于计算出到达组播源的每条单播路由的主用出接口、 备用出接口、 主用下一跳和备用下一跳; 将计算出的主用出接口作为组播 的主用入接口发送协议无关组播加入 PIM Join报文给所述主用下一跳以建 立主用路径; 将计算出的备用出接口作为组播的备用入接口发送 PIM Join 报文给所述备用下一跳以建立备用路径; 当所述主用路径发生故障时, 通 过所述备用路径接收组播源下发的组播流并转发组播流;
第二路由器, 作为主用下一跳, 用于接收第一路由器发送的 PIM Join 报文, 发送 PIM Join报文给第四路由器以建立主用路径, 在接收到第四路 由器发送的组播流后, 将组播流转发给第一路由器;
第三路由器, 作为备用下一跳, 用于接收第一路由器发送的 PIM Join 报文, 发送 PIM Join报文给第四路由器以建立备用路径, 在接收到第四路 由器发送的组播流后, 将组播流转发给第一路由器;
第四路由器, 用于接收第二路由器发送的 PIM Join报文, 以及接收第三 路由器发送的 PIM Join报文, 在主用路径和备用路径建立完成后, 通过主用 路径发送组播流给第二路由器, 通过备用路径发送组播流给第三路由器。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10818393A EP2437444A4 (en) | 2009-09-25 | 2010-09-17 | METHOD, ROUTER AND COMMUNICATION SYSTEM FOR FAST MULTICAST CONVERGENCE |
US13/339,402 US20120099422A1 (en) | 2009-09-25 | 2011-12-29 | Fast convergence method, router, and communication system for multicast |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009101778349A CN101656679B (zh) | 2009-09-25 | 2009-09-25 | 一种组播快速收敛方法、路由器和通信*** |
CN200910177834.9 | 2009-09-25 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/339,402 Continuation US20120099422A1 (en) | 2009-09-25 | 2011-12-29 | Fast convergence method, router, and communication system for multicast |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011035699A1 true WO2011035699A1 (zh) | 2011-03-31 |
Family
ID=41710776
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/077022 WO2011035699A1 (zh) | 2009-09-25 | 2010-09-17 | 一种组播快速收敛方法、路由器和通信*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US20120099422A1 (zh) |
EP (1) | EP2437444A4 (zh) |
CN (1) | CN101656679B (zh) |
WO (1) | WO2011035699A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102315951A (zh) * | 2011-09-19 | 2012-01-11 | 华为技术有限公司 | 一种组播报文的传输方法、相关设备及*** |
CN102388568A (zh) * | 2011-09-20 | 2012-03-21 | 华为技术有限公司 | 一种转发方法及转发装置 |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101656679B (zh) * | 2009-09-25 | 2012-04-04 | 华为技术有限公司 | 一种组播快速收敛方法、路由器和通信*** |
CN102244602B (zh) * | 2010-05-11 | 2014-12-31 | 华为技术有限公司 | 在协议无关组播双重加入下转发数据的方法、装置及*** |
CN102316016B (zh) * | 2010-07-05 | 2014-12-31 | 华为技术有限公司 | 组播流量的转发方法及装置 |
CN101902403A (zh) * | 2010-07-30 | 2010-12-01 | 中国联合网络通信集团有限公司 | 一种增强组播源可靠性的方法及其装置 |
CN102726000B (zh) * | 2011-07-22 | 2017-06-16 | 华为技术有限公司 | 故障通告方法、检测装置、转发装置及*** |
CN102299847B (zh) * | 2011-08-19 | 2014-06-04 | 北京星网锐捷网络技术有限公司 | 组播分发树切换方法、装置、***、源设备和目的设备 |
CN102447569B (zh) * | 2011-12-29 | 2015-06-03 | 中兴通讯股份有限公司 | 一种点对多点组播业务的保护方法及网络设备 |
US8948051B2 (en) * | 2012-05-30 | 2015-02-03 | Alcatel Lucent | System and method for efficient MVPN source redundancy with S-PMSI |
CN103259721B (zh) * | 2013-04-16 | 2016-08-17 | 杭州华三通信技术有限公司 | Spbm网络中的报文转发方法及装置 |
CN104348736A (zh) * | 2013-07-31 | 2015-02-11 | 北京华为数字技术有限公司 | 组播负载场景下选路的方法和路由器 |
CN103490951A (zh) * | 2013-09-09 | 2014-01-01 | 神州数码网络(北京)有限公司 | 基于bfd的多跳链路中双向转发检测方法 |
CN104579945B (zh) * | 2013-10-18 | 2019-07-02 | 中兴通讯股份有限公司 | 一种冗余保护方法及装置 |
CN103795626B (zh) | 2014-02-19 | 2017-07-07 | 华为技术有限公司 | 组播快速保护倒换的方法与装置 |
US9674075B1 (en) * | 2014-12-22 | 2017-06-06 | Juniper Networks, Inc. | Multicast only fast re-route for PIM ASM mode |
CN104901893B (zh) * | 2015-06-11 | 2018-05-11 | 新华三技术有限公司 | 组播流量保护方法及装置 |
CN107534608B (zh) * | 2015-06-17 | 2020-05-08 | 华为技术有限公司 | 用于在无线通信网络中处理数据流的方法和装置 |
CN106470162B (zh) * | 2015-08-19 | 2019-06-25 | ***通信集团公司 | 一种业务报文的组播方法及装置 |
US10051022B2 (en) * | 2016-03-30 | 2018-08-14 | Juniper Networks, Inc. | Hot root standby support for multicast |
CN107800547A (zh) * | 2016-09-07 | 2018-03-13 | 华为技术有限公司 | 一种用于处理组播加入消息的方法及其设备 |
US10425458B2 (en) | 2016-10-14 | 2019-09-24 | Cisco Technology, Inc. | Adaptive bit rate streaming with multi-interface reception |
US10735248B2 (en) * | 2018-02-12 | 2020-08-04 | Futurewei Technologies, Inc. | Cloudified N-way routing protection at hyper scale |
CN109189549A (zh) * | 2018-08-01 | 2019-01-11 | 新华三技术有限公司 | 虚拟机迁移方法及装置 |
CN109495320B (zh) * | 2018-12-24 | 2021-12-24 | 新华三技术有限公司 | 一种数据报文的传输方法和装置 |
CN111385213B (zh) * | 2018-12-29 | 2021-10-22 | 华为技术有限公司 | 一种组播转发表项生成方法及装置 |
CN112134776B (zh) * | 2019-06-25 | 2022-08-26 | 华为技术有限公司 | 生成组播转发表项的方法和接入网关 |
CN112822097B (zh) * | 2019-11-15 | 2024-06-18 | 华为技术有限公司 | 报文转发的方法、第一网络设备以及第一设备组 |
US11695685B2 (en) * | 2020-06-16 | 2023-07-04 | Nokia Solutions And Networks Oy | Supporting candidate path selection |
CN114363114B (zh) * | 2020-09-29 | 2023-07-07 | 华为技术有限公司 | 转发流量的方法及设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101094175A (zh) * | 2007-06-14 | 2007-12-26 | 华为技术有限公司 | 一种组播流量保护方法、装置及*** |
JP2008028714A (ja) * | 2006-07-21 | 2008-02-07 | Hitachi Ltd | ネットワークおよびマルチキャスト転送装置 |
US20080267078A1 (en) * | 2007-04-26 | 2008-10-30 | Cisco Technology, Inc. | Multicast fast reroute |
CN101656679A (zh) * | 2009-09-25 | 2010-02-24 | 华为技术有限公司 | 一种组播快速收敛方法、路由器和通信*** |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6751747B2 (en) * | 2000-05-02 | 2004-06-15 | Nortel Networks Limited | System, device, and method for detecting and recovering from failures in a multicast communication system |
US20020150094A1 (en) * | 2000-10-27 | 2002-10-17 | Matthew Cheng | Hierarchical level-based internet protocol multicasting |
US6973024B1 (en) * | 2001-02-28 | 2005-12-06 | Utstarcom, Inc. | Method for modem element switchover using multicast groups |
GB2395629B (en) * | 2002-11-20 | 2006-06-21 | Motorola Inc | Wireless communications systems and methods |
JP4516496B2 (ja) * | 2005-07-27 | 2010-08-04 | 株式会社日立製作所 | マルチキャスト配信方法及びシステム、コンテンツサーバ |
US20070174483A1 (en) * | 2006-01-20 | 2007-07-26 | Raj Alex E | Methods and apparatus for implementing protection for multicast services |
US8004960B2 (en) * | 2006-04-28 | 2011-08-23 | Cisco Technology, Inc. | Method and apparatus for forwarding label distribution protocol multicast traffic during fast reroute |
US8279749B2 (en) * | 2006-11-27 | 2012-10-02 | Cisco Technology, Inc. | Failure protection for P2MP tunnel head-end node |
US7830785B2 (en) * | 2008-01-25 | 2010-11-09 | At&T Labs, Inc. | System and method for restoration in a multimedia IP network |
-
2009
- 2009-09-25 CN CN2009101778349A patent/CN101656679B/zh not_active Expired - Fee Related
-
2010
- 2010-09-17 EP EP10818393A patent/EP2437444A4/en not_active Withdrawn
- 2010-09-17 WO PCT/CN2010/077022 patent/WO2011035699A1/zh active Application Filing
-
2011
- 2011-12-29 US US13/339,402 patent/US20120099422A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008028714A (ja) * | 2006-07-21 | 2008-02-07 | Hitachi Ltd | ネットワークおよびマルチキャスト転送装置 |
US20080267078A1 (en) * | 2007-04-26 | 2008-10-30 | Cisco Technology, Inc. | Multicast fast reroute |
CN101094175A (zh) * | 2007-06-14 | 2007-12-26 | 华为技术有限公司 | 一种组播流量保护方法、装置及*** |
CN101656679A (zh) * | 2009-09-25 | 2010-02-24 | 华为技术有限公司 | 一种组播快速收敛方法、路由器和通信*** |
Non-Patent Citations (1)
Title |
---|
See also references of EP2437444A4 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102315951A (zh) * | 2011-09-19 | 2012-01-11 | 华为技术有限公司 | 一种组播报文的传输方法、相关设备及*** |
EP2571209A1 (en) * | 2011-09-19 | 2013-03-20 | Huawei Technologies Co., Ltd. | Multicast packet transmission method, related device and system |
US9160616B2 (en) | 2011-09-19 | 2015-10-13 | Huawei Technologies Co., Ltd. | Multicast packet transmission method, related device and system |
CN102388568A (zh) * | 2011-09-20 | 2012-03-21 | 华为技术有限公司 | 一种转发方法及转发装置 |
CN102388568B (zh) * | 2011-09-20 | 2014-12-03 | 华为技术有限公司 | 一种转发方法及转发装置 |
Also Published As
Publication number | Publication date |
---|---|
CN101656679B (zh) | 2012-04-04 |
US20120099422A1 (en) | 2012-04-26 |
EP2437444A4 (en) | 2012-08-15 |
CN101656679A (zh) | 2010-02-24 |
EP2437444A1 (en) | 2012-04-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011035699A1 (zh) | 一种组播快速收敛方法、路由器和通信*** | |
US8218429B2 (en) | Method and device for multicast traffic redundancy protection | |
US9509590B2 (en) | Method and apparatus for providing resiliency in multicast networks | |
EP3151488B1 (en) | Multicast only fast re-route over remote loop-free alternate backup path | |
US7839850B2 (en) | Forming equal cost multipath multicast distribution structures | |
US8009671B2 (en) | Multicast method and multicast routing method | |
JP6165850B2 (ja) | ダウンストリーム通知パケットを用いたプロトコル独立マルチキャスト(pim)高速再ルーティング方法論の強化 | |
US20090201803A1 (en) | Multicast fast reroute for network topologies | |
WO2012003743A1 (zh) | 组播流量的转发方法及装置 | |
WO2008151553A1 (fr) | Procédé, dispositif et système pour protéger un trafic à diffusion multiple | |
WO2017028586A1 (zh) | 一种业务报文的组播方法及装置 | |
WO2009000180A1 (fr) | Procédé, appareil et système de protection d'un noeud amont d'un trajet de commutation d'étiquette point à multipoint | |
KR101878085B1 (ko) | 멀티캐스트 고속 보호 스위칭 방법 및 디바이스 | |
WO2010111956A1 (zh) | 一种组播转发路径收敛的方法和*** | |
WO2007082432A1 (fr) | Procédé de réacheminement | |
WO2009146622A1 (zh) | 实现组播的方法、路由器及*** | |
WO2009111958A1 (zh) | 一种组播快速重路由的方法、装置和*** | |
WO2010048812A1 (zh) | 提高组播转发可靠性的方法和装置 | |
CN101163103A (zh) | 一种实现快速重路由的方法 | |
WO2012152134A1 (zh) | 以太网二层组播快速收敛的方法及以太网*** | |
WO2009074057A1 (fr) | Procede de protection de nœud de tete, systeme et dispositif pour le trajet de commutation d'etiquettes point a multipoint | |
WO2012103748A1 (zh) | 一种组播控制方法、路由设备及组播*** | |
WO2012136062A1 (zh) | 组播路径切换方法及路由器 | |
WO2010000172A1 (zh) | 组播保护方法、***、接收端设备和组播源设备 | |
CN118283539A (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: 10818393 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2010818393 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010818393 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |