CN100349406C - A method for controlling establishment of label switch path (LSP) based on resource reservation protocol (RSVP) - Google Patents
A method for controlling establishment of label switch path (LSP) based on resource reservation protocol (RSVP) Download PDFInfo
- Publication number
- CN100349406C CN100349406C CNB031467385A CN03146738A CN100349406C CN 100349406 C CN100349406 C CN 100349406C CN B031467385 A CNB031467385 A CN B031467385A CN 03146738 A CN03146738 A CN 03146738A CN 100349406 C CN100349406 C CN 100349406C
- Authority
- CN
- China
- Prior art keywords
- retries
- path
- ingress node
- message
- node
- 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
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000012217 deletion Methods 0.000 claims description 14
- 230000037430 deletion Effects 0.000 claims description 14
- 239000002699 waste material Substances 0.000 abstract description 10
- 238000011144 upstream manufacturing Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 8
- 238000012423 maintenance Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000007257 malfunction Effects 0.000 description 3
- 239000000654 additive Substances 0.000 description 2
- 230000000996 additive effect Effects 0.000 description 2
- 230000006378 damage Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 230000002045 lasting effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention provides a method for controlling the establishment of a label switch path based on a resource reservation protocol, which is characterized in that predetermined time is set for an entry node which needs to establish the label switch path; if the entry node does not receive a reservation massage within the predetermined time, states related to the label switch path and corresponding the entry node are deleted via utilizing the resource reservation protocol; when a failure of a network occurs and the failure can not be recovered in time, artificial interference does not need via utilizing the present invention, and the states related to the label switch path can be automatically deleted by the resource reservation protocol according to the predetermined time; thereby, the network resource waste caused by that a network node continuously requests for establishing the label switch path because of the occurrence of the network failure can be avoided, and also, the temporary failure of the network can be greatly endured; consequently, the goal of saving network resources can be realized.
Description
Technical field
The present invention relates to the network communications technology field, be specifically related to a kind of method of setting up label switched path based on resources pre-reserving protocol control.
Background technology
RSVP (RSVP) initial design is the RSVP of the integrated service of support IP QoS (internet protocol service mass).RSVP can support MPLS (multiprotocol label switching) by expansion, and sets up LSP (label switched path) by protocol operation.
The basic functional principle of RSVP expansion is that transmit leg is that Ingress node is that Egress node sends PATH (PATH) to the recipient, comprise information such as resource request and label distribution request among the PATH, after Egress node receives PATH, upstream send RESV (reserving message), comprise the reservation of resource and the information such as distribution of label among the RESV.After RESV arrived Ingress node, then LSP set up successfully.
RSVP uses the method for soft-state refreshes to carry out the maintenance of PATH state, and the PATH state is kept among the PSB (path state block).RSVP each node between Ingress node and Egress node has been a PATH state-maintenance refresh timer and a removing timer.Because Ingress node can not receive the PATH refresh message, so RSVP only safeguards PATH state refresh timer at Ingress node, the removing timer is not set, can avoid causing the deletion of LSP like this because of the removing timer expiry.
The PATH state refresh timer expiry of Ingress node, send the PATH refresh message to next-hop node, after next-hop node receives the PATH refresh message, the PATH state that resets is removed timer and continue to carry out to downstream node the transmission of PATH refresh message when its PATH state refresh timer expiry, arrives Egress node until the PATH refresh message.
If when the PATH state of a certain hop node was removed timer expiry, this node did not receive the PATH refresh message yet, this node sends PATHTEAR (path tear down message) to its downstream node so, deletes all PSB of this node and downstream node thereof.But because Ingress node does not have the PATH state to remove timer, delete all PSBs relevant and the RSB (reservation state block) in its downstream so can not remove timer expiry with LSP because of the PATH state of Ingress node, again because PATHTEAR sends downstream, so Ingress node can't obtain PATHTEAR.The PATH state refresh timer of Ingress node exists all the time, the refresh timer of Ingress node sends the PATH refresh message all the time to downstream node, drive downstream node and set up LSP, when network disaster recovery, because the continuing to refresh still and can successfully set up described LSP of Ingress node; When network failure can't in time recover,, drive downstream node and set up LSP and cause waste of network resources because of Ingress node sends the PATH refresh message all the time to downstream node.At this moment need manually to intervene deletion Ingress node and all PSB relevant of downstream node thereof with LSP.
Be that example illustrates the process that above-mentioned PATH refresh message transmits with accompanying drawing 1 below.
R1 is an Ingress node, and RSVP is that R2, R3, R4 have safeguarded a PATH state refresh timer and a PATH state removing timer respectively until Egress node, has only safeguarded PATH state refresh timer at the R1 place, the PATH state is not set removes timer.Avoided like this removing the deletion that timer expiry causes LSP because of the PATH state of R1.
If network failure occurs between R3 and the R4, the PATH state of R4 is removed timer expiry, and R4 does not still receive the PATH refresh message that R3 sends, and R4 sends PATHTEAR to downstream node so, deletion R4 and all PSBs relevant with LSP of downstream node thereof.
R1 does not remove timer because of there being the PATH state, sends PATHTEAR so can not remove timer expiry because of the PATH state to R2.Again because PATHTEAR sends downstream, so the PATHTEAR that R4 sends can't arrive R1.The PATH state refresh timer of R1 exists all the time, during the PATH state refresh timer expiry of R1, send the PATH refresh message to R2, after R2 receives the PATH refresh message, reset its PATH state is removed timer, make the PATH state of R2 remove timer not can because of overtime to
R3 sends PATHTEAR.The PATH state refresh timer expiry of R2 sends the PATH refresh message to R3, and the PATH state refresh timer expiry of R3 sends the PATH refresh message to R4.
When the network failure between R3 and the R4 in time recovered, owing to R1, R2, R3 have kept PSB, the PATH state refresh timer among R1, R2, the R3 can continue to refresh requirement and set up the successful foundation of LSP until LSP.
When the network failure between R3 and the R4 can't recover, because R1, R2, R3 have kept PSB, the PATH state refresh timer among R1, R2, the R3 can continue to refresh and causes waste of network resources.Need manually intervene all PSBs relevant among deletion R1, R2, the R3 with LSP.
RSVP uses the method for soft-state refreshes to carry out the maintenance of RESV state for setting up successful LSP, and the RESV state is kept among the RSB.RSVP each node between Ingress node and Egress node has been a RESV state-maintenance refresh timer and a removing timer.
Send the RESV refresh message to its previous dive node during the RESV state refresh timer expiry of Egress node, the RESV state that the previous dive node receives this node that resets behind the RESV refresh message is removed timer and at the RESV of this node state refresh timer expiry, continuation is carried out the transmission of RESV refresh message to its upstream node, arrives Ingress node until the RESV refresh message.
If a certain hop node does not still receive the RESV refresh message when the RESV of a certain hop node state is removed timer expiry, this node sends RESVTEAR (reservation tear down message) to its upstream node so, deletes all RSBs relevant with LSP of this node and upstream thereof.
If the network between Egress node and the Ingress node breaks down, because the downstream node of fault remains with RSB, the node of the RSB that withed a hook at the end can continue to refresh, and LSP is set up in the upstream of driving malfunction.Because the upstream node of fault and fault has kept PSB, and the node of the PSB that withed a hook at the end also can continue to carry out refreshing of PATH message, the downstream node of driving malfunction is set up LSP simultaneously.
When fault is in time recovered, the PATH state refresh timer expiry that the upstream node of fault keeps, the upstream node of fault sends the PATH refresh message to its downstream node, and the downstream node that drives it is set up LSP until successfully setting up LSP.The RESV state refresh timer expiry that the downstream node of fault keeps, the downstream node of fault sends the RESV refresh message to its upstream node, drives its upstream node and sets up LSP until RESV refresh message arrival Ingress node.
When fault can not in time be recovered, the PATH state refresh timer expiry that the upstream node of fault keeps, the upstream node of fault sends the PATH refresh message to its downstream node, and the downstream node that drives it is set up LSP.The RESV state refresh timer expiry that the downstream node of fault keeps, the downstream node of fault sends the RESV refresh message to its upstream node, and the upstream node of driving malfunction is set up LSP.Thereby cause waste of network resources.
Said method can be avoided the network failure that can in time recover between Ingress node and the Egress node, but when this network failure can't in time recover, can be because have withed a hook at the end in the fault upstream withed a hook at the end the continuing to refresh and cause waste of network resources of node of RSB of the downstream of the node of PSB and fault.Need manually intervene deletion Ingress node and downstream all PSB relevant and RSB with LSP.
Be that example illustrates the process that above-mentioned RESV refresh message transmits with accompanying drawing 2 below.
In Fig. 2, R1 is an Ingress node.RSVP is that the RESV state of R1, R2, R3, R4 each node between Egress node is provided with a refresh timer and a removing timer.
The RESV state refresh timer expiry of R4, send RESV state refresh message to R3, after R3 received the RESV refresh message, the RESV state of the R3 that resets was removed timer, the RESV state refresh timer expiry of R3 continues to carry out the transmission of RESV refresh message to R2.RESV refresh message Using such method is sent to R1 by Egress node, and then LSP successfully sets up.
If network failure occurs between R3 and the R4, the RESV state of R3 is removed timer expiry, and R3 does not still receive the RESV refresh message, and R3 sends RESVTEAR to R2 so, the RSB of deletion R3 and R2, R1.The PATH state of R4 is removed timer expiry, and R4 does not still receive the PATH refreshing information, and R4 sends PATHTEAR downstream so, the PSB of deletion R4 and all downstream nodes thereof.Because R4 remains with RSB until Egress node, the node of the RSB that withed a hook at the end can continue to carry out refreshing of RESV message, and LSP is set up in the upstream that drives R4.Owing to R3, R2, R1 have kept PSB, the node of the PSB that withed a hook at the end also can continue to carry out refreshing of PATH message simultaneously, and the downstream node of drive node R3 is set up LSP.
When fault was in time recovered, R3, R2, R1 had kept PSB, continued to send to downstream node the PATH refresh message, and the downstream node that drives R3 is set up LSP until successfully setting up LSP.R4 has kept RSB until Egress node, continues upstream nodes and sends the RESV refresh message, and the upstream node of driving R4 is set up LSP and received RESV until Ingress node.
Said method can be avoided the network failure that can in time recover between Ingress node and the Egress node, but when this network failure can't in time recover, can be because have kept PSB among R3, R2, the R1 and R4 has kept RSB and caused waste of network resources until Egress node.Need manually intervene deletion R1 and downstream node all PSB relevant and RSB with LSP.
Summary of the invention
The objective of the invention is to, provide a kind of and set up the method for label switched path, when network breaks down, delete all states relevant automatically, to realize the purpose of conserve network resources with label switched path based on resources pre-reserving protocol control.
For achieving the above object, the method for setting up label switched path based on resources pre-reserving protocol control provided by the invention comprises:
A, be set for the Ingress node that need set up label switched path the scheduled time;
B, in the described scheduled time, do not receive and the Ingress node of reserving message utilize RSVP to delete all states relevant in this Ingress node and the downstream with label switched path.
Described step a comprises:
When RSVP is that Ingress node is that the path state block of Ingress node is set the scheduled time when path state block is set; Or
The path state block that is Ingress node when Ingress node is received reservation tear down message is set the scheduled time.
When the described scheduled time realized by timer, described step b comprised:
Judgement is in the timer time scope, and whether described Ingress node receives reserving message;
If described Ingress node is received reserving message, the timeing closing device;
If described Ingress node is not received reserving message, utilize RSVP to delete the path state block of described Ingress node, and, delete all path state block relevant and reservation state blocks with label switched path to the downstream of described Ingress node transmit path tear down message.
The described scheduled time can realize by retry interval and number of retries equally;
The product of described retry interval and number of retries is the described scheduled time.
When the described scheduled time was realized by retry interval and number of retries, described step a comprised:
A1, the traversal timer is set;
A2, regularly travel through all and need set up the forwarding equivalence class of label switched path and be respectively it retry interval and number of retries are set.
When described step a comprised a1 and a2, described step b comprised:
Whether the metering value of judging number of retries reaches described number of retries;
If do not reach described number of retries, begin timing to described retry interval;
Whether the clocking value of judging described retry interval reaches described retry interval;
If do not reach described retry interval, judge whether described Ingress node receives reserving message;
If receive reserving message, stop to the timing of described retry interval with to the metering of described number of retries; Otherwise continue timing to described retry interval;
If reach described retry interval, the metering value of described number of retries increases progressively, and returns describedly to judge whether the metering value of described number of retries reaches the step of described number of retries;
If reach described number of retries, described Ingress node is not also received reserving message, delete the forwarding equivalence class of this Ingress node correspondence, utilize RSVP to delete the path state block of this Ingress node, and, delete all path state block relevant and reservation state blocks with label switched path to the downstream of described Ingress node transmit path tear down message.
When described step a comprised a1 and a2, described step b can comprise equally:
Whether the metering value of judging number of retries reaches described number of retries;
If do not reach described number of retries, begin timing to described retry interval;
Whether the clocking value of judging described retry interval reaches described retry interval;
If do not reach described retry interval, judge whether described Ingress node receives reserving message;
If receive reserving message, stop to the timing of described retry interval with to the metering of described number of retries; Otherwise continue timing to described retry interval;
If reach described retry interval, the metering value of described number of retries increases progressively, and returns describedly to judge whether the metering value of described number of retries reaches the step of described number of retries;
If reach described number of retries, described Ingress node is not also received reserving message, this forwarding equivalence class is changed to disarmed state also is its dozen timestamp, utilize RSVP to delete the path state block of the Ingress node of this forwarding equivalence class correspondence, and, delete all path state block relevant and reservation state blocks with label switched path to the downstream of described Ingress node transmit path tear down message.
In the said method, described step a2 can also comprise:
When traversing the forwarding equivalence class of described useless state,, retry interval and number of retries are set for the current time deducts the forwarding equivalence class that described timestamp is not less than the scheduled update time.
The scheduled time of the present invention is not less than the Loop Round Trip Time of message;
The Loop Round Trip Time of described message is message returns described Ingress node from described Egress node from described Ingress node arrival Egress node and message a time sum.
RSVP of the present invention comprises RSVP and resource reservation Extended Protocol.
Utilize the present invention, by the scheduled time is set, when fault that can't in time recover appears in network, do not need manually to intervene, can delete all states relevant by RSVP automatically according to the scheduled time with label switched path, avoided making network node continue to require to set up the waste of network resources that label switched path causes, can bear the temporary fault that network occurs by range content at the fixed time again because of network failure occurring; Setting after the update time and can when avoiding the lasting network resources waste that requires to set up label switched path and cause of node, set up label switched path by the unlimited retry of assurance, tolerate the fault that network occurs to the full extent, thereby realized the purpose of conserve network resources.
Description of drawings
Fig. 1 is that the PATH refresh message flows to schematic diagram;
Fig. 2 is that the RESV refresh message flows to schematic diagram;
Fig. 3 is that the flow chart that timer realizes setting up based on resources pre-reserving protocol control the tag changeable path routing method is created in use of the present invention;
Fig. 4 use retry interval of the present invention, number of retries, traversal timer realize setting up based on resources pre-reserving protocol control the flow chart of tag changeable path routing method;
Fig. 5 is the flow chart that use retry interval of the present invention, number of retries, traversal timer, update time realize setting up based on resources pre-reserving protocol control the tag changeable path routing method;
(a) sets up label switched path based on RSVP in the prior art among Fig. 6, takies the schematic diagram of Internet resources when network breaks down; (b) be that the present invention uses the establishment timer to realize setting up label switched path based on resources pre-reserving protocol control, take the schematic diagram of Internet resources when network breaks down; (c) be that the present invention uses retry interval, number of retries, traversal timer, update time to realize setting up label switched path based on resources pre-reserving protocol control, take the schematic diagram of Internet resources when network breaks down.
Embodiment
For the clearer understanding the present invention of the technical staff who makes the technical field of the invention, now be described with reference to the accompanying drawings.
Use and create the timer realization flow chart that the LSP method is set up in control based on RSVP, this flow process is described in detail below in conjunction with accompanying drawing 1, Fig. 2 with reference to shown in the accompanying drawing 3.
The timing of creating timer is the scheduled time.
Set between Ingress node R1 and the Egress node and need to set up LSP.
In step 300, RSVP is R1 when PSB is set, and creates timer or is that the PSB of R1 is provided with the establishment timer when R1 receives RESVTEAR for this PSB is provided with.The timing of creating timer is the scheduled time.The establishment timer picks up counting.
In step 310, judge whether the establishment timer is overtime, if it is not overtime to create timer,, judge whether RESV reaches Ingress node R1 to step 320, if RESV reaches Ingress node R1, to step 330, RSVP successfully sets up LSP, closes the establishment timer, to step 340, the process of setting up LSP finishes.
In step 310, if establishment timer expiry, because the fault between R3 and the R4, RESV no show Ingress node R1, to step 311, RESV deletes the PSB of Ingress node R1, and sends PATHTEAR to the downstream node of R1, PSB and the RSB relevant with LSP among deletion R2, the R3 close the establishment timer.To step 340, method finishes.Thereby the state that the upstream node of the fault that is through with continues to refresh has been saved Internet resources.
Use the establishment timer to realize breaking down when LSP is set up in control based on RSVP, the situation that takies of Internet resources is shown in (b) among Fig. 6.(a) among Fig. 6 is that network breaks down when setting up LSP based on RSVP in the prior art, Internet resources take schematic diagram; (a) of comparison diagram 6 and (b), can obviously know, the present invention program is owing to set the establishment timer, when fault that can't in time recover appears in network, do not need manually to intervene, RSVP can delete entry node R1 and downstream node all PSB and RSBs relevant with LSP thereof automatically, can not cause network resources waste because node has kept PSB and RSB, can bear the temporary fault that network occurs at the timing range content of creating timer again.
Create the timing of timer and answer choose reasonable, the foundation of the destruction LSP that the too small meeting that the timing of establishment timer is provided with is artificial; It is excessive that the timing of establishment timer is provided with, and Ingress node can continue the path and refresh, and can not reach the purpose of real conserve network resources.Timing should be not less than returning the time of message.In practical operation, the timing of creating timer should dispose, and can select suitable timing according to practical experience.
The establishment timer is set utilizes RSVP to be provided with, also can utilize additive method such as software, be provided with.
Use retry limit and the traversal timer realization flow chart that the LSP method is set up in control based on RSVP with reference to shown in the accompanying drawing 4, this flow process is described in detail below in conjunction with accompanying drawing 1, Fig. 2.
Retry limit comprises retry interval and number of retries.
The product of retry interval and number of retries is the scheduled time.
In step 400, the traversal timer is set, according to the traversal timer, regularly traversal need be set up the FEC of LSP and for it retry interval and number of retries is set respectively.The product of retry interval and number of retries is the scheduled time.Begin to be the number of retries metering.
In step 410, judge whether the metering value reaches number of retries, if the metering value does not reach number of retries,, begin to be the retry interval timing to step 420; To step 430, judge whether clocking value reaches retry interval, if do not reach retry interval, to step 440, judge whether RESV reaches Ingress node R1, if RESV reaches Ingress node R1, to step 450, RSVP successfully sets up LSP, ends up being the retry interval timing, ends up being the number of retries metering.To step 460, the process of setting up LSP for FEC finishes.
In step 430, if clocking value reaches retry interval, because network failure appears between R3 and the R4, and RESV no show Ingress node R1, to step 431, the metering value adds 1, to step 410, judges whether the metering value reaches number of retries; If reach number of retries, to step 411, delete the FEC corresponding with this LSP, RESV deletes the PSB of the Ingress node R1 of this FEC correspondence, and sending PATHTEAR to the downstream node of R1, PSB and the RSB relevant with this LSP among deletion R2, the R3 end up being the retry interval timing, end up being the number of retries metering, to step 460, the process of setting up LSP for FEC finishes.Thereby the state that the upstream node path of the fault that is through with continues to refresh has been saved Internet resources.
Use the flow chart of retry limit, traversal timer and update time realizing that the LSP method is set up in control based on RSVP with reference to shown in the accompanying drawing 5, this flow process is described in detail below in conjunction with accompanying drawing 1, Fig. 2.
The state of FEC has two kinds in this embodiment, and a kind of is useless state, and another kind is non-useless state.We successfully do not set up LSP with retry limit in the time FEC is changed to useless state, and other FEC are non-useless state.
In step 500, the traversal timer is set, according to the traversal timer, regularly traversal need be set up the FEC of LSP.To step 510, judge respectively whether the FEC that need set up LSP is useless state, if FEC is not useless state, to step 530; If FEC is useless state, to step 520, whether the difference of timestamp of FEC of judging current time and this useless state is less than the scheduled update time, if less than the scheduled update time, to step 521, according to traversal timer wait traversal next time, to step 590, the process of setting up LSP for this FEC finishes.In step 520, if the difference of the timestamp of the FEC of current time and this useless state is not less than the scheduled update time, to step 530.
In step 530,, begin to be the number of retries metering for not being the FEC of useless state and being that the difference of useless state and current time and timestamp is not less than the FEC of scheduled update time and sets up retry interval and number of retries respectively.The product of retry interval and number of retries is the scheduled time.To step 540, judge whether the metering value reaches number of retries, if the metering value does not reach number of retries,, begin to be the retry interval timing to step 550.To step 560, judge whether clocking value reaches retry interval, if do not reach retry interval, to step 570, judge whether RESV reaches Ingress node R1, if RESV reaches Ingress node R1, to step 580, RSVP successfully sets up LSP, ends up being the retry interval timing, ends up being the number of retries metering.To step 590, the process of setting up LSP for this FEC finishes.
In step 560, if clocking value reaches retry interval, because network failure appears between R3 and the R4, and in step 570, RESV no show Ingress node R1, to step 561, the metering value adds 1, to step 540, judges whether the metering value reaches number of retries.
In step 540, if the metering value reaches number of retries, to step 541, the PSB of RESV deletion Ingress node R1, and send PATHTEAR to the downstream node of R1, LSP relevant PSB, the RSB corresponding among deletion R2, the R3 with this FEC, but do not delete this FEC, this FEC is set to disarmed state, and beat timestamp for FEC, end up being the retry interval timing, end up being the number of retries metering, to step 590, this finishes for the process that this FEC sets up LSP.Thereby the state that the upstream node of the fault that is through with continues to refresh has been saved Internet resources.
Retry interval and number of retries are answered choose reasonable, the foundation of the destruction label switched path that the too small meeting that retry interval and number of retries are provided with is artificial; It is excessive that retry interval and number of retries are provided with, and Ingress node can continue the path and refresh, and can not reach the purpose of real conserve network resources.The time product value of retry interval and number of retries should be not less than returning the time of message.In practical operation, retry interval and number of retries should dispose, and can select suitable numerical value according to practical experience.It is bigger that the setting of update time should be chosen as far as possible, can really play the purpose of conserve network resources like this.
Use and realize retry interval, number of retries, traversal timer and update time that LSP is set up in control based on RSVP, network breaks down, and the situation that takies of Internet resources is shown in (c) among Fig. 6.(a) of comparison diagram 6 and (c), can obviously learn, in the present embodiment, owing to set retry interval, number of retries, traversal timer, when fault that can't in time recover appears in network, do not need manually to intervene, RSVP can delete entry node R1 and all PSB and the RSB of downstream node thereof automatically, can not keep PSB and RSB and caused network resources waste because of node, can guarantee update time under the situation of abundant conserve network resources owing to set, unlimited retry is set up LSP, has tolerated the fault that occurs in the network to the full extent.
The present invention can utilize RSVP that methods such as creating timer, number of retries, retry interval, update time is set respectively, when in setting up the process of LSP, breaking down, delete all states relevant with LSP, also can be provided with and create timer, number of retries, retry interval, update time when in setting up the process of LSP, breaking down, delete all states relevant with LSP by methods such as additive method such as softwares.Need set up the FEC of LSP for all, more suitable with software administration.
In actual applications also can more effective conserve network resources with being provided with that the method for creating timer and retry limit, update time being set is used in combination.
RSVP described in the said method comprises the Extended Protocol of described RSVP and described RSVP.
Though described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, wish that appended claim comprises these distortion and variation and do not break away from spirit of the present invention.
Claims (10)
1. set up the method for label switched path based on resources pre-reserving protocol control for one kind, it is characterized in that comprising:
A, be set for the Ingress node that need set up label switched path the scheduled time;
B, in the described scheduled time, do not receive the Ingress node of reserving message, utilize RSVP to delete the path state block of this Ingress node, and transmit path tear down message downstream, all path state block relevant and reservation state blocks in the deletion downstream with label switched path.
2. as claimed in claim 1ly a kind ofly set up the method for label switched path, it is characterized in that described step a comprises based on resources pre-reserving protocol control:
When RSVP is that Ingress node is that the path state block of Ingress node is set the scheduled time when path state block is set; Or
The path state block that is Ingress node when Ingress node is received reservation tear down message is set the scheduled time.
3. as claimed in claim 1 or 2ly a kind ofly set up the method for label switched path, it is characterized in that based on resources pre-reserving protocol control:
When the described scheduled time realized by timer, described step b comprised:
Judgement is in the timer time scope, and whether described Ingress node receives reserving message;
If described Ingress node is received reserving message, the timeing closing device;
If described Ingress node is not received reserving message, utilize RSVP to delete the path state block of described Ingress node, and, delete all path state block relevant and reservation state blocks with label switched path to the downstream of described Ingress node transmit path tear down message.
4. as claimed in claim 1 or 2ly a kind ofly set up the method for label switched path, it is characterized in that the described scheduled time realizes by retry interval and number of retries based on resources pre-reserving protocol control;
The product of described retry interval and number of retries is the described scheduled time.
5. as claimed in claim 4ly a kind ofly set up the method for label switched path, it is characterized in that described step a comprises based on resources pre-reserving protocol control:
A1, the traversal timer is set;
A2, regularly travel through all and need set up the forwarding equivalence class of label switched path and be respectively it retry interval and number of retries are set.
6. as claimed in claim 5ly a kind ofly set up the method for label switched path, it is characterized in that described step b comprises based on resources pre-reserving protocol control:
Whether the metering value of judging number of retries reaches described number of retries;
If do not reach described number of retries, begin timing to described retry interval;
Whether the clocking value of judging described retry interval reaches described retry interval;
If do not reach described retry interval, judge whether described Ingress node receives reserving message;
If receive reserving message, stop to the timing of described retry interval with to the metering of described number of retries;
Otherwise continue described retry interval timing;
If reach described retry interval, the metering value of described number of retries increases progressively, and returns describedly to judge whether the metering value of described number of retries reaches the step of described number of retries;
If reach described number of retries, described Ingress node is not also received reserving message, delete the forwarding equivalence class of this Ingress node correspondence, utilize RSVP to delete the path state block of this Ingress node, and, delete all path state block relevant and reservation state blocks with label switched path to the downstream of described Ingress node transmit path tear down message.
7. as claimed in claim 5ly a kind ofly set up the method for label switched path, it is characterized in that described step b comprises based on resources pre-reserving protocol control:
Whether the metering value of judging number of retries reaches described number of retries;
If do not reach described number of retries, begin timing to described retry interval;
Whether the clocking value of judging described retry interval reaches described retry interval;
If do not reach described retry interval, judge whether described Ingress node receives reserving message;
If receive reserving message, stop to the timing of described retry interval with to the metering of described number of retries;
Otherwise continue timing to described retry interval;
If reach described retry interval, the metering value of described number of retries increases progressively, and returns describedly to judge whether the metering value of described number of retries reaches the step of described number of retries;
If reach described number of retries, described Ingress node is not also received reserving message, this forwarding equivalence class is changed to disarmed state also is its dozen timestamp, utilize RSVP to delete the path state block of the Ingress node of this forwarding equivalence class correspondence, and, delete all path state block relevant and reservation state blocks with label switched path to the downstream of described Ingress node transmit path tear down message.
8. as claimed in claim 7ly a kind ofly set up the method for label switched path, it is characterized in that described step a2 also comprises based on resources pre-reserving protocol control:
When traversing the forwarding equivalence class of described useless state, for the current time deducts the forwarding equivalence class that described timestamp is not less than the scheduled update time retry interval and number of retries are set.
9. as claimed in claim 1ly a kind ofly set up the method for label switched path, it is characterized in that the described scheduled time is not less than the Loop Round Trip Time of message based on resources pre-reserving protocol control;
The Loop Round Trip Time of described message is message returns described Ingress node from described Egress node from described Ingress node arrival Egress node and message a time sum.
10. as claimed in claim 1ly a kind ofly set up the method for label switched path, it is characterized in that described RSVP comprises RSVP and resource reservation Extended Protocol based on resources pre-reserving protocol control.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031467385A CN100349406C (en) | 2003-06-22 | 2003-06-22 | A method for controlling establishment of label switch path (LSP) based on resource reservation protocol (RSVP) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031467385A CN100349406C (en) | 2003-06-22 | 2003-06-22 | A method for controlling establishment of label switch path (LSP) based on resource reservation protocol (RSVP) |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1567844A CN1567844A (en) | 2005-01-19 |
| CN100349406C true CN100349406C (en) | 2007-11-14 |
Family
ID=34471843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB031467385A Expired - Fee Related CN100349406C (en) | 2003-06-22 | 2003-06-22 | A method for controlling establishment of label switch path (LSP) based on resource reservation protocol (RSVP) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100349406C (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7843845B2 (en) * | 2005-11-28 | 2010-11-30 | Alcatel Lucent | Diagnostic tool and method for troubleshooting multicast connectivity flow problem(s) in a layer 2 aggregation network |
| CN101079729B (en) * | 2006-05-23 | 2011-04-20 | 华为技术有限公司 | Method for reserving network resource |
| CN101087207B (en) | 2006-06-09 | 2010-05-12 | 华为技术有限公司 | A processing method for multi-node communication failure |
| CN101136788A (en) * | 2006-08-30 | 2008-03-05 | 华为技术有限公司 | Fault location method and system for MPLS multicast |
| EP1983701B1 (en) * | 2007-04-17 | 2010-08-25 | Alcatel Lucent | Method and apparatus for reserving network resources for pseudo point-to-point connection |
| US9001672B2 (en) * | 2012-07-27 | 2015-04-07 | Alcatel Lucent | System, method and apparatus conforming path cost criteria across multiple ABRs |
| CN106470159B (en) * | 2015-08-18 | 2020-09-15 | 中兴通讯股份有限公司 | Tunnel convergence method and device |
| CN112154628B (en) * | 2018-05-17 | 2022-10-14 | 瑞典爱立信有限公司 | Tearing down label switched paths through a communication network |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002057702A (en) * | 2000-08-08 | 2002-02-22 | Mitsubishi Electric Corp | Priority control method for label switching path and communication system using the same |
| CN1360806A (en) * | 1999-05-10 | 2002-07-24 | 艾利森电话股份有限公司 | Methods and systems for error handling in radio communication systems employing pre-paging |
| CN1412989A (en) * | 2002-10-15 | 2003-04-23 | 华为技术有限公司 | Method for controlling tag retransmission path establishment and deletion |
| US20030099194A1 (en) * | 2001-11-28 | 2003-05-29 | Youngseok Lee | Constrained multipath routing method |
| US20030112749A1 (en) * | 2001-12-18 | 2003-06-19 | Brian Hassink | Methods, systems, and computer program products for detecting and/or correcting faults in a multiprotocol label switching network by using redundant paths between nodes |
-
2003
- 2003-06-22 CN CNB031467385A patent/CN100349406C/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1360806A (en) * | 1999-05-10 | 2002-07-24 | 艾利森电话股份有限公司 | Methods and systems for error handling in radio communication systems employing pre-paging |
| JP2002057702A (en) * | 2000-08-08 | 2002-02-22 | Mitsubishi Electric Corp | Priority control method for label switching path and communication system using the same |
| US20030099194A1 (en) * | 2001-11-28 | 2003-05-29 | Youngseok Lee | Constrained multipath routing method |
| US20030112749A1 (en) * | 2001-12-18 | 2003-06-19 | Brian Hassink | Methods, systems, and computer program products for detecting and/or correcting faults in a multiprotocol label switching network by using redundant paths between nodes |
| CN1412989A (en) * | 2002-10-15 | 2003-04-23 | 华为技术有限公司 | Method for controlling tag retransmission path establishment and deletion |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1567844A (en) | 2005-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101682518B (en) | Distributed connection establishment and restoration | |
| CN100558055C (en) | Reduce the method and the router of continuous duration of error smoothness rebooting status | |
| CN100583827C (en) | Method and equipment for multiple protocol label switching network flow switchover | |
| WO2007140689A1 (en) | A failure processing method and a system and a device thereof | |
| CN101640637B (en) | Resource reservation protocol tunnel management method based on flow rate engineering and system thereof | |
| CN100349406C (en) | A method for controlling establishment of label switch path (LSP) based on resource reservation protocol (RSVP) | |
| CN102165740A (en) | Congestion control method and devices | |
| CN101984600B (en) | Graceful restart method, equipment and system of routing protocol | |
| CN101296239B (en) | Method for refreshing label exchange route and label exchange router | |
| CN1801802B (en) | Node restarting method on universal multi protocol label exchange path | |
| EP1921797A1 (en) | Recovery method and apparatus for optical network lsp occuring abnormal delete | |
| CN100591051C (en) | Multi-link failure processing method and label switching router | |
| CN103368861A (en) | System and method for processing network congestion | |
| CN101420378B (en) | Optimum restart implementing apparatus and method under resource reservation protocol flow engineering | |
| US7499436B2 (en) | Mobile communication system using resource reservation protocol | |
| CN101123473B (en) | Recovery method for control plane after node restart in automatic switching optical network | |
| US7542413B1 (en) | Method and apparatus for delaying start of restoration of low priority services | |
| CN100370748C (en) | Method of implementing synchronization of topology resource information between bearer networks | |
| CN102136936A (en) | Method, node and system for preventing control plane faults from influencing operation of forward data plane | |
| CN1553663B (en) | Method for resource reservation protocol to reduce soft status update | |
| CN106161243A (en) | A kind of state reporting control method and device | |
| JP4099772B2 (en) | IP multicast switching control system, IP multicast switching control method, program for the same, and recording medium recording the program | |
| CN100352215C (en) | Automatic detecting and processing method of label exchange path condition | |
| CN101594288B (en) | Query facility selecting method, router and network system | |
| JP2005236701A (en) | Ip multicast distribution source switching control system, method thereof, switching control server, switching control program and recording medium recording this program |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170922 Address after: 075000 No. 2, building 2, building 1, building 202, Qiaodong District, Qiaodong District, Hebei, Zhangjiakou Patentee after: Liu Xinwei Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20071114 Termination date: 20180622 |