3GPP Release 17

Also known as: 3GPP Rel-17, Release 17

Definition

The set of technical specifications published by the 3rd Generation Partnership Project as Release 17, functionally frozen in June 2022, which for the first time defines how non-terrestrial platforms integrate into the 5G System as a standardized radio access technology, alongside a broader set of 5G System enhancements.

Key Points
  • First 3GPP release to define NR-NTN, covering both LEO and GEO satellite integration with the 5G System
  • Introduced RedCap (NR-Light) for mid-tier IoT devices between LPWA and full-featured 5G modems
  • Standardized 5G Multicast-Broadcast Services (5MBS) for one-to-many content delivery
  • Extended timing advance ranges and defined Doppler pre-compensation procedures specifically to support satellite propagation conditions
  • Functionally frozen (ASN.1 freeze) in June 2022, forming the compliance baseline that Release 18 and later releases extend rather than replace
Concept

Equipment vendors, satellite operators, and mobile network operators build NTN-capable products against the Release 17 specification set as the compliance baseline — a device or network element claiming "NTN support" is, in practice, claiming conformance to the relevant Release 17 (or later) technical specifications. Because 3GPP releases are additive rather than replacing prior baselines, Release 17 NTN capability sits alongside, not instead of, the terrestrial 5G RAN and core procedures defined in Release 15 and 16.

Explainer

Release 17 matters operationally because "5G NTN" as a marketing term has no fixed meaning outside reference to a specific 3GPP release, and the practical capability a network or device actually has depends entirely on which release's specifications it implements and which features within that release are actually deployed. A Release 17 NTN device supports NR-NTN for LEO and GEO with certain constraints on supported frequency bands, duplex modes, and satellite payload types (bent-pipe was prioritized; regenerative payload support matured further in later releases); a device or network claiming NTN support without specifying the release may be relying on pre-standard or proprietary implementations that will not interoperate across vendors. This creates real procurement risk in CE verticals adopting early NTN equipment: a maritime or mining operator purchasing NTN terminals needs to confirm which release and which optional feature set a given device implements, since Release 17 defines several NTN capabilities as optional rather than mandatory, and vendor roadmaps for Release 18 and 19 features (higher throughput, additional bands, improved handover) are not backward-compatible guarantees.