CN103095473B - The source-specific multicast method of crossing virtual private networks network, device and the network equipment - Google Patents
The source-specific multicast method of crossing virtual private networks network, device and the network equipment Download PDFInfo
- Publication number
- CN103095473B CN103095473B CN201310029552.0A CN201310029552A CN103095473B CN 103095473 B CN103095473 B CN 103095473B CN 201310029552 A CN201310029552 A CN 201310029552A CN 103095473 B CN103095473 B CN 103095473B
- Authority
- CN
- China
- Prior art keywords
- multicast
- vpn
- address information
- backup
- source address
- 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 kind of source-specific multicast method across VPN, device and the network equipment, in the method, PE sets up the backup multicast table of the main multicast table of CE, PE is in the process of carrying out IGMPv3 and IGMPv2 switching, multicast source address information in main multicast table and backup multicast table is inconsistent, the multicast forwarding across VPN is carried out according to the multicast source address in backup multicast table, when main multicast table is consistent with the multicast source address information in backup multicast table, the multicast forwarding across VPN is carried out according to the multicast source address information in main multicast table, can be reliable and effective reference frame to back up multicast table, realize carrying out forwarding across the source-specific multicast of VPN to CE, can solve in prior art PE carry out IGMPv3 and IGMPv2 switch time, cause the problem that the source-specific multicast across VPN of CE is stopped.
Description
Technical field
The present invention relates to the network communications technology, particularly, relate to a kind of source-specific multicast method of crossing virtual private networks network, device and the network equipment.
Background technology
Based on multiprotocol label switching (Multi-ProtocolLabelSwitching, MPLS) VPN (virtual private network) (VirtualPrivateNetwork, VPN) third layer (L3VPN) is that the one that provides of service provider is based on edge router (ProviderEdgeRouter, PE) VPN technologies, it uses Border Gateway Protocol (BorderGatewayProtocol, BGP) at service provider (ServiceProvider, SP) key Web realease VPN route, uses MPLS technology to forward VPN message on SP backbone network.And multicasting VPN is a kind of technology based on multicast packet in MPLSL3VPN Internet communication VPN, its network basic model as shown in Figure 1:
Communication terminal (CommunicationEdge, CE), is positioned at the equipment of customer network edge, belongs to the VPN of user in logic, and certain interface of CE is directly connected with the operator PE of SP, and CE can be main frame also can be router or switch; CE1 belongs to VPN1 in FIG, and CE2 belongs to VPN2, CE1 with CE2 is connected with PE1 respectively, and CE3 belongs to VPN1, and CE4 belongs to VPN2, CE3 with CE4 is connected with PE2 respectively, and the upper interface be connected with CE of PE can be called private network interface.
PE is the edge device of the backbone network that SP provides, and as shown in fig. 1 PE1 and PE2, PE apparatus logic belongs to SP, PE and CE is direct-connected, and a PE can connect multiple CE belonging to similar and different VPN.
Vendor equipment (ProviderRouter, P), is positioned at the nucleus equipment of SP backbone network.P discord CE is connected, and is responsible for route and the fast-forwarding of public network.
Network topology in Fig. 1, running the multicast protocol Multicast Routing built in VPN in VPN is also VPN forwarding multicasting stream; When PE1 receives the multicast data flow that CE1 and CE2 arrive, convert thereof into the multicast packet form that public network can propagate and propagate in public network, make on its PE2 propagating into other VPN website of connection; Time PE2 receives public network multicast packet, its decapsulation is forwarded in corresponding VPN website.
And be the expansion to above-mentioned technology across VPN multicast, namely the expanded application (being called for short Extranet-MVPN) of multicasting VPN makes the multicast source in a multicasting VPN multicast data flow can be distributed to the multicast reception end of other multicasting VPN.Namely, in the topological structure shown in Fig. 1, multicast source and multicast reception end may reside in VPN1 and VPN2, by PE1 equipment across VPN multicast functionality, the program request between different VPN can be realized.
Multicast reception end has sparse mode Protocol Independent Multicast (ProtocolIndependentMulticast-SparseMode when VPN accesses, PIM-SM) and source-specific multicast (ProtocolIndependentMulticast-Source-SpecificMulticast, PIM-SSM) two kinds of modes access.Wherein PIM-SSM access way is the multicast mode of assigned source, needs by running multicast member management protocol (InternetGroupManagementProtocol, the IGMP) third edition this (IGMPv3) protocol realization in the Internet between CE and PE.
When applying IGMPv3 and realizing forwarding across the source-specific multicast of VPN, there is a PE and v2/v3 handover operation is carried out to igmp version, cause the problem of interrupting across VPN multicast data flow, break period is a minute rank, this problem is that application IGMPv3 and PIM-SSM realizes across a leak in the multicast forwarding technology of VPN, and detailed process is as follows:
Scene as shown in Figure 1, if multicast reception end is CE1, multicast source is CE2, CE2 address is A, PE1, CE1 and CE2 main frame all runs the multicast on demand that IGMPv3 agreement is carried out across VPN, such as belong to the flux of multicast that the CE1 program request of VPN1 belongs to the CE2 of VPN2, CE2 is multicast source, CE1 is multicast reception end, (Query) message communicates with report (Report) message to use the protocol massages of IGMPv3 namely to inquire between PE1 and CE1, whether PE1 regularly sends the inquiry of Query message under normal circumstances has multicast reception end to exist, CE1 replys the existence that Report message notices multicast receivers, PE1 generates according to the Report message received and safeguards multicast member relation and multicast forwarding list item, the mark of the multicast group of the flux of multicast of CE1 program request and the address information of multicast source is included in multicast forwarding list item.
When PE1 carries out v2/v3 handover operation to igmp version, by version from IGMPv3(hereinafter referred to as v3 version) switch to IGMPv2(hereinafter referred to as v2 version), switch back IGMPv3 again, PE1 is by the Query message of the Query message and v3 version that send v2 version at short notice, by the Query message of the Query message and v3 version that receive v2 version at short notice, there is following processing procedure in CE1 equipment:
After step one, PE1 switch to IGMPv2 from IGMPv3, CE1 equipment first receives the Query of the v2 version from PE1, that now CE1 runs is IGMPv3, according to IGMPv3 protocol processes flow process, start the compatibility mechanism to IGMPv2 version, CE1 equipment can set the inquiry timer of a compatible v2 version, time is 255 seconds, the Query message of v2 version or v3 version no matter is received within this 255 second time, CE1 replys the Report message of v2 version, further, in 255 seconds of timing, CE1 sent the Report message of v2 version every 60 seconds to PE1;
Step 2, because CE1 replys the Report message of v2 version, after PE1 equipment receives, think the multicast receivers that there is v2 version, then start the compatibility mechanism to v2 version, the Report message that PE1 often receives a v2 just generates the timer that corresponds to v2 version, time is 250 seconds, and in IGMP multicast member table, generate the exclude(NULL of this multicast member CE1) information table, this list item represents in the CE that PE connects has the recipient of multicast to need to receive the flow of this multicast group, exclude(NULL) expression CE can receive the flux of multicast that any multicast source sends.
But owing in this scene environment being the VPN access of application SSM, multicast data flow need according to shortest path tree (ShortestPathTree, SPT) multicast forwarding is carried out, namely with multicast source S for root node, recipient is the multicast transmit tree of leaf node, flux of multicast directly walks the shortest path from multicast source to multicast receivers, PE carries out the place must knowing the multicast source of specifying when specifying the flux of multicast of information source to forward according to SPT, but PE1 does not form for the multicast forwarding list item of CE1 the list item being with source address, only have exclude(NULL) list item, what the multicast source address causing PE1 not know that CE1 specifies is, SPT cannot be formed to CE1, also the forwarding of flux of multicast just cannot be carried out to CE1, cause CE1 stops, this process will continue about 255 seconds.
3, after CE1 timing 255 seconds then, CE1 equipment stops the Report message sending v2 version to PE1, and after the Query message receiving the v3 version that PE1 sends, CE1 changes the Report message of replying v3 version into.After PE1 receives this v3 version Report message, the EXCLUDE(NULL of CE1 owing to being formed before existing) list item, according to IGMPv3 agreement, the particular content of this group membership's information table will be changed to EXCLUDE(A), A represents the IP address in certain specific multicast source and the IP address of CE2, at this moment multicast member information table is EXCLUDE(A), represent the multicast data flow got rid of and namely do not receive this source address A and CE2 multicast source and send, cause now CE2 to CE1 will still cannot get through across VPN multicast data flow, this process will continue about 250 seconds, namely also PE1 receives the Report message of last v2 version that CE sends in 255 seconds in timing and timing 250 seconds.
4, PE1 is after the Report message timing 250 seconds for last v2 version then, according to IGMPv3 agreement, PE1 can from EXCLUDE(A by the multicast member information table for CE1) be rewritten as INCLUDE(A), the assigned address received should be that the flux of multicast of A is transmitted to CE1 by expression PE1, now, PE1 equipment could generate SPT for CE1, just can get through across VPN multicast data flow, and the cutout time probably continues 255+250 second.
To be realized by IGMPv3 forwarding across the source-specific multicast of VPN existing as seen, there is PE and IGMPv2 and IGMPv3 version occurs when switching, cause the problem that the source-specific multicast across VPN stops.
Summary of the invention
In view of this, embodiments provide a kind of source-specific multicast method across VPN, device and the network equipment, in order to solve existing by IGMPv3 realize across VPN source-specific multicast forward in, when there is PE generation IGMPv2 and IGMPv3 version switching, the problem that the source-specific multicast across VPN caused stops.
Embodiment of the present invention technical scheme is as follows:
A kind of source-specific multicast method of crossing virtual private networks network VPN, comprise: provider edge router PE determines described PE to run the Internet this IGMPv3 of the multicast member management protocol third edition in detection, and detect when the communication terminal CE belonging in VPN that determines to be connected with described PE runs IGMPv3 and source-specific multicast pattern, the main multicast table set up according to the report message from the IGMPv3 version of described CE is backed up, the multicast source address information of the flux of multicast across VPN of described CE program request is included in described main multicast table and backup multicast table, described PE is in the process of carrying out IGMPv3 and IGMPv2 switching, multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
The source-specific multicast device of a kind of crossing virtual private networks network VPN, comprise: backup module, determine described PE to run the Internet this IGMPv3 of the multicast member management protocol third edition for detecting at described device place PE, and detect when the communication terminal CE belonging in VPN that determines to be connected with described PE runs IGMPv3 and source-specific multicast pattern, the main multicast table that described PE sets up according to the report message of the IGMPv3 version from described CE is backed up, the multicast source address information of the flux of multicast across VPN of described CE program request is included in described main multicast table and backup multicast table, forwarding module, for carrying out in the process of IGMPv3 and IGMPv2 switching at described device place PE, multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
A kind of network equipment, comprises the source-specific multicast device of crossing virtual private networks network as above.
According to the technical scheme of the embodiment of the present invention, PE sets up the backup multicast table of the main multicast table of CE, carry out in the different phase of IGMPv3 and IGMPv2 switching at PE, PE can modify to the content in the multicast source address item in main multicast table, but can not modify to the multicast table of backup, such PE is in the process of carrying out IGMPv3 and IGMPv2 switching, multicast source address information in main multicast table and backup multicast table is inconsistent, the multicast forwarding across VPN is carried out according to the multicast source address in backup multicast table, can be reliable and effective reference frame to back up multicast table, carry out in the process of IGMPv3 and IGMPv2 switching at PE, realization carries out the multicast forwarding across VPN to CE, can solve in prior art PE occur IGMP v2 and v3 version switch time, main multicast table according to constantly amendment forwards, cause the problem that the source-specific multicast across VPN of CE is stopped.
Other features and advantages of the present invention will be set forth in the following description, and, partly become apparent from specification, or understand by implementing the present invention.Object of the present invention and other advantages realize by structure specifically noted in write specification, claims and accompanying drawing and obtain.
Accompanying drawing explanation
Fig. 1 is the scene schematic diagram across VPN multicast forwarding in prior art;
The workflow of the source-specific multicast method across VPN that Fig. 2 provides for the embodiment of the present invention;
The structured flowchart of the source-specific multicast device across VPN that Fig. 3 provides for the embodiment of the present invention;
Another structured flowchart of the source-specific multicast device across VPN that Fig. 4 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with accompanying drawing, embodiments of the invention are described, should be appreciated that embodiment described herein is only for instruction and explanation of the present invention, is not intended to limit the present invention.
Realize in the source-specific multicast forwarding across VPN for existing by IGMPv3, when there is PE generation IGMPv2 and IGMPv3 version switching, the problem causing the source-specific multicast across VPN to stop, embodiments provides a kind of source-specific multicast scheme across VPN, to solve this problem.In the technical scheme that the embodiment of the present invention provides, provide a kind of back mechanism of main multicast table and one and select a good opportunity and easily show forwarding mechanism, according to back mechanism, PE sets up the backup multicast table of the main multicast table of CE, easily forwarding mechanism is shown according to selecting a good opportunity, carry out in the different phase of IGMPv3 and IGMPv2 switching at PE, PE can modify to the content in the multicast source address item in main multicast table, but can not modify to the multicast table of backup, such PE is in the process of carrying out IGMPv3 and IGMPv2 switching, multicast source address information in main multicast table and backup multicast table is inconsistent, the multicast forwarding across VPN is carried out according to the multicast source address in backup multicast table, when main multicast table is consistent with the multicast source address information in backup multicast table, the multicast forwarding across VPN is carried out according to the multicast source address information in main multicast table, can be reliable and effective reference frame to back up multicast table, carry out in the process of IGMPv3 and IGMPv2 switching at PE, realization carries out the multicast forwarding across VPN to CE, can solve in prior art PE occur IGMP v2 and v3 version switch time, main multicast table according to constantly amendment forwards, cause the problem that the source-specific multicast across VPN of CE is stopped.
Below the embodiment of the present invention is described in detail.
Fig. 2 shows the workflow of the source-specific multicast method across VPN that the embodiment of the present invention provides, and comprising:
Step 201, PE determine described PE runs IGMPv3 in detection, and detect when the CE belonging in VPN that determines to be connected with described PE runs IGMPv3 and SSM, the main multicast table set up according to the report message from the IGMPv3 version of CE is backed up, in main multicast table and backup multicast table, includes the multicast source address information of the flux of multicast across VPN of CE program request;
Particularly, main multicast table and backup multicast table in can also comprise the flux of multicast across VPN of CE program request multicast mark;
Further, PE can also add the address information of CE in backup multicast table, and address information can be Internet protocol (IP, InternetProtocol) address and media interviews control (MAC, MediaAccessControl) address of CE;
By above-mentioned back mechanism, correct, reliable and effective multicast source address information can be provided for follow-up repeating process;
Step 202, PE carrying out in the process that IGMPv3 and IGMPv2 switch, the multicast source address information in main multicast table and backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in backup multicast table is carried out across VPN to CE;
Particularly, after PE switches to IGMPv2 from IGMPv3, PE sends the inquiry message (Query) of IGMPv2 to CE, CE starts the compatibility mechanism to IGMPv2, CE sets the inquiry timer of a compatible IGMPv2, time is 255 seconds, and in 255 seconds of timing, CE sent the report message (Report) of IGMPv2 every 60 seconds to PE, PE receives the report message of the IGMPv2 that CE replys, then start the compatibility mechanism to IGMPv2 version, the report message that PE often receives an IGMPv2 just generates the timer that corresponds to v2 version, time is 250 seconds, and the multicast source address information table of this CE in main multicast table is rewritten as exclude(NULL), namely the flux of multicast that the equipment not forwarding any multicast source address to CE sends, now main multicast table is with backup multicast table, the multicast source address information of CE is inconsistent, if now forwarded according to the multicast source address information in master meter, any flux of multicast cannot be forwarded to CE,
Compatible timing is carried out after 255 seconds for IGMPv2 at CE, CE stops the report message sending IGMPv2 to PE, after the inquiry message receiving the IGMPv3 that PE sends, CE changes the report message of replying IGMPv3 into, after PE receives the report message of this IGMPv3, the exclude(NULL of CE owing to being formed before existing) list item, according to IGMPv3 agreement, the multicast source address information of CE is changed to exclude(A), A represents the IP address in certain specific multicast source, represent and do not forward to CE the flux of multicast that this source address A sends, now main multicast table is with backup multicast table, the multicast source address information of CE is inconsistent, if now forwarded according to the multicast source address information in master meter, any flux of multicast cannot be forwarded to CE,
Therefore, when PE receives report message from the IGMPv2 of described CE and multicast source address information in main multicast table and backup multicast table is inconsistent, or when PE receives report message from the IGMPv3 of CE and multicast source address information in main multicast table and backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in backup multicast table is carried out across VPN to CE;
PE is after the report message timing 250 seconds for last IGMPv2 then, according to IGMPv3 agreement, PE can from EXCLUDE(A by the multicast member information table for CE) be rewritten as INCLUDE(A), the assigned address received should be that the flux of multicast of A is transmitted to CE by expression PE, now, in main multicast table CE multicast source address information amendment get back to PE carry out IGMPv3 and IGMPv2 switch before situation, consistent with the source address information of CE in backup multicast table in main multicast table, multicast forwarding can be carried out according to the source address information in main multicast table;
Like this, when main multicast table is consistent with the multicast source address information in backup multicast table, according to the multicast forwarding that the multicast source address in main multicast list carries out across VPN to CE;
Particularly, a flux of multicast can be received at PE, carry out flux of multicast forward time, according to the mark of this flux of multicast, inquire about main multicast table whether consistent with the multicast source address information of the CE of this flux of multicast of program request mark in backup multicast table, in the case of inconsistencies, according to situation about recording in backup multicast table, this flux of multicast is transmitted to the CE of this flux of multicast of program request, when consistent, carry out the forwarding of flux of multicast according to situation about recording in main multicast table.
Easily show forwarding mechanism according to above-mentioned selecting a good opportunity, the correct flux of multicast forwarded across the appointment information source of VPN can be ensured.
Particularly, when main multicast forward table and backup multicast forward table comprise the record list item for multiple CE, PE can according to the multicast mark of carrying in the report message of the report message of the IGMPv3 received or IGMPv2, and the address information of CE, the list item that matching inquiry identifies with this multicast and the address information of CE is consistent in described backup multicast table, finds the multicast source address information of CE from this list item.
Further, when the independent main multicast table set up for CE is deleted, or comprise in the main multicast table of multiple record list item to the record list item of CE deleted fall, illustrate that CE has exited the program request to flux of multicast, then, delete the backup multicast table corresponding with independent main multicast table, or delete the record list item for CE in the backup multicast table corresponding with the main multicast table comprising multiple record.
By above-mentioned processing procedure, PE sets up the backup multicast table of the main multicast table of CE, easily forwarding mechanism is shown according to selecting a good opportunity, carry out in the different phase of IGMPv3 and IGMPv2 switching at PE, PE can modify to the content in the multicast source address item in main multicast table, concrete amendment situation is: exclude(NULL) → EXCLUDE(A) → INCLUDE(A), but can not modify to the multicast table of backup, such PE is in the process of carrying out IGMPv3 and IGMPv2 switching, multicast source address information in main multicast table and backup multicast table is inconsistent, the multicast forwarding across VPN is carried out according to the multicast source address in backup multicast table, when main multicast table is consistent with the multicast source address information in backup multicast table, the multicast forwarding across VPN is carried out according to the multicast source address information in main multicast table, can to back up multicast table for reference frame, carry out in the process of IGMPv3 and IGMPv2 switching at PE, the reliable multicast forwarding effectively realizing carrying out across VPN to CE, can solve in prior art PE occur IGMP v2 and v3 version switch time, main multicast table according to constantly amendment forwards, cause the problem that the source-specific multicast across VPN of CE is stopped.
Based on identical inventive concept, the embodiment of the present invention additionally provides a kind of source-specific multicast device across VPN.
Fig. 3 shows the structured flowchart that the embodiment of the present invention provides the source-specific multicast device across VPN, and this device comprises:
Backup module 31, determine this PE runs IGMPv3 for detecting at the described source-specific multicast device place PE across VPN, and detect when the CE belonging in VPN that determines to be connected with this PE runs IGMPv3 and source-specific multicast pattern, the main multicast table that described PE sets up according to the report message of the IGMPv3 version from CE is backed up, in main multicast table and backup multicast table, includes the multicast source address information of the flux of multicast across VPN of CE program request; Also include in main multicast table and in backup multicast table: the multicast mark of the flux of multicast across VPN of CE program request;
Backup module 31, also for: in backup multicast table, record the address information of described CE; The address information of this CE comprises IP address and the MAC Address of CE;
Forwarding module 32, be connected to backup module 31, for carrying out in the process of IGMPv3 and IGMPv2 switching at described device place PE, multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
Particularly, forwarding module 32 is when described PE receives report message from the IGMPv2 of described CE and multicast source address information in described main multicast table and described backup multicast table is inconsistent, or when described PE receives report message from the IGMPv3 of described CE and multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE;
Forwarding module 32 also when described main multicast table is consistent with the multicast source address information in described backup multicast table, according to the multicast forwarding that the multicast source address in described main multicast list carries out across VPN to described CE.
Further, the multicast mark of forwarding module 32 also for carrying in the report message of IGMPv3 that receives according to described PE or the report message of IGMPv2, and the address information of CE, in backup multicast table, matching inquiry is to the multicast source address information of CE.
Preferably, as shown in Figure 4, on the basis of Fig. 3 shown device, the source-specific multicast device across VPN that the embodiment of the present invention provides can also comprise: removing module 33, is connected to backup module 31, for after main multicast table is deleted, deletes backup multicast table.
The operation principle of Fig. 3 or Fig. 4 shown device as shown in Figure 2, repeats no more here.
By device as shown in Figure 3 or Figure 4, also can carry out in the process of IGMPv3 and IGMPv2 switching at PE, the reliable multicast forwarding effectively realizing carrying out across VPN to CE, can solve in prior art PE occur IGMP v2 and v3 version switch time, main multicast table according to constantly amendment forwards, and causes the problem stopped to the source-specific multicast across VPN of CE.
Based on identical inventive concept, the embodiment of the present invention additionally provides a kind of network equipment, and this network equipment comprises the source-specific multicast device across VPN as shown in Figure 3 or Figure 4, and preferably, this network equipment can be PE.
One of ordinary skill in the art will appreciate that realizing all or part of step that above-described embodiment method carries is that the hardware that can carry out instruction relevant by program completes, described program can be stored in a kind of computer-readable recording medium, this program perform time, step comprising embodiment of the method one or a combination set of.
In addition, each functional unit in each embodiment of the present invention can be integrated in a processing module, also can be that the independent physics of unit exists, also can be integrated in a module by two or more unit.Above-mentioned integrated module both can adopt the form of hardware to realize, and the form of software function module also can be adopted to realize.If described integrated module using the form of software function module realize and as independently production marketing or use time, also can be stored in a computer read/write memory medium.
Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt the form of complete hardware embodiment, completely software implementation or the embodiment in conjunction with software and hardware aspect.And the present invention can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disc store and optical memory etc.) of computer usable program code.
The present invention describes with reference to according to the flow chart of the method for the embodiment of the present invention, equipment (system) and computer program and/or block diagram.Should understand can by the combination of the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or block diagram and/or square frame.These computer program instructions can being provided to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, making the instruction performed by the processor of computer or other programmable data processing device produce device for realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
These computer program instructions also can be stored in can in the computer-readable memory that works in a specific way of vectoring computer or other programmable data processing device, the instruction making to be stored in this computer-readable memory produces the manufacture comprising command device, and this command device realizes the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
These computer program instructions also can be loaded in computer or other programmable data processing device, make on computer or other programmable devices, to perform sequence of operations step to produce computer implemented process, thus the instruction performed on computer or other programmable devices is provided for the step realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
Obviously, those skilled in the art can carry out various change and modification to the present invention and not depart from the spirit and scope of the present invention.Like this, if these amendments of the present invention and modification belong within the scope of the claims in the present invention and equivalent technologies thereof, then the present invention is also intended to comprise these change and modification.
Claims (12)
1. a source-specific multicast SSM method of crossing virtual private networks network VPN, wherein, when the VPN access of application source-specific multicast SSM, multicast data flow carries out the multicast forwarding across VPN according to shortest path tree SPT, it is characterized in that, comprising:
Provider edge router PE determines described PE to run the Internet this IGMPv3 of the multicast member management protocol third edition in detection, and detect when the communication terminal CE belonging in VPN that determines to be connected with described PE runs IGMPv3 and source-specific multicast pattern, the main multicast table set up according to the report message from the IGMPv3 version of described CE is backed up, in described main multicast table and backup multicast table, includes the multicast source address information of the flux of multicast across VPN of described CE program request;
Described PE is in the process of carrying out IGMPv3 and IGMPv2 switching, multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
2. method according to claim 1, it is characterized in that, multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address in described backup multicast table carries out across VPN to described CE, specifically comprise:
When described PE receives from the report message of the IGMPv2 of described CE or the report message of IGMPv3 and multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
3. method according to claim 1, is characterized in that, described method also comprises:
When described main multicast table is consistent with the multicast source address information in described backup multicast table, according to the multicast forwarding that the multicast source address information in main multicast table is carried out across VPN to described CE.
4. method according to claim 1, is characterized in that, also includes in described main multicast table He in described backup multicast table: the multicast mark of the flux of multicast across VPN of described CE program request;
Described method also comprises:
The address information of described CE is recorded in described backup multicast table;
Described PE is according to the multicast mark of carrying in the report message of described IGMPv3 received or the report message of IGMPv2, and the address information of described CE, and in described backup multicast table, matching inquiry is to the multicast source address information of described CE.
5. method according to claim 1, is characterized in that, described method also comprises:
After described main multicast table is deleted, delete described backup multicast table.
6. the method according to any one of Claims 1 to 5, is characterized in that, the address information of described CE comprises:
The internet protocol address information of described CE and media interviews control information.
7. a source-specific multicast SSM device of crossing virtual private networks network VPN, wherein, when the VPN access of application source-specific multicast SSM, multicast data flow carries out the multicast forwarding across VPN according to shortest path tree SPT, it is characterized in that, comprising:
Backup module, determine described PE to run the Internet this IGMPv3 of the multicast member management protocol third edition for detecting at described device place PE, and detect when the communication terminal CE belonging in VPN that determines to be connected with described PE runs IGMPv3 and source-specific multicast pattern, the main multicast table that described PE sets up according to the report message of the IGMPv3 version from described CE is backed up, in described main multicast table and backup multicast table, includes the multicast source address information of the flux of multicast across VPN of described CE program request;
Forwarding module, for carrying out in the process of IGMPv3 and IGMPv2 switching at described device place PE, multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
8. device according to claim 7, is characterized in that, described forwarding module, specifically for:
When described PE receives from the report message of the IGMPv2 of described CE or the report message of IGMPv3 and multicast source address information in described main multicast table and described backup multicast table is inconsistent, according to the multicast forwarding that the multicast source address information in described backup multicast table is carried out across VPN to described CE.
9. device according to claim 7, is characterized in that, described forwarding module, also for:
When described main multicast table is consistent with the multicast source address information in described backup multicast table, according to the multicast forwarding that the multicast source address information in main multicast table is carried out across VPN to described CE.
10. device according to claim 7, is characterized in that, also includes in described main multicast table He in described backup multicast table: the multicast mark of the flux of multicast across VPN of described CE program request;
Described backup module, also for the address information that records described CE in described backup multicast table;
Described forwarding module, multicast mark also for carrying in: the report message of described IGMPv3 received according to described PE or the report message of described IGMPv2, and the address information of described CE, in described backup multicast table, matching inquiry is to the multicast source address information of described CE.
11. devices according to claim 7, is characterized in that, described device also comprises:
Removing module, for after described main multicast table is deleted, deletes described backup multicast table.
12. 1 kinds of network equipments, is characterized in that, comprise the source-specific multicast device of the crossing virtual private networks network according to any one of claim 7 ~ 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310029552.0A CN103095473B (en) | 2013-01-25 | 2013-01-25 | The source-specific multicast method of crossing virtual private networks network, device and the network equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310029552.0A CN103095473B (en) | 2013-01-25 | 2013-01-25 | The source-specific multicast method of crossing virtual private networks network, device and the network equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103095473A CN103095473A (en) | 2013-05-08 |
| CN103095473B true CN103095473B (en) | 2016-03-02 |
Family
ID=48207636
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310029552.0A Active CN103095473B (en) | 2013-01-25 | 2013-01-25 | The source-specific multicast method of crossing virtual private networks network, device and the network equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103095473B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105991248B (en) * | 2015-01-30 | 2020-02-28 | 中兴通讯股份有限公司 | Method for realizing hybrid automatic repeat request information transmission and data receiving end |
| CN110636033B (en) * | 2018-06-25 | 2021-11-26 | 中国电信股份有限公司 | Multicast data transmission method, system, multicast tunnel terminal and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101374069A (en) * | 2007-08-25 | 2009-02-25 | 华为技术有限公司 | Method, system and equipment for transforming multicast packet |
| CN101902403A (en) * | 2010-07-30 | 2010-12-01 | 中国联合网络通信集团有限公司 | Method and device for enhancing reliability of multicast source |
| CN102142970A (en) * | 2011-03-16 | 2011-08-03 | 华为技术有限公司 | Method for constructing multicast tree in two-layer Ethernet and network node equipment |
| CN102571375A (en) * | 2012-02-09 | 2012-07-11 | 北京星网锐捷网络技术有限公司 | Multicast forwarding method and device as well as network device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070097991A1 (en) * | 2005-10-31 | 2007-05-03 | Tatman Lance A | Method and system for discovering and providing near real-time updates of VPN topologies |
-
2013
- 2013-01-25 CN CN201310029552.0A patent/CN103095473B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101374069A (en) * | 2007-08-25 | 2009-02-25 | 华为技术有限公司 | Method, system and equipment for transforming multicast packet |
| CN101902403A (en) * | 2010-07-30 | 2010-12-01 | 中国联合网络通信集团有限公司 | Method and device for enhancing reliability of multicast source |
| CN102142970A (en) * | 2011-03-16 | 2011-08-03 | 华为技术有限公司 | Method for constructing multicast tree in two-layer Ethernet and network node equipment |
| CN102571375A (en) * | 2012-02-09 | 2012-07-11 | 北京星网锐捷网络技术有限公司 | Multicast forwarding method and device as well as network device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103095473A (en) | 2013-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105991432B (en) | Provider edge router and method | |
| CN102694718B (en) | A kind of VPLS fast rerouting method and equipment | |
| CN112636935B (en) | Virtual private network multicast method based on IPv6 network and electronic equipment | |
| CN102148745B (en) | Method and system for increasing forwarding efficiency of virtual private LAN service network | |
| CN101631069B (en) | Method, system and equipment for pseudo wire parameter negotiation | |
| CN107612809A (en) | A kind of multicast list synchronous method and equipment | |
| EP2457349B1 (en) | Method and device for a light host management protocol on multicast capable router | |
| CN104135420A (en) | A method, apparatus and system for forwarding message | |
| CN104253736A (en) | PE (provider edge) equipment and method for notifying same of information | |
| CN102316030A (en) | Method for realizing two-layer internetworking of data center and device | |
| CN105162704A (en) | Multicast replication method and device in Overlay network | |
| CN103124236B (en) | The management method of route and label and device | |
| CN103326940A (en) | Method for forwarding message in network and edge device of operator | |
| CN102137000A (en) | Method, device and system for establishing switching multicast distribution tree | |
| CN102571375B (en) | Multicast forwarding method and device as well as network device | |
| CN103716169B (en) | Point-to-multipoint method of realizing group broadcasting, network node and system | |
| US11323279B1 (en) | Internet group management protocol host mobility in ethernet virtual private network multicast networks | |
| CN102647328A (en) | Label distribution method, equipment and system | |
| CN103095473B (en) | The source-specific multicast method of crossing virtual private networks network, device and the network equipment | |
| JP2012533959A (en) | Effective host management protocol for multicast routers | |
| US9548887B2 (en) | Proactive creation of multicast state in an overlay transport network to achieve fast convergence on failover | |
| CN102724126A (en) | Method, device and equipment for forwarding Ethernet tree (E-tree) service message | |
| CN103634210B (en) | Find the method and apparatus of the opposite end PE equipment of VPLS example | |
| CN103780420A (en) | Automatic configuration method and system of Ethernet connectivity detection in VPLS environment | |
| CN105553857B (en) | A kind of IP Multicast Routings retransmission method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: Cangshan District of Fuzhou City, Fujian province 350002 Jinshan Road No. 618 Garden State Industrial Park 19 floor Patentee after: RUIJIE NETWORKS Co.,Ltd. Address before: Cangshan District of Fuzhou City, Fujian province 350002 Jinshan Road No. 618 Garden State Industrial Park 19 floor Patentee before: Beijing Star-Net Ruijie Networks Co.,Ltd. |