Description
Acknowledged Mode (AM) is a fundamental operational mode of the Radio Link Control (RLC) layer in 3GPP radio access networks (UTRAN, E-UTRAN, NG-RAN). It is also a mode used in the Packet Data Convergence Protocol (PDCP) layer, particularly for control plane data and for data radio bearers requiring reliability. Its primary function is to ensure the reliable, in-sequence delivery of upper layer protocol data units (PDUs) over the potentially error-prone air interface.
Architecturally, AM operates within the RLC entity established for a specific logical channel. An RLC entity in AM consists of a transmitting side and a receiving side. The transmitting side segments or concatenates Service Data Units (SDUs) from higher layers into RLC PDUs, which are then transmitted. Each PDU is assigned a sequence number. The receiving side uses these sequence numbers to detect missing PDUs and to reassemble SDUs in the correct order for delivery upward. Crucially, the receiving side sends status reports (ACK/NACK) back to the transmitter, indicating which PDUs were received correctly.
The mode works through a selective repeat Automatic Repeat Request (ARQ) mechanism. When the transmitting AM RLC entity receives a status report indicating a missing PDU, it retransmits that specific PDU. The transmitter maintains a transmit buffer to hold PDUs until they are positively acknowledged. Window-based flow control is used to manage the sequence number space and prevent buffer overflows. This process ensures that all data is delivered, albeit with variable latency due to retransmissions.
Key components include the sequence numbering scheme, the retransmission buffer, the status reporting mechanism (using RLC control PDUs), and the timers that trigger status reports and poll for acknowledgments. Its role is critical for signaling messages (RRC, NAS) and for user plane data that cannot tolerate loss, such as TCP/IP traffic. It provides the reliability that the underlying physical layer cannot guarantee, forming a crucial link in the end-to-end data integrity chain.
Purpose & Motivation
Acknowledged Mode was created to address the inherent unreliability of wireless communication channels. The physical layer alone, with its forward error correction (FEC), cannot guarantee 100% error-free packet delivery, especially at cell edges or under poor radio conditions. AM introduces a link-layer retransmission scheme to recover from these residual errors, solving the problem of packet loss for critical data.
Its motivation stems from the need to support a wide range of services with different reliability requirements. For applications like web browsing, file transfer, or signaling, packet loss leads to severe performance degradation at the transport layer (e.g., TCP timeouts). By providing reliable delivery at the RLC layer, AM improves overall network efficiency and user experience. It addresses the limitations of Unacknowledged Mode (UM), which offers no retransmissions and is unsuitable for error-sensitive traffic. The creation of AM was essential for making cellular data networks a viable platform for reliable IP-based services.
What changed in its specifications
The latest release-to-release comparison of specifications that define AM. 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 →Polling via POLL SUFI, flexible RLC PDU sizes in uplink, new primitive parameters for UM and AM, optional SN_Delivery configuration, altered SDU handling.
Full comparison in TS 25.322 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Formally specified as a core RLC mode in the 3GPP UMTS specifications (25.322). It established the fundamental procedures for segmentation, concatenation, retransmission, and in-sequence delivery that remain consistent through 4G and 5G, providing reliable data transfer for dedicated channels.
Defining Specifications
3GPP specifications that define or reference AM, 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 |
| TR 22.815 ve00 | Study on Multimedia Broadcast Supplement for PWS | Rel-14 read |
| TS 25.322 vj00 | RLC Protocol Specification | Rel-19 read |
| TS 25.331 vj01 | UTRAN Radio Resource Control Protocol | Rel-19 read |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 read |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 read |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 read |
| TS 29.519 vk10 | 5G UDR Policy and Application Data Services | Rel-20 read |
| TS 29.521 vk10 | Binding Support Management Service | Rel-20 read |
| TS 29.522 vk10 | NEF Northbound Interface | Rel-20 read |
| TS 32.859 vc10 | Alarm Management Quality Improvement Study | Rel-12 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 read |
| TS 36.322 vj00 | E-UTRA Radio Link Control Protocol Specification | Rel-19 read |
| TS 36.323 vj00 | PDCP Protocol Specification | Rel-19 read |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| TS 38.322 vj30 | NR Radio Link Control (RLC) Protocol Specification | Rel-19 read |
| TS 38.323 vj10 | PDCP Protocol Specification | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |