3GPP Release 17 Explained: From RedCap and NTN to Slicing, Edge, and Beyond

3GPP Release 17 is the third major 5G standards package (following the foundational Release 15 and the Phase-2 expansions of Release 16). It consolidates and broadens 5G capabilities across radio, core, devices, and vertical use cases, serving as the practical expansion bridge before the formal “5G-Advanced” branding that begins with Release 18.

It does not redesign the 5G system from scratch. Instead, it extends the architecture, improves performance for existing scenarios (enhanced mobile broadband, industrial IoT, V2X), and adds targeted support for new device classes, satellite connectivity, multicast/broadcast services, higher-frequency operation, and operational efficiency.

Timeline and Formal Status

Release 17 work began in earnest after scope decisions in late 2019. Despite being developed almost entirely under pandemic-era remote working conditions, it reached Stage-3 functional freeze in March 2022 (TSG#95-e) and protocol stability in June 2022 (SA#96). It is fully frozen.

Official summary documentation is available in 3GPP TR 21.917 (“Release 17 Description; Summary of Rel-17 Work Items”). Subsequent releases (18 onward) build on this stable base while the industry continues commercializing Release 17 features.

Position in the 5G Roadmap

Aspect	Release 15	Release 16	Release 17	Release 18+ (5G-Advanced)
Primary focus	5G foundation (NR + 5GC)	Phase-2 expansion (URLLC, V2X, IIoT)	Broad practical expansion & new verticals	AI/ML, XR, further efficiency
Device classes	High-end eMBB/URLLC	Maturity of existing classes	New mid-tier RedCap devices	eRedCap and further evolution
Non-terrestrial	Limited study	Groundwork	Full NR + IoT over NTN	Enhancements
Spectrum	Up to ~52.6 GHz	Refinements	Extension to 71 GHz (FR2-2)	Continued expansion
Branding	Initial 5G	5G Phase 2	Bridge release	Formal 5G-Advanced

Release 17 therefore occupies a pivotal middle position: it makes 5G more usable for a wider range of devices, geographies, and applications without waiting for the deeper architectural and AI-driven changes of later releases.

Major Feature Areas

1. Reduced Capability (RedCap / NR-Light) Devices

One of the most commercially significant introductions. RedCap creates a mid-tier 5G device class optimized for cost, size, and power between high-end eMBB/URLLC smartphones and ultra-low-complexity NB-IoT/eMTC sensors.

Key technical reductions relative to baseline NR:

Maximum bandwidth: 20 MHz in FR1 (sub-6 GHz), 100 MHz in FR2 (mmWave)
Fewer receive antennas (1 or 2) and typically one transmit antenna
Lower mandatory modulation order (64-QAM; 256-QAM optional)
Half-duplex FDD support allowed
No requirement for carrier aggregation or dual connectivity in the basic RedCap profile

Resulting peak rates are typically in the 85–150 Mbps downlink / ~50 Mbps uplink range—sufficient for industrial sensors, video surveillance cameras, wearables, and many IoT gateways—while enabling smaller form factors and longer battery life. Additional Release 17 power-saving and uplink-coverage features further improve the practicality of these devices.

2. Non-Terrestrial Networks (NTN)

Release 17 brings native support for 5G NR (and IoT technologies) over satellites and high-altitude platforms. It addresses the distinctive challenges of non-terrestrial links:

Long round-trip times
High Doppler shifts (especially LEO)
Large path loss and frequent satellite handovers

Both transparent and regenerative satellite payloads are considered. The feature set covers mobile broadband and massive IoT use cases, enabling coverage extension to remote land, maritime, and aeronautical environments and laying groundwork for direct-to-device satellite services. IoT-over-NTN (NB-IoT and LTE-M adaptations) is also specified.

3. Spectrum Expansion to 71 GHz (FR2-2)

Existing FR2 (24.25–52.6 GHz) is extended upward to 71 GHz. To cope with increased phase noise and propagation characteristics, higher subcarrier spacings (480 kHz and 960 kHz) are introduced alongside the previously defined 120 kHz. This opens additional capacity, including the globally available 60 GHz unlicensed band, for dense urban or specialized high-capacity deployments.

4. Multicast and Broadcast Services (MBS)

Release 17 defines a native 5G Multicast/Broadcast Service that reuses existing 5GC and NG-RAN entities as far as possible (with MB-SMF and MB-UPF enhancements). It supports both:

Multicast (to a defined group of authorized UEs)
Broadcast (to all UEs in a service area)

Delivery can switch dynamically between point-to-multipoint and point-to-point, supports UEs in connected, inactive, and idle states, and includes mechanisms for service continuity during mobility. Typical applications include public-safety mission-critical communications, live video/TV, software/firmware updates, and efficient IoT group messaging.

5. Radio and System Performance Enhancements

MIMO and multi-TRP: Further improvements in multi-beam operation, multi-TRP transmission for reliability and capacity, CSI feedback, and sounding reference signals.
Coverage: Uplink control and data channel enhancements (repetitions, joint channel estimation, frequency hopping) aimed at both terrestrial and NTN scenarios.
UE power saving: Extended discontinuous reception, relaxed measurements, reduced PDCCH monitoring, and other techniques applicable to both regular and RedCap devices.
Positioning: Targeting higher accuracy (tens of centimeters in industrial settings) and lower latency, with integrity support.
Sidelink: Enhancements for V2X, public safety, and relay scenarios.
Integrated Access and Backhaul (IAB): Topology robustness and resource multiplexing improvements.
RAN slicing and QoE: Better support for differentiated treatment and quality-of-experience reporting.
Core and service features: Native edge-computing architecture support, Access Traffic Steering/Switching/Splitting (ATSSS), enhanced non-public (private) networks, proximity services, and network automation Phase 2.

Protocol and Implementation Impact

Changes touch nearly every layer:

PHY: higher SCS, DMRS/PTRS options, coverage techniques, RedCap capability signaling
MAC/RLC/PDCP/RRC: power-saving states, sidelink, NTN timing/Doppler handling, RedCap reduced feature sets
Core (NGAP, NAS, SMF/UPF): MBS session management, edge application discovery, multi-USIM, slicing enhancements

Network vendors and device chipset makers therefore implement a mix of mandatory and optional features; commercial deployments typically activate subsets first (RedCap and power saving are among the earlier visible commercial items).

Industry and Use-Case Implications

Release 17 expands the addressable market for 5G beyond high-end smartphones and early industrial pilots:

Cost-effective IoT and wearables via RedCap
Ubiquitous coverage via NTN (including maritime, rural, and emergency scenarios)
Efficient one-to-many content distribution via MBS
Higher-capacity dense deployments via 60–71 GHz spectrum
More reliable private networks and positioning for Industry 4.0

It also improves operational economics through better energy efficiency, automation, and flexible traffic steering.

Looking Ahead

Release 17 completed the first major wave of 5G system expansion. Release 18 and subsequent 5G-Advanced releases build directly on this foundation with AI/ML integration, further RedCap evolution (eRedCap), extended reality optimizations, and continued performance gains. For network operators, device manufacturers, and application developers, Release 17 remains the practical reference point for many mid-2020s commercial 5G features that are now moving from specification into real-world deployments.

In short, Release 17 makes 5G broader, more adaptable, and more relevant to a far wider set of devices and environments while preserving backward compatibility with the earlier releases that established the 5G baseline.

1) Reduced Capability (RedCap / NR-Light) Devices

Reduced Capability (RedCap), also known as NR-Light, is a mid-tier 5G New Radio device class introduced in 3GPP Release 17. It deliberately strips down the complexity, cost, size, and power consumption of full 5G NR devices while still delivering significantly higher performance than low-power wide-area technologies such as NB-IoT and LTE-M.

It fills a long-standing gap in the cellular IoT landscape: devices that need more throughput, lower latency, and richer 5G features (network slicing, better security, native 5G core connectivity) than LPWA solutions can provide, but that do not require the multi-gigabit speeds, multi-antenna complexity, or high power draw of enhanced mobile broadband (eMBB) or ultra-reliable low-latency (URLLC) smartphones and industrial terminals.

Why RedCap Was Needed

Full 5G NR devices are over-engineered for many industrial sensors, wearables, video cameras, and mid-tier IoT applications. Their high baseband processing, wide bandwidth support, multiple RF chains, and advanced MIMO features drive up chipset cost, module size, and battery drain. At the same time, NB-IoT and LTE-M top out at very low data rates (typically under 1–2 Mbps) and higher latency, limiting them to simple metering or tracking.

RedCap targets the “middle triangle” of use cases that previously relied on LTE Categories 1–4. It brings these devices onto the modern 5G Standalone (SA) architecture so they can benefit from long-term network evolution, slicing, edge computing, and improved security without paying the full 5G complexity tax.

Core Technical Simplifications (Release 17)

RedCap achieves complexity reduction through a set of mandatory and optional constraints:

Bandwidth — Maximum channel bandwidth is limited to 20 MHz in FR1 (sub-6 GHz) and 100 MHz in FR2 (mmWave). Full NR devices typically support 100 MHz+ in FR1.
Antenna configuration — Typically 1 transmit antenna; 1 or 2 receive antennas (1Rx or 2Rx). Full NR often requires 4Rx or more.
MIMO layers — Limited to the number of receive branches (so 1 or 2 layers).
Modulation — 64-QAM is mandatory in both uplink and downlink; 256-QAM is optional in the downlink.
Duplex mode — Full-duplex FDD, half-duplex FDD, and TDD are supported. Half-duplex operation further simplifies the RF front-end.
No multi-carrier features — Carrier aggregation and dual connectivity are not required (and generally not supported in basic RedCap profiles).
Other reductions — Relaxed processing timelines in some cases, fewer data radio bearers, and optional power-saving enhancements such as extended discontinuous reception (eDRX) and relaxed radio resource management measurements.

These changes can reduce overall device complexity by roughly 50–70% compared with baseline Release 15/16 NR devices, bringing cost and power closer to LTE Category 2–4 levels.

Performance Characteristics

Typical peak data rates for Release 17 RedCap:

Downlink: approximately 85–226 Mbps (depending on antenna configuration, duplex mode, and modulation).
Uplink: approximately 50–120 Mbps.

Latency is generally in the range of a few milliseconds to tens of milliseconds—far better than classic LPWA and sufficient for most industrial sensors, video, and wearable applications. Coverage enhancements and power-saving features from Release 17 further improve practical battery life and uplink performance.

RedCap devices operate only in 5G Standalone mode and can coexist in the same spectrum and cells as full NR devices.

Primary Use Cases

Use-case category	Example applications	Why RedCap fits well
Industrial sensors	Wireless process monitoring, predictive maintenance, factory automation	Moderate data rates, low latency, long battery life, small form factor
Video surveillance	Fixed or mobile cameras, security systems	Higher uplink rates than LPWA, still cost-effective
Wearables & health	Smartwatches, medical monitors, fitness bands	Compact size, multi-day battery, moderate throughput
Smart grids & utilities	Advanced metering, grid monitoring	Better than NB-IoT for richer data, lower cost than full 5G
Logistics & tracking	Asset trackers, fleet devices with video or richer telemetry	Balance of performance and power
Consumer / retail IoT	Point-of-sale terminals, smart home hubs, low-end AR/VR	5G features without smartphone-level cost

Evolution: eRedCap in Release 18

Release 18 introduced enhanced RedCap (eRedCap) to push cost and power even lower for simpler devices. Key differences include:

Peak data rate capped at approximately 10 Mbps in both downlink and uplink (regardless of antenna configuration).
Optional further reduction of data-channel bandwidth to ~5 MHz (while the RF front-end can still support 20 MHz).
Focus primarily on FR1 (sub-6 GHz); FR2 support is dropped or de-emphasized.
Additional power-saving improvements, including longer eDRX cycles.

eRedCap is positioned as a more direct 5G successor to LTE Category 1 / 1bis, targeting the very high-volume, cost-sensitive segment that still needs more capability than NB-IoT or LTE-M.

Comparison Snapshot

Parameter	Full 5G NR (eMBB)	RedCap (Rel-17)	eRedCap (Rel-18)	NB-IoT / LTE-M
Typical peak DL rate	1+ Gbps	~85–226 Mbps	~10 Mbps	<1–2 Mbps
Max bandwidth (FR1)	100 MHz+	20 MHz	20 MHz (data ~5 MHz opt.)	180 kHz / 1.4 MHz
Antenna chains (typical)	4Rx+	1–2 Rx / 1 Tx	Primarily 1 Rx / 1 Tx	1 Rx
Complexity / cost	High	Medium (LTE Cat-2/3/4 level)	Low (LTE Cat-1 level)	Very low
Battery life potential	Hours–days	Days–weeks / months	Months–years	Years
5G SA features	Full	Yes	Yes	Limited / none

Practical Implications for the Ecosystem

Device makers gain a clear migration path from LTE Cat-1/4 modules to 5G without redesigning for full smartphone-class complexity.
Operators can serve a much wider IoT portfolio on a single 5G SA network, using network slicing to isolate traffic and applying power-saving and coverage features already standardized.
Enterprises obtain future-proof connectivity that supports richer data (video, analytics, firmware updates) while controlling cost and power budgets.
Commercial modules and early deployments have been appearing since 2023–2024; broader volume adoption continues through 2025–2026 as chipset prices fall and networks mature.

In summary, RedCap (and its eRedCap extension) is one of the most commercially important device-class innovations of 3GPP Release 17. It democratizes access to the 5G system for the vast middle tier of IoT and industrial applications, balancing performance, cost, size, and energy efficiency in a way that neither full 5G NR nor classic LPWA technologies could achieve alone.

2) Non-Terrestrial Networks (NTN)

Non-Terrestrial Networks (NTN) refer to 3GPP-standardized radio access that uses spaceborne or airborne platforms—primarily satellites (LEO, MEO, GEO) and High-Altitude Platform Stations (HAPS)—to provide connectivity to standard 5G and IoT user equipment.

Introduced as a major new feature in 3GPP Release 17, NTN enables direct communication between ordinary cellular devices (smartphones, IoT sensors, trackers) and satellites using the same air interface families already defined for terrestrial networks. This removes the need for proprietary satellite waveforms or specialized terminal hardware in many cases and integrates satellite access into the 5G System (5GS).

Why NTN Matters

Terrestrial 5G networks cannot economically cover oceans, polar regions, remote rural areas, maritime routes, or disaster zones. NTN extends coverage to these environments, supports continuity of service when terrestrial infrastructure fails, and enables new global IoT and direct-to-device services. By standardizing the technology inside 3GPP, it leverages the massive existing UE and chipset ecosystem rather than requiring a parallel satellite-only industry.

Two Parallel Tracks in Release 17

Release 17 defined two distinct but complementary NTN families:

Aspect	NR-NTN (5G New Radio over NTN)	IoT-NTN (NB-IoT / LTE-M over NTN)
Base technology	5G NR	4G NB-IoT and eMTC (LTE-M)
Target services	Mobile broadband, voice, higher-rate data, direct-to-smartphone	Low-data-rate, delay-tolerant IoT telemetry
Typical throughput	Mbps-class (scales with bandwidth and terminal type)	Tens of kbps (NB-IoT class)
Device examples	Smartphones, VSAT terminals, gateways	Sensors, trackers, meters, asset tags
Power profile	Higher (mains or large battery)	Ultra-low (multi-year battery possible)
Primary bands (Rel-17)	FR1 (sub-6 GHz), FDD	FR1, FDD

Both tracks assume Frequency Division Duplex (FDD) operation in Release 17 and require the UE to have GNSS capability for timing and frequency pre-compensation.

Architecture Options

Transparent (bent-pipe) payload — Standardized in Releases 17 and 18. The satellite simply amplifies and frequency-converts the signal. All baseband processing (gNB functions) remains on the ground at the NTN Gateway. The service link (satellite ↔ UE) and feeder link (satellite ↔ gateway) together form the extended Uu interface. This approach keeps satellite payload complexity low and enables faster commercial deployment.

Regenerative payload — Introduced in Release 19. The satellite hosts a full or partial gNB (and potentially more). The Uu interface terminates on the satellite; the feeder link carries NG or F1 interfaces. This enables inter-satellite links (ISL), reduced round-trip time for many procedures, on-board routing, and store-and-forward operation when the feeder link is unavailable.

Cell types supported include:

Earth-fixed (typical of GEO)
Quasi-Earth-fixed (steerable beams on LEO)
Earth-moving (beams that slide with the satellite)

Key Technical Challenges and Solutions

Satellite links introduce impairments far beyond terrestrial cells:

Long propagation delay — One-way delay can reach ~4–6 ms for LEO and ~120 ms for GEO (plus feeder-link contribution).
High Doppler shift and rate of change — Especially severe with fast-moving LEO satellites.
Large timing advance range and rapid change in path length.
Frequent handovers due to satellite motion.
Link-budget constraints for handheld devices with low transmit power and omnidirectional antennas.

Release 17 solutions include:

UE-side open-loop pre-compensation of timing advance and Doppler using GNSS position + satellite ephemeris broadcast in system information (SIB19).
Extended HARQ processes (up to 32) and the ability to disable HARQ on selected processes.
Expanded random-access window and timing parameters.
New system-information content for ephemeris, common timing offsets (K-offset), and cell-specific parameters.
Tracking Area and cell-identity handling adapted to satellite footprints.
Mobility enhancements, including conditional handover triggered by time or location.

These mechanisms allow the same physical-layer waveform (CP-OFDM downlink, DFT-s-OFDM uplink) used on the ground to work over satellite with only moderate protocol and parameter changes.

Evolution Beyond Release 17

Release 18 — Coverage enhancements, better terrestrial–NTN mobility, additional bands (including higher frequencies), and further IoT-NTN refinements.
Release 19 — Regenerative payloads, store-and-forward for IoT, inter-satellite connectivity, and more advanced mobility.
Later releases continue work on multi-orbit operation, voice-over-satellite optimizations, RedCap support over NTN, and improved positioning/emergency services.

Use Cases and Commercial Impact

Ubiquitous coverage for maritime, aviation, rural, and polar regions
Direct-to-device (direct-to-cell) smartphone connectivity for messaging, emergency, and eventually voice/data
Global IoT for logistics, agriculture, environmental monitoring, and asset tracking
Network resilience and disaster recovery
Backhaul for remote terrestrial cells or temporary deployments
Broadcast/multicast of popular content or public-safety information

By embedding satellite access inside the 3GPP ecosystem, NTN allows operators and device makers to treat space-based connectivity as an extension of the terrestrial 5G network rather than a separate silo. Early commercial services based on Release 17 IoT-NTN and NR-NTN are already live or in advanced trials; regenerative architectures and broader direct-to-smartphone capabilities are the next major wave.

In short, Non-Terrestrial Networks turn satellites from specialized, proprietary systems into standardized, interoperable components of the global 5G fabric—delivering coverage and resilience that pure terrestrial networks cannot economically achieve.

3) Spectrum Expansion to 71 GHz (FR2-2)

Spectrum Expansion to 71 GHz (FR2-2) is a key radio-access enhancement introduced in 3GPP Release 17. It extends 5G New Radio (NR) millimeter-wave operation from the original upper limit of 52.6 GHz up to 71 GHz, creating a new frequency sub-range formally designated FR2-2.

This expansion brings the globally available unlicensed 60 GHz band (typically 57–71 GHz) under the 5G NR umbrella and enables significantly wider channel bandwidths, unlocking higher peak data rates and new capacity for dense deployments, private networks, and high-throughput applications.

Frequency Range Definitions

Prior to Release 17, 3GPP defined two main frequency ranges for NR:

FR1: 410 MHz – 7 125 MHz (sub-6 GHz / cmWave)
FR2: 24 250 MHz – 52 600 MHz (mmWave)

Release 17 split and extended FR2 as follows:

Designation	Frequency Range	Notes
FR2-1	24.25 – 52.6 GHz	Original mmWave range from Releases 15/16
FR2-2	52.6 – 71 GHz	New range introduced in Release 17

The most prominent operating band defined for FR2-2 is n263 (57–71 GHz), specified for unlicensed / shared-spectrum operation under regional regulations. Licensed operation in portions of this range is also supported where regulators make spectrum available.

Why Expand to 71 GHz?

Several external and technical drivers motivated the work:

World Radiocommunication Conference (WRC-19) identified 66–71 GHz for International Mobile Telecommunications (IMT).
The 57–71 GHz range already contains substantial unlicensed spectrum worldwide, previously used mainly by IEEE 802.11ad/ay (WiGig).
Higher frequencies allow wider contiguous bandwidths, translating directly into higher peak throughput and system capacity.
The existing FR2 physical-layer design and RF implementations could be largely reused and scaled, minimizing the specification and implementation burden.

Key Technical Adaptations

Higher carrier frequencies bring increased phase noise, higher free-space path loss, and different regulatory environments. Release 17 therefore introduced several targeted changes while preserving as much of the existing NR framework as possible.

New Subcarrier Spacings (SCS) In addition to the 120 kHz SCS already used in FR2-1, two larger numerologies were added:

480 kHz
960 kHz

These larger SCS values:

Better combat phase noise at higher frequencies.
Enable wider channel bandwidths (up to 2 GHz per component carrier).
Shorten OFDM symbol duration, supporting lower latency.

For FR2-2 operation, 120 kHz SCS remains mandatory for UEs, while 480 kHz and 960 kHz are optional capabilities.

Wider Channel Bandwidths

FR2-2 supports channel bandwidths of 50, 100, 200, 400, 800, 1 600, and 2 000 MHz. In the initial Release 17 specifications, 400 MHz support is mandatory for band n263; wider bandwidths are optional capabilities that a UE can signal.

Initial Access and Synchronization

Synchronization Signal Blocks (SSBs) are defined for 120 kHz, 480 kHz, and 960 kHz SCS. Both 120 kHz and 480 kHz SSBs can be used for initial access. Up to 64 SSB candidate positions are supported, along with Discovery Burst Transmission Windows adapted for the new numerologies.

Channel Access for Unlicensed Spectrum

Because much of the 57–71 GHz range is unlicensed, Release 17 defines three channel-access types (Listen-Before-Talk variants) to satisfy different regional regulations:

Type 1 – aligned with European requirements
Type 2 – optimized for efficient coexistence (e.g., Japan)
Type 3 – for regions that do not mandate LBT

Beamforming is supported during sensing to improve detection performance under high path loss.

Other Protocol and RF Adjustments

Maximum number of HARQ processes increased to 32 in both downlink and uplink.
RF requirements (ACLR, ACS, reference sensitivity, etc.) were defined or adapted for the new range and wider bandwidths.
Support for stand-alone operation as well as carrier aggregation or dual connectivity with lower-frequency anchors.
UE antenna assumptions were updated (e.g., potential for more antenna elements due to smaller wavelength).

Performance and Deployment Implications

The combination of wider bandwidth and higher SCS enables theoretical peak rates well into the multi-Gbps range on a single carrier, significantly beyond what FR2-1 could deliver with typical 400 MHz channels. Practical deployments benefit from:

Extremely high capacity in dense urban hotspots, stadiums, or indoor venues.
Private 5G networks for factories, campuses, and venues that can use unlicensed 60 GHz spectrum without licensing delays.
Complementary use with lower FR2-1 or FR1 carriers for coverage and mobility.
Potential for integrated sensing and communication applications that leverage the wide bandwidth and short wavelengths.

Propagation remains challenging—higher free-space loss and poorer penetration mean FR2-2 cells will typically be small (tens to a few hundred meters) and rely heavily on beamforming, line-of-sight or strong reflected paths, and dense site deployment or indoor installation.

Relationship to Other Release 17 Features

FR2-2 coexists with, and can be combined with, other Release 17 enhancements such as further MIMO improvements, coverage techniques, RedCap devices (where supported), and carrier aggregation across frequency ranges. Later releases continue to refine RF requirements, multi-band operation, and higher-layer procedures for this spectrum.

In summary, the extension of 5G NR to 71 GHz (FR2-2) is a pragmatic yet powerful expansion of the mmWave toolbox. By scaling the existing scalable numerology framework, introducing wider bandwidths and appropriate channel-access mechanisms, 3GPP made the valuable 60 GHz unlicensed band—and adjacent spectrum—available for standardized 5G deployments, opening new avenues for ultra-high-capacity and private-network use cases while keeping implementation impact manageable.

4) Multicast and Broadcast Services (MBS)

Multicast and Broadcast Services (MBS) is the native 5G point-to-multipoint capability standardized in 3GPP Release 17. It enables efficient delivery of the same content from a single source to many receivers simultaneously, either to a defined group of authorized users (multicast) or to all users in a geographic service area (broadcast).

Unlike earlier 3GPP generations that relied on LTE-based eMBMS/FeMBMS, Release 17 MBS is fully integrated into the 5G System (5GS) architecture, reusing existing network functions wherever possible while adding targeted enhancements for radio efficiency, reliability, mobility, and QoS.

Core Concepts: Multicast vs Broadcast

Aspect	Multicast MBS Session	Broadcast MBS Session
Target audience	Authorized group of UEs only	All UEs in the defined service area
Authorization	Required (based on subscription / session join)	Not required
Delivery flexibility	Shared or Individual in 5GC; PTP or PTM on radio	Shared in 5GC; PTM only on radio
Typical use	Public safety groups, software updates to selected devices, enterprise content	Live TV/video, public alerts, mass IoT firmware, V2X broadcast

Both session types are identified by a Temporary Mobile Group Identity (TMGI) and support defined service areas (including location-dependent content).

Architecture Overview

The design principle was to minimize new network entities and maximize reuse of the existing 5G Core and NG-RAN. Key new or enhanced functions include:

MB-SMF (Multicast/Broadcast Session Management Function) — Manages MBS sessions, allocates/deallocates TMGIs, configures the user plane, and handles QoS and policy.
MB-UPF (Multicast/Broadcast User Plane Function) — Acts as the data anchor/ingress point for MBS traffic into the 5GS; performs packet processing, QoS enforcement, and replication toward RAN nodes or UPFs.
MBSF (optional Multicast/Broadcast Service Function) — Provides service-layer control, interacts with Application Functions, and can configure the MBSTF.
MBSTF (optional Multicast/Broadcast Service Transport Function) — Handles user-plane media processing, object delivery, and can act as a media anchor.

Existing functions (AMF, SMF, UPF, PCF, NEF, UDM, NG-RAN) are enhanced to support MBS procedures. The architecture supports both shared and individual traffic delivery methods between the 5GC and NG-RAN.

Traffic Delivery Methods

In the 5G Core:

5GC Shared MBS traffic delivery — A single copy of each MBS packet is sent from the MB-UPF to each relevant NG-RAN node (via N3mb). This is the efficient default for both multicast and broadcast.
5GC Individual MBS traffic delivery — Used only for multicast. The MB-UPF (or UPF) sends separate copies to individual UEs via their PDU sessions. Useful for UEs under non-MBS-capable gNBs or for service continuity.

On the radio interface (NG-RAN ↔ UE):

Point-to-Multipoint (PTM) — One transmission reaches multiple UEs using group-common scheduling (G-RNTI). Highly efficient when many users receive the same content.
Point-to-Point (PTP) — Individual unicast-like transmissions to each UE (using C-RNTI). Useful for reliability, cell-edge users, or when few UEs are present.

The gNB dynamically decides between PTM and PTP (or a combination) based on the number of receivers, radio conditions, QoS requirements, and feedback. HARQ feedback and retransmissions are supported for both modes, improving reliability compared with earlier broadcast systems.

UEs can receive MBS while simultaneously using unicast services. Reception of PTM transmissions is possible in RRC Connected, Inactive, and Idle states (with certain limitations depending on the mode).

Key Features and Capabilities

Efficient shared delivery of identical content across the core and radio.
Dynamic switching between PTM and PTP for reliability and efficiency.
Support for MBS QoS flows aligned with the 5G QoS framework (5QI, etc.).
Service area concepts (including local and location-dependent services).
Mobility support with service continuity mechanisms (including lossless handover aspects via sequence-number synchronization in some cases).
Interworking with LTE eMBMS at the service layer for public-safety (e.g., MCX) continuity.
Integration with 5G Media Streaming (5GMS) for hybrid unicast/multicast media delivery and user-service announcement.
Group scheduling that coexists with unicast traffic on the same carrier.

Typical Use Cases

Public safety and mission-critical communications (group push-to-talk, video, alerts)
Live video / IPTV / stadium or event broadcasting
Over-the-air software / firmware updates to large device populations
V2X broadcast of traffic or safety information
IoT group messaging and mass device configuration
Efficient distribution of popular content to reduce unicast load

Evolution and Status

Release 17 established the foundational architecture and basic radio procedures. Subsequent releases (5G-Advanced) continue to enhance MBS with improved reliability, coverage, multi-cell coordination, better support for mixed traffic, and tighter integration with media frameworks. Commercial interest is particularly strong for public safety, media distribution, and enterprise/private-network scenarios where one-to-many efficiency delivers clear operational and cost benefits.

In summary, 5G MBS brings true native multicast and broadcast capabilities into the 5G System for the first time. By combining shared core delivery, flexible PTM/PTP radio transmission, dynamic reliability mechanisms, and reuse of the existing 5G architecture, it provides a scalable, efficient solution for one-to-many services that was missing from the earlier 5G releases.

5) MIMO and Multi-Antenna Enhancements

MIMO and Multi-Antenna Enhancements in 3GPP Release 17 further refine the massive MIMO and multi-antenna capabilities first established in Releases 15 and 16. These improvements, often referred to under the work item “Further enhancements on MIMO for NR,” focus on better beam management, stronger multi-Transmission/Reception Point (multi-TRP) operation, richer Channel State Information (CSI) feedback, and more flexible Sounding Reference Signal (SRS) support. The goal is higher spectral efficiency, improved reliability (especially for URLLC), better performance under high mobility, and more robust operation in both FR1 and FR2.

Four Main Enhancement Areas

Release 17 MIMO work targeted four complementary areas:

Multi-beam operation (primarily FR2, also applicable to FR1)
Multi-TRP deployment (both FR1 and FR2)
SRS enhancements
CSI measurement and reporting (including reciprocity-based techniques)

Beam Management Improvements

Earlier releases used somewhat separate frameworks for downlink and uplink beam indication. Release 17 introduced a more unified Transmission Configuration Indication (TCI) framework that covers both directions. Key advances include:

Streamlined signaling to reduce latency in high-mobility scenarios.
Better support for UEs equipped with multiple antenna panels, including faster panel selection and switching.
Enhanced beam reporting that allows a UE to indicate groups of beams it can receive simultaneously from different TRPs.
Improved beam failure recovery (BFR) procedures tailored for multi-TRP operation, so a failure on one TRP does not necessarily disrupt the entire connection.

These changes help maintain robust links when users move quickly or when beams are blocked (common in mmWave).

Multi-TRP Enhancements

Multi-TRP allows geographically separated transmission points to cooperate for higher capacity (non-coherent joint transmission) or higher reliability (diversity). Release 17 expanded this significantly:

Support for multi-TRP operation across different Physical Cell IDs (inter-cell multi-TRP), removing earlier limitations that restricted coordination mainly to the same cell.
PDCCH repetition via explicit linkage of search-space sets associated with different TCI states, providing beam diversity for control channels.
PUSCH and PUCCH enhancements, including inter-slot repetition with beam switching across TRPs for improved uplink reliability.
Dynamic scheduling that can select which TRP (or combination) serves a given transmission.
Group-based beam reporting extended so a UE can report multiple beam pairs/groups corresponding to different TRPs in a single CSI report (up to N groups, with N configurable based on UE capability).

These features improve both eMBB throughput (by enabling higher effective ranks) and URLLC reliability (by providing spatial diversity against blockage or deep fades).

CSI Feedback and Codebook Enhancements

Richer and more efficient CSI is essential for multi-TRP and multi-panel operation:

Support for more dynamic channel and interference hypotheses in non-coherent joint transmission (NC-JT).
Enhanced group-based L1-RSRP reporting for multi-TRP scenarios.
Type-II codebook refinements and port-selection enhancements that exploit partial angle-delay reciprocity (especially useful in FDD FR1), reducing feedback overhead while maintaining performance.
Ability to associate CSI-RS resources with different TRPs/TCI states at the resource level.

The net result is better precoder selection at the gNB with lower uplink overhead.

SRS Enhancements

Sounding Reference Signals are critical for uplink channel estimation and reciprocity-based downlink precoding:

More flexible SRS triggering (DCI formats can trigger SRS without requiring simultaneous CSI request or data).
Expanded antenna-switching configurations to support UEs with more receive antennas (e.g., 1T6R, 1T8R, 2T6R, 2T8R, 4T8R).
Improvements that help manage inter-TRP interference and support higher-order uplink MIMO in future use cases.

Practical Benefits and Deployment Impact

Benefit	How Release 17 Helps	Typical Scenarios
Higher spectral efficiency	Better multi-TRP coordination and richer CSI	Dense urban, indoor hotspots
Improved reliability	PDCCH/PUSCH/PUCCH diversity across TRPs	URLLC, industrial, high-mobility
Better mobility handling	Unified TCI, faster panel switching, enhanced BFR	High-speed trains, vehicles
Reduced overhead	More efficient CSI feedback and SRS	Capacity-constrained cells
Robustness to blockage	Multi-TRP spatial diversity	mmWave (FR2) deployments

These enhancements are backward-compatible with earlier NR deployments and can be activated selectively based on UE capabilities and network configuration. They form a solid foundation for further MIMO evolution in 5G-Advanced (Release 18 and beyond), where coherent joint transmission across more TRPs and even higher-order uplink MIMO continue to be refined.

In summary, Release 17 MIMO and multi-antenna work focuses on making multi-beam and multi-TRP operation more practical, reliable, and efficient. By unifying beam indication, expanding multi-TRP coordination (including inter-cell), enriching CSI, and improving SRS flexibility, it delivers tangible gains in capacity, coverage robustness, and mobility performance across both sub-6 GHz and mmWave spectrum.

6) Coverage Enhancements

Coverage Enhancements in 3GPP Release 17 address one of the most persistent practical challenges of 5G NR: limited uplink coverage, especially at higher frequencies and for cell-edge users.

Studies conducted during the Release 17 timeframe identified the Physical Uplink Shared Channel (PUSCH) as the primary coverage bottleneck in many scenarios, with the Physical Uplink Control Channel (PUCCH) also requiring improvement. The resulting specifications focus on increasing the effective energy delivered to the base station receiver through smarter repetitions, better channel estimation, and more flexible resource use, delivering several decibels of coverage gain without requiring higher UE transmit power in every case.

Why Coverage Was a Priority

5G NR operates in higher frequency bands than LTE (mid-band FR1 and mmWave FR2). Free-space path loss is higher, penetration is poorer, and UE transmit power is limited by battery, regulatory, and device constraints. Uplink channels are particularly constrained because the UE has far fewer antennas and lower power than the base station. Coverage shortfalls increase the need for denser site deployment (raising cost) and can degrade service quality for cell-edge users.

Key Technical Solutions for PUSCH

Release 17 introduced several complementary techniques that work together:

1. Enhanced PUSCH Repetition Type A

Maximum number of repetitions increased from 16 (Release 16) to 32.
Available-slot-based counting: Repetitions are now counted only on slots that are actually available for uplink transmission. In TDD patterns this prevents downlink or special slots from “consuming” the repetition budget, resulting in more actual PUSCH transmissions and higher effective SNR.
These changes significantly improve coverage in TDD deployments.

2. Transport Block Processing over Multiple Slots (TBoMS)

A single transport block can be mapped and coded across multiple PUSCH slots.
This provides additional coding gain and more flexible resource utilization compared with simple repetition of the same coded block.

3. DMRS Bundling / Joint Channel Estimation

Demodulation Reference Signals (DMRS) from multiple consecutive or related PUSCH transmissions can be jointly processed at the gNB.
Combining DMRS symbols across slots improves channel estimation accuracy, especially at low SNR, which is critical for reliable decoding of repeated or multi-slot transmissions.
Lower time-domain DMRS density with sharing across transmissions is also supported in some configurations, freeing resources for data while still enabling good estimation.

4. Inter-Slot Frequency Hopping Enhancements

More flexible frequency offsets and hopping patterns increase frequency diversity, further aiding coverage in frequency-selective channels.

5. Msg3 PUSCH Repetition

Random-access Message 3 (the first uplink transmission after the Random Access Response) can now be repeated (up to 8 times).
This improves the success rate of initial access and connection establishment in coverage-limited conditions. The network can indicate the repetition factor based on measured RSRP.

PUCCH Coverage Improvements

Dynamic indication of the PUCCH repetition factor (instead of a single semi-static value for all resources).
Support for multi-TRP PUCCH repetition, allowing spatial diversity across transmission points.
More flexible configuration of repetition numbers per PUCCH resource or resource group.

Performance Impact

Evaluations and industry analyses indicate that the combination of these techniques can deliver approximately 5–6 dB (and in some studies up to ~9–10% coverage-area improvement) of uplink coverage gain in both FR1 and FR2 scenarios, depending on the specific configuration, channel conditions, and TDD pattern. The gains are particularly valuable for mid-band TDD deployments and for supporting higher-frequency or NTN operation.

Complementary Measures

Coverage is also helped by related Release 17 features:

High-power UE support extensions in FR1 (including certain FDD bands).
Multi-TRP operation that provides spatial diversity.
Power-saving and measurement-relaxation features that can indirectly improve effective coverage by allowing devices to operate more efficiently at the cell edge.
Simple NR repeaters (amplify-and-forward) as a low-cost infrastructure option for coverage extension.

Practical Benefits

Better cell-edge throughput and reliability without proportional increases in site density.
Improved initial-access success rates.
More consistent performance for uplink-heavy applications (video upload, industrial sensors, cloud gaming, etc.).
Synergies with NTN and higher-frequency (FR2-2) deployments, where path loss is even more severe.

In summary, Release 17 coverage enhancements take a pragmatic, multi-pronged approach focused on the uplink. By increasing the effective number of PUSCH repetitions (especially in TDD), enabling multi-slot transport-block processing, improving channel estimation through DMRS bundling, and adding flexibility to PUCCH and Msg3, 3GPP delivered meaningful coverage gains that help close the practical gap between theoretical 5G performance and real-world deployment conditions. These techniques remain foundational for further coverage work in later 5G-Advanced releases.

7) UE Power Saving

UE Power Saving enhancements in 3GPP Release 17 significantly extend the energy-efficiency toolbox of 5G NR for both conventional eMBB devices and Reduced Capability (RedCap) UEs.

These features reduce unnecessary radio activity across RRC Connected, Inactive, and Idle states, delivering longer battery life while maintaining acceptable latency and connectivity for a wide range of traffic patterns.

Why Power Saving Matters in 5G

5G NR devices often operate with wider bandwidths, more antennas, higher sampling rates, and more frequent control-channel monitoring than LTE. Without targeted optimizations, modem and RF power consumption rises sharply. Release 15 and 16 already introduced Connected-mode DRX, cross-slot scheduling, and basic measurement relaxation. Release 17 builds on this foundation with finer-grained control, better Idle/Inactive optimizations, and mechanisms suited to both latency-tolerant IoT traffic and more dynamic applications such as XR or voice.

Power Saving in RRC Idle and Inactive States

Paging Early Indication (PEI)

A major optimization for Idle and Inactive UEs. The network can send a PEI (typically on a PDCCH) before the actual Paging Occasion (PO). If the PEI indicates that the UE is not being paged, the device can skip decoding the full paging message (PDCCH + PDSCH). This avoids unnecessary wake-ups and yields substantial power savings, especially when the paging rate is moderate.

TRS/CSI-RS Occasions for Idle/Inactive UEs

Additional Tracking Reference Signal or CSI-RS occasions can be provided via system information (e.g., SIB17). These help the UE maintain better time/frequency synchronization and Automatic Gain Control before a PO, reducing the number of Synchronization Signal Blocks (SSBs) that must be monitored and improving detection reliability under weaker conditions.

Extended Discontinuous Reception (eDRX)

Longer eDRX cycles are supported, particularly beneficial for latency-tolerant devices (including RedCap). In later refinements (and for eRedCap in Release 18), eDRX cycles in RRC Inactive can be extended significantly (up to hours in some configurations), allowing multi-day or multi-year battery targets for simple sensors.

Small Data Transmission (SDT)

UEs can send or receive small amounts of data while remaining in RRC Inactive, avoiding the full transition to Connected state and the associated signaling overhead and power cost.

Power Saving in RRC Connected State

Further PDCCH Monitoring Reduction PDCCH monitoring is one of the largest continuous power consumers in Connected mode. Release 17 introduces two complementary DCI-triggered adaptations within an active Bandwidth Part (BWP):

PDCCH Skipping — The network can instruct the UE (via scheduling DCI) to skip PDCCH monitoring for a configured duration (up to three possible skip lengths). After the skip period the UE resumes monitoring. This is especially effective when the network can predict quiet periods between packets.
Search Space Set Group (SSSG) Switching — Multiple groups of search-space sets with different monitoring periodicities can be configured. The network (or a timer) switches the UE between a dense group (for active traffic) and a sparse group (for periods of inactivity), reducing the average monitoring duty cycle.

These mechanisms can be combined with Connected-mode DRX and deliver additional double-digit percentage power savings for bursty traffic such as XR or voice, with only modest latency impact when properly configured.

Relaxation of Radio Link Monitoring (RLM) and Beam Failure Detection (BFD)

When the UE experiences good radio conditions and/or low mobility, it can relax the frequency of RLM and BFD measurements on the serving cell. This reduces processing and RF activity without compromising link reliability under stable conditions.

Secondary Cell Group (SCG) Activation/Deactivation

For dual-connectivity scenarios (EN-DC or NR-DC), the UE can deactivate the secondary cell group when it is not needed, saving power on the secondary radio chain.

Applicability to RedCap Devices

Many of the above techniques are particularly valuable for RedCap UEs, which already have reduced complexity and bandwidth. Combined with the inherent lower power of a narrower RF front-end and fewer antennas, Release 17 power-saving features help RedCap devices achieve multi-day or longer battery life for industrial sensors, wearables, and video cameras.

Performance Impact and Trade-offs

Industry evaluations show:

Paging Early Indication alone can reduce Idle/Inactive power consumption by more than 10 % (and higher under low paging rates).
PDCCH skipping and SSSG switching in Connected mode typically provide 10–25 % additional modem/RF power savings for relevant traffic models, with latency increases generally kept to a few milliseconds when the network chooses appropriate skip durations or monitoring periodicities.
Measurement relaxation yields further gains under low-mobility or high-SINR conditions.

The network retains control and can balance power saving against latency and reliability requirements on a per-UE or per-service basis.

Summary of Key Release 17 UE Power-Saving Features

Feature	Primary State(s)	Main Benefit
Paging Early Indication (PEI)	Idle / Inactive	Avoid unnecessary paging decoding
TRS/CSI-RS for Idle/Inactive	Idle / Inactive	Better sync with fewer SSB detections
Extended eDRX	Idle / Inactive	Longer sleep cycles for delay-tolerant traffic
Small Data Transmission (SDT)	Inactive	Data transfer without full connection
PDCCH Skipping	Connected	Temporary suspension of control monitoring
SSSG Switching	Connected	Dynamic dense/sparse monitoring
RLM / BFD Measurement Relaxation	Connected	Reduced measurement activity
SCG Deactivation	Connected (DC)	Power down secondary radio chain

Release 17 UE power-saving enhancements make 5G devices more practical for battery-constrained use cases while preserving the performance advantages of NR. They form a critical bridge between high-capability eMBB smartphones and the emerging ecosystem of mid-tier RedCap and IoT devices, and they continue to be refined in 5G-Advanced releases.

8) Positioning Enhancements

Positioning Enhancements in 3GPP Release 17 significantly advance the 5G NR positioning capabilities first introduced in Release 16. They improve accuracy, reduce latency, increase efficiency for both the network and the device, add support for positioning while the UE is in RRC Inactive state, and introduce integrity features. These changes target commercial requirements (sub-meter accuracy) and more demanding Industrial IoT (IIoT) scenarios (around 20 cm horizontal accuracy in suitable deployments).

Background and Target Requirements

Release 16 defined the core RAT-dependent methods:

Downlink Time Difference of Arrival (DL-TDOA)
Uplink Time Difference of Arrival (UL-TDOA)
Multi-cell Round Trip Time (Multi-RTT)
Downlink Angle of Departure (DL-AoD)
Uplink Angle of Arrival (UL-AoA)
Enhanced Cell ID (E-CID)

Release 17 builds on these foundations with the following performance targets:

Commercial use cases: horizontal accuracy < 1 m (90 % of UEs), vertical accuracy < 3 m, latency typically < 100 ms
IIoT / factory automation: horizontal accuracy ~20 cm, vertical accuracy < 1 m, with latency on the order of tens of milliseconds desired in the most demanding cases

Accuracy Improvements

Several mechanisms reduce residual errors that limited Release 16 performance:

Mitigation of Tx/Rx timing errors — Introduction of Timing Error Groups (TEGs). UEs and TRPs can report associations of measurements with specific TEGs (groups of antenna panels or elements that share the same timing error). This allows the Location Management Function (LMF) to compensate for nanosecond-level timing offsets between different RF chains or panels.
Multi-path and NLOS mitigation — Enhanced reporting of additional paths (up to 8) with per-path RSRP and relative timing, plus LOS/NLOS indications. This helps the positioning algorithm discard or de-weight non-line-of-sight measurements.
Richer measurement reporting — Higher maximum numbers of PRS resources and measurements per TRP; support for first-path and additional-path reporting for angle and time-based methods.
Angle-based refinements — Improved UL-AoA and DL-AoD accuracy through better measurement configurations and reporting.

These techniques collectively push practical accuracy from meter-level toward the sub-meter and decimeter range in favorable deployments (especially indoor factories with good geometry and LOS).

Latency Reductions

Release 17 introduces several procedure and configuration optimizations:

Pre-configured Measurement Gaps — Measurement gap patterns can be pre-configured via RRC and then quickly activated or deactivated by MAC CE (or requested by the LMF via NRPPa). This avoids the longer latency of full RRC reconfiguration when a gap is needed for PRS measurement on a non-serving frequency.
Measurement Gap-less Positioning — In some cases the UE can measure DL-PRS inside the active downlink Bandwidth Part (when numerology matches), eliminating the need for a measurement gap entirely.
On-demand DL-PRS — Positioning Reference Signals are transmitted only when needed rather than continuously. Either the UE or the LMF can trigger transmission. This reduces both network overhead and unnecessary UE power consumption while still allowing short measurement intervals when positioning is required.
Faster reporting paths — Support for more efficient measurement reporting, including use of Configured Grants in some scenarios to avoid Scheduling Request latency.

Device and Network Efficiency

Positioning in RRC Inactive State

One of the most practically important enhancements. Previously, a UE typically had to enter RRC Connected to perform positioning measurements and report them. Release 17 allows the UE to remain in RRC Inactive, use Small Data Transmission (SDT) mechanisms (random access or configured grant), exchange positioning messages and SRS configurations, perform the required measurements, and report results—without a full state transition. This dramatically reduces signaling overhead and power consumption for infrequent or periodic positioning (common in industrial sensors and asset trackers).

On-demand PRS (already noted above) also improves network efficiency by avoiding continuous transmission of positioning signals when no UEs need them.

Integrity and Other Enhancements

Support for positioning integrity (measures of trustworthiness of the position estimate), important for safety-related and regulatory applications.
Improved Assisted-GNSS (A-GNSS) support, including additional GNSS systems/signals (e.g., BDS B2a/B3I, NavIC).
Better handling of carrier aggregation and multi-TRP scenarios for positioning measurements.

Supported Methods (Summary)

Method	Primary Measurements	Key Rel-17 Improvements
Multi-RTT	UE Rx-Tx + gNB Rx-Tx time differences	Timing error mitigation, Inactive support
DL-TDOA	RSTD (+ PRS-RSRP)	TEG reporting, multi-path, on-demand PRS
UL-TDOA	UL Relative Time of Arrival	Accuracy and reporting enhancements
DL-AoD	PRS-RSRP across beams	Angle accuracy, multi-path mitigation
UL-AoA	Angle of Arrival (+ SRS-RSRP)	Improved accuracy and reporting
E-CID	Cell ID + basic measurements	Continued support and refinements

Practical Impact

These enhancements make 5G positioning viable for a much wider set of use cases:

Factory automation and indoor industrial tracking (high accuracy + low latency)
Asset and personnel tracking with long battery life (Inactive-state support)
Commercial indoor navigation and location-based services (sub-meter accuracy)
Safety and regulatory applications that require integrity information

Later releases (especially Release 18 and beyond) continue to refine power efficiency, further accuracy, and support for even lower-power devices, but Release 17 established the critical foundation of high-accuracy, low-latency, and energy-efficient NR positioning.

In short, Release 17 positioning enhancements transform 5G from a system capable of basic location services into one that can meet the stringent accuracy, latency, and efficiency demands of industrial and commercial applications.

9) Integrated Access and Backhaul (IAB) and Repeaters

Integrated Access and Backhaul (IAB) and Repeaters are two complementary approaches in 3GPP Release 17 for extending 5G NR coverage and capacity while reducing the need for fiber backhaul.

IAB provides intelligent, multi-hop wireless relaying that reuses the NR air interface for both access and backhaul. NR Repeaters offer a simpler, lower-cost amplify-and-forward option for filling coverage holes. Together they give operators flexible tools for densification, especially in mmWave and mid-band deployments where fiber is expensive or impractical.

Integrated Access and Backhaul (IAB)

IAB was first specified in Release 16. An IAB-node acts as both a gNB Distributed Unit (IAB-DU) serving UEs and child nodes, and as a Mobile Termination (IAB-MT) that connects wirelessly to a parent node (another IAB-node or the IAB-donor). The IAB-donor is a full gNB (with Central Unit functionality) that terminates the wireless backhaul and connects to the 5G Core.

Multi-hop topologies are supported, and the architecture remains transparent to ordinary UEs.

Key Release 17 Enhancements

1. Duplexing and Resource Multiplexing

Release 16 IAB was largely limited to Time-Division Multiplexing (TDM) between the IAB-MT and IAB-DU (half-duplex constraint).
Release 17 adds support for simultaneous operation on child and parent links:
- MT Tx / DU Tx
- MT Tx / DU Rx
- MT Rx / DU Tx
- MT Rx / DU Rx
This is enabled by Space-Division Multiplexing (SDM) and Frequency-Division Multiplexing (FDM), plus new timing alignment modes (Case 6 and Case 7) that align transmit or receive timing between the MT and DU sides.
Beam preference and restriction signaling between parent and child nodes helps manage interference and enables practical simultaneous operation.
Result: higher spectral efficiency and lower multi-hop latency.

2. Topology Robustness and Load Balancing

Inter-donor IAB-node migration and partial migration (IAB-MT migrates while the IAB-DU may remain under the original donor in some cases).
Enhanced Backhaul Radio Link Failure (BH RLF) detection and recovery indications that propagate through the topology, reducing packet loss.
Better support for dual-connectivity scenarios involving IAB-nodes, improving redundancy and load balancing.
Conditional handover-like mechanisms for topology adaptation to minimize service interruption.

3. Other Improvements

Enhanced QoS handling on the backhaul (extended Logical Channel Group space).
Better scheduling, flow control, and congestion management for end-to-end performance.
Applicability to both FR1 and FR2, and continued transparency to UEs (including legacy devices that benefit from the denser coverage).

These enhancements make IAB more practical for dense urban, indoor, and temporary deployments, and improve resilience when backhaul links fluctuate.

NR Repeaters

Release 17 also standardized NR Repeaters — simpler network nodes that amplify and forward RF signals without decoding or higher-layer processing.

Characteristics

Pure amplify-and-forward operation (no demodulation or protocol processing).
Defined for both FR1 (conducted requirements, Type 1-C) and FR2 (radiated/OTA requirements, Type 2-O).
Multiple classes tailored to deployment scenarios:
- Wide Area — macro-like (minimum distance to UE typically 35 m)
- Medium Range — micro-cell scenarios
- Local Area — pico/indoor scenarios
Separate class definitions for downlink and uplink.
RF requirements cover operating bands in FR1 and FR2-1, including error vector magnitude (EVM), adjacent channel leakage, intermodulation, and other emission limits.

Because repeaters do not decode the signal, they are lower cost and lower complexity than IAB-nodes, but they also amplify noise and interference. Proper placement, gain control, and (in later releases) network control become important to manage these effects.

Comparison and Complementary Roles

Aspect	IAB-Node	NR Repeater (Rel-17)
Processing	Decode-and-forward (full lower-layer stack)	Amplify-and-forward only
Complexity / Cost	Higher	Lower
Multi-hop capability	Native multi-hop support	Single hop (simple extension)
Intelligence	Scheduling, QoS, topology management	None (transparent RF relay)
Interference management	Advanced (beam, timing, power control)	Limited (placement and gain setting)
Best use cases	Capacity densification, multi-hop coverage, flexible topology	Quick coverage fill, indoor/outdoor holes, low-cost extension
Transparency to UE	Fully transparent	Fully transparent

IAB is preferred when intelligent routing, multi-hop reach, or capacity are needed. Repeaters are ideal for rapid, low-cost coverage extension in areas where a full IAB-node is unnecessary.

Later Evolution Note

Release 18 and beyond introduce more advanced Network-Controlled Repeaters (NCRs) that add side-control information for beamforming, TDD configuration, and on/off control, bridging the gap between simple Rel-17 repeaters and full IAB-nodes. IAB itself continues to evolve with further duplexing, mobility, and mobile-IAB capabilities.

Practical Benefits

Reduced fiber dependency and faster, lower-cost densification.
Better mmWave and mid-band coverage without proportional increases in fiber-connected sites.
Improved network resilience through topology adaptation and redundancy.
Flexible mix of intelligent (IAB) and simple (repeater) nodes according to local needs.

In summary, Release 17 significantly strengthens wireless backhaul and coverage-extension options. IAB enhancements deliver higher efficiency, lower latency, and greater robustness for multi-hop networks, while the introduction of standardized NR Repeaters provides a cost-effective tool for filling coverage gaps. Together they form a practical toolkit for operators deploying dense 5G networks.

10) Sidelink Enhancements

Sidelink Enhancements in 3GPP Release 17 expand NR Sidelink (direct device-to-device communication over the PC5 interface) beyond the vehicle-centric focus of Release 16.

Release 16 introduced NR Sidelink primarily for advanced Vehicle-to-Everything (V2X) services. Release 17 broadens its applicability to public safety, commercial proximity services, and battery-constrained devices while adding reliability, power-efficiency, and coverage-extension capabilities.

Main Objectives and Scope

The key goals of the Release 17 NR Sidelink work were:

Improve reliability and reduce latency for Mode 2 (autonomous) resource allocation.
Introduce power-saving mechanisms suitable for pedestrian/Vulnerable Road User (VRU) devices, wearables, and other battery-limited UEs.
Support coverage extension through UE-based relaying.
Enable broader use cases including public safety Proximity Services (ProSe) and commercial D2D applications, while remaining compatible with V2X.

Power Saving Enhancements

Release 16 Sidelink assumed relatively power-rich devices (e.g., vehicles). Release 17 adds mechanisms for energy-constrained UEs:

Sidelink Discontinuous Reception (SL DRX)
- Defines active and inactive periods for reception (and related transmission) on the PC5 interface. SL DRX cycles can be aligned between a transmitting UE and its receiving peer(s), and also coordinated with Uu DRX when the UE is under network coverage. This allows devices to sleep for extended periods while still supporting sidelink communication.
Resource allocation optimizations that reduce the need for continuous sensing, further lowering power consumption for Mode 2 operation.

These features are essential for VRU warning, public-safety handhelds, and commercial proximity applications.

Reliability and Resource Allocation Improvements

Inter-UE Coordination (IUC)

A major enhancement for Mode 2 autonomous resource selection. UEs exchange assistance information over the sidelink to help each other avoid resource conflicts. Typical information includes:

Preferred or non-preferred resources
Indications of potential collisions or half-duplex conflicts
Hidden-node related feedback

This helps mitigate classic distributed-scheduling problems (half-duplex, persistent collisions, and hidden nodes), improving reliability and reducing latency without requiring continuous network scheduling.

Sidelink Relay (Coverage Extension)

Release 17 introduces standardized support for UE-based relaying, a critical capability for public safety and coverage-limited scenarios:

UE-to-Network (U2N) Relay
- A Relay UE provides connectivity to the network for one or more Remote UEs that may be out of direct coverage. Both Layer-2 and Layer-3 relay architectures are supported. The Remote UE communicates with the Relay UE over PC5; the Relay UE forwards traffic to/from the network over the Uu interface.
UE-to-UE (U2U) Relay
- Allows two UEs that cannot reach each other directly to communicate via an intermediate Relay UE, supporting both in-coverage and out-of-coverage operation.

Supporting procedures include relay discovery, selection/reselection, path switching, and appropriate RRC state handling. Relaying extends both on-network and off-network coverage and is particularly valuable for public-safety operations in disaster or coverage-challenged environments.

Broader Use-Case Support

Public safety / Proximity Services (ProSe) — direct communication and group communication independent of network coverage.
Commercial D2D and proximity services.
Continued and enhanced support for advanced V2X services (including better support for VRUs).
Alignment with 5G system architecture enhancements for ProSe and V2X.

Architecture and Protocol Notes

Both L2 and L3 U2N relay architectures are defined, with clear rules for RRC states of Relay and Remote UEs.
Sidelink remains transparent to ordinary UEs that do not support the new features.
Coexistence with LTE Sidelink and with Uu operation continues to be supported.
Resource pools, power control, and discovery mechanisms are adapted for the new relay and power-saving scenarios.

Summary of Key Release 17 Sidelink Features

Feature	Primary Benefit	Main Beneficiaries
SL DRX	Significant power saving	VRUs, public-safety devices, IoT
Inter-UE Coordination (IUC)	Higher reliability, lower collision rate	All Mode 2 users, especially dense scenarios
UE-to-Network Relay	Coverage extension to the network	Out-of-coverage UEs, public safety
UE-to-UE Relay	Direct communication beyond single-hop range	Public safety, commercial D2D
Resource allocation refinements	Lower power + better reliability	Battery-constrained and high-density use

Practical Impact

Release 17 transforms NR Sidelink from a primarily automotive technology into a versatile direct-communication platform. It enables:

Longer battery life for handheld and wearable devices using sidelink.
More reliable autonomous resource selection in dense environments.
Coverage extension without additional infrastructure via UE relays.
Stronger support for public-safety direct-mode and group communications.

Later releases (especially Release 18 and beyond) continue to refine sidelink with further enhancements for unlicensed spectrum, positioning over sidelink, multi-hop relays, and additional commercial use cases. Release 17, however, established the essential foundations of power efficiency, reliability, and relaying that make NR Sidelink practical for a much wider ecosystem.

11) System-Level and Architectural Improvements

System-Level and Architectural Improvements in 3GPP Release 17 refine the 5G System (5GS) architecture to better support industry verticals, improve operational efficiency, and close practical deployment gaps left by earlier releases.

These enhancements build on the service-based architecture (SBA) introduced in Release 15 and the foundational features of Release 16. They focus on more sophisticated network slicing, stronger edge-computing support, multipath connectivity, multi-USIM handling, RAN-level slicing awareness, and related system optimizations.

Network Slicing Enhancements (Phase 2)

Network slicing remains a cornerstone of 5G. Release 17 adds practical controls and RAN awareness:

Network Slice Admission Control (NSAC)
- A new Network Slice Admission Control Function (NSACF) monitors and enforces limits on the number of registered UEs and the number of PDU Sessions per slice. This prevents a slice from exceeding the capacity agreed in Service Level Agreements (derived from the Generic Slice Template).
UE-Slice-MBR
- Introduces a Maximum Bit Rate that applies across all PDU Sessions of a given UE on a specific network slice (covering both GBR and non-GBR flows). This provides finer-grained traffic control per UE per slice.
Network Slice Simultaneous Registration Groups (NSSRG)
- Defines groups of slices that a UE is allowed (or not allowed) to register to simultaneously, improving flexibility and control over multi-slice UE behavior.
RAN Slicing Support
- Enhanced interaction between the Core and RAN so that the RAN can perform slice-aware cell reselection, prioritized Random Access configurations per Network Slice Admission Group (NSAG), and better service continuity when a UE moves between cells that support different sets of slices. Slice-based redirection and preferred frequency bands per S-NSSAI are also supported.

These features make slicing more enforceable, scalable, and usable in real multi-operator and multi-vertical deployments.

Edge Computing Support

Release 17 strengthens the integration of edge computing with the 5G Core:

Improved discovery and (re)discovery of Edge Application Servers (EAS).
Better support for different connection models (including local breakout and dedicated edge Data Networks).
Enhancements to the Edge Enabler Layer and related application-layer enablement (EASDF, etc.).
Tighter coordination with network slicing and local traffic steering so that latency-sensitive applications can be efficiently directed to nearby edge resources.

These changes help operators and application providers deliver low-latency services (AR/VR, industrial control, content caching, etc.) more reliably.

Access Traffic Steering, Switching and Splitting (ATSSS) Phase 2

ATSSS enables a Multi-Access (MA) PDU Session that can simultaneously use 3GPP and non-3GPP (e.g., Wi-Fi) accesses.

Release 17 improvements include:

Enhanced steering modes with performance measurements (RTT, packet loss rate) that can be performed per QoS flow.
Support for hybrid scenarios in which one leg of the MA PDU Session uses EPC (4G) while the other uses 5GC.
More flexible traffic distribution, switching, and splitting policies.

This gives UEs and the network better tools for multipath connectivity, improving throughput, reliability, and seamless use of Wi-Fi alongside cellular.

Multi-USIM Support

Release 17 formalizes system support for UEs with multiple USIMs (or equivalent). This includes coordinated handling of paging, connection management, and service prioritization across the different subscriptions so that dual-SIM (or multi-SIM) devices behave more predictably and efficiently in a 5G network.

Other Notable Architectural and System Improvements

Non-Public Networks (NPN) — Further refinements to Standalone Non-Public Networks (SNPN) and Public Network Integrated NPN (PNI-NPN), including better interworking and isolation.
Network Automation / Analytics — Continued enhancements to the Network Data Analytics Function (NWDAF) and related data-collection mechanisms that support more autonomous network operation and SON/MDT improvements.
Multicast/Broadcast Services (MBS) Architecture — Introduction of MB-SMF and MB-UPF (reusing existing entities where possible) together with Shared Delivery in the core, enabling efficient one-to-many distribution.
Proximity Services (ProSe) and Sidelink System Support — Architectural support for the UE-to-Network and UE-to-UE relays and related discovery/selection procedures described in the Sidelink enhancements.
Support for Uncrewed Aerial Systems (UAS) and other vertical-specific architectural extensions.

High-Level Impact

Area	Key Rel-17 Improvement	Practical Benefit
Network Slicing	NSAC, UE-Slice-MBR, RAN slice awareness	Enforceable SLAs, better multi-vertical isolation
Edge Computing	Improved EAS discovery & local breakout	Lower latency for edge applications
Multipath Connectivity	ATSSS Phase 2 (per-QoS measurements, hybrid EPC/5GC)	Better Wi-Fi + cellular aggregation
Multi-USIM	Coordinated multi-subscription handling	Improved dual-SIM device behavior
RAN–Core Coordination	Slice-based reselection, RACH, continuity	More intelligent radio resource use per slice
Broadcast/Multicast	MB-SMF/MB-UPF + Shared Delivery	Efficient group services

Overall Significance

Release 17 system-level and architectural work shifts 5G from a strong foundational architecture to a more mature, operator- and vertical-ready platform. By adding admission control and RAN awareness to slicing, strengthening edge integration, refining multipath connectivity, and formalizing multi-USIM and relay architectures, it addresses many of the practical issues encountered in early commercial 5G deployments.

These improvements also serve as a solid base for the further automation, AI/ML integration, and service continuity features that continue to evolve in 5G-Advanced (Release 18 and beyond).

In short, the architectural enhancements of Release 17 make the 5G System more controllable, more efficient at the edge, and better suited to the diverse requirements of industry verticals and multi-access devices.

12) Network Slicing Enhancements (Phase 2)

Network Slicing Enhancements (Phase 2) in 3GPP Release 17 make network slicing more enforceable, scalable, and RAN-aware.

Earlier releases (15 and 16) established the basic architecture for slicing—S-NSSAI identification, slice selection, Network Slice Specific Authentication and Authorization (NSSAA), and isolation principles. Phase 2 focuses on admission control, per-UE rate limiting, simultaneous registration constraints, and closer coordination between the 5G Core and the RAN so that slicing works reliably in real multi-vertical, multi-operator deployments.

1. Network Slice Admission Control (NSAC)

A new Network Function, the Network Slice Admission Control Function (NSACF), is introduced.

Purpose Monitor and control:

The number of registered UEs per network slice
The number of PDU Sessions per network slice

for those slices that are subject to admission control (typically derived from parameters in the GSMA Generic Slice Template / GST and operator policy).

How it works

The AMF (and in some cases the SMF or combined SMF+PGW-C) interacts with the NSACF during registration and PDU Session establishment/release.
The NSACF tracks current occupancy against configured maxima and access-type restrictions.
If limits would be exceeded, the request can be rejected or the UE directed to alternative slices.

This provides the missing “capacity policing” layer that operators need to honour Service Level Agreements and protect high-priority slices (e.g., public safety or industrial URLLC) from overload.

2. UE-Slice-MBR (Slice Maximum Bit Rate)

A new QoS parameter, UE-Slice-MBR (also referred to as S-MBR), limits the aggregate bit rate of a single UE across all its PDU Sessions that belong to the same S-NSSAI.

Applies to the sum of both GBR and non-GBR QoS flows of that UE on that slice.
Enforced primarily in the RAN (the AMF provides the value to the gNB via NGAP).
Can also be considered by the PCF for policy decisions.
Optionally complemented by network-wide monitoring of aggregate data rate per slice (e.g., via NWDAF).

This prevents a single UE from consuming an unfair share of a slice’s resources and gives operators a clear per-UE, per-slice rate ceiling.

3. Network Slice Simultaneous Registration Group (NSSRG)

Subscription data in the UDM can now include NSSRG information for each S-NSSAI.

NSSRG indicates which sets of S-NSSAIs a UE is allowed to have simultaneously in its Allowed NSSAI.
The AMF uses this information to restrict the combination of slices granted to the UE.
This supports business and technical constraints (e.g., certain enterprise and public slices must not be used together, or regulatory isolation requirements).

4. RAN Slicing Enhancements

Release 17 significantly improves RAN awareness of slices so that radio procedures themselves become slice-aware:

Slice-based Cell Reselection

Network Slice AS Groups (NSAGs) group one or more S-NSSAIs.
The network (via SIB or RRC Release) can provide frequency priorities and cell lists per NSAG.
The UE combines NSAG priority (from NAS) with frequency priority (from RRC) when performing inter-frequency cell reselection.
This steers UEs toward cells/frequencies that actually support the slices they need, reducing failed access attempts and latency.

Slice-based RACH Configuration

Different Random Access configurations (preamble partitioning, higher-priority power ramping, dedicated RACH occasions) can be associated with different NSAGs.
High-priority slices (e.g., URLLC or public safety) can obtain faster, more reliable access.

Service Continuity and Redirection

Support for Target NSSAI and slice-aware redirection so the Core can guide the UE toward a more suitable cell or frequency when the current cell does not support the required slices.
Enhanced signalling on NG, Xn, F1 and E1 interfaces to carry UE-Slice-MBR and related slice information.

Summary of Key Phase-2 Features

Feature	Main Entity / Location	What it Controls / Enables	Benefit
NSAC / NSACF	Core (new NF)	# of UEs and # of PDU Sessions per slice	Enforce capacity SLAs
UE-Slice-MBR	RAN (enforcement) + Core	Aggregate bit rate of one UE on one slice	Fairness and resource protection
NSSRG	UDM → AMF	Which slices a UE may register to simultaneously	Business & isolation constraints
NSAG + Slice-based reselection	RAN + NAS	Cell/frequency selection according to needed slices	Faster access to the right resources
Slice-based RACH	RAN	Differentiated random-access parameters per slice group	Priority access for critical slices

Practical Impact

These enhancements close several important gaps:

Operators can now guarantee that a slice will not be overloaded by too many UEs or sessions.
Per-UE rate limits protect shared slices from abusive or high-volume users.
Simultaneous-registration rules support complex multi-slice business models.
RAN procedures become intelligent about slice availability, improving accessibility and reducing unnecessary signalling.

Together they move network slicing from a largely Core-centric concept to a system-wide capability that is enforceable end-to-end and usable in commercial multi-vertical environments. Later releases continue to build on this foundation with further automation, service continuity, and management enhancements, but Release 17 Phase 2 provides the essential operational controls that make large-scale slicing practical.

13) Edge Computing Support

Edge Computing Support in 3GPP Release 17 provides native, standardized mechanisms that make Multi-access Edge Computing (MEC) a first-class citizen of the 5G System.

While the basic 5G architecture has allowed traffic to be steered toward local Data Networks since Release 15, Release 17 introduces dedicated procedures, a new network function, and clearer connectivity models so that Edge Application Servers (EAS) can be discovered efficiently, traffic can be broken out locally with low latency, and the system can handle UE mobility and edge relocation gracefully.

Key Architectural Building Blocks

Edge Application Server Discovery Function (EASDF)

A new 5GC Network Function whose primary role is intelligent DNS handling for edge discovery:

Intercepts or processes DNS queries from the UE (under SMF instruction).
Can add EDNS Client Subnet (ECS) options, forward queries to central or local DNS servers, and report relevant information back to the SMF.
Enables the SMF to learn the IP address (or FQDN) of a suitable EAS that is topologically close to the UE.
Supports multiple instances per PLMN and is discovered/selected via the NRF.

Connectivity Models Supported

Distributed Anchor Point — The PDU Session Anchor (PSA) UPF itself is located at a local site close to the UE. The PSA may be changed (SSC mode 2 or 3) as the UE moves.
Session Breakout — A central PSA UPF remains the IP anchor, while one or more Local PSA (L-PSA) UPFs are inserted. Traffic for edge applications is selectively diverted to the L-PSA using UL Classifier (UL CL) or multi-homing Branching Point mechanisms.
Multiple PDU Sessions — The UE establishes separate PDU Sessions (possibly with different DNNs/S-NSSAIs) for edge versus central traffic.

These models give operators flexibility depending on whether they prefer a single IP address for the UE or optimized local breakout.

EAS Discovery and Re-discovery

Discovery

During or after PDU Session establishment the SMF can select an EASDF and instruct it how to handle DNS queries for specific FQDNs. The EASDF returns the address of a nearby EAS; the SMF can then insert or select the appropriate local UPF/DNAI so that subsequent application traffic is routed optimally.

Re-discovery

When the optimal edge location changes (UE mobility, edge relocation, L-PSA insertion/change/removal, or AF trigger), the system can indicate to the UE that previously cached EAS information is stale. The UE then re-initiates discovery to obtain a new, better EAS. This keeps latency low even as the UE moves.

Application-Layer Enablement (TS 23.558)

In parallel with the Core enhancements, Release 17 defines an Edge Enabler Layer that sits between Application Clients (ACs) on the UE and Edge Application Servers:

Edge Enabler Client (EEC) on the UE
Edge Enabler Server (EES) and Edge Configuration Server (ECS) in the Edge Data Network
Service provisioning, rich EAS discovery (with filters), capability exposure (location, QoS, etc. via NEF/PCF), and dynamic availability notifications.

This layer makes edge-aware applications portable and able to discover and adapt to available edge resources without deep knowledge of the underlying 5GC procedures.

Additional Supporting Features

Dynamic insertion, change, or removal of Local PSA UPFs and UL CL/BP based on DNS results or AF influence.
Support for both pre-established and dynamic session-breakout configurations.
Coordination with network slicing (edge traffic can be associated with specific S-NSSAIs).
Exposure of network capabilities to the Edge Application Servers.
Handling of edge relocation while maintaining service continuity where possible.

Benefits and Practical Impact

Aspect	Release 17 Contribution	Resulting Benefit
EAS Discovery	EASDF + DNS-based procedures	UE finds the nearest suitable application server
Local Breakout	Clear Session Breakout & Distributed Anchor models	Lower latency, reduced transport load
Mobility / Relocation	Standardized re-discovery triggers	Maintains optimal edge selection as UE moves
Application Portability	Edge Enabler Layer (EEC/EES/ECS)	Apps work across different edge deployments
Operator Control	SMF-driven DNS rules + AF influence	Flexible policy and traffic steering

These enhancements are particularly valuable for latency-sensitive services such as:

Augmented / Virtual / Extended Reality (AR/VR/XR)
Cloud gaming
Industrial automation and real-time control
Vehicle-to-Everything (V2X) and autonomous driving applications
Content caching and media processing at the edge

Relationship to Later Releases

Release 18 and beyond continue to refine edge support (roaming scenarios, further reduction of impact on central NFs, improved common DNAI/EAS selection, etc.). Release 17, however, established the essential native 5GC mechanisms and the application enablement framework that make large-scale, standards-based edge computing practical.

In summary, Release 17 Edge Computing Support transforms edge from an operator-specific overlay into an integrated, discoverable, and mobility-aware part of the 5G System—enabling consistent low-latency services across different deployments and use cases.

14) Access Traffic Steering, Switching and Splitting (ATSSS) Phase 2

Access Traffic Steering, Switching and Splitting (ATSSS) Phase 2 in 3GPP Release 17 significantly enhances the multi-access connectivity framework first introduced in Release 16.

ATSSS allows a UE to establish a Multi-Access PDU (MA PDU) Session that can simultaneously use one 3GPP access (e.g., NG-RAN) and one non-3GPP access (e.g., Wi-Fi or trusted/untrusted non-3GPP). Traffic can be steered, switched, or split across the two accesses according to network policy and real-time conditions. Phase 2 improves measurement accuracy, steering flexibility, and interworking with EPC.

Core Concept Recap (Release 16 Baseline)

An MA PDU Session has independent user-plane resources on both accesses and two N3/N9 tunnels toward the PSA UPF.
Steering is controlled by ATSSS rules (provided to the UE) and corresponding rules in the UPF.
Supported steering functionalities include:
- ATSSS Low-Layer (ATSSS-LL)
- Multipath TCP (MPTCP)
Basic steering modes: Active-Standby, Smallest Delay, Load Balancing, Priority-Based.
Performance Measurement Function (PMF) protocol used for RTT and access availability measurements (typically over the default QoS flow).

Key Phase 2 Enhancements

1. Steering Mode and Measurement Improvements

PMF Measurements per QoS Flow

In Release 16, performance measurements (RTT, etc.) were performed over the default QoS flow and applied roughly to the whole MA PDU Session. Release 17 allows RTT and Packet Loss Rate (PLR) measurements to be conducted over a specific QoS flow.

The network decides during MA PDU Session establishment whether measurements for a given data flow use the default QoS flow or the same QoS flow that carries the data.
This provides much more accurate, flow-specific performance information for steering decisions.

Load-Balancing Enhancements

Support for load-balancing without pre-defined split percentages.
The split ratio can be determined dynamically based on current conditions rather than fixed configuration.
Additional steering-mode indicators and threshold conditions improve control and flexibility.

Threshold Conditions

Steering modes (especially Priority-Based and others) can now incorporate explicit threshold conditions (e.g., based on RTT, PLR, or load) that trigger switching or splitting behaviour.

These changes make steering more responsive to actual application and network conditions.

2. Support for Hybrid EPC / 5GC MA PDU Sessions

A major practical enhancement: an MA PDU Session can now have:

One leg over 3GPP access connected to EPC (E-UTRAN + EPC PDN Connection), and
The other leg over non-3GPP access connected to 5GC.

(The reverse combination is also supported in related scenarios.)

This enables smooth multipath operation in mixed 4G/5G environments and during migration periods, without requiring both accesses to be fully 5GC-connected.

3. Additional Supporting Capabilities

Better handling of Non-IP type PDN Connections as one leg of an MA PDU Session.
Refined procedures for establishment, modification, and release when one access uses EPC.
Continued support for both ATSSS-LL and MPTCP (and later multipath QUIC considerations in subsequent releases), with clearer capability signalling of which steering functionalities and modes a UE supports.

How Steering Works in Practice (Phase 2)

UE requests (or network triggers) an MA PDU Session.
SMF, guided by PCF policy, generates ATSSS rules for the UE and corresponding N4 rules for the UPF.
PMF measurements (now optionally per QoS flow) provide real-time RTT / PLR / availability data.
UE applies ATSSS rules + local conditions (signal quality, user preference, etc.) for uplink traffic.
UPF applies corresponding rules for downlink traffic.
Traffic can be:
- Fully on one access (Active-Standby or Priority-Based),
- Sent on the access with currently best performance (Smallest Delay),
- Split across both accesses (Load Balancing, with dynamic ratios).

Benefits

Enhancement	Benefit
Per-QoS-flow PMF measurements	More accurate, application-aware steering
Dynamic / threshold-based load balancing	Better utilization of both accesses, improved QoE
Hybrid EPC + 5GC MA PDU Sessions	Seamless multipath during 4G-to-5G transition
Refined steering modes	Greater policy flexibility for operators

Typical Use Cases

Smartphones simultaneously using 5G/4G cellular and Wi-Fi for higher throughput or reliability.
Enterprise or industrial devices that combine licensed and unlicensed access.
Smooth interworking scenarios where part of the network is still EPC-based.
Applications that benefit from lowest-latency path selection or bandwidth aggregation.

Relationship to Later Releases

Subsequent releases continue to evolve multipath connectivity (e.g., further multipath QUIC support, additional analytics-driven steering, multi-USIM interactions). Release 17 Phase 2, however, delivered the critical measurement accuracy and hybrid-access capabilities that make ATSSS robust and commercially useful in real multi-access environments.

In summary, ATSSS Phase 2 transforms multi-access connectivity from a basic dual-path feature into a more intelligent, measurement-driven, and deployment-flexible solution—enabling better performance, reliability, and operator control when a UE can use both 3GPP and non-3GPP accesses at the same time.

15) Multi-USIM Support

Multi-USIM (MUSIM) Support in 3GPP Release 17 standardizes the behaviour of devices that have multiple Universal Subscriber Identity Modules (or equivalent subscriptions) active at the same time.

Prior to Release 17, dual-SIM or multi-SIM operation was largely implementation-specific. This led to inconsistent behaviour, especially for single-Rx/single-Tx UEs that cannot fully operate on two networks simultaneously. Release 17 introduces coordinated mechanisms in both the Core Network and the RAN so that paging collisions are avoided, the network is informed when the UE temporarily leaves one connection, and the UE can indicate preferences about which services it is willing to accept.

What is a Multi-USIM UE?

A Multi-USIM UE maintains a separate registration state with a PLMN (or SNPN) for each USIM, at least over 3GPP access. Typical commercial devices are dual-SIM dual-standby (DSDS) with a single transmitter and one or two receivers. The most challenging cases are single-Rx/single-Tx devices that can actively communicate with only one network at a time.

Key Features Introduced in Release 17

1. Paging Timing Collision Control

When two USIMs produce overlapping paging occasions, the UE may miss pages.

In 5GS the UE can trigger a new 5G-GUTI reallocation (via Mobility Registration Update) so that the calculated paging occasions change.
In EPS the UE can request an IMSI Offset; the MME returns an accepted offset and both sides use an alternative IMSI value for paging-occasion calculation.

This gives the UE a standards-based way to shift its paging schedule and avoid collisions.

2. Network Notification / Coordinated Leaving

The UE can explicitly inform Network A that it needs to leave (or temporarily suspend activity on) Network A because of activity on Network B. Two main approaches are supported:

Leaving RRC_CONNECTED (connection release requested by the UE for MUSIM reasons).
Remaining in RRC_CONNECTED while using configured MUSIM gaps (periodic or aperiodic gaps during which the UE can tune to the other network).

The UE can request preferred gap patterns; the network may configure them. This prevents the network from wasting resources by scheduling data or expecting responses while the UE is occupied elsewhere.

3. Paging Cause Indication for Voice

The network can include a simple paging-cause indication (currently focused on “voice”) in the paging message. The MUSIM UE can therefore decide, based on the service type and its own priorities, whether to respond immediately, reject the page, or postpone action.

4. Reject Paging Request

The UE can respond to a page by indicating that it does not accept the paging and wishes to return to CM-IDLE / RRC_IDLE (or equivalent). This is useful when the UE is engaged in a higher-priority activity on the other USIM.

5. Paging Restriction

The UE can request the network to restrict future paging:

No paging at all, or
Paging only for voice, or
Paging only for traffic on selected PDU Sessions / PDN Connections, or
Combinations of the above.

This gives the user or the device policy control over which services are allowed to interrupt the other subscription.

RAN Aspects

MUSIM gap configuration and UE Assistance Information for preferred gaps.
Support for both periodic and aperiodic MUSIM gaps (with limits on the number that can be requested).
Coordination of leaving assistance and gap assistance in RRC signalling (including during conditional handover or PSCell change in some cases).

Benefits

Problem	Release 17 Solution	Result
Paging occasion collision	5G-GUTI reallocation / IMSI Offset	Reliable reception of pages on both USIMs
Network unaware of UE absence	Connection release or MUSIM gaps	Reduced wasted scheduling & better resource use
Unknown service priority	Paging cause (voice) + Reject / Restriction	UE can prioritise according to user preference
Inconsistent dual-SIM behaviour	Standardised procedures	Predictable, interoperable multi-SIM devices

Practical Impact

Dual-SIM smartphones behave more reliably when one SIM is in a call or data session and the other receives a page.
Power consumption and network signalling overhead are reduced because the UE and network coordinate absences.
Operators can implement consistent policies for multi-SIM devices instead of relying on proprietary UE behaviour.
The features apply to both 5GS and EPS, easing deployment in mixed 4G/5G networks.

Limitations and Later Evolution

Release 17 primarily targets single-Rx/single-Tx architectures and the most common dual-SIM scenarios. More advanced dual-Rx dual-Tx devices already have greater flexibility and benefit less from some of the features. Subsequent releases continue to refine multi-SIM operation (additional gap patterns, better analytics, multi-USIM interactions with other features such as ATSSS, etc.).

In summary, Multi-USIM Support in Release 17 turns an implementation-specific dual-SIM experience into a standardised, coordinated system feature. By solving paging collisions, enabling explicit network notification of absences, and giving the UE control over which pages it accepts, it significantly improves reliability and efficiency for the large population of multi-SIM devices in the market.

16) Protocol and Implementation Impact

Release 17 introduces a large number of features that collectively require significant but carefully managed changes across the protocol stack and in product implementations. The design philosophy was to maximise reuse of existing procedures and network functions while adding targeted extensions, keeping the impact on legacy UEs and earlier-release networks as low as possible.

1. Radio Resource Control (RRC) – TS 38.331

RRC carries the majority of the new configuration and assistance information:

New Information Elements and containers for RedCap indication, NTN-specific parameters (e.g., ephemeris, timing advance, Doppler pre-compensation), FR2-2 (52.6–71 GHz) band and SCS configurations, MBS session joins, SL DRX and inter-UE coordination, MUSIM gaps and leave assistance, slice-based cell reselection (NSAG), UE-Slice-MBR, pre-configured measurement gaps for positioning, on-demand PRS, IAB simultaneous operation timing modes, and enhanced MIMO TCI/beam reporting.
Extensions to existing messages (RRCSetup, RRCReconfiguration, RRCRelease, SIB1, new SIBs such as SIB16/SIB17/SIB19-type information) to carry the above.
Support for Small Data Transmission (SDT) in Inactive state and positioning in Inactive state, requiring careful state-machine handling.

Implementation note: RRC message size and parsing complexity increase. Vendors must carefully manage ASN.1 extensions and ensure backward-compatible decoding.

2. Non-Access Stratum (NAS) – TS 24.501 / 24.301

Multi-USIM procedures: connection release for MUSIM reasons, paging restriction, reject paging, paging-cause indication, 5G-GUTI reallocation / IMSI offset handling.
Network Slice Admission Control related signalling and UE-Slice-MBR.
ATSSS Phase 2 rules and capability signalling (including hybrid EPC/5GC MA PDU Session support).
Edge-related DNS settings delivered via Protocol Configuration Options (PCO).
NTN-specific registration and mobility handling.
MBS session management and ProSe/Sidelink relay related NAS aspects.

Implementation note: Dual-registration state machines for Multi-USIM devices become more complex; careful coordination between the two USIM contexts is required.

3. NG Application Protocol (NGAP) – TS 38.413 and related interfaces

New or extended IEs for RedCap Indication, IAB-node indication, NTN-related information, MBS session resources, UE-Slice-MBR, NSAC-related admission control, Target NSSAI, positioning assistance, MUSIM assistance, and ATSSS-related information.
Support for MBS Shared Delivery and Local Delivery paths.
Enhanced procedures for PDU Session resource setup/modification to carry slice MBR and edge/DNAI information.

Xn, F1, and E1 interfaces received corresponding extensions (especially for IAB, multi-TRP, slice MBR, and MBS).

4. User-Plane and Lower-Layer Impacts

PDCP / RLC / MAC: Support for MBS (PTM/PTP), SDT, enhanced repetitions and DMRS bundling for coverage, SL DRX, inter-UE coordination messages, and MUSIM gap handling.
Physical layer: New SCS (480/960 kHz) and channel bandwidths for FR2-2, RedCap bandwidth/antenna restrictions, NTN-specific timing/frequency compensation, enhanced multi-TRP and beam management, positioning reference signals (on-demand PRS), and IAB simultaneous Tx/Rx timing modes.
New Network Functions or upgraded entities: NSACF, EASDF, MB-SMF / MB-UPF (lightweight upgrades of existing SMF/UPF).

5. Implementation Considerations by Node Type

Node	Major Impacts	Complexity Drivers
UE	Many optional features; capability signalling becomes richer; dual-USIM state machines; power-saving vs. reliability trade-offs	Feature combinations, battery impact, single-Rx limitations
gNB / IAB	Beam/TCI management, multi-TRP, MBS delivery modes, slice-aware scheduling & RACH, NTN/IAB timing, RedCap handling	Scheduler complexity, RF (especially FR2-2 and simultaneous operation)
AMF / SMF	NSAC, UE-Slice-MBR, ATSSS Phase 2, Multi-USIM coordination, edge DNS steering, MBS session management	Policy integration, multi-access state handling
UPF	ATSSS steering (per-QoS-flow measurements), MBS Shared Delivery, local breakout for edge	User-plane performance and measurement accuracy
New/Upgraded NFs	NSACF, EASDF, MB-SMF/MB-UPF	Service-based interface implementation

6. Cross-Cutting Implementation Themes

Backward compatibility: Almost all features are optional and indicated via UE capability or network configuration. Legacy UEs continue to work.
Feature combinations: Real products must handle simultaneous activation of RedCap + power saving, NTN + positioning, Slicing + Edge + ATSSS, Multi-USIM + Sidelink, etc. Testing matrices grow significantly.
Capability signalling: UE capability containers expanded substantially; network must correctly interpret and act on the new bits.
Performance vs. complexity trade-off: Many features (coverage repetitions, multi-TRP, on-demand PRS, MUSIM gaps) improve KPIs but increase processing, memory, and power demands.
Testing and certification: New test cases required for RedCap, NTN, FR2-2, MBS, positioning in Inactive, Multi-USIM collision scenarios, IAB simultaneous operation, and slice-aware mobility.
Software vs. hardware: Most Core and higher-layer changes are software. FR2-2, advanced MIMO, and high-end IAB/repeater features have stronger RF and hardware implications.

7. Overall Assessment

Release 17 is evolutionary rather than revolutionary at the protocol level. It reuses the existing SBA, RRC state machine, and NGAP framework wherever possible, adding targeted extensions. The cumulative impact is nevertheless substantial: UE and gNB protocol stacks become noticeably richer, Core Network functions gain new control points (admission, edge discovery, multipath, multi-USIM), and system testing effort increases.

Vendors that invested early in modular, capability-driven implementations (especially for RRC and NAS) experienced lower integration cost. The reward is a more complete 5G platform that supports reduced-capability devices, satellite, broadcast, high-accuracy positioning, intelligent multi-access, and robust multi-SIM behaviour—laying a solid foundation for 5G-Advanced.

17) Industry and Use-Case Implications

Release 17 marks the point at which 5G transitions from a high-performance mobile broadband platform into a versatile, multi-vertical system. The combination of Reduced Capability devices, Non-Terrestrial Networks, refined slicing and edge support, broadcast/multicast, high-accuracy positioning, sidelink relays, coverage and power-saving improvements, and multi-access/multi-SIM enhancements unlocks practical deployments across a wide range of industries.

1. Consumer and Mass-Market Mobile

RedCap / NR-Light brings mid-tier 5G devices (wearables, mid-range smartphones, fixed wireless access CPE, video cameras) at significantly lower cost and power than full eMBB devices.
UE power-saving features (PEI, SL/Uu DRX enhancements, PDCCH skipping, measurement relaxation) extend battery life for everyday smartphones and wearables.
Multi-USIM support improves the dual-SIM experience that is standard in many markets.
ATSSS Phase 2 enables seamless cellular + Wi-Fi aggregation with better performance awareness.

Result: Broader 5G device ecosystem and better user experience on mid-range and dual-SIM devices.

2. Industrial IoT, Smart Manufacturing & Industry 4.0

High-accuracy positioning (sub-meter commercial, ~20 cm IIoT targets) with low latency and Inactive-state support enables real-time asset tracking, AGV navigation, and worker safety.
Time-Sensitive Communication refinements, coverage enhancements, and ultra-reliable features support motion control and deterministic networking.
Network slicing Phase 2 (NSAC, UE-Slice-MBR, RAN slice awareness) allows dedicated, enforceable slices for factory floors with guaranteed capacity and isolation.
Edge computing (EASDF + local breakout) keeps control loops and analytics close to the machines.
RedCap provides cost-effective sensors, actuators, and cameras.

Result: Private 5G networks become commercially viable for smart factories, ports, mines, and warehouses.

3. Automotive, Transportation & V2X

Sidelink enhancements (power saving, inter-UE coordination, UE-to-UE and UE-to-Network relays) improve reliability for vulnerable road users and extend coverage.
Advanced V2X benefits from better sidelink and positioning.
NTN provides connectivity for remote highways, maritime, and aviation corridors.
High-accuracy positioning supports lane-level navigation and cooperative manoeuvres.

Result: Stronger foundation for connected and automated mobility, including safety-critical direct communications.

4. Public Safety, Mission-Critical & Emergency Services

Sidelink relays (U2N and U2U) and enhanced ProSe enable direct-mode and coverage-extension communications when the macro network is unavailable.
MBS (Multicast/Broadcast) efficiently delivers group communications, video, and alerts to large numbers of first responders.
NTN ensures connectivity in disaster zones or remote areas.
Priority and pre-emption mechanisms combined with slicing deliver guaranteed service.

Result: 5G becomes a credible long-term replacement or complement to legacy LMR/TETRA systems.

5. Media, Entertainment & Content Delivery

Multicast/Broadcast Services (MBS) enable efficient delivery of live TV, stadium content, software updates, and large-scale event video without saturating unicast capacity.
Edge computing supports low-latency cloud gaming, AR/VR/XR, and personalized content insertion.
FR2-2 spectrum (up to 71 GHz) and advanced MIMO provide extreme capacity for dense venues.

Result: New business models for broadcasters, operators, and venue owners.

6. Satellite / Non-Terrestrial & Remote Connectivity

NR-NTN and IoT-NTN bring 5G to ships, aircraft, rural areas, and disaster zones using LEO/MEO/GEO satellites and HAPS.
Combined with RedCap and power-saving features, low-cost, long-battery IoT devices can operate over satellite.
IAB and repeaters help densify terrestrial coverage that complements satellite.

Result: True global 5G coverage and new satellite–terrestrial hybrid services.

7. Fixed Wireless Access, Rural & Developing Markets

Coverage enhancements (PUSCH repetitions, TBoMS, DMRS bundling, Msg3 repetition) improve cell-edge performance.
IAB and NR Repeaters reduce the need for fibre.
RedCap and power saving lower device and operational costs.
NTN fills remaining gaps.

Result: More viable 5G FWA and rural broadband business cases.

8. Enterprise, Private Networks & Vertical Slicing

Network slicing Phase 2 provides the admission control, rate limiting, and RAN awareness needed for commercial SLA-backed slices.
Edge computing + local breakout supports enterprise applications on-premises or at the operator edge.
NPN enhancements improve standalone and public-network-integrated private networks.
Multi-USIM and ATSSS give flexible device connectivity options for enterprise users.

Result: Operators can offer differentiated, high-value enterprise and vertical services with confidence.

Cross-Industry Enabling Themes

Theme	Key Rel-17 Enablers	Industries Benefiting Most
Lower device cost & power	RedCap, power saving, eDRX	IoT, wearables, industrial sensors, consumer
Coverage & reach	Coverage enh., IAB, Repeaters, NTN	Rural, maritime, public safety, logistics
Determinism & precision	Positioning, TSC, slicing, edge	Manufacturing, automotive, energy
Group & efficient delivery	MBS, Sidelink	Public safety, media, V2X, software update
Multi-access flexibility	ATSSS Phase 2, Multi-USIM	Consumer, enterprise, transportation
Enforceable isolation	Slicing Phase 2 (NSAC, UE-Slice-MBR, RAN awareness)	All private/vertical networks

Strategic Takeaway

Release 17 does not introduce a single revolutionary radio technology. Instead, it delivers a balanced portfolio of pragmatic enhancements that remove the remaining barriers to commercial 5G adoption outside pure enhanced mobile broadband.

Operators gain tools for cost-effective densification, differentiated services, and hybrid terrestrial–satellite networks. Device makers can address mid-tier and IoT markets. Vertical industries finally obtain the combination of performance, cost, coverage, and manageability required for large-scale digital transformation.

In essence, Release 17 makes 5G usable at scale across the full spectrum of consumer, enterprise, industrial, public-safety, and remote-connectivity use cases — setting the stage for the further AI-native and immersive capabilities of 5G-Advanced.

18) Real-World Applications of 3GPP Release 17

Release 17 features are moving rapidly from specification into commercial networks, trials, and early deployments. Below are concrete examples of how the key capabilities are being applied in practice (as of 2025–2026).

1. Reduced Capability (RedCap / NR-Light) Devices

RedCap has seen the fastest commercial traction among Rel-17 radio features.

China: Large-scale commercial rollout since mid-2024. By late 2024, hundreds of thousands of 5G base stations supported RedCap. Deployments span smart manufacturing, power grids, ports, healthcare (e.g., Li Huili Hospital in Ningbo), video surveillance, and smart cities.
Europe & Asia: Commercial launches by operators including Deutsche Telekom and Telefónica (Germany), SoftBank (Japan), M1 (Singapore – first enterprise RedCap in Southeast Asia), EE and Vodafone (UK), and several Middle Eastern operators.
Use cases in the field:
- Industrial sensors and cameras with multi-year battery life
- Wearables and mid-tier IoT gateways
- Smart-grid monitoring and video surveillance
- Cost-effective Fixed Wireless Access CPE and routers

RedCap is bridging the gap between high-end eMBB devices and low-power LPWA technologies (NB-IoT/LTE-M).

2. Non-Terrestrial Networks (NTN)

NTN is progressing from trials to operator-grade integration.

Iridium + Deutsche Telekom: Integration of Iridium’s LEO NTN Direct with DT’s global IoT footprint for 3GPP-compliant NB-IoT NTN. Commercial service targeted for 2026, enabling seamless terrestrial-to-satellite roaming for logistics, agriculture, automotive, and emergency response.
Direct-to-Device (D2D) demonstrations:
- Viasat demos in Brazil with unmodified smartphones and IoT devices over L-band.
- OQ Technology emergency broadcast from LEO satellite to standard smartphones (99.99% success rate).
- 5GAA demos of satellite + 5G-V2X for emergency messaging and hazard warnings.
Starlink and others: Growing Direct-to-Device text and light data services, with 3GPP Rel-17 alignment accelerating standardization.

Real impact: Connectivity for remote assets, maritime, aviation, rural areas, and disaster recovery without proprietary satellite phones.

3. Multicast and Broadcast Services (MBS) / 5G Broadcast

Live 5G Broadcast proofs-of-concept in Brazil (Rohde & Schwarz, Qualcomm, Motorola) delivering television content and value-added services directly to smartphones, supporting Brazil’s TV 3.0 initiative and major events such as the FIFA World Cup.
Operators and broadcasters are evaluating MBS for stadium content, software/firmware updates, public alerts, and efficient group communications.

4. Private 5G Networks & Industrial Applications

Many private 5G deployments leverage Rel-17 improvements in coverage, positioning, slicing, edge computing, and RedCap:

Tesla Gigafactory Texas: Private 5G eliminated AGV stoppages previously caused by unstable Wi-Fi.
Jaguar Land Rover (UK): Connectivity inside a five-story paint shop that was previously too expensive to wire.
Lufthansa Cargo (LAX): 60% reduction in processing time by replacing unreliable Wi-Fi/public cellular.
Numerous smart ports, steel plants, mines, and factories in China and Europe using RedCap sensors, high-accuracy positioning, and dedicated slices.

5. Positioning, Sidelink & Automotive

High-accuracy positioning trials supporting indoor industrial tracking and outdoor lane-level applications.
5GAA demonstrations combining satellite NTN with 5G-V2X sidelink for emergency messaging and vulnerable-road-user protection.
Growing interest in UE-to-Network and UE-to-UE relays for public-safety and coverage extension.

6. Coverage, IAB, Repeaters & Power Saving

Operators are using Rel-17 coverage enhancements (PUSCH repetitions, DMRS bundling, Msg3 repetition) to improve mid-band and cell-edge performance.
IAB and NR Repeaters are being deployed for rapid densification and indoor/outdoor coverage fill without fiber.
Power-saving features (PEI, enhanced DRX, PDCCH skipping) are being activated to extend smartphone and IoT device battery life.

7. System-Level Features in Action

Network Slicing Phase 2: Used in private and hybrid networks for enforceable capacity and isolation (NSAC, UE-Slice-MBR).
Edge Computing: Local breakout and EAS discovery supporting low-latency industrial control and media applications.
ATSSS: Multi-access (cellular + Wi-Fi) sessions improving reliability and throughput for enterprise and consumer devices.
Multi-USIM: Standardized dual-SIM behaviour improving user experience on commercial smartphones.

Summary of Maturity (2026 Snapshot)

Feature Area	Commercial Status (2026)	Leading Regions / Examples
RedCap	Commercial launches & scaling	China, Germany, UK, Singapore, Middle East
NTN (IoT & NR)	Operator integrations & D2D trials → early service	DT + Iridium, Viasat, Starlink, OQ Technology
MBS / 5G Broadcast	PoCs and early trials	Brazil, Europe, Asia
Private 5G + Positioning	Widespread industrial deployments	Tesla, JLR, ports, factories globally
IAB / Repeaters / Coverage	Growing commercial use	Dense urban & rural densification
Slicing / Edge / ATSSS	Enabled in advanced SA networks	Enterprise & vertical slices

Bottom line: Release 17 is no longer just a specification. RedCap is already in commercial service at scale, NTN is entering operator IoT portfolios, private 5G networks are delivering measurable productivity gains, and broadcast, positioning, and multi-access features are moving from labs into live networks. These real-world applications confirm that Release 17 successfully broadened 5G beyond enhanced mobile broadband into a practical platform for IoT, industry, public safety, and global coverage.

19) Consumer Broadband Improvements

While Release 17 is widely recognized for expanding 5G into IoT, industrial, and satellite use cases, it also delivers meaningful enhancements for everyday consumer mobile broadband (eMBB) experiences on smartphones, tablets, and Fixed Wireless Access (FWA) devices. These improvements focus on higher throughput (especially uplink), better spectral efficiency, expanded spectrum, improved coverage and reliability, more flexible multi-connectivity, and longer battery life.

1. Advanced MIMO and Multi-TRP for Higher Capacity & Reliability

Release 17 further enhanced massive MIMO and multi-Transmission/Reception Point (multi-TRP) operation:

Support for multi-TRP coordination across different Physical Cell IDs (inter-cell multi-TRP).
Improved beam management, unified TCI framework, and richer CSI feedback.
Better performance in high-mobility scenarios and for UEs with multiple antenna panels.

Consumer benefit: Higher average and cell-edge data rates, more consistent video streaming, and improved reliability in dense urban environments or when moving at speed (trains, vehicles).

2. Spectrum Expansion to 71 GHz (FR2-2)

New frequency range FR2-2 (52.6–71 GHz) with support for 480 kHz and 960 kHz subcarrier spacing and channel bandwidths up to 2 GHz.
Enables both licensed and unlicensed (e.g., 60 GHz) operation.

Consumer benefit: Extreme capacity in dense venues (stadiums, airports, city centers) and potential for multi-gigabit peak rates. Complements existing mid-band and lower mmWave deployments.

3. Carrier Aggregation and Multi-Radio Dual Connectivity Enhancements

Expanded FR2 CA combinations (e.g., 28 GHz + 28 GHz, 40 GHz + 40 GHz in downlink; 28 GHz + 40 GHz in uplink).
SCG deactivation, more robust PSCell addition/change, and faster SCell activation using temporary reference signals.
UL Tx Switching (Release 17 enhancements) that optimizes the use of available UE transmit chains across TDD and FDD carriers.

Real-world example: T-Mobile demonstrated over 550 Mbps uplink speeds in sub-6 GHz spectrum using Release 17 UL Tx Switching — a world record at the time and a significant boost for uploading 4K video, cloud gaming, and XR applications.

Consumer benefit: Higher peak and sustained speeds, better uplink performance (increasingly important for content creation and interactive apps), and lower latency when combining multiple bands.

4. Coverage Enhancements

Improved PUSCH repetitions (up to 32, available-slot counting), Transport Block processing over multiple slots (TBoMS), DMRS bundling, and Msg3 repetition.
These primarily address uplink coverage bottlenecks.

Consumer benefit: Better performance at the cell edge, fewer dropped connections in buildings or rural areas, and more reliable service on mid-band TDD networks without requiring denser site deployment.

5. UE Power Saving for Longer Battery Life

Paging Early Indication (PEI), enhanced DRX, PDCCH skipping, Search Space Set Group switching, and relaxed RLM/BFD measurements.
Applicable to both full eMBB smartphones and RedCap devices.

Consumer benefit: Noticeably longer battery life during typical mixed-use patterns (browsing, video, social media) while maintaining good responsiveness.

6. Multi-Access and Multi-SIM Improvements

ATSSS Phase 2: More intelligent steering, switching, and splitting between cellular and Wi-Fi, with per-QoS-flow performance measurements.
Multi-USIM support: Standardized handling of dual-SIM devices (paging collision avoidance, coordinated leaving, voice paging indication).

Consumer benefit: Smoother Wi-Fi + cellular aggregation and a more reliable dual-SIM experience (common in many markets).

7. Other Supporting Improvements

Enhanced mobility and high-speed train support extended to FR2.
Better support for cloud gaming QoS and interactive applications.
IAB and NR Repeaters enable cost-effective densification that improves consumer capacity and coverage in hard-to-reach areas.

Summary of Consumer Impact

Improvement Area	Key Rel-17 Feature(s)	Primary Consumer Benefit
Downlink capacity & speed	Multi-TRP, FR2-2, CA extensions	Higher peak & average speeds
Uplink performance	UL Tx Switching, CA, coverage enhancements	Faster uploads, better interactive apps
Coverage & reliability	PUSCH/PUCCH enhancements, multi-TRP	More consistent service at cell edge
Battery life	PEI, PDCCH skipping, DRX enhancements	Longer usage time between charges
Multi-connectivity	ATSSS Phase 2, Multi-USIM, SCG deactivation	Seamless Wi-Fi + cellular, better dual-SIM
Dense venue capacity	FR2-2, advanced MIMO	Better experience in stadiums & cities

Bottom line: Release 17 does not reinvent consumer mobile broadband, but it meaningfully refines it. Users experience higher and more consistent speeds (especially uplink), better coverage, longer battery life, and improved multi-access/dual-SIM behaviour. Combined with the ongoing densification enabled by IAB and the capacity of new spectrum, these enhancements help operators deliver a superior everyday 5G experience while preparing networks for more demanding applications such as XR and real-time cloud services.

20) Enhancements for User Equipment (UE) in 3GPP Release 17

Release 17 introduces a wide range of UE-side improvements that reduce complexity and cost, extend battery life, improve dual-SIM behaviour, enhance coverage and mobility, and enable new device categories. These changes benefit both full eMBB smartphones and the new class of mid-tier / IoT devices.

1. Reduced Capability (RedCap / NR-Light) Devices

The most significant new UE category in Release 17.

Key simplifications compared with regular NR UEs:

Maximum bandwidth: 20 MHz (FR1) / 100 MHz (FR2)
Reduced number of receive antennas (typically 1Rx or 2Rx)
Lower mandatory modulation (64-QAM)
Half-duplex FDD allowed
No requirement for carrier aggregation or dual connectivity
Relaxed RRM measurements

Target peak rates: roughly 85–226 Mbps downlink (depending on configuration).

Benefits: Lower chipset cost, smaller form factor, and significantly better power efficiency. Ideal for wearables, industrial sensors, video cameras, mid-tier IoT gateways, and cost-sensitive FWA devices.

2. UE Power Saving Enhancements

One of the largest focuses of Release 17 for both eMBB and RedCap UEs.

Idle / Inactive mode:

Paging Early Indication (PEI) — Network indicates whether the UE needs to decode the full paging message, avoiding unnecessary wake-ups.
Additional TRS/CSI-RS occasions for better synchronization before paging.
Extended DRX (eDRX) cycles (especially beneficial for RedCap; up to hours in some configurations).
Small Data Transmission (SDT) allowing data transfer while remaining in RRC Inactive.

Connected mode:

PDCCH Skipping — Network can instruct the UE to temporarily stop monitoring PDCCH.
Search Space Set Group (SSSG) Switching — Dynamic switching between dense and sparse PDCCH monitoring configurations.
Relaxation of Radio Link Monitoring (RLM) and Beam Failure Detection (BFD) measurements under good radio conditions or low mobility.
SCG deactivation in dual-connectivity scenarios.

Result: Double-digit percentage reductions in modem power consumption for typical traffic patterns, translating into longer battery life for smartphones and multi-day/year life for IoT devices.

3. Multi-USIM (MUSIM) Support

Standardized behaviour for dual-SIM (or multi-SIM) devices, especially single-Rx/single-Tx architectures:

Paging occasion collision avoidance (via 5G-GUTI reallocation or IMSI offset).
Coordinated leaving / MUSIM gaps so the UE can notify one network when it needs to serve the other.
Paging cause indication (e.g., voice) and ability to reject paging or request paging restrictions.
Better handling of connection release for MUSIM reasons.

Benefit: More predictable and reliable dual-SIM experience with less wasted network signalling and fewer missed pages or calls.

4. Coverage-Related UE Enhancements

Support for increased PUSCH repetitions (up to 32), available-slot counting, Transport Block over Multiple Slots (TBoMS), and DMRS bundling.
Msg3 (initial access) repetition.
These improve uplink coverage and reliability at the cell edge without requiring higher UE transmit power in every case.

5. MIMO, Beam Management & Multi-Panel Improvements

Enhanced support for UEs with multiple antenna panels.
Unified TCI framework and improved beam reporting / failure recovery for multi-TRP scenarios.
Better performance under high mobility.

6. New Spectrum and Radio Capabilities

Support for FR2-2 (52.6–71 GHz) with new subcarrier spacings (480/960 kHz) and wider bandwidths.
NTN-specific UE behaviour: timing advance, Doppler pre-compensation, and handling of satellite ephemeris information.
Improved UL Tx Switching for better uplink carrier aggregation and MIMO performance.

7. Positioning and Sidelink UE Features

Ability to perform positioning measurements and reporting while in RRC Inactive state (using SDT mechanisms).
Sidelink DRX and inter-UE coordination for power-efficient and more reliable direct device-to-device communication.
Support for UE-to-Network and UE-to-UE relays.

8. Other Notable UE Capabilities

ATSSS client-side support for intelligent traffic steering/splitting between 3GPP and non-3GPP (Wi-Fi) accesses.
Enhanced UE Assistance Information for power saving, scheduling preferences, and release preferences.
Support for MBS reception (multicast/broadcast).

Summary of UE Impact

Category	Main Enhancements	Primary Benefit for Devices
New device class	RedCap	Lower cost, complexity & power
Battery life	PEI, PDCCH skipping, SSSG, eDRX, measurement relaxation	Significantly longer battery life
Dual-SIM experience	Multi-USIM procedures	More reliable dual-SIM operation
Coverage & reliability	Uplink repetitions, DMRS bundling, multi-TRP	Better cell-edge performance
New spectrum / scenarios	FR2-2, NTN support	Access to higher bands and satellite
Direct & group comms	Sidelink DRX/relays, MBS	Efficient D2D and broadcast reception
Positioning	Inactive-state positioning	Lower power location services

Overall, Release 17 makes 5G UEs more diverse, power-efficient, and practical. Full eMBB smartphones gain better battery life, dual-SIM behaviour, uplink performance, and coverage, while the introduction of RedCap opens a large new market for affordable, long-battery mid-tier and IoT devices. These UE enhancements are essential to the broader commercial success of 5G beyond pure high-end mobile broadband.