CN101808004B - Method and system for realizing Anycast-RP mechanism - Google Patents
Method and system for realizing Anycast-RP mechanism Download PDFInfo
- Publication number
- CN101808004B CN101808004B CN201010140592.9A CN201010140592A CN101808004B CN 101808004 B CN101808004 B CN 101808004B CN 201010140592 A CN201010140592 A CN 201010140592A CN 101808004 B CN101808004 B CN 101808004B
- Authority
- CN
- China
- Prior art keywords
- multicast
- rendezvous point
- registration
- multicast source
- sends
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000007246 mechanism Effects 0.000 title claims abstract description 31
- 230000001629 suppression Effects 0.000 claims description 9
- 238000004891 communication Methods 0.000 claims description 7
- 230000002776 aggregation Effects 0.000 claims 6
- 238000004220 aggregation Methods 0.000 claims 6
- 101000604054 Homo sapiens Neuroplastin Proteins 0.000 description 23
- 101000806155 Homo sapiens Short-chain dehydrogenase/reductase 3 Proteins 0.000 description 23
- 102100037857 Short-chain dehydrogenase/reductase 3 Human genes 0.000 description 23
- 238000010586 diagram Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 102100037425 17-beta-hydroxysteroid dehydrogenase 14 Human genes 0.000 description 4
- 101100309766 Arabidopsis thaliana SDR3a gene Proteins 0.000 description 4
- 101100309767 Arabidopsis thaliana SDR3b gene Proteins 0.000 description 4
- 101150072282 HSD17B14 gene Proteins 0.000 description 4
- 230000004083 survival effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000005764 inhibitory process Effects 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 102100027626 Ferric-chelate reductase 1 Human genes 0.000 description 2
- 101000862406 Homo sapiens Ferric-chelate reductase 1 Proteins 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for realizing an Anycast-RP mechanism. The method comprises that a multicast source sends a multicast stream to an SDR; the SDR sends a packaged registration message to an RP; the RP is added with an SPT in the multicast source direction and establishes the SPT from the multicast source to a multicast receiver; the RPT is switched to the SPT and the SDR sends the multicast stream to a UDR by the SPT. The invention also discloses a system for realizing the Anycast-RP mechanism. According to the technical scheme of the invention, the Anycast-RP mechanism is simply realized.
Description
Technical Field
The invention relates to a network protocol multicast technology in the field of data communication, in particular to a method and a system for realizing an anycast rendezvous point mechanism.
Background
In the application field of network data transmission, multicast has high-efficiency bandwidth and the capability of transmitting the same content to a plurality of receiving sites at one time, and the load of a network and a server is reduced. Up to now, the IP multicast technology has been widely applied to value-added services such as video on demand, Internet Protocol Television (IPTV), video conference, distance education, internet radio, and network games. Due to the characteristics of the IP multicast technology, the IP multicast technology has huge development prospect in the field of IP networks.
The sparse mode Independent Multicast Protocol (PIM-SM) means that there is no correlation between Multicast routing and the type of unicast routing Protocol, and the Protocol has independence, usability, efficiency and expandability of natural Protocol, and has become a preferred scheme of current and next generation IP Multicast technology.
Rendezvous Point (RP) is an important concept in PIM-SM, and is a Router named as RP, and a direct connection multicast source Designated Router (DR) is responsible for registering multicast source information to the RP, so as to establish a Shortest Path Tree (SPT) between the RP and the direct connection multicast source DR. The last DR is connected with a multicast receiver and is responsible for initiating and adding a multicast shared Tree (RPT, Rendezvous Point Tree) to the RP direction, so that a multicast distribution Tree between a multicast source and the multicast receiver is established. Therefore, the RP becomes a central link between the multicast source and the multicast receiver and is also a key node for forwarding the multicast traffic in the PIM-SM. In the following, DR of the direct connection multicast source is referred to as SDR, and DR of the direct connection multicast receiver is referred to as UDR.
In standard PIM-SM, each multicast group can only map to a unique one of the active RPs, which brings the following disadvantages: firstly, both a control message and a data message pass through the RP, so that the burden of the RP is increased, and a network bottleneck is formed; secondly, after the active RP fails, RP election needs to be carried out again, and the registration and joining processes are initiated again, so that the convergence of the multicast routing is slow; wherein the active RP is a final elected RP of the plurality of RPs; thirdly, single RP has poor reliability. In order to enhance the reliability of the RP in the PIM-SM and share the multicast flow in the network, a plurality of RPs can be selected to operate an Anycast-RP mechanism on the backbone network so as to achieve the purposes of redundant backup and load sharing. An Anycast Rendezvous Point (Anycast-RP) mechanism refers to that a certain unicast Address is selected in a PIM-SM domain to serve as an RP Address (RPA), RP information can be dynamically issued through static configuration or PIM-SM, and the RP information comprises the priority of the RP and the RPA of the RP; and selecting a group of nodes in the PIM-SM domain as RP, wherein the group of nodes is called an Anycast-RP set, and all members in the Anycast-RP set use an address as a local Loopback interface (Loopback) of the RPA and issue the Loopback interface to the unicast routing system. Each member of the Anycast-RP repertoire is referred to as an Anycast-RP member. Multicast source information is shared among Anycast-RP members through a certain means, and each Anycast-RP member only takes the central role of the surrounding area.
In the prior art, a Multicast Source Discovery Protocol (MSDP) peer is established between Anycast-RP members, and Source-Active (SA) messages are used to share Multicast Source information, as shown in fig. 1, the working flow and functions of an Anycast-RP mechanism in PIM-SM are as follows:
1. RP1 and RP2 are MSDP peers of each other and enable the same IP address as the RPA.
2. The designated router SDR1 connected to the multicast source S1 selects the closer rendezvous point RP1 to register.
3. The Anycast-RP member RP1 advertises the multicast source information to another member RP2 in the Anycast-RP set through the MSDP.
4. The designated router UDR2 connected with the multicast receiver USER2 selects a closer rendezvous point RP2 to join the SPT, and the RP2 initiates joining towards the designated router SDR1 to create the RPT.
5. A multicast forwarding path is created from the designated router SDR1 to the rendezvous point RP1 and then to the designated router UDR 2.
6. The flow of the multicast receiver USER1 receiving the multicast source S2 is the same as the above steps.
7. If the rendezvous point RP1 fails or a unicast path from a designated router SDR1 to RP1 fails, waiting for convergence of the unicast path, the SDR1 reselects the RP2 as the rendezvous point; similarly, if the rendezvous point RP2 fails or the unicast path from the designated router SDR2 to RP2 fails, after waiting for the unicast route to converge, the SDR2 reselects the RP1 as the rendezvous point, thereby realizing the fast convergence of the multicast forwarding path.
In the method for realizing the Anycast-RP mechanism in the prior art, MSDP needs to be operated on all Anycast-RP member nodes, so that a large number of MSDP peers among the Anycast-RP member nodes need to be maintained; because the MSDP peer is connected to multiple PIM-SM domains to discover multicast source information in other PIM-SM domains, there is interaction between the PIM-SM domain and multiple MSDP peers, thereby increasing the complexity of the Anycast-RP mechanism. In addition, in the research and planning of next generation networks, the IP multicast architecture has abandoned MSDP. Therefore, whether to optimize the current network or perfect the IP multicast routing protocol in the next generation network, how to reserve the Anycast-RP mechanism under the condition of removing MSDP needs to be considered.
Disclosure of Invention
In view of this, the main objective of the present invention is to provide a method and a system for implementing Anycast rendezvous point mechanism, which simply implement the Anycast-RP mechanism.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for realizing an anycast rendezvous point mechanism, which comprises the following steps:
the multicast source sends the multicast stream to a designated router (SDR) directly connected with the multicast source, and the SDR sends the encapsulated registration message to a Rendezvous Point (RP);
adding the RP into a Shortest Path Tree (SPT) in the multicast source direction, and establishing the SPT from the multicast source to the multicast receiver;
and switching the multicast sharing tree (RPT) into the SPT, and sending the multicast stream to a specified router (UDR) of a direct connection multicast receiver by the SDR through the SPT.
In the above method, the method further comprises:
a Rendezvous Point Address (RPA) and a Rendezvous Point Communication Address (RPCA) are configured on each Anycast rendezvous point (Anycast-RP) member.
In the above method, the configuring of RPA and RPCA on each Anycast-RP member specifically includes:
the same RPA is configured on each Anycast-RP member, one RPCA is configured on each Anycast-RP member, and the RPCAs of other Anycast-RP members are stored on each RP.
In the above method, the sending of the multicast stream to the SDR by the multicast source, and the sending of the encapsulated registration packet to the RP by the SDR specifically includes:
the multicast source sends multicast stream to SDR, one RP is selected out according to the priority of the candidate RP and the RPA of the RP, and the SDR sends a registration message which encapsulates the multicast data message to the output interface direction of the RP by searching the unicast route with the destination address of the RPA.
In the above method, the adding, by the RP, the SPT in the multicast source direction, and the establishing of the SPT from the multicast source to the multicast recipient specifically includes:
the RP adds the SPT in the multicast source direction, sends a registration stop message to the SDR, and forwards the registration message to all other Anycast-RP members; SDR stops sending registration message, and sends empty registration message to RP after register inhibition timer is overtime; and other Anycast-RP members send registration stop messages to the RP and join the SPT in the multicast source direction.
In the above method, the SDR further includes, after stopping sending the registration packet and after the registration suppression timer is overtime, sending an empty registration packet to the RP:
the RP sends a registration stop message to the SDR and forwards an empty registration message to all other Anycast-RP members; and other RPs in the Anycast-RP member send registration stop messages to the RP sending the empty registration messages.
The invention also provides a system for realizing the anycast rendezvous point mechanism, which comprises the following components: SDR, RP, a switching module and UDR, wherein,
SDR, which is used to receive multicast flow sent by multicast source and send the packaged register message to RP; sending the multicast stream to the UDR through the SPT;
RP, used for receiving the registration message of encapsulation, and join SPT of the multicast source direction, set up SPT from multicast source to multicast receiver;
the switching module is used for switching the RPT into the SPT;
and the UDR is used for receiving the multicast stream sent by the SDR through the SPT.
In the above system, the system further comprises:
a configuration module for configuring RPA and RPCA on each Anycast-RP member.
The method and the system for realizing the Anycast rendezvous point mechanism simply realize the Anycast-RP mechanism, redundant backup of RP, load sharing of multicast flow and rapid convergence of a multicast forwarding path on the basis of removing MSDP in the prior art, and further improve an IP multicast routing protocol and the current network in a next generation network.
Drawings
Fig. 1 is a schematic diagram of a typical application networking in the prior art for implementing an anycast rendezvous point mechanism;
FIG. 2 is a flow chart illustrating a method for implementing an anycast rendezvous point mechanism according to the present invention;
FIG. 3 is a flowchart illustrating a method for registering and joining SPT in the multicast source direction by RP according to the present invention;
FIG. 4 is a schematic networking diagram illustrating an embodiment of a method for implementing an anycast rendezvous point mechanism according to the present invention;
FIG. 5 is a flowchart illustrating a first embodiment of a method for implementing an anycast rendezvous point mechanism according to the present invention;
fig. 6 is a schematic structural diagram of a system for implementing an anycast rendezvous point mechanism according to the present invention.
Detailed Description
The invention provides a method and a system for realizing an anycast rendezvous point mechanism in a PIM-SM domain, and the basic idea of the invention is as follows: the multicast source sends the multicast stream to the SDR, and the SDR sends the encapsulated registration message to the RP; the RP adds the SPT in the multicast source direction and establishes the SPT from the multicast source to the multicast receiver; and switching the RPT into the SPT, and sending the multicast stream to the UDR by the SDR through the SPT.
The invention is further described in detail below with reference to the drawings and the specific embodiments.
Fig. 2 is a flowchart illustrating a method for implementing an anycast rendezvous point mechanism according to the present invention, and as shown in fig. 2, the method includes the following steps:
step 201, configuring RPA and RPCA on each Anycast-RP member;
specifically, the same RPA is configured on each Anycast-RP member in the PIM-SM domain, a Rendezvous Point Contact Address (RPCA) is configured on each Anycast-RP member, and RPCAs of other Anycast-RP members are stored on each RP, so that the Anycast-RP members can know the existence of each other and the RPCAs of other Anycast-RP members, and can communicate with each other; in this embodiment, the devices that enable the Anycast-RP are all referred to as Anycast-RP members;
step 202, the multicast source sends the multicast stream to SDR, SDR sends the packaged register message to RP;
specifically, a multicast source sends a multicast stream to an SDR, the SDR elects an RP according to the priority of a candidate RP and the RPA of the RP, the commonly elected RP is the closest RP to the SDR, the distance refers to a physical distance, the address of the RP is the RPA, the SDR sends a registration message encapsulating a multicast data message to the direction of an outgoing interface of the RP by searching a unicast route with the destination address of the RPA, the source address of the registration message is the address of the SDR, and the destination address is the RPA;
step 203, the RP adds the SPT in the multicast source direction and establishes the SPT from the multicast source to the multicast receiver;
step 204, switching the RPT to the SPT, and sending the multicast stream to the UDR by the SDR through the SPT;
specifically, in the above step, an SPT from the multicast source to the multicast receiver is already formed, so that the forwarding path from the multicast stream to the UDR along the RP and the RPT is not the optimal forwarding path, the RPT needs to be switched to the SPT, a shortest path forwarding tree from the multicast source to the multicast receiver is formed after switching, and the SDR sends the multicast stream to the UDR through the SPT; after the SPT from the Multicast source to the Multicast receiver is established, the RPT and the SPT exist at the same time, so that the last hop in the Multicast routing table utilizes Protocol Independent Multicast (PIM) to cut off the RPT, and the original Multicast stream transmitted in the RPT can be automatically switched to the SPT for transmission;
switching from RPT to SPT is only a change of unicast path, only a change of processing logic on RP is caused, and no change of logic on SDR and UDR is caused.
Fig. 3 is a specific method for implementing step 203 in fig. 2, which is a flowchart illustrating a method for an RP to join an SPT in a multicast source direction and establish an SPT from a multicast source to a multicast recipient according to the present invention, and as shown in fig. 3, the method includes the following steps:
step 301, adding SPT in multicast source direction into RP, sending registration stop message to SDR, and forwarding registration message to all other Anycast-RP members;
specifically, the RP decapsulates the registration message after receiving the encapsulated registration message, sends the inner layer multicast data message to the RPT, initiates an SPT joining in the multicast source direction, sends a registration stop message to the SDR after the RP joins in the SPT, and forwards the registration message to all other Anycast-RP members;
step 302, SDR stops sending registration message, and sends empty registration message to RP after register suppression timer is overtime; other Anycast-RP members send registration stop messages to the RP and join the SPT in the multicast source direction;
specifically, after receiving the registration stop message, the SDR refreshes a registration inhibition timer, stops sending the registration message, and sends an empty registration message to the RP when the registration inhibition timer is overtime; other RPs in the Anycast-RP member decapsulate the registration message after receiving the registration message from the RP, send the inner layer multicast data message to the RPT, initiate the SPT joining the multicast source direction, and send the registration stop message to the RP sending the registration message after the RP joins the SPT;
step 303, the RP sends a registration stop message to the SDR, and forwards an empty registration message to all other Anycast-RP members;
specifically, after receiving an empty registration message sent by the SDR, the RP refreshes (S, G) the time of the survival time timer, sends a registration stop message to the SDR, copies the empty registration message, and sends the copied empty registration message to other RPs in Anycast-RP members; (S, G) represents a multicast routing table of a multicast group G and a multicast source S, and comprises a multicast source address, a multicast group address, an input interface, an output interface list, a timer and the like; the (S, G) survival time timer is used for updating the multicast group routing table, and the multicast group routing table is updated every time the (S, G) survival time timer is refreshed;
after receiving the registration stop message sent by the RP, the SDR refreshes the registration suppression timer again, and after the timer is overtime, the SDR continues to send an empty registration message to the RP;
304, other RPs in the Anycast-RP member send register stop messages to the RP sending the empty register messages;
specifically, after receiving the empty registration message from the RP, other RPs in the Anycast-RP member send a registration stop message to the RP that sends the empty registration message, and refresh (S, G) the time of the survival time timer.
Fig. 4 is a networking diagram of an embodiment of the method for implementing an Anycast rendezvous point mechanism according to the present invention, as shown in fig. 4, RP1 and RP2 belong to RPs of non-direct-connected sources DR, RP3 belongs to RPs of direct-connected sources DR, SDR1 is directly connected to multicast sources S1, UDR1 is directly connected to multicast receivers USER1, SDR1 and UDR1 are configured to have a closest unicast distance relationship with RP1, UDR2 is directly connected to multicast receivers USER2, UDR2 is configured to have a closest unicast distance relationship with RP2, RP3 is directly connected to multicast sources S3, and RP3 are simultaneously used as SDR3, and hereinafter, a method for implementing an Anycast-RP mechanism is respectively described with respect to an RP of a non-direct-connected source DR and an RP of a direct-connected source DR.
Fig. 5 is a flowchart of a first embodiment of a method for implementing an anycast rendezvous point mechanism according to the present invention, which is described by taking an RP1 in a non-direct-connection-source DR device as an example, and as shown in fig. 5, the method includes the following steps:
step 501, configuring RPA and RPCA;
specifically, the same RPA is configured on RP1, RP2 and RP3, and RPCA1, RPCA2 and RPCA3 are configured on RP1, RP2 and RP3 respectively, each RP stores RPCA of other RPs, for example, RP1 stores RPCA of RP2 and RP3, so that RP1 knows existence of RP2 and RP3 and knows RPCA of RP2 and RP3, and RP1 can communicate with RP2 and RP3 by using RPCA;
step 502, establishing an RPT from the RP to the UDR;
specifically, a multicast receiver USER1 sends a request for joining a multicast group G to UDR1, RP1 is elected according to a configured unicast distance relationship, the priority of a candidate RP and an RPCA of the RP, RP1 is the closest RP to SDR1, UDR1 initiates PIM joining to an outgoing interface direction of RP1, the RP1 is reached through a hop-by-hop joining mode of the PIM, and an RPT from RP1 to UDR1 is established; similarly, the multicast receiver USER2 first sends a request to UDR2 to join the multicast group G, and then establishes an RPT from RP2 to UDR 2;
step 503, the multicast source S1 sends the data of the multicast group G to the SDR1, and the SDR1 sends a registration message to the RP 1;
specifically, the multicast source S1 sends the data of the multicast group G to the SDR1, the SDR1 sends a PIM registration packet encapsulating the multicast data packet to the output interface direction of the RP1, where the source address of the registration packet is SDR1 and the destination address is RPA;
step 504, the multicast data message obtained by decapsulating the registration message is forwarded to the RPT, the SPT in the multicast source direction is added, and the RP1 sends a registration stop message to the SDR 1; forwarding the registration message to RP2 and RP 3;
specifically, after the registration message reaches the RP1, because the source address of the registration message is not the RPCA of other RPs, the RP1 determines that the registration message is from SDR, and the RP1 decapsulates the multicast data message in the registration message and forwards the multicast data message to the established RPT, and initiates an SPT joining the multicast source S1; the RP1 sends a registration stop message to the SDR1, and then proceeds to step 509; because the RP1 stores RPCAs of other RPs, the RP1 copies the registration message and then forwards the registration message to the RP2 and the RP3, the source address of the forwarded registration message is RPCA1, the destination addresses are RPCA2 and RPCA3, the RP2 executes step 505 when receiving the registration message, and the RP3 executes step 506 when receiving the registration message;
505, decapsulating the registration message to obtain a multicast data message, forwarding the multicast data message to the RPT, and adding the SPT in the multicast source direction;
specifically, after the registration message reaches RP2, because the source address of the registration message is the RPCA of RP1, RP2 determines that the message is from RP1, and RP2 decapsulates the multicast data message in the registration message and forwards the multicast data message to the established RPT, and sends a registration stop message to RP1, and initiates an SPT joining the multicast source in the direction of S1;
step 506, the RP3 creates a routing table, discards the registration message and sends a registration stop message to the RP 1;
specifically, after the registration packet reaches RP3, no RPT is established on RP3 in step 502, so RP3 only creates an (S, G) routing table for the RP receiving the packet to quickly join the SPT in the multicast source S1 direction, RP3 discards the registration packet, and sends a registration stop packet to RP 1;
step 507, the RP1 discards the registration stop message;
specifically, after receiving the registration stop message sent by RP2 and RP3, RP1 discards the registration stop message because RP1 is not a direct connection source device and does not have a maintenance registration state machine;
step 508, switching from RPT to SPT, and the data of the multicast group G reaches UDR through SPT;
specifically, in the above steps, the SPT from the multicast source S1 to the multicast receiver UDR1 has been formed, so that the RPT is not an optimal forwarding path, the RPT needs to be switched to the SPT, a shortest path forwarding tree from the multicast source to the multicast receiver is formed after the switching, and the SDR sends the data of the multicast group G to the UDR through the SPT;
step 509, after receiving the registration stop message, the SDR1 stops sending the registration message;
specifically, after receiving the registration stop message sent by the RP1, the SDR1 refreshes the registration suppression timer to stop sending the registration message, and after the timer times out, the SDR1 sends an empty registration message to the RP 1;
step 510, after receiving the empty registration message of the SDR1, the RP1 sends a registration stop message to the SDR1, and forwards the empty registration message to the RP2 and the RP 3;
specifically, after receiving the empty registration message of the SDR1, the RP1 refreshes the time-to-live timer of the related multicast routing forwarding table, sends a registration stop message to the SDR1, and forwards the empty registration message to the RP2 and the RP 3; after receiving the registration stop message sent by the RP1, the SDR1 refreshes the registration suppression timer again, and after the timer is overtime, the SDR1 continues to send an empty registration message to the RP 1;
step 511, the RP2 and RP3 refresh the time-to-live timer and send a registration stop message to the RP 1;
specifically, after receiving the empty registration message from RP1, RP2 and RP3 refresh the time-to-live timer of the relevant multicast routing forwarding table, and send a registration stop message to RP 1.
The direct connection source DR represented by RP3 differs from the RP1 processing method only in that when the multicast source S3 sends the data of the multicast group G to the SDR3, because the SDR3 and the RP3 are at the same position, the SDR3 directly sends the registration packet encapsulating the multicast data packet to the RP1 and the RP2, and does not need to forward the registration packet through the RP 3.
Fig. 6 is a schematic structural diagram of the system for implementing an anycast rendezvous point mechanism according to the present invention, and as shown in fig. 6, the system includes: SDR 31, RP 32, switching module 33, UDR 34; wherein,
a switching module 33, configured to switch the RPT to the SPT;
the UDR34 is used for receiving the multicast stream sent by the SDR32 through the SPT;
the system further comprises:
a configuration module 35 for configuring RPA and RPCA on each Anycast-RP member.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (6)
1. A method for implementing an anycast rendezvous point mechanism, the method comprising:
the multicast source sends the multicast stream to a designated router directly connected with the multicast source, and the designated router directly connected with the multicast source sends the encapsulated registration message to the rendezvous point;
the convergent point is added into the shortest path tree in the multicast source direction, and the shortest path tree from the multicast source to the multicast receiver is established;
the multicast sharing tree is switched into a shortest path tree, and a designated router of a direct connection multicast source sends the multicast stream to a designated router of a direct connection multicast receiver through the shortest path tree; wherein,
the convergent point is added into the shortest path tree in the multicast source direction, and the shortest path tree from the multicast source to the multicast receiver is established as follows:
the rendezvous point joins the shortest path tree in the multicast source direction, sends a registration stop message to a designated router directly connected with the multicast source, and forwards the registration message to all other members of the multicast rendezvous point; the designated router directly connected with the multicast source stops sending the registration message, and sends an empty registration message to the rendezvous point after the registration suppression timer is overtime, and other multicast rendezvous point members send the registration stop message to the rendezvous point and join the shortest path tree in the multicast source direction; wherein,
the method comprises the steps that the designated router of the direct connection multicast source stops sending registration messages, and after a registration suppression timer is overtime, empty registration messages are sent to a rendezvous point, wherein the rendezvous point sends the registration stop messages to the designated router of the direct connection multicast source, and the empty registration messages are forwarded to all other multicast rendezvous point members; and other aggregation points in the multicast aggregation point members send registration stop messages to the aggregation point which sends the empty registration message.
2. The method of claim 1, further comprising:
a rendezvous point address and a rendezvous point communication address are configured on each anycast rendezvous point member.
3. The method of claim 2, wherein the configuring of the rendezvous point address and the rendezvous point communication address on each anycast rendezvous point member is specifically:
the same rendezvous point address is configured on each anycast rendezvous point member, a rendezvous point communication address is configured on each anycast rendezvous point member, and the rendezvous point communication addresses of other anycast rendezvous point members are stored on each rendezvous point.
4. The method according to claim 1, wherein the sending, by the multicast source, the multicast stream to the designated router of the direct connection multicast source, and the sending, by the designated router of the direct connection multicast source, the encapsulated registration packet to the rendezvous point specifically includes:
the multicast source sends the multicast stream to a designated router directly connected with the multicast source, a rendezvous point is selected according to the priority of the candidate rendezvous point and the rendezvous point address of the rendezvous point, and the designated router directly connected with the multicast source sends a registration message encapsulating the multicast data message to the direction of an outgoing interface of the rendezvous point by searching a unicast route with the destination address as the rendezvous point address.
5. A system for implementing an anycast rendezvous point mechanism, the system comprising: a designated router of a direct connection multicast source, a rendezvous point, a switching module, a designated router of a direct connection multicast receiver, wherein,
the router directly connected with the multicast source is used for receiving the multicast stream sent by the multicast source and sending the encapsulated registration message to the rendezvous point; sending the multicast stream to a designated router of a direct connection multicast receiver through a shortest path tree;
the convergent point is used for receiving the encapsulated registration message, adding the shortest path tree in the multicast source direction and establishing the shortest path tree from the multicast source to the multicast receiver;
the switching module is used for switching the multicast sharing tree into a shortest path tree;
the designated router of the direct connection multicast receiver is used for receiving the multicast stream sent by the designated router through the shortest path tree; wherein,
the convergent point joins the shortest path tree in the multicast source direction, and the shortest path tree from the multicast source to the multicast receiver is established as follows:
the rendezvous point joins the shortest path tree in the multicast source direction, sends a registration stop message to a designated router directly connected with the multicast source, and forwards the registration message to all other members of the multicast rendezvous point; the designated router directly connected with the multicast source stops sending the registration message, and sends an empty registration message to the rendezvous point after the registration suppression timer is overtime, and other multicast rendezvous point members send the registration stop message to the rendezvous point and join the shortest path tree in the multicast source direction; wherein,
the method comprises the steps that the designated router of the direct connection multicast source stops sending registration messages, and after a registration suppression timer is overtime, empty registration messages are sent to a rendezvous point, wherein the rendezvous point sends the registration stop messages to the designated router of the direct connection multicast source, and the empty registration messages are forwarded to all other multicast rendezvous point members; and other aggregation points in the multicast aggregation point members send registration stop messages to the aggregation point which sends the empty registration message.
6. The system of claim 5, further comprising:
and the configuration module is used for configuring the convergent point address and the convergent point communication address on each anycast convergent point member.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010140592.9A CN101808004B (en) | 2010-03-23 | 2010-03-23 | Method and system for realizing Anycast-RP mechanism |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010140592.9A CN101808004B (en) | 2010-03-23 | 2010-03-23 | Method and system for realizing Anycast-RP mechanism |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101808004A CN101808004A (en) | 2010-08-18 |
| CN101808004B true CN101808004B (en) | 2014-04-30 |
Family
ID=42609625
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010140592.9A Expired - Fee Related CN101808004B (en) | 2010-03-23 | 2010-03-23 | Method and system for realizing Anycast-RP mechanism |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101808004B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101951344B (en) * | 2010-09-25 | 2012-09-05 | 北京星网锐捷网络技术有限公司 | Multicast path switching method and device and network equipment |
| CN103503370A (en) * | 2011-10-26 | 2014-01-08 | 华为技术有限公司 | Load decreasing method and apparatus |
| CN102316124B (en) * | 2011-10-28 | 2015-05-20 | 杭州华三通信技术有限公司 | Registration method and equipment for terminal equipment |
| WO2014205786A1 (en) * | 2013-06-28 | 2014-12-31 | 华为技术有限公司 | Anycast service registration and implementation method and apparatus, and switching device and system |
| CN103401788B (en) * | 2013-07-30 | 2016-12-07 | 杭州华三通信技术有限公司 | A kind of SPT method for building up and equipment |
| CN103516548B (en) * | 2013-09-26 | 2017-02-15 | 杭州华三通信技术有限公司 | RP equipment management method and equipment |
| CN103634219B (en) * | 2013-11-27 | 2017-03-08 | 杭州华三通信技术有限公司 | A kind of maintaining method of Anycast Rendezvous Point Anycast RP and device |
| CN104202240A (en) * | 2014-07-30 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Method of accelerating RP (Rendezvous Point) switchover |
| CN107342938B (en) * | 2016-04-29 | 2020-11-03 | 华为技术有限公司 | Method for switching from RPT to SPT and PE equipment |
| CN107547350B (en) * | 2017-08-02 | 2020-09-08 | 新华三技术有限公司 | Traffic processing method and device |
| CN108234325B (en) * | 2018-01-10 | 2021-09-07 | 北京知道创宇信息技术股份有限公司 | System based on IP anycast and message forwarding method |
| CN113489642B (en) * | 2021-07-04 | 2023-05-12 | 芯河半导体科技(无锡)有限公司 | PIM-SM source registration optimization method |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1921490A (en) * | 2006-09-14 | 2007-02-28 | 杭州华为三康技术有限公司 | Method and device for configuring protocol independent multicast rarefaction mode protocol confluence |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| ES2381175T3 (en) * | 2007-06-26 | 2012-05-23 | Media Patents, S. L. | Device for managing multicast groups |
-
2010
- 2010-03-23 CN CN201010140592.9A patent/CN101808004B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1921490A (en) * | 2006-09-14 | 2007-02-28 | 杭州华为三康技术有限公司 | Method and device for configuring protocol independent multicast rarefaction mode protocol confluence |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101808004A (en) | 2010-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101808004B (en) | Method and system for realizing Anycast-RP mechanism | |
| US10476793B2 (en) | Multicast flow overlay using registration over a reliable transport | |
| US20210058260A1 (en) | Multicast Data Transmission Method, Related Apparatus, and System | |
| US9871718B2 (en) | Method and device for registering multicast source and establishing multicast path | |
| US7626984B2 (en) | Method and apparatus for providing congruent multicast and unicast routing | |
| US9838303B2 (en) | PIM source discovery by last hop router | |
| US9660898B2 (en) | Enhanced protocol independent multicast source registration over a reliable transport | |
| US8848609B2 (en) | Forwarding internet protocol version 6 link-local multicast to support roaming of wireless mobile client devices | |
| CN102137000B (en) | Method, device and system for establishing switching multicast distribution tree | |
| JP2002217952A (en) | Small group multicast support method in mobile ip | |
| WO2018214809A1 (en) | Message transmission method and device, and storage medium | |
| WO2010139115A1 (en) | Method and device for multiple rendezvous points processing multicast services of mobile multicast source jointly | |
| US9008118B2 (en) | Multicast data delivery over mixed multicast and non-multicast networks | |
| CN113014496A (en) | Central control-based PIM-SSM multicast label routing method | |
| US20230291682A1 (en) | Method and device for processing data packet, storage medium, and electronic device | |
| CN110999230B (en) | Method, network equipment and system for transmitting multicast message | |
| US9548887B2 (en) | Proactive creation of multicast state in an overlay transport network to achieve fast convergence on failover | |
| CN115102806B (en) | Multicast data transmission method, device, system and storage medium | |
| EP3907940B1 (en) | Ingress replication procedures to facilitate migration to segment routing technology in a computer network | |
| KR101038811B1 (en) | Method of connection-oriented and connectionless transferring frame by using dynamic address combining technology in interconnected bridge network | |
| CN108512762B (en) | Multicast implementation method and device | |
| JP2005252503A (en) | Network, router apparatus, and multicast transfer method used for them | |
| CN116743519A (en) | Method and device for discovering root node | |
| CN113810285A (en) | Multicast source discovery protocol MSDP loop avoidance | |
| WO2019161928A1 (en) | Methods, nodes and system for a multicast service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140430 Termination date: 20190323 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |