Application aware traffic shaping service node positioned between the access and core networks

• US 7,606,147 B2
• Filed: 04/13/2005
• Issued: 10/20/2009
• Est. Priority Date: 04/13/2005
• Status: Active Grant

• Current Assignee: Tellabs Communications Canada Ltd. (Infinera Corp.)
• Original Assignee: Zeugma Systems Incorporated (Infinera Corp.)
• Inventors: Luft, Siegfried Johannes, Chiang, Ping
• Primary Examiner(s): Yao; Kwang B
• Assistant Examiner(s): Elpenord; Candal
• Application Number:
  US11/106,163
• Publication Number:
  US 20060233100A1
• Time in Patent Office: 1,651 Days
• Field of Search: 370229-237, 370/395.2, 370/395.21, 370/395.42, 370/395.43, 370/241, 370/252
• US Class Current: 370/229
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• 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 41/5019 Ensuring fulfilment of SLA
• CPC Class Codes: H04L 41/5022 by giving priorities, e.g. assigning classes of service
• CPC Class Codes: H04L 41/5087 wherein the managed service relates to voice services management of VoIP services H04M7/0081
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/22 Traffic shaping
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 47/32 by discarding or delaying data units, e.g. packets or frames
• CPC Class Codes: H04W 92/02 Inter-networking arrangements

Abstract

A method and apparatus for an application aware traffic shaping service node positioned between the access and core networks is described. One embodiment of the invention enforces a per subscriber, per application traffic policy for network traffic between one or more subscribers communicatively connected through an access network and a set of one or more service providers communicatively connected through a core network. According to another embodiment of the invention enforcement of the per subscriber, per application traffic policy comprises classifying the network traffic into application level subscriber flows, maintaining real-time statistics on the application level subscriber flows and overall network element congestion, updating, in real-time, the per subscriber, per application traffic policy based on the real-time statistics and restricting bandwidth and dropping packets on the application level subscriber flows as necessary to enforce the per subscriber, per application traffic policy. Another embodiment of the invention is a passthrough mode where the data traffic is transmitted by the traffic in the same manner as received by the traffic shaping service node. Yet another embodiment of the invention is a combined service node with integral edge routing and traffic aggregator.

Claims

1. A method comprising:

enforcing a per subscriber, per application traffic policy on network traffic flowing through a network device between a set of one or more subscribers communicatively coupled through an access network and a set of one or more services communicatively coupled through a core network by;

classifying the network traffic at the network device located between the access network and the core network into application level subscriber flows, the classifying including identifying a particular subscriber associated with a given packet, identifying a particular application associated with the given packet, and identifying a control protocol if the given packet contains control protocol data for the particular application;

generating real-time statistics at the network device on the application level subscriber flows and overall network element congestion, wherein the real-time statistics are generated at least in part based on deep packet inspection of the network traffic;

updating, in real-time, at the network device, the per subscriber, per application traffic policy based on the real-time statistics and the classifying, wherein the updating is triggered by the real-time statistics and by identified control protocols; and

restricting bandwidth for the application level subscriber flows at the network device to enforce the updated per subscriber, per application traffic policy.

2. The method of claim 1, wherein the classifying the network traffic comprises deep packet inspection.

3. The method of claim 1, wherein the classifying the network traffic comprises identifying an instance of an application.

4. The method of claim 1, wherein the classifying the network traffic comprises querying the packet to determine if the packet is associated with an application control program.

5. The method of claim 1, wherein maintaining real-time statistics comprises gathering statistics selected from the group consisting of network statistics, long-term subscriber statistics, short-term subscriber statistics and application statistics.

12. The method of claim 1, further comprising:

if the given packet contains the control protocol data for the particular application, then temporarily increasing bandwidth limits for a data flow of the particular application.

13. The method of claim 1, wherein generating the real-time statistics further comprises:

determine a sliding window time period;

generating short term statistics for a given subscriber during the sliding window time period; and

generating short term statistics for a given application associated with the given subscriber during the sliding window time period.

14. The method of claim 13, wherein generating the real-time statistics further comprises generating long term statistics for the given subscriber for a duration of a session associated with the given subscriber.

15. The method of claim 14, wherein restricting bandwidth for the application level subscriber flows further includes restricting bandwidth of the particular application for the particular subscriber based at least in part on short term statistics and long term statistics generated for the particular subscriber.

6. A traffic shaping network device comprising:

a first set of interfaces to couple to an access network through which a plurality of subscribers are communicatively coupled;

a second set of interfaces to couple to a core network through which a plurality of service providers are communicatively coupled;

classifying modules distributed across at least the first and second set of interfaces to classify network traffic between the access and the core networks into application level subscriber flows;

statistics modules distributed across at least the first and second set of interfaces and coupled to receive results of the classifying modules and coupled to maintain real-time statistics on individual subscribers, individual applications, and overall network element congestion based on the results of the classifying modules, wherein the real-time statistics are generated at least in part based on deep packet inspection of the network traffic;

a policy module coupled to receive the real-time statistics and to update the per subscriber, per application traffic policies in real-time based on the real-time statistics; and

a set of traffic modules distributed across the first and second set of interfaces, the traffic modules coupled to receive the updated per subscriber, per application traffic policies in real-time and to enforce the updated per subscriber, per application traffic policy by restricting bandwidth and dropping packets on the application level subscriber flows flowing between the first and second set of interfaces.

7. The traffic shaping network device of claim 6, wherein the classifying module further comprises deep packet inspection on the network traffic.

8. The traffic shaping network device of claim 6, wherein the classifying module further comprises identifying an instance of an application of the network traffic.

9. The traffic shaping network device of claim 6, wherein the classifying module further comprises querying a packet to determine if the packet is associated with an application control program.

10. The traffic shaping network device of claim 6, wherein the statistics module further comprises gathering statistics selected from the group consisting of network statistics, long-term subscriber statistics, short-term subscriber statistics and application statistics.

11. The traffic shaping network device of claim 6, wherein the subscriber application level traffic shaping network device is non-routing.

16. The traffic shaping network device of claim 6, wherein the policy module comprises a plurality of policy modules distributed across a plurality of processor cards and wherein the first and second set of interfaces comprise a plurality of line cards each coupled to each of the processor cards.

17. The traffic shaping network device of claim 16, wherein portions of the classify modules and statistics modules are also distributed across the plurality of processor cards.

18. The traffic shaping network device of claim 17 wherein the policy modules operating on the processor cards update traffic policies enforced by the traffic modules operating on the line cards in response to identified control protocols without introducing delay in data flows flowing between the line cards.

19. The traffic shaping network device of claim 17, wherein a first processor card comprises a backup processor card for a second processor card by maintaining functionality and state information for the second processor card to be ready to takeover functions of the second processor card in an event of failure.