REAL-TIME ADAPTIVE PROCESSSING OF NETWORK DATA PACKETS FOR ANALYSIS

• US 20170264506A1
• Filed: 05/23/2017
• Published: 09/14/2017
• Est. Priority Date: 04/08/2010
• Status: Active Grant

• Current Assignee: NetScout Systems Incorporated
• Original Assignee: NetScout Systems Incorporated
• Inventors: Singhal, Anil K., Kelley, JR., Bruce A., Nadkarni, Rajeev, Byrapuram, Narendra, Saraswati, Abhishek, Singhal, Ashwani
• Granted Patent: US 10,284,440 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/026 using flow identification
• CPC Class Codes: H04L 43/028 by filtering
• CPC Class Codes: H04L 43/062 related to network traffic
• 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/0829 Packet loss
• CPC Class Codes: H04L 43/087 Jitter
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A network monitoring system that summarizes a plurality of data packets of a session into a compact session record for storage and processing. Each session record may be produced in real-time and made available during the session and/or after the termination of the session. Depending on protocols, a network monitoring system extracts different sets of information, removes redundant information from the plurality of data packets, and adds performance information to produce the session record. The network monitoring system may retrieve and process a single session record or multiple session records for the same or different protocols to determine cause of events, resolve issues in a network or evaluate network performance or conditions. The session record enables analysis in the units of session instead of individual packets. Hence, the network monitoring system can analyze events, issues or performance of the network more efficiently and effectively.

Claims

1-20. -20. (canceled)

21. A method, comprising:

determining first and second sessions associated with data packets received by a network monitoring device at a location in a network;

generating a common header summarizing information in headers of a plurality of data packets in each of the first and second sessions by the network monitoring device; and

generating, for each first and session, a session record for respectively storing the common header of the first and second session, and storing mapping information representing association of the first session with the second session when the first and second sessions are associated with planes in a same protocol.

22. The method as recited in claim 21, further including generating a unit of payload metadata summarizing information in payloads of the plurality of the data packets in each of the first and second session by the network monitoring device wherein the generating step further includes storing the payload metadata of each of the first and second session respectively in the session record for each first and second session.

23. The method of claim 22, further comprising determining a protocol associated with each of the first and second session, information included in the common header or the payload metadata of each first and second session is respectively determined based on a protocol associated with the first and second session.

24. The method of claim 22, wherein the common header and the payload metadata are generated in real-time responsive to receiving data packets for each of the first and second session from the network.

25. The method of claim 21, further comprising:

generating performance parameters representing performance of the network for transmitting the plurality of the data packets in each of the first and second sessions; and

adding the performance parameters of the first and seconds sessions respectively in the first and second session record.

26. The method of claim 25, wherein the performance parameters comprise at least one of a packet loss rate, a response time, a number of packets or bytes transmitted, parameters indicative of transmission latency, codec parameters, total transfer time for the session, R-Factor (rating factor), MOS (Mean Opinion Score), a file or page size, a file name, sender/receive information, a total transfer time, a user ID, jitter, and phone number.

27. The method of claim 21, wherein the first session is associated with a first protocol and the second session is associated with a second protocol different than the first protocol.

28. The method of claim 21, wherein each first and second session record further stores links to the plurality of the data packets respectively in each of the first and second sessions.

29. The method of claim 21, wherein the common header comprises fields of the headers that remain unchanged throughout each respective first and second session.

30. A network monitoring device for processing network data for analysis, comprising:

a network interface configured to receive data packets at a location in a network; and

a session tracing engine configured to;

determine first and second sessions associated with data packets received by a network monitoring device at a location in a network;

generate a common header summarizing information in headers of a plurality of data packets in each of the first and second sessions by the network monitoring device; and

generate, for each first and session, a session record for respectively storing the common header of the first and second session, and storing mapping information representing association of the first session with the second session when the first and second sessions are associated with planes in a same protocol.

31. The network monitoring device as recited in claim 30, wherein the session tracing engine is further configured to generate a unit of payload metadata summarizing information in payloads of the plurality of the data packets in each of the first and second session by the network monitoring device wherein the generating step further includes storing the payload metadata of each of the first and second session respectively in the session record for each first and second session.

32. The network monitoring device as recited in claim 31, wherein the session tracing engine is further configured to determine a protocol associated with each of the first and second session, information included in the common header or the payload metadata of each first and second session is respectively determined based on a protocol associated with the first and second session.

33. The network monitoring device as recited in claim 31, wherein the common header and the payload metadata are generated in real-time responsive to receiving data packets for each of the first and second session from the network.

34. The network monitoring device as recited in claim 30, wherein the session tracing engine is further configured to:

generate performance parameters representing performance of the network for transmitting the plurality of the data packets in each of the first and second sessions; and

add the performance parameters of the first and seconds sessions respectively in the first and second session record.

35. The network monitoring device as recited in claim 34, wherein the performance parameters comprise at least one of a packet loss rate, a response time, a number of packets or bytes transmitted, parameters indicative of transmission latency, codec parameters, total transfer time for the session, R-Factor (rating factor), MOS (Mean Opinion Score), a file or page size, a file name, sender/receive information, a total transfer time, a user ID, jitter, and phone number.

36. The network monitoring device as recited in claim 30, wherein the first session is associated with a first protocol and the second session is associated with a second protocol different than the first protocol.

37. The network monitoring device as recited in claim 31, wherein each first and second session record further stores links to the plurality of the data packets respectively in each of the first and second sessions.

38. The network monitoring device as recited in claim 30, wherein the common header comprises fields of the headers that remain unchanged throughout each respective first and second session.