Description
Error Indication (EI) is a primitive defined within the 3GPP protocol architecture, specifically in the context of the Service Access Points (SAPs) between protocol layers. It is a control primitive, not a user data primitive, used to convey that a lower layer has detected an unrecoverable error condition related to a specific instance of a service or connection. When a lower layer (e.g., the Radio Link Control (RLC) layer) encounters a severe failure, such as a maximum number of retransmissions being exceeded or a radio link failure, it generates an EI primitive and passes it up to the higher layer (e.g., the Packet Data Convergence Protocol (PDCP) layer or Radio Resource Control (RRC) layer). This primitive contains parameters identifying the affected entity, such as a Radio Bearer identity or a Signaling Radio Bearer identity.
The reception of an Error Indication triggers specific recovery actions in the higher layer. For instance, in LTE and 5G NR, if the RLC layer sends an EI for a data radio bearer, the PDCP layer may initiate a re-establishment procedure for that bearer. For signaling radio bearers, the RRC layer might interpret the EI as a radio link failure and initiate connection re-establishment procedures. The EI mechanism is crucial for maintaining service continuity and robustness, as it allows the network and the User Equipment (UE) to react promptly to deteriorating link conditions.
The specification of the EI primitive, including its parameters and the precise conditions for its generation, is detailed in 3GPP TS 26.110 and other layer-specific specifications. Its implementation is integral to the layered protocol design, providing a standardized way for layers to communicate fault conditions without being tightly coupled. This abstraction is key to the modularity and maintainability of the 3GPP protocol stack.
Purpose & Motivation
The Error Indication primitive was introduced to provide a standardized, unambiguous method for lower protocol layers to report critical, unrecoverable failures to higher layers. Prior to such formalized mechanisms, error handling could be ad-hoc or implementation-dependent, leading to interoperability issues and unpredictable behavior during network failures. The EI primitive creates a clear contract between protocol layers, defining the conditions under which an error is reported and the expected response from the receiving layer.
Its creation was motivated by the need for robust mobility and session management in packet-switched cellular networks like LTE and 5G NR. As these networks support real-time services and high-reliability communications, rapid detection and recovery from link failures are paramount. The EI mechanism enables swift escalation of problems, allowing higher-layer procedures (like handover, bearer reconfiguration, or connection re-establishment) to be triggered efficiently, minimizing service interruption and preserving user experience.
Key Features
- Standardized primitive for inter-layer error reporting
- Triggers higher-layer recovery and re-establishment procedures
- Carries identifiers for the affected protocol entity (e.g., Radio Bearer ID)
- Indicates unrecoverable lower-layer failures
- Fundamental to radio link failure detection and handling
- Defined for both control-plane and user-plane protocol stacks
Evolution Across Releases
Initially introduced in LTE specifications as a core primitive within the protocol layer Service Access Point definitions. It was defined for layers like RLC to report irrecoverable errors to PDCP and RRC, forming the basis for radio link failure procedures and bearer management in the new EPS architecture.
Defining Specifications
| Specification | Title |
|---|---|
| TS 26.110 | 3GPP TS 26.110 |