PRIVATE CLOUD TOPOLOGY MANAGEMENT SYSTEM

• US 20150052247A1
• Filed: 08/14/2013
• Published: 02/19/2015
• Est. Priority Date: 08/14/2013
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Threefoot, Matthew John, Sender, Thierry R.
• Granted Patent: US 9,338,223 B2
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A device configured to receive network topological information from devices in a private Internet Protocol (PIP) network receive network performance data from the devices; receive service topological information from a cloud; receive service performance data from the cloud; receive policies for determining optimum routes to the cloud from an administration device; apply the policies to the network topological information from the devices, the network performance data, the service topological information, and the service performance data to obtain routing rules; and forward the routing rules to a set of request routers.

Claims

1. A system comprising:

a topology manager to;

receive network topological information from devices in a private Internet Protocol (PIP) network;

receive network performance data from the devices;

receive service topological information from a cloud;

receive service performance data from the cloud;

receive policies for determining optimum routes to the cloud from an administration device;

apply the policies to the network topological information from the devices, the network performance data, the service topological information, and the service performance data to obtain routing rules; and

forward the routing rules to a set of request routers.

2. The system of claim 1, further comprising the request routers,

wherein the request routers are configured to:

receive the routing rules from the topology manager;

receive a request for a path to the cloud from a user device;

in response to the request, send a message indicating a path to the cloud or recommending another cloud.

3. The system of claim 2, wherein the user device is connected to the PIP network via one of:

a wireless link;

one or more tunnels;

or

a partner network to the PIP network.

4. The system of claim 2, wherein the message includes:

an address of the cloud;

or

an address of the other cloud.

5. The system of claim 2, wherein the message includes:

a hypertext transfer protocol (HTTP) 302 redirect response.

6. The system of claim 2, wherein the network topological information indicates at least one of:

a star topology;

a tree topology;

or

a fully-meshed topology.

7. The system of claim 1, wherein the network performance information includes:

for each of the routers, network traffic for each of differentiated service point (DSCP) markings for different classes of data.

8. The system of claim 7, wherein the different types of data include:

voice data and real-time data that correspond to expedited forwarding markings of the DSCP;

video data and priority data, of high priority, that correspond to assured forwarding 41 of the DSCP; and

video data and priority data, of low priority, that correspond to assured forwarding 42/43 of the DSCP.

9. The system of claim 1, wherein the topology manager is configured to:

receive a request for cloud information from the administration device; and

provide a report in response to the request to the administration device.

10. The system of claim 1, wherein the cloud provides at least one of:

a Software-as-a-Service (SaaS);

a Platform-as-a-Service (PaaS);

or

an Infrastructure-as-a-Service (IaaS).

11. The system of claim 1, wherein the request routers are configured to forward address information to an intermediate device, wherein the intermediate device includes at least one of:

a DNS server device;

or

a host device that includes a web server.

12. A method comprising:

receiving network topological information from devices not in a private Internet Protocol (PIP) network;

receiving network performance data from the devices;

receiving service topological information from a cloud;

receiving service performance data from the cloud;

receiving policies for determining optimum routes to the cloud from an administration device;

applying the policies to the network topological information from the devices, the network performance data, the service topological information, and the service performance data to obtain routing rules; and

forwarding the routing rules to a set of request routers.

13. The method of claim 12, further comprising:

receiving a list of clouds from the administration device, wherein the list of clouds includes an identifier for the cloud; and

wherein the policies include policies for selecting one of the clouds.

14. The method of claim 13, further comprising:

receiving configuration information for collecting network data; and

sending the configuration information to the devices.

15. The method of claim 14, wherein the network performance data includes:

simple network management protocol (SNMP) data.

16. The method of claim 15, wherein the network topological information and service topological information include one or more of:

a virtual private network (VPN) topology map;

a multiprotocol label switched (MPLS) network topology map;

an autonomous system (AS) topology map;

a global topology map of clouds;

or

a topology map of a cloud for a particular service.

17. The method of claim 12, wherein the network performance data and the service performance data include at least one of:

aggregated traffic load on networks or virtual networks;

traffic loads between cloud devices;

load conditions on each of cloud devices;

bandwidth consumption of cloud traffic per each of differentiated services code point (DSCP) classes.

18. A device comprising:

a network interface to communicate with devices not in a private Internet Protocol (PIP) network and to communicate with a cloud;

a memory to store instructions; and

one or more processors to execute the instructions to;

receive network topological information from the devices via the network interface;

receive network performance data from the devices;

receive service topological information from the cloud;

receive service performance data from the cloud;

receive policies for determining optimum routes to the cloud from an administration device;

apply the policies to the network topological information from the devices, the network performance data, the service topological information, and the service performance data to obtain routing rules; and

forward the routing rules to a set of request routers.

19. The device of claim 18, wherein the request routers are configured to:

receive the routing rules from the topology manager;

receive a request for a path to the cloud from a user device;

in response to the request, send a message indicating a path to the cloud or recommending another cloud.

20. The device of claim 19, wherein the user device is connected to the PIP network via one of:

a wireless link;

one or more tunnels;

or

a partner network to the PIP network.