CPAC

Conditional PSCell Addition or Change

Mobility →
Introduced in Rel-17

CPAC is a 5G mobility enhancement for dual connectivity that allows a UE to prepare candidate PSCells and conditionally execute their addition or change based on radio measurements to improve reliability and reduce interruption.

Category
Mobility
Introduced
Rel-17
Where
Radio Access Network › NG-RAN (5G)
Specifications
7 specs
CPAC Description Purpose Detected Changes Specifications

Description

Conditional PSCell Addition or Change (CPAC) is a sophisticated mobility procedure introduced in 3GPP Release 17 for scenarios involving Dual Connectivity (DC), specifically E-UTRA-NR Dual Connectivity (EN-DC) and NR-NR Dual Connectivity (NR-DC). It extends the principles of Conditional Handover (CHO) to the management of the Primary SCell (PSCell) within a secondary node (SN) in a DC configuration. The core concept is to allow the network to pre-configure the User Equipment (UE) with one or more candidate PSCells along with specific execution conditions, typically based on radio measurement thresholds (e.g., RSRP, RSRQ). The UE then autonomously monitors these conditions for the candidate cells while maintaining its current connection. When a condition for a candidate PSCell is met, the UE executes the PSCell addition or change without needing further signaling from the network at the moment of execution, thereby reducing latency and the risk of failure during the critical transition phase.

Architecturally, CPAC involves coordination between the Master Node (MN) and the Candidate Secondary Node (C-SN). The procedure is initiated by the MN, which requests the preparation of candidate PSCell resources from one or more C-SNs via the Xn interface (or X2 in the case of EN-DC). The C-SN provides the necessary configuration, including the new PSCell's cell identity, bearer configuration, and security parameters, which are encapsulated in a 'Conditional PSCell Addition/Change' command sent to the UE via RRC signaling from the MN. This command includes the execution condition(s) for each candidate. The UE stores this configuration and begins evaluating the conditions. Key RRC messages involved are the RRCReconfiguration message for delivering the CPAC configuration and the subsequent RRCReconfigurationComplete message upon successful execution.

The execution phase is UE-controlled. Upon fulfilling a condition, the UE performs a synchronization and random access procedure to the target PSCell, applies the stored configuration, and releases the resources of the old PSCell if applicable. It then informs the MN of the successful change via an RRCReconfigurationComplete message. The network then updates its context and may initiate data forwarding and path switch procedures. CPAC is particularly valuable in high-mobility or challenging radio environments where the radio conditions for the current PSCell can degrade rapidly. By preparing alternatives in advance, CPAC enhances mobility robustness, minimizes data interruption, and contributes to higher reliability and seamless user experience in advanced 5G networks utilizing carrier aggregation and dual connectivity.

Purpose & Motivation

CPAC was created to address specific mobility robustness challenges inherent in Dual Connectivity and Multi-RAT Dual Connectivity deployments. In traditional 'blind' or measurement-report-triggered PSCell addition/change procedures, the decision and execution are network-controlled and sequential, which can lead to failures if radio conditions deteriorate faster than the network can react. This is especially problematic for the PSCell, which often operates on higher frequencies (e.g., mmWave) with more pronounced signal fluctuations. The primary problem CPAC solves is the reduction of handover failure rates and radio link failures (RLFs) associated with the secondary node, thereby improving overall connection stability and service continuity.

The historical context stems from the successful application of Conditional Handover (CHO) for the primary cell, introduced in earlier releases. Observing CHO's benefits in reducing handover failures for the PCell, 3GPP recognized a similar need for the secondary node's primary cell (PSCell) in DC scenarios. Previous approaches relied on timely measurement reports and network processing, which introduced latency and a single point of failure. If the signaling path was delayed or the source PSCell link failed before completion, the procedure would fail, potentially causing a DC link drop. CPAC mitigates this by decentralizing the execution decision to the UE, which has the most immediate knowledge of its radio environment, allowing for a faster and more reliable transition when predefined conditions are met.

Furthermore, CPAC supports the evolution towards more autonomous and intelligent UE behavior in 5G-Advanced networks. It enables network load balancing and optimization by allowing the network to pre-configure multiple candidate cells, potentially in different nodes or frequency layers. This prepares the network for ultra-reliable low-latency communication (URLLC) use cases and high-mobility scenarios like vehicular communications, where predictable and robust mobility is non-negotiable. By solving the PSCell mobility robustness gap, CPAC is a key enabler for reliable multi-connectivity, which is fundamental for achieving the high data rates and consistent performance promised by 5G and beyond.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 9 changes

In Release 17, the CPAC function was enhanced with Stage-2 aspects and specific procedures including Xn-U Address Information delivery and PDCP PDU early transmission. The release also introduced corrections to clarify optional late data forwarding, conditional MCG configuration, and the ASN.1 definitions. Furthermore, it specified that a single, unique SN Counter value could be configured for a CPAC procedure independently of any pre-configured lists.

  • CPAC BL CR to TS 38.423 TS 38.423CR0634
  • Stage-2 aspects for CPAC TS 37.340CR0331
  • Xn-U Address Information delivery in CPAC TS 37.340CR0362
  • PDCP PDU early transmission in CPAC TS 37.340CR0363
  • Correction of CPAC to clarify optional late data forwarding TS 37.340CR0376
  • Correction on CPAC to 38.423 TS 38.423CR0776

+ 3 more changes

Rel-18 28 changes

In Release 18, the primary new feature for Conditional PSCell Addition or Change (CPAC) was the formal introduction and specification of subsequent CPAC (S-CPAC). This enhancement allows the Master Node (MN) to provide the UE with one or several candidate SCG configurations for multiple candidate Secondary Nodes (SNs), enabling the UE to select and execute one conditional reconfiguration based on measurements. The release also included extensive stage-2 description updates, corrections, and specific support for intra-SN S-CPAC scenarios with MN involvement.

  • on subsequent CPAC TS 37.483CR0097
  • Introduction of Subsequent CPAC TS 38.423CR1051
  • On Subsequent CPAC TS 38.473CR1227
  • Correction to 37.340 for CPAC of SON feature TS 37.340CR0385
  • Support intra-SN subsequent CPAC in MN format TS 37.340CR0387
  • Completion of the s tage-2 description of S-CPAC TS 37.340CR0389

+ 22 more changes

Rel-19 2 changes

In Release 19, the enhancements to Conditional PSCell Addition or Change (CPAC) included specific corrections for Mobility Robustness Optimization (MRO) related to both Subsequent CPAC (S-CPAC) and CHO procedures. The release also introduced a clarification on the configuration of a single, unique SN Counter value during a CPAC procedure, ensuring it does not conflict with any pre-configured lists for the current K gNB. These corrections refined the management of candidate SCG configurations and measurement-based execution for the UE.

  • Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340 TS 37.340CR0429
  • Correction to CPAC MRO TS 38.331CR5539

Explore further

Broader topics and technologies where CPAC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 37.340 vj00 Multi-Connectivity Operation Overview Rel-19
TS 37.483 vj10 E1 Application Protocol (E1AP) Rel-19
TS 38.306 vj00 NR UE Radio Access Capability Parameters Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.