Description
The Retransmission Sequence Number (RSN) is a fundamental mechanism within the data retransmission protocols of the 3GPP radio interface, specifically in the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer. Its primary function is to uniquely identify data packets (or segments) that are eligible for or undergoing retransmission, enabling orderly and efficient recovery from transmission errors.
In architecture, both PDCP and RLC layers manage the transmission of data between the UE and the base station (gNB/eNB). They employ acknowledgment-based protocols (like RLC Acknowledged Mode (AM)) to ensure reliability. When a packet is transmitted, it is assigned a sequence number (SN). If the receiver fails to acknowledge it (due to error, loss), the packet may need retransmission. The RSN is a separate sequence space or a sub-field used specifically to track the retransmission instances of such packets. In some implementations, the RSN is a counter incremented each time a particular packet is retransmitted.
How it works: Upon initial transmission, a packet is sent with its primary SN. If a negative acknowledgment (NACK) is received or a timer expires, the transmitter schedules a retransmission. For this retransmission, the packet is marked with an RSN value (e.g., RSN=1 for first retransmission). The receiver uses this RSN to understand that this is a retransmission of a previously seen packet (identified by its primary SN). This helps the receiver in reassembly and deduplication. In protocols supporting multiple retransmissions (like HARQ at MAC or RLC), the RSN may increment with each retry, allowing both ends to track the retransmission count, which can be used for adaptive strategies like modifying modulation or power.
Its role in the network is critical for maintaining data integrity over the unreliable wireless channel. By clearly labeling retransmissions, the RSN prevents the receiver from misinterpreting a retransmitted packet as a new packet, which would cause duplication and sequence gaps. It also aids in buffer management at both transmitter and receiver. For the transmitter, tracking RSN helps implement retransmission limits and prioritize retries. For the receiver, it assists in correctly reordering packets before delivering them to higher layers. This mechanism is essential for services requiring high reliability, such as VoIP, online gaming, and critical IoT communications, ensuring seamless data flow despite intermittent radio errors.
Purpose & Motivation
The RSN concept exists to address the inherent unreliability of the wireless medium in mobile communications. Radio links suffer from fading, interference, and noise, causing packets to be lost or corrupted. To guarantee data delivery, retransmission protocols are necessary. However, simple retransmission without proper labeling leads to problems: the receiver might accept a retransmitted packet as a new, duplicate packet, corrupting the data stream; the transmitter might lose track of how many times a packet has been retried, potentially wasting resources on persistently failing packets.
Historically, early wireless data protocols used simple sequence numbers for ordering but lacked dedicated retransmission tracking. The introduction of RSN in 3GPP protocols (evident from Rel-6 onwards) provided a refined tool for managing retransmissions. It solved the duplication issue by allowing the receiver to distinguish between a new packet and a retransmission of an old packet, even if they carry the same user data. This is crucial for protocols like RLC AM, which may deliver large data blocks segmented into many packets.
The motivation was to enhance the efficiency and reliability of the radio link layer, especially as data rates and service demands increased with HSPA, LTE, and 5G. By incorporating RSN, the protocols could support more sophisticated retransmission strategies, including incremental redundancy (where retransmissions send complementary encoding) and adaptive retransmission based on count. It also facilitates clearer status reporting (e.g., in RLC status reports) and better radio resource management. Ultimately, RSN is a key component enabling the high reliability and quality of service that modern cellular data services provide, even under challenging radio conditions.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the RSN (Retransmission Sequence Number) function was newly introduced as a core parameter for establishing end-to-end redundant user plane paths using Dual Connectivity. The UE can now include an RSN and/or a PDU Session Pair ID in the PDU Session Establishment Request, with the value determined either by UE local mechanisms or from matched URSP rules. This RSN parameter, provided to the NG-RAN by the SMF, explicitly indicates the requirement for redundant user plane resources on a per-PDU Session basis, enabling the RAN to set up dual connectivity for fully disjoint paths.
- PDU session associating with PDU session pair ID and RSN TS 24.501CR3919
- Support of RSN and PDU Session Pair ID in the URSP Rule TS 29.525CR0181
- Inclusion of PDU session pair ID and/or RSN in PDU session establishment request TS 24.526CR0133
- Referenced clause numbers for PDU session pair and RSN TS 24.526CR0138
Explore further
Broader topics and technologies where RSN plays a role.
Defining Specifications
3GPP specifications that define or reference RSN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.725 vg20 | Study on URLLC Architecture Enhancements | Rel-16 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.526 vj30 | UE Policies for 5GS; Stage 3 | Rel-19 |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 |
| TS 25.309 v1600 | FDD Enhanced Uplink Support | Rel-6 |
| TS 25.319 vj00 | Enhanced Uplink for UTRA FDD/TDD | Rel-19 |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.705 vd00 | UMTS Small Data Transmission Enhancements Study | Rel-13 |
| TS 27.007 vj40 | AT Command Set for UE | Rel-19 |
| TS 29.502 vj50 | 5G System; Nsmf Service Based Interface; Stage 3 | Rel-19 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |
| TS 29.561 vj30 | 5G Interworking with External Data Networks | Rel-19 |
| TS 38.413 vj10 | NG Application Protocol (NGAP) | Rel-19 |
| TS 38.423 vj10 | Xn Application Protocol (XnAP) specification | Rel-19 |
| TS 48.018 vj00 | BSS-SGSN Interface for GPRS Control | Rel-19 |