This Page provides information about 5G NR TBS (Transport Block size) Calculator. Calculator is based on 3GPP 38.214 communication standards and allows you to calculate TBS depends on MCS (Modulation order, code rate), number of used PRB etc. Modulation Order and Code Rate are determined by tables: 38.214 Table 5.1.3.1-1 and Table 5.1.3.1-2. (depends on DCI, C-RNTI, MCS indexs).
Approximately TBS can be calculated using the formulas from 3GPP 38.214 chapter 5.1.3.2, where Ninfo – number of information bits:
Update1: UPDATE to Latest 3GPP Release
Update2: FIX Calculated Throughput (Added Numerology µ parameter)
Found a mistake? Contact us!
Was this information helpful?
Share with colleagues or use:
5G NR: 5G NR Throughput calculator, 5G NR Link budget calculator, 5G NR ARFCN Calculator, 5G NR GSCN Calculator, 5G NR TBS Calculator, Spectral Efficiency 5G NR calculator, 5G NR SSB SSS EPRE Power Calculator, 5G Neighbor planning calculator, QoS for 5G NR
4G LTE: 4G LTE Throughput calculator, 4G LTE Link budget calculator, 4G LTE EARFCN calculator, 4G LTE RS RE Power calculator, 4G LTE Users (CCE) calculator, 4G LTE Timing Advance Distance Calculator, 4G Neighbor planning calculator, QoS for 4G LTE
NB-IoT: NB-IoT Link budget calculator
Nre value seems to ambigous for values, for 12 and 11 ofdm symbols i see N(RE)=720 , when the number of symbols are increased number of RE should be increased accordingly
Dear, Abhilash!
I think it happend, because Calculator use Table 5.1.3.2-1: Quantized number of REs allocated for PDSCH within a PRB
from 3GPP 38.214 rel 15.0.0 ( it was deleted in later releases)
I will fix it soon
Regards, Oleg
Dear, Abhilash!
Fixed! Please Check!
Regards, Oleg
If I use 30 KHz sub carrier spacing for 100 MHz BW ( 273 PRBs), I can schedule all 273 PRBs in 0.5 ms slot.
So for this perspective, the max throughput should be twice the TBS. Please share your view.
Dear, Manoj!
You are right. Max throughput should be twice the TBS.
(if Numerology =2, 30 KHz)
Fixed it! I added Numerology µ parameter
Regards, Oleg
Hello! Could you explain why Ninfo, in the results, is always floored to an integer value?
The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than 0.95, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the number of physical channel bits on PDSCH.
Hi , thank U for your tool. But when N_info is less than 3824, TBS should be selected from the table, but it does not seem to be the case here.
Fixed, Can you check it?
Regards, Oleg
The spec says: use Table 5.1.3.2-1 find the closest TBS that is not less than N’info. So why for Ninfo=556 the calculator selects 552, not 576?