Successful PSCell Addition/Change Report

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.

Key Features

• Triggered upon successful application of an SCG reconfiguration involving PSCell addition or change.
• Contains the `measResultSCG` field with measurement results (e.g., RSRP/RSRQ) for the new PSCell.
• Transported within the `RRCReconfigurationComplete` message from UE to network.
• Provides explicit confirmation to network RRM for reliable state synchronization.
• Supports both LTE-NR Dual Connectivity (EN-DC) and NR-NR Dual Connectivity (NR-DC) architectures.
• Enables faster recovery from failed reconfiguration attempts by providing clear success/failure demarcation.

Evolution Across Releases

Defining Specifications