Systems and methods for identifying and characterizing client devices

• US 9,692,830 B2
• Filed: 07/14/2016
• Issued: 06/27/2017
• Est. Priority Date: 12/30/2011
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Heller, Alec, Kobrin, Eric L., Scaffidi, Stephen R., Tetzner, Walter P., Kaufman, David H.
• Primary Examiner(s): Parry, Chris
• Assistant Examiner(s): STILTNER, WEIWEI YE
• Application Number:
  US15/210,357
• Publication Number:
  US 20160323387A1
• Time in Patent Office: 348 Days
• Field of Search: 709227
• CPC Class Codes: G06F 16/2237 Vectors, bitmaps or matrices
• CPC Class Codes: G06F 16/24575 using context
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The teachings herein generally relate to client-server communications and the delivery of content over computer networks to clients, and provide improved methods, systems, and apparatus for identifying and/or characterizing client devices that are requesting content from a server. For example, based on information sent in a client device'"'"'s request for content, a web server modified in accordance with the teachings hereof can identify a set of characteristics associated with that client device. Such characteristics might include the model name of the client device, the screen dimensions of the client device, information about the particular operating system or browser name/version it is running, content formats it is capable of consuming, and so on. The web server can use this information to modify and customize its response for the given client device.

Claims

1. A system, comprising:

a first computer that has circuitry forming one or more processors and memory storing instructions to be executed by the one or more processors to operate the first computer to;

(i) generate a list of tokens based on a plurality of sample user agent header fields;

(ii) generating a whitelist by removing one or more tokens from the list, the removed one or more tokens being selected for removal because they are low-value tokens with respect to any of a content delivery process and a content optimization process;

(iii) create a match index, the match index associating each of one or more client devices with a set of one or more tokens from the whitelist, where client devices are identified in the match index by client device identifiers;

(iv) sending the match index to a second computer, to configure the second computer to identify client devices;

the second computer that has circuitry forming one or more processors and memory storing instructions to be executed by the one or more processors to operate the second computer to;

(v) receive and store the match index;

(vii) receive a request for content from a client device;

(viii) generate one or more tokens from information in the request;

(ix) identify the client device as a particular one of one or more known client devices, wherein said identification step includes;

with the match index, looking up a particular client device identifier that is associated with the one or more tokens that were generated from the information in the request.

2. The system of claim 1, wherein the one or more tokens generated from the information in the request represent portions of user-agent strings.

3. The system of claim 1, wherein the request comprises an HTTP request.

4. The system of claim 1, wherein the requesting client device is a mobile device.

5. The system of claim 1, wherein the second computer comprises an HTTP proxy server.

6. A method operable in a plurality of computers for identifying a client device making requests for content, each of the plurality of computers comprising circuitry forming one or more processors and memory storing instructions to be executed by the one or more processors and thereby perform the method, the method comprising:

at a first computer;

generating a list of tokens based on a plurality of sample user agent header fields;

generating a whitelist by removing one or more tokens from the list, the removed one or more tokens being selected for removal because they are low-value tokens with respect to any of a content delivery process and a content optimization process;

sending the whitelist to a second computer to configure the second computer to identify client devices;

creating a match index, the match index associating each of one or more client devices with a set of one or more tokens from the whitelist, where client devices are identified in the match index by client device identifiers;

sending the match index to the second computer;

at the second computer;

receiving and storing the match index;

receiving a request for content from a client device;

generating one or more tokens from information in the request;

identifying the client device as a particular one of one or more known client devices, wherein said identification step includes;

with the match index, looking up a particular client device identifier that is associated with the one or more tokens that were generated from the information in the request.

7. The method of claim 6, wherein the one or more tokens generated from the information in the request represent portions of user-agent strings.

8. The method of claim 6, wherein the request comprises an HTTP request.

9. The method of claim 6, wherein the requesting client device comprises a mobile device.

10. The method of claim 6, wherein the one or more computers include an HTTP proxy server.