# US 2013/0254343 A1 · Server with message exchange accounting

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254343 A1
- Document ID: US20130254343A1
- Status: Published application
- Kind: A1
- Application number: 13/471,079
- Filed: 2012-05-14
- Published: 2013-09-26
- Earliest claimed: 2012-03-22
- Assignees: Akamai Technologies, Inc.
- Inventors: Matthew J. Stevens; Ameya P. Shendarkar
- Web page: https://patentgrep.com/patent/US20130254343A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 63/02: {for separating internal from external traffic, e.g. firewalls}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/289: Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
- H04N 21/222: Secondary servers, e.g. proxy server, cable television Head-end {(provisioning of proxy services in data packet switching networks H04L67/56)}
- H04N 21/237: Communication with additional data server
- H04N 21/2396: {characterized by admission policies (admission control, resource allocation in open networks H04L12/5692; arrangements for network security using user profiles for access control H04L63/102; access security in wireless networks H04W12/08)}
- H04L 61/2503: Translation of Internet protocol [IP] addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

A server has a firewall module that performs accounting of traffic seen at the server. The traffic includes message exchanges, such as HTTP requests and HTTP responses. The server tests the message exchanges to determine if they match any of several message exchange categories. The server keeps statistics on matching traffic, for example the rate of matching traffic generated by a particular requesting client. Typically, the server is a proxy server that is part of a content delivery network (CDN), and the message exchanges occur between a client requesting content, the proxy server, other servers in the CDN, and/or an origin server from which the proxy server retrieves requested content. Using the message exchange model and the statistics generated thereby, the server can flag particular traffic or clients, and take protective action (e.g., deny, alert). In an alternate embodiment, a central control system gathers statistics from multiple servers for analysis.

## Claims

### Claim at position 1

-11. (canceled)

### Claim 12

A computer-implemented method operative at a proxy server that comprises circuitry forming one or more processors and memory holding instructions for execution by the one or more processors, the proxy server being communicatively coupled to a computer network, the method comprising:
at the proxy server, participating in an exchange of messages between at least one of (i) a client and the proxy server and (ii) the proxy server and an origin server, wherein the exchange of messages is in accordance with a protocol and includes at least one request message and at least one response message;
applying one or more match conditions against the content of multiple messages in the exchange of messages, the one or more match conditions defining a category of message traffic that is of interest;
if the one or more match conditions are satisfied, recording information about the message exchange at the proxy server; and,
if the one or more match conditions are not satisfied, not recording said information.

### Claim 13 (depends on 12)

The method of claim 12, wherein the multiple messages in the exchange of messages include at least one response message received by the proxy server from the origin server.

### Claim 14 (depends on 12)

The method of claim 12, wherein the multiple messages in the exchange of messages include at least one request message sent from the proxy server to the origin server.

### Claim 15 (depends on 12)

The method of claim 12, wherein the one or more match conditions include a condition that is satisfied by any request message from the proxy server to the origin server.

### Claim 16 (depends on 12)

The method of claim 12, wherein the multiple messages in the exchange of messages include at least one request message and at least one response message.

### Claim 17 (depends on 12)

The method of claim 12, wherein messages have headers and bodies and the one or more match conditions specify a matching value for a field in any of a message header and a message body.

### Claim 18 (depends on 12)

The method of claim 12, wherein the protocol comprises HTTP and the one or more match conditions specify a matching value for an HTTP method.

### Claim 19 (depends on 12)

The method of claim 12, wherein recording information comprises incrementing a count associated with the category of traffic described by the one or more match conditions.

### Claim 20 (depends on 12)

The method of claim 12, wherein recording information comprises incrementing a count for a client identifier associated with the client.

### Claim 21 (depends on 12)

The method of claim 12, wherein recording information comprises incrementing a count associated with a URI related to the exchange of messages.

### Claim 22 (depends on 12)

The method of claim 12, wherein recording information comprises incrementing a count associated with the category of message traffic defined by the one or more match conditions, and further comprising:
using the recorded information to calculate a rate of occurrence for message traffic falling within the category that is associated with a particular client or URI.

### Claim 23 (depends on 12)

The method of claim 12, wherein recording information comprises incrementing a count associated with the category of message traffic defined by the one or more match conditions, and further comprising:
using the recorded information to calculate a rate of occurrence for message traffic that falls within the category and that is associated with a particular client or URI, and,
comparing the rate of occurrence to a threshold value to determine whether to limit requests associated with the particular client or URI.

### Claim 24 (depends on 12)

The method of claim 12, wherein the protocol is HTTP.

### Claim 25

A proxy server, comprising:
circuitry forming one or more processors;
a hardware interface communicatively coupled to a computer network;
memory holding instructions for execution by the one or more processors, wherein the instructions, when executed by the one or more processors, cause the proxy server to:
participate in an exchange of messages between at least one of (i) a client and the proxy server and (ii) the proxy server and an origin server, wherein the exchange of messages is in accordance with a protocol and includes at least one request message and at least one response message;
apply one or more match conditions against the content of multiple messages in the exchange of messages, the one or more match conditions defining a category of message traffic that is of interest;
if the one or more match conditions are satisfied, record information about the message exchange at the proxy server; and,
if the one or more match conditions are not satisfied, not record said information.

### Claim 26 (depends on 25)

The proxy server of claim 25, wherein the multiple messages in the exchange of messages include at least one response message received by the proxy server from the origin server.

### Claim 27 (depends on 25)

The proxy server of claim 25, wherein the multiple messages in the exchange of messages include at least one request message sent from the proxy server to the origin server.

### Claim 28 (depends on 25)

The proxy server of claim 25, wherein the one or more match conditions include a condition that is satisfied by any request message from the proxy server to the origin server.

### Claim 29 (depends on 25)

The proxy server of claim 25, wherein the multiple messages include at least one request message and at least one response message.

### Claim 30 (depends on 25)

The proxy server of claim 25, wherein messages have headers and bodies and the one or more match conditions specify a matching value for a field in any of a message header and a message body.

### Claim 31 (depends on 25)

The proxy server of claim 25, wherein the protocol comprises HTTP and the one or more match conditions specify a matching value for an HTTP method.

### Claim 32 (depends on 25)

The proxy server of claim 25, wherein the proxy server records information by incrementing a count associated with the category of message traffic described by the one or more match conditions.

### Claim 33 (depends on 25)

The proxy server of claim 25, wherein the proxy server records information by incrementing a count for a client identifier associated with the client.

### Claim 34 (depends on 25)

The proxy server of claim 25, wherein the proxy server records information by incrementing a count associated with a URI related to the exchange of messages.

### Claim 35 (depends on 25)

The proxy server of claim 25, wherein the proxy server records information by incrementing a count associated with the category of message traffic defining by the one or more match conditions, and the proxy server further:
uses the recorded information to calculate a rate of occurrence for message traffic that falls within the category and that is associated with a particular client or URI.

### Claim 36 (depends on 25)

The proxy server of claim 25, wherein recording information comprises incrementing a count associated with the category of message traffic defined by the one or more match conditions, and the proxy server further:
uses the recorded information to calculate a rate of occurrence for message traffic falling within the category that is associated with a particular client or URI, and,
compares the rate of occurrence to a threshold value to determine whether to limit requests associated with the particular client or URI.

### Claim 37 (depends on 25)

The proxy server of claim 25, wherein the protocol is HTTP.

### Claim at position 28

-88. (canceled)
