# US 2020/0287816 A1 · System and method for using real-time packet data to detect and manage network issues

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

- Number: US 2020/0287816 A1
- Document ID: US20200287816A1
- Status: Published application
- Kind: A1
- Application number: 16/821,957
- Filed: 2020-03-17
- Published: 2020-09-10
- Earliest claimed: 2016-04-18
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Balachander Chandrasekaran; Anand Srinivas; Murtaza Zafer
- Web page: https://patentgrep.com/patent/US20200287816A1

## CPC

- H04L 43/0882: Utilisation of link capacity
- H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L 41/142: using statistical or mathematical methods
- H04L 43/0811: by checking connectivity
- H04L 43/16: Threshold monitoring
- H04L 47/11: Identifying congestion
- H04L 47/28: in relation to timing considerations
- H04L 61/103: across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
- H04L 61/4511: using domain name system [DNS]
- H04W 8/02: Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04L 43/0817: by checking functioning
- H04L 43/0829: Packet loss
- H04L 43/0852: Delays
- H04L 61/4523: using lightweight directory access protocol [LDAP]
- H04L 61/5014: using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A system and method is disclosed of extracting information from real-time network packet data to analyze connectivity data for client devices in a network. The method includes: detecting when client devices initiate a connectivity event; after detecting a connectivity event, waiting a period of time for the client device to either reach or fail to reach a network connected state; after waiting a period of time, recording connectivity event information; and sending the recorded connectivity event information to an analytics system for network incident and/or network congestion analysis.

## Claims

### Claim at position 1

1-25. (canceled)

### Claim 26

A method for analyzing and remediating network incidents, the method comprising:
executing performance calculations on collected network data to compute performance metrics;
detecting a network incident from the performance calculations on the network data by correlating a sequence of performance metrics with other composite metrics that define relevant symptoms;
identifying a root cause of the detected network incident; and
identifying, and providing for display, remediation of the identified root cause of the detected network incident.

### Claim 27 (depends on 26)

The method of claim 26, wherein identifying the root cause comprises aggregating correlations of symptoms across a plurality of network incidents over a duration of time, and mapping a set of symptom correlations to root causes.

### Claim 28 (depends on 27)

The method of claim 27, wherein the detected incident comprises a network infrastructure incident relating to one or more network infrastructure elements, and the plurality of network incidents comprise a plurality of network infrastructure incidents relating to a plurality of sets of network infrastructure elements.

### Claim 29 (depends on 27)

The method of claim 27, wherein the detected incident comprises a client network incident relating to a particular client, and the plurality of network incidents comprise a plurality of client network incidents relating to a plurality of clients.

### Claim 30 (depends on 29)

The method of claim 29, wherein each client in a set of clients is a company, and detecting the network incident comprising performing cross-company comparison of network incidents among similar companies.

### Claim 31 (depends on 30)

The method of claim 30, further comprising identifying a similar plurality of companies to place in the set of companies based on a plurality of network factors including at least three of a number of wired/wireless clients, a number of access points, types of devices, types of network elements, a density of network deployment, a topology of network deployment, and geographical locations.

### Claim 32 (depends on 26)

The method of claim 26, wherein detecting the network incident comprising at least one of detecting a proportion of performance metric values crossing a threshold, detecting a presence of a sequence of metric values, detecting a time-ordered stretch of metric values with a length of the time-ordered stretch exceeding a defined threshold, and detecting a cyclical presence of a sequence of metric values.

### Claim 33 (depends on 26)

The method of claim 26, wherein detecting the network incident comprises identifying deviations in historical time-series data computed based on network incidents over a duration of time.

### Claim 34 (depends on 33)

The method of claim 33 further comprising identifying changes in the computed historical time-series data and identifying factors contributing to these changes, wherein the identifying factors comprise at least two of configuration changes, topology changes, changes and upgrades of the network elements in the network.

### Claim 35 (depends on 26)

The method of claim 26, wherein identifying remediation comprises assigning a priority to the detected network incident, wherein the priority is determined based on at least two of a percentage of affected entities, relative deviation from the historical baseline, presence of important entities within the affected entities.

### Claim 36

A non-transitory machine readable medium storing a program which when executed by at least one processing unit analyzes and remediates network incidents, the program comprising sets of instructions for:
executing performance calculations on collected network data to compute performance metrics;
detecting a network incident from the performance calculations on the network data by correlating a sequence of performance metrics with other composite metrics that define relevant symptoms;
identifying a root cause of the detected network incident; and
identifying, and providing for display, remediation of the identified root cause of the detected network incident.

### Claim 37 (depends on 36)

The non-transitory machine readable medium of claim 36, wherein the set of instructions for identifying the root cause comprises sets of instructions for aggregating correlations of symptoms across a plurality of network incidents over a duration of time, and mapping a set of symptom correlations to root causes.

### Claim 38 (depends on 37)

The non-transitory machine readable medium of claim 37, wherein the detected incident comprises a network infrastructure incident relating to one or more network infrastructure elements, and the plurality of network incidents comprise a plurality of network infrastructure incidents relating to a plurality of sets of network infrastructure elements.

### Claim 39 (depends on 37)

The non-transitory machine readable medium of claim 37, wherein the detected incident comprises a client network incident relating to a particular client, and the plurality of network incidents comprise a plurality of client network incidents relating to a plurality of clients.

### Claim 40 (depends on 39)

The non-transitory machine readable medium of claim 39, wherein each client in a set of clients is a company, and the set of instructions for detecting the network incident comprises a set of instructions for performing cross-company comparison of network incidents among similar companies.

### Claim 41 (depends on 40)

The non-transitory machine readable medium of claim 40, wherein the set of instructions for detecting the network incident further comprises a set of instructions for identifying a similar plurality of companies to place in the set of companies based on a plurality of network factors including at least three of a number of wired/wireless clients, a number of access points, types of devices, types of network elements, a density of network deployment, a topology of network deployment, and geographical locations.

### Claim 42 (depends on 36)

The non-transitory machine readable medium of claim 36, wherein the set of instructions for detecting the network incident comprises sets of instructions for at least one of detecting a proportion of performance metric values crossing a threshold, detecting a presence of a sequence of metric values, detecting a time-ordered stretch of metric values with a length of the time-ordered stretch exceeding a defined threshold, and detecting a cyclical presence of a sequence of metric values.

### Claim 43 (depends on 36)

The non-transitory machine readable medium of claim 36, wherein the set of instructions for detecting the network incident comprises a set of instructions for identifying deviations in historical time-series data computed based on network incidents over a duration of time.

### Claim 44 (depends on 43)

The non-transitory machine readable medium of claim 43, wherein the set of instructions for detecting the network incident further comprises sets of instructions for identifying changes in the computed historical time-series data and identifying factors contributing to these changes, wherein the set of instructions for identifying factors comprises at least two of configuration changes, topology changes, changes and upgrades of the network elements in the network.

### Claim 45 (depends on 36)

The non-transitory machine readable medium of claim 36, wherein the set of instructions for identifying remediation comprises a set of instructions for assigning a priority to the detected network incident, wherein the priority is determined based on at least two of a percentage of affected entities, relative deviation from the historical baseline, presence of important entities within the affected entities.
