# US 10,374,900 B2 · Updating a virtual network topology based on monitored application data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,374,900 B2
- Document ID: US10374900B2
- Status: Granted
- Kind: B2
- Application number: 15/500,039
- Filed: 2015-03-16
- Published: 2017-08-24
- Granted: 2019-08-06
- Earliest claimed: 2014-12-03
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Yogesh Dujodwala; Sunil Gurumallesha
- Web page: https://patentgrep.com/patent/US10374900B2

## CPC

- H04L 41/0896: Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76)
- H04L 12/42: Loop networks
- H04L 41/0213: Standardised network management protocols, e.g. simple network management protocol [SNMP]
- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 41/147: for predicting network behaviour
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 41/5096: {wherein the managed service relates to distributed or central networked applications}
- H04L 43/0882: Utilisation of link capacity
- H04L 43/16: Threshold monitoring
- H04L 47/22: Traffic shaping
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In some examples, data traffic over a virtual network can be monitored for an application. An existing topology for the virtual network can be updated based on the monitored data. The updated topology can, for example, be determined to better handle predicted data traffic for the application. The topology of the virtual network can then be updated to achieve the determined updated virtual network topology.

## Claims

### Claim 1

A system comprising:
a processing resource; and
a memory resource storing non-transitory machine-readable instructions to cause the processing resource to:
determine historical data trends for application data traffic monitored over a virtualized routing infrastructure having a plurality of nodes in a network;
determine an updated virtual network topology for the virtualized routing infrastructure based on the determined historical data trends by identifying that virtual routing paths should be added to the virtualized routing infrastructure to accommodate a predicted increase in traffic load over the virtualized routing infrastructure above a predetermined threshold; and
automatically scale the virtualized routing infrastructure to achieve the determined updated virtual network topology by implementing Link Aggregation (LAG) via a node of the plurality of nodes such that the LAG node determines a link to route a packet downstream on the network, wherein the determination is based on packet metadata of the packet.

### Claim 2 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to determine an updated virtual network topology that includes additional virtual routing paths by indicating that a virtual network switch should be added to the virtualized routing infrastructure.

### Claim 3 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to determine an updated virtual network topology that includes additional virtual routing paths by indicating that an additional network connection should be added between previously connected network nodes.

### Claim 4 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to determine that virtual routing paths should be removed from the virtualized routing infrastructure to accommodate a predicted decrease in traffic load over the virtualized routing infrastructure above a predetermined threshold.

### Claim 5 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to determine historical data trends based on network throughput over the virtualized routing infrastructure for application data traffic.

### Claim 6 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to determine historical data trends based on network resiliency over the virtualized routing infrastructure for application data traffic.

### Claim 7 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to determine an updated network topology for the virtualized routing infrastructure to achieve a predetermined Quality of Service (QoS) for application data traffic over the network.

### Claim 8 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to receive data from a monitoring application installed on a network device within the virtualized routing infrastructure to determine historical data trends for application data traffic.

### Claim 9 (depends on 1)

The system of claim 1, including instructions to cause the processing resource to receive data via Simple Network Management Protocol (SNMP) to determine historical data trends for application data traffic.

### Claim 10 (depends on 1)

The system of claim 1, wherein the network is a cloud network and the virtualized routing infrastructure and the application are hosted in the cloud network.

### Claim 11

A method comprising:
monitoring application data traffic for a predetermined software application routed through a virtual network infrastructure having a plurality of nodes in a network;
determining historical data trends for the monitored application data traffic;
determining, based on the historical data trends, an updated virtual network topology that is to better handle predicted data traffic for the predetermined software application by identifying that virtual routing paths should be added to the virtual network infrastructure to accommodate a predicted increase in traffic load over the virtual network infrastructure above a predetermined threshold; and
automatically scaling the virtual network infrastructure to achieve the determined updated virtual network topology by implementing Link Aggregation (LAG) via a node of the plurality of nodes such that the LAG node determines a link to route a packet downstream on the network, wherein the determination is based on packet metadata of the packet.

### Claim 12 (depends on 11)

The method of claim 11, wherein the data traffic monitoring is performed by a virtual network switch within the network.

### Claim 13 (depends on 11)

The method of claim 11, wherein the data traffic monitoring is performed by a hardware network switch within the network.

### Claim 14

A memory resource storing non-transitory machine-readable instructions that when executed causes a processing resource to implement a virtual network topology updating system, the instructions comprising:
a data traffic monitoring module that, when executed, causes the processing resource to monitor data traffic over a virtual network having a plurality of nodes for a software application;
a historical trend module that, when executed, causes the processing resource to determine historical trends in the monitored data traffic;
a network topology determination module that, when executed, causes the processing resource to determine, based on the determined historical trends, an updated virtual network topology for the virtual network by identifying that virtual routing paths should be added to the virtual network to accommodate a predicted increase in traffic load over the virtual network above a predetermined threshold to improve network performance of the software application; and
a network topology update module that, when executed, causes the processing resource to automatically scale the topology of the virtual network to achieve the determined updated virtual network topology by implementing Link Aggregation (LAG) via a node of the plurality of nodes such that the LAG node determines a link to a packet downstream on the virtual network, wherein the determination is based on packet metadata of the packet.