METHOD, SERVER, AND SYSTEM FOR DIRECTING NETWORK TRAFFIC

• US 20140325045A1
• Filed: 04/24/2013
• Published: 10/30/2014
• Est. Priority Date: 04/24/2013
• Status: Active Grant

• Current Assignee: Secured Connectivity, LLC
• Original Assignee: Selectivevpn, Inc.
• Inventors: PECHERSKY, Leonid
• Granted Patent: US 9,634,935 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 45/745 Address table lookup; Address filtering
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00

Abstract

A server, intermediation server, system and a method for directing network traffic are provided. The name server and intermediation server each include a network interface configured to communicate with a network, a memory configured to store the profile record a processor in communication with the memory and the network interface. The name server is for returning an assigned query result to a originating computing device when a destination identifier is associated with the profile record. The intermediation server is for perform a routing operation based on the request. The system includes an originating computing device a name server and an intermediation server all connected to a network. The method involves receiving a profile record and destination identifier, determining an association of the between the profile record and identifier, and returning with an assigned query result or a default query result.

Claims

1. A name server for directing network traffic from an originating computing device to a destination computing device, the server comprising:

a network interface configured to communicate with a network to receive a profile record for the originating computing device and a destination identifier;

a memory configured to store the profile record; and

a processor in communication with the memory and the network interface, the processor configured to determine if the destination identifier is associated with the profile record, the processor configured to return, via the network interface, an assigned query result to the originating computing device when the destination identifier is associated with the profile record, and the processor configured to return, via the network interface, a default query result to the originating computing device when the destination identifier is not associated with the profile record.

2. The server of claim 1, wherein the processor is further configured to request the assigned query result from an intermediation server.

3. The server of claim 1, wherein the destination identifier is a request for an intended numerical address.

4. The server of claim 3, wherein the processor is further configured to identify the originating computing device.

5. An intermediation server for directing network traffic from an originating computing device to a destination computing device, the server comprising:

a network interface configured to communicate with a network to receive a request for data intended for the destination computing device and a source identifier associated with the originating computing device;

a memory configured to store routing information in a routing database; and

a processor in communication with the memory and the network interface, the processor configured to perform a routing operation based on the request, the source identifier and the routing information.

6. The server of claim 5, wherein the processor is further configured to determine a routing operation based on the originating computing device and the destination identifier.

7. The server of claim 5, wherein the routing operation involves blocking traffic between the originating computing device and the destination computing device.

8. The server of claim 5, wherein the routing operation involves providing a notification interrupt for inserting a notification page.

9. The server of claim 5, wherein the routing operation involves anonymizing the originating computing device.

10. A system comprising:

an originating computing device connected to a network;

a name server for directing network traffic from the originating computing device to a destination computing device, the name server having a first network interface configured to communicate with the network to receive a profile record for the originating computing device and a destination identifier;

a first memory configured to store the profile record; and

a processor in communication with the first memory and the first network interface, the processor configured to determine if the destination identifier is associated with the profile record, the processor configured to return, via the first network interface, an assigned query result to the originating computing device when the destination identifier is associated with the profile record, and the processor configured to return, via the network interface, a default query result to the originating computing device when the destination identifier is not associated with the profile record; and

an intermediation server for directing network traffic from the originating computing device to the destination computing device, the intermediation server having a second network interface configured to communicate with the network to receive a request for data intended for the destination computing device and a source identifier associated with the originating computing device;

a second memory configured to store routing information in a routing database; and

a processor in communication with the second memory and the second network interface, the processor configured to perform a routing operation based on the request, the source identifier and the routing information.

11. A method of directing network traffic, the method comprising:

receiving, at a name server, a profile record for an originating computing device;

receiving, at the name server, a destination identifier from the originating computing device, the destination identifier associated with a destination computing device;

determining, at the name server, if the destination identifier is associated with the profile record;

returning, from the name server, an assigned query result to the originating computing device when the destination identifier is associated with the profile record; and

returning, from the name server, a default query result to the originating computing device when the destination identifier is not associated with the profile record.

12. The method of claim 11, wherein the name server requests the assigned query result from an intermediation server.

13. The method of claim 11, wherein the destination identifier is a request for an intended numerical address.

14. The method of claim 13, further comprising identifying, at the intermediation server, the originating computing device.

15. The method of claim 14, further comprising determining, at the intermediation server, a routing operation based on the originating computing device.

16. The method of claim 15, further comprising routing traffic in accordance with the routing operation.

17. The method of claim 16, wherein the routing operation involves blocking traffic between the originating computing device and the destination computing device.

18. The method of claim 16, wherein the routing operation involves providing, from the intermediation server to the originating computing device, a notification interrupt for inserting a notification page.

19. The method of claim 16, wherein the routing operation involves anonymizing the originating computing device.

20. A non-transitory computer readable medium encoded with codes, the codes for directing a processor to:

receive a profile record for an originating computing device;

receive a destination identifier from the originating computing device, the destination identifier associated with a destination computing device;

determine if the destination identifier is associated with the profile record;

return an assigned query result to the originating computing device when the destination identifier is associated with the profile record; and

return a default query result to the originating computing device when the destination identifier is not associated with the profile record.