3GPP Releases: Which One Does Your Feature Need?

How 3GPP Releases Work

The 3rd Generation Partnership Project (3GPP) develops mobile telecommunications standards through a structured release process. Each release bundles a set of features that are frozen (functionally complete) on a published date, after which only corrections are allowed. New features go into the next release.

A release progresses through three phases: Study Item (SI) phase where feasibility is assessed via Technical Reports (TR documents), Work Item (WI) phase where normative specifications are written (TS documents), and Freeze where functional specifications are locked. After freeze, ASN.1/protocol coding is completed in a subsequent stage.

Understanding the release timeline is essential because operator RFP requirements, chipset capabilities, and device certifications all reference specific releases. A "Rel-17 compliant" device supports a different feature set than a "Rel-18" device, with concrete implications for throughput, latency, and capability.

The Complete Release Timeline

LTE Era: Releases 8-14

Release 8 established the LTE foundation: OFDMA downlink, SC-FDMA uplink, flat all-IP architecture with eNB and EPC. The design targeted 100 Mbps DL and 50 Mbps UL with 20 MHz bandwidth, though the specification supports up to 300 Mbps with 4x4 MIMO. Release 10 was the watershed moment — LTE-Advanced met ITU IMT-Advanced requirements through carrier aggregation (up to 5 CCs per TS 36.101 Section 5.6A), enhanced MIMO (8x8 DL, 4x4 UL), and heterogeneous network support (eICIC). This release proved that evolutionary standards could meet revolutionary performance targets. Release 13 introduced the LTE-Advanced Pro brand and three features that extended LTE's reach: LAA (Licensed Assisted Access) for unlicensed spectrum at 5 GHz, NB-IoT for ultra-low-power wide-area IoT, and LTE-M (eMTC) for mid-tier IoT. NB-IoT achieves -164 dBm MCL (Maximum Coupling Loss per TS 36.888), enabling deep indoor/underground coverage.

5G NR Era: Releases 15-17

Release 15 defined the 5G NR air interface from scratch while maintaining backward compatibility through EN-DC (NSA deployment option). Key design choices:

• Flexible numerology: SCS of 15, 30, 60, 120, 240 kHz per TS 38.211 Section 4.2 (vs. fixed 15 kHz in LTE)
• Bandwidth parts (BWP): Dynamic bandwidth adaptation per TS 38.213
• Massive MIMO: Up to 256 antenna elements, codebook and non-codebook based transmission
• mmWave support: FR2 bands from 24.25-52.6 GHz with analog/hybrid beamforming

Two architecture options were defined: Option 3x (NSA/EN-DC) with LTE anchor and 5GC, and Option 2 (SA) with NR-only connection to 5GC per TS 38.401 Section 4.

Release 16 hardened 5G NR for industrial and vehicular use. URLLC enhancements reduced latency to 0.5 ms user-plane with 99.9999% reliability through features like configured grant, mini-slots, and PDCP duplication. NR-V2X (per TS 38.885) replaced the LTE sidelink with NR-based sidelink supporting groupcast and broadcast modes for autonomous driving.

Qualcomm's Snapdragon X65 was the first chipset supporting Rel-16 features, enabling 10 Gbps peak DL in commercial devices by late 2022.

Release 17 extended NR to new spectrum, new devices, and new domains:

• FR2-2 (52.6-71 GHz): Opened the 60 GHz band for NR with new SCS of 480 and 960 kHz per TS 38.211 Rel-17
• RedCap (Reduced Capability): NR devices with limited bandwidth (20 MHz FR1, 100 MHz FR2), 1-2 Rx antennas, for wearables and industrial sensors per TS 38.300 Section 5.7A
• NR-NTN (Non-Terrestrial Networks): NR via LEO/GEO satellites per TS 38.821, enabling global coverage

5G-Advanced Era: Releases 18-19

Release 18 is the first 5G-Advanced release, marking the second phase of 5G evolution. Its three pillar features: AI/ML for NR air interface (per TR 38.843 → normative in TS 38.214 Rel-18): Standardizes ML-based CSI feedback, beam management, and positioning. The UE can use a neural network for channel estimation and report compressed CSI via a learned codebook, reducing CSI overhead by up to 60% while improving accuracy. XR (Extended Reality) optimization: New traffic models and scheduling enhancements for VR/AR per TR 26.928. Jitter-aware scheduling, PDU set handling, and power-saving for head-mounted displays operating at 90-120 fps rendering rates. Duplex evolution: Study and initial specification of subband full-duplex (SBFD) where the gNB transmits and receives simultaneously on different subbands within the same carrier per TR 38.858, potentially doubling spectral efficiency. Release 19 advances 5G-Advanced with:

• Ambient IoT: Zero-energy and ultra-low-energy devices (battery-free tags) communicating via backscatter with NR base stations per TR 38.769. Target: -130 dBm sensitivity for tag-to-reader link.
• Network energy saving: AI-driven cell sleep orchestration with standardized interfaces per TR 38.864
• NR-NTN Phase 2: Regenerative satellite payloads with on-board gNB processing

6G Era: Release 20+

Release 20 will be the first 6G release, aligned with ITU-R's IMT-2030 framework defined in Recommendation M.2160. The IMT-2030 vision specifies six usage scenarios:

1. Immersive Communication: Holographic, multi-sensory
2. Hyper Reliable Low Latency: 0.1 ms with 99.99999% reliability
3. Massive Communication: 10 million devices/km²
4. Ubiquitous Connectivity: Terrestrial + NTN seamless
5. AI and Communication: AI-native protocol stack
6. Integrated Sensing and Communication (ISAC): Radar-like sensing via communication signals

Worked Example: Feature Availability Timeline

An operator planning a private 5G network in Q4 2026 needs to understand which features are commercially available:

Feature                    Release    Frozen    Chipset Availability    Network Ready
Basic NR SA               Rel-15     2019      2020 (X55)              Now
URLLC enhancements         Rel-16     2020      2022 (X65)              Now
RedCap devices             Rel-17     2022      2024 (various)          Now
AI/ML CSI feedback         Rel-18     2025      Expected H2 2026        2027
Subband full duplex        Rel-18     2025      Expected 2027           2028
Ambient IoT                Rel-19     2026      Expected 2028           2029

The operator can confidently deploy Rel-15 through Rel-17 features today. Rel-18 features require waiting for chipset and infrastructure availability, typically 18-24 months after specification freeze.

Worked Example: Throughput Evolution Across Releases

Tracking peak DL throughput evolution for a single 20 MHz FDD carrier shows the impact of each release's enhancements:

Release   MIMO      Modulation   Peak DL (20 MHz)   Gain vs Prior
Rel-8     2x2       64QAM        150 Mbps            Baseline
Rel-10    4x4       64QAM        300 Mbps            2.0x
Rel-12    4x4       256QAM       400 Mbps            1.3x
Rel-15*   4x4       256QAM       ~450 Mbps           1.1x (* NR 20 MHz, SCS 15 kHz)
Rel-18    4x4       1024QAM      ~530 Mbps           1.2x

Note: 5G NR's throughput advantage over LTE becomes dramatic with wider bandwidths. At 100 MHz (n78, SCS 30 kHz, 4x4 MIMO, 256QAM), NR Rel-15 achieves approximately 3.3 Gbps DL — a capability LTE cannot match due to its 20 MHz per-carrier limitation (though LTE CA can aggregate up to 5x20 MHz = 100 MHz with 5CC CA, achieving ~2 Gbps with 256QAM).

Working It Backwards: "Which Release Do I Need for X?"

Almost nobody looks up a release timeline to learn history. They look it up

because they need to answer one of two questions, and the timeline above answers

neither directly.

"A vendor says this needs Release 18. Is that true?" "We need feature X. What is the earliest release that gives it to us?"

Here is how to resolve either one properly, in the order that costs least time.

1. Find the work item, not the marketing name. Vendor feature names rarely

match 3GPP terminology, and this is where most confusion starts. Translate to

the specification term first — "network energy saving", "beam management

enhancement", "RedCap" — then search on that. If you cannot find a specification

term for the feature, that is itself the answer: it is a vendor implementation,

not a standard, and portability is not something you can assume.

2. Check whether it was a study item or a work item. A study item produces a

technical report; a work item produces normative text you can hold a vendor to.

Many features are studied and never specified. "It is in Release 19" can be true

of a study and mean nothing contractual — this is the single most common way a

roadmap conversation goes wrong.

3. Find the specification and the version. Once you have the right TS number,

the version string carries the release. A 38.331 at version 18.x.y is Release 18

of that specification. This is the only unambiguous answer in the whole process,

which is why it is worth going all the way to it rather than stopping at a

feature list. Our 3GPP Spec Lookup resolves TS and TR

numbers if you do not have the number to hand.

Three different things people call "supported"

This is what actually causes the argument in the room, and separating the three

usually ends it:

A feature can be specified for years, implemented by your vendor, and still be

off in your network — frequently because it is licensed separately. When a

capability "should work" and does not, check these in reverse order. Configuration

is the cheapest thing to check and the most common answer.

The release a feature landed in is not when you can use it

There is a lag of roughly two to four years between a release freezing and the

feature being deployable at scale, and it is not vendor slowness. Chipsets have

to implement it, devices have to ship with those chipsets, and the installed base

has to turn over enough for the feature to be worth enabling. Release 15 froze in

2018; standalone 5G with a meaningful device population arrived years later.

Plan against device penetration, not the freeze date. The freeze date tells

you when the argument about what the feature does ends. It tells you nothing

about when you can sell it.

Specification Numbering Explained

3GPP specification numbers follow a systematic scheme:

The prefix TS denotes a normative Technical Specification (binding for compliance). TR denotes a Technical Report (informative study, not binding). When evaluating vendor claims, always check whether the referenced document is a TS or TR — a feature described only in a TR has not been fully standardized.

How to Track 3GPP Progress

Staying current with 3GPP is essential for telecom professionals. Key resources:

3GPP Work Plan: The official tracker at www.3gpp.org/specifications/work-plan lists every active study and work item with status, rapporteur, and target completion date. TSG meeting reports: Plenary meetings (RAN, SA, CT) occur quarterly. Meeting documents are publicly available on the 3GPP portal within days of each meeting. Change Requests (CRs): Individual specification changes are tracked as CRs. Monitoring CRs for key specs (e.g., TS 38.214 for physical layer procedures) reveals feature evolution between releases.

> Key Takeaway: The 3GPP release timeline from Rel-8 LTE through Rel-20 6G represents a continuous evolution spanning two decades. Each release builds on the prior foundation — understanding the feature baseline of each release is critical for network planning, device procurement, and career development in telecom engineering.