Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

RSN

Retransmission Sequence Number

Protocol →

RSN is the sequence number used in 3GPP radio link protocols to identify and order data packets for retransmission, enabling reliable delivery by tracking missing packets.

Introduced
Rel-6
Where
Radio Access Network › UTRAN (3G)
Specifications
19 specs
Also in
Core Network, User Equipment
RSN Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define RSN. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-17 4 changes
  • 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

Defining Specifications

3GPP specifications that define or reference RSN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.725 vg20 Study on URLLC Architecture Enhancements Rel-16 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.526 vk00 5GS UE Policies Rel-20 read
TS 25.222 vj00 UTRA TDD Multiplexing & Channel Coding Rel-19 read
TS 25.309 v660 FDD Enhanced Uplink Technical Specification Rel-6 read
TS 25.319 vj00 Enhanced Uplink for UTRA FDD/TDD Rel-19 read
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.705 vd00 UMTS Small Data Transmission Enhancements Study Rel-13 read
TS 27.007 vk00 AT Command Interface for Mobile Terminals Rel-20 read
TS 29.502 vk10 5G SMF Service Based Interface Stage 3 Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.423 vj40 NG-RAN Xn Application Protocol Rel-19 read
TS 48.018 vj00 BSS-SGSN Interface for GPRS Control Rel-19 read