CPC

Continuous Packet Connectivity

Radio Access Network →
Introduced in Rel-7 Also in: Services, Core Network

CPC is a set of UMTS/HSPA radio resource management techniques designed to significantly increase the number of simultaneous packet data users a cell can support by enhancing uplink efficiency, reducing interference, and minimizing battery consumption.

Category
Radio Access Network
Introduced
Rel-7
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
20 specs
CPC Description Purpose Related Classification Detected Changes Specifications

Description

Continuous Packet Connectivity (CPC) is a comprehensive feature suite for UMTS/HSPA networks, primarily defined in 3GPP Release 7, that optimizes the radio interface for a large population of always-on, packet-switched users. Its core objective is to maximize the number of users that can be kept in a connected state—specifically the CELL_DCH state—without causing excessive uplink interference or draining device batteries. Prior to CPC, maintaining a user in CELL_DCH required continuous transmission of pilot and control signals, which consumed significant uplink capacity and power. CPC introduces mechanisms that allow the network to keep a user in this high-performance state while drastically reducing the overhead when the user is not actively transmitting data.

Architecturally, CPC operates within the Node B (base station) and User Equipment (UE), governed by the Radio Network Controller (RNC) through specific Radio Resource Control (RRC) configurations. It is not a single protocol but a collection of complementary techniques. A key component is Discontinuous Transmission (DTX) in the uplink, which allows the UE to stop transmitting the Dedicated Physical Control Channel (DPCCH) during periods of inactivity. The DPCCH carries vital pilot and power control bits. By transmitting it only in predefined, short bursts, uplink interference is reduced and UE battery life is extended. Similarly, Discontinuous Reception (DRX) in the downlink allows the UE to power down its receiver circuitry according to a scheduled pattern, further conserving energy.

Another fundamental mechanism is the Enhanced Dedicated Channel (E-DCH) in the uplink, which is part of HSPA. CPC optimizes its operation. The High-Speed Dedicated Physical Control Channel (HS-DPCCH), which carries downlink channel quality feedback (CQI) and HARQ acknowledgments, can also be configured with reduced activity. Furthermore, CPC introduces the concept of a 'CPC active set' for softer handover scenarios, optimizing how multiple Node Bs manage a single UE's connection. The RNC configures all these parameters—DTX/DRX cycle lengths, activation thresholds, and channel configurations—based on the user's service profile and network load. This allows the network to trade off slightly increased packet call setup latency for vastly improved capacity and battery life, making it ideal for bursty, interactive applications like web browsing and instant messaging.

Purpose & Motivation

CPC was developed to address critical capacity and battery life limitations in early UMTS/HSPA networks as mobile data usage began to surge. The traditional approach of keeping a data user in the CELL_DCH state ensured low latency but was highly inefficient. The UE continuously transmitted the DPCCH pilot, creating constant uplink interference that limited the number of simultaneous users a cell could support. This 'always-on' signaling also rapidly drained device batteries, making always-connected services impractical for users. Network operators faced a dilemma: either keep users in lower states (like CELL_FACH or CELL_PCH) with higher latency and poorer user experience, or accept severely limited network capacity.

The motivation for CPC was to break this trade-off. It was driven by the need to support a massive increase in always-connected smartphone applications and services anticipated in the late 2000s. By minimizing control channel overhead during idle periods within an active session, CPC directly tackles the root cause of uplink interference. This allows the network to maintain many more users in the high-performance CELL_DCH state, ready to transmit data with minimal delay, without collapsing system capacity. From a user perspective, it enables the 'always-on' internet experience—where email and messaging apps remain connected—without catastrophically impacting battery life. CPC thus served as a vital evolutionary step for HSPA, enhancing its competitiveness as a mobile broadband technology before the widespread deployment of LTE.

Classification

Part ofHSPA

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 9 changes

In Release 16, the CPC (Continuous Packet Connectivity) function saw corrections and clarifications to its configuration, signaling flow, and procedures such as the CPC Complete Transfer. Enhancements included extending Conditional Handover (CHO) usage to support intra-SN/inter-UP CPC cases and clarifying the handling of CPC during fast MCG recovery. The release also specified the non-support of combining CHO/CPC with LTE/5GC and addressed CPC operations with and without SRB3 involvement.

  • Correction on CPC Complete Transfer TS 36.423CR1545
  • Minor Correction for CPC Configuration Related Procedure TS 37.340CR0218
  • Correction of signalling flow for CPC TS 37.340CR0223
  • Corrections to CPC with and without SRB3 involved TS 37.340CR0220
  • Non-support of CHO/CPC with LTE/5GC TS 37.340CR0251
  • Handling of CPC in fast MCG recovery TS 38.331CR1755

+ 3 more changes

Rel-17 15 changes

In Release 17, the enhancements to Continuous Packet Connectivity (CPC) focused on refining its coordination with Conditional Handover (CHO) and improving data forwarding procedures. Key additions included a specific indicator for CHO-CPC coordination and the enablement of direct early data forwarding in SN-initiated inter-SN CPC scenarios. The release also provided clarifications and corrections for procedures over the Xn interface and for interactions like CPC Cancel with SN Release.

  • Alignment of the criticality of CPC Cancel with XnAP ASN.1 TS 36.423CR1681
  • Additional indicator for CHO-CPC coordination TS 36.423CR1722
  • Direct early data forwarding in SN initiated inter-SN CPC TS 36.423CR1723
  • Completion of the work on CHO-CPC coordination TS 36.423CR1731
  • Correction on coordination of CHO and CPC over X2 TS 36.423CR1736
  • Clarification on direct data forwarding for MN initiated CPC to TS37340 TS 37.340CR0346

+ 9 more changes

Rel-18 2 changes

In Release 18, the updates for Continuous Packet Connectivity (CPC) included a correction to the CPC Cancel and SN Release procedure. Furthermore, the standard's abbreviation list was formally updated to include both CPA and the specific CPC R18 designation.

  • Correction of CPC Cancel and SN Release TS 37.340CR0418
  • Update the abbreviation list to include CPA and CPC R18 TS 33.501CR1827

Explore further

Broader topics and technologies where CPC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.404 v1700 Communication Diversion Services (CDIV) Rel-7
TS 24.504 v8m0 Communication Diversion Services Stage 3 Rel-8
TS 25.824 v800 HSPA Evolution for 1.28Mcps TDD Study Rel-8
TR 25.903 vj00 Continuous Connectivity for Packet Data Users Rel-19
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19
TS 37.340 vj00 Multi-Connectivity Operation Overview Rel-19
TS 37.483 vj10 E1 Application Protocol (E1AP) Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
TS 38.463 vj00 E1 Application Protocol (E1AP) 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.