NPUs Run OFDM Baseband Without Baseband Chips

Recasting radio operators as dense matrix and vector kernels enables a full 3.0 GHz OFDM link on Ascend edge NPUs.

Editorial Desk·July 12, 2026·5 min readstrong

Underlying Paper

AI-RAN on NPUs: Baseband Processing Without Baseband Chips

AI-RAN aims to unify artificial intelligence and radio access network workloads on a shared compute substrate. While this paradigm has so far been demonstrated primarily on Graphics Processing Units (GPUs), it remains unclear whether Neural Processing Units (NPUs), which are AI accelerators optimized for inference, can also support wireless baseband processing. Here, we provide the first affirmative answer by resolving the fundamental mismatch between baseband workloads and NPU architecture. A computational isomorphism exists: matrix and vector engines NPUs dedicate to inference inherently cover physical-layer operations. Yet NPU architectures are natively shaped for dense-tensor AI inference, not baseband. This architectural mismatch surfaces as opposing optimization objectives: traditional baseband minimizes arithmetic operations, whereas NPU performance demands maximizing engine utilization. We close this gap by reconstructing communication algorithms onto AI compute primitives, prioritizing engine utilization over arithmetic count. We validate this with a complete OFDM transceiver on an Ascend 310B1 edge NPU, demonstrating end-to-end over-the-air transmission via USRP X300 at 3.0 GHz.

arXiv:2607.04224Submitted: Jul 5, 2026v1

AI-RAN assumes that radio access networks and AI workloads can share compute, but most demonstrations have treated GPUs as the common substrate. This paper asks a narrower hardware question: can an inference-oriented NPU execute wireless baseband processing directly, rather than serving only neural models around the radio stack? The authors answer with a full OFDM transceiver on Huawei Ascend 310B1 NPUs, using USRP X300 devices only as RF front ends.

The paper’s central claim is that AI and baseband workloads share enough matrix-and-vector structure to run on the same NPU engines. Figure 1 frames that claim as computational isomorphism: attention maps, neural weights, OFDM spectra, QAM constellations, and signal waveforms all reduce to primitives that can be scheduled on matrix and vector units.

Figure 1. Two paradigms for realizing AI-RAN. Top: GPU-based AI-RAN (left) integrates AI-on-RAN, AI-and-RAN, and AI-for-RAN within a centralized, high-power server infrastructure, benefiting from the maturity of GPU software ecosystems, but limiting energy efficiency and large-scale edge deployment. NPU-based AI-RAN (right) distributes the same three functionalities across edge devices by exploiting the energy efficiency, inference-optimized compute engines, and high compute density of NPU hardware. Bottom: enabling principle. AI operators, such as attention maps, neural networks, and quantized weights, and communication operators, such as signal waveforms, QAM constellations, and OFDM spectra, can both be expressed as matrix and vector primitives executed on common NPU engines. We refer to this shared computational structure as computational isomorphism.

Core Contribution

The contribution is not that OFDM can be implemented in software; CPUs, DSPs, FPGAs, and GPUs already do that. The new part is the NPU-native rewrite. Traditional baseband code tries to minimize arithmetic count, for example by preferring an FFT butterfly with O(NlogN)O(N \log N) work over an explicit DFT matrix with O(N2)O(N^2) work. On an NPU, that choice can be wrong: a lean algorithm may starve the matrix engine, while a denser formulation fills the hardware.

The authors turn that mismatch into a design rule. Linear baseband operators are restored into matrix form for the Cube engine, nonlinear operators are rewritten as arithmetic chains for the Vector engine, and adjacent operators are fused when intermediate tensors would otherwise round-trip through external memory.

Technical Approach

The implementation maps representative transmit and receive operators onto AscendC kernels. FFT and IFFT become batched DFT matrix multiplications. RRC filtering becomes a Toeplitz matrix multiplication. LDPC encoding and decoding are lifted from bitwise GF(2) operations into int8 generator-matrix multiplication followed by modulo-2 reduction. Least-squares channel estimation is precomputed as a matrix multiplication rather than per-subcarrier division.

For nonlinear pieces, the authors avoid lookup-heavy or scalar-control formulations that fit CPUs better than NPUs. Frame synchronization becomes batched energy detection plus cross-correlation. CFO estimation uses parallel cyclic-prefix autocorrelation. CFO compensation is rewritten from per-sample trigonometric evaluation into a recursive phasor and angle-sum update, keeping the work on vector units. QAM modulation becomes a truncated-scale arithmetic chain; QAM demodulation uses quantize-clamp plus scalar bit extraction.

The other major rewrite is on-chip pipeline fusion. The paper uses LS channel estimation followed by ZF equalization as the example: the channel estimate is produced, consumed, and discarded within one fused kernel. Similar stride-level fusions remove layout conversion between pulse shaping and FFT input, modulation and transform input, and other neighboring stages. The point is practical: on NPUs, moving intermediate tensors through global memory can cost more than the arithmetic itself.

Figure 2 shows the measurement setup: two Orange Pi AI Pro boards, each with an Ascend 310B1 NPU, paired with USRP X300 radios and horn antennas to form a 3.0 GHz SISO over-the-air link.

Figure 2. Experimental setup. Two Orange Pi AI Pro single-board computers, each with an on-board Ascend 310B1 NPU, paired with USRP X300 software- defined radios and horn antennas to form a SISO over-the-air link at 3.0 GHz. All baseband processing executes on the NPUs; the USRPs serve only as RF front-ends.

Results and Analysis

The benchmark compares the same baseband algorithm, with matched matrix dimensions, across an 8 W NPU, a 25 W GPU, a 125 W x86 CPU, and the same-board ARM CPU. End-to-end latency is mixed if judged only in milliseconds: the NPU reaches 30.7 ms transmit and 46.2 ms receive, faster than the GPU at 65.1 ms and 110.2 ms and far faster than the ARM CPU at 255.9 ms and 536.1 ms, but not faster than the 125 W x86 CPU on transmit, where x86 reports 20.6 ms. The energy-normalized result is the stronger case. The NPU reaches 4.1 frames/W on transmit and 2.7 frames/W on receive, compared with 0.6 and 0.4 frames/W for the GPU and 0.4 and 0.1 frames/W for x86.

Operator-level results explain why this is not a blanket NPU win. Some kernels favor the NPU rewrite: receive CFO is 2.8 ms on NPU versus 32.0 ms on GPU and 26.5 ms on x86; RRC downsampling is 2.3 ms versus 12.0 ms and 4.6 ms. Others still favor x86, including transmit RRC upsampling at 2.2 ms on x86 versus 11.7 ms on NPU. The evidence therefore supports a more precise conclusion: NPUs can execute a complete OFDM physical layer efficiently when the algorithms are reformulated around engine occupancy and data movement, but the result depends on operator shape and low-level kernel access.

Caveats

The system is a real over-the-air demonstration, but it is still a narrow one: SISO, 5 MHz sampling, 64-QAM, LDPC(512,256), a 256-point FFT, and one Ascend NPU family with AscendC access. The authors also note that many mainstream NPUs expose only inference runtimes or partial engine access, which limits portability of the method. For radio and edge-AI engineers, the paper is most useful as a mapping recipe and feasibility result, not as proof that any NPU can replace dedicated baseband silicon in deployed RAN equipment.

Evidence Box

strong

Key Claims

  • Baseband operators can be mapped onto NPU matrix and vector engines
  • NPU-native rewrites favor engine occupancy over arithmetic minimization
  • On-chip fusion reduces data movement between adjacent OFDM operators
  • Edge NPUs can run a complete OFDM transceiver without baseband chips

Key Results

  • NPU end-to-end latency 30.7 ms TX and 46.2 ms RX, versus GPU 65.1 ms TX and 110.2 ms RX
  • NPU performance per watt 4.1 frames/W TX and 2.7 frames/W RX, versus GPU 0.6 and 0.4 frames/W
  • 3.0 GHz SISO over-the-air link using two Ascend 310B1 NPUs and USRP X300 RF front ends
  • Dataset includes 200 over-the-air capture frames with complex64 IQ samples and latency measurements across 4 platforms

Limitations & Caveats

  • Evaluation limited to SISO OFDM at 5 MHz sampling on one Ascend 310B1 NPU family
  • Requires kernel-level access to matrix and vector engines through AscendC
  • Several operators remain slower on NPU than x86, including transmit RRC upsampling
  • No deployment-scale multi-user, multi-antenna, or real-time RAN scheduler evaluation

Related Articles

Readers are encouraged to consult the original arXiv paper for complete details. SOTA Papers does not make claims beyond what is supported by the authors' reported evidence.