802.11ax trigger-based UL + TWT (Kestrel / RTL8852) — scheduled contention-free TX, the standards answer to the TX-egress gap
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- c
调研方向
Start by reading docs/timing-accuracy.md, docs/time-distribution.md, and the Kestrel bring-up notes in CLAUDE.md; the issue says the RTL8852 HAL is a prerequisite and currently out of scope. First determine during Kestrel bring-up whether firmware exposes HE Trigger-frame TX and TWT scheduling to the host. Done means establishing feasibility and, only if supported, implementing the scoped trigger-based UL and TWT scheduling; no specific source files or tests are identified.
由索引模型根据 Issue 内容生成。
描述
Goal
This session characterized and measured the fundamental limit of scheduled TX on Realtek 11ac/n silicon: there is no host-reported TX-egress timestamp, and CSMA governs air-departure, so µs-precise scheduled per-frame TX is not achievable (docs/timing-accuracy.md). The only hardware-TX-timed primitive is the beacon engine (auto-TX at TBTT), which is why devourer's uplink timing-advance loop steers the beacon TBTT rather than data frames.
802.11ax's trigger-based UL access + TWT is the standard's mechanism for exactly this — the AP schedules UE transmit opportunities (contention-free, OFDMA UL via Trigger frames), and TWT negotiates wake/TX windows. That is genuinely cellular-like scheduled access, and it is the forward path to the "scheduled-TX half" of the LTE/5G-parity picture. This issue plans it for the Kestrel (RTL8852) family for whoever takes it on.
Depends on
- A Kestrel HAL (RTL8852 family) — currently out of scope (see CLAUDE.md). This is a forward-looking plan; it presumes Kestrel bring-up exists first.
Why this is the right lever
Faster transports (PCIe, SDIO — #235) lower the submit floor but cannot schedule air-departure, because that is a MAC/firmware property, not a transport one. 802.11ax moves scheduling into the MAC/PHY: the AP's Trigger frame grants each STA a resource unit and a start time (SIFS after the trigger), and the STA's MAC fires the UL-OFDMA transmission at that instant — hardware-scheduled, contention-free. This is the only path to cellular-grade scheduled UL on Realtek Wi-Fi.
Scope / implementation detail
AP side
- Build + air HE Trigger frames (Basic Trigger for UL-OFDMA): per-STA RU allocation, UL length, target RSSI, and the common info (UL BW, GI/LTF).
- Own the schedule: which STAs transmit in which trigger, at what cadence.
STA side
- Respond to a Trigger with UL-OFDMA TX at trigger + SIFS — this is the hardware-scheduled TX (the STA MAC fires at the scheduled instant, not after CSMA backoff).
TWT
- Negotiate Target Wake Time agreements (individual + broadcast TWT): schedule wake / service periods; the AP owns the timetable. Useful independently for power-scheduled FPV links.
Key question (decides feasibility)
Does the RTL8852 firmware expose trigger-frame TX + TWT scheduling to the host — the way the current silicon exposes TBTT-timed beacon TX via the reserved-page engine?
- If yes, this delivers the µs-precise scheduled TX that USB/SDIO/PCIe cannot — because it is a MAC/firmware mechanism, transport-independent.
- If the firmware owns trigger/TWT scheduling opaquely (typical of consumer 11ax), host control may be limited to negotiating TWT parameters rather than µs-steering individual transmissions. This is the first thing to determine during Kestrel bring-up.
Relation to existing work
devourer's uplink timing-advance loop (beacon-engine TBTT steering, docs/time-distribution.md) is a workaround for the missing scheduled TX. 802.11ax trigger-UL would replace it with the native mechanism — and would be the concrete "we closed the scheduled-TX gap vs LTE/5G" milestone.
Out of scope
The Kestrel HAL itself (prerequisite), and full 11ax data-plane (MU-MIMO, 1024-QAM) beyond what trigger-UL/TWT scheduling needs.
- 主要语言
- C
- 星标
- 56
- 派生
- 29
- 平均合并
- 3 小时 43 分钟
- 30 天内合并 PR
- 75
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
OpenIPC/devourer 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)可能已有人在做 @josephnef 今天认领。 未关闭enhancement
难度 4/5 3-5 天 新手友好度 42/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 12/100
OpenIPC/devourer#579 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 8/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Needs-Triage
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 2 天内回复
-
issue: bug report
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
-
cross-platform fix-now
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
feature:index kind:crash status:confirmed triaged
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复