# US 2023/0155910 A1 · Latency diagnostics for multiparty systems

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

- Number: US 2023/0155910 A1
- Document ID: US20230155910A1
- Status: Published application
- Kind: A1
- Application number: 17/454,686
- Filed: 2021-11-12
- Published: 2023-05-18
- Earliest claimed: 2021-11-12
- Assignees: AT&T Intellectual Property I, L.P.
- Applicants: AT & T Intellectual Property I, L.P.
- Inventors: Xiaowen Mang; Carolyn Johnson; Gregory Smith
- Web page: https://patentgrep.com/patent/US20230155910A1

## CPC

- H04L 43/0829: Packet loss
- H04L 43/0864: Round trip delays
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 41/5067: Customer-centric QoS measurements
- H04L 43/067: using time frame reporting
- H04L 43/0817: by checking functioning
- H04L 43/0852: Delays
- H04L 43/0894: Packet rate
- H04L 43/16: Threshold monitoring
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The described technology is generally directed towards latency diagnostics for multiparty systems, such as a system comprising a communication network, a content delivery network (CDN), and one or more internet service providers (ISPs). A latency analyzer component can process latency data in response to a latency diagnostic trigger, such as an alert from a video quality monitoring system. The latency analyzer can determine whether latency is attributable to the communication network. If not, the latency analyzer can determine whether the latency is attributable to the CDN. If the latency is not attributable to the communication network or the CDN, the latency analyzer can determine that the latency is attributable to the ISP, and the latency analyzer can identify the ISP and generate appropriate reports and notifications.

## Claims

### Claim 1

A method, comprising:
receiving, by network equipment comprising a processor, a latency diagnostic trigger;
in response to receiving the latency diagnostic trigger, first determining, by the network equipment, whether a latency associated with the latency diagnostic trigger is attributable to a first group of network equipment, wherein the first determining whether the latency is attributable to the first group of network equipment comprises querying a network monitoring system to obtain latency and loss statistics associated with a time window comprising the latency associated with the latency diagnostic trigger;
in response to a result of the first determining being that the latency associated with the latency diagnostic trigger is not attributable to the first group of network equipment, second determining, by the network equipment, whether the latency associated with the latency diagnostic trigger is attributable to a second group of network equipment; and
in response to a result of the second determining being that the latency associated with the latency diagnostic trigger is not attributable to the second group of network equipment, third determining, by the network equipment, that the latency associated with the latency diagnostic trigger is attributable to a third group of network equipment.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first group of network equipment comprises equipment of a communication network comprising the network equipment.

### Claim 3 (depends on 1)

The method of claim 1, wherein the second group of network equipment comprises equipment of a content delivery network.

### Claim 4 (depends on 1)

The method of claim 1, wherein the second group of network equipment comprises first content delivery network equipment and second content delivery network equipment, and wherein the second determining whether the latency is attributable to the second group of network equipment comprises determining whether the latency associated with the latency diagnostic trigger is attributable to the first content delivery network equipment or the second content delivery network equipment.

### Claim 5 (depends on 1)

The method of claim 1, wherein the third group of network equipment comprises equipment of an internet service provider, and wherein the equipment of the internet service provider does not comprise the network equipment.

### Claim 6 (depends on 1)

The method of claim 1, wherein receiving the latency diagnostic trigger comprises receiving a notification from a ticketing system or receiving an alert from a video quality monitoring system.

### Claim 7 (depends on 1)

The method of claim 1, further comprising, in response to receiving the latency diagnostic trigger, collecting, by the network equipment, network information associated with a session impacted by the latency associated with the latency diagnostic trigger.

### Claim 8 (depends on 7)

The method of claim 7, wherein the network information comprises at least one of time information, location information, a session identifier, or an internet protocol address.

### Claim 9 (depends on 8)

The method of claim 8, wherein the third group of network equipment comprises equipment of an internet service provider, and further comprising using, by the network equipment, at least one of the session identifier or the internet protocol address to identify the internet service provider.

### Claim 10 (depends on 1)

The method of claim 1, wherein querying the network monitoring system to obtain the latency and loss statistics comprises querying the network monitoring system to obtain a round trip time associated with first group of network equipment.

### Claim 11 (depends on 1)

The method of claim 1, wherein the second determining whether the latency is attributable to the second group of network equipment comprises querying a content server access log to determine a cache server processing time.

### Claim 12 (depends on 11)

The method of claim 11, wherein the second determining whether the latency is attributable to the second group of network equipment comprises detecting an increase of a content server cache fill latency.

### Claim at position 13

13-20. (canceled)

### Claim 21

Network equipment, comprising:
a processor; and
a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:
receiving a latency diagnostic trigger;
in response to receiving the latency diagnostic trigger, first determining whether a latency associated with the latency diagnostic trigger is attributable to cellular communication network equipment, wherein the first determining whether the latency is attributable to the cellular communication network equipment comprises querying a cellular communication network monitoring system to obtain latency and loss statistics associated with a time window comprising the latency associated with the latency diagnostic trigger;
in response to a result of the first determining being that the latency associated with the latency diagnostic trigger is not attributable to the cellular communication network equipment, second determining whether the latency associated with the latency diagnostic trigger is attributable to content delivery network equipment; and
in response to a result of the second determining being that the latency associated with the latency diagnostic trigger is not attributable to the content delivery network equipment, third determining that the latency associated with the latency diagnostic trigger is attributable to internet service provider equipment.

### Claim 22 (depends on 21)

The network equipment of claim 21, wherein the content delivery network equipment comprises first content delivery network equipment and second content delivery network equipment, and wherein the second determining whether the latency is attributable to the content delivery network equipment comprises determining whether the latency associated with the latency diagnostic trigger is attributable to the first content delivery network equipment or the second content delivery network equipment.

### Claim 23 (depends on 21)

The network equipment of claim 21, wherein the latency diagnostic trigger comprises a notification from a ticketing system.

### Claim 24 (depends on 21)

The network equipment of claim 21, wherein querying the network monitoring system to obtain the latency and loss statistics comprises querying the network monitoring system to obtain a round trip time associated with the cellular communication network equipment.

### Claim 25 (depends on 21)

The network equipment of claim 21, wherein the second determining whether the latency is attributable to the content delivery network equipment comprises detecting an increase of a content server cache fill latency.

### Claim 26

A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising:
receiving a latency diagnostic trigger;
in response to receiving the latency diagnostic trigger, first determining whether a latency associated with the latency diagnostic trigger is attributable to cellular communication network equipment, wherein the first determining whether the latency is attributable to the cellular communication network equipment comprises querying a network monitoring system to obtain latency and loss statistics associated with a time window comprising the latency associated with the latency diagnostic trigger; and
in response to the first determining indicating that the latency associated with the latency diagnostic trigger is not attributable to the first group of network equipment, second determining whether the latency associated with the latency diagnostic trigger is attributable to content delivery network equipment, wherein the content delivery network equipment comprises first content delivery network equipment and second content delivery network equipment, and wherein the second determining whether the latency is attributable to the content delivery network equipment comprises determining whether the latency associated with the latency diagnostic trigger is attributable to the first content delivery network equipment or the second content delivery network equipment.

### Claim 27 (depends on 26)

The non-transitory machine-readable medium of claim 26, wherein the operations further comprise, in response to the second determining indicating that the latency associated with the latency diagnostic trigger is not attributable to the content delivery network equipment, third determining that the latency associated with the latency diagnostic trigger is attributable to internet service provider network equipment.

### Claim 28 (depends on 27)

The non-transitory machine-readable medium of claim 27, wherein the operations further comprise, in response to receiving the latency diagnostic trigger, collecting a session identifier associated with an internet service provider network session impacted by the latency associated with the latency diagnostic trigger and using the using the session identifier to identify the internet service provider equipment.
