Why Channel-Centric Models are not Enough to Predict End-to-End Performance in Private 5G: A Measurement Campaign and Case Study

This paper demonstrates that channel-centric models, including ray-tracing simulators, fail to accurately predict end-to-end throughput in private 5G networks due to systematic over-estimation of MIMO spatial layers, whereas data-driven Gaussian process models trained on direct measurements provide significantly more reliable predictions for communication-aware robot planning.

Nils Jörgensen

Published Wed, 11 Ma
📖 5 min read🧠 Deep dive

Here is an explanation of the paper, translated into everyday language with some creative analogies.

The Big Picture: The Robot's "Crystal Ball" Problem

Imagine you are programming a robot to zip around a factory, carrying heavy parts from one machine to another. To do this safely and quickly, the robot needs to talk to a central computer via a 5G network. If the connection drops, the robot might crash or stop working.

So, before the robot even moves, engineers try to predict: "If the robot goes to this spot, how fast will the internet be?"

For a long time, engineers have used two main ways to make this prediction:

  1. The Physics Simulator (The "Map Maker"): A computer program that draws a 3D map of the factory and uses the laws of physics to calculate how radio waves bounce off walls and metal.
  2. The Data Learner (The "Experienced Local"): A computer program that looks at real measurements taken by a robot walking around the factory and learns patterns from that data.

The Big Question: Do these methods actually tell us the truth about how fast the internet will be?

The Experiment: A Robot in a Nuclear Bunker

The researchers took this question to a very specific place: the KTH Reactor Hall in Stockholm. It's an underground, radio-shielded room that used to house a nuclear reactor. Because it's shielded and empty, it's the "perfect classroom" for testing—no outside interference, no random people walking around.

They set up a private 5G network there and sent a robot on a grid pattern to measure the actual internet speed at hundreds of different spots. Then, they compared the robot's real data against the predictions from the two methods mentioned above.

The Surprise: The "Map Maker" Got the Signal Right, But the Speed Wrong

Here is where the story gets interesting.

The Physics Simulator (The Map Maker) was actually pretty good at predicting the signal strength. It knew exactly where the walls were and where the signal would be strong or weak. It was like a weather forecaster who correctly predicted it would be sunny.

However, when it came to predicting the actual internet speed (throughput), the simulator was wildly optimistic. It kept telling the engineers, "You'll get super-fast speeds here!" But when the robot actually went there, the speed was much slower.

Why? The "Four-Lane Highway" Illusion.
Think of 5G MIMO (Multiple-Input Multiple-Output) technology like a highway with multiple lanes.

  • The Simulator's View: It assumed the highway always had 4 lanes open for traffic, no matter what. It thought, "The signal is strong, so we can use all 4 lanes!"
  • The Reality: In the real world, the highway was often only 1 or 2 lanes open. The system was smart enough to realize that even though the signal was strong, the "traffic" (interference and physics) was too messy to safely use all 4 lanes. So, it dropped back to 1 or 2 lanes to stay stable.

Because the simulator didn't know about these "lane closures," it kept predicting 4x the speed that was actually possible. It was like a GPS telling you, "You'll get there in 10 minutes!" because it assumes you have a 4-lane highway, while in reality, you're stuck in a single-lane construction zone.

The Solution: The "Experienced Local" (Data-Driven Model)

The researchers then tried the second method: Gaussian Process Regression (GPR).

Instead of trying to calculate physics, this method was like hiring a local guide who has walked the factory floor a thousand times.

  • The robot walked around, measured the speed, and fed that data to the model.
  • The model didn't care about walls or antennas; it just learned: "When the robot is here, the speed is this."

The Result:
The "Local Guide" was incredibly accurate. It predicted the speed almost perfectly, with almost no bias. It learned the messy reality of the factory floor (the "lane closures") directly from the data, bypassing the need to guess how the physics worked.

The Takeaway: Don't Trust the Map, Trust the Experience

The paper concludes with a warning for anyone building robots that rely on 5G:

  1. Signal Strength \neq Speed: Just because the signal is strong (good bars on your phone) doesn't mean the internet is fast. The system might be throttling itself down to stay stable.
  2. Physics Simulators Lie: Even the most advanced physics simulators are too optimistic about speed because they don't understand the complex "traffic rules" of the 5G network (like how many lanes are actually open).
  3. Data is King: If you want to know how fast a robot will actually move, you need real-world data, not just a pretty 3D map.

In short: If you are planning a robot's path, don't just look at the signal map. You need to know the real speed, or your robot might plan a route that looks great on paper but fails in reality.