US2011026398A1PendingUtilityA1

Dynamic Traffic Rearrangement to Enforce Policy Change in MPLS Networks

Assignee: TELCORDIA TECH INCPriority: Mar 30, 2006Filed: Oct 12, 2010Published: Feb 3, 2011
Est. expiryMar 30, 2026(expired)· nominal 20-yr term from priority
H04L 45/02H04L 45/22H04L 45/247H04L 47/29H04L 43/16H04L 45/302H04L 47/20H04L 45/50H04L 45/125H04L 45/04H04L 43/0894H04L 47/2408
43
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system and method of rearranging Label Switched Paths (LSPs) and rerouting traffic in a DiffServ-enabled Multi-Protocol Label Switched (MPLS) network is disclosed. The system periodically monitors network performance, and rearranges LSPs and reroutes traffic through existing or new Label Switched Paths (LSPs) based on network performance and network bandwidth utilized by various DiffServ classes.

Claims

exact text as granted — not AI-modified
1 . A method of controlling traffic of data through a network, the network having a plurality of Label Switched Paths (LSPs) created with Multi-Protocol Label Switching (MPLS), the method comprising:
 (a) monitoring network traffic through the plurality of LSPs and determining utilization of LSPs on a DiffServ class basis;   (b) if LSP utilization for one or more classes exceeds a predetermined threshold, issuing a rearrange request comprising:
 (i) a new policy on fraction of network bandwidth to be allocated for each DiffServ class. 
   
     
     
         2 . The method of  claim 1  wherein the step of monitoring LSP utilization includes calculating the bandwidth used on each of the plurality of LSPs by each of a plurality of differentiated services classes. 
     
     
         3 . The method of  claim 2  wherein the bandwidth used by each of a plurality of differentiated services classes is compared to a predetermined threshold for each particular class. 
     
     
         4 . The method of  claim 1  further comprising:
 (c) if LSP utilization for one or more DiffServ classes falls below a predetermined threshold, issuing a rearrange request comprising: 
 (i) a new policy on fraction of network bandwidth to be allocated for each DiffServ class. 
 
     
     
         5 . (canceled) 
     
     
         6 . (canceled) 
     
     
         7 . (canceled) 
     
     
         8 . (canceled) 
     
     
         9 . (canceled) 
     
     
         10 . (canceled) 
     
     
         11 . (canceled) 
     
     
         12 . (canceled) 
     
     
         13 . (canceled) 
     
     
         14 . (canceled) 
     
     
         15 . (canceled) 
     
     
         16 . (canceled) 
     
     
         17 . A system used for traffic engineering in a network, the network having a plurality of Label Switched Paths (LSPs) the system comprising:
 (a) means for monitoring network performance data and sending a rearrange order if LSP utilization on a DiffServ class basis exceeds a predetermined level;   (b) means for responding to the rearrange order by evaluating which of a plurality of paths should be provisioned a different amount of bandwidth according to traffic currently flowing through the plurality of paths;   (c) means for determining whether new paths should be created to accommodate the rearrange order and creating those new paths,   (d) means for reallocating traffic between the plurality of paths and any new paths that have been created.   
     
     
         18 . The system of  claim 17  wherein the means for monitoring sends a rearrange order if LSP utilization falls below a predetermined level. 
     
     
         19 . The system of  claim 18  further comprising means for deleting one or more paths when LSP utilization falls below a predetermined level. 
     
     
         20 . (canceled) 
     
     
         21 . (canceled) 
     
     
         22 . (canceled) 
     
     
         23 . (canceled) 
     
     
         24 . (canceled)

Join the waitlist — get patent alerts

Track US2011026398A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.