Description
The Residual Error Rate (RER) is a fundamental Quality of Service (QoS) parameter defined in 3GPP TS 21.905 and TS 22.060 that characterizes the accuracy of a bearer service. It measures the frequency of Service Data Units (SDUs) that are lost, corrupted, or duplicated when delivered at the user-network interface. Unlike other error metrics that focus on the radio link, RER captures end-to-end errors that remain after all error detection and correction mechanisms have been applied, including CRC checks, ARQ retransmissions, and HARQ combining. This makes it a critical parameter for applications that cannot tolerate undetected data corruption.
In the 3GPP architecture, the Residual Error Rate is defined at the boundary between the user equipment and the network, specifically at the user-network interface. This positioning is significant because it encompasses the entire protocol stack from the application layer down through the radio protocols. The parameter accounts for errors introduced at any layer that are not caught by lower-layer error detection mechanisms. For example, if a transport block passes CRC validation but contains bit errors that escape detection, those errors contribute to the residual error rate. Similarly, if an SDU is lost due to buffer overflow or discarded due to protocol errors, this also contributes to the metric.
The RER is typically expressed as a ratio or percentage of erroneous SDUs to total SDUs transmitted over a measurement period. The exact measurement methodology depends on the specific bearer service and the QoS class it belongs to. For conversational and streaming services, which are delay-sensitive, the RER requirements are typically more stringent than for background or interactive services. The parameter works in conjunction with other QoS parameters such as transfer delay, delay variation, and bit error rate to fully characterize the service quality.
From an implementation perspective, measuring RER requires instrumentation at the SDU delivery points in both the transmitting and receiving entities. The transmitting side must maintain a record of SDUs passed down to the bearer service, while the receiving side must track SDUs delivered up to the application. Discrepancies between these counts, after accounting for legitimate protocol operations, yield the residual error rate. In practice, this measurement is often performed using test equipment or specialized QoS monitoring functions embedded in the network.
The Residual Error Rate has been part of 3GPP specifications since Release 4 and has remained remarkably stable in its definition across all subsequent releases through Release 19. This stability reflects the fundamental nature of the parameter and its independence from specific radio access technologies. Whether the bearer service is implemented over GERAN, UTRAN, E-UTRAN, or NR, the concept of residual errors at the user-network interface remains constant. This makes RER a valuable metric for comparing QoS across different generations of mobile networks.
Purpose & Motivation
The Residual Error Rate parameter exists to provide a standardized, technology-agnostic measure of service accuracy for bearer services in 3GPP networks. Before its introduction, QoS characterization focused primarily on throughput and delay, with error performance often described in vague or vendor-specific terms. This made it difficult for operators to guarantee specific error performance levels to application providers and end users, and equally difficult for application developers to design services that would perform reliably across different networks and radio technologies.
The RER addresses the fundamental question: after all error correction mechanisms have done their work, how many errors remain? This is crucial for applications such as file transfer, database synchronization, and certain industrial control applications where undetected data corruption can have serious consequences. By defining this parameter precisely and requiring its support in bearer service specifications, 3GPP enabled the creation of Service Level Agreements (SLAs) that include quantitative error performance guarantees.
The parameter also serves as a design target for radio protocol engineers. When developing new radio access technologies or enhancing existing ones, engineers must ensure that the residual error rate meets the requirements of the services that will use the technology. This has driven innovations in error detection codes, retransmission protocols, and cross-layer optimization techniques. The stability of the RER definition across releases demonstrates its enduring value as a foundational QoS concept.
What changed in its specifications
The latest release-to-release comparison of specifications that define Residual error rate. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 22.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 22.060 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced in TS 21.905 and TS 22.060 as 'A parameter describing service accuracy. The frequency of lost SDUs, and of corrupted or duplicated network SDUs delivered at the user-network interface.' This established the fundamental concept and measurement point for the parameter.
Defining Specifications
3GPP specifications that define or reference Residual error rate, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.060 vj00 | GPRS Stage 1 Service Description | Rel-19 read |