3GPP Release 17: Satellites, RedCap and 5G IoT
Release 17 extended 5G in three dimensions simultaneously: upward into space with Non-Terrestrial Networks, outward to simpler IoT devices with RedCap, and inward to native group delivery with Multicast and Broadcast Services. It also deepened the sidelink for relay and public safety use cases. Together these features transformed 5G from a terrestrial broadband standard into a global connectivity platform.
Overview
The Rel-17 specification freeze happened in June 2022, delayed partly by the complexity of NTN standardisation — adapting a protocol stack designed for 10 ms round-trip times to a system with 600 ms RTT required fundamental changes to HARQ, timing advance, and synchronisation. The work was worth the effort: Rel-17 NTN support shipped in consumer chipsets (Qualcomm Snapdragon 8 Gen 2) within eighteen months of the freeze.
RedCap addresses a market gap that had been widening since 5G's commercial launch. Full NR chipsets, with 100 MHz bandwidth, four receive antennas, and full-duplex FDD, are expensive. LTE-M and NB-IoT are cheap but too limited for applications that need several megabits per second. RedCap slots between them — purpose-built for smartwatches, industrial wireless sensors, and HD video surveillance cameras.
NTN — 5G From Space
Non-Terrestrial Networks (NTN) adapts NR to work via satellite links. Two orbit classes with very different characteristics:
Round-trip time approximately 4–8 ms — much closer to terrestrial NR than GEO. A single LEO satellite is visible for roughly 10 minutes before moving below the horizon at its orbital speed of ~7.5 km/s. The principal challenge is Doppler shift: at 2 GHz, a satellite approaching at 7.5 km/s causes up to ±48 kHz of frequency shift — orders of magnitude larger than terrestrial Doppler. Timing advance also changes continuously as the satellite moves closer and then further away.
Stationary from the UE's perspective — no Doppler, no footprint handover. But the round-trip time is approximately 600 ms. Standard NR HARQ assumes a ~4 ms RTT; a 600 ms RTT would stall every HARQ process waiting for acknowledgement, rendering transmission efficiency near zero. GEO NTN requires fundamentally different HARQ timing configuration.
Rel-17 defines three key adaptations that make NR work in both orbit classes:
- HARQ timer extension: HARQ processes are configured with timers matching the actual RTT of the satellite link — up to 600 ms for GEO. The gNB (or ground station acting as gNB in transparent mode) holds HARQ context for the full RTT before timing out.
- UE-side Doppler pre-compensation: the UE uses its GNSS position fix and a published satellite ephemeris (broadcast by the satellite) to calculate the expected Doppler offset. It pre-compensates its transmit carrier frequency so the signal arrives at the satellite at the correct frequency. The network compensates the remaining residual Doppler.
- Extended timing advance: the TA field in the NR uplink scheduling grant is widened significantly — standard NR supports up to ~670 µs of timing advance; LEO NTN requires up to 7 ms and GEO requires up to 600 ms. The extended field accommodates this.
The satellite simply amplifies and frequency-shifts the NR signal — it is a "bent pipe" in space. The gNB is located on the ground at a gateway station. Simpler satellite design, lower satellite cost, easier software updates from the ground. The added propagation delay of the feeder link (ground to satellite) adds to the RTT.
The gNB is hosted onboard the satellite itself — it demodulates, decodes, and re-encodes the NR signal. Latency is reduced because there is no feeder link RTT for the user-plane path. More complex and expensive satellite, but enables true inter-satellite routing and reduces the number of ground gateways needed.
RedCap — Right-Sized 5G for IoT
Reduced Capability (RedCap) NR is a new device category that sits between full NR and NB-IoT, addressing applications that need 5G reliability and network integration but not phone-grade throughput. The capability reduction is specific and deliberate:
vs 100 MHz for full NR
vs 4 for full NR
one RF switch, no duplexer
sufficient for HD video
competing with LTE-M on price
wake-up signal for IoT duty cycles
The target applications illustrate why the compromise makes sense. Smartwatches need more bandwidth than LTE-M (heart-rate monitoring, LTE-M's 1 Mbps is fine; cellular ECG streaming, LTE-M falls short) but will never stream 4K video. Industrial wireless sensors for vibration, temperature, and pressure monitoring need 5G's NR reliability and determinism, not the throughput of a smartphone. HD video surveillance cameras need approximately 10 Mbps for 1080p — far more than LTE-M but far less than the 1 Gbps+ that full NR enables.
MBS — 5G Native Multicast and Broadcast
Multicast and Broadcast Services (MBS) bring native one-to-many delivery to 5G NR within a standard NR carrier. Unlike LTE's eMBMS — which required dedicated MBSFN (Multicast-Broadcast Single-Frequency Network) configurations that could not be mixed with normal unicast traffic on the same subframes — NR MBS operates within a standard NR carrier using normal PDSCH transmissions.
The key mechanism is the multicast session: a single PDSCH transmission from the gNB addresses multiple UEs that are members of the same multicast group. The gNB transmits once; every member UE receives it. Feedback is handled through aggregate NACK — rather than every UE independently ACKing (which would create thousands of simultaneous uplink transmissions), the gNB retransmits if any UE reports a NACK. The session is assigned a dedicated G-RNTI (Group Radio Network Temporary Identifier) that all members monitor.
- Mission-critical push-to-talk (MCPTT): a dispatcher's voice transmission is sent once and received by all officers simultaneously — no per-UE unicast required, saving massive uplink capacity in public safety communications.
- Fleet OTA software updates: a new firmware image is broadcast to all IoT devices in a cell simultaneously — updating ten thousand devices takes no more radio resources than updating one.
- Live event streaming: inside a stadium, a single video stream is delivered to all viewers simultaneously rather than replicating unicast streams that would saturate the cell.
Enhanced Sidelink — Relay and Power Saving
Three enhancements to the NR sidelink expand its coverage and efficiency:
A UE with network coverage — a Relay UE — forwards traffic on behalf of a Remote UE that has no direct gNB connection. The Remote UE communicates over PC5 sidelink to the Relay UE; the Relay UE communicates with the gNB over the standard Uu interface. From the network's perspective, the Remote UE appears as a normal served device — it has a full PDU session, registration, and mobility management. This enables coverage extension in basements, rural areas, and public safety scenarios where not every first responder is within direct gNB range.
Always-on sidelink — as required for V2X where a vehicle must always be ready to transmit safety messages — drains battery continuously. Rel-17 introduces DTX/DRX mechanisms for the PC5 interface: UEs that are not currently transmitting sidelink can disable their sidelink receiver for configured intervals. A Sidelink DRX cycle analogous to Uu DRX lets IoT devices on sidelink duty-cycle their radio hardware, extending battery life in always-on deployment configurations.
URLLC and IIoT Rel-17 Enhancements
Building on the Rel-16 URLLC foundation, Rel-17 tightened timing and expanded the reliability toolkit further:
- Enhanced TSN integration: tighter timing error bounds between the 5G PTP clock and the factory TSN grandmaster — error reduced from tens of microseconds to single-digit microseconds — enabling TSN traffic classes with the most stringent timing requirements, including those used by semiconductor manufacturing equipment.
- Sidelink URLLC: the URLLC reliability enhancements (configured grant, PDCP duplication, mini-slot aggregation) applied to the PC5 sidelink interface. This enables deterministic machine-to-machine communication directly between industrial devices without a gNB in the latency path — critical for safety interlocking between co-operating robots.
- Multiple simultaneous CG configurations: up to four configured grant configurations active concurrently, each with a different periodicity and priority, allowing a single UE to serve mixed URLLC traffic types (for example, high-priority safety alarms and lower-priority sensor telemetry) with independent scheduling resources and pre-emption rules.
Why Rel-17 Mattered
- NTN enabled the first standards-based satellite-to-phone connectivity — Qualcomm Snapdragon 8 Gen 2 shipped with Rel-17 NTN support, and Apple followed with Emergency SOS via satellite using a related architecture. Standards-based NTN means any conformant device can connect to any conformant NTN network globally.
- RedCap defined the IoT chipset that will connect hundreds of millions of mid-tier devices in 5G networks — it fills the critical gap that LTE-M is too slow for but full NR is too expensive for, including a large fraction of industrial sensor deployments.
- MBS provides the multicast foundation that public safety 5G networks require — FirstNet's 5G mission-critical PTT capability depends on native multicast; without MBS, every push-to-talk transmission would require individual unicast streams to each officer, exhausting capacity in the exact emergency scenarios where capacity is most constrained.
- UE relay coverage extension is critical for rural 5G — where macros are sparse and infrastructure buildout is economically constrained, UE-to-network relay can extend effective coverage without any additional network equipment.