CN101588296B - Method, head node and tail node of forwarding multicasting message - Google Patents
Method, head node and tail node of forwarding multicasting message Download PDFInfo
- Publication number
- CN101588296B CN101588296B CN200910086654XA CN200910086654A CN101588296B CN 101588296 B CN101588296 B CN 101588296B CN 200910086654X A CN200910086654X A CN 200910086654XA CN 200910086654 A CN200910086654 A CN 200910086654A CN 101588296 B CN101588296 B CN 101588296B
- Authority
- CN
- China
- Prior art keywords
- message
- traffic engineering
- tail node
- interface
- engineering tunnel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
The invention provides a method, head node and tail node of a forwarding multicasting message, where the method includes: the head node the multiprotocol label switching (MPLS) traffic engineering (TE) tunnel transmits the path message to the tail node of the MPLS TE tunnel through the main label switching path of the MPLS TE tunnel; the tail node acquires the range of the multicasting address supported by the MPLS TE tunnel from the path message; the tail node transmits the adding message in the multicasting address range by the requested multicasting address through the MPLS TE tunnel; afterthe head node receives the adding message transmitted by the tail node, the head node adds the MPLS TE tunnel interface to the shortest path tree (SPT) outlet interface list corresponding to the mult icasting address requested by the adding message; after the head node receives the multicasting message, the head node transmits the multicasting message according to the SPT outlet interface list corresponding to the multicasting address of the multicasting message.
Description
Technical field
The present invention relates to network communications technology field, particularly a kind of method of forwarding multicasting message, head node and tail node.
Background technology
Traffic engineering (TE, Traffic Engineering) is the mode that is used for equiblibrium mass distribution that extensively adopts in the present network, and target is to avoid in the network bandwidth of part of links to be overused and other link bandwidth is not fully utilized.When TE and multiprotocol label switching (MPLS, Multi Protocol LabelSwitch) when technology combines, can be used for solving the network congestion problem of MPLS network, the traffic engineering tunnel of setting up in the MPLS network is called the MPLS traffic engineering tunnel.
Message on the MPLS traffic engineering tunnel is transmitted by setting up good label forwarding path (LSP) in advance based on label; other node in the MPLS traffic engineering tunnel except head node and tail node need not to carry out the list item inquiry; transmit according to the label that carries in the message and to get final product, and can exist many LSP to realize link protection and Node Protection on same mpls-te tunnel.As shown in Figure 1, suppose to have the MPLS traffic engineering tunnel between router R1 and the router R4, wherein, router R1 is a head node, and router R4 is a tail node, wherein R3 is Point of Local Repair (PLR, Point of LocalRepair), via the LSP of R3, R4 as main LSP, via the LSP of R3, R5 and R4 as bypass LSP, after the link among the main LSP or node break down, can switch on the bypass LSP immediately.
Though the MPLS traffic engineering tunnel has above-mentioned advantage, but, present MPLS traffic engineering tunnel transmits because only being used for unidirectional message, be unidirectional tunnel, and the forwarding of multicast message is based on the shortest path tree (SPT that utilizes adding or prune packet to set up, Shortest Path Tree), and the transmission of adding or prune packet is opposite with the transmission of multicast message, and therefore, existing MPLS traffic engineering tunnel can not be used for the forwarding of multicast message and handle.
Summary of the invention
In view of this, the invention provides a kind of method, head node and tail node of forwarding multicasting message, facilitate the use the forwarding that the MPLS traffic engineering tunnel realizes multicast message.
A kind of method of forwarding multicasting message, this method comprises:
The head node of A, multiprotocol label switching MPLS TE tunnel of traffic engineering passes through the main label switching path LSP of this MPLS traffic engineering tunnel to the tail node transmit path Path of this MPLS traffic engineering tunnel message;
B, described tail node are obtained the multicast address scope that described MPLS traffic engineering tunnel is supported from described Path message, this main LSP is gone up tail node and last jump the inverse path forwarding RPF interface that the interface that is connected is recorded as multicast;
C, described tail node be multicast address the joining message in described multicast address scope of request, carries the identification information and the tail node information of described MPLS traffic engineering tunnel by extended attribute, transmits by described MPLS traffic engineering tunnel;
After D, described head node receive joining message of described tail node transmission, determine that described joining message sends into the tail node of described MPLS traffic engineering tunnel, MPLS traffic engineering tunnel interface is added in the shortest path tree SPT outgoing interface tabulation of multicast address correspondence of the described request of joining message, and transmit described joining message to multicast source;
After E, described head node receive multicast message, transmit described multicast message according to the SPT outgoing interface tabulation of the multicast address correspondence of this multicast message.
A kind of head node of MPLS traffic engineering tunnel, this head node comprises: information receiving and transmitting unit, interface processing unit and message retransmission unit;
Described information receiving and transmitting unit is used for sending Path message by the main LSP of MPLS traffic engineering tunnel to the tail node of this MPLS traffic engineering tunnel; Described Path message is carried the multicast address scope that described MPLS traffic engineering tunnel is supported by the multicast address object of expansion; Receive joining message of described tail node transmission, and transmit described joining message to multicast source;
Described interface processing unit is used to judge described joining message when carrying the information of described tail node by extended attribute, MPLS traffic engineering tunnel interface is added in the SPT outgoing interface tabulation of multicast address correspondence of the described request of joining message;
Described message retransmission unit after being used to receive multicast message, is transmitted described multicast message according to the SPT outgoing interface tabulation of the multicast address correspondence of this multicast message.
A kind of tail node of MPLS traffic engineering tunnel, this tail node comprises: message sink unit, information acquisition unit, interface record cell and message process unit;
Described message sink unit is used to receive the Path message of the head node of MPLS traffic engineering tunnel by the main LSP transmission of MPLS traffic engineering tunnel;
Described information acquisition unit is used for obtaining the multicast address scope that described MPLS traffic engineering tunnel is supported from described Path message;
Described interface record cell is used for after described message sink unit receives described Path message, this main LSP is gone up tail node jump the RPF interface that the interface that is connected is recorded as multicast with last one;
Described message process unit, be used for will request multicast address joining message in described multicast address scope, carry the identification information and the tail node information of described MPLS traffic engineering tunnel by extended attribute, transmit by described MPLS traffic engineering tunnel.
As can be seen from the above technical solutions, head node sends Path message by the main LSP in the MPLS traffic engineering tunnel to tail node among the present invention, tail node is obtained the multicast address scope that this MPLS traffic engineering tunnel is supported from this Path message, and with the request multicast address joining message in this multicast address scope transmit by this MPLS traffic engineering tunnel, make head node MPLS traffic engineering tunnel interface can be added in the corresponding SPT outgoing interface tabulation, thereby make the MPLS traffic engineering tunnel finish the support function of multicast message, after head node receives multicast message, can transmit according to the SPT outgoing interface tabulation of correspondence, realize utilizing MPLS traffic engineering tunnel forwarding multicasting message.Use under the increasingly extensive situation at network multicast, effectively utilize the MPLS traffic engineering tunnel, make bandwidth resources in the multicast forwarding process, obtain more reasonably using.
Description of drawings
Fig. 1 is the tunnel schematic diagram of MPLS TE of the prior art;
The detailed method flow chart that Fig. 2 provides for the embodiment of the invention;
The network architecture diagram that Fig. 3 provides for the embodiment of the invention;
Fig. 4 is a RSVP TE protocol signaling message format schematic diagram;
Fig. 5 is the multicast address Format Object schematic diagram in the expansion Path message;
Fig. 6 is the form schematic diagram of existing PIM protocol massages;
Fig. 7 is for carrying the attribute format schematic diagram of MPLS traffic engineering tunnel identification information and tail node information in the PIM protocol massages;
The head node structural representation that Fig. 8 provides for the embodiment of the invention;
The tail node structural representation that Fig. 9 provides for the embodiment of the invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
Method provided by the present invention mainly comprises: the head node of MPLS traffic engineering tunnel is via the main LSP in this MPLS tunnel tail node transmit path (Path) message to the MPLS traffic engineering tunnel; The tail node of MPLS traffic engineering tunnel is obtained the multicast address scope that this MPLS traffic engineering tunnel is supported from Path message, this main LSP is gone up tail node and last jump inverse path forwarding (RPF) interface that the interface that is connected is recorded as multicast; Multicast address the joining message in described multicast address scope of request transmitted by this MPLS traffic engineering tunnel; After head node receives joining message that tail node sends, during the SPT outgoing interface that the mpls-te tunnel interface is added the multicast address correspondence of asking is tabulated, and transmit this and join message; After head node receives multicast message, transmit according to the SPT outgoing interface tabulation of the multicast address correspondence of this multicast message.
Below in conjunction with specific embodiment said method is described in detail.The detailed method flow chart that Fig. 2 provides for the embodiment of the invention, this method can be based upon on as shown in Figure 3 the network architecture, and as shown in Figure 2, this method can may further comprise the steps:
Step 201: the MPLS traffic engineering tunnel that is identified for multicast data forwarding.
Can set up the MPLS traffic engineering tunnel that is used for multicast data forwarding separately in the present invention, also can multiplex unicast MPLS traffic engineering tunnel be used for the forwarding of multicast packet.If when having a large amount of multicast packet in the network, the more convenient bandwidth of carrying out of MPLS traffic engineering tunnel that adopts foundation to be used for multicast data forwarding is separately controlled, because MPLS traffic engineering tunnel information safeguards that by the tunnel head node this kind mode head node need be safeguarded many MPLS traffic engineering tunnel information.
All-router all is published to the link information of self in the network in the network, for example maximum link bandwidth, maximum reservable bandwidth, current bandwidth reserved etc., thus form traffic engineering database (TEDB).Utilize the information calculations among the TEDB to go out a LSP, can adopt the mode of specifying a LSP, also can adopt SPF (CSPF) algorithm to calculate a LSP based on constraint for setting up the use of MPLS traffic engineering tunnel.Wherein, specifying the mode of a LSP is each jumping of clearly specifying the mpls-te tunnel process on head node.The mode of CSPF algorithm computation is only to specify constraints on head node, utilizes TEDB to satisfy the LSP of constraints in conjunction with the CSPF algorithm computation.
Step 202:MPLS traffic engineering tunnel head node sends Path message via the main LSP of MPLS traffic engineering tunnel to tail node, comprises the multicast address scope that the MPLS traffic engineering tunnel is supported in this Path message.
As shown in Figure 3, can on the MPLS of head node R1 traffic engineering tunnel interface, dispose the multicast address scope that multicast routing protocol and this MPLS traffic engineering tunnel are supported in advance in the embodiment of the invention.
The present invention can introduce multicast address (Multicast-Address) object and be used for carrying the multicast address scope that the MPLS traffic engineering tunnel is supported by expansion RSVP TE agreement in Path message.
Understand for convenience and at first RSVP TE protocol signaling message format is simply introduced, Fig. 4 is a RSVP TE protocol signaling message format, and its protocol number is 46.Wherein version (Version) field is carried version information, has only version 1 at present; Sign (Flag) field is undefined temporarily; Type of message (Message Type) field is carried message type information, 1 sign Path message, 2 identifying resources are reserved (Resv) message, 3 sign path error (PathError) message, 4 identifying resource reservation error (ResvError) message, (PathTear) message is removed in 5 sign paths, 6 identifying resources are removed (ResvTear) message, 7 identifying resource reservation confirmation (ResvConf) message, 10 identifying resources are removed and are confirmed (ResvTeafConf) message, 20 sign heartbeat (Hello) message; The message verification and (MessageChecksum) field carry the verification and the information of whole message; Time-to-live (Send TLL) field is carried the jumping figure information of this message survival; Message-length (Message Lengh) field is carried the length information of whole message.Remaining field is the information of the entrained object of message among Fig. 4, and wherein, object length (Length) is carried object length information; Object number (Object Class) field is carried object-type information; C type (C-type) field combines object of unique definition with the object number field.
The present invention to expand in Path message introduce the multicast address object form as shown in Figure 5, object number can be set to 25 these objects of sign and carried the multicast address scope this moment, the C-Type field can be set to 1 and represent IPv4.
In addition, this Path message can also be carried a last hop-information of tail node among identification information, head node information and the LSP of identification information, LSP of tail node information, the MPLS traffic engineering tunnel of MPLS traffic engineering tunnel by collective (Session) object.
Head node R1 sends to tail node R4 with above-mentioned Path message by the main LSP in the tunnel, and this main LSP can be the unique LSP in the MPLS traffic engineering tunnel; When having many LSP in the MPLS traffic engineering tunnel, the LSP that sends Path message is main LSP wherein; When having enabled quick heavy-route characteristic, when carrying out the LSP switching, the main LSP after switching sends Path message; When having enabled the re-optimization characteristic, send Path message from the more excellent main LSP that occurs.Hypothesis R1 sends Path message from the LSP that R1-R2-R3-R4 constitutes to tail node among Fig. 3.
Step 203: after the Path message that tail node receives, determine from tail node according to the tail node information of carrying in the Path message as the MPLS traffic engineering tunnel, obtain the multicast address range information that a hop-information and MPLS traffic engineering tunnel are supported on the identification information, head node information, tail node information, tail node of identification information, the LSP of MPLS traffic engineering tunnel from Path message, record comprises the list item of these information of obtaining.
The identification information of MPLS traffic engineering tunnel, the identification information of LSP, head node information, tail node information can go out the path that forwarding multicasting message adopts by unique identification.The list item of tail node record can be as shown in table 1.
Table 1
| Tunnel mark information | The identification information of LSP | Head node information | Tail node information | A last hop-information of tail node | Initial multicast address | Stop multicast address |
| Tunnel ID | LSP?ID | Head node address, tunnel | Tail node address, tunnel | Last one of tail node is jumped the address | The initial value of the multicast address scope of carrying in the multicast object | The stop value of the multicast address scope of carrying in the multicast object |
Behind the tail node R4 record list item, return Resv message, thereby this Resv message is used to carry the foundation that other option of distributed labels information and negotiation is finished LSP to head node R1.
In this step, tail node can further be carried out record to the RPF interface, is specially: a hop-information in the path message that utilization receives on this LSP, and the last tail node of this LSP and last is jumped the interface that is connected be recorded as the RPF interface.Usually only write down a RPF interface at a MPLS traffic engineering tunnel.
Step 204: after tail node receives joining message of downstream transmission, judge that according to the list item of record this joins message the multicast address of being asked whether in the multicast address scope that the MPLS traffic engineering tunnel is supported, if, execution in step 205, otherwise according to existing protocol independent multicast (PIM) agreement flow process this multicast message is handled.
Step 205: in joining message, carry the identification information and the tail node information of MPLS traffic engineering tunnel, be packaged into unicast message, and utilize the RPF interface of record to send to head node.
If join message the multicast address of asking to add in the multicast address scope that the MPLS traffic engineering tunnel is supported, then this joins message and need be transferred to head node to set up the SPT of this multicast correspondence by the MPLS traffic engineering tunnel.
In this step, can carry the identification information and the tail node information of MPLS traffic engineering tunnel by expansion PIM protocol massages.Fig. 6 is the form of existing PIM protocol massages, and wherein type of coding (Encoding Type) field is that 1 o'clock sign is carried extended attribute; Whether continue during the nonrecognition of F field identification extended attribute to transmit, must continue upwards to transmit when being changed to 1 o'clock this attribute of sign router nonrecognition, abandon this message when being changed to 0 o'clock this attribute of sign router nonrecognition; At the bottom of whether the E field identification is stack.Fig. 7 carries the identification information of MPLS traffic engineering tunnel and the attribute format of tail node information.This moment, the F field can be changed to 0, and attribute type (Attr Type) field can be set to 2 and be used to identify identification information and the tail node information that this attribute carries the MPLS traffic engineering tunnel.
Step 206: after head node receives and joins message, according to its extended attribute determine this join message be tail node send the time, the MPLS tunnel interface is added the SPT outgoing interface tabulation of this multicast address correspondence of being asked of joining message, and continue to transmit this and join message to multicast source.
Step 207: after head node receives multicast message, transmit according to the SPT outgoing interface tabulation of the multicast address correspondence of this multicast message.
If head node has added MPLS traffic engineering tunnel interface by step 201-206 the SPT outgoing interface tabulation of multicast address 1 correspondence, receive the multicast message of multicast address 1 when head node after, just can transmit this multicast message by the SPT outlet tabulation of this multicast address 1 correspondence, wherein also comprise MPLS traffic engineering tunnel interface, thereby realize carrying out the forwarding of multicast message by the MPLS traffic engineering tunnel.
Can realize the forwarding of the multicast message in the multicast address scope that the MPLS traffic engineering tunnel supported via above-mentioned steps 201-207.
Be to be the description that example is carried out among the above-mentioned steps 204-206 to join message, processing mode for prune packet is basic identical, just at the head node place, deletion the SPT outgoing interface tabulation of the multicast address correspondence that the MPLS tunnel interface need be asked from prune packet.
If the MPLS traffic engineering tunnel has adopted the FRR characteristic, if the convergent point (MP) of main LSP and bypass LSP is positioned at the intermediate node of MPLS traffic engineering tunnel, when the LSP switching takes place when, last one of tail node is jumped and can't be changed, correspondingly, the RPF interface of this MPLS traffic engineering tunnel can not change yet, and therefore, does not need to carry out extra processing for this situation head node and tail node.
If the MP of main LSP and bypass LSP is in tail node, then after LSP switches, tail node can be received the notice of the LSP switching of carrying MP information, determine certainly as MP, also can receive the Path message that Point of Local Repair (PLR) comes by backup LSP forwarding, determine after tail node as the MPLS traffic engineering tunnel, this moment, tail node can be according to the list item of the contents of object updated stored of Path message, it is the identification information of the LSP in the list item, a last hop-information of tail node can change, and redefine the RPF interface, and the RPF interface that utilizes the RPF interface replacement that redefines to write down according to the last hop-information after upgrading.As shown in Figure 3, suppose that main LSP switches to R1-R2-R3-R5-R4 (as shown in phantom in FIG.) from the path of R1-R2-R3-R4, head node R1 can send Path message to tail node R4 by the LSP of R1-R2-R3-R5-R4, after R4 receives this Path message, if determine from MP as generation LSP switching, then according to the list item of the contents of object updated stored of Path message, this moment, the identification information of LSP changed, last one of tail node R4 jumps and becomes R5 by R3, utilizes the more RPF interface of new record of the last interface that is connected with R5 of R4 according to the information of R5.
When LSP deletes, head node can send the PathTear message of the identification information of the identification information carry the MPLS traffic engineering tunnel and LSP to tail node, after tail node receives this PathTear message, deletion comprises the list item of the identification information of the identification information of this MPLS traffic engineering tunnel and LSP, and deletion is based on the RPF interface of this LSP record.In addition, when MPLS traffic engineering tunnel interface being added the tabulation of SPT outgoing interface, can identify the LSP of this MPLS traffic engineering tunnel interface correspondence, when deletion LSP, can be unique MPLS traffic engineering tunnel interface that should LSP be deleted from the tabulation of SPT outgoing interface.
If the MPLS traffic engineering tunnel has disposed the re-optimization characteristic, promptly work as the MPLS traffic engineering tunnel because some reason has occurred one than the more excellent LSP of current main LSP, head node can switch to flow on the more excellent LSP, is about to this more excellent LSP as main LSP.If after more excellent LSP sets up, original LSP does not also have deletion, then may occur two main LSP simultaneously.
More excellent LSP is when setting up, head node can send path message to tail node by this more excellent LSP, after tail node receives this path message, determine from tail node according to the tail node information of carrying in this Path message as the MPLS traffic engineering tunnel, obtain the multicast address range information that a hop-information and MPLS traffic engineering tunnel are supported on the identification information, head node information, tail node information, tail node of the identification information of MPLS traffic engineering tunnel, newly-established LSP from this Path message, record comprises the list item of these information of obtaining.Will exist two list items of the sign that comprises same MPLS traffic engineering tunnel this moment, under and the situation of depositing temporary transient at this two LSP, exist two list items can't influence the forwarding of adding or prune packet simultaneously, only need timely RPF interface to upgrade to multicast, promptly utilize LSP more excellent in the list item of new record to go up a last hop-information of tail node, the last tail node of the LSP that this is more excellent and last one is jumped the interface that is connected and is defined as the RPF interface, judge whether to record the RPF interface, if then utilize the new RPF interface of determining to replace the RPF interface that has existed.That is to say, before record RPF interface, can further include: judge whether to record the RPF interface message, if utilize the new RPF interface message of determining to replace the RPF interface message that has write down; Otherwise, directly write down this RPF interface message of determining.In addition, after more excellent LSP sets up, head node can be with original LSP deletion, be specially: the PathTear message that sends the identification information of the identification information carry the MPLS traffic engineering tunnel and original LSP, after tail node received this PathTear message, deletion comprised the list item of the identification information of the identification information of this MPLS traffic engineering tunnel and LSP.
More than be the detailed description that method provided by the present invention is carried out, head node and the tail node to MPLS traffic engineering tunnel provided by the present invention is described in detail below.
The head node structural representation that Fig. 8 provides for the embodiment of the invention, as shown in Figure 8, this head node can comprise: information receiving and transmitting unit 801, interface processing unit 802 and message retransmission unit 803.
Information receiving and transmitting unit 801 is used for sending Path message by the main LSP of MPLS traffic engineering tunnel to the tail node of this MPLS traffic engineering tunnel; Receive joining message that tail node sends, and transmit this and join message.
When the MPLS traffic engineering tunnel has only a main LSP, send Path message by this main LSP; When the MPLS traffic engineering tunnel is carried out the LSP switching, send Path message by the main LSP after switching; When having enabled the re-optimization characteristic, when more excellent LSP occurring, may there be two main LSP, on new main LSP, also send Path message.
Wherein, above-mentioned Path message is carried the multicast address scope that the MPLS traffic engineering tunnel is supported by the multicast address object of expansion.
Particularly, interface processing unit 802 can comprise: judgment sub-unit 8021 and processing subelement 8022.
In addition, information receiving and transmitting unit 801 can also be used to receive prune packet.
Above-mentioned judgment sub-unit 8021 can also be used for judging that whether prune packet carries the information of tail node by extended attribute.
The tail node structural representation that Fig. 9 provides for the embodiment of the invention, as shown in Figure 9, this tail node can comprise: message sink unit 901, information acquisition unit 902, interface record cell 903 and message process unit 904.
Further, this tail node can also comprise: list item record cell 904.
List item record cell 904 is used to write down and comprises the information that information acquisition unit 902 obtains and the list item of multicast address scope.
More preferably, the situation that main LSP switches takes place in order to be adapted to the MPLS traffic engineering tunnel, this tail node can also comprise: first judging unit 906, be used for before the operation of list item record cell 904 executive loggings, judge whether this tail node has received the LSP switching notice that comprises this tail node information, if not, send the record notice to list item record cell 904, if send the replacement notice to list item record cell 904.
Correspondingly, list item record cell 904 can receive the operation of record notice back executive logging, receive replace notice after, utilize the list item that comprises information that information acquisition unit 902 obtains and multicast address scope to replace the existing list item of the identification information that comprises the MPLS traffic engineering tunnel.
More preferably, when certain bar LSP of needs deletions MPLS traffic engineering tunnel, head node sends the PathTear message of the identification information of the identification information that carries the MPLS traffic engineering tunnel and LSP to tail node; At this moment,
Correspondingly, list item record cell 904 can also be used for after message sink unit 901 receives PathTear message, and deletion comprises the list item of the identification information of the identification information of MPLS traffic engineering tunnel and LSP.
In addition, when the MPLS traffic engineering tunnel has enabled the re-optimization characteristic, more excellent LSP may occur sets up when being called main LSP, main LSP originally is not deletion as yet, at this moment, this tail node can also comprise: second judging unit 907, be used for before the operation of interface record cell 903 executive loggings, judge the RPF interface message whether interface record cell 903 has recorded at the MPLS traffic engineering tunnel, if, notification interface record cell 903 utilizes the last tail node of this main LSP and last to jump the interface message that is connected and replaces the RPF interface message that has write down, otherwise notification interface record cell 903 continues the operation of executive loggings.In this case, the sign that has the MPLS traffic engineering tunnel on the tail node is identical, but LSP sign two list items different with a last hop-information, but only have one at the RPF interface of MPLS traffic engineering tunnel.
Particularly, message process unit 904 transmit join message in carry mpls-te tunnel by extended attribute identification information and tail node information.
By above description as can be seen, head node sends Path message by the main LSP in the MPLS traffic engineering tunnel to tail node among the present invention, tail node is obtained the multicast address scope that this MPLS traffic engineering tunnel is supported from this Path message, and with the request multicast address joining message in this multicast address scope transmit by this MPLS traffic engineering tunnel, make head node MPLS traffic engineering tunnel interface can be added in the corresponding SPT outgoing interface tabulation, thereby make the MPLS traffic engineering tunnel finish the support function of multicast message, after head node receives multicast message, can transmit according to the SPT outgoing interface tabulation of correspondence, realize utilizing MPLS traffic engineering tunnel forwarding multicasting message.Use under the increasingly extensive situation at network multicast, effectively utilize the MPLS traffic engineering tunnel, make bandwidth resources in the multicast forwarding process, obtain more reasonably using.
In addition, the quick heavy-route characteristic and the re-optimization characteristic that the present invention is directed to the MPLS traffic engineering tunnel also provide solution at length, thereby adapt to the demand of various network conditions.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being made, is equal to replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (17)
1. the method for a forwarding multicasting message is characterized in that, this method comprises:
The head node of A, multiprotocol label switching MPLS TE tunnel of traffic engineering passes through the main label switching path LSP of this MPLS traffic engineering tunnel to the tail node transmit path Path of this MPLS traffic engineering tunnel message;
B, described tail node are obtained the multicast address scope that described MPLS traffic engineering tunnel is supported from described Path message, this main LSP is gone up tail node and last jump the inverse path forwarding RPF interface that the interface that is connected is recorded as multicast;
C, described tail node be multicast address the joining message in described multicast address scope of request, carries the identification information and the tail node information of described MPLS traffic engineering tunnel by extended attribute, transmits by described MPLS traffic engineering tunnel;
After D, described head node receive joining message of described tail node transmission, determine that described joining message sends into the tail node of described MPLS traffic engineering tunnel, MPLS traffic engineering tunnel interface is added in the shortest path tree SPT outgoing interface tabulation of multicast address correspondence of the described request of joining message, and transmit described joining message to multicast source;
After E, described head node receive multicast message, transmit described multicast message according to the SPT outgoing interface tabulation of the multicast address correspondence of this multicast message.
2. method according to claim 1 is characterized in that, described Path message is carried the multicast address scope that described MPLS traffic engineering tunnel is supported by the multicast address object of expansion.
3. method according to claim 1, it is characterized in that, described step B also comprises: described tail node is also obtained a hop-information on the identification information, head node information, tail node information, tail node of the identification information of described MPLS traffic engineering tunnel, described LSP from described Path message, and record comprises the information obtained and the list item of described multicast address scope.
4. method according to claim 3, it is characterized in that, comprise at record before the list item of the information obtained and described multicast address scope, also comprise: described tail node judges whether to receive the LSP switching notice that comprises this tail node information, if not, carry out described record and comprise the information obtained and the list item of described multicast address scope, if utilize the list item comprise the information obtained and described multicast address scope to replace the existing list item of the identification information that comprises described MPLS traffic engineering tunnel.
5. method according to claim 3, it is characterized in that, this method also comprises: after PathTear message is removed in the path that described tail node receives the identification information of the identification information that carries described MPLS traffic engineering tunnel and described LSP, deletion comprises the list item of the identification information of the identification information of described MPLS traffic engineering tunnel and described LSP, and deletes described RPF interface.
6. method according to claim 1, it is characterized in that, described will this main LSP on tail node with on one jump before the interface that is connected is recorded as the RPF interface of multicast, also comprise: judge whether to record RPF interface message at described MPLS traffic engineering tunnel, if, utilize the last tail node of this main LSP and last to jump the interface message that is connected and replace the RPF interface message that has write down, finish described step B; Otherwise, continue to carry out and describedly will this main LSP to go up the interface that tail node and a last jumping be connected and be recorded as the RPF interface.
7. method according to claim 1, it is characterized in that, described step C specifically comprises: after described tail node receives and joins message, judge that the described multicast address of being asked of joining message is whether in the multicast address scope in described list item, if transmit described joining message by described RPF interface.
8. method according to claim 1 is characterized in that, described tail node is transmitted described prune packet after receiving the prune packet of multicast address in described multicast address scope of request by described MPLS traffic engineering tunnel;
After described head node receives the prune packet of described tail node transmission, with the deletion from the SPT outgoing interface tabulation of the multicast address correspondence of this prune packet request of MPLS tunnel interface.
9. the head node of a MPLS traffic engineering tunnel is characterized in that, this head node comprises: information receiving and transmitting unit, interface processing unit and message retransmission unit;
Described information receiving and transmitting unit is used for sending Path message by the main LSP of MPLS traffic engineering tunnel to the tail node of this MPLS traffic engineering tunnel; Described Path message is carried the multicast address scope that described MPLS traffic engineering tunnel is supported by the multicast address object of expansion; Receive joining message of described tail node transmission, and transmit described joining message to multicast source;
Described interface processing unit is used to judge described joining message when carrying the information of described tail node by extended attribute, MPLS traffic engineering tunnel interface is added in the SPT outgoing interface tabulation of multicast address correspondence of the described request of joining message;
Described message retransmission unit after being used to receive multicast message, is transmitted described multicast message according to the SPT outgoing interface tabulation of the multicast address correspondence of this multicast message.
10. head node according to claim 9 is characterized in that, described interface is handled unit pack and drawn together: judgment sub-unit and processing subelement;
Described judgment sub-unit is used to judge that whether described joining message carry the information of described tail node by extended attribute;
Described processing subelement is used in the judged result of described judgment sub-unit when being, MPLS traffic engineering tunnel interface is added in the SPT outgoing interface tabulation of multicast address correspondence of the described request of joining message.
11. head node according to claim 10 is characterized in that, described information receiving and transmitting unit also is used to receive prune packet;
Described judgment sub-unit is used for also judging that whether described prune packet carries the information of described tail node by extended attribute;
Described processing subelement also is used in the judged result of described judgment sub-unit when being, with the deletion from the SPT outgoing interface tabulation of the multicast address correspondence of described prune packet request of mpls-te tunnel interface.
12. the tail node of a MPLS traffic engineering tunnel is characterized in that, this tail node comprises: message sink unit, information acquisition unit, interface record cell and message process unit;
Described message sink unit is used to receive the Path message of the head node of MPLS traffic engineering tunnel by the main LSP transmission of MPLS traffic engineering tunnel;
Described information acquisition unit is used for obtaining the multicast address scope that described MPLS traffic engineering tunnel is supported from described Path message;
Described interface record cell is used for after described message sink unit receives described Path message, this main LSP is gone up tail node jump the RPF interface that the interface that is connected is recorded as multicast with last one;
Described message process unit, be used for will request multicast address joining message in described multicast address scope, carry the identification information and the tail node information of described MPLS traffic engineering tunnel by extended attribute, transmit by described MPLS traffic engineering tunnel.
13. tail node according to claim 12 is characterized in that, this tail node also comprises: the list item record cell;
Described information acquisition unit also is used for obtaining a hop-information on the identification information, head node information, tail node information, tail node of the identification information of described MPLS traffic engineering tunnel, described LSP from described Path message;
Described list item record cell is used to write down and comprises the information that described information acquisition unit obtains and the list item of described multicast address scope.
14. tail node according to claim 13, it is characterized in that, this tail node also comprises: first judging unit, be used for before described list item record cell is carried out the operation of described record, judge whether this tail node has received the LSP switching notice that comprises this tail node information, if not, send the record notice to described list item record cell, if send the replacement notice to described list item record cell;
Described list item record cell receives the operation that described record is carried out in record notice back, receive replace notice after, utilize the list item that comprises information that described information acquisition unit obtains and described multicast address scope to replace the existing list item of the identification information that comprises described MPLS traffic engineering tunnel.
15. tail node according to claim 13 is characterized in that, described message sink unit also is used to receive the PathTear message of the identification information of the identification information that carries described MPLS traffic engineering tunnel and described LSP;
Described list item record cell also is used for after described message sink unit receives described PathTear message, and deletion comprises the list item of the identification information of the identification information of described MPLS traffic engineering tunnel and described LSP;
Described interface record cell also is used for deleting described RPF interface after described message sink unit receives described PathTear message.
16. tail node according to claim 12, it is characterized in that, this tail node also comprises: second judging unit, be used for before described interface record cell is carried out the operation of described record, judge whether described interface record cell has recorded the RPF interface message at described MPLS traffic engineering tunnel, if, notify described interface record cell to utilize the last tail node of this main LSP and last to jump the interface message that is connected and replace the RPF interface message that has write down, otherwise, notify described interface record cell to continue to carry out the operation of described record.
17. tail node according to claim 12 is characterized in that, described message process unit also is used for the prune packet of multicast address in described multicast address scope of request transmitted by described MPLS TE tunnel.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910086654XA CN101588296B (en) | 2009-06-16 | 2009-06-16 | Method, head node and tail node of forwarding multicasting message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910086654XA CN101588296B (en) | 2009-06-16 | 2009-06-16 | Method, head node and tail node of forwarding multicasting message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101588296A CN101588296A (en) | 2009-11-25 |
| CN101588296B true CN101588296B (en) | 2011-09-07 |
Family
ID=41372367
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910086654XA Expired - Fee Related CN101588296B (en) | 2009-06-16 | 2009-06-16 | Method, head node and tail node of forwarding multicasting message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101588296B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101917343B (en) * | 2010-08-23 | 2015-06-03 | 中兴通讯股份有限公司 | Re-optimized triggering method and system |
| CN101984604A (en) | 2010-11-12 | 2011-03-09 | 中兴通讯股份有限公司 | Tunnel multiplexing method in linear protection groups and tail nodes of tunnels |
| CN102123088B (en) * | 2011-02-21 | 2015-09-23 | 杭州华三通信技术有限公司 | Set up the method and apparatus of traffic engineering tunnel |
| US9130857B2 (en) * | 2011-06-22 | 2015-09-08 | Futurewei Technologies, Inc. | Protocol independent multicast with quality of service support |
| CN102594645B (en) * | 2011-11-25 | 2017-12-01 | 中兴通讯股份有限公司 | The method for dismounting and node device of traffic engineering tunnel in distributed network |
| CN103166850B (en) * | 2011-12-08 | 2016-03-16 | 上海贝尔股份有限公司 | Set up the method for the label switched path of two equipment rooms outside MPLS network |
| CN103067286B (en) * | 2013-01-25 | 2016-06-08 | 杭州华三通信技术有限公司 | A kind of muticast data transmission method and apparatus |
| CN104426763B (en) | 2013-08-21 | 2018-10-26 | 南京中兴新软件有限责任公司 | Tunnel switching method, device and interchanger |
| CN103581027B (en) * | 2013-09-06 | 2017-06-16 | 上海斐讯数据通信技术有限公司 | A kind of method that optimization PIM SM Multicast Routings are set up |
| CN105591967B (en) * | 2014-11-12 | 2019-06-28 | 华为技术有限公司 | A kind of data transmission method and device |
| CN105591957B (en) * | 2015-11-18 | 2019-04-19 | 新华三技术有限公司 | A kind of multicast stream control method and device based on point-to-multi-point tunnel |
| CN109067578B (en) * | 2018-07-31 | 2021-05-25 | 杭州迪普科技股份有限公司 | Method and device for multicast fast switching |
| CN115442295A (en) * | 2019-07-12 | 2022-12-06 | 华为技术有限公司 | Data transmission method, network node and storage medium |
| CN111917622B (en) * | 2019-09-23 | 2021-08-03 | 华为技术有限公司 | Reverse Path Forwarding (RPF) checking method and device |
| CN113839870B (en) * | 2020-06-24 | 2023-01-13 | 华为技术有限公司 | Path creation method, device and system |
| CN114143142B (en) * | 2020-09-02 | 2023-06-20 | 华为技术有限公司 | Message transmission method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1716904A (en) * | 2004-06-30 | 2006-01-04 | 华为技术有限公司 | Group broadcast realizing method based on multiple service transmission platform |
| CN101207560A (en) * | 2006-12-18 | 2008-06-25 | 中兴通讯股份有限公司 | Method for establishing multicast tree in multi protocol label switching network |
-
2009
- 2009-06-16 CN CN200910086654XA patent/CN101588296B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1716904A (en) * | 2004-06-30 | 2006-01-04 | 华为技术有限公司 | Group broadcast realizing method based on multiple service transmission platform |
| CN101207560A (en) * | 2006-12-18 | 2008-06-25 | 中兴通讯股份有限公司 | Method for establishing multicast tree in multi protocol label switching network |
Non-Patent Citations (1)
| Title |
|---|
| JP特開2007-214899A 2007.08.23 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101588296A (en) | 2009-11-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101588296B (en) | Method, head node and tail node of forwarding multicasting message | |
| CN110061920B (en) | Method, equipment and storage medium for establishing bidirectional segment routing tunnel | |
| CN102316016B (en) | Method and device for forwarding multicasting flow | |
| EP3554021B1 (en) | Flow label negotiation method, related device, and system | |
| CN101047614B (en) | Flow transmission route set-up method and data transmission system in IPv6 network environment | |
| CN103748835A (en) | Dynamic updating of a label switched path | |
| CN104038417A (en) | Service Instance Applied To Mpls Networks | |
| CN101335695A (en) | Head node protection method, apparatus and device for point-to-multipoint label switching path | |
| CN101073226A (en) | Method and device for creating a tunnel in a label-switched telecommunication network | |
| EP2541847B1 (en) | Method and system for establishing an associated bidirectional label-switched path | |
| CN110224935A (en) | A kind of method and device handling multicast data message | |
| CN101552715A (en) | Method, node and system for establishing backup label switching path | |
| CN105791074A (en) | Method and device for establishing PW (Pseudo Wire) links | |
| CN101106515B (en) | Service quality guarantee method and system in multicast network | |
| CN101286863B (en) | Implementing system and method of multicast application service based on MPLS | |
| CN101163100A (en) | Tunnel mapping method | |
| 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 | |
| CN101304325B (en) | Multicast method and device | |
| CN101257455A (en) | Label pre-distributing mechanism based on T-MPLS grouping conveying network | |
| CN103685260A (en) | Overlaying multicast zone file transmitting method and system | |
| CN103999404A (en) | Internet group management protocol version three for quality of service support | |
| CN102904809B (en) | The bandwidth management methods, devices and systems of label forwarding path | |
| CN101150503B (en) | Upstream node label allocation method and system for point-to-point tunnel | |
| CN101483582B (en) | Method, system and router for implementing second and third layer multicast trace route | |
| CN101163099B (en) | Mapping method |
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 | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |
|
| CP03 | Change of name, title or address | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110907 Termination date: 20200616 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |