Description
A Sequence Number (SN) is a critical field in many 3GPP layer 2 and layer 3 protocols, providing a mechanism to impose order on a stream of data units. It is a counter, typically incremented for each new packet or Service Data Unit (SDU) submitted for transmission. The primary role of the SN is to allow the receiver to reconstruct the original order of packets, which may arrive out-of-sequence due to network conditions like multi-path routing or radio link layer retransmissions. Furthermore, by detecting gaps or repeats in the sequence, the receiver can identify lost or duplicate packets, triggering retransmission requests in reliable protocols.
In the architecture of radio access networks, SNs are employed extensively. For example, in the Packet Data Convergence Protocol (PDCP) layer (specified in 36.323 for LTE and 38.323 for NR), a PDCP SN is assigned to each data packet. This SN is used for in-sequence delivery to the upper layers, duplicate detection, and as a basis for ciphering and integrity protection. Similarly, the Radio Link Control (RLC) layer uses its own RLC SN for segmentation, reassembly, and Automatic Repeat Request (ARQ) operations. In the core network, sequence numbers appear in signaling protocols to ensure the correct order of operations.
The operation relies on the sender and receiver maintaining state about the expected sequence numbers. The receiver acknowledges received packets, often using the SN, allowing the sender to discard successfully delivered data from its buffers. The size of the SN field (e.g., 12-bit, 18-bit) determines the maximum window of packets that can be 'in flight' before wraparound occurs, which is a key factor in link efficiency and throughput, especially over high-latency connections.
Purpose & Motivation
The Sequence Number is a fundamental concept borrowed from computer networking and adapted to meet the stringent reliability and efficiency requirements of cellular systems. In early mobile networks, as data services emerged, the simple, connection-oriented circuits of voice calls were insufficient. Packet-switched data introduced the problems of out-of-order delivery, packet loss, and the need for efficient retransmission over unreliable radio links. The SN provides a lightweight yet powerful tool to manage these issues.
It solves the core problem of maintaining data integrity and order across the air interface, where conditions are highly variable. Without sequence numbers, higher-layer protocols like TCP would bear the full burden of recovery, which is inefficient over the radio link due to its different error characteristics. By implementing SN-based mechanisms at the radio link layer (RLC) and the convergence layer (PDCP), 3GPP systems can perform localized retransmissions and reordering, hiding radio-induced impairments from upper layers and significantly improving overall throughput and latency. Its creation was motivated by the need for a robust data delivery service over the inherently challenging wireless medium.
What changed in its specifications
The latest release-to-release comparison of specifications that define SN. Each summary describes the whole specification, not only this term.
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 →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.
Introduced in the context of UMTS Radio Access Network protocols. Sequence Numbers were fundamental to the new Radio Link Control (RLC) layer specified in 25.322, enabling acknowledged, unacknowledged, and transparent data transfer modes for the packet-switched domain, a cornerstone for 3G data services.
Defining Specifications
3GPP specifications that define or reference SN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 read |
| TS 25.322 vj00 | RLC Protocol Specification | Rel-19 read |
| TS 26.110 vj00 | 3G-324M Multimedia Codecs for Circuit Switched Networks | Rel-19 read |
| TS 33.224 vj00 | Generic Push Layer (GPL) Specification | 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.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 36.463 vj00 | XwAP Protocol Specification | 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.415 vj10 | PDU Session User Plane Protocol | Rel-19 read |