CN103516616A - Transmission method and equipment for SA messages - Google Patents
Transmission method and equipment for SA messages Download PDFInfo
- Publication number
- CN103516616A CN103516616A CN201310493597.3A CN201310493597A CN103516616A CN 103516616 A CN103516616 A CN 103516616A CN 201310493597 A CN201310493597 A CN 201310493597A CN 103516616 A CN103516616 A CN 103516616A
- Authority
- CN
- China
- Prior art keywords
- peer
- msdp
- message
- address
- list
- 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.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a transmission method and transmission equipment for SA (Source Active) messages. The method comprises the following steps: an MSDP (Multicast Source Discovery Protocol) peer receives pruning messages of other MSDP peers and corresponding relations between RP (Rendezvous Point) addresses carried in the pruning messages and other MSDP peers are recorded in a pruning receiving list; when the MSDP peer receives the SA messages, the SA messages are subjected to RPF (Reverse Path Forwarding) checking; if RPF checking is successful, RP addresses carried in the SA messages are utilized to inquire the pruning receiving list; if the MSDP peers corresponding to the RP addresses carried in the SA messages are recorded in the pruning receiving list, the SA messages are not transmitted to the MSDP peers corresponding to the RP addresses. In the embodiment of the invention, each MSDP peer can avoid receiving a great amount of redundancy SA messages, and processing performance of each MSDP peer can be improved.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of transmission method and equipment of SA message.
Background technology
MSDP(Multicast Source Discovery Protocol, Multicast Source Discovery Protocol) be in order to solve a plurality of PIM-SM(Protocol Independent Multicast Sparse Mode, Protocol independent multicast-sparse mode) interconnection between territory and the inter-domain multicast solution developed, for finding the information about multicast source in other pim-sm domain.Concrete, because multicast source is only to the RP(RendezvousPoint in this pim-sm domain, convergent point) registration, and the information about multicast source of each pim-sm domain is isolated mutually, therefore RP only knows the information about multicast source in this pim-sm domain, can only in this pim-sm domain, set up multicast distribution tree, the multicast data delivery that multicast source in this pim-sm domain is sent is to local user.If there is a kind of mechanism, information about multicast source in other pim-sm domain is passed to the RP in this pim-sm domain, the RP in this pim-sm domain just can initiate adition process and set up multicast distribution tree to the multicast source in other pim-sm domain, thereby realizes the cross-domain transmission of multicast packet.Based on this imagination, MSDP sets up MSDP peer relationship by choose suitable router in network, to be communicated with the RP in each pim-sm domain, and by mutual SA(Source Active between each MSDP peer-to-peer, information source is effective) message shares information about multicast source.
As shown in Figure 1, for transmit the networking schematic diagram of information about multicast source between a plurality of pim-sm domains by MSDP, Router A(router-A) periodically by SA message, the information about multicast source in PIM-SM1 territory is noticed to all MSDP peer-to-peers, by SA message, the information about multicast source in PIM-SM1 territory is noticed to Router B and Router C.Router B, after the SA message of receiving from Router A, notices SA message to all MSDP peer-to-peers, is about to SA message and notices the C to Router, but SA message is not noticed to the A to Router.Router C, after the SA message of receiving from Router A, notices SA message to all MSDP peer-to-peers, is about to SA message and notices the B to Router, but SA message is not noticed to the A to Router.
Obviously, when there is a large amount of MSDP peer-to-peers, existing processing mode can cause each MSDP peer-to-peer all to receive the SA message of bulk redundancy.For example, the SA message that carries the information about multicast source in PIM-SM1 territory from Router A that Router B receives is effective SA message, and the SA message that carries the information about multicast source in PIM-SM1 territory of the MSDP peer-to-peer from other of receiving is the SA message of redundancy.Further, each SA message that MSDP peer-to-peer need to be received self is processed, and when each SA message that self is received is processed, can cause the handling property of MSDP peer-to-peer to decline.
Summary of the invention
The embodiment of the present invention provides a kind of transmission method and equipment of SA message, to avoid each MSDP peer-to-peer to receive the SA message of bulk redundancy, improves the handling property of each MSDP peer-to-peer.
In order to achieve the above object, the embodiment of the present invention provides the transmission method of the effective SA message of a kind of information source, and the method is applied to comprise that in the network of a plurality of Multicast Source Discovery Protocol MSDP peer-to-peers, the method comprises the following steps:
MSDP peer-to-peer receives the prune packet from other MSDP peer-to-peer, has carried convergent point RP address in described prune packet; Described MSDP peer-to-peer, after receiving described prune packet, receives in list and records the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning;
Described MSDP peer-to-peer, when receiving SA message, carries out inverse path to described SA message and forwards rpf check; If rpf check success, utilizes beta pruning described in the RP address lookup carrying in described SA message to receive list; If described beta pruning receives in list and records MSDP peer-to-peer corresponding to RP address carrying in described SA message, to GaiRP address, corresponding MSDP peer-to-peer does not forward described SA message.
Described method also comprises: described MSDP peer-to-peer forwards described SA message to other MSDP peer-to-peer outside MSDP peer-to-peer corresponding to GaiRP address.
After described MSDP peer-to-peer carries out inverse path forwarding rpf check to described SA message, described method also comprises:
If rpf check failure, described MSDP peer-to-peer abandons described SA message, and the RP address of carrying record described SA message in beta pruning transmission list in and the corresponding relation between the MSDP peer-to-peer of the described SA message of transmission, and send prune packet to the MSDP peer-to-peer that sends described SA message, in this prune packet, carry the RP address of carrying in described SA message; By the MSDP peer-to-peer that sends described SA message, after the prune packet of receiving from described MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in recording described SA message in list and the corresponding relation between described MSDP peer-to-peer.
After corresponding relation between the RP address that described MSDP peer-to-peer carries record described SA message in beta pruning transmission list in and the MSDP peer-to-peer that sends described SA message, described method also comprises: it is while sending the MSDP peer-to-peer of described SA message that described MSDP peer-to-peer detects the rpf check opposite end corresponding to RP address of carrying in described SA message, from beta pruning transmission list, delete the corresponding relation between the RP address of carrying in described SA message and the MSDP peer-to-peer that sends described SA message, and send graft packet to the MSDP peer-to-peer that sends described SA message; By the MSDP peer-to-peer that sends described SA message, after the graft packet of receiving from described MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in deleting described SA message in list and the corresponding relation between described MSDP peer-to-peer;
After described MSDP peer-to-peer records the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning reception list, described method also comprises: described MSDP peer-to-peer receives the graft packet from described other MSDP peer-to-peer, carries LiaoRP address in described graft packet; Described MSDP peer-to-peer, after receiving described graft packet, receives the RP address of carrying in deleting described graft packet in list and the corresponding relation between described other MSDP peer-to-peer in described beta pruning.
Different MSDP peer-to-peers is positioned at identical Protocol independent multicast-sparse mode pim-sm domain; Or different MSDP peer-to-peers are positioned at different pim-sm domains.
The embodiment of the present invention provides a kind of Multicast Source Discovery Protocol MSDP peer-to-peer, is applied in the network that comprises a plurality of MSDP peer-to-peers, and described MSDP peer-to-peer specifically comprises:
Logging modle, for receiving the prune packet from other MSDP peer-to-peer, has carried convergent point RP address in described prune packet; And after receiving described prune packet, in beta pruning, receive in list and record the corresponding relation between described RP address and described other MSDP peer-to-peer;
Detection module, for when receiving the effective SA message of information source, carries out inverse path to described SA message and forwards rpf check; And in rpf check when success of described SA message, utilize beta pruning described in the RP address lookup carrying in described SA message to receive list;
Processing module, while recording MSDP peer-to-peer corresponding to the RP address of carrying in described SA message for receive list when described beta pruning, to GaiRP address, corresponding MSDP peer-to-peer does not forward described SA message.
Described processing module, also forwards described SA message for other MSDP peer-to-peer outside MSDP peer-to-peer corresponding to GaiRP address.
Described logging modle, also for after described SA message is carried out to rpf check, in rpf check when failure of described SA message, in beta pruning, send the corresponding relation between the MSDP peer-to-peer of the RP address of carrying in recording described SA message in list and the described SA message of transmission;
Described processing module, also, for after described SA message is carried out to rpf check, when the rpf check failure of described SA message, abandon described SA message, and send prune packet to the MSDP peer-to-peer that sends described SA message, in this prune packet, carry the RP address of carrying in described SA message; By the MSDP peer-to-peer that sends described SA message, after receiving prune packet, in beta pruning, receive the RP address of carrying in recording described SA message in list and the corresponding relation between this MSDP peer-to-peer.
Described processing module, also for after the RP address and the corresponding relation between the MSDP peer-to-peer of the described SA message of transmission of carrying in described SA message is recorded in beta pruning transmission list, the rpf check opposite end corresponding to RP address of carrying in described SA message being detected is while sending the MSDP peer-to-peer of described SA message, from beta pruning transmission list, delete the corresponding relation between the RP address of carrying in described SA message and the MSDP peer-to-peer that sends described SA message, and send graft packet to the MSDP peer-to-peer that sends described SA message; By the MSDP peer-to-peer that sends described SA message, after the graft packet of receiving from this MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in deleting described SA message in list and the corresponding relation between this MSDP peer-to-peer;
Record the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning reception list after, receive the graft packet from described other MSDP peer-to-peer, in described graft packet, carry LiaoRP address; After receiving described graft packet, in described beta pruning, receive the RP address of carrying in deleting described graft packet in list and the corresponding relation between described other MSDP peer-to-peer.
Different MSDP peer-to-peers is positioned at identical Protocol independent multicast-sparse mode pim-sm domain; Or different MSDP peer-to-peers are positioned at different pim-sm domains.
Compared with prior art, the embodiment of the present invention at least has the following advantages: in the embodiment of the present invention, MSDP peer-to-peer is by receiving in list and record the corresponding relation between RP address and other MSDP peer-to-peer in beta pruning, to show that MSDP peer-to-peer does not need to send to other MSDP peer-to-peer the SA message that carries GaiRP address; MSDP peer-to-peer is when receiving SA message, if beta pruning receives in list and records MSDP peer-to-peer corresponding to RP address carrying in this SA message, this MSDP peer-to-peer does not need the MSDP peer-to-peer corresponding to GaiRP address to forward this SA message, thereby avoid each MSDP peer-to-peer to receive the SA message of bulk redundancy, and can improve the handling property of each MSDP peer-to-peer.
Accompanying drawing explanation
Fig. 1 transmits the networking diagram of information about multicast source by MSDP between pim-sm domain in prior art;
Fig. 2 is the transmission method schematic flow sheet of a kind of SA message of providing of the embodiment of the present invention;
Fig. 3 and Fig. 4 are the prune packet that proposes in the embodiment of the present invention and the form schematic diagram of graft packet;
Fig. 5 is the structural representation of a kind of MSDP peer-to-peer of providing of the embodiment of the present invention.
Embodiment
For problems of the prior art, the embodiment of the present invention provides a kind of transmission method of SA message, and the method is applied to comprise in the network of a plurality of MSDP peer-to-peers.Wherein, different MSDP peer-to-peers is positioned at identical pim-sm domain; Or different MSDP peer-to-peers are positioned at different pim-sm domains.In addition, MSDP peer-to-peer can be the RP in pim-sm domain, can not be also the RP in pim-sm domain, but other network equipment.The application scenarios schematic diagram that the Fig. 1 of take is the embodiment of the present invention, MSDP peer-to-peer is Router A, Router B and Router C, and Router A is the RP in PIM-SM1 territory, and Router B is the RP in PIM-SM2 territory, and Router C is the RP in PIM-SM3 territory.
In the embodiment of the present invention, as shown in Table 1 and Table 2, on each MSDP peer-to-peer, all need to safeguard that beta pruning receives list and beta pruning sends list, this beta pruning receives list for recording the corresponding relation between RP address and MSDP peer-to-peer, and this beta pruning sends list for recording the corresponding relation between RP address and MSDP peer-to-peer.Wherein, MSDP peer-to-peer can be the device identification of MSDP peer-to-peer or the IP address of MSDP peer-to-peer etc.; Based on this, this beta pruning receives list for recording the corresponding relation between RP address and the device identification of MSDP peer-to-peer, and this beta pruning sends list for recording the corresponding relation between RP address and the device identification of MSDP peer-to-peer; Or this beta pruning receives list for recording the corresponding relation between RP address and the IP address of MSDP peer-to-peer, this beta pruning sends list for recording the corresponding relation between RP address and the IP address of MSDP peer-to-peer.
Table 1 beta pruning receives list
| RP address | MSDP peer-to-peer |
| ? | ? |
| ? | ? |
Table 2 beta pruning sends list
| RP address | MSDP peer-to-peer |
| ? | ? |
| ? | ? |
Based on beta pruning, receive list and beta pruning transmission list, as shown in Figure 2, the method comprises the following steps:
In the embodiment of the present invention, this MSDP peer-to-peer after the prune packet that carries LiaoRP address of receiving from other MSDP peer-to-peer, the RP address that this MSDP peer-to-peer carries record this prune packet in beta pruning receives list in and the corresponding relation between other MSDP peer-to-peer; Further, this MSDP peer-to-peer sends and carries after the prune packet of LiaoRP address to other MSDP peer-to-peer, other MSDP peer-to-peer after the prune packet of receiving from this MSDP peer-to-peer, the RP address of carrying record this prune packet in beta pruning receives list in and the corresponding relation between this MSDP peer-to-peer.
Below in conjunction with the application scenarios shown in Fig. 1, the above-mentioned steps of the embodiment of the present invention is elaborated.
Suppose that Router A periodically sends SA message to MSDP peer-to-peer (Router B and Router C), in this SA message, carry the information about multicast source in PIM-SM1 territory, and in this SA message, carried the IP address of RP1, the IP address that the RP address of carrying in SA message is RP1.
For step 201, Router B, when the SA message of receiving for the first time from Router A, carries out rpf check to this SA message, now rpf check success.Router C, when the SA message of receiving for the first time from Router A, carries out rpf check to this SA message, now rpf check success.
For step 202, when the RP address that Router B carries in utilizing SA message (being the IP address of RP1) inquiry beta pruning receives list, because now beta pruning receives list, be empty, therefore beta pruning receives in list and does not record other MSDP peer-to-peer corresponding to RP address carrying in this SA message, so Router B need to forward this SA message to Router C.When the RP address that Router C carries in utilizing SA message (being the IP address of RP1) inquiry beta pruning receives list, because now beta pruning receives list, be empty, therefore beta pruning receives in list and does not record other MSDP peer-to-peer corresponding to RP address carrying in this SA message, so Router C need to forward this SA message to Router B.
For step 201, Router B, when receiving the SA message forwarding from Router C, carries out rpf check to this SA message, now rpf check failure.Router C, when receiving the SA message forwarding from Router B, carries out rpf check to this SA message, now rpf check failure.
For step 203, Router B is after receiving the SA message forwarding from Router C, abandon this SA message, the MSDP peer-to-peer that the RP address (being the IP address of RP1) of carrying record this SA message in beta pruning transmission list in and Router C(send this SA message) corresponding relation between, as shown in table 3.Router B sends prune packet to Router C afterwards, has carried the RP address (being the IP address of RP1) of carrying in SA message in this prune packet.Router C after the prune packet of receiving from Router B, the RP address (being the IP address of RP1) of carrying record this prune packet in beta pruning receives list in and the corresponding relation between Router B, as shown in table 4.
For step 203, Router C is after receiving the SA message forwarding from Router B, abandon this SA message, the MSDP peer-to-peer that the RP address (being the IP address of RP1) of carrying record this SA message in beta pruning transmission list in and Router B(send this SA message) corresponding relation between, as shown in table 5.Router C sends prune packet to Router B afterwards, has carried the RP address (being the IP address of RP1) of carrying in SA message in this prune packet.Router B after the prune packet of receiving from Router C, the RP address (being the IP address of RP1) of carrying record this prune packet in beta pruning receives list in and the corresponding relation between Router C, as shown in table 6.
Table 3 beta pruning sends list
| RP address | MSDP peer-to-peer |
| The IP address of RP1 | Router?C |
| ? | ? |
Table 4 beta pruning receives list
| RP address | MSDP peer-to-peer |
| The IP address of RP1 | Router?B |
| ? | ? |
Table 5 beta pruning sends list
| RP address | MSDP peer-to-peer |
| The IP address of RP1 | Router?B |
| ? | ? |
Table 6 beta pruning receives list
| RP address | MSDP peer-to-peer |
| The IP address of RP1 | Router?C |
| ? | ? |
For step 201, Router B is follow-up while again receiving the SA message from Router A, this SA message carried out to rpf check, now rpf check success.Router C is follow-up while again receiving the SA message from Router A, this SA message carried out to rpf check, now rpf check success.
For step 202, when the RP address that Router B carries in utilizing SA message (being the IP address of RP1) inquiry beta pruning receives list, it is as shown in table 6 that now beta pruning receives list, be that beta pruning receives other MSDP peer-to-peer (being Router C) that has RP address (being the IP address of the RP1) correspondence of carrying in this SA message in list, now illustrate that Router C need to not receive from Router B the SA message of the IP address of this RP1, so Router B does not need to forward this SA message to Router C.
For step 202, when the RP address that Router C carries in utilizing SA message (being the IP address of RP1) inquiry beta pruning receives list, it is as shown in table 4 that now beta pruning receives list, be that beta pruning receives that in list, to have other MSDP peer-to-peer corresponding to RP address (being the IP address of RP1) carrying in this SA message be Router B), now illustrate that Router B need to not receive from Router C the SA message of the IP address of this RP1, so Router C does not need to forward this SA message to Router B.
In the embodiment of the present invention, after RP address and the corresponding relation between other MSDP peer-to-peer that this MSDP peer-to-peer carries record SA message in beta pruning transmission list in, if it is other MSDP peer-to-peer that this MSDP peer-to-peer detects the rpf check opposite end corresponding to RP address of carrying in this SA message, this MSDP peer-to-peer also need to send and list, delete the RP address of carrying in this SA message and the corresponding relation between other MSDP peer-to-peer from beta pruning, and send graft packet to other MSDP peer-to-peer, and in this graft packet, carried the RP address of carrying in this SA message.
In the embodiment of the present invention, after MSDP peer-to-peer records the corresponding relation between RP address and other MSDP peer-to-peer in beta pruning reception list, if MSDP peer-to-peer receives from the graft packet of other MSDP peer-to-peer (carrying LiaoRP address in this graft packet), MSDP peer-to-peer is after receiving graft packet, also need to receive the RP address of carrying in deleting this graft packet in list and the corresponding relation between other MSDP peer-to-peer in beta pruning; Further, this MSDP peer-to-peer is after the graft packet of LiaoRP address is carried in other MSDP peer-to-peer transmission, other MSDP peer-to-peer, after the graft packet of receiving from this MSDP peer-to-peer, also need to receive the RP address of carrying in deleting this graft packet in list and the corresponding relation between this MSDP peer-to-peer in beta pruning.
Continuation is elaborated to the said process of the embodiment of the present invention in conjunction with the application scenarios shown in Fig. 1.
Suppose that on Router B, the beta pruning shown in Maintenance Table 3 sends the beta pruning reception list shown in list and table 6, the beta pruning on Router C shown in Maintenance Table 5 sends the beta pruning shown in list and table 4 and receives list.
After the link failure between Router B and Router A, rpf check opposite end corresponding to IP address that Router B detects RP1 is Router C, based on this, Router B also need to send list and delete the IP address of RP1 and the corresponding relation between Router C from the beta pruning shown in table 3.Further, Router B also needs to send graft packet to Router C, and the IP address of having carried RP1 in this graft packet.Further, Router C, after the graft packet of receiving from Router B, also need to receive list and delete the IP address of RP1 and the corresponding relation between Router B from the beta pruning shown in table 4.Based on this, when Router C receives from the SA message of Router A again, this SA message can be sent to Router B, to guarantee that Router B can receive the SA message from Router A.
After the link failure between Router C and Router A, rpf check opposite end corresponding to IP address that Router C detects RP1 is Router B, based on this, Router C also need to send list and delete the IP address of RP1 and the corresponding relation between Router B from the beta pruning shown in table 5.Further, Router C also needs to send graft packet to Router B, and the IP address of having carried RP1 in this graft packet.Further, Router B, after the graft packet of receiving from Router C, also need to receive list and delete the IP address of RP1 and the corresponding relation between Router C from the beta pruning shown in table 6.Based on this, when Router B receives from the SA message of Router A again, this SA message can be sent to Router C, to guarantee that Router C can receive the SA message from Router A.
In a kind of specific implementation of the embodiment of the present invention, between MSDP peer-to-peer, the form schematic diagram of mutual prune packet and graft packet respectively as shown in Figure 3 and Figure 4.Wherein, all need to carry RP address in this prune packet and graft packet, and prune packet and graft packet can distinguish by different types, for example: the type of prune packet is 8, the type of graft packet is 9.
In sum, in the embodiment of the present invention, MSDP peer-to-peer is by receiving in list and record the corresponding relation between RP address and other MSDP peer-to-peer in beta pruning, to show that MSDP peer-to-peer does not need to send to other MSDP peer-to-peer the SA message that carries GaiRP address; Based on this, MSDP peer-to-peer is when receiving SA message, if beta pruning receives in list and records MSDP peer-to-peer corresponding to RP address carrying in this SA message, this MSDP peer-to-peer does not need the MSDP peer-to-peer corresponding to GaiRP address to forward this SA message, thereby avoids each MSDP peer-to-peer to receive the SA message of bulk redundancy.
Inventive concept based on same with said method, also provides a kind of Multicast Source Discovery Protocol MSDP peer-to-peer in the embodiment of the present invention, be applied in the network that comprises a plurality of MSDP peer-to-peers, and as shown in Figure 5, described MSDP peer-to-peer specifically comprises:
Described processing module 13, also forwards described SA message for other MSDP peer-to-peer outside MSDP peer-to-peer corresponding to GaiRP address.
Described logging modle 11, also for after described SA message is carried out to rpf check, in rpf check when failure of described SA message, in beta pruning, send the corresponding relation between the MSDP peer-to-peer of the RP address of carrying in recording described SA message in list and the described SA message of transmission;
Described processing module 13, also, for after described SA message is carried out to rpf check, when the rpf check failure of described SA message, abandon described SA message, and send prune packet to the MSDP peer-to-peer that sends described SA message, in this prune packet, carry the RP address of carrying in described SA message; By the MSDP peer-to-peer that sends described SA message, after receiving prune packet, in beta pruning, receive the RP address of carrying in recording described SA message in list and the corresponding relation between this MSDP peer-to-peer.
Described processing module 13, also for after the RP address and the corresponding relation between the MSDP peer-to-peer of the described SA message of transmission of carrying in described SA message is recorded in beta pruning transmission list, the rpf check opposite end corresponding to RP address of carrying in described SA message being detected is while sending the MSDP peer-to-peer of described SA message, from beta pruning transmission list, delete the corresponding relation between the RP address of carrying in described SA message and the MSDP peer-to-peer that sends described SA message, and send graft packet to the MSDP peer-to-peer that sends described SA message; By the MSDP peer-to-peer that sends described SA message, after the graft packet of receiving from this MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in deleting described SA message in list and the corresponding relation between this MSDP peer-to-peer;
Record the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning reception list after, receive the graft packet from described other MSDP peer-to-peer, in described graft packet, carry LiaoRP address; After receiving described graft packet, in described beta pruning, receive the RP address of carrying in deleting described graft packet in list and the corresponding relation between described other MSDP peer-to-peer.
In the embodiment of the present invention, different MSDP peer-to-peers is positioned at identical Protocol independent multicast-sparse mode pim-sm domain; Or different MSDP peer-to-peers are positioned at different pim-sm domains.
Wherein, the modules of apparatus of the present invention can be integrated in one, and also can separatedly dispose.Above-mentioned module can be merged into a module, also can further split into a plurality of submodules.
Through the above description of the embodiments, those skilled in the art can be well understood to the mode that the present invention can add essential general hardware platform by software and realize, and can certainly pass through hardware, but in a lot of situation, the former is better execution mode.Understanding based on such, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in a storage medium, comprise that some instructions are with so that a computer equipment (can be personal computer, server, or the network equipment etc.) carry out the method described in each embodiment of the present invention.
It will be appreciated by those skilled in the art that accompanying drawing is the schematic diagram of a preferred embodiment, the module in accompanying drawing or flow process might not be that enforcement the present invention is necessary.
It will be appreciated by those skilled in the art that the module in the device in embodiment can be distributed in the device of embodiment according to embodiment description, also can carry out respective change and be arranged in the one or more devices that are different from the present embodiment.The module of above-described embodiment can be merged into a module, also can further split into a plurality of submodules.
The invention described above embodiment sequence number, just to describing, does not represent the quality of embodiment.
Disclosed is above only several specific embodiment of the present invention, and still, the present invention is not limited thereto, and the changes that any person skilled in the art can think of all should fall into protection scope of the present invention.
Claims (10)
1. a transmission method for the effective SA message of information source, the method is applied to comprise in the network of a plurality of Multicast Source Discovery Protocol MSDP peer-to-peers, it is characterized in that, the method comprises the following steps:
MSDP peer-to-peer receives the prune packet from other MSDP peer-to-peer, has carried convergent point RP address in described prune packet; Described MSDP peer-to-peer, after receiving described prune packet, receives in list and records the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning;
Described MSDP peer-to-peer, when receiving SA message, carries out inverse path to described SA message and forwards rpf check; If rpf check success, utilizes beta pruning described in the RP address lookup carrying in described SA message to receive list; If described beta pruning receives in list and records MSDP peer-to-peer corresponding to RP address carrying in described SA message, to GaiRP address, corresponding MSDP peer-to-peer does not forward described SA message.
2. the method for claim 1, is characterized in that, described method also comprises:
Described MSDP peer-to-peer forwards described SA message to other MSDP peer-to-peer outside MSDP peer-to-peer corresponding to GaiRP address.
3. the method for claim 1, is characterized in that, after described MSDP peer-to-peer carries out inverse path forwarding rpf check to described SA message, described method also comprises:
If rpf check failure, described MSDP peer-to-peer abandons described SA message, and the RP address of carrying record described SA message in beta pruning transmission list in and the corresponding relation between the MSDP peer-to-peer of the described SA message of transmission, and send prune packet to the MSDP peer-to-peer that sends described SA message, in this prune packet, carry the RP address of carrying in described SA message; By the MSDP peer-to-peer that sends described SA message, after the prune packet of receiving from described MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in recording described SA message in list and the corresponding relation between described MSDP peer-to-peer.
4. method as claimed in claim 3, is characterized in that,
After corresponding relation between the RP address that described MSDP peer-to-peer carries record described SA message in beta pruning transmission list in and the MSDP peer-to-peer that sends described SA message, described method also comprises: it is while sending the MSDP peer-to-peer of described SA message that described MSDP peer-to-peer detects the rpf check opposite end corresponding to RP address of carrying in described SA message, from beta pruning transmission list, delete the corresponding relation between the RP address of carrying in described SA message and the MSDP peer-to-peer that sends described SA message, and send graft packet to the MSDP peer-to-peer that sends described SA message; By the MSDP peer-to-peer that sends described SA message, after the graft packet of receiving from described MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in deleting described SA message in list and the corresponding relation between described MSDP peer-to-peer;
After described MSDP peer-to-peer records the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning reception list, described method also comprises: described MSDP peer-to-peer receives the graft packet from described other MSDP peer-to-peer, carries LiaoRP address in described graft packet; Described MSDP peer-to-peer, after receiving described graft packet, receives the RP address of carrying in deleting described graft packet in list and the corresponding relation between described other MSDP peer-to-peer in described beta pruning.
5. the method as described in claim 1-4 any one, is characterized in that,
Different MSDP peer-to-peers is positioned at identical Protocol independent multicast-sparse mode pim-sm domain; Or different MSDP peer-to-peers are positioned at different pim-sm domains.
6. a Multicast Source Discovery Protocol MSDP peer-to-peer, is applied in the network that comprises a plurality of MSDP peer-to-peers, it is characterized in that, described MSDP peer-to-peer specifically comprises:
Logging modle, for receiving the prune packet from other MSDP peer-to-peer, has carried convergent point RP address in described prune packet; And after receiving described prune packet, in beta pruning, receive in list and record the corresponding relation between described RP address and described other MSDP peer-to-peer;
Detection module, for when receiving the effective SA message of information source, carries out inverse path to described SA message and forwards rpf check; And in rpf check when success of described SA message, utilize beta pruning described in the RP address lookup carrying in described SA message to receive list;
Processing module, while recording MSDP peer-to-peer corresponding to the RP address of carrying in described SA message for receive list when described beta pruning, to GaiRP address, corresponding MSDP peer-to-peer does not forward described SA message.
7. MSDP peer-to-peer as claimed in claim 6, is characterized in that,
Described processing module, also forwards described SA message for other MSDP peer-to-peer outside MSDP peer-to-peer corresponding to GaiRP address.
8. MSDP peer-to-peer as claimed in claim 6, is characterized in that,
Described logging modle, also for after described SA message is carried out to rpf check, in rpf check when failure of described SA message, in beta pruning, send the corresponding relation between the MSDP peer-to-peer of the RP address of carrying in recording described SA message in list and the described SA message of transmission;
Described processing module, also, for after described SA message is carried out to rpf check, when the rpf check failure of described SA message, abandon described SA message, and send prune packet to the MSDP peer-to-peer that sends described SA message, in this prune packet, carry the RP address of carrying in described SA message; By the MSDP peer-to-peer that sends described SA message, after receiving prune packet, in beta pruning, receive the RP address of carrying in recording described SA message in list and the corresponding relation between this MSDP peer-to-peer.
9. MSDP peer-to-peer as claimed in claim 8, is characterized in that,
Described processing module, also for after the RP address and the corresponding relation between the MSDP peer-to-peer of the described SA message of transmission of carrying in described SA message is recorded in beta pruning transmission list, the rpf check opposite end corresponding to RP address of carrying in described SA message being detected is while sending the MSDP peer-to-peer of described SA message, from beta pruning transmission list, delete the corresponding relation between the RP address of carrying in described SA message and the MSDP peer-to-peer that sends described SA message, and send graft packet to the MSDP peer-to-peer that sends described SA message; By the MSDP peer-to-peer that sends described SA message, after the graft packet of receiving from this MSDP peer-to-peer, in beta pruning, receive the RP address of carrying in deleting described SA message in list and the corresponding relation between this MSDP peer-to-peer;
Record the corresponding relation between described RP address and described other MSDP peer-to-peer in beta pruning reception list after, receive the graft packet from described other MSDP peer-to-peer, in described graft packet, carry LiaoRP address; After receiving described graft packet, in described beta pruning, receive the RP address of carrying in deleting described graft packet in list and the corresponding relation between described other MSDP peer-to-peer.
10. the MSDP peer-to-peer as described in claim 6-9 any one, is characterized in that,
Different MSDP peer-to-peers is positioned at identical Protocol independent multicast-sparse mode pim-sm domain; Or different MSDP peer-to-peers are positioned at different pim-sm domains.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310493597.3A CN103516616B (en) | 2013-10-18 | 2013-10-18 | Transmission method and equipment for SA messages |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310493597.3A CN103516616B (en) | 2013-10-18 | 2013-10-18 | Transmission method and equipment for SA messages |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103516616A true CN103516616A (en) | 2014-01-15 |
| CN103516616B CN103516616B (en) | 2017-02-15 |
Family
ID=49898680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310493597.3A Active CN103516616B (en) | 2013-10-18 | 2013-10-18 | Transmission method and equipment for SA messages |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103516616B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639446A (en) * | 2015-02-03 | 2015-05-20 | 杭州华三通信技术有限公司 | Method and device for obtaining multicasting source information |
| CN109963333A (en) * | 2017-12-26 | 2019-07-02 | 成都鼎桥通信技术有限公司 | Multicast resource distribution method and device based on service area |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101291242A (en) * | 2008-06-17 | 2008-10-22 | 杭州华三通信技术有限公司 | Method, system and apparatus for PIM DM to support bandwidth reservation and establishing multicast list |
| CN101764812A (en) * | 2009-12-30 | 2010-06-30 | 华为技术有限公司 | Method, router and network system for transmitting active source messages |
| US20100303073A1 (en) * | 2009-05-28 | 2010-12-02 | Alaxala Networks Corporation | Network relay apparatus and inter-network relay method |
| CN102075417A (en) * | 2010-09-30 | 2011-05-25 | 杭州华三通信技术有限公司 | Multicast cutting method, protocol independent multicast router, and two-layer exchanger |
-
2013
- 2013-10-18 CN CN201310493597.3A patent/CN103516616B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101291242A (en) * | 2008-06-17 | 2008-10-22 | 杭州华三通信技术有限公司 | Method, system and apparatus for PIM DM to support bandwidth reservation and establishing multicast list |
| US20100303073A1 (en) * | 2009-05-28 | 2010-12-02 | Alaxala Networks Corporation | Network relay apparatus and inter-network relay method |
| CN101764812A (en) * | 2009-12-30 | 2010-06-30 | 华为技术有限公司 | Method, router and network system for transmitting active source messages |
| CN102075417A (en) * | 2010-09-30 | 2011-05-25 | 杭州华三通信技术有限公司 | Multicast cutting method, protocol independent multicast router, and two-layer exchanger |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639446A (en) * | 2015-02-03 | 2015-05-20 | 杭州华三通信技术有限公司 | Method and device for obtaining multicasting source information |
| CN104639446B (en) * | 2015-02-03 | 2018-05-08 | 新华三技术有限公司 | A kind of information about multicast source acquisition methods and device |
| CN109963333A (en) * | 2017-12-26 | 2019-07-02 | 成都鼎桥通信技术有限公司 | Multicast resource distribution method and device based on service area |
| CN109963333B (en) * | 2017-12-26 | 2022-09-20 | 成都鼎桥通信技术有限公司 | Multicast resource allocation method and device based on service area |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103516616B (en) | 2017-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4745387B2 (en) | Multicast routing protocol in mesh networks | |
| CN101605103B (en) | Method and apparatus for static forwarding multicast data | |
| CN105897444B (en) | Multicast group management method and device | |
| CN103516609B (en) | Method and equipment for transmitting service messages | |
| CN101247210B (en) | Method for implementing multicast forwarding tree based on multicast source discovering protocol | |
| CN103117935B (en) | Be applied to multicast data forwarding method and the device of multi-home networking | |
| US8243585B2 (en) | Method and apparatus for fault-resilient multicast using multiple sources | |
| CN102957573B (en) | Path detection realizing method and node | |
| CN101232392B (en) | Method for notifying multicast source between MSDP and PIM | |
| CN104052667A (en) | Packet processing method and device | |
| CN103414798B (en) | The communication means of address transition Network Based, equipment and system | |
| CN101800742A (en) | Method for updating and processing upstream information of routing device, routing devices and network system | |
| CN104601742A (en) | Message transmission method and device | |
| CN102739521A (en) | Multicast service realizing method and equipment thereof | |
| CN103188153B (en) | BFD file transmitting method and equipment on a kind of broadcasting network link | |
| CN105337746A (en) | Multicast data transmission method and apparatus | |
| CN102201996B (en) | Method and equipment for forwarding message in network address translation (NAT) environment | |
| CN104579981A (en) | Multicast data message forwarding method and equipment | |
| CN103609063A (en) | Protocol independent multicast last hop router discovery | |
| CN105471742A (en) | Message processing method and message processing equipment | |
| CN103516616A (en) | Transmission method and equipment for SA messages | |
| EP3155772A1 (en) | A new instant messaging(im) routing method and router | |
| CN102104551B (en) | Bidirectional protocol independent multicast forwarding method and two-layer network device | |
| CN114584262B (en) | Data transmission method and related equipment | |
| CN100508467C (en) | Method and route equipment for retransmitted layer proxy PIM |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |