Establishing nodes for global routing manager

• US 10,063,419 B2
• Filed: 10/31/2015
• Issued: 08/28/2018
• Est. Priority Date: 10/31/2015
• Status: Active Grant

• Current Assignee: Skyhigh Security LLC
• Original Assignee: McAfee, LLC
• Inventors: Horstmann, Ralf, Kendzorra, Juergen, Madikonda, Pavan Kumar, Stein, Andre, Stecher, Martin
• Primary Examiner(s): Whipple, Brian
• Application Number:
  US14/929,277
• Publication Number:
  US 20170126502A1
• Time in Patent Office: 1,032 Days
• Field of Search: None
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1021 based on client or server locations

Abstract

Embodiments of the present disclosure include an Orchestrator to commission a point of presence (PoP) node based on receiving an internet protocol (IP) address, the IP address associated with a geographic location; and a global routing manager for assigning a client device to a PoP node based on the received IP address. Embodiments also include a performance manager to acquire performance information about each PoP node.

Claims

1. A system comprising:

at least one processor device;

at least one memory element;

an orchestrator to commission on-demand a new point of presence (PoP) node based, at least in part, on receiving an internet protocol (IP) address, the IP address associated with a geographic location; and

a global routing manager to assign a client device to the PoP node based on the received IP address;

further comprising

a performance manager to acquire performance information about each PoP node of a plurality of PoP nodes in the geographic location, wherein the performance information includes load information;

wherein

the global routing manager uses the load information from the performance manager to cause the orchestrator to commission the new POP node based at least in part on the load information; and

wherein

the global routing manager uses the load information from the performance manager to reassign the client device to the new PoP node for load balancing.

2. The system of claim 1, wherein the global routing manager uses the load information to determine that the PoP node is overloaded and to make a request to the orchestrator to commission a new PoP node in the geographic location, and wherein the orchestrator commissions the new PoP node based on a request from the global routing manager and the load information from the performance manager.

3. The system of claim 1, wherein the global routing manager assigns the client device to the PoP node based on a policy or preference associated with the client device.

4. The system of claim 3, wherein the global routing manager identifies the PoP node based on a proxy request made on behalf of the client device, the proxy request comprising the IP address, and wherein the global routing manager assigns an outbound IP address to the client device based on the geolocation of the PoP node.

5. The system of claim 3, wherein the policy or preference associated with the client device comprises assigning to the client device an outbound IP address geolocated within a home area of the client device.

6. The system of claim 3, wherein the policy or preference associated with the client device comprises assigning to the client device an outbound IP address geolocated in an area proximate the PoP node.

7. The system of claim 3, wherein the policy or preference associated with the client device comprises assigning to the client device the PoP node based upon the PoP node having a specified minimum quality of service.

8. The system of claim 3, further comprising

one or more sensor nodes, the sensor nodes to monitor each PoP node of a plurality of PoP nodes and provide information to the performance manager, the information comprising one or more of load information, quality of service, latency, or throughput.

9. The system of claim 1, wherein the orchestrator coordinates between PoP nodes associated with a customer to facilitate handoff between PoP nodes associated with the customer.

10. The system of claim 1, wherein the PoP nodes handoff clients based on load balancing requirements, service offerings, or both.

11. At least one non-transitory, machine accessible storage medium having instructions stored thereon, the instructions, when executed on a machine, cause the machine to:

commission on demand, by an orchestrator implemented at least partially in hardware, a new point of presence (PoP) node based on receiving an internet protocol (IP) address, the IP address associated with a geographic location; and

assigning, by a global routing manager implemented at least partially in hardware, a client device to the PoP node based on the received IP address;

wherein

the instructions are further operable, when executed, to acquire, by a performance manager implemented at least partially in hardware, load information about each PoP node of a plurality of PoP nodes, wherein

the instructions are further operable, when executed, to cause the orchestrator, by the global routing manager, to commission on demand the new PoP node based on the load information; and

wherein

the instructions are further operable, when executed, to reassign, by the global routing manager, the client device to the new PoP node for load balancing based on the load information.

12. The at least one machine accessible storage medium of claim 11, wherein the instructions further cause a machine to commission the PoP node based on a load balancing between one or more PoP nodes associated with the geographic location.

13. The at least one machine accessible storage medium of claim 11, wherein the instructions are further operable when executed to determine, by the performance manager, that the PoP node is overloaded based on the load information and request commissioning of a new PoP node in the geographic location.

14. The at least one machine accessible storage medium of claim 11, wherein the instructions are further operable when executed to assign, by the global routing manager, the client device to the PoP node based on a policy or preference associated with the client device.

15. The at least one machine accessible storage medium of claim 11, wherein the instructions are further operable when executed to coordinate, by the global routing manager, between PoP nodes associated with a customer to facilitate handoff between PoP nodes associated with the customer.

16. A method comprising:

receiving, at a global routing manager implemented at least partially in hardware, a proxy request from a client device, the proxy request comprising an Internet Protocol (IP) address from the client device;

identifying, by the global routing manager, a point of presence node (PoP node) in a location based on the received IP address;

assigning, by the global routing manager, the client device to the identified PoP node;

the method further comprising;

receiving, by a performance manager implemented at least partially in hardware, load information about one or more PoP nodes;

assigning, by the global routing manager, PoP nodes to the client device based on the load information about the one or more PoP nodes;

determining, by the performance manager, that a PoP node is overloaded based on the received load information; and

reassigning the client device to a new PoP node in a same geographic location of the overloaded PoP node.

17. The method of claim 16, further comprising

assigning, by the global routing manager, the client device to the PoP node based on a policy or preference associated with the client device.

18. The method of claim 17, wherein the policy or preference associated with the client device comprises assigning, by the global routing manager, to the client device an outbound IP address geolocated within a home area of the client device.

19. The method of claim 18, wherein the policy or preference associated with the client device comprises assigning, by the global routing manager, to the client device an outbound IP address geolocated in an area proximate the PoP node.

20. The method of claim 18, wherein the policy or preference associated with the client device comprises assigning, by the global routing manager, to the client device a PoP node based on the PoP node having a specified minimum quality of service.