802.11ax trigger-based UL + TWT (Kestrel / RTL8852) — scheduled contention-free TX, the standards answer to the TX-egress gap
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Ruhig
- Tech-Stack
- c
- Bereich
- embedded-iot, networking
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- C
- Sterne
- 56
- Forks
- 29
- Ø Merge
- 3 Std. 43 Min.
- Gemergte PRs (30 T.)
- 75
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus OpenIPC/devourer
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)Evtl. vergeben @josephnef hat das heute übernommen. Offenenhancement
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 42/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 12/100
OpenIPC/devourer#579 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 12/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 8/100
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in OpenIPC/devourer
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
Needs-Triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 2 Tagen
-
issue: bug report
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 2 Tagen
-
cross-platform fix-now
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
feature:index kind:crash status:confirmed triaged
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
clice-io/clice#1123 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag