BBU (Baseband Unit)
Understanding the BBU
The BBU is the brain of the base station. While the RRU handles RF transmission and reception (analog domain), the BBU performs all the digital intelligence: deciding what data to send, how to encode it, which users get which resources, and when to retransmit failed packets. These decisions happen in real time, with scheduling decisions made every 0.5 ms (2,000 times per second).
Modern BBU hardware uses custom ASICs or FPGAs optimized for the computationally intensive operations of 5G NR: LDPC decoding (40 to 60% of processing load), FFT/beamforming (20 to 30%), and MAC scheduling (10 to 15%). A single BBU shelf can support an entire macro cell site with multiple frequency bands and technologies (LTE + NR).
BBU Processing Requirements
Rate = Nant × fs × 2(I/Q) × bsample × 10/8(coding)
2x2 MIMO, 20 MHz LTE: 2.46 Gbps
64T64R, 100 MHz NR: 157 Gbps (impractical)
eCPRI (Split 7-2x):
5–10 Gbps per cell (frequency-domain IQ)
10x reduction vs. CPRI
Processing per cell (100 MHz NR):
LDPC: ~500 GOPS
FFT: ~100 GOPS
Scheduling: ~50 GOPS
Total: ~650 GOPS per cell
BBU Evolution
| Generation | Architecture | Processing | Fronthaul |
|---|---|---|---|
| 3G/4G (traditional) | Monolithic BBU | Custom ASIC | CPRI |
| C-RAN (pooled) | BBU hotel | Custom ASIC | CPRI (fiber) |
| 5G O-RAN | CU + DU + RU | ASIC/FPGA/GPU | eCPRI |
| vRAN/Cloud RAN | COTS servers | x86 + accel. | eCPRI |
Frequently Asked Questions
What does the BBU process?
L1: LDPC/Polar coding, OFDM FFT, MIMO precoding. L2: scheduling (0.5 ms), HARQ, RLC. L3: PDCP ciphering, RRC, handover. 6 to 12 cells per card. 40+ Gbps throughput. LDPC = 40 to 60% of compute.
BBU-RRU connection?
CPRI: digitized IQ, 2.5 Gbps/cell (20 MHz LTE). 64T64R at 100 MHz = 157 Gbps (impractical). eCPRI: functional split 7-2x, 5 to 10 Gbps/cell. Max distance: 15 to 20 km (100 µs latency).
BBU pooling and vRAN?
Pooling: centralized BBU hotel serves distributed RRUs. 10 BBUs serve 15 to 20 cells via resource sharing. vBBU: COTS x86 with FlexRAN (AVX-512). Needs RT Linux, DPDK for 0.5 ms deadline.