Residual Bit Error Ratio

Description

Residual Bit Error Ratio is defined as the ratio of erroneously received bits to the total number of transmitted bits, measured after the Forward Error Correction (FEC) decoder at the receiver. It is a post-decoding metric, in contrast to the Raw BER measured before decoding. RBER provides a direct measure of the link's delivered data integrity. In 3GPP systems, the physical layer employs channel coding (e.g., Turbo codes, LDPC codes) and interleaving to protect data blocks (transport blocks) against channel impairments like noise, interference, and fading. The receiver decodes these blocks, and any bits that cannot be corrected constitute the residual errors.

The calculation of RBER typically involves cyclic redundancy check (CRC) verification. Each transport block is appended with a CRC at the transmitter. After decoding at the receiver, the CRC is recalculated and compared. If the CRC check fails, the entire block is considered in error and may be requested for retransmission via HARQ. However, RBER estimation for successfully CRC-checked blocks can involve more sophisticated techniques, as these blocks may still contain undetected errors. System specifications often define target RBER values for different services and channel conditions, which drive the selection of modulation and coding schemes (MCS).

RBER is a fundamental input to the link adaptation algorithm, which dynamically selects the optimal MCS for current radio conditions. A high RBER indicates that the current MCS is too aggressive (e.g., high-order modulation with a weak code rate) for the channel, prompting a shift to a more robust scheme. Conversely, a consistently low RBER may allow the use of a higher-rate MCS to improve spectral efficiency. RBER targets vary by service: for example, control signaling requires an extremely low RBER (e.g., 10^-6), while some background data traffic may tolerate a higher RBER. Monitoring RBER over time also provides valuable data for network optimization and performance troubleshooting.

Purpose & Motivation

RBER exists as a critical quality metric to evaluate the performance and reliability of the digital communication link after error correction. Its primary purpose is to quantify the effectiveness of the physical layer's FEC coding and to ensure that the delivered data meets the error rate requirements of the higher-layer service or application. Without measuring RBER, the network would have no objective way to assess whether the chosen modulation and coding scheme is providing the intended level of data integrity, potentially leading to unacceptable packet loss or corrupted information for sensitive services.

The concept was formally defined in 3GPP Release 4, aligning with the enhancement of packet data capabilities in UMTS. It addressed a key limitation of simply measuring raw, pre-decoding BER, which does not reflect the performance gain provided by powerful channel codes like Turbo codes introduced in 3G. RBER provides a more accurate picture of the user-perceived link quality. It solved the problem of optimally matching the physical layer transmission parameters to the service requirements and instantaneous channel state, which is essential for efficient spectrum use in variable wireless environments.

As data rates and service diversity increased with HSPA, LTE, and 5G, the role of RBER became even more crucial. The introduction of advanced FEC like LDPC codes in 5G NR required precise RBER characterization to tune their performance. RBER targets are integral to the definition of QoS classes (e.g., through 5QI values) and are a key parameter in the design of link adaptation and outer-loop link adaptation algorithms, which are fundamental to achieving the high reliability and low latency goals of modern cellular systems.

Key Features

• Post-Decoding Error Measurement: Quantifies bit errors after FEC decoding, reflecting the net effectiveness of the channel code.
• Link Adaptation Input: Serves as a key metric for dynamic MCS selection to balance spectral efficiency and transmission reliability.
• Service-Specific Targets: Defined for different traffic types (e.g., voice, video, signaling) with varying error tolerance levels.
• Performance Monitoring: Used for network performance evaluation, optimization, and fault detection in the radio link.
• HARQ Interaction: Informs Hybrid ARQ processes; a high RBER on initial transmission may trigger a different redundancy version in a retransmission.
• QoS Parameter Mapping: Linked to higher-layer QoS parameters like SDU Error Ratio, influencing end-to-end service quality.

Evolution Across Releases

Defining Specifications