Methods and systems for providing quality of service in packet-based core transport networks

• US 7,599,290 B2
• Filed: 08/11/2006
• Issued: 10/06/2009
• Est. Priority Date: 08/11/2006
• Status: Expired due to Fees

• Current Assignee: Latitude Broadband Incorporated
• Original Assignee: Latitude Broadband Incorporated
• Inventors: Dos Remedios, Rene Maria Buniel, Delos Angeles, Joel Cruz, Eliseeff, Ma Josefa Betia
• Primary Examiner(s): Patel; Jayanti K
• Assistant Examiner(s): SOL, ANTHONY M
• Application Number:
  US11/463,908
• Publication Number:
  US 20080037552A1
• Time in Patent Office: 1,152 Days
• Field of Search: 370/395.21, 370/395.2, 370230-234
• US Class Current: 370/230.1
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/115 using a dedicated packet
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/22 Traffic shaping
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 47/29 using a combination of thresholds
• CPC Class Codes: H04L 47/41 by acting on aggregated flows or links
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

Methods and systems for providing necessary and sufficient quality-of-service (QoS), in a packet-based core transport network that utilizes dynamic setting of bandwidth management pipes or thresholds to obviate link congestion are disclosed. Congestion avoidance is a necessary and sufficient requirement in order to guarantee Quality of Service (QoS) in packet-based core networks.

A typical network is composed of a plurality of backbone links connecting edge nodes where backhaul links are aggregated. The backhaul links connect the backbone links to the remote sites serving the subscribers. In order to enforce bandwidth management policies, Access Controllers, which perform traffic shaping, are situated on each remote site.

In the event of a violation of certain link threshold settings, dynamic adjustment of the bandwidth management policies on affected Access Controllers is enforced. Various algorithms in determining the correlation between the link nearing congestion and the source or destination of traffic streams are also discussed. This invention implements a feedback control loop wherein probes at various points in the network checks for congestion states to guide bandwidth management threshold decisions in order to maintain the condition of non-congestion throughout the network. Capacity planning and congestion avoidance mechanisms work hand-in-hand to fulfill Service Level Agreements (SLA).

Claims

1. A method for avoiding congestion in a core transport network of a packet-based network, said packet-based network comprising:

said core transport network comprising a plurality of backbone links connected to a plurality of backhaul links through a plurality of edge nodes,

an access network comprising a plurality of subscriber terminals connected to said core transport network through a plurality of access controllers, wherein

said access controllers perform resource and admission control functions, said method comprising;

a. identifying access controllers that are a source or destination of packets traversing each said backbone and backhaul links,

b. utilizing a plurality of monitoring probes in said core transport network to identify at least one of said backbone or backhaul links that is nearing congestion and to trigger a dynamic bandwidth adjustment,

c. determining bandwidth settings for affected access controllers that are the source or destination of packets traversing each of the backbone or backhaul links nearing congestion,

d. checking if subscribers'"'"' service level agreements in the backbone or backhaul links nearing congestion are violated,

e. enforcing said bandwidth settings to said affected access controllers if said subscribers'"'"' service level agreements in the backbone or backhaul links nearing congestion are not violated,

f. notifying a network operator to implement a capacity upgrade if said subscribers'"'"' service level agreements in the backbone or backhaul links nearing congestion are violated,

whereby said avoiding congestion in said core transport network will provide necessary and sufficient quality-of-service in said core transport network of said packet-based network.

2. The method of claim 1, wherein said identifying said access controllers that are the source or destination of packets traversing each said backbone and backhaul links is done by correlating a list of identifiers contained in packet headers captured by the monitoring probes in said backbone and backhaul links and a network topology database from a network management system.

3. The method of claim 1, further including identifying said access controllers that are the source or destination of packets traversing each said backbone and backhaul links from a list of backhaul links which is generated through path traversal.

4. The method of claim 1, wherein said utilizing said plurality of monitoring probes in said core transport network to identify at least one of said backbone or backhaul links that is nearing congestion and to trigger said dynamic bandwidth adjustment is performed by configuring said monitoring probes to observe a plurality of connectivity performance metrics in each said backbone and backhaul links and to check if at least one of said connectivity performance metrics has reached corresponding predetermined connectivity threshold settings.

5. The method of claim 4, wherein said dynamic bandwidth adjustment is implemented using a proportional integral derivative control mechanism.

6. The method of claim 4, wherein said monitoring probes are configured to observe said connectivity performance metrics in each said backbone and backhaul links with response times quicker than time constants of network traffic load profiles of each said backbone and backhaul links.

7. The method of claim 1, wherein said determining said bandwidth settings for said affected access controllers that are the source or destination of packets traversing each of the backbone or backhaul links nearing congestion is performed by utilizing a plurality of algorithms comprising:

a. distributing an allocated backbone or backhaul capacity equally or weighted among said affected access controllers;

b. distributing said allocated backbone or backhaul capacity among said affected access controllers in proportion to their sum of subscriber committed information rates in the backhaul links interfaced to said affected access controllers;

c. identifying access controllers with highest ratios of backhaul utilization to said sum of subscriber committed information rates in the backhaul links interfaced to said affected access controllers and performing a slow start process to set their said bandwidth settings at a percentage of their initial settings;

d. configuring said bandwidth settings of said affected access controllers based on served subscriber committed information rate or maximum information rate to proactively limit network traffic traversing the backhaul links interfaced to said affected access controllers.

8. The method of claim 7, wherein the allocated backbone capacity is configured to be less than total capacity of the backbone link nearing congestion.

9. The method of claim 7, wherein the allocated backhaul capacity is configured to be less than total capacity of the backhaul link nearing congestion.

10. The method of claim 1, wherein said checking if said subscribers'"'"' service level agreements in the backbone or backhaul links nearing congestion are violated is performed by checking if sum of subscriber committed information rates in the backbone links nearing congestion reached a predetermined backbone allocation threshold setting or checking if sum of subscriber committed information rates in the backhaul links nearing congestion reached a predetermined backhaul allocation threshold setting.