IP Library Granted Patent US 10,230,609
Granted Patent B2
US 10,230,609 · App. 15/132,057 · Granted Mar 12, 2019

System and method for using real-time packet data to detect and manage network issues

Inventors: Balachander Chandrasekaran (San Ramon, CA); Anand Srinivas (San Francisco, CA); Murtaza Zafer (San Jose, CA)
Assignee: Nyansa, Inc.
H04L43/0882H04L43/0811H04L47/28H04L61/103H04L61/1511H04W8/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,230,609
App. No.
15/132,057
Granted
Mar 12, 2019
Kind
B2
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 (35)

1. A method of extracting information from real-time network data to analyze connectivity data for client devices in a network, the method comprising:

detecting when the 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;

sending the recorded connectivity event information to an analytics system for network incident and network congestion analysis;

analyzing, via a remote network manager, (1) the network traffic data from a plurality of network elements in a network and (2) network management data from an enterprise system in the network, wherein the network management data includes L1 through L7 network topology data, network configuration data, and simple network management protocol data;

detecting network incidents from the connectivity event information on the real-time network data and the analysis of the network traffic data and network management data;

identifying one or more root causes of the detected network incidents; and

determining remediation of the identified one or more root causes of the detected network incidents.

2. The method of claim 1 , wherein the connectivity event comprises a connectivity event determined by looking for a Remote Authentication Dial-In User Service (RADIUS) request, Dynamic Host Configuration Protocol (DHCP) discover message, or DHCP request message.

3. The method of claim 1 , wherein a network connected state comprises the client device authenticated with the network, having a valid IP address, and being able to communicate with internal or external computer hosts.

4. The method of claim 3 , wherein being able to communicate with internal and external computer hosts includes data traffic transmitted either to a public IP address, or to a network subnet using any Transport Layer protocol such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Real-time Transport Protocol (RTP), Secure Real-time Transport Protocol (SRTP) and File Transfer Protocol (FTP) protocol.

5. The method of claim 1 , wherein connectivity event information includes one or more of: RADIUS last state, DHCP last state, ARP (Address Resolution Protocol) last state with respect to default gateway, DNS (Domain Name Server) response, and communication with internal or external computer hosts.

6. The method of claim 5 , wherein a RADIUS last state includes one or more of failed, success, and timeout.

7. The method of claim 5 , wherein a DHCP last state includes one or more of Offer, Acknowledge, and Negative Acknowledgement, timeout.

8. The method of claim 5 , wherein an ARP last state with respect to default gateway includes one or more of response and timeout.

9. The method of claim 5 , wherein a DNS last state includes one or more of response and timeout.

10. The method of claim 1 , wherein the analytics system computes baseline time-series from the computed network incidents and compares baselines across multiple environments.

11. The method of claim 1 , wherein the real-time network data includes one or more of: data obtained from deep packet analysis of real-time network traffic, data from network elements including wireless controllers, access points, on-premise network systems, and system logs.

12. The method of claim 1 , wherein the real-time network data includes: device information OS (Operating System) information, wireless metrics, Layer 2 through Layer 4 information, network services related Layer 7 information, Layer 5 through Layer 7 information, and application related data.

13. The method of claim 12 , wherein the wireless metrics include one or more of SNR (signal to noise ratio), packet loss, packet retransmits, connected access points, channel utilization at the access points, neighboring access points information, outside-network access points information, interference information in the RF (Radio Frequency) bands, network topology information, CPU (Central Processing Unit) utilization, memory-utilization, configuration of wireless controllers, and configuration of access points.

14. The method of claim 12 , wherein Layer 2 through Layer 4 information includes one or more of VLAN (Virtual Local Area Network) data, receive packets, transmit packets, DSCP (Differentiated Services Code Point) data, TCP (transmission control protocol) related data, UDP (User Datagram Protocol) related data, RTP (Real-time Transport Protocol) related data, SRTP (Secure Real-time Transport Protocol) related data, and FTP (File Transfer Protocol) protocol related data.

15. The method of claim 12 , wherein network services related Layer 7 information includes one or more of DHCP (Dynamic Host Configuration Protocol), DNS (Domain Name System), RADIUS (Remote Authentication Dial-In User Service) protocol information, request times, response times, and failure codes.

16. The method of claim 12 , wherein Layer 5 through Layer 7 information includes one or more of SSL (Secure Sockets Layer) Certificate, hostnames, and HTTP (Hypertext Transfer Protocol) response times.

17. The method of claim 12 , wherein the real-time network data is pulled from on-premise systems and includes one or more of Netflow records, Sflow records, SNMP (Simple Network Management Protocol) records from routers, switches, and network elements.

18. A method of extracting information from real-time network data to analyze connectivity data for client devices in a network, the method comprising:

detecting when the 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;

sending the recorded connectivity event information to an analytics system for network incident and/or network congestion analysis;

analyzing, via a remote network manager, (1) the network traffic data from a plurality of network elements in a network and (2) network management data from an enterprise system in the network, wherein the network management data includes L1 through L7 network topology data, network configuration data, and simple network management protocol data;

detecting network incidents from the connectivity event information on the real-time network data and the analysis of the network traffic data and network management data;

identifying one or more root causes of the detected network incidents; and

determining remediation of the identified one or more root causes of the detected network incidents; and

automatically implementing the determined remediation, wherein the remediation of the network incidents comprises programming, via a controller, configuration settings of network infrastructure including one or more of wireless LAN (Local Area Network) controllers, access points, switches, routers, and firewalls.

Assignments (3)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
NUNC PRO TUNC ASSIGNMENT Recorded May 13, 2020
From: NYANSA, INC.
To: VMWARE, INC.
Reel/Frame 052655/0218 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 5, 2016
From: CHANDRASEKARAN, BALACHANDER; SRINIVAS, ANAND; ZAFER, MURTAZA
To: NYANSA, INC.
Reel/Frame 039599/0556 →
Continuity (1)
Related Publication 20170302554A1 · Oct 19, 2017
Cited By (2)
US 12,388,713 US 12,580,840