BLER
Understanding BLER
In LTE/5G NR, data is transmitted in transport blocks. Each block is encoded with CRC and LDPC (5G) or Turbo (LTE) FEC. The receiver decodes the block and checks CRC. If CRC fails, the block is declared in error (NACK sent via HARQ). The transmitter retransmits, and the receiver combines both attempts (incremental redundancy or chase combining). After HARQ, residual BLER drops to <0.1%.
The eNB/gNB uses CQI feedback from the UE to select the MCS (Modulation and Coding Scheme) that achieves the target BLER. Too aggressive MCS causes high BLER and retransmission overhead; too conservative wastes spectral efficiency.
After HARQ (max 4 retx in LTE):
Residual BLER < BLERinitialNretx+1
10% initial, 3 retx: <10−4
BLER Targets by Service
| Service | Initial BLER | After HARQ | Latency |
|---|---|---|---|
| eMBB | 10% | <0.1% | ~4 ms |
| VoNR | 1% | <0.01% | ~10 ms |
| URLLC | 10−5 | 10−6 | <1 ms |
Frequently Asked Questions
BLER vs BER?
BER counts bit errors. BLER counts block failures. 10% BLER = 1 in 10 blocks fails initial decode. HARQ retransmission drops residual to <0.1%.
Why 10%?
Maximizes spectral efficiency. Aggressive MCS + HARQ recovery is more efficient than conservative MCS at 1% BLER. URLLC uses 10−5 for reliability.
How measured?
UE reports CQI based on SINR. Network selects MCS for target BLER. Measured via HARQ ACK/NACK ratios. CQI updated every 1-5 ms.