L4S, Working Latency, and the Future of the Internet

Header image for L4S and Working Latency podcast recap blog

On a recent Preseem podcast episode, we welcomed Jason Livingood, Vice President of Technology Policy, Product and Standards at Comcast, to chat about L4S, working latency, congestion control, and lots more.

Jason leads Comcast’s efforts in developing and deploying new open standards. In this role, he supports applied R&D via collaboration with the research community, engaging with governments, regulators, and other external key stakeholders on technology policy issues, and provides leadership on end-user product technology roadmap.

Jason is also a member of the board of directors at the Internet Engineering Task Force (IETF) and the Alliance for Telecommunications Industry Solutions, and a member of the Technical Advisory Council at the FCC.

What follows is a recap of the episode, but you can listen to the full discussion here. As always, the podcast is hosted by Dan Siemon, Chief Product Officer, and Jeremy Austin, Senior Product Manager at Preseem.

What is L4S?

For those unfamiliar with the term, L4S stands for Low-Latency, Low-Loss, Scalable Throughput. Comcast is currently rolling out an L4S trial and their goal is to dramatically improve on what Jason called the “working latency or network responsiveness of someone’s internet connection.”

An example of poor working latency came with the mass shift to remote work that happened when the COVID-19 pandemic began, where even those with 1GB fiber-to-the-home connections would occasionally experience delays with video calls.

“And the reason wasn’t lack of bandwidth, it was a latency problem,” said Jason. He said people only really pay attention to idle latency (e.g. when doing a ping test). However, once you start to actually use the connection, that’s where working latency comes into play. Addressing that is “the next frontier of performance improvement,” Jason said.

Businessman asleep at laptop, representing a slow internet connection caused by lack of low latency.

Working Latency and How L4S Can Help

Working latency is a relatively new term, and Jeremy asked why it’s taken so long for the industry to name it. As Jason explained, for a long time network engineers saw increased capacity, which often gets described as “speed,” as the way to improve end-user quality.

And while it’s true that increasing capacity can be a good proxy for improving quality of experience (QoE), the rise of real-time applications like video conferencing is placing new demands on networks at a scale not seen before.

There’s also been a larger philosophical challenge at play, Jason added. That is, many engineers thought you could have one of two things: either you could have very high throughput or very low latency, but you couldn’t have both. However, this was just an assumption and not backed up with data or proof.

Jason said L4S aims for dramatically lower working latency. As an example, in networks that don’t currently use Active Queue Management (AQM), you could be looking at a working latency of hundreds of milliseconds to whole seconds for just one roundtrip. Also, if you’re on a mobile app, that means lots of roundtrips that are then going to stack up on top of each other, further increasing latency to as much as 4 to 5 seconds.

Graphic showing an internet speed test

Even with AQM, you might be at 25-250 ms of delay, depending on how far out you’re going from the access network. The objective with L4S is sub-10ms. Jason said Comcast is conducting field trials right now to see if this is achievable, and added that they’d be happy with a 99th percentile working latency of 25ms.

Where Does Latency Come From?

Or more specifically, where does latency come from in relation to congestion control algorithms? As Jason explained, when many of the TCP congestion control algorithms were originally developed, you’d have one computer connected to a connection with a limited number of flows (often just one). In the modern era, however, with dozens of IoT devices and multiple personal devices online, there are not only multiple flows but the amount of bandwidth that’s needed is constantly changing.

The challenge is finding a flow controller that has a very tight control loop and can quickly adapt to changing conditions. Otherwise, you can get dramatic back-off to reduce consumption, creating the classic sawtooth pattern. Part of the objective with L4S is to tighten those sawtooths, so they’re really tiny and able to adapt to the constantly changing traffic flows.

Dan added that, during those big “sawtooths,” queues build up in the network and that’s what creates latency. Buffering and not propagation latency is the problem, and it’s specifically those TCP flows filling the buffers that are a major cause.

L4S and the Evolving Internet

The panel also discussed whether L4S was essentially creating a two-channel internet, one with traditional congestion control, and one with a more aggressive lower-latency congestion control, with applications able to opt into the channel they prefer.

Jason agreed and said that, unlike previous approaches, with L4S the application is expected to do the marking. This is because the app developer knows their app best and it’s very hard for networks to guess that and get it right.

He added that often when network operators deploy systems that are doing prioritization or trying to infer what type of application is being used, it’s possible at one point in time to get it right, but by that time the applications are already multiple steps ahead because they’re iterating at a different pace. As a result, it becomes impossible to keep up.

Woman working from home on Zoom call.

L4S also gets around having to use things like DPI, traffic is examined and then prioritized based on the type of flow. That’s a lot more difficult with the pervasive encryption we have today, Jason said, and also those systems will always get it wrong at some point.

In the case of a large ISP like Comcast, “getting it wrong” can have major negative consequences for millions of subscribers. Jason also said it’s important to point out that both queues are at the same priority level and both share the same bandwidth. There’s no higher priority or lower priority at work with L4S, it’s simply dividing traffic by congestion control behavior.

The Comcast L4S Trial

Jason explained that Comcast is in the early stages of deploying L4S and is the first ISP to conduct field trials. He said they’ve had “overwhelming customer interest” in participating in the trials. This “really demonstrates to me that people have a better understanding of what latency, delay and lag is than they did a few years ago, maybe as a benefit of working from home during the pandemic,” he said.

After talking about what the trial will entail and how Comcast will measure success, the panel talked about the potential impact of L4S.

“This is potentially a seismic shift in the way that we think about networks and network services and (how we) deploy them,” Jason said. “And for years we’ve always thought just throw bandwidth at people and things get better,” but even people on smaller plans can still have a great internet experience if they have really low latency.

As Stuart Cheshire from Apple has mentioned, app developers have always assumed that there is delay when you access something over the network, usually high (and highly variable) delay. However, if you took that core foundational assumption away, and made it so that delay was roughly the same as on your LAN or local device, that drop in latency under load could fundamentally change the kinds of things that app developers could do, Jason said. This could significantly improve AR/VR capabilities, for example.

Jason pointed out that over the years people have just gotten used to hiccups during video calls or audio and video not syncing, and have been conditioned to think that that’s “just how the internet works”—something you just have to put up with it now and then. However, he said, “I think that’s just this latency problem and that can go away. It doesn’t have to work that way.”

If you’re interested in getting geeky with our team on these and other technical topics affecting internet service providers, follow the Preseem podcast and listen to all of our episodes here.

Where Do the Minutes Go on a Tier 1 ISP Support Call?

A subscriber calls because the internet has been dropping out every evening, and your agent starts the call already behind. They open the account in billing, then the subscriber's radio or ONT in the vendor's portal, then the ticket history, and run a test against the CPE while narrating the wait to someone who was already annoyed when they dialled. That's often how a technical call runs in Tier 1 ISP support: much of it goes to searching, and the conversation fits in around it.

A seasoned agent knows which systems to open and in what order, but still has to open them, because the subscriber's experience, the state of the shared asset and the history of the account are stored in different places. As Wi-Fi or the Network? set out, each check answers part of the question and sends the agent somewhere else for the rest, so the difficulty lies in where the evidence lives rather than in the person reading it. When the call runs out before the answer arrives, the subscriber gets a callback, an escalation or a reboot script that may not address the fault.

Why Is One Agent Doing Two Jobs on Every Call?

Every technical call holds two jobs. One is finding the answer: gathering evidence across systems, comparing this subscriber with their neighbours and deciding where the fault is. The other is handling the person: listening and empathizing with what they've been living with, explaining what's wrong in terms they recognize and telling them what happens next. They're different skills, and on today's desk one agent does both at once.

On the evening-dropout call, the investigation takes the agent's attention first, because there's nothing to explain until it's done. The subscriber listens to typing while the agent moves between portals, and if the answer arrives after they've hung up, the explanation never happens, and the ticket moves to Tier 2. Repeated across a day, that's the reactive load that keeps ISP support teams stuck in firefighting mode.

What Does Tier 1 ISP Support Need on Screen to Close the Call?

Four pieces of evidence, read together:

The What Tier 1 Needs

Where It Usually Lives Today

What It Helps Determine

The What Tier 1 Needs

The subscriber's experience over the window they're describing (latency, packet loss, throughput against their plan)

Where It Usually Lives Today

A QoE system, if the operator collects it at all

What It Helps Determine

Whether the problem the subscriber describes actually happened, and when

The What Tier 1 Needs

The asset they sit on, and how other subscribers on that AP, sector or PON did over the same hours

Where It Usually Lives Today

The network management system, or one portal per radio and OLT vendor

What It Helps Determine

Whether others on the same asset were affected at the same time, which points to a shared issue

The What Tier 1 Needs

Has a problem that's in your network

Where It Usually Lives Today

The radio or OLT vendor's tool

What It Helps Determine

Whether the drop to the home is healthy, which narrows the search without placing the fault inside the home

The What Tier 1 Needs

What was tried on this account last time

Where It Usually Lives Today

The ticketing system or CRM

What It Helps Determine

Which steps not to repeat

None of these settles the question alone. Identifying an in-home Wi-Fi problem takes evidence from behind the CPE, and neighbours degrading at the same hours points to a shared issue without naming its cause. With all four in one view, an agent can reason through the diagnosis and explain what the evidence points to as they go, but reading them together mid-call is still the investigation, just done faster.

How Does an AI Support Assistant Get the Answer on Screen?

Preseem's Support Assistant, part of Preseem Plus, does the troubleshooting itself. Once the call is tied to a subscriber, it works through the same evidence an agent would chase across systems: the subscriber's experience over recent days, the other subscribers on their AP, sector or PON, the history of their radio or ONT, and the tickets already on the account. It gives the agent the cause and the next action in plain language, including whether the fault is in the home or on the network, and where, along with the evidence that places it there.

On the evening-dropout call, the agent opens the account and sees the pattern laid out: the subscriber's latency and packet loss climbing from around 7 p.m. on each of the evenings they described, their radio link healthy throughout, the other subscribers on the same sector showing the same pattern over the same hours, and the sector running at capacity while it happens. The assistant reads those together and places the problem on the shared sector as evening congestion, then routes it to the network team with that evidence attached. That reading is what it adds beyond four sources on one screen, since the agent isn't the one left to work out whether a healthy link and degraded neighbours add up to congestion.

The agent doesn't need another round of checks; they square the answer with what the subscriber is describing and act on it. Because the Support Assistant works alongside the agent, a person who knows the subscriber and the network sees its answer before the subscriber does, which is what separates an assistant from a tool placed in front of the subscriber, as covered in what AI actually does in ISP customer support.

What Does the Agent Tell the Subscriber?

With the investigation done, the rest of the call focuses on the subscriber. The agent can tell them that their own connection and equipment are fine, that the slowdown they've been seeing is on the part of the network they share with their neighbours and happens when it's busiest in the evening, and that it has been escalated to the network team with the evidence attached. Then comes what happens next: when they should see a change, that nobody needs to visit, and how they'll hear back.

The agent also has time to listen. If the subscriber mentions that the dropouts happen on weekend mornings too, that doesn't fit an evening congestion pattern, and an agent who isn't juggling portals can hear it, ask about it and check it against what's on screen before the call ends.

How Much Shorter Do Calls Get When Tier 1 Has the Answer?

Among Preseem customers using the Support Assistant, we've seen call times fall from over 30 minutes per call to under five. Read it as an indication of what's possible rather than a benchmark for your desk; your own call mix and network will shape where you land.

What Happens Next Once Tier 1 Has a Diagnosis?

A diagnosis on the call leads to one of three outcomes, and only one resolves the issue before the subscriber hangs up. When the assistant places the fault inside the home, the agent can often fix it with the subscriber on the line by moving the router or switching a device to a wired connection. Where the home network itself is what's holding the subscriber back, such as an ageing router or Wi-Fi coverage that doesn't reach the rooms they use, the agent can also offer a managed router service, so the operator looks after that part of the connection from then on. When it points to a fault on the shared network, as on the evening-dropout call, the ticket goes to the NOC with the fault confirmed. When it points to the subscriber's own link, a technician goes out with the fault already located.

The second and third outcomes still leave work for someone else, but they change what that work is. A call that runs out before the cause is found often escalates as little more than a description of symptoms, and Tier 2 or a network engineer starts the investigation again from scratch. With the diagnosis and its evidence attached, they start from the finding, and that's the metric for a support leader to watch: how many tickets reach Tier 2 needing the investigation started over. The engineers who would otherwise rerun it are often the same people planning upgrades and building out new areas, so each investigation they don't repeat is time back on that work. For how this fits with first-contact resolution, ramp time and the rest of the desk's numbers, see the complete guide to improving ISP support performance.

 

Take A Tour:

ISP Network Priorities

Explore how Network Priorities ranks network issues by subscriber impact, helping you focus on the fixes that make the biggest difference.

Take A Tour:

Support Assistant

See the Support Assistant in action! 

Frequently Asked Questions

 

When should a Tier 1 ISP support call escalate?

A call should escalate when the fix needs something Tier 1 can't do: a configuration change on the network, a field repair, or a fault the NOC has to work. An escalation made because nobody could identify the cause in time is the easiest kind to recover, since the information needed to settle it often already exists in the operator's systems. Sort a month of escalations into those two groups and you'll see how much of your Tier 2 load is diagnosis rather than repair. The ISP support performance guide covers the escalation measures that sit alongside it.

Is an AI support assistant for ISPs just a smarter knowledge base?

No. A knowledge base holds procedures that apply to any subscriber, while an assistant connected to network data works out what's wrong with this subscriber's connection today. The knowledge base still has a place, because it's where the steps for a router reset or a plan change live once the cause is known. What it can't do is locate the fault, which is why an agent working from articles alone ends up troubleshooting by elimination.

What does AI agent assist need from a broadband network?

It needs per-subscriber experience measured continuously, a map tying each subscriber to the AP, sector or PON they sit on, access-link telemetry from the radio and OLT vendors you run, and the account's ticket history. To place a problem inside the home rather than just rule out the access link, it also needs evidence from behind the CPE. The topology map is easy to overlook, and without it a tool can't compare a subscriber with their neighbours, which is how a shared fault is told apart from a single one.

What if the subscriber doesn't accept the help desk diagnosis?

Show them the evidence in terms of their own experience: the drops on the evenings they described, or the fact that their neighbours on the same sector saw the same thing. A help desk diagnosis is much easier to accept when it matches what the subscriber lived through, and an agent with the answer already on screen has time to make that connection instead of reading a conclusion off a script.

About Preseem

Preseem shows regional ISPs what every subscriber is actually experiencing, from the network into the home and across every major equipment vendor. Operators use it to improve subscriber experience and business results together: keeping subscribers happier for longer, running a more efficient operation at lower cost, and earning more from upgrades and services subscribers want. Preseem turns that intelligence into next steps for support, the NOC and sales, aimed at whatever helps the most subscribers. Support Assistant gives the rep on the call the cause and the next action in plain language, including whether the fault is in the home or on the network. Network Priorities ranks the sites, APs and PONs to fix first by how many subscribers each one is degrading, and Service Priorities shows which subscribers to contact and whether to fix something or offer an upgrade. Expert view keeps two years of history behind every subscriber, AP and OLT. Learn more at preseem.com.

[/et_pb_post_content][/et_pb_column][/et_pb_row][/et_pb_section]

Latest From Our Blog

Network insights, best practices, and product updates to help you get the most from Preseem.

STOP MANAGING COMPLEXITY

START RUNNING YOUR BUSINESS

Every week without visibility is another week of trucks that didn't need to roll and subscribers who left without telling you why.

Let's start with your network, your vendors, your subscribers.