跳到正文
研踪PaperTrail
← 研踪 PaperTrail

arXiv:2608.15138 · v2

ReForge: Keeping ABR Algorithms Never Finished with Verified Large Language Model Revisions

首次提交 2026-08-15 17:23
版本更新 2026-11-13 13:22
雷达观测 2026-11-17 04:57
arXiv ↗PDF ↗

摘要

Designing an ABR algorithm for a network scenario takes an engineer months, and large language models (LLMs) now do this work in hours. But either way, the algorithm is fixed once it is deployed. It fits the networks seen during its design and falls behind on the networks that arrive afterwards. We ask whether an ABR algorithm can keep being designed after deployment, revised as each new network arrives, without becoming worse on any network it already serves. We propose ReForge, which keeps a pool of existing ABR policies unchanged and lets an LLM revise only the rules that decide which policy chooses the next bitrate. When a new network arrives, the LLM reads how the current rules and every policy perform on the networks served so far and rewrites the rules. The rewrite is deployed only if a replay in simulation shows that it improves the served networks as a whole and makes none of them worse. A fast GPU simulator that replays every episode exactly makes this acceptance test cheap enough to run for every revision. We evaluate ReForge on nine real-world network datasets, with new networks arriving one at a time. The revisions raise the mean QoE from 1.43 to 1.79, past the best single policy at 1.66 and close to the 1.86 of selecting the best policy for each dataset, while the QoE on the networks served first does not drop. The gain also holds in a real video player. All code, data, and records will be available.

AI 论文解读

基于摘要 · 非全文审阅

此版本尚未生成 AI 解读。解读由后台任务生成并按论文版本保存,登录后共享已有结果。

版本差异

本站首次收录为 v2,暂无更早版本可对照。

观测到的版本

相邻记录可能跳过中间版本;首次发现 v2 及以上也会标为版本更新。

v2 · 2026-11-13 13:22 · 最新观测版本

ReForge: Keeping ABR Algorithms Never Finished with Verified Large Language Model Revisions

Designing an ABR algorithm for a network scenario takes an engineer months, and large language models (LLMs) now do this work in hours. But either way, the algorithm is fixed once it is deployed. It fits the networks seen during its design and falls behind on the networks that arrive afterwards. We ask whether an ABR algorithm can keep being designed after deployment, revised as each new network arrives, without becoming worse on any network it already serves. We propose ReForge, which keeps a pool of existing ABR policies unchanged and lets an LLM revise only the rules that decide which policy chooses the next bitrate. When a new network arrives, the LLM reads how the current rules and every policy perform on the networks served so far and rewrites the rules. The rewrite is deployed only if a replay in simulation shows that it improves the served networks as a whole and makes none of them worse. A fast GPU simulator that replays every episode exactly makes this acceptance test cheap enough to run for every revision. We evaluate ReForge on nine real-world network datasets, with new networks arriving one at a time. The revisions raise the mean QoE from 1.43 to 1.79, past the best single policy at 1.66 and close to the 1.86 of selecting the best policy for each dataset, while the QoE on the networks served first does not drop. The gain also holds in a real video player. All code, data, and records will be available.

查看此版本解读 →查看此版本原文 ↗