SPR

Successful PSCell Addition/Change Report

Mobility →
Introduced in Rel-7 Also in: Management, Radio Access Network

SPR is a report generated by a UE upon successful PSCell addition or change, confirming the SCG configuration to the network for efficient mobility and resource management in dual connectivity or carrier aggregation.

Category
Mobility
Introduced
Rel-7
Where
Core Network › Evolved Packet Core
Also touches
2 segments
Specifications
14 specs
SPR Description Purpose Detected Changes Specifications

Description

The Successful PSCell Addition/Change Report (SPR) is a crucial signaling message in 3GPP networks, specifically within the context of dual connectivity (DC) and carrier aggregation (CA) operations. It is transmitted by the User Equipment (UE) to the network, specifically to the Master Node (MN) via the Secondary Node (SN) in EN-DC or NGEN-DC architectures, upon the successful execution of a PSCell (Primary Secondary Cell) addition or modification procedure. The PSCell is the primary cell of the Secondary Cell Group (SCG), which is managed by the Secondary Node (e.g., a gNB in NR or an en-gNB in EN-DC). The SPR serves as an explicit acknowledgment that the UE has successfully applied the new radio resource configuration for the SCG, including the new PSCell, as commanded by the network through an RRC Reconfiguration message.

The generation and transmission of the SPR are triggered by specific conditions defined in the RRC protocol. When the UE receives an RRCReconfiguration message containing the `secondaryCellGroup` configuration (for addition or change of the SCG), it applies the new configuration. Upon successful completion of random access to the new PSCell and application of the SCG configuration, the UE constructs an RRCReconfigurationComplete message. If the reconfiguration included the `sCellToReleaseList` or `sCellToAddModList` for the SCG, or involved a change of the PSCell itself, the UE includes the SPR within this RRCReconfigurationComplete message. The SPR contains critical information elements such as the `measResultSCG`, which includes measurement results for the new PSCell (like RSRP and RSRQ), and potentially other SCG cell measurements, providing the network with immediate feedback on the radio conditions of the newly configured cells.

From an architectural perspective, the SPR flows from the UE to the SN (which receives it as part of the RRC message over the air interface), and the SN then forwards the relevant contents to the MN via the Xn or X2-C interface (e.g., in the SN Reconfiguration Complete message). This allows the MN, which maintains the overall connection and mobility management, to be informed of the successful SCG reconfiguration. The information within the SPR is vital for the network's Radio Resource Management (RRM) algorithms. It confirms the success of the handover-like procedure within the SCG, enables the network to verify that the UE is correctly camped on the intended PSCell, and provides fresh measurement data that can be used for subsequent mobility decisions, load balancing, and link adaptation.

The SPR mechanism enhances the reliability and efficiency of multi-connectivity operations. Without such a report, the network would have to infer success indirectly, potentially leading to delayed failure detection or suboptimal resource states. By providing a confirmed status update, the SPR helps in maintaining synchronization between the UE's configuration and the network's view, reduces the time to recover from failed reconfiguration attempts, and supports advanced features like fast SCG addition for traffic steering and improved data rates. It is a foundational element for the robust operation of features like NR-DC, NE-DC, and NR CA, where rapid and reliable configuration of secondary nodes is essential for harnessing the full potential of aggregated spectrum and multi-RAT deployments.

Purpose & Motivation

The SPR was introduced to address the specific control and management challenges arising from the introduction of dual connectivity and advanced carrier aggregation in 3GPP networks. Prior to DC, mobility events typically involved a single cell change (handover) with a clear success/failure report. With DC, where a UE is connected to a Master Node and a Secondary Node simultaneously, procedures like adding, changing, or releasing the Secondary Cell Group (SCG) became more complex. The network needed a reliable mechanism to confirm that the UE had successfully executed these complex reconfiguration commands, especially the critical step of accessing a new PSCell.

The primary problem the SPR solves is the lack of explicit success reporting for SCG modifications. In its absence, the network might assume a reconfiguration was successful based on the transmission of the command, while the UE could have failed to apply it due to radio issues or configuration errors. This could lead to a desynchronized state where the network schedules data on resources the UE cannot use, causing data loss and inefficient resource utilization. The SPR provides a closed-loop control mechanism, ensuring that the network's RRM entity receives definitive confirmation and fresh radio measurements, enabling it to make informed subsequent decisions.

Historically, as 3GPP evolved from LTE Carrier Aggregation (which involved a single eNB) to Dual Connectivity between LTE and later 5G NR, the need for inter-node coordination intensified. The SPR, introduced in the context of these enhancements, became a cornerstone for reliable multi-connectivity management. It supports the overarching goals of increased data rates, seamless mobility, and load balancing across multiple nodes or frequencies by giving the network a verified 'green light' before fully utilizing the newly configured secondary resources. This explicit reporting is particularly crucial for the robustness of features like conditional PSCell addition/change (CPAC), where the success report validates the execution of a previously prepared conditional configuration.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (99 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-7, normative work from Rel-15.

Rel-15 23 changes

In Release 15, the SPR function was enhanced to support reporting for PSCell changes between different Secondary Node (SN) nodes and to clarify procedures for security key changes alongside bearer termination point changes. It also introduced specific SMTC (SSB-based RRM Measurement Timing Configuration) setting for NR PSCell changes within MR-DC (Multi-RAT Dual Connectivity). Furthermore, the release added reporting of PSCell information specifically for Lawful Interception (LI) purposes.

  • Support for group based event configuration and reporting TS 29.154CR0022
  • Delay budget report and MAC CE adaptation for NR for TS 38.300 TS 38.300CR0042
  • Addition of Annex X for SPID ranges TS 38.300CR0140
  • Activate the transfer policy via chargeable party change procedure TS 29.214CR1578
  • CR on EN-DC bearer type changes in TS 37.340 TS 37.340CR0014
  • Stage 2 CR on combined bearer type and termination point change TS 37.340CR0018

+ 17 more changes

Rel-16 24 changes

In Release 16, the SPR function was enhanced with the introduction of Conditional PSCell Change for intra-SN scenarios without requiring Master Node involvement. This new procedure allowed for more efficient and autonomous secondary node mobility management. Additionally, the release included corrections and clarifications on user plane handling for full configuration during a Secondary Node Change.

  • Report of EPS Fallback TS 29.214CR1635
  • Access Type Report for a MA PDU session TS 29.214CR1640
  • Reallocation of credit reporting to the AF TS 29.214CR1644
  • Addition of streaming trace requirements TS 32.421CR0087
  • Introduction of Conditional PSCell Change for intra-SN without MN involvement TS 37.340CR0210
  • Introduction of additional enhancements for eMTC TS 38.300CR0175

+ 18 more changes

Rel-17 15 changes

In Release 17, the SPR function was enhanced with clarifications on the prepared PSCell addition procedure by a candidate Secondary Node during Conditional PSCell Change/Addition (CPC-A). Furthermore, a correction was introduced to improve Mobility Robustness Optimization (MRO) for Secondary Node Change Failure scenarios.

  • Correction to enable retrieval of Network Provided Location information at mid-call access change TS 29.214CR1676
  • Add some additional MDT requirements TS 32.421CR0096
  • Inter-MN RRC Resume without SN change [InterMNResume] TS 37.340CR0301
  • Addition of SON features enhancement TS 37.340CR0308
  • Addition of SON features enhancement TS 38.300CR0431
  • Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] TS 38.300CR0474

+ 9 more changes

Rel-18 23 changes

In Release 18, the SPR function was enhanced with corrections and optimizations for its retrieval and forwarding procedures. Specific corrections were made to the handling of the PSCell list within the RA (Random Access) report and to the procedures for conditional PSCell addition or change failure. Furthermore, the release introduced the addition of CPAC (Conditional PSCell Addition/Change) detection in the stage 2 specifications.

  • Report Amount for M4, M5, M6 and M7 measurements in LTE TS 28.622CR0272
  • Rel-18 CR TS 28.622 Report Amount parameter in NR TS 28.622CR0288
  • Addition of SON Rel.18 features TS 37.340CR0377
  • Addition of SON features enhancement TS 38.300CR0757
  • Rel-18 CR TS 28.622 Aligning ReportAmount LTE parameters with ImmediateMDT datatype TS 28.622CR0287
  • Rel-18 CR TS 28.622 Change NpnId from dataType to choice to align with TS 38.331 TS 28.622CR0370

+ 17 more changes

Rel-19 14 changes

In Release 19, the SPR function was enhanced through the introduction of new RRC reports for tracing, which were added to previously missing IOCs (Information Object Classes). The release also included corrections and clarifications for the tracing and reporting of these RRC reports within the management system. Furthermore, specific corrections were made to the reporting of the `reportAmount` parameter related to these new RRC reports.

  • Rel-19 CR 28.622 Trace new RRC reports TS 28.622CR0438
  • Rel-19 CR TS 28.622 Add RRC report in missing IOCs TS 28.622CR0526
  • Rel-19 CR 32.421 Trace new RRC reports TS 32.421CR0138
  • Addition of SON enhancements TS 37.340CR0421
  • Support Aerial UE Flight Information Reporting TS 38.300CR1031
  • Addition of SON enhancements TS 38.300CR1034

+ 8 more changes

Explore further

Broader topics and technologies where SPR plays a role.

Defining Specifications

3GPP specifications that define or reference SPR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 23.803 v1700 PCC Architecture Harmonization Study Rel-7
TS 28.622 vk20 Telecommunication Management; Generic NRM Information Service Rel-20
TS 29.154 vj00 Nt Reference Point Protocol Rel-19
TS 29.201 vj00 RESTful Rx Interface for AF-PC Communication Rel-19
TS 29.214 vj20 Policy and Charging Control over Rx Rel-19
TS 29.816 va00 PCRF Failure & Restoration Study Rel-10
TS 29.817 vc10 Study on XML-based Rx interface for PCC Rel-12
TS 32.421 vj30 Subscriber & Equipment Trace Concepts & Requirements Rel-19
TS 32.422 vk00 Telecom Management: Trace Control & Configuration Rel-20
TS 32.820 v1801 Charging Architecture Study for Evolved 3GPP Rel-8
TS 32.843 vd00 PS Domain Online Charging in Roaming Rel-13
TS 37.340 vj00 Multi-Connectivity Operation Overview Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19