US 12,438,794 B2
Determining an end user experience score based on client device, network, server device, and application metrics
Steve Cohen, Chanhassen, MN (US)
Assigned to VIAVI Solutions Inc., Chandler, AZ (US)
Filed by VIAVI Solutions Inc., Chandler, AZ (US)
Filed on Mar. 21, 2024, as Appl. No. 18/611,776.
Application 18/611,776 is a continuation of application No. 17/648,021, filed on Jan. 14, 2022, granted, now 11,985,053.
Application 17/648,021 is a continuation in part of application No. 17/303,157, filed on May 21, 2021, granted, now 12,113,691.
Application 17/303,157 is a continuation of application No. 15/940,278, filed on Mar. 29, 2018, granted, now 11,018,967, issued on May 25, 2021.
Prior Publication US 2024/0235973 A1, Jul. 11, 2024
Int. Cl. H04L 43/08 (2022.01); H04L 43/04 (2022.01); H04L 43/065 (2022.01); H04L 43/0864 (2022.01); H04L 67/50 (2022.01)
CPC H04L 43/0864 (2013.01) [H04L 43/04 (2013.01); H04L 43/065 (2013.01); H04L 67/535 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A system, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to cause the system to:
receive, from network probes, one or more of:
first metrics that indicate delay experienced at a client device,
second metrics that indicate delay experienced in a network, or
third metrics that indicate delay experienced at one or more of an application or a server device;
receive one or more minimum round trip time (RTT) alarms from one or more of a client uniform resource locator (cURL) service, a ping service, a traceroute service, a multi-step web service, or another type of service;
utilize a machine learning model to determine one or more active delay scores based on one or more of the first metrics that indicate delay experienced at the client device, the second metrics that indicate delay experienced in the network, or the third metrics that indicate delay experienced at one or more of the application or the server device and based on a minimum RTT alarm of the one or more minimum RTT alarms;
determine one or more passive delay scores based on one or more of the first metrics that indicate delay experienced at the client device, the second metrics that indicate delay experienced in the network, or the third metrics that indicate delay experienced at one or more of the application or the server device; and
cause, based on the one or more active delay scores and the one or more passive delay scores, one or more actions to be performed with regard to one or more of an end user experience at the client device, one or more network devices in the network, the application, or the server device.