CN101075842B - Method for transmitting multi cast data in shared network - Google Patents

Method for transmitting multi cast data in shared network Download PDF

Info

Publication number
CN101075842B
CN101075842B CN2006100783670A CN200610078367A CN101075842B CN 101075842 B CN101075842 B CN 101075842B CN 2006100783670 A CN2006100783670 A CN 2006100783670A CN 200610078367 A CN200610078367 A CN 200610078367A CN 101075842 B CN101075842 B CN 101075842B
Authority
CN
China
Prior art keywords
lsr
upper reaches
downstream
candidate
label
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
Application number
CN2006100783670A
Other languages
Chinese (zh)
Other versions
CN101075842A (en
Inventor
刘淑英
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN2006100783670A priority Critical patent/CN101075842B/en
Priority to PCT/CN2007/000564 priority patent/WO2007131403A1/en
Publication of CN101075842A publication Critical patent/CN101075842A/en
Application granted granted Critical
Publication of CN101075842B publication Critical patent/CN101075842B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/16Multipoint routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/24Multipath
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/50Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

The method comprises: when at least one multicast path on the shared network segment has more than one candidate upstream router, said more than one candidate upstream router bears and relays the multicast data via said multicast path, and transmits the multicast data to the downstream router of said shared network segment corresponding to the multicast path. The invention is used for balancing the loads between upstream LSRs.

Description

Sharing the method for carrying out the multi-case data transmission on the network segment
Technical field
The present invention relates to the data transmission technology on the communication network, relate in particular to a kind of method of on the shared network segment of communication network, carrying out the multi-case data transmission.
Background technology
Multicasting technology (Multicast) is the multi-party communication technology of a kind of point to multiple spot; Compare with the unicast technique of generally using; Multicasting technology reduces identical data in the network to the taking of link bandwidth resource through setting up optimum multicast forwarding path, thereby reduces the consumption of multi-party communication to Internet resources significantly.
Along with the relevant criterion of multiprotocol label switching (mpls) technology is ripe gradually, the application of MPLS is in continuous expansion.The technology of multicast data forwarding constantly development and ripe on the MPLS network at present.It is a tag distribution protocol that is closely related with the MPLS technology that conventional tag is distributed (LDP) agreement, is mainly used in and under unicast case, sets up point-to-point (P2P), puts the label switched path (LSP) of multiple spot (P2MP).Along with the application of MPLS, be used on the MPLS network, setting up relevant criterion work engineering duty group (IETF) expansion of P2MP LSP in the Internet in the multicast field.
When above candidate's upper tag TSR (LSR) is owned in the multicast path on the shared network segment in the network together; That is to say for sharing in the network segment and own together under the situation of an above candidate upper reaches LSR to more than one P2MP LSP; How to transmit the problem of multi-case data; By having proposed the solution that a kind of upper tag distributes in the relevant draft of MPLS-UPSTREAM, that is: utilize one (by the Routing Protocol decision) among the above candidate upper reaches LSR to carry out the multi-case data distribution at present.
Fig. 1 is the sketch map of the said existing upper reaches routing tag allocative decision that is proposed by MPLS-UPSTREAM.Referring to Fig. 1, wherein comprise the multicast path of putting multiple spot more than, the multicast path of putting multiple spot has a source LSR and a plurality of reception LSRs (s wherein is expressed as more than).Corresponding point-to-multipoint label switch paths (being one or more P2MP LSP) all passes through the described topological structure of Fig. 1 between these sources LSRs and the reception LSRs; Said multicast path is the corresponding P2MP LSP of multicast forwarding equivalence class (FEC): wherein R2, R3 and R4 are directed against three candidate upper reaches LSRs that share network segment downstream LSRs (R5, R6, R7 and R8) among these P2MP LSPs, and promptly R2, R3 and R4 are next the jumping LSR of candidate that shares downstream LSRs (R5, R6, R7 and the R8) LSRs to the source in the network segment.
Correlation technique according to existing MPLS-UPSTREAM; In the process of setting up certain multicast FEC path; On shared network segment LAN1; When downstream LSRs (R5, R6, R7 and R8) when candidate upper reaches LSR sends the label request, downstream LSRs (R5, R6, R7 and R8) can select a LSR as upper reaches LSR in an above candidate upper reaches LSRs (R2, R3 and R4) according to unicast routing protocol.For example in Fig. 1, selected the upper reaches LSR of R2 as downstream LSRs; When R2 receive that R5, R6, R7 or R8 send to behind the label request message of certain multicast FEC; R2 distributes identical upper tag for R5, R6, R7 and R8, is so just sharing the part path of having set up the P2MP LSP of said FEC on the network segment LAN1.For the P2MP LSP of other multicast FEC, also be to distribute identical label for R5, R6, R7 and R8 through R2.The tree that the solid line of band arrow is formed among Fig. 1 is the part path through an above P2MP LSPs of above topology structure.
When R2 lost efficacy; Each downstream LSRs (R5, R6, R7 and R8) may send the label request message to above-mentioned FEC to another one candidate upper reaches LSR according to unicast routing protocol; For example in Fig. 1, R5, R6, R7 and R8 can send label request message to another candidate upper reaches R3 when R2 loses efficacy.Dotted portion among Fig. 1 representes that after R2 lost efficacy a said above P2MP LSPs switches to the path situation of new upper reaches R3.
The shortcoming of above-mentioned prior art is: when above candidate's upstream router is owned in the multicast path (an above P2MPLSPs) on sharing the network segment together; Because only selecting a candidate upper reaches LSR to make data, transmit all P2MP LSPs; The multi-case data flow that can cause certain candidate upper reaches LSR is very big and the multicast traffic at other several candidates upper reaches is very little; Cause an above candidate upper reaches LSR multicast load seriously unbalanced, the efficient of transfer of data is lower; When upper reaches LSR that unicast routing protocol is chosen lost efficacy, P2MP LSP need switch to other candidate upper reaches LSR and get on, so the time of data interruption is also long in addition.
Summary of the invention
In view of this; Main purpose of the present invention is to provide a kind of and is sharing the method for carrying out the multi-case data transmission on the network segment; When owning an above candidate upper reaches LSR together in the multicast path on sharing the network segment; Solve the serious unbalanced problem of multicast load of candidate upper reaches LSR, improve data transmission efficiency.
In order to realize the foregoing invention purpose, main technical schemes of the present invention is:
A kind of method of on the shared network segment, carrying out the multi-case data transmission, said method specifically comprises:
To all candidate upper reaches LSR request multicast labels of sharing this multicast path on the network segment, wherein, said multicast path has an above candidate upper reaches LSR to the downstream LSR of A, the shared network segment when setting up certain multicast path;
B, said each candidate upper reaches LSR that receives request ask the downstream LSR of said multicast label for all and distribute upper tag, and issue upper tag and give said downstream LSR;
C, said each upper reaches LSR that receives the candidate upper reaches LSR distribution downstream label of request and send to self; If the convergent point LSR that said upper reaches LSR is not a path candidate; Then these upper reaches LSR distributes the downstream label and sends to self upper reaches LSR, and this process of distributing the downstream label finishes when convergent point LSR that said upper reaches LSR is a path candidate;
D, this convergent point of said convergent point LSR record LSR are to outgoing interface and corresponding downstream label between next the jumping LSR that reports the downstream label;
E, when the retransmitting multi-casting data; Through the load balancing algorithm multi-case data of being transmitted is shared to the more than one outgoing interface that is write down, an above candidate upper reaches LSR who said multi-case data is shared to correspondence through outgoing interface and corresponding downstream label transmits.
Preferably, said multi-case data transmits based on multiprotocol label switching MPLS network, and said multicast path is the corresponding label switched path of multicast forwarding equivalence class FEC, and said router is LSR LSR.
Preferably, among the said step D, said convergent point LSR sets up the forwarding state of said multicast FEC, and this convergent point LSR is recorded in the forwarding state of this multicast FEC with corresponding downstream label to next outgoing interface of jumping between LSR that reports the downstream label;
Set up at least one multicast FEC corresponding forwarding state to step D at convergent point LSR through said steps A.
Preferably, said step e specifically comprises:
E1, said convergent point LSR are when the retransmitting multi-casting data; Through the load balancing algorithm multi-case data of being transmitted is shared the more than one outgoing interface that is write down in the said forwarding state, and utilize the downstream label of outgoing interface and correspondence each candidate upper reaches LSR retransmitting multi-casting data to correspondence;
E2, a corresponding above candidate upper reaches LSR are transmitted to the downstream LSR of the said shared network segment with said multi-case data, and downstream LSR transmits said multi-case data again.
Preferably, when on sharing the network segment, adding the new candidate upper reaches LSR that is on the said multicast path, then further comprise:
Each downstream LSR on the said shared network segment of A6, said multicast path correspondence is to this newly-increased candidate upper reaches LSR request upper tag;
B6, said newly-increased candidate upper reaches LSR ask the downstream LSR of said upper tag for all and distribute upper tag, and the concurrent vernier of serving is signed each the downstream LSR to the request of said initiation label;
C6, said newly-increased candidate upper reaches LSR distribute the downstream label; And send the downstream label to self upper reaches LSR; If the convergent point LSR that said upper reaches LSR is not a path candidate; Then said these upper reaches LSR distributes the downstream label equally and sends the downstream label and give the upper reaches LSR of himself, and this said process that distributes the downstream label finishes when convergent point LSR that said upper reaches LSR is a path candidate.
Preferably, when said newly-increased candidate upper reaches LSR is on the above multicast path, carry out said steps A 6 to step C6 respectively to each multicast path;
Perhaps, each the downstream LSR on the shared network segment in said multicast path adopts in batches label request mode to newly-increased candidate upper reaches LSR initiation one-time request; Newly-increased candidate upper reaches LSR is each multicast path allocation upper tag, and adopts the batch send mode to send upper tag to said each downstream LSR; Newly-increased candidate upper reaches LSR adopts in batches, and the mode of downstream label distribution is each multicast path allocation downstream label; And send the downstream label to the upper reaches LSR of the direction of said path candidate convergent point LSR in bulk; If receive the upper reaches LSR of downstream label is not said convergent point LSR; The upper reaches LSR that then receives the downstream label utilizes batch downstream label distribution method to distribute the downstream label and send the upper reaches LSR of downstream label to himself equally, and the process of this mass distributed downstream label finishes when the upper reaches LSR that receives the downstream label is the convergent point LSR of path candidate.
Preferably; When one or more inefficacies among the candidate upper reaches LSR described in the said shared network segment; Then in the step e; Said convergent point LSR shares the outgoing interface of the candidate upper reaches LSR that remains valid to the sensing of being write down through the load balancing algorithm with the multi-case data of being transmitted, and the candidate upper reaches LSR that outgoing interface through pointing to corresponding candidate upper reaches LSR and downstream label share said multi-case data to correspondence transmits.
Preferably, said load balancing is that every current load is shared or every bag load balancing.
Preferably, said candidate upper reaches LSR is identical for all upper tags of asking the downstream LSR of same multicast label to distribute.
Said candidate upper reaches LSR is on the equative route or on the non-equivalence path; If on equative route, then corresponding said load balancing algorithm is the equal cost multipath algorithm, if on the non-equivalence path, then corresponding said load balancing algorithm is a weight multipath algorithm.
The embodiment of the invention has also proposed another kind of method of on the shared network segment, carrying out the multi-case data transmission, and said method specifically comprises:
The downstream LSR of a, the shared network segment confirms to share a candidate upper reaches LSR on the network segment according to the load balancing algorithm when setting up certain multicast path, and to these candidate upper reaches LSR request label, wherein, said multicast path has above candidate's upstream router;
B, said candidate upper reaches LSR are that the multicast of being asked distributes upper tag, and this upper tag is handed down to the downstream LSR that this multicast path is set up in all requests;
C, said candidate upper reaches LSR are that the multicast of being asked distributes the downstream label; And send the downstream label and give the upper reaches LSR of self; If the upper reaches LSR that receives the downstream label is not the convergent point LSR of path candidate; The upper reaches LSR that then receives the downstream label distributes the downstream label and sends to the upper reaches LSR of self, and this distributes the process of downstream label when the upper reaches LSR that receives the downstream label is the convergent point LSR of path candidate, to finish;
Outgoing interface between d, the said convergent point LSR record convergent point LSR corresponding and next the jumping LSR that reports the downstream label and corresponding downstream label with said multicast;
E, when the retransmitting multi-casting data, outgoing interface through this multicast corresponding record and downstream label are transferred to corresponding candidate upper reaches LSR with multi-case data and transmit.
Preferably, in the said steps d, said convergent point LSR sets up forwarding state to multicast FEC, said convergent point LSR is recorded in the forwarding state of this multicast FEC with outgoing interface and corresponding downstream label between next the jumping LSR that reports the downstream label; Set up the forwarding state of at least one multicast FEC at convergent point LSR to steps d through said step a.
Preferably, said step e specifically comprises:
E1, said convergent point LSR give corresponding candidate upper reaches LSR according to outgoing interface that is write down in the corresponding forwarding status information of this multicast and downstream label forwarding data when the retransmitting multi-casting data;
E2, corresponding candidate upper reaches LSR are transmitted to the downstream LSR of the said shared network segment with said multi-case data, and downstream LSR transmits again.
Preferably; When one or more inefficacies among the said candidate upper reaches LSR that chooses; Then sharing among the candidate upper reaches LSR that remains valid on the network segment according to the load balancing algorithm again and confirming a candidate upper reaches LSR at the shared network segment downstream LSR on the multicast path that these candidate upper reaches LSR shares; And to these candidate upper reaches LSR request label, and carry out said step b and subsequent step.
Preferably, said load balancing is that every current load is shared.
Preferably, said candidate upper reaches LSR is on the equative route or on the non-equivalence path; If on equative route, then corresponding said load balancing algorithm is the equal cost multipath algorithm, if on the non-equivalence path, then corresponding said load balancing algorithm is a weight multipath algorithm.
Because the present invention is when owning above candidate's upstream router together when the multicast path on the shared network segment; Mode through load balancing; The forwarding load of multicast data stream reasonably is assigned on each candidate upper reaches LSR that shares the network segment; Expand the forwarding approach of multicast data stream, solved the serious unbalanced problem of multicast load of existing candidate upper reaches LSR, improved data transmission efficiency.
In addition; The method of the said load balancing of the application of the invention; When some or certain the several LSRs in sharing the network segment among above candidate upper reaches LSRs take place to lose efficacy; Multicast data stream can instantaneously switch to other candidate upper reaches LSRs and get on, and has shortened the time that multicast data stream interrupted when certain candidate upper reaches LSR lost efficacy greatly.
Description of drawings
Fig. 1 is the sketch map of the said existing upper reaches routing tag allocative decision that is proposed by MPLS-UPSTREAM;
The network topology structure sketch map of Fig. 2 when owning above candidate's upstream router together when the multicast path on the shared network segment;
Fig. 3 is for carrying out the method flow diagram of transfer of data under the situation of first embodiment of the invention when owning above candidate's upstream router together when the multicast path on the shared network segment;
Fig. 4 is for setting up the instance graph of the P2MPLSP of certain multicast FEC on based on shared network segment LAN1 shown in Figure 2;
Fig. 5 is for having added the topology diagram of new candidate upper reaches LSR on the shared network segment shown in Figure 1;
Fig. 6 is the flow chart of second embodiment of the method for the invention.
Embodiment
Through specific embodiment and accompanying drawing the present invention is explained further details below.
Core technology scheme of the present invention is: in the data transmission procedure of network; When above candidate's upstream router is owned at least one the multicast path on sharing the network segment together; By said more than one candidate's upstream router the multi-case data by way of said multicast path is carried out load balancing and transmit, be transferred to the downstream router of the corresponding said shared network segment in said multicast path.
Embodiment according to the invention mainly is transmitted as example and describes in the multiprotocol label switching (mpls) network, to carry out multi-case data.The present invention can also be applied in the multi-case data transmission of all similar network.
Among the embodiment of the present invention, said multi-case data transmits based on multiprotocol label switching MPLS network, and said multicast path is the corresponding label switched path of multicast forwarding equivalence class FEC, and said router is LSR LSR.
The network topology structure sketch map of Fig. 2 when owning above candidate's upstream router together when the multicast path on the shared network segment.Referring to Fig. 2, wherein comprise the multicast path of putting multiple spot more than, the multicast path of putting multiple spot has a source LSR and a plurality of reception LSR.Corresponding point-to-multipoint label switch paths (P2MP LSP) all passes through the described topological structure of Fig. 2 between these sources LSR and the reception LSR: wherein R2 is an above candidate upper reaches LSR who is directed against downstream LSRs (Rn is to Ru) among the said P2MP LSPs to Rm; Be that R2 is next jumping LSRs of more than one candidate of downstream LSRs (Rn is to Ru) LSRs to the source to Rm; Said candidate upper reaches LSR can be on equative route (being that transmission performance is identical), also can be in the non-equivalence path (being that transmission performance is incomplete same).R1 is the convergent point in candidate's (equivalence/non-equivalence) path, said candidate upper reaches LSR (R2 is to Rm) place, can direct connection between R1 and the said candidate upper reaches LSR, also can have the middle LSR of at least one jumping.
Method of the present invention relates to the technical scheme of setting up P2MP LSP on the network segment LAN1 and between an above candidate upper reaches LSRs, carrying out transfer of data sharing, for set up at other network segments of network P2MP LSP go forward side by side the method for data transfer can be with reference to existing technology.
Fig. 3 is for carrying out the method flow diagram of transfer of data under the situation of first embodiment of the invention when owning above candidate's upstream router together when the multicast path on the shared network segment.Referring to Fig. 3, this flow process comprises:
At first sharing the P2MP LSP that sets up multicast forwarding equivalence class (FEC) correspondence on the network segment.Specifically comprise step 301 to step 306:
When step 301, one or more LSRs in the downstream LSRs (Rn is to Ru) that shares the network segment set up the P2MP LSP of certain multicast FEC correspondence to source LSR direction, said downstream LSRs sent the label request to the candidate upper reaches LSRs of all LSR to the source (being that R2 is to Rm) and asks upper reaches LSR distributing labels.
Step 302, when R2 receives the label request message that downstream LSR sends to each the candidate upper reaches LSR among the Rm after; The downstream LSR that each candidate upper reaches LSR utilizes the upper tag apportion design to set up same multicast FEC to all requirements distributes an identical upper tag (here identical is meant that the upper tag that same candidate upper reaches LSR distributes is identical, and the upper tag that different candidates upper reaches LSR is distributed can be the same or different); Each candidate upper reaches LSR sets up the forwarding state of said multicast FEC.
The downstream LSR that step 303, each candidate upper reaches LSR set up same multicast FEC to all requirements issues the identical upper tag that is distributed.All requirements set up among the downstream LSRs of the corresponding P2MP LSP of said multicast FEC each all can obtain a upper reaches distributing labels from each candidate upper reaches LSR; And set up forwarding state in view of the above; Each LSR among the said like this downstream LSRs can safeguard that simultaneously m-1 is gone into label for this multicast FEC; Be that forwarding plane will safeguard that simultaneously m-1 is gone into tag match (ILM) list item for this multicast FEC, but only be that this multicast FEC safeguards an outgoing interface tabulation.
Step 304, when each candidate upper reaches LSR (R2 is to Rm) after the downstream LSR that the corresponding P2MP LSP of said multicast FEC is set up in all requirements distributes same label and sends; It is that the multicast FEC that is asked distributes the downstream label that each candidate upper reaches LSR (R2 is to Rm) need to use downstream label distribution methods (concrete distribution method can adopt prior art), and sends the downstream label that is distributed to its upper reaches LSR (R1).
If LSR in the middle of existing between said candidate upper reaches LSR and the R1; Be the convergent point LSR (R1) that said upper reaches LSR is not a path candidate; Then these upper reaches LSR distributes the downstream label and sends to self upper reaches LSR, and this process of distributing the downstream label finishes when convergent point LSR (R1) that said upper reaches LSR is a path candidate.
Step 305, after R1 receives the downstream label that downstream LSR sends; R1 sets up the forwarding status information of said multicast FEC, continuous interface in adding and each candidate upper reaches LSR (R2 is to Rm) and corresponding outgoing label (being the downstream label that corresponding candidate upper reaches LSR is distributed) in the corresponding forwarding status information (in follow-up transfer of data, carrying out data forwarding according to this forwarding status information) of this FEC.If the LSR in the middle of having between R1 and the said candidate upper reaches LSR, then R1 add in the corresponding forwarding status information of said multicast FEC that R1 reports the downstream label to each next jump outgoing interface (promptly pointing to the outgoing interface of each candidate upper reaches LSR (R2 is to Rm)) and the outgoing label (being the downstream label that said next jumping LSR reports) of correspondence between LSR.
The P2MPLSP that sets up other multicasts FEC correspondence on the network segment LAN1 can shared through said process.
Step 306, the transmission said multicast FEC data the time; R1 (recommends use source IP according to the load balancing algorithm to the relevant information in the multicast data stream packet header; Group address to) calculate after; Adopt the outgoing interface that every current load is shared or the mode of every bag load balancing shares the multi-case data of being transmitted to each candidate upper reaches of the sensing of writing down in multicast forwarding status information LSR to transmit; Promptly, be transferred to corresponding candidate upper reaches LSR through R1 and the outgoing interface of said each candidate upper reaches LSR (R2 is to Rm) and corresponding binding tab.If the LSR in the middle of having between R1 and the said candidate upper reaches LSR; Then adopt every current load to share or the mode of every bag load balancing shares the multi-case data of being transmitted to the more than one outgoing interface that writes down in the multicast forwarding state (each outgoing interface points to corresponding candidate upper reaches LSR respectively); Promptly jump LSR to next, and finally be transmitted to corresponding candidate upper reaches LSR through said outgoing interface and corresponding downstream label forwarding data.Be transmitted to downstream LSR (Rn is to Ru) by the candidate upper reaches LSR that receives data then.Can overcome the serious unbalanced shortcoming of load in the prior art sharing on the network segment load multicast data stream reasonably like this by candidate upper reaches LSR.
If said candidate upper reaches LSR is on equative route; Then corresponding said load balancing algorithm is equal cost multipath algorithm (ECMP; Equal Cost Multipath); If on the non-equivalence path, then corresponding said load balancing algorithm is weight multipath algorithm (WCMP, Weight Cost Multipath).In addition, R1 can represent to adopt every current load to share the perhaps mode of every bag load balancing through the sign that appointment is set in forwarding state.The mode that said every current load is shared is for to share each multicast FEC current load of being transmitted to different candidate upper reaches LSR; The mode of every bag load balancing is for giving different candidate upper reaches LSR with each packet load balancing of being transmitted.Concrete every current load is shared with every bag load sharing method and can be utilized existing mode to carry out.It should be noted that: R1 can not adopt the mode of duplicating distribution simultaneously to transmit data when each candidate upper reaches LSR (R2 is to Rm) transmit data, otherwise can cause downstream can repeat to receive same packet.
Fig. 4 is for setting up the instance graph of the P2MPLSP of certain multicast FEC on based on shared network segment LAN1 shown in Figure 2.Referring to Fig. 4, the downstream LSR (for example Rn and Ru) of the shared network segment that at first hopes to set up certain multicast path is to all upper reaches LSR (R2 is to Rm) transmission label request messages of sharing the network segment; Each upper reaches LSR is that the multicast FEC that is asked distributes upper tag, and is handed down to the downstream LSR of initiation request, and the upper tag that for example R2 distributes among the figure is L2, sets up the forwarding state of said multicast FEC, and this L2 is handed down to Rn and Ru; The upper tag that Rm distributes is Lm, sets up the forwarding status information of said multicast FEC, and Lm is handed down to Rn and Ru; Said each upper reaches LSR reallocation downstream label, and send to R1, for example the downstream label of R2 distribution is L12, the downstream label that Rm distributes is L1m; R1 sets up the forwarding state of said multicast FEC, record links to each other with each candidate upper reaches LSR (R2 is to Rm) in this forwarding state interface and outgoing label.Through above-mentioned processing; R1 is last to have m-1 outgoing interface in the multicast forwarding state of said FEC; When the retransmitting multi-casting data; After according to the ECMP/WCMP algorithm relevant information in the multicast data stream packet header being calculated, adopt every current load to share or the mode of every bag load balancing is transmitted to different candidate upper reaches LSR.
In addition; When one or more inefficacies among the candidate upper reaches LSR described in the said shared network segment; Then in the step e; Said convergent point LSR (R1) shares the outgoing interface of the candidate upper reaches LSR that remains valid to the sensing of being write down in the said forwarding status information through the load balancing algorithm with the multi-case data of being transmitted, and utilizes the outgoing interface that points to corresponding candidate upper reaches LSR and downstream label to the candidate upper reaches of correspondence LSR retransmitting multi-casting data.
In the method for the present invention:
To a concrete multicast FEC, each candidate upper reaches LSR (R2 each LSR in the Rm) can use the method for downstream label distribution to distribute an outgoing label to its upper reaches equivalence/non-equivalence path convergent point LSR (R1); If candidate upper reaches LSR (R2 is to Rm) are not one to jump but multi-hop to the jumping figure of R1, each in the middle of so jump all use the downstream label distribution method to its upper reaches LSR distributing labels, up to R1; R1 is that an outgoing interface and outgoing label are safeguarded in the downstream in each equivalence/non-equivalence path; Outgoing interface for equivalence more than/non-equivalence path is corresponding is tabulated with outgoing label, adopts every current load to share or the mode of every bag load balancing and do not use the mode of duplicating distribution simultaneously;
To a concrete multicast FEC; Each candidate upper reaches LSR (R2 each LSR in the Rm) can be request all downstream of setting up the corresponding P2MP LSP of this multicast FEC (Rn some in the Ru or certain is several) identical labels of distribution with the mode that upper tag distributes, and the upper reaches LSR (R1) that the mode of also using the downstream label distribution is simultaneously distributed downstream label for this FEC and is distributed to oneself is that all to go into label and outgoing interface and outgoing label right for this of FEC maintenance in the forwarding state of each candidate upper reaches LSR;
To a concrete multicast FEC; Rn all requirements in the Ru set up among the LSRs of the corresponding P2MPLSP of this FEC each all can obtain a upper reaches distributing labels from each candidate upper reaches LSR (R2 each LSR to the Rm); Each LSR among the said like this downstream LSRs can safeguard that simultaneously m-1 is gone into label for this multicast FEC; Be that forwarding plane will be safeguarded m-1 ILM list item simultaneously for this multicast FEC, but only be that this multicast FEC safeguards an outgoing interface tabulation.
Fig. 5 is for having added the topology diagram of new candidate upper reaches LSR on the shared network segment shown in Figure 1.In Fig. 5, on the shared network segment, set up the P2MP LSP that between each candidate upper reaches LSR (R2 is to R4), carries out load balancing according to the method described above, if add a new candidate upper reaches LSR (R0) this moment again, need do some special processings.Concrete steps are following:
Step 501, on shared network LAN1; When the downstream LSR (R5 is to R8) among the above-mentioned P2MP LSP found a new candidate upper reaches LSR (R0) that arrive the corresponding source LSR of this P2MP LSP according to existing routing protocol after, R5 can send label request message to R0 to the corresponding multicast FEC of said P2MP LSP to each LSR among the R8.
Step 502, R0 can utilize allocating method for upper tag to distribute identical upper tag to each downstream LSR of the said multicast FEC label of request after receiving the label request message of the said multicast FEC that each downstream LSR sends; Set up forwarding state; And sending said upper tag to each downstream LSR, downstream LSR sets up forwarding state in view of the above; While R0 can use the downstream label distribution method to distribute downstream performance and LSR (R1) transmission upstream to this multicast FEC.If LSR in the middle of existing between said candidate upper reaches LSR and the R1; Be the convergent point LSR (R1) that said upper reaches LSR is not a path candidate; Then these upper reaches LSR distributes the downstream label and sends to self upper reaches LSR, and this process of distributing the downstream label finishes when convergent point LSR (R1) that said upper reaches LSR is a path candidate.
Step 503,, R1 records in the forwarding state of said multicast FEC when receiving after next jumps the downstream label that LSR sends the outgoing interface of correspondence and downstream label added.
Step 504, when the data of R1 at the said multicast FEC of transmission, adopt every current load to share or the mode of every bag load balancing is shared the multi-case data of being transmitted the outgoing interface that is transferred to the corresponding candidate upper reaches LSR of sensing (R0, R2, R3 and R4) that writes down in the forwarding state.
As R0 when being R5 to the candidate upper reaches of the last above P2MP LSPs of R8, R5 can adopt respectively to each LSR among the R8 each P2MP LSP is carried out the label request, and R0 also carries out the downstream label distribution to each P2MP LSP respectively to be handled; R5 also can adopt batch label request mode and needn't carry out the label request to each P2MP LSP respectively to each LSR among the R8, that is: adopt batch label request mode to initiate one-time request to R0; R0 is that each P2MP LSP distributes upper tag, and sets up the forwarding state of each multicast FEC respectively, and adopts the batch send mode to send the upper tag that is distributed to the shared network segment downstream LSR of all these P2MP LSP labels of request; R0 adopts the mode of batch downstream label distribution to distribute downstream label for each P2MP LSP equally, and sends the label mapping to distribute label to said convergent point LSR in bulk.
Fig. 6 is the flow chart of second embodiment of the method for the invention.This flow process mainly is the reduction procedure to first embodiment, and this sentences based on topological structure shown in Figure 2 and describes.This flow process comprises:
Step 601, when Rn some in Ru or certain several LSR require to set up P2MP LSP to certain multicast FEC; They are not to send the label request to each candidate upper reaches LSR; But according to the load balancing algorithm information among this multicast FEC is calculated, finally confirm a candidate upper reaches LSR and send label request (that for example choose to this multicast FEC is R2) to it.Here, if said candidate upper reaches LSR on equative route, then corresponding said load balancing algorithm is the equal cost multipath algorithm, if on the non-equivalence path, then corresponding said load balancing algorithm is a weight multipath algorithm.
Step 602, after R2 receives the label request to the selected candidate upper reaches LSR among the Rm; Utilize the upper tag apportion design to distribute identical upper tag to the shared network segment downstream LSR that this multicast FEC sends the label request to all; Set up corresponding forwarding state, and upper tag is sent to the downstream LSR that this multicast FEC path is set up in said all requests.
Step 603, R2 distribute the downstream label and this downstream label are sent to its upper reaches LSR to this multicast FEC with the method for downstream label distribution.If LSR in the middle of also having between said R2 and the R1; Be the convergent point LSR that said upper reaches LSR is not a path candidate; Then these upper reaches LSR distributes the downstream label and sends to self upper reaches LSR, and this process of distributing the downstream label finishes when convergent point LSR that said upper reaches LSR is a path candidate.
Step 604, after R1 receives the label mapping message that sends in downstream; To this multicast FEC; Set up forwarding state, write down interface and corresponding downstream label between R1 and the shared network segment candidate upper reaches LSR (R2) that reports this multicast FEC label (promptly safeguard an outgoing interface and outgoing label to) therein.If the LSR in the middle of having between R1 and the R2, then in forwarding state record R1 with report the downstream label next jump outgoing interface (this outgoing interface sensing R2) and corresponding downstream label between LSR.
Step 605, R1 are transmitted to corresponding candidate upper reaches LSR (R2) according to outgoing interface that is write down in this multicast FEC forwarding status information and outgoing label when the retransmitting multi-casting data.It should be noted that this second embodiment can only carry out every current load and share.
Step 606, corresponding candidate upper reaches LSR (R2) are transmitted to the downstream LSR of the said shared network segment according to self forwarding state with said multi-case data, and downstream LSR transmits according to self forwarding state again.
In the process of setting up other multicast FEC path, also utilize the method for above-mentioned flow process, an above multicast FEC path is based upon respectively on the different candidate upper reaches LSR, when the retransmitting multi-casting data, can realize the load balancing transmission.But this scheme can only be used for every current load and share and can not be used for every bag load balancing.In addition; When one or more inefficacies among the candidate upper reaches LSR that chooses described in the said shared network segment; Then these candidate upper reaches LSR shares among the candidate upper reaches LSR that the shared network segment downstream LSR of the multicast FEC of forwarding remains valid on sharing the network segment according to the load balancing algorithm again and confirms a candidate upper reaches LSR; And to these candidate upper reaches LSR request label, and carry out said step 602 and subsequent step.Compare first embodiment, when second embodiment lost efficacy at the candidate upper reaches LSR that chooses, the flow interruption time was long, but has then still shortened greatly break period with respect to prior art.
The above; Be merely the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, anyly is familiar with this technological people in the technical scope that the present invention disclosed; The variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.

Claims (16)

1. sharing the method for carrying out the multi-case data transmission on the network segment for one kind, it is characterized in that said method specifically comprises:
To all candidate upper reaches LSR request multicast labels of sharing this multicast path on the network segment, wherein, said multicast path has an above candidate upper reaches LSR to the downstream LSR (LSR) of A, the shared network segment when setting up certain multicast path;
B, said each candidate upper reaches LSR that receives request ask the downstream LSR of said multicast label for all and distribute upper tag, and issue upper tag and give said downstream LSR;
C, said each upper reaches LSR that receives the candidate upper reaches LSR distribution downstream label of request and send to self; If the upper reaches LSR that receives the downstream label is not the convergent point LSR of path candidate; The upper reaches LSR that then receives the downstream label distributes the downstream label and sends to the upper reaches LSR of self, and this distributes the process of downstream label when the upper reaches LSR that receives the downstream label is the convergent point LSR of path candidate, to finish;
D, this convergent point of said convergent point LSR record LSR are to outgoing interface and corresponding downstream label between next the jumping LSR that reports the downstream label;
E, when the retransmitting multi-casting data; Through the load balancing algorithm multi-case data of being transmitted is shared to the more than one outgoing interface that is write down, an above candidate upper reaches LSR who said multi-case data is shared to correspondence through outgoing interface and corresponding downstream label transmits.
2. method according to claim 1 is characterized in that said multi-case data transmits based on the multiprotocol label switching (mpls) network, and said multicast path is the corresponding label switched path of multicast forwarding equivalence class (FEC).
3. method according to claim 2; It is characterized in that; Among the said step D; Said convergent point LSR sets up the forwarding state of said multicast FEC, and this convergent point LSR is recorded in the forwarding state of this multicast FEC with corresponding downstream label to next outgoing interface of jumping between LSR that reports the downstream label;
Set up at least one multicast FEC corresponding forwarding state to step D at convergent point LSR through said steps A.
4. method according to claim 3 is characterized in that, said step e specifically comprises:
E1, said convergent point LSR are when the retransmitting multi-casting data; Through the load balancing algorithm multi-case data of being transmitted is shared the more than one outgoing interface that is write down in the said forwarding state, and utilize the downstream label of outgoing interface and correspondence each candidate upper reaches LSR retransmitting multi-casting data to correspondence;
E2, a corresponding above candidate upper reaches LSR are transmitted to the downstream LSR of the said shared network segment with said multi-case data, and downstream LSR transmits said multi-case data again.
5. method according to claim 2 is characterized in that, when on sharing the network segment, adding the new candidate upper reaches LSR that is on the said multicast path, then further comprises:
Each downstream LSR on the said shared network segment of A6, said multicast path correspondence is to this newly-increased candidate upper reaches LSR request upper tag;
B6, said newly-increased candidate upper reaches LSR ask the downstream LSR of said upper tag for all and distribute upper tag, and the concurrent vernier of serving is signed each the downstream LSR to the request of said initiation label;
C6, said newly-increased candidate upper reaches LSR distribute the downstream label; And send the downstream label to self upper reaches LSR; If the convergent point LSR that said upper reaches LSR is not a path candidate; Then said these upper reaches LSR distributes the downstream label equally and sends the downstream label and give the upper reaches LSR of himself, and this said process that distributes the downstream label finishes when convergent point LSR that said upper reaches LSR is a path candidate.
6. method according to claim 5 is characterized in that, when said newly-increased candidate upper reaches LSR is on the above multicast path,
Carry out said steps A 6 to step C6 respectively to each multicast path;
Perhaps, each the downstream LSR on the shared network segment in said multicast path adopts in batches label request mode to newly-increased candidate upper reaches LSR initiation one-time request; Newly-increased candidate upper reaches LSR is each multicast path allocation upper tag, and adopts the batch send mode to send upper tag to said each downstream LSR; Newly-increased candidate upper reaches LSR adopts in batches, and the mode of downstream label distribution is each multicast path allocation downstream label; And send the downstream label to the upper reaches LSR of the direction of said path candidate convergent point LSR in bulk; If receive the upper reaches LSR of downstream label is not said convergent point LSR; The upper reaches LSR that receives the downstream label utilizes batch downstream label distribution method to distribute the downstream label and send the upper reaches LSR of downstream label to himself equally, and the process of this mass distributed downstream label finishes when the upper reaches LSR that receives the downstream label is the convergent point LSR of path candidate.
7. method according to claim 2; It is characterized in that; When one or more inefficacies among the candidate upper reaches LSR described in the said shared network segment; Then in the step e, said convergent point LSR shares the outgoing interface of the candidate upper reaches LSR that remains valid to the sensing of being write down through the load balancing algorithm with the multi-case data of being transmitted, and the candidate upper reaches LSR that outgoing interface through pointing to corresponding candidate upper reaches LSR and downstream label share said multi-case data to correspondence transmits.
8. according to each described method of claim 2 to 7, it is characterized in that said load balancing is that every current load is shared or every bag load balancing.
9. according to each described method of claim 2 to 7, it is characterized in that said candidate upper reaches LSR is identical for all upper tags of asking the downstream LSR of same multicast label to distribute.
10. according to each described method of claim 1 to 7, it is characterized in that said candidate upper reaches LSR is on the equative route or on the non-equivalence path; If on equative route, then corresponding said load balancing algorithm is the equal cost multipath algorithm, if on the non-equivalence path, then corresponding said load balancing algorithm is a weight multipath algorithm.
11. sharing the method for carrying out the multi-case data transmission on the network segment, it is characterized in that said method specifically comprises for one kind:
The downstream LSR (LSR) of a, the shared network segment confirms to share a candidate upper reaches LSR on the network segment according to the load balancing algorithm when setting up certain multicast path; And to these candidate upper reaches LSR request label; Wherein, said multicast path has above candidate's upstream router;
B, said candidate upper reaches LSR are that the multicast of being asked distributes upper tag, and this upper tag is handed down to the downstream LSR that this multicast path is set up in all requests;
C, said candidate upper reaches LSR are that the multicast of being asked distributes the downstream label; And send the downstream label and give the upper reaches LSR of self; If the upper reaches LSR that receives the downstream label is not the convergent point LSR of path candidate; The upper reaches LSR that then receives the downstream label distributes the downstream label and sends to the upper reaches LSR of self, and this distributes the process of downstream label when the upper reaches LSR that receives the downstream label is the convergent point LSR of path candidate, to finish;
Outgoing interface between d, the said convergent point LSR record convergent point LSR corresponding and next the jumping LSR that reports the downstream label and corresponding downstream label with said multicast;
E, when the retransmitting multi-casting data, outgoing interface through this multicast corresponding record and downstream label are transferred to corresponding candidate upper reaches LSR with multi-case data and transmit.
12. method according to claim 11; It is characterized in that; In the said steps d, said convergent point LSR sets up forwarding state to multicast forwarding equivalence class (FEC), said convergent point LSR is recorded in the forwarding state of this multicast FEC with outgoing interface and corresponding downstream label between next the jumping LSR that reports the downstream label; Set up the forwarding state of at least one multicast FEC at convergent point LSR to steps d through said step a.
13. method according to claim 12 is characterized in that, said step e specifically comprises:
E1, said convergent point LSR give corresponding candidate upper reaches LSR according to outgoing interface that is write down in the corresponding forwarding status information of this multicast and downstream label forwarding data when the retransmitting multi-casting data;
E2, corresponding candidate upper reaches LSR are transmitted to the downstream LSR of the said shared network segment with said multi-case data, and downstream LSR transmits again.
14. method according to claim 11; It is characterized in that; When one or more inefficacies among the said candidate upper reaches LSR that chooses; Then sharing among the candidate upper reaches LSR that remains valid on the network segment according to the load balancing algorithm again and confirming a candidate upper reaches LSR at the shared network segment downstream LSR on the multicast path that these candidate upper reaches LSR shares, and to these candidate upper reaches LSR request label, and carry out said step b and subsequent step.
15., it is characterized in that said load balancing is that every current load is shared according to each described method of claim 11 to 14.
16., it is characterized in that said candidate upper reaches LSR is on the equative route or on the non-equivalence path according to each described method of claim 11 to 14; If on equative route, then corresponding said load balancing algorithm is the equal cost multipath algorithm, if on the non-equivalence path, then corresponding said load balancing algorithm is a weight multipath algorithm.
CN2006100783670A 2006-05-15 2006-05-15 Method for transmitting multi cast data in shared network Active CN101075842B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2006100783670A CN101075842B (en) 2006-05-15 2006-05-15 Method for transmitting multi cast data in shared network
PCT/CN2007/000564 WO2007131403A1 (en) 2006-05-15 2007-02-15 A multicast data transmission method on shared segments and label switching router

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2006100783670A CN101075842B (en) 2006-05-15 2006-05-15 Method for transmitting multi cast data in shared network

Publications (2)

Publication Number Publication Date
CN101075842A CN101075842A (en) 2007-11-21
CN101075842B true CN101075842B (en) 2012-06-27

Family

ID=38693525

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2006100783670A Active CN101075842B (en) 2006-05-15 2006-05-15 Method for transmitting multi cast data in shared network

Country Status (2)

Country Link
CN (1) CN101075842B (en)
WO (1) WO2007131403A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9571364B2 (en) * 2012-07-13 2017-02-14 Telefonaktiebolaget L M Ericsson (Publ) Connectivity fault management in a communication network

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1483266A (en) * 2000-09-06 2004-03-17 ŵ�������繫˾ Multicast route in AD-HOC network
CN1549521A (en) * 2003-05-07 2004-11-24 华为技术有限公司 Method for realizing universal multi-protocol mark exchange in network

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8488616B2 (en) * 2005-04-05 2013-07-16 Cisco Technology, Inc. Building multipoint-to-multipoint label switch paths

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1483266A (en) * 2000-09-06 2004-03-17 ŵ�������繫˾ Multicast route in AD-HOC network
CN1549521A (en) * 2003-05-07 2004-11-24 华为技术有限公司 Method for realizing universal multi-protocol mark exchange in network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李建元等.MPLS关键技术及其应用.《南昌大学学报(工科版)》.2004,第25卷(第04期),65-69. *

Also Published As

Publication number Publication date
WO2007131403A1 (en) 2007-11-22
CN101075842A (en) 2007-11-21

Similar Documents

Publication Publication Date Title
US7787380B1 (en) Resource reservation protocol with traffic engineering point to multi-point label switched path hierarchy
US7860104B1 (en) Upstream label assignment for the resource reservation protocol with traffic engineering
CN109150580B (en) Protocol independent multicast join entropy
US7839862B1 (en) Upstream label assignment for the label distribution protocol
JP5691703B2 (en) Multicast network system
EP2371093B1 (en) Method and system for multicast path switching, corresponding network and computer program product
US20090219806A1 (en) Method, apparatus, and system for protecting head node of point to multipoint label switched path
CN101645790B (en) Switching-over method, device and system of multicast distribution tree
CN102217238A (en) Service instance applied to mpls networks
CN102638389A (en) Redundancy backup method and system of TRILL (Transparent Interconnection over Lots of Links) network
CN101369958A (en) Fast rerouting method and label exchange router
CN102148745A (en) Method and system for increasing forwarding efficiency of virtual private LAN service network
CN101674224B (en) Method, label switching router and system for generating forwarding-table item information
CN103117925A (en) Processing method and processing device for data message forward
CN102130829B (en) Method and device for establishing label switch paths (LSP)
CN102217254B (en) Method and apparatus for transferring boot strap information
CN102447611A (en) Method and system for establishing bidirectional point-to-multipoint label switched path as well as method and system for removing bidirectional point-to-multipoint label switched path
JP2009060609A (en) Method and apparatus for multicast tree allocation
JP3780987B2 (en) Route control method and apparatus, route control program, and storage medium storing route control program
CN101924704B (en) Method and device thereof for switching double-layer multicast links
CN101453414B (en) Head node protection method, system and equipment for point to multiple points label switch path
JP5669955B2 (en) Network configuration method, ring network system, and node
EP2571201B1 (en) Method, device and system for forwarding data under protocol independent multicast (pim) dual join
CN102571534B (en) Service transmission method based on ring network protection and node used for service transmission
CN101075842B (en) Method for transmitting multi cast data in shared network

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