| US 7,373,416 B2 | ||
| Method and system for constraining server usage in a distributed network | ||
| Marty Kagan, North Hollywood, Calif. (US); Sylvain Lauzac, Seattle, Wash. (US); and Eisar Lipkovitz, San Francisco, Calif. (US) | ||
| Assigned to Akamai Technologies, Inc., Cambridge, Mass. (US) | ||
| Filed on Apr. 23, 2004, as Appl. No. 10/830,802. | ||
| Claims priority of provisional application 60/465145, filed on Apr. 24, 2003. | ||
| Prior Publication US 2005/0120107 A1, Jun. 02, 2005 | ||
| Int. Cl. G06F 15/16 (2006.01); G06F 15/173 (2006.01) | ||
| U.S. Cl. 709—232 [709/219; 709/241; 709/238; 709/223] | 11 Claims |
| 1. A content server for use in a content delivery network (CDN) that is shared by a set of content providers, the content
server being one of a set of other content servers in the CDN, comprising:
a processor;
an operating system;
a server process responsive to requests for serving given content from the content server to requesting end users; and
a manager process to enable each of the set of content providers to manage an amount of traffic served from the content server
and the other content servers in the CDN, wherein each content provider can manage its traffic independent of any other content
provider using attributes associated with first and second tags, wherein the attributes are identified by the content provider
via a secure configuration portal associated with the content delivery network, the attributes associated with the first tag
being settable on a per content provider basis and specifying one of a set of tables that are accessible on a per content
provider basis, and the attributes associated with the second tag being settable by the content provider and specifying a
given table selected from the set of tables and at least one match condition, comprising, on a content provider-by-content
provider basis:
first code responsive to a first tag attribute that is set by a given content provider to obtain one or more given tables
of traffic data for the given content provider, a given table of traffic data being at least one of a historical bandwidth
usage, and a current bandwidth usage; and
second code responsive to a second tag attribute that is set by the given content provider to determine, for each given table
of traffic data that is obtained, whether information in the given table of traffic data exceeds a given threshold that is
set by the given content provider; and
third code responsive to a determination that the given threshold has been met for controlling the server process to take
a given action, wherein the given action is one of: limiting outbound traffic served from the content server, serving an indication
that the given content is not available to be served from the content server, serving a modified version of the given content,
issuing a redirection to another server in the content delivery network, issuing a go forward request to a customer origin
server, and issuing an alert.
|