Papers › Discover Your Competition in LTE: Client-Based Passive Data Rate Prediction by Machine Learning
Discover Your Competition in LTE: Client-Based Passive Data Rate Prediction by Machine Learning
Robert Falkenberg, Karsten Heimann, Christian Wietfeld
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
To receive the highest possible data rate or/and the most reliable connection, the User Equipment (UE) may want to choose between different networks. However, current LTE and LTE-Advanced mobile networks do not supply the UE with an explicit indicator about the currently achievable data rate. For this reason, the mobile device will only see what it obtains from the network once it actively sends data. A passive estimation in advance is therefore not doable without further effort. Although the device can identify its current radio conditions based on the received signal strength and quality, it has no information about the cell's traffic load caused by other users. To close this gap we present an Enhanced Client-based Control-Channel Analysis for Connectivity Estimation (EC3ACE), which uncovers the cell load broken down by each single user. Based on this information and in conjunction with existing indicators like Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ), a neural network is trained to perform a data rate prediction for the current LTE link. Compared to an earlier work, our approach reduces the average prediction error below one third. Applied in public networks, the predicted data rate differs by less than 1.5 Mbit/s in 93% of cases.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections