What are OFDMA resource units in IEEE 802.11ax (Wi-Fi 6) and how are they sized?

OFDMA in 802.11ax divides each channel into Resource Units (RUs), where each RU is a contiguous block of subcarriers. The defined sizes are 26-tone (roughly 2 MHz), 52-tone, 106-tone, 242-tone (a full 20 MHz channel), 484-tone (40 MHz), and 996-tone (80 MHz). A 160 MHz channel uses two 996-tone allocations. The access point scheduler maps stations to RUs based on traffic load, packet size, and channel quality — small RUs are efficient for low-rate clients and small frames, while larger RUs serve high-throughput clients. The RU partitioning is what makes OFDMA different from OFDM in earlier Wi-Fi generations: instead of one station per transmission, the AP can serve many in a single OFDM symbol burst.

What is the difference between a Regular Resource Unit (RRU) and a Distributed Resource Unit (DRU)?

A Regular Resource Unit (RRU) is the traditional contiguous tone allocation defined since IEEE 802.11ax — the data subcarriers are grouped together in adjacent frequency slots. A Distributed Resource Unit (DRU) is a new tone allocation in IEEE 802.11bn (Wi-Fi 8) where the data subcarriers are spread across the entire transmission bandwidth instead of being contiguous. DRUs provide a power-boost coverage gain because energy is spread across more frequency, which helps far stations at the edge of coverage. The trade-off is that DRUs limit the number of spatial streams and reduce how many simultaneous OFDMA users an AP can serve, so they are not a free upgrade — they are an adaptive choice for range-limited links.

What is a Multiple DRU (MDRU) and why does 802.11bn add it on top of DRU?

Multiple DRU (MDRU) refers to an allocation where more than one DRU is used in the same transmission, typically to serve more than one far station simultaneously while still capturing the power-boost coverage gain of the distributed tone pattern. MDRU is part of the 802.11bn (Wi-Fi 8) toolset for ultra-high reliability: instead of forcing the AP to choose between coverage (DRU) and multi-user efficiency (RRU), MDRU lets a deployment combine multiple distributed allocations in one PPDU. The cost is preamble and signaling complexity — the receivers need to decode which DRU pattern they are assigned to.

How does the OFDMA scheduler decide which station gets which resource unit?

The OFDMA scheduler at the access point weighs several factors: per-station traffic queue depth, packet size, channel state information per subcarrier, modulation and coding scheme the station can support, and access category (voice / video / best-effort / background) for QoS. A typical scheduling pass groups small-packet clients into smaller RUs (26-tone or 52-tone) so dozens of stations can share one transmission, while a high-throughput single client may take a 242-tone or 484-tone allocation alone. The scheduler also considers fairness — long-starved low-rate stations are promoted to avoid airtime starvation. The specific algorithm is a vendor implementation choice; the standard defines the RU framework but not the scheduling policy.

How does OFDMA differ from MU-MIMO, and when does an access point use each?

OFDMA partitions the channel in the frequency domain into resource units and serves multiple stations on disjoint sub-bands in one transmission. MU-MIMO partitions in the spatial domain and serves multiple stations on the same frequency at the same time using independent spatial streams. They solve different problems. OFDMA is best for many small-packet clients (low latency, fairness, contention reduction). MU-MIMO is best for fewer high-throughput clients with high SNR and good CSI (raw aggregate throughput). Modern Wi-Fi 6 and Wi-Fi 7 access points use both: OFDMA for the uplink where many clients contend, and MU-MIMO for the downlink to capable high-rate clients. A strong interview answer separates the two before comparing.

Why does the IEEE 802.11bn (Wi-Fi 8) tone allocation surface get its own interview question category?

Because Wi-Fi 8 introduces engineering choices that did not exist in earlier amendments. The split between RRU, DRU, and MDRU forces deployment decisions about who gets coverage gain versus who gets multi-user efficiency. The UHR-LTF training field that supports the new RU types must coexist with EHT-LTF for backward compatibility with Wi-Fi 7 clients. The scheduler now has more degrees of freedom (which RU type, which power profile, which spatial stream count). Candidates who can navigate this surface — even at the level of "DRU is for far stations, RRU is the default, MDRU combines both" — are demonstrating the kind of mechanism-level reasoning that distinguishes wireless systems engineers from feature memorizers.

What common mistakes do new graduates make when explaining OFDMA in interviews?

The most common mistake is calling OFDMA "OFDM with multiple users" — which is technically true but skips the engineering content. OFDMA introduces resource-unit allocation, scheduling, and trigger-based uplink access, none of which exist in single-user OFDM. A second mistake is confusing OFDMA with MU-MIMO. A third is assuming that more users in an OFDMA transmission always means lower per-user throughput; the better framing is that OFDMA trades per-user peak rate for aggregate efficiency under contention. A fourth is forgetting that uplink OFDMA requires the access point to send a trigger frame so all the stations transmit at the same time on their assigned RUs — uplink scheduling is centrally controlled, not contended.

OFDMA Resource Units Explained (IEEE 802.11ax / 802.11bn) Interview Prep

OFDMA resource units in IEEE 802.11ax (Wi-Fi 6) and 802.11bn (Wi-Fi 8): 26 to 996-tone RUs, RRU vs DRU vs MDRU, scheduling, and OFDMA vs MU-MIMO.

Quick answer

OFDMA Resource Units (RUs) are the fundamental allocation granularity in IEEE 802.11ax (Wi-Fi 6), 802.11be (Wi-Fi 7), and 802.11bn (Wi-Fi 8).

Wireless interviews use OFDMA resource units as a fast filter for whether a candidate can connect PHY-level concepts to MAC-level scheduling decisions.

Editorial review

Written by

CompoundLearn editorial team

Wireless / RF / hardware engineering

Reviewed by

CompoundLearn editorial team

Wireless / RF / hardware engineering

Last reviewed

June 17, 2026

Built from curated topic maps, editorial validation, and subject-matter review so the page stays aligned with the interview intent and the current content pipeline.

Key points

OFDMA splits a Wi-Fi channel into Resource Units (RUs) so one access point serves many stations in a single transmission — OFDM served only one station per burst.
802.11ax RU sizes run from 26-tone (~2 MHz, for small IoT frames) to 996-tone (80 MHz, one high-rate client); 242-tone is a full 20 MHz channel.
Uplink OFDMA requires a trigger frame from the AP to synchronize start time, RU assignment, MCS, and transmit power across all stations.
OFDMA partitions the channel in frequency (resource units); MU-MIMO partitions in space (spatial streams, see /topics/mimo) — modern access points use both.
Wi-Fi 8 (802.11bn) adds the Distributed RU (DRU) for a power-boost coverage gain at far stations (see /topics/papr-peak-to-average-power-ratio), plus the Multiple DRU (MDRU) to serve several far stations at once.

What it is

OFDMA Resource Units (RUs) are the fundamental allocation granularity in IEEE 802.11ax (Wi-Fi 6), 802.11be (Wi-Fi 7), and 802.11bn (Wi-Fi 8). Where earlier Wi-Fi generations used OFDM as a single-user waveform (see /topics/ofdm) — one station per transmission burst — OFDMA partitions each channel into resource units so the access point can serve many stations in one transmission. The defined RU sizes in 802.11ax are 26-tone (about 2 MHz), 52-tone, 106-tone, 242-tone (a full 20 MHz channel), 484-tone (40 MHz), and 996-tone (80 MHz); a 160 MHz channel uses two 996-tone allocations. In IEEE 802.11bn, the resource-unit framework expands. The traditional contiguous RU, now called the Regular Resource Unit (RRU), keeps its 802.11ax behavior. A new tone allocation, the Distributed Resource Unit (DRU), spreads data subcarriers across the entire transmission bandwidth instead of grouping them contiguously — producing a power-boost coverage gain for far stations at the cost of fewer simultaneous OFDMA users and tighter spatial-stream limits. A further variant, the Multiple DRU (MDRU), uses more than one DRU in the same transmission so an access point can serve several far stations together while still capturing the distributed-tone coverage gain. All three are supported by the new UHR-LTF (Ultra-High Reliability Long Training Field) preamble structure, which is designed to coexist with EHT-LTF for backward compatibility with Wi-Fi 7 clients. Case study: a warehouse Wi-Fi 8 access point covering long aisles with many low-rate scanners. The scheduler picks 26-tone RRUs for near scanners (small payload, multi-user efficiency dominates) and DRU allocations for far scanners at the edge of coverage (power-boost gain wins despite fewer simultaneous users). RRU and DRU coexist in the same channel; the engineering decision is per-station, not per-deployment. The same scheduling surface interacts with Multi-Link Operation (see /topics/multi-link-operation-deep-dive for the MLO mechanics) and with the broader Wi-Fi 8 mechanism set covered at /topics/wifi-8-80211bn-ultra-high-reliability. The reason this matters for interview prep is that the OFDMA surface tests whether a candidate understands the relationship between waveform, scheduling, and link budget — three engineering domains that interact in every modern Wi-Fi design.

Why interviewers ask

Wireless interviews use OFDMA resource units as a fast filter for whether a candidate can connect PHY-level concepts to MAC-level scheduling decisions. Most candidates can name "OFDMA" and "resource units" from a feature list; far fewer can explain that 26-tone RUs are the small-packet workhorse, that 242-tone is one full 20 MHz channel, that uplink OFDMA requires a trigger frame to synchronize stations, and that 802.11bn extends the framework with DRU and MDRU for coverage-gain trade-offs. Three signals matter most. First, can the candidate distinguish the OFDMA framework (resource units, trigger-based uplink, multi-user scheduling) from the underlying OFDM waveform (subcarriers, IFFT, cyclic prefix)? The two are layered but distinct; conflating them is a fast tell that the candidate has memorized terms without understanding mechanisms. Second, can the candidate articulate the OFDMA vs MU-MIMO trade-off — frequency-domain partitioning versus spatial-domain partitioning — and explain when each is the right choice? Third, can they reason about the 802.11bn extensions: why DRU exists at all, what an MDRU buys over a single DRU, and how the scheduler navigates the expanded design space? Roles where these questions matter most include wireless systems engineers designing access points, modem firmware engineers working on Wi-Fi MAC scheduling, RF engineers planning multi-AP coverage, and product managers scoping Wi-Fi 7 to Wi-Fi 8 upgrade cycles. The OFDMA surface is the single most commonly asked Wi-Fi 6+ interview topic after MIMO.

Common mistakes

The most common mistake is treating OFDMA as a small marketing-level addition to OFDM. OFDMA introduces resource-unit allocation, the trigger-based uplink access mode, and a multi-user MAC scheduling framework — none of which exist in single-user OFDM. A candidate who says "OFDMA is OFDM with multiple users" is technically not wrong but skips every interesting engineering point. The second most common mistake is conflating OFDMA and MU-MIMO. OFDMA partitions the channel in the frequency domain into resource units and serves multiple stations on disjoint sub-bands. MU-MIMO partitions in the spatial domain and serves multiple stations on the same frequency at the same time using independent spatial streams. They solve different problems and modern access points use both; treating them as interchangeable is a fast tell. A third frequent gap is misunderstanding the uplink trigger frame. New graduates often assume each station independently wins CSMA/CA back-off for an uplink transmission; in OFDMA the access point sends a trigger frame that synchronizes start time, assigns RUs, specifies MCS, and signals a transmit-power target so all the uplinks arrive at the AP aligned. Without the trigger, simultaneous uplink would collide. A fourth gap is assuming all the 802.11bn additions are pure upgrades. DRU buys coverage gain at the cost of spatial streams and multi-user count. MDRU lets multiple DRU allocations coexist but adds preamble and signaling overhead. The scheduler now has more degrees of freedom but also more configuration to get wrong. A strong interview answer acknowledges the trade-offs explicitly. Other gaps: assuming OFDMA is uplink-only or downlink-only (it operates in both), assuming 4096-QAM is the OFDMA default modulation (the MCS is per-station and channel-dependent), and assuming OFDMA replaces OFDM entirely (mixed-generation fleets remain interoperable on the same access point for years after a generation transition).

IEEE 802.11 OFDMA resource-unit types — sizing and use case

RU type	Subcarriers (tones)	Approx. bandwidth	Introduced in	Best for
26-tone RRU	26	~2 MHz	802.11ax (Wi-Fi 6)	Many small-packet IoT clients, short status frames
52-tone RRU	52	~4 MHz	802.11ax (Wi-Fi 6)	Low-rate clients with slightly larger payloads
106-tone RRU	106	~8 MHz	802.11ax (Wi-Fi 6)	Mid-rate clients in dense cells
242-tone RRU	242	20 MHz	802.11ax (Wi-Fi 6)	Full 20 MHz channel allocation to one station
484-tone RRU	484	40 MHz	802.11ax (Wi-Fi 6)	High-throughput clients on bonded channels
996-tone RRU	996	80 MHz	802.11ax (Wi-Fi 6)	Single high-rate client; 160 MHz uses two of these
DRU (Distributed RU)	Variable, spread across PPDU	Tone-spread	802.11bn (Wi-Fi 8)	Far stations needing power-boost coverage gain
MDRU (Multiple DRU)	Two or more DRUs combined	Tone-spread	802.11bn (Wi-Fi 8)	Multiple far stations served in one PPDU

Sample interview questions

An access point on an 80 MHz Wi-Fi 6 channel needs to serve 24 IoT sensors sending short 100-byte status frames. Which OFDMA resource-unit configuration is most efficient?
- A. Partition the 80 MHz channel into 26-tone RUs, scheduling many sensors into one transmission so each gets a small slice instead of contending individually for the full channel. ✓
- B. Allocate a 996-tone RU to each sensor in sequence, since the wider RU delivers higher peak rate per device.
- C. Disable OFDMA and rely on CSMA/CA contention so each sensor wins channel access on its own.
- D. Use only 484-tone RUs because they match the 40 MHz subchannel boundaries.
Option A is correct. For many small-packet clients, partitioning the channel into small (26-tone) RUs lets the access point schedule dozens of stations into a single transmission window. Each sensor gets a small frequency slice that exactly fits its 100-byte payload, and contention overhead collapses because the AP centrally schedules the airtime via OFDMA trigger frames. Option B is wrong because allocating a full 996-tone RU per sensor wastes 99 percent of the bandwidth on a short payload and serializes 24 transmissions back to back — the opposite of what OFDMA is designed for. Option C is wrong because pure CSMA/CA scales poorly with 24 contending clients; collision and back-off overhead dominate. Option D is wrong because 484-tone RUs are sized for moderate-throughput single clients, not for many tiny payloads. The 26-tone RU is purpose-built for this case.
A wireless engineer is comparing DRU and RRU for an 802.11bn (Wi-Fi 8) deployment in a large warehouse. What is the strongest argument for using DRU rather than RRU on the far edges of coverage?
- A. DRU spreads the data subcarriers across the full PPDU bandwidth, delivering a power-boost gain that lifts the link budget for far stations at the cost of fewer simultaneous OFDMA users per transmission. ✓
- B. DRU and RRU have identical link-budget behavior; the choice is purely a vendor preference.
- C. DRU supports unlimited spatial streams while RRU is capped at one stream per station.
- D. DRU eliminates the need for an OFDMA trigger frame because each station chooses its own subcarriers.
Option A is correct. The defining property of a Distributed Resource Unit is that its data subcarriers are spread across the transmission bandwidth instead of being grouped contiguously. The spreading produces a power-boost coverage gain that helps far stations at the edge of the cell, which is precisely the warehouse-aisle use case. The trade-off is that DRU limits the number of spatial streams and reduces simultaneous OFDMA user count — so RRU remains the right choice for near stations. Option B is wrong because DRU and RRU have explicitly different link-budget profiles; that is why both exist in 802.11bn. Option C is wrong because DRU constrains spatial streams more tightly than RRU, not less. Option D is wrong because OFDMA uplink scheduling still requires a trigger frame regardless of whether the RUs are distributed or contiguous; the scheduling protocol does not change.
In uplink OFDMA, why does the access point send a trigger frame before stations transmit on their assigned resource units?
- A. The trigger frame synchronizes the transmit start time, RU assignment, modulation, and transmit-power target across all participating stations so their simultaneous uplink transmissions arrive at the AP aligned in time and frequency. ✓
- B. The trigger frame is a security mechanism that prevents unauthorized stations from transmitting.
- C. The trigger frame is optional and most APs skip it in favor of CSMA/CA.
- D. The trigger frame increases the modulation order to 4096-QAM for every station regardless of channel state.
Option A is correct. Uplink OFDMA cannot rely on each station independently winning CSMA/CA back-off — the entire point is that multiple stations transmit at the same time on disjoint subcarriers. The trigger frame from the AP synchronizes the start time, tells each station which resource unit to occupy, specifies the MCS to use, and signals a target transmit-power adjustment so all uplink signals arrive at the AP at comparable received levels. Without the trigger frame, simultaneous uplink would collide. Option B is wrong because the trigger frame is a scheduling and synchronization mechanism, not a security check. Option C is wrong because the trigger frame is the defining mechanism that makes uplink OFDMA possible; CSMA/CA is the alternative single-user access mode it replaces for scheduled multi-user uplinks. Option D is wrong because the MCS in the trigger frame is per-station and depends on channel conditions; 4096-QAM is rarely the assigned MCS in real deployments and is band/SNR-dependent.
A new graduate says "OFDMA is just OFDM with more users." How would you correct this in an interview?
- A. OFDM is a single-user waveform — one transmission per symbol burst. OFDMA adds resource-unit scheduling, an uplink trigger-based access mode, and a multi-user MAC framework so the AP can serve many stations in one transmission. The waveform is similar; the access framework is fundamentally different. ✓
- B. The statement is correct as written; OFDMA and OFDM are interchangeable terms.
- C. OFDMA only differs from OFDM in that it uses higher modulation orders.
- D. OFDMA replaces OFDM entirely and is incompatible with OFDM clients on the same access point.
Option A is correct. The waveform mechanics (orthogonal subcarriers, IFFT-based modulation) are inherited from OFDM, but OFDMA adds: resource-unit allocation per station, a trigger-frame uplink protocol so multiple stations transmit at the same time on disjoint RUs, MAC-layer scheduling integrated with the resource grid, and trigger-based access categories. None of those exist in single-user OFDM. Option B is wrong because OFDM and OFDMA differ at the access framework level; calling them interchangeable misses every engineering point. Option C is wrong because modulation order is independent of multi-user access; OFDM also supports high modulation orders. Option D is wrong because OFDMA-capable access points still support OFDM-only clients (e.g., legacy Wi-Fi 4 and Wi-Fi 5 stations); modern APs interoperate with mixed-generation fleets on the same channel.

Frequently asked questions

What are OFDMA resource units in IEEE 802.11ax (Wi-Fi 6) and how are they sized?: OFDMA in 802.11ax divides each channel into Resource Units (RUs), where each RU is a contiguous block of subcarriers. The defined sizes are 26-tone (roughly 2 MHz), 52-tone, 106-tone, 242-tone (a full 20 MHz channel), 484-tone (40 MHz), and 996-tone (80 MHz). A 160 MHz channel uses two 996-tone allocations. The access point scheduler maps stations to RUs based on traffic load, packet size, and channel quality — small RUs are efficient for low-rate clients and small frames, while larger RUs serve high-throughput clients. The RU partitioning is what makes OFDMA different from OFDM in earlier Wi-Fi generations: instead of one station per transmission, the AP can serve many in a single OFDM symbol burst.
What is the difference between a Regular Resource Unit (RRU) and a Distributed Resource Unit (DRU)?: A Regular Resource Unit (RRU) is the traditional contiguous tone allocation defined since IEEE 802.11ax — the data subcarriers are grouped together in adjacent frequency slots. A Distributed Resource Unit (DRU) is a new tone allocation in IEEE 802.11bn (Wi-Fi 8) where the data subcarriers are spread across the entire transmission bandwidth instead of being contiguous. DRUs provide a power-boost coverage gain because energy is spread across more frequency, which helps far stations at the edge of coverage. The trade-off is that DRUs limit the number of spatial streams and reduce how many simultaneous OFDMA users an AP can serve, so they are not a free upgrade — they are an adaptive choice for range-limited links.
What is a Multiple DRU (MDRU) and why does 802.11bn add it on top of DRU?: Multiple DRU (MDRU) refers to an allocation where more than one DRU is used in the same transmission, typically to serve more than one far station simultaneously while still capturing the power-boost coverage gain of the distributed tone pattern. MDRU is part of the 802.11bn (Wi-Fi 8) toolset for ultra-high reliability: instead of forcing the AP to choose between coverage (DRU) and multi-user efficiency (RRU), MDRU lets a deployment combine multiple distributed allocations in one PPDU. The cost is preamble and signaling complexity — the receivers need to decode which DRU pattern they are assigned to.
How does the OFDMA scheduler decide which station gets which resource unit?: The OFDMA scheduler at the access point weighs several factors: per-station traffic queue depth, packet size, channel state information per subcarrier, modulation and coding scheme the station can support, and access category (voice / video / best-effort / background) for QoS. A typical scheduling pass groups small-packet clients into smaller RUs (26-tone or 52-tone) so dozens of stations can share one transmission, while a high-throughput single client may take a 242-tone or 484-tone allocation alone. The scheduler also considers fairness — long-starved low-rate stations are promoted to avoid airtime starvation. The specific algorithm is a vendor implementation choice; the standard defines the RU framework but not the scheduling policy.
How does OFDMA differ from MU-MIMO, and when does an access point use each?: OFDMA partitions the channel in the frequency domain into resource units and serves multiple stations on disjoint sub-bands in one transmission. MU-MIMO partitions in the spatial domain and serves multiple stations on the same frequency at the same time using independent spatial streams. They solve different problems. OFDMA is best for many small-packet clients (low latency, fairness, contention reduction). MU-MIMO is best for fewer high-throughput clients with high SNR and good CSI (raw aggregate throughput). Modern Wi-Fi 6 and Wi-Fi 7 access points use both: OFDMA for the uplink where many clients contend, and MU-MIMO for the downlink to capable high-rate clients. A strong interview answer separates the two before comparing.
Why does the IEEE 802.11bn (Wi-Fi 8) tone allocation surface get its own interview question category?: Because Wi-Fi 8 introduces engineering choices that did not exist in earlier amendments. The split between RRU, DRU, and MDRU forces deployment decisions about who gets coverage gain versus who gets multi-user efficiency. The UHR-LTF training field that supports the new RU types must coexist with EHT-LTF for backward compatibility with Wi-Fi 7 clients. The scheduler now has more degrees of freedom (which RU type, which power profile, which spatial stream count). Candidates who can navigate this surface — even at the level of "DRU is for far stations, RRU is the default, MDRU combines both" — are demonstrating the kind of mechanism-level reasoning that distinguishes wireless systems engineers from feature memorizers.
What common mistakes do new graduates make when explaining OFDMA in interviews?: The most common mistake is calling OFDMA "OFDM with multiple users" — which is technically true but skips the engineering content. OFDMA introduces resource-unit allocation, scheduling, and trigger-based uplink access, none of which exist in single-user OFDM. A second mistake is confusing OFDMA with MU-MIMO. A third is assuming that more users in an OFDMA transmission always means lower per-user throughput; the better framing is that OFDMA trades per-user peak rate for aggregate efficiency under contention. A fourth is forgetting that uplink OFDMA requires the access point to send a trigger frame so all the stations transmit at the same time on their assigned RUs — uplink scheduling is centrally controlled, not contended.

Essential AI-Native Skills for OFDMA Resource Units Explained (IEEE 802.11ax / 802.11bn)

Modern engineering work increasingly uses AI tools for design and code review, debugging, documentation, test and testbench generation, and workflow automation. The goal is not to let AI replace engineering judgment — it is to move faster while keeping verification discipline.

Use AI to explain unfamiliar code, logs, waveforms, datasheets, or test failures.
Break large problems into small, reviewable steps you can verify independently.
Ask AI for hypotheses, then validate them against tests, measurements, simulations, or lab data.
Version-control your analysis scripts, testbenches, and configs — keep changes small and reviewable.
Document your assumptions, design tradeoffs, and debugging decisions.
Verify AI output before trusting it: run the checks that fit the domain — unit tests, linters, simulations, or bench/lab measurements.
Review AI output for correctness, edge cases, and real-world consequences.

OFDMA Resource Units Explained (IEEE 802.11ax / 802.11bn) — coming to the question bank

The adaptive practice engine is already live for core wireless, RF, and ML systems. OFDMA Resource Units Explained (IEEE 802.11ax / 802.11bn) isn't covered in the question bank yet — get notified when it's added.