IP Library Granted Patent US 10,681,052
Granted Patent B2
US 10,681,052 · App. 16/057,994 · Granted Jun 9, 2020

Method and system for classifying network requests

Inventors: Phil Wang (Sunnyvale, CA); Ravikiran Meka (Bangalore, IN)
Assignee: Oath Inc.
H04L63/101H04L63/08H04L63/1433H04L67/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,681,052
App. No.
16/057,994
Granted
Jun 9, 2020
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 (44)

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;

determining a mode of operation based on a startup signal;

selecting a rule associated with the mode of operation;

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

determining whether the at least one non IP key satisfies the selected rule;

determining, upon the selected rule being satisfied by the at least one non IP key, whether content to the client device is to be transmitted or blocked based on the mode of operation; and

computing, in response to the selected rule being unsatisfied, a score indicative of a likelihood of denying the network request.

2. The method of claim 1 , wherein the at least one non-IP key is one of 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 1 , wherein the mode of operation is a first mode of operation and the selected rule is a whitelist rule, and content to the client device is transmitted upon the at least one non IP key satisfying the whitelist rule.

4. The method of claim 1 , wherein the mode of operation is a second mode of operation and the selected rule is a blacklist rule, and the network request is blocked upon the at least one non IP key satisfying the blacklist rule.

5. 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 content to the client device is to be transmitted or blocked is based on the at least one non IP key and the at least one IP key satisfying the selected rule.

6. The method of claim 5 , wherein the at least one IP key is one of a peer IP address, a remote IP address, and a proxy IP address.

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,

determine a mode of operation based on a startup signal, and

select a rule associated with the mode of operation; 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 the at least one non IP key satisfies the selected rule,

determine, upon the selected rule being satisfied by the at least one non IP key, whether content to the client device is to be transmitted or blocked based on the mode of operation, and

compute, in response to the selected rule being unsatisfied, a score indicative of a likelihood of denying the network request.

8. The system of claim 7 , wherein the at least one non-IP key is one of 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 7 , wherein the mode of operation is a first mode of operation and the selected rule is a whitelist rule, and content to the client device is transmitted upon the at least one non IP key satisfying the whitelist rule.

10. The system of claim 7 , wherein the mode of operation is a second mode of operation and the selected rule is a blacklist rule, and the network request is blocked upon the at least one non IP key satisfying the blacklist rule.

11. The system of claim 7 , wherein the matcher is further configured to:

obtain at least one IP key based on the network request, and determine whether content to the client device is to be transmitted or blocked is based on the at least one non IP key and the at least one IP key satisfying the selected rule.

12. The system of claim 11 , wherein the at least one IP key is one of a peer IP address, a remote IP address, and a proxy IP address.

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 the following:

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

determining a mode of operation based on a startup signal;

selecting a rule associated with the mode of operation;

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

determining whether the at least one non IP key satisfies the selected rule;

determining, upon the selected rule being satisfied by the at least one non IP key, whether content to the client device is to be transmitted or blocked based on the mode of operation; and

computing, in response to the selected rule being unsatisfied, a score indicative of a likelihood of denying the network request.

14. The medium of claim 13 , wherein the at least one non-IP key is one of 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 13 , wherein the mode of operation is a first mode of operation and the selected rule is a whitelist rule, and content to the client device is transmitted upon the at least one non IP key satisfying the whitelist rule.

16. The medium of claim 13 , wherein the mode of operation is a second mode of operation and the selected rule is a blacklist rule, and the network request is blocked upon the at least one non IP key satisfying the blacklist rule.

17. The medium of claim 13 , further comprising:

obtaining at least one IP key based on the network request, and wherein the step of determining whether content to the client device is to be transmitted or blocked is based on the at least one non IP key and the at least one IP key satisfying the selected rule.

18. The method of claim 1 , wherein the step of computing is performed in response to the mode of operation being a second mode of operation, and the selected rule being a blacklist rule, and wherein the method further comprises transmitting content to the client device based on the score satisfying a criterion.

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 Aug 8, 2018
From: WANG, PHIL; MEKA, RAVIKIRAN
To: YAHOO! INC.
Reel/Frame 046582/0216 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 8, 2018
From: YAHOO! INC.
To: YAHOO HOLDINGS, INC.
Reel/Frame 046745/0251 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 8, 2018
From: YAHOO HOLDINGS, INC.
To: OATH INC.
Reel/Frame 046746/0001 →
Cited By (1)
US 12,335,280