IP Library Granted Patent US 10,116,661
Granted Patent B2
US 10,116,661 · App. 15/391,716 · Granted Oct 30, 2018

Method and system for classifying network requests

Inventors: Phil Wang (Sunnyvale, CA); Ravikiran Meka (Bangalore, IN)
Assignee: Oath Inc.
H04L63/101H04L61/2007H04L63/08H04L67/02H04L67/146H04L2463/121
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,116,661
App. No.
15/391,716
Granted
Oct 30, 2018
Kind
B2
Abstract

Methods, systems and programming for classifying network requests. In one example, a network request for content to be fetched by a content server is received from a client device. At least one non-internet protocol (IP) key is obtained based on the network request. Whether to deny or allow the network request is determined based on the at least one non-IP key.

Claims (34)

1. A method, implemented on at least one machine each of which having at least one processor, storage, and a communication platform connected to a network for classifying network requests, the method comprising:

receiving, from a client device, a network request for content to be fetched by a content server;

obtaining at least one non-internet protocol (IP) key based on the network request;

determining whether to deny the network request based on the at least one non-IP key satisfying a blacklist rule;

computing, in response to the blacklist rule being unsatisfied, a score indicative of a likelihood of denying the network request; and

transmitting content to the client device based on the score satisfying a criterion.

2. The method of claim 1 , wherein the at least one non-IP key comprises one or more selected from a uniform resource identifier (URI) key, a user key, a hypertext transfer protocol (HTTP) key, a location key, and a cookie key.

3. The method of claim 2 , wherein the URI key is a URI path or a URI parameter, wherein the user key is a user identifier (ID) or a user attribute, wherein the HTTP key is a protocol type, a HTTP method, or a HTTP header, wherein the location key is indicative of a location of a source or a destination, and wherein the cookie key is ab-cookie, a timestamp cookie, or a session cookie.

4. The method of claim 1 , further comprising obtaining at least one IP key based on the network request, and wherein the step of determining whether to deny the network request is based on the at least one IP key and the at least one non-IP key.

5. The method of claim 4 , wherein the at least one IP key comprises one or more selected from a peer IP address, a remote IP address, and a proxy IP address.

6. The method of claim 1 , wherein the step of determining to deny the network request is implemented upon receipt of a startup signal at runtime configuration.

7. A system having at least one processor, storage, and a communication platform connected to a network for classifying network requests, the system comprising:

an initializer implemented by the at least one processor and configured to receive, from a client device, a network request for content to be fetched by a content server; and

a matcher implemented by the at least one processor and configured to:

obtain at least one non-internet protocol (IP) key based on the network request;

determine whether to deny the network request based on the at least one non-IP key satisfying a blacklist rule;

compute, in response to the blacklist rule being unsatisfied, a score indicative of a likelihood of denying the network request; and

transmit content to the client device based on the score satisfying a criterion.

8. The system of claim 7 , wherein the at least one non-IP key comprises one or more selected from a uniform resource identifier (URI) key, a user key, a hypertext transfer protocol (HTTP) key, a location key, and a cookie key.

9. The system of claim 8 , wherein the URI key is a URI path or a URI parameter, wherein the user key is a user identifier (ID) or a user attribute, wherein the HTTP key is a protocol type, a HTTP method, or a HTTP header, wherein the location key is indicative of a location of a source or a destination, and wherein the cookie key is ab-cookie, a timestamp cookie, or a session cookie.

10. The system of claim 7 , wherein the matcher is further configured to obtain at least one IP key based on the network request, and wherein whether to deny the network request is determined based on the at least one IP key and the at least one non-IP key.

11. The system of claim 10 , wherein the at least one IP key comprises one or more selected from a peer IP address, a remote IP address, and a proxy IP address.

12. The system of claim 7 , wherein whether the matcher is to deny the network request is implemented upon receipt of a startup signal at runtime configuration.

13. A non-transitory machine-readable medium having information recorded thereon for classifying network requests, wherein the information, when read by the machine, causes the machine to perform following:

receiving, from a client device, a network request for content to be fetched by a content server;

obtaining at least one non-internet protocol (IP) key based on the network request;

determining whether to deny the network request based on the at least one non-IP key satisfying a blacklist rule;

computing, in response to the blacklist rule being unsatisfied, a score indicative of a likelihood of denying the network request; and

transmitting content to the client device based on the score satisfying a criterion.

14. The medium of claim 13 , wherein the at least one non-IP key comprises one or more selected from a uniform resource identifier (URI) key, a user key, a hypertext transfer protocol (HTTP) key, a location key, and a cookie key.

15. The medium of claim 14 , wherein the URI key is a URI path or a URI parameter, wherein the user key is a user identifier (ID) or a user attribute, wherein the HTTP key is a protocol type, a HTTP method, or a HTTP header, wherein the location key is indicative of a location of a source or a destination, and wherein the cookie key is ab-cookie, a timestamp cookie, or a session cookie.

16. The medium of claim 13 , wherein the information, when read by the machine, further causes the machine to obtain at least one IP key based on the network request, and wherein whether to deny the network request is based on the at least one IP key and the at least one non-IP key.

17. The medium of claim 16 , wherein the at least one IP key comprises one or more selected from a peer IP address, a remote IP address, and a proxy IP address.

18. The medium of claim 13 , wherein to deny the network request is implemented upon receipt of a startup signal at runtime configuration.

Assignments (6)
PATENT SECURITY AGREEMENT (FIRST LIEN) Recorded Sep 29, 2022
From: YAHOO ASSETS LLC
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 061571/0773 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2021
From: YAHOO AD TECH LLC (FORMERLY VERIZON MEDIA INC.)
To: YAHOO ASSETS LLC
Reel/Frame 058982/0282 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2020
From: OATH INC.
To: VERIZON MEDIA INC.
Reel/Frame 054258/0635 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 2, 2018
From: YAHOO HOLDINGS, INC.
To: OATH INC.
Reel/Frame 045240/0310 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 2, 2017
From: WANG, PHIL; MEKA, RAVIKIRAN
To: YAHOO! INC.
Reel/Frame 044019/0586 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 23, 2017
From: YAHOO! INC.
To: YAHOO HOLDINGS, INC.
Reel/Frame 042963/0211 →
Continuity (1)
Related Publication 20180183798A1 · Jun 28, 2018