Retransmission Sequence Number

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.

Key Features

• Unique identifier for packets undergoing retransmission
• Prevents misinterpretation of retransmitted packets as new data at the receiver
• Enables tracking of retransmission count for adaptive transmission strategies
• Used in both PDCP and RLC layers for reliable data delivery
• Supports protocols like RLC Acknowledged Mode (AM) and HARQ processes
• Facilitates correct packet reordering and reassembly after retransmissions

Evolution Across Releases

Defining Specifications