Application based bandwidth limiting proxies

• US 20020110084A1
• Filed: 12/18/2000
• Published: 08/15/2002
• Est. Priority Date: 12/18/2000
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Eatough, David A., Butt, Alan B., Sarra, Tony N.
• Granted Patent: US 6,928,051 B2
• Time in Patent Office: Days
• US Class Current: 370/230
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/13 in a LAN segment, e.g. ring or bus
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Embodiments of application based bandwidth limiting proxy servers are described.

Claims

1. A method comprising:

receiving a packet at a forwarding device, the packet specifying a port number corresponding to an application to be bandwidth limited; and

forwarding the packet according to a bandwidth limiting policy.

2. The method of claim 1 and further comprising the forwarding device changing the port number from the port number corresponding to an application to be bandwidth limited to another port number prior to forwarding the packets.

3. The method of claim 2 wherein said another port number comprises a port number corresponding to regular traffic that is not bandwidth limited.

4. The method of claim 1 wherein the bandwidth limiting policy comprises an application based bandwidth limiting policy that throttles or limits the use of bandwidth by one or more types of applications.

5. A method comprising:

receiving a packet;

forwarding the packet according to a bandwidth limiting policy if the packet is a first type of packet; and

forwarding the packet without bandwidth limiting if the packet is a second type of packet.

6. The method of claim 5 wherein the type of packet is detected based on a destination port number of the packet.

7. The method of claim 5 wherein the first type of packet is indicated based on a first destination port number in the packet, and the second type of packet is indicated by a second destination port number in the packet.

8. A method comprising:

receiving a packet;

detecting whether or not the packet was sent by an application to be bandwidth limited;

forwarding the packet without bandwidth limiting if the packet was sent by an application that is not to be bandwidth limited; and

otherwise, if the packet was sent by an application to be bandwidth limited, then forwarding the packet according to an application based bandwidth limiting policy.

9. The method of claim 8 wherein the receiving a packet comprises a proxy server receiving the packet.

10. The method of claim 8 wherein the detecting whether or not the packet was sent by an application to be bandwidth limited comprises detecting a port number in the packet corresponding to a type of application to be bandwidth limited.

11. The method of claim 10 and further comprising changing the port number in the received packet from the port number corresponding to a type of application to be bandwidth limited to a regular port number prior to forwarding the packet.

13. The apparatus of claim 12 wherein the instructions further result in the following when executed:

changing the port number from the port number corresponding to an application to be bandwidth limited to another port number prior to forwarding the packets.

14. The apparatus of claim 13 wherein the instructions further result in the following when executed:

receiving a second packet specifying a port number corresponding to an application not to be bandwidth limited; and

forwarding the packet without using the bandwidth limiting policy.

16. The apparatus of claim 15 wherein the determining comprises determining a type of application that sent the packet based on a port number in the packet.

17. The apparatus of claim 16 wherein the determining comprises determining a type of application that sent the packet based on a destination port number in the packet.

19. The apparatus of claim 18 wherein the server comprises a server to forward the packets while limiting bandwidth usage based on requirements or rules of the policy.

20. The apparatus of claim 18 wherein the server comprises an application based bandwidth limiting server.

12. An apparatus comprising a storage readable media having instructions stored thereon, the instructions resulting in the following when executed:

receiving a packet, the packet specifying a port number corresponding to an application to be bandwidth limited; and

forwarding the packet according to a bandwidth limiting policy.

15. An apparatus comprising a storage readable media having instructions stored thereon, the instructions causing the following to be performed when executed:

receiving a packet;

determining a type of application that sent the packet;

forwarding the packet according to a bandwidth limiting policy if the packet is sent by a first type of application; and

forwarding the packet without bandwidth limiting if the packet is from a second type of application.

18. An apparatus comprising a server to grant a connection request received for a destination port number corresponding to a type of application to be bandwidth limited, and to reject a connection request for a destination port number which does not correspond to the type of application to be bandwidth limited, the server to forward any received packets after granting the connection request according to an application based bandwidth limiting policy.

21. An apparatus comprising a server to receive a packet and detect a type of application that sent the packet from examining the packet, to forward the packet without bandwidth limiting or throttling the packet if the packet was sent from a first type of application, and to forward the packet according to a bandwidth or throttling policy if the packet was sent from a second type of application.

22. The apparatus according to claim 21 wherein the apparatus detects the type of application that sent the packet on the basis of a destination port number in the packet.

23. The apparatus of claim 21 wherein the first type of application is a regular type of application that is not to be bandwidth limited or throttled by the proxy server, while the second type of application comprises one or more types of applications that are to be bandwidth limited or throttled according to the bandwidth limiting policy.

24. The apparatus of claim 21 wherein the server comprises an application based bandwidth limiting proxy server.

26. The apparatus of claim 25 wherein the limiting forwarding device comprises an application based bandwidth limiting proxy server.

29. The apparatus of claim 27 wherein the bandwidth limiting policy comprises an application based bandwidth limiting policy.

25. An apparatus comprising:

a non-limiting forwarding device coupled between first and second groups of applications to receive and forward packets;

a limiting forwarding device coupled to the first group of applications to receive a packet and to detect whether the packet was sent by an application to be bandwidth limited, and then to forward the packet to the non-limiting forwarding device according to an application based bandwidth limiting policy if the packet was sent by an application to be bandwidth limited.

27. An apparatus comprising:

a bandwidth limiting policy;

a proxy server to respond to requests and forward messages;

a local memory to store response messages, the proxy server to respond to requests with messages from the local memory if available, otherwise to retrieve a requested message from another server and then forward the message according to a bandwidth limiting policy.

28. The apparatus of clam 27 wherein the local memory comprises a cache.