Method and apparatus for enforcing service level agreements

• US 7,272,115 B2
• Filed: 09/30/2002
• Issued: 09/18/2007
• Est. Priority Date: 08/31/2000
• Status: Expired due to Term

• Current Assignee: AudioCodes, Inc. (Audiocodes Limited)
• Original Assignee: AudioCodes, Inc. (Audiocodes Limited)
• Inventors: Hervin, Mark Warden, Maher, III, Robert Daniel, Deerman, James Robert, Lie, Milton Andre
• Primary Examiner(s): Pham, Chi
• Assistant Examiner(s): JONES, PRENELL P
• Application Number:
  US10/260,768
• Publication Number:
  US 20030118029A1
• Time in Patent Office: 1,814 Days
• Field of Search: 370/253, 370/395, 370/428, 370/254, 370235-238, 709/231, 709219-229, 709/230
• US Class Current: 370/253
• CPC Class Codes: H04L 41/5022 by giving priorities, e.g. assigning classes of service
• CPC Class Codes: H04L 41/5083 wherein the managed service relates to web hosting
• CPC Class Codes: H04L 41/5087 wherein the managed service relates to voice services management of VoIP services H04M7/0081
• CPC Class Codes: H04L 41/5093 wherein the managed service relates to messaging or chat services
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]

Abstract

A network device for enforcing service level agreements is described that is able to scan the contents of entire data packets including header and payload information. The network device includes memory for storing subscriber information, policies and statistics. The traffic flow scanning processor scans the header and payload information from each data packet, which is used to associate each data packet with a particular subscriber, classify the type of network traffic in the data packet and to enforce the particular policies associated with the subscriber. The traffic flow scanning processor produces a treatment for the data packet based on the scanning. The scanned data packets and the associated treatments are then passed to a quality of service processor, which modifies the data packets if necessary and enforces resource allocation according to the preprogrammed policies.

Claims

1. A network device for enforcing service level agreements between a provider and a customer set relating to a network having network traffic composed of data packets, the network device comprising:

memory for storing customer information, statistics and policies, the policies defining network attributes and services agreed to in the service level agreement;

a traffic flow scanning processor connected to the memory for scanning data packets, associating the data packets with a particular customer from the customer set, and determining a treatment for the data packets based on the policies for the particular customer; and

a quality of service processor connected to the traffic flow scanning processor and including a plurality of queues to process the data packets according to the treatment determined by the traffic flow scanning processor, wherein the network device checks for available bandwidth for each of the data packets by comparing available capacity for a particular type of network traffic contained within the data packets with a predetermined unit capacity associated with the particular type of network traffic, such that if the available capacity is greater than the unit capacity there is available bandwidth for the data packets.

2. The network device of claim 1 wherein the policies define maximum capacities for each type of network traffic, each of the maximum capacities being programmable, wherein the sum of the maximum capacities define the bandwidth allocated to the customer.

3. The network device of claim 1 wherein the traffic flow scanning processor classifies the data packets as real time traffic or non-real time traffic.

4. The network device of claim 3 wherein data packets associated with non-real time type network traffic that does not have available bandwidth are sent to queues associated with another non-real time traffic type for the customer.

5. The network device of claim 1 wherein the traffic flow scanning processor and the quality of service processor are further able to provide security services for the customer.

6. The network device of claim 1 wherein the network traffic includes real time video, voice over IP, email, web surfing, and file transfers.

7. The network device of claim 1 wherein the memory also stores event information per subscriber.

8. The network device of claim 1 wherein the treatment includes modifying the data packet.

9. A method for enforcing resource allocation in service level agreements for a data network including a plurality of traffic flows each formed by a plurality of data packets, the method comprising:

associating a data packet with a particular customer;

classifying contents of the data packet, the contents being classified as a type of traffic that is real time or non-real time;

checking for available bandwidth according to preprogrammed policies for the particular customer and the type of traffic; and

sending the data packet to an appropriate quality of service queue based on the type of traffic and available bandwidth according to the preprogrammed policies, wherein real time traffic is marked for deletion when there is not available bandwidth in the associated quality of service queue.

10. The method of claim 9 wherein non-real time traffic includes a plurality of types of network traffic each of the plurality of types of network traffic having a quality of service queue with a predetermined capacity based on the preprogrammed policies such that if there is not available bandwidth in the quality of service queue associated with the type of traffic the method checks for available bandwidth in quality of service queues associated with other non-real time types of network traffic.

11. The method of claim 10 wherein data packets associated with non-real time traffic are sent to a best efforts quality of service queue when there is not available bandwidth in the associated quality of service queue or in other non-real time quality of service queues.

12. The method of claim 9 wherein checking for available bandwidth includes comparing available capacity with a predetermined unit capacity associated with the particular type of traffic, such that if the available capacity is greater than the unit capacity there is available bandwidth for the data packet.

13. The method of claim 10 wherein the total bandwidth for the particular customer is the sum predetermined capacities for all traffic types.