5G NR Throughput Calculator
- Venkateshu Kamarthi

- Jun 12
- 2 min read
Overview:
A 3GPP-aligned, multi-layer throughput estimation tool covering the full gNB protocol stack from PHY to PDCP. Built for RF engineers, protocol testers, and RAN architects who need quick but specification-accurate numbers without opening a spreadsheet or reading 38.214 line by line.
Tool Features
4-layer protocol stack
Calculates throughput independently at PHY, MAC, RLC, and PDCP — each with its own overhead model per 3GPP specs, not a single flat deduction.
All three MCS tables
Supports 38.214 Table 1 (64-QAM), Table 2 (256-QAM), and Table 3 (low-SE / URLLC), with all 28–29 MCS indices per table and live Qm/R display.
TDD frame structure
Full 38.213 11.1-1 slot format library (formats 0- + custom), special slot symbol split, TDD periodicity, and real-time slot pattern visualizer.
FR1 + FR2 NRB lookup
Automatically resolves the correct NRB from the 38.101-1/2 bandwidth-SCS table. Invalid combinations are caught and flagged before calculation.
Carrier aggregation
Up to 8 component carriers, applied correctly at PHY before overhead — not as a post-multiplier — giving accurate CA throughput estimates.
Granular overhead control
DMRS type/config, PTRS, PDCCH/CSI-RS RE overhead, MAC CE %, scaling factor f, RLC AM/UM/TM mode, PDCP SN length, SDAP header — all individually tunable.
Protocol layer data flow

Daily 5G testing use cases
Expected throughput baselining
Before an RF drive test or lab KPI run, set the exact gNB config (BW, MCS, MIMO, TDD pattern) to get the theoretical ceiling. Any measured value above ~85–90% of PDCP throughput signals a well-functioning stack.
Layer-by-layer gap analysis
If PHY shows 800 Mbps but PDCP delivers 650 Mbps, the 18% gap points to RLC/PDCP misconfiguration (e.g. wrong SN length, AM retransmissions), not RF. The per-layer view isolates root cause fast.
TDD ratio optimization
Toggle between TDD slot formats (e.g. 8:1:5 vs 7:3:2) to quantify the DL/UL throughput trade-off before changing live network parameters — a change that would otherwise require CRQ and rollback risk.
MCS sanity check vs CQI feedback
Cross-check that the MCS index reported in UE logs (e.g. from QXDM/TEMS) matches what the network should be selecting for a given SINR. Spot scheduler issues without opening the 38.214 spec
Multi-CC aggregate target setting
For 5G NR carrier aggregation trials (2–5 CC), the tool computes the combined PDCP throughput target so test engineers know what iperf3 or FTP throughput to expect and when to flag an issue.
KPI report reference values
Include theoretical max throughput per layer alongside measured KPIs in test reports — gives reviewers and RAN vendors objective context when evaluating whether observed numbers are acceptable.
References
TS 38.214 Table 5.4.2.1 / 6.4.2.1 — PDSCH/PUSCH throughput formula, MCS tables 1/2/3, Qm and code rate per index
TS 38.213 Table 11.1.1-1 — TDD slot format configurations, DL/UL/Special symbol allocations per format index
TS 38.101-1/2 Table 5.3.2-1 — Allocated resource blocks NRB for each BW + SCS combination in FR1 and FR2
TS 38.321 / 38.322 / 38.323 — MAC CE subheader overhead, RLC AM/UM/TM header sizes, PDCP SN and SDAP header modeling




Comments