Physical Uplink Control Channel Secondary Cell

Description

PUCCH SCell (Physical Uplink Control Channel Secondary Cell) is a concept introduced in 3GPP Release 13 as part of the enhanced carrier aggregation (CA) framework for LTE and later carried into NR specifications. In a conventional carrier aggregation deployment, all uplink control information (UCI) — including HARQ-ACK feedback, channel state information (CSI) reports, and scheduling requests — must be transmitted on the Primary Cell (PCell) via the Physical Uplink Control Channel (PUCCH). This creates a bottleneck: the PCell's uplink becomes congested while SCells' uplink resources may be underutilized, and UEs at cell edge may suffer from poor PUCCH coverage on the PCell.

The PUCCH SCell concept resolves this by allowing the network to configure one SCell (per PUCCH group) with PUCCH resources. According to 3GPP TS 36.331, a PUCCH SCell is 'An SCell configured with PUCCH by PUCCH-Config.' When a UE is configured with a PUCCH SCell, the network organizes serving cells into PUCCH groups: the PCell forms one group, and the PUCCH SCell forms another. Each group has its own PUCCH resource on its respective cell. Uplink control information for SCells belonging to a group is transmitted on that group's PUCCH cell.

From a protocol perspective, the configuration is managed via RRC signaling in TS 36.331. The network includes PUCCH-Config within the SCellToAddMod-r13 IE for the designated SCell. The MAC layer (TS 36.321) manages scheduling and HARQ processes across the PUCCH groups. The PUCCH SCell can also be changed or released via RRC reconfiguration, giving the network flexibility to adapt to changing traffic and radio conditions. Notably, cross-carrier scheduling may be applied within PUCCH groups.

The primary benefits include: improved uplink coverage for control signaling when the PUCCH SCell operates on a lower frequency with better propagation characteristics; load balancing of PUCCH resources across carriers; and enhanced capacity for UEs configured with many SCells. In NR (TS 38.331), the concept is reflected in the PUCCH-Config within ServingCellConfig for SCells, though the architecture differs due to NR's more flexible PUCCH configuration and beamforming framework.

For the network operator, PUCCH SCells enable more efficient use of spectrum in dense deployments and support for advanced CA configurations (e.g., 32 component carriers), where concentrating all UCI on a single PCell uplink would be impractical. They also facilitate dual-connectivity-like enhancements within a single RAT, improving reliability and user experience.

Purpose & Motivation

PUCCH SCell was introduced to overcome a fundamental limitation of carrier aggregation: the requirement that all uplink control signaling be carried on the PCell. As CA evolved toward higher numbers of component carriers (up to 32 in later releases) and more diverse spectrum bands, the PCell uplink became a severe bottleneck. Control channel capacity, coverage, and interference on a single uplink carrier could not scale with the number of aggregated downlink carriers, degrading both throughput and reliability.

By allowing PUCCH to be configured on an SCell, the network can distribute control signaling load across multiple uplink carriers. This is especially valuable in scenarios where the PCell operates on a high-frequency band with limited coverage, while a lower-frequency SCell could provide more robust uplink control transmission. It also supports better load balancing in heterogeneous networks and small cell deployments.

The concept directly addresses the limitations of the original Rel-10/Rel-11 CA framework, where the PCell was a single point of failure for UCI. With PUCCH SCells, the network gains a tool to improve uplink coverage, increase control channel capacity, and optimize resource utilization across carriers — all without requiring a full dual connectivity architecture.