Per user per service traffic provisioning

• US 20040064560A1
• Filed: 09/26/2002
• Published: 04/01/2004
• Est. Priority Date: 09/26/2002
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Jiang, Tianji, Zhang, Shujin
• Granted Patent: US 7,130,917 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/5602 Bandwidth control in ATM Networks, e.g. leaky bucket
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/215 using token-bucket
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/32 by discarding or delaying data units, e.g. packets or frames

Abstract

A host object representing a user, a service object representing a service, and a connection object linking the two may be utilized in order to provide Quality of Service (QoS). The host object and/or connection object may contain a provisioning scheme defining a limit on traffic, which can be provided through either a local or remote programming mechanism. When traffic flows through the host object and/or connection object, the appropriate provisioning scheme is utilized to determine which packets to discard.

Claims

1. A method for providing quality of service for a user in a gateway, comprising:

defining a host object corresponding to the user, the host object having a provisioning scheme indicating a limit on traffic sent to or from the user; and

discarding traffic sent to or from the user that exceeds said limit.

2. The method of claim 1, wherein said defining a host object occurs when a user logs in.

3. The method of claim 1, wherein said host object is defined using a user profile having an attribute describing provisioning parameters.

4. The method of claim 3, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

5. The method of claim 1, wherein said provisioning scheme is implemented as token bucket provisioning.

6. The method of claim 1, further including receiving said provisioning scheme through a remote subscriber management system.

7. A method for providing quality of service for a service in a gateway, comprising:

defining a service object corresponding to the service;

creating a connection object linking said service object to a host objects, the host object corresponding to a user subscribing to the service, wherein the connection object has a provisioning scheme indicating a limit on traffic sent to or from the service; and

discarding traffic sent to or from the service that exceeds said limit.

8. The method of claim 7, wherein said defining a service object occurs when a user logs in to the service.

9. The method of claim 7, wherein said connection object is created using a service profile having an attribute describing provisioning parameters.

10. The method of claim 9, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

11. The method of claim 7, wherein said provisioning scheme is implemented as token bucket provisioning.

12. The method of claim 7, further including receiving said provisioning scheme through a remote subscriber management system.

13. A method for providing quality of service for a user subscribing to one or more services in a gateway, comprising:

defining a host object corresponding to the user, the host object having a provisioning scheme indicating a limit on traffic sent to or from the user;

defining a service object corresponding to one of the services;

creating a connection object linking said service object to said host object, the connection object having a provisioning scheme indicating a limit on traffic sent to or from the service;

discarding traffic sent to or from the user that exceeds said limit on traffic sent to or from the user; and

discarding traffic sent to or from the service that exceeds said limit on traffic sent to or from the service.

14. The method of claim 13, wherein said defining a host object occurs when a user logs in.

15. The method of claim 13, wherein said host object is defined using a user profile having an attribute describing provisioning parameters.

16. The method of claim 13, wherein said defining a service object occurs when a user logs in to the service.

17. The method of claim 13, wherein said connection object is created using a service profile having an attribute describing provisioning parameters.

18. The method of claim 15, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

19. The method of claim 17, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

20. The method of claim 13, wherein said provisioning scheme is implemented as token bucket provisioning.

21. The method of claim 13, further including receiving said provisioning schemes through a remote subscriber management system.

22. A gateway comprising:

a host object definer; and

a traffic discarder coupled to said host object definer.

23. A gateway comprising:

a service object definer;

a connection object creator coupled to said service object definer; and

a traffic discarder coupled to said connection object creator.

24. A gateway comprising:

a host object definer;

a service object definer;

a connection object creator coupled to said host object definer and said service object definer;

a traffic discarder coupled to said host object definer and said connection object creator.

25. An apparatus for providing quality of service for a user in a gateway, comprising:

means for defining a host object corresponding to the user, the host object having a provisioning scheme indicating a limit on traffic sent to or from the user; and

means for discarding traffic sent to or from the user that exceeds said limit.

26. The apparatus of claim 25, wherein said defining a host object occurs when a user logs in.

27. The apparatus of claim 25, wherein said host object is defined using a user profile having an attribute describing provisioning parameters.

28. The apparatus of claim 27, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

29. The apparatus of claim 25, wherein said provisioning scheme is implemented as token bucket provisioning.

30. The apparatus of claim 25, further including means for receiving said provisioning scheme through a remote subscriber management system.

31. An apparatus for providing quality of service for a service in a gateway, comprising:

means for defining a service object corresponding to the service;

means for creating a connection object linking said service object to a host object, the host object corresponding to a user subscribing to the service, wherein the connection object has a provisioning scheme indicating a limit on traffic sent to or from the service; and

means for discarding traffic sent to or from the service that exceeds said limit.

32. The apparatus of claim 31, wherein said defining a service object occurs when a user logs in to the service.

33. The apparatus of claim 31, wherein said connection object is created using a service profile having an attribute describing provisioning parameters.

34. The apparatus of claim 33, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

35. The apparatus of claim 31, wherein said provisioning scheme is implemented as token bucket provisioning.

36. The apparatus of claim 31, further including means for receiving said provisioning scheme through a remote subscriber management system.

37. An apparatus for providing quality of service for a user subscribing to one or more services in a gateway, comprising:

means for defining a host object corresponding to the user, the host object having a provisioning scheme indicating a limit on traffic sent to or from the user;

means for defining a service object corresponding to one of the services;

means for creating a connection object linking said service object to said host object, the connection object having a provisioning scheme indicating a limit on traffic sent to or from the service;

means for discarding traffic sent to or from the user that exceeds said limit on traffic sent to or from the user; and

means for discarding traffic sent to or from the service that exceeds said limit on traffic sent to or from the service.

38. The apparatus of claim 37, wherein said defining a host object occurs when a user logs in.

39. The apparatus of claim 37, wherein said host object is defined using a user profile having an attribute describing provisioning parameters.

40. The apparatus of claim 37, wherein said defining a service object occurs when a user logs in to the service.

41. The apparatus of claim 37, wherein said connection object is created using a service profile having an attribute describing provisioning parameters.

42. The apparatus of claim 41, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

43. The apparatus of claim 41, wherein said provisioning parameters include upstream bandwidth, upstream normal burst size, upstream excess burst size, downstream bandwidth, downstream normal burst size, and downstream excess burst size.

44. The apparatus of claim 37, wherein said provisioning scheme is implemented as token bucket provisioning.

45. The apparatus of claim 37, further including means for receiving said provisioning schemes through a remote subscriber management system.

46. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for providing quality of service for a user in a gateway, the method comprising:

defining a host object corresponding to the user, the host object having a provisioning scheme indicating a limit on traffic sent to or from the user; and

discarding traffic sent to or from the user that exceeds said limit.

47. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for providing quality of service for a service in a gateway, the method comprising:

defining a service object corresponding to the service;

creating a connection object linking said service object to a host object, the host object corresponding to a user subscribing to the service, wherein the connection object has a provisioning scheme indicating a limit on traffic sent to or from the service; and

discarding traffic sent to or from the service that exceeds said limit.

48. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for providing quality of service for a user subscribing to one or more services in a gateway, comprising:

defining a host object corresponding to the user, the host object having a provisioning scheme indicating a limit on traffic sent to or from the user;

defining a service object corresponding to one of the services;

creating a connection object linking said service object to said host object, the connection object having a provisioning scheme indicating a limit on traffic sent to or from the service;

discarding traffic sent to or from the user that exceeds said limit on traffic sent to or from the user; and

discarding traffic sent to or from the service that exceeds said limit on traffic sent to or from the service.