CN103516616B - Transmission method and equipment for SA messages - Google Patents
Transmission method and equipment for SA messages Download PDFInfo
- Publication number
- CN103516616B CN103516616B CN201310493597.3A CN201310493597A CN103516616B CN 103516616 B CN103516616 B CN 103516616B CN 201310493597 A CN201310493597 A CN 201310493597A CN 103516616 B CN103516616 B CN 103516616B
- Authority
- CN
- China
- Prior art keywords
- peer
- message
- msdp
- 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.)
- Active
Links
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, more particularly, to a kind of transmission method of SA message and equipment.
Background technology
MSDP（Multicast Source Discovery Protocol, Multicast Source Discovery Protocol）It is many in order to solve
Individual PIM-SM（Protocol Independent Multicast Sparse Mode, Protocol independent multicast-sparse mode）Domain
Between interconnection and the inter-domain multicast solution developed, for finding the information about multicast source in other pim-sm domains.Specifically,
Due to the multicast source only RP into this pim-sm domain（RendezvousPoint, convergent point）Registration, and the multicast of each pim-sm domain
Source information is mutually isolated, and therefore RP just knows that the information about multicast source in this pim-sm domain, can only set up group in this pim-sm domain
Broadcast distribution tree, the multicast data delivery that multicast source in this pim-sm domain is sent is to local user.If there are a kind of mechanism, by it
Information about multicast source in its pim-sm domain passes to the RP in this pim-sm domain, then the RP in this pim-sm domain just can be to other
Multicast source in pim-sm domain is initiated adition process and is set up multicast distribution tree, thus realizing the cross-domain transmission of multicast packet.Base
In this imagination, MSDP sets up MSDP peer relationship, to connect each PIM-SM by choosing suitable router in a network
RP in domain, and by interaction SA between each MSDP peer-to-peer（Source Active, information source is effective）Message is sharing multicast
Source information.
As shown in figure 1, being the networking schematic diagram transmitting information about multicast source between multiple pim-sm domains by MSDP, Router
A（Router A）Periodically through SA message, the information about multicast source in PIM-SM1 domain is advertised to all MSDP peer-to-peers, that is, leads to
Cross SA message and the information about multicast source in PIM-SM1 domain is advertised to Router B and Router C.Router B is derived from receiving
After the SA message of Router A, SA message is advertised to all MSDP peer-to-peers, Router C will be advertised to by SA message, but not
SA message is advertised to Router A.Router C is receiving after the SA message of Router A, and SA message is advertised to institute
There is MSDP peer-to-peer, Router B will be advertised to by SA message, but SA message is not advertised to Router A.
Obviously, when there is substantial amounts of MSDP peer-to-peer, existing processing mode can lead to each MSDP peer-to-peer all to be received
SA message to bulk redundancy.For example, the multicast source letter carrying in PIM-SM1 domain from Router A that Router B receives
The SA message of breath is effective SA message, and the multicast carrying in PIM-SM1 domain from other MSDP peer-to-peers receiving
The SA message of source information is the SA message of redundancy.Further, MSDP peer-to-peer needs each SA message that itself is received to enter
Row is processed, and when each SA message that itself is received is processed, the process performance of MSDP peer-to-peer can be led to decline.
Content of the invention
The embodiment of the present invention provides a kind of transmission method of SA message and equipment, to avoid each MSDP peer-to-peer to receive in a large number
The SA message of redundancy, improves the process performance of each MSDP peer-to-peer.
In order to achieve the above object, the embodiment of the present invention provides a kind of transmission method of information source effective SA message, the method
It is applied in the network including multiple 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-peers, carries convergent point in described prune packet
RP address；Described MSDP peer-to-peer, after receiving described prune packet, receives in list in beta pruning and records described RP address and institute
State the corresponding relation between other MSDP peer-to-peers；
Described MSDP peer-to-peer, when receiving SA message, carries out inverse path and forwards rpf check to described SA message；If
Rpf check success, then receive list using the beta pruning described in RP address lookup carrying in described SA message；If described beta pruning connects
Receiving record in list has the RP address corresponding MSDP peer-to-peer carrying in described SA message, then not corresponding to this RP address
MSDP peer-to-peer forwards described SA message.
Methods described also includes：Other MSDP to outside the corresponding MSDP peer-to-peer of this RP address for the described MSDP peer-to-peer
Peer-to-peer forwards described SA message.
After described MSDP peer-to-peer carries out inverse path forwarding rpf check to described SA message, methods described also includes：
If rpf check failure, described MSDP peer-to-peer abandons described SA message, and records institute in beta pruning transmission list
State the corresponding relation between the RP address carrying in SA message and the MSDP peer-to-peer sending described SA message, and described to sending
The MSDP peer-to-peer of SA message sends prune packet, carries the RP address carrying in described SA message in this prune packet；By send out
The MSDP peer-to-peer sending described SA message is receiving after the prune packet of described MSDP peer-to-peer, receives in list in beta pruning
Record the corresponding relation between the RP address carrying in described SA message and described MSDP peer-to-peer.
Described in described MSDP peer-to-peer records the RP address carrying in described SA message in beta pruning transmission list and sends
After corresponding relation between the MSDP peer-to-peer of SA message, methods described also includes：Described MSDP peer-to-peer detects described
When the RP address corresponding rpf check opposite end carrying in SA message is the MSDP peer-to-peer sending described SA message, send out from beta pruning
Send the corresponding pass deleting between the RP address carrying in described SA message and the MSDP peer-to-peer sending described SA message in list
System, and send graft packet to the MSDP peer-to-peer sending described SA message；Existed by the MSDP peer-to-peer sending described SA message
Receive after the graft packet of described MSDP peer-to-peer, receive in beta pruning and in list, delete the RP ground carrying in described SA message
Corresponding relation between location and described MSDP peer-to-peer；
Described MSDP peer-to-peer receives in beta pruning and records in list between described RP address and described other MSDP peer-to-peer
Corresponding relation after, methods described also includes：Described MSDP peer-to-peer receives the grafting from described other MSDP peer-to-peer
Message, carries RP address in described graft packet；Described MSDP peer-to-peer, after receiving described graft packet, is cut described
The corresponding relation deleted in list between the RP address carrying in described graft packet and described other MSDP peer-to-peer is received in scion grafting.
Different MSDP peer-to-peers is located at identical Protocol independent multicast-sparse mode pim-sm domain；Or, different
MSDP peer-to-peer is located at different pim-sm domains.
The embodiment of the present invention provides a kind of Multicast Source Discovery Protocol MSDP peer-to-peer, applies and is including multiple MSDP peer-to-peers
Network in, described MSDP peer-to-peer specifically includes：
Logging modle, for receiving the prune packet from other MSDP peer-to-peers, carries remittance in described prune packet
Accumulation RP address；And after receiving described prune packet, receive in beta pruning and in list, record described RP address and described other
Corresponding relation between MSDP peer-to-peer；
Detection module, forwards RPF inspection for when receiving information source effective SA message, described SA message is carried out with inverse path
Look into；And in the rpf check success of described SA message, received using the beta pruning described in RP address lookup carrying in described SA message
List；
Processing module, for having the RP address carrying in described SA message corresponding when described beta pruning receives record in list
During MSDP peer-to-peer, do not forward described SA message to this RP address corresponding MSDP peer-to-peer.
Described processing module, is additionally operable to the other MSDP peer-to-peers to outside the corresponding MSDP peer-to-peer of this RP address and forwards
Described SA message.
Described logging modle, is additionally operable to after carrying out rpf check to described SA message, in the RPF inspection of described SA message
When looking into unsuccessfully, beta pruning transmission list records the RP address carrying in described SA message and send described SA message MSDP pair
Deng the corresponding relation between body；
Described processing module, is additionally operable to after carrying out rpf check to described SA message, in the RPF inspection of described SA message
When looking into unsuccessfully, abandon described SA message, and send prune packet, this prune packet to the MSDP peer-to-peer sending described SA message
In carry the RP address carrying in described SA message；By send described SA message MSDP peer-to-peer after receiving prune packet,
Receive the corresponding relation recording in list between the RP address carrying in described SA message and this MSDP peer-to-peer in beta pruning.
Described processing module, is additionally operable to record the RP address carrying in described SA message and transmission in beta pruning transmission list
After corresponding relation between the MSDP peer-to-peer of described SA message, the RP address carrying in described SA message is detected corresponds to
Rpf check opposite end when being the MSDP peer-to-peer sending described SA message, delete from beta pruning transmission list in described SA message
Corresponding relation between the RP address carrying and the MSDP peer-to-peer sending described SA message, and to the described SA message of transmission
MSDP peer-to-peer sends graft packet；Transferring from this MSDP peer-to-peer is being received by the MSDP peer-to-peer sending described SA message
It is informed of a case after literary composition, delete corresponding between the RP address carrying in described SA message and this MSDP peer-to-peer in beta pruning reception list
Relation；
After beta pruning receives the corresponding relation recording in list between described RP address and described other MSDP peer-to-peer,
Receive the graft packet from described other MSDP peer-to-peer, in described graft packet, carry RP address；Transfer described in receive
It is informed of a case after literary composition, receive in described beta pruning and in list, delete the RP address carrying in described graft packet and described other MSDP pair
Deng the corresponding relation between body.
Different MSDP peer-to-peers is located at identical Protocol independent multicast-sparse mode pim-sm domain；Or, different
MSDP peer-to-peer is located at different pim-sm domains.
Compared with prior art, the embodiment of the present invention at least has advantages below：In the embodiment of the present invention, MSDP peer-to-peer
By receiving the corresponding relation between record RP address and other MSDP peer-to-peer in list in beta pruning, to show MSDP peer-to-peer
Do not need to send, to other MSDP peer-to-peers, the SA message carrying this RP address；MSDP peer-to-peer when receiving SA message, if
Beta pruning receives record in list the RP address corresponding MSDP peer-to-peer carrying in this SA message, then this MSDP peer-to-peer is not required to
To forward this SA message to this RP address corresponding MSDP peer-to-peer, thus avoiding each MSDP peer-to-peer to receive the SA of bulk redundancy
Message, and the process performance of each MSDP peer-to-peer can be improved.
Brief description
Fig. 1 is the networking diagram transmitting information about multicast source in prior art between pim-sm domain by MSDP；
Fig. 2 is a kind of transmission method schematic flow sheet of SA message provided in an embodiment of the present invention；
Fig. 3 and Fig. 4 is the form schematic diagram of the prune packet and graft packet proposing in the embodiment of the present invention；
Fig. 5 is a kind of structural representation of MSDP peer-to-peer provided in an embodiment of the present invention.
Specific embodiment
For problems of the prior art, the embodiment of the present invention provides a kind of transmission method of SA message, the method
It is applied in the network including multiple MSDP peer-to-peers.Wherein, different MSDP peer-to-peers is located at identical pim-sm domain；Or
Person, different MSDP peer-to-peers is located at different pim-sm domains.Additionally, MSDP peer-to-peer can be the RP in pim-sm domain,
Can not be the RP in pim-sm domain, but other network equipment.Application scenarios schematic diagram with Fig. 1 as 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 domain, and Router B is
RP in PIM-SM2 domain, Router C is the RP in PIM-SM3 domain.
In the embodiment of the present invention, as shown in Table 1 and Table 2, each MSDP peer-to-peer is required to safeguard beta pruning receive list and
Beta pruning transmission list, this beta pruning receives list and is used for recording the corresponding relation between RP address and MSDP peer-to-peer, and this beta pruning is sent out
List is sent to be used for recording the corresponding relation between RP address and MSDP peer-to-peer.Wherein, MSDP peer-to-peer can be MSDP equity
IP address of the device identification of body or MSDP peer-to-peer etc.；Based on this, this beta pruning receive list be used for recording RP address with
Corresponding relation between the device identification of MSDP peer-to-peer, this beta pruning transmission list is used for recording RP address and MSDP peer-to-peer
Corresponding relation between device identification；Or, this beta pruning receives list and is used for recording the IP address of RP address and MSDP peer-to-peer
Between corresponding relation, this beta pruning transmission list be used for record between RP address and the IP address of MSDP peer-to-peer corresponding close
System.
Table 1 beta pruning receives list
| RP address | MSDP peer-to-peer |
Table 2 beta pruning transmission list
| RP address | MSDP peer-to-peer |
List and beta pruning transmission list are received based on beta pruning, as shown in Fig. 2 the method comprises the following steps：
Step 201, MSDP peer-to-peer, when receiving from the SA message of other MSDP peer-to-peers, is carried out to this SA message
RPF（Reverse Path Forwarding, inverse path forwards）Check；If rpf check success, execution step 202；
If rpf check failure, execution step 203.
Step 202, MSDP peer-to-peer receives list using the RP address lookup beta pruning carrying in this SA message；If beta pruning
Receiving record in list has the RP address corresponding MSDP peer-to-peer carrying in this SA message, then MSDP peer-to-peer does not need to this
RP address corresponding MSDP peer-to-peer forwards this SA message and it needs to other to outside the corresponding MSDP peer-to-peer of this RP address
MSDP peer-to-peer forwards this SA message.
Step 203, MSDP peer-to-peer abandons this SA message, records the RP carrying in this SA message in beta pruning transmission list
Corresponding relation between address and the MSDP peer-to-peer sending this SA message, and send to the MSDP peer-to-peer sending this SA message
Prune packet；Wherein, carry the RP address carrying in the SA message that this MSDP peer-to-peer receives in this prune packet.Afterwards,
Received after the prune packet of this MSDP peer-to-peer by the MSDP peer-to-peer sending this SA message, receiving in list in beta pruning
Record the corresponding relation between the RP address carrying in this SA message and this MSDP peer-to-peer.
In the embodiment of the present invention, this MSDP peer-to-peer carries cutting of RP address from other MSDP peer-to-peers receiving
After branch message, this MSDP peer-to-peer receives in beta pruning and records the RP address carrying in this prune packet and other MSDP pair in list
Deng the corresponding relation between body；Further, this MSDP peer-to-peer sends to other MSDP peer-to-peers and carries cutting of RP address
After branch message, other MSDP peer-to-peers are receiving after the prune packet of this MSDP peer-to-peer, receive in list in beta pruning and remember
Record the corresponding relation between the RP address carrying in this prune packet and 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 are described in detail.
Assume Router A periodicity to MSDP peer-to-peer（Router B and Router C）Send SA message, this SA message
In carry information about multicast source in PIM-SM1 domain, and in this SA message, carry the IP address of RP1, carry in SA message
RP address is the IP address of RP1.
For step 201, Router B, when receiving from the SA message of Router A first time, is carried out to this SA message
Rpf check, now rpf check success.Router C first time receive from the SA message of Router A when, to this SA message
Carry out rpf check, now rpf check success.
The RP address carrying in using SA message for step 202, Router B（The i.e. IP address of RP1）Inquiry beta pruning
When receiving list, it is sky because now beta pruning receives list, therefore beta pruning receives not recording in this SA message in list and carries
RP address corresponding other MSDP peer-to-peers, therefore Router B needs to forward this SA message to Router C.Router C
The RP address carrying in using SA message（The i.e. IP address of RP1）When inquiry beta pruning receives list, because now beta pruning receives
List is sky, and therefore beta pruning receives and do not record the RP address carrying in this SA message corresponding other MSDP equity in list
Body, therefore Router C need to forward this SA message to Router B.
For step 201, Router B, when receiving from the SA message that Router C forwards, is carried out to this SA message
Rpf check, now rpf check failure.Router C, when receiving from the SA message that Router B forwards, enters to this SA message
Row rpf check, now rpf check failure.
For step 203, Router B is receiving after the SA message that Router C forwards, and abandons this SA message,
The RP address carrying in this SA message is recorded in beta pruning transmission list（The i.e. IP address of RP1）With Router C（Send this SA
The MSDP peer-to-peer of message）Between corresponding relation, as shown in table 3.Router B sends prune packet to Router C afterwards,
The RP address carrying in SA message is carried in this prune packet（The i.e. IP address of RP1）.Router C is derived from receiving
After the prune packet of Router B, receive in list in beta pruning and record the RP address carrying in this prune packet（The i.e. IP ground of RP1
Location）Corresponding relation and Router B between, as shown in table 4.
For step 203, Router C is receiving after the SA message that Router B forwards, and abandons this SA message,
The RP address carrying in this SA message is recorded in beta pruning transmission list（The i.e. IP address of RP1）With Router B（Send this SA
The MSDP peer-to-peer of message）Between corresponding relation, as shown in table 5.Router C sends prune packet to Router B afterwards,
The RP address carrying in SA message is carried in this prune packet（The i.e. IP address of RP1）.Router B is derived from receiving
After the prune packet of Router C, receive in list in beta pruning and record the RP address carrying in this prune packet（The i.e. IP ground of RP1
Location）Corresponding relation and Router C between, as shown in table 6.
Table 3 beta pruning transmission 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 transmission 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 be subsequently received again by from the SA message of Router A when, this SA message is carried out
Rpf check, now rpf check success.Router C be subsequently received again by from the SA message of Router A when, to this SA message
Carry out rpf check, now rpf check success.
The RP address carrying in using SA message for step 202, Router B（The i.e. IP address of RP1）Inquiry beta pruning
When receiving list, now beta pruning receives list as shown in table 6, and that is, beta pruning receives in list the RP address carrying in this SA message
（The i.e. IP address of RP1）Corresponding other MSDP peer-to-peer（I.e. Router C）, now explanation Router C do not need from
Router B receives the SA message of the IP address of this RP1, and therefore Router B does not need to forward this SA message to Router C.
The RP address carrying in using SA message for step 202, Router C（The i.e. IP address of RP1）Inquiry beta pruning
When receiving list, now beta pruning receives list as shown in table 4, and that is, beta pruning receives in list the RP address carrying in this SA message
（The i.e. IP address of RP1）Corresponding other MSDP peer-to-peer is Router B）, now illustrate that Router B does not need from Router
C receives the SA message of the IP address of this RP1, and therefore Router C does not need to forward this SA message to Router B.
In the embodiment of the present invention, this MSDP peer-to-peer record in beta pruning transmission list the RP address carrying in SA message with
After corresponding relation between other MSDP peer-to-peers, if this MSDP peer-to-peer detects the RP address carrying in this SA message
Corresponding rpf check opposite end is other MSDP peer-to-peer, then this MSDP peer-to-peer also needs to delete from beta pruning transmission list and is somebody's turn to do
Corresponding relation between the RP address carrying in SA message and other MSDP peer-to-peer, and send grafting to other MSDP peer-to-peers
The RP address carrying in this SA message is carried in message, and this graft packet.
In the embodiment of the present invention, MSDP peer-to-peer beta pruning receive in list record RP address and other MSDP peer-to-peers it
Between corresponding relation after, if MSDP peer-to-peer receives the graft packet from other MSDP peer-to-peers（This graft packet
In carry RP address）, then MSDP peer-to-peer delete this and transfer in addition it is also necessary to receive in list in beta pruning after receiving graft packet
The corresponding relation being informed of a case between the RP address carrying in literary composition and other MSDP peer-to-peer；Further, this MSDP peer-to-peer is to it
After its MSDP peer-to-peer sends the graft packet carrying RP address, other MSDP peer-to-peers are receiving from this MSDP equity
The RP address carrying in this graft packet and this MSDP pair is deleted in list in addition it is also necessary to receive in beta pruning after the graft packet of body
Deng the corresponding relation between body.
Continuing with the application scenarios shown in Fig. 1, the said process of the embodiment of the present invention is described in detail.
Assume that on Router B, the beta pruning transmission list shown in Maintenance Table 3 and the beta pruning shown in table 6 receive list, Router
Beta pruning transmission list shown in the upper Maintenance Table of C 5 and the beta pruning shown in table 4 receive list.
After link failure between Router B and Router A, the IP address that Router B detects RP1 is corresponding
Rpf check opposite end is Router C, and based on this, Router B also needs to delete RP1's the beta pruning transmission list shown in from table 3
Corresponding relation between IP address and Router C.Further, Router B also needs to send graft packet to Router C,
And in this graft packet, carry the IP address of RP1.Further, Router C is receiving the graft packet from Router B
Afterwards in addition it is also necessary to the beta pruning shown in from table 4 receives the corresponding relation deleting between the IP address of RP1 and Router B list.
Based on this, Router C be received again by from the SA message of Router A when, this SA message can be sent to Router B, with
Ensure that Router B can receive the SA message from Router A.
After link failure between Router C and Router A, the IP address that Router C detects RP1 is corresponding
Rpf check opposite end is Router B, and based on this, Router C also needs to delete RP1's the beta pruning transmission list shown in from table 5
Corresponding relation between IP address and Router B.Further, Router C also needs to send graft packet to Router B,
And in this graft packet, carry the IP address of RP1.Further, Router B is receiving the graft packet from Router C
Afterwards in addition it is also necessary to the beta pruning shown in from table 6 receives the corresponding relation deleting between the IP address of RP1 and Router C list.
Based on this, Router B be received again by from the SA message of Router A when, this SA message can be sent to Router C, with
Ensure that Router C can receive the SA message from Router A.
In a kind of specific implementation of the embodiment of the present invention, the prune packet of interaction and grafting between MSDP peer-to-peer
The form schematic diagram of message is respectively as shown in Figure 3 and Figure 4.Wherein, it is required to carry RP ground in this prune packet and graft packet
Location, and prune packet and graft packet can be made a distinction by different types, for example：The type of prune packet is 8, grafting
The type of message is 9.
In sum, in the embodiment of the present invention, MSDP peer-to-peer pass through beta pruning receive list in record RP address and its
Corresponding relation between its MSDP peer-to-peer, carries this RP to show that MSDP peer-to-peer does not need to send to other MSDP peer-to-peers
The SA message of address；Based on this, MSDP peer-to-peer is when receiving SA message, if beta pruning receives record in list and has this SA message
In the RP address corresponding MSDP peer-to-peer that carries, then this MSDP peer-to-peer do not need to this RP address corresponding MSDP peer-to-peer
Forward this SA message, thus avoiding each MSDP peer-to-peer to receive the SA message of bulk redundancy.
Based on the inventive concept same with said method, in the embodiment of the present invention, additionally provide a kind of Multicast Source Discovery Protocol
MSDP peer-to-peer, applies in the network including multiple MSDP peer-to-peers, as shown in figure 5, described MSDP peer-to-peer specifically includes：
Logging modle 11, for receiving the prune packet from other MSDP peer-to-peers, carries in described prune packet
Convergent point RP address；And after receiving described prune packet, receive in beta pruning and in list, record described RP address and described other
Corresponding relation between MSDP peer-to-peer；
Detection module 12, forwards RPF for when receiving information source effective SA message, described SA message is carried out with inverse path
Check；And in the rpf check success of described SA message, connect using the beta pruning described in RP address lookup carrying in described SA message
Receive list；
Processing module 13, for having the RP address carrying in described SA message to correspond to when described beta pruning receives record in list
MSDP peer-to-peer when, not to this RP address corresponding MSDP peer-to-peer forward described SA message.
Described processing module 13, is additionally operable to the other MSDP peer-to-peers to outside the corresponding MSDP peer-to-peer of this RP address and turns
Send out SA message described.
Described logging modle 11, is additionally operable to after carrying out rpf check to described SA message, in the RPF of described SA message
When checking unsuccessfully, beta pruning transmission list records the RP address carrying in described SA message and the MSDP sending described SA message
Corresponding relation between peer-to-peer；
Described processing module 13, is additionally operable to after carrying out rpf check to described SA message, in the RPF of described SA message
When checking unsuccessfully, abandon described SA message, and send prune packet, this beta pruning report to the MSDP peer-to-peer sending described SA message
Carry, in literary composition, the RP address carrying in described SA message；Prune packet is being received by the MSDP peer-to-peer sending described SA message
Afterwards, receive, in beta pruning, the corresponding relation recording in list between the RP address carrying in described SA message and this MSDP peer-to-peer.
Described processing module 13, is additionally operable to record the RP address carrying in described SA message in beta pruning transmission list and send out
After sending the corresponding relation between the MSDP peer-to-peer of described SA message, the RP address pair that carries in described SA message is detected
When the rpf check opposite end answered is the MSDP peer-to-peer sending described SA message, delete described SA message from beta pruning transmission list
In corresponding relation between the RP address that carries and the MSDP peer-to-peer sending described SA message, and to sending described SA message
MSDP peer-to-peer sends graft packet；Transferring from this MSDP peer-to-peer is being received by the MSDP peer-to-peer sending described SA message
It is informed of a case after literary composition, delete corresponding between the RP address carrying in described SA message and this MSDP peer-to-peer in beta pruning reception list
Relation；
After beta pruning receives the corresponding relation recording in list between described RP address and described other MSDP peer-to-peer,
Receive the graft packet from described other MSDP peer-to-peer, in described graft packet, carry RP address；Transfer described in receive
It is informed of a case after literary composition, receive in described beta pruning and in list, delete the RP address carrying in described graft packet and described other MSDP pair
Deng the corresponding relation between body.
In the embodiment of the present invention, different MSDP peer-to-peers is located at identical Protocol independent multicast-sparse mode PIM-SM
Domain；Or, different MSDP peer-to-peers is located at different pim-sm domains.
Wherein, the modules of apparatus of the present invention can be integrated in one it is also possible to be deployed separately.Above-mentioned module can be closed
And for a module it is also possible to be further split into multiple submodule.
Through the above description of the embodiments, those skilled in the art can be understood that the present invention can be by
Software adds the mode of necessary general hardware platform to realize naturally it is also possible to pass through hardware, but the former is more in many cases
Good embodiment.Based on such understanding, technical scheme substantially contributes to prior art in other words
Partly can be embodied in the form of software product, this computer software product is stored in a storage medium, if including
Dry instruction is with so that a computer equipment（Can be personal computer, server, or network equipment etc.）Execute this
Method described in each embodiment bright.
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 stream
Journey is not necessarily implemented necessary to the present invention.
It will be appreciated by those skilled in the art that module in device in embodiment can be carried out point according to embodiment description
It is distributed in the device of embodiment and be disposed other than in one or more devices of the present embodiment it is also possible to carry out respective change.On
The module stating embodiment can merge into a module it is also possible to be further split into multiple submodule.
The embodiments of the present invention are for illustration only, do not represent the quality of embodiment.
The several specific embodiments being only the present invention disclosed above, but, the present invention is not limited to this, any ability
What the technical staff in domain can think change all should fall into protection scope of the present invention.
Claims (8)
1. the transmission method of the effective SA message of a kind of information source, the method is applied to including multiple Multicast Source Discovery Protocol MSDP equity
It is characterised in that the method comprises the following steps in the network of body：
MSDP peer-to-peer, when receiving SA message, carries out inverse path and forwards rpf check to described SA message；If rpf check
Success, then receive list using the RP address lookup beta pruning carrying in described SA message；If described beta pruning receives in list remembered
Record has the RP address corresponding MSDP peer-to-peer carrying in described SA message, then do not turn to this RP address corresponding MSDP peer-to-peer
Send out SA message described；
If rpf check failure, described MSDP peer-to-peer abandons described SA message, and records described SA in beta pruning transmission list
Corresponding relation between the RP address carrying in message and the MSDP peer-to-peer sending described SA message, and report to sending described SA
The MSDP peer-to-peer of literary composition sends prune packet, carries the RP address carrying in described SA message in this prune packet；By transmission institute
The MSDP peer-to-peer stating SA message is receiving after the prune packet of described MSDP peer-to-peer, receives in list in beta pruning and records
Corresponding relation between the RP address carrying in described SA message and described MSDP peer-to-peer.
2. the method for claim 1 is it is characterised in that methods described also includes：
Other MSDP peer-to-peers to outside the corresponding MSDP peer-to-peer of this RP address for the described MSDP peer-to-peer forward described SA report
Literary composition.
3. the method for claim 1 it is characterised in that
Described MSDP peer-to-peer records the RP address carrying in described SA message in beta pruning transmission list and sends described SA report
After corresponding relation between the MSDP peer-to-peer of literary composition, methods described also includes：Described MSDP peer-to-peer detects described SA report
When the RP address corresponding rpf check opposite end carrying in literary composition is the MSDP peer-to-peer sending described SA message, send row from beta pruning
The corresponding relation between the RP address carrying in described SA message and the MSDP peer-to-peer sending described SA message is deleted in table, and
Send graft packet to the MSDP peer-to-peer sending described SA message；Receiving by the MSDP peer-to-peer sending described SA message
From after the graft packet of described MSDP peer-to-peer, receive in list in beta pruning and delete the RP address carrying in described SA message and institute
State the corresponding relation between MSDP peer-to-peer；
The MSDP peer-to-peer sending SA message receives the MSDP recording described RP address and transmission prune packet in list in beta pruning
After corresponding relation between peer-to-peer, methods described also includes：The MSDP peer-to-peer reception sending SA message is cut from transmission
The graft packet of the MSDP peer-to-peer of branch message, carries RP address in described graft packet；Send the MSDP equity of SA message
Body after receiving described graft packet, described beta pruning receive list in delete the RP address carrying in described graft packet with
Send the corresponding relation between the MSDP peer-to-peer of prune packet.
4. the method as described in any one of claim 1-3 it is characterised in that
Different MSDP peer-to-peers is located at identical Protocol independent multicast-sparse mode pim-sm domain；Or, different MSDP pairs
It is located at different pim-sm domains Deng body.
5. a kind of Multicast Source Discovery Protocol MSDP peer-to-peer, applies in the network including multiple MSDP peer-to-peers, its feature exists
In described MSDP peer-to-peer specifically includes：
Detection module, forwards rpf check for when receiving information source effective SA message, described SA message is carried out with inverse path；
And in the rpf check success of described SA message, receive list using the RP address lookup beta pruning carrying in described SA message；
Processing module, for having, when described beta pruning receives record in list, the corresponding MSDP in RP address carrying in described SA message
During peer-to-peer, do not forward described SA message to this RP address corresponding MSDP peer-to-peer；
Logging modle, for after rpf check is carried out to described SA message, in the rpf check failure of described SA message,
Record in beta pruning transmission list between the RP address carrying in described SA message and the MSDP peer-to-peer sending described SA message
Corresponding relation；
Described processing module, is additionally operable to, after carrying out rpf check to described SA message, lose in the rpf check of described SA message
When losing, abandon described SA message, and send prune packet to the MSDP peer-to-peer sending described SA message, take in this prune packet
RP address with carrying in described SA message；By sending the MSDP peer-to-peer of described SA message after receiving prune packet, cutting
Scion grafting is received in list and is recorded between the RP address carrying in described SA message and the MSDP peer-to-peer sending described prune packet
Corresponding relation.
6. MSDP peer-to-peer as claimed in claim 5 it is characterised in that
Described processing module, the other MSDP peer-to-peers forwardings being additionally operable to outside the corresponding MSDP peer-to-peer of this RP address are described
SA message.
7. MSDP peer-to-peer as claimed in claim 5 it is characterised in that
Described processing module, is additionally operable to record the RP address carrying in described SA message in beta pruning transmission list and sends described
After corresponding relation between the MSDP peer-to-peer of SA message, the RP address carrying in described SA message is detected is corresponding
When rpf check opposite end is the MSDP peer-to-peer sending described SA message, deletes from beta pruning transmission list in described SA message and take
Corresponding relation between the RP address of band and the MSDP peer-to-peer sending described SA message, and the MSDP to the described SA message of transmission
Peer-to-peer sends graft packet；Received from send prune packet MSDP pair by the MSDP peer-to-peer sending described SA message
After the graft packet of body, receive in beta pruning and in list, delete the RP address carrying in described SA message and transmission prune packet
Corresponding relation between MSDP peer-to-peer；
Beta pruning receive list in record described RP address and send prune packet MSDP peer-to-peer between corresponding relation it
Afterwards, receive the graft packet from the MSDP peer-to-peer sending prune packet, in described graft packet, carry RP address；Receiving
To after described graft packet, delete, in described beta pruning reception list, the RP address carrying in described graft packet and cut with transmission
Corresponding relation between the MSDP peer-to-peer of branch message.
8. the MSDP peer-to-peer as described in any one of claim 5-7 it is characterised in that
Different MSDP peer-to-peers is located at identical Protocol independent multicast-sparse mode pim-sm domain；Or, different MSDP pairs
It is located at different pim-sm domains Deng body.
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 CN103516616A (en) | 2014-01-15 |
| CN103516616B true 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) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639446B (en) * | 2015-02-03 | 2018-05-08 | 新华三技术有限公司 | A kind of information about multicast source acquisition methods and device |
| CN109963333B (en) * | 2017-12-26 | 2022-09-20 | 成都鼎桥通信技术有限公司 | Multicast resource allocation method and device based on service area |
Citations (3)
| 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 |
| CN102075417A (en) * | 2010-09-30 | 2011-05-25 | 杭州华三通信技术有限公司 | Multicast cutting method, protocol independent multicast router, and two-layer exchanger |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5210245B2 (en) * | 2009-05-28 | 2013-06-12 | アラクサラネットワークス株式会社 | Network relay device and inter-network relay method |
-
2013
- 2013-10-18 CN CN201310493597.3A patent/CN103516616B/en active Active
Patent Citations (3)
| 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 |
| CN102075417A (en) * | 2010-09-30 | 2011-05-25 | 杭州华三通信技术有限公司 | Multicast cutting method, protocol independent multicast router, and two-layer exchanger |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103516616A (en) | 2014-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102075417B (en) | Multicast cutting method, protocol independent multicast router | |
| CN100456740C (en) | Layer 2 switch | |
| US20050180440A1 (en) | Method of transporting a multipoint stream in a local area network and device for connection implementing the method | |
| CN101605103B (en) | Method and apparatus for static forwarding multicast data | |
| JP3931175B2 (en) | Explicit multicast tunneling service method and apparatus | |
| US10237189B2 (en) | System and method for distance-based interest forwarding | |
| CN102957573B (en) | Path detection realizing method and node | |
| CN100542127C (en) | A kind of method of realizing group broadcasting based on multiservice transport platform | |
| CN101247210B (en) | Method for implementing multicast forwarding tree based on multicast source discovering protocol | |
| CN101232392B (en) | Method for notifying multicast source between MSDP and PIM | |
| US8243585B2 (en) | Method and apparatus for fault-resilient multicast using multiple sources | |
| CN104052667A (en) | Packet processing method and device | |
| CN103546381A (en) | Method, device and system for creating bidirectional multicast distribution trees on basis of interior gateway protocol | |
| CN102739521B (en) | A kind of multicast service realizing method and equipment thereof | |
| CN100596141C (en) | Method for establishing optimistically PIM-DM route table entry | |
| CN104539545B (en) | Method for forwarding multicast message and equipment in TRILL network | |
| CN103685032B (en) | Message forwarding method and network address translation services device | |
| CN106685828A (en) | Message transmitting method and apparatus | |
| CN103516616B (en) | Transmission method and equipment for SA messages | |
| CN102377646A (en) | Forwarding chip, network switching system and multicast implementation method | |
| CN104052672A (en) | Multicast achieving method and device based on LISP | |
| CN104468139A (en) | Multicast data message transmitting method and device | |
| CN103391251B (en) | A kind of method and apparatus reducing redundant flow in PBB network | |
| US10833808B1 (en) | Multicast error detection and recovery | |
| CN102412976A (en) | Method and device for processing multicase messages in provider backbone bridge (PBB) network |
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 |
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. |
|
| CP03 | Change of name, title or address |