← Latest papers
🤖 machine learning

Adaptive Reinforcement Learning for Unobservable Random Delays

This paper introduces a general interaction layer framework and a model-based Actor-Critic with Delay Adaptation (ACDA) algorithm that enable reinforcement learning agents to dynamically adapt to unobservable, time-varying delays and packet losses, significantly outperforming existing methods in locomotion benchmarks.

Original authors: John Wikman, Alexandre Proutiere, David Broman

Published 2026-07-14
📖 5 min read🧠 Deep dive

Original authors: John Wikman, Alexandre Proutiere, David Broman

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are playing a high-speed video game where you control a robot. In a perfect world, you see the screen, press a button, and the robot moves instantly. But in the real world, things are messy. Your signal might get stuck in traffic, the robot's brain might take a moment to think, or the message might get lost entirely. By the time your command finally arrives, the robot has already moved, and your instruction is now wrong.

This is the problem researchers John Wikman, Alexandre Proutiere, and David Broman tackled. They found that standard AI training assumes everything happens instantly, which breaks down when dealing with real-world delays that are random and invisible to the AI.

The "Old Way" vs. The Real Problem
Previous methods tried to solve this by playing it super safe. They assumed the worst-case scenario: "What if the delay is 10 seconds?" So, they made the AI wait exactly 10 seconds before acting, even if the delay was usually only 1 second. It's like a driver who always waits at a green light for 10 minutes just in case the light stays red longer, even though it usually turns green in 2 seconds. This is safe, but it's incredibly slow and inefficient.

Other methods tried to guess the delay, but they often failed because the AI didn't actually know how long the delay would be when it made its decision. The paper argues against these rigid, fixed-delay approaches, showing they are too conservative and don't adapt to the chaos of real networks.

The New Solution: The "Interaction Layer"
The team introduced a clever new framework called the Interaction Layer. Think of this as a smart "command center" sitting between the AI brain and the robot.

Instead of sending one single command like "Jump now," the AI sends a matrix of future actions—a giant grid of possibilities. It's like a chess player who doesn't just make one move, but writes down a whole book of moves: "If the opponent moves here, I do this; if they move there, I do that."

The AI fills out this grid for many different possible future delays. It doesn't know which row of the grid will actually be used, because it doesn't know how long the message will take to arrive. But the Interaction Layer acts as the referee. When the message finally arrives, the Layer checks the time, figures out exactly how long the delay was, and picks the correct row from the grid to execute. If a message gets lost or arrives out of order, the Layer has backup rows ready to go.

The "Actor-Critic with Delay Adaptation" (ACDA)
To make this work, they built a new AI algorithm called ACDA. This AI is a bit of a psychic. Because it can't see the future, it uses a "model" to imagine what the world will look like when its action finally lands.

Imagine you are throwing a ball to a friend who is running away. You don't just aim at where they are now; you aim at where you think they will be when the ball arrives. ACDA does this mathematically. It calculates a "distribution" of where the robot will be in the future and generates actions based on that prediction. It's not guessing blindly; it's using a learned model of how the robot moves to fill in the gaps of missing information.

What the Numbers Say
The researchers tested this in a simulated world using MuJoCo, a physics engine for robots, across five different environments: Ant-v4, Humanoid-v4, HalfCheetah-v4, Hopper-v4, and Walker2d-v4. They didn't just use fake delays; they used real-world data collected from WiFi networks in a university library and an office.

The results were clear:

  • In the Ant-v4 environment with a specific simulated delay (GE1,23), the old best method (BPQL) scored 2691.88, while ACDA scored 4112.78.
  • In the Humanoid-v4 environment with the same delay, BPQL scored 585.19, while ACDA scored 4608.76.
  • Even with real-world WiFi delays from the library (DLib), ACDA consistently outperformed the state-of-the-art methods.

The paper notes that in almost every scenario tested, ACDA achieved higher average returns than the best existing methods. There was one exception: in the Ant-v4 environment with a specific type of delay (MM1), BPQL performed slightly better. However, across 15 out of 25 benchmarks tested, ACDA was the top performer.

How Sure Are They?
The authors are very confident in these results based on their simulations and replayed real-world data. They ran their tests over 1 million steps of training. However, they are careful to note that while the results are strong, they haven't mathematically proved that the algorithm will always converge to the perfect solution in every possible situation. The success is measured by how well it performed in their specific tests, not by a theoretical guarantee that it works 100% of the time in every universe.

The Bottom Line
This paper suggests that by letting the AI send a "menu" of future actions and letting a smart middle-layer pick the right one based on when it actually arrives, we can handle messy, unpredictable delays much better than by just waiting around or guessing. It turns a chaotic, unpredictable problem into a manageable game of "what if," allowing robots to move smoothly even when their signals are stuck in traffic.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →