Carrier Aggregation LTE and 5G: practical field guide for engineers

Carrier Aggregation (CA) is the primary mechanism for increasing throughput in LTE and 5G NR. It allows a terminal to simultaneously use multiple carriers (Component Carriers) to multiply the available bandwidth. In theory, the concept is simple. In practice, CA introduces specific diagnostic challenges that every field engineer must master. This guide covers fundamental principles, field verification methods, and troubleshooting of common issues.

Carrier Aggregation fundamentals

PCell, SCell, and Component Carriers

In a system with Carrier Aggregation, the terminal uses multiple carriers simultaneously. Each carrier is called a Component Carrier (CC). Roles are defined as follows:

PCell (Primary Cell): the primary cell, always active. It manages:

• The control plane (RRC messages)
• The main PUCCH (Physical Uplink Control Channel)
• Mobility (handovers)
• Initial connection establishment

SCell (Secondary Cell): secondary cells, dynamically added to increase throughput. Characteristics:

• Activated and deactivated by the network as needed
• Carry only user plane (data)
• Can be on the same band (intra-band CA) or different bands (inter-band CA)
• The terminal can have 1 to 7 SCells (up to 8 CCs total in LTE, 16 in NR)

PSCell (Primary Secondary Cell): in EN-DC (5G NSA) configuration, the primary cell of the Secondary Node (gNB NR). It manages the NR control plane.

CA Architecture (example: 3CC LTE + 1CC NR in EN-DC):

LTE (Master Node)           NR (Secondary Node)
+----------------+          +----------------+
| PCell (B3)     |          | PSCell (n78)   |
| + SCell1 (B7)  |          |                |
| + SCell2 (B1)  |          |                |
+----------------+          +----------------+
        |                           |
        +-----------+---------------+
                    |
               +----+----+
               |   UE    |
               +---------+
    4 simultaneous Component Carriers
    = aggregated bandwidth

Types of Carrier Aggregation

Intra-band contiguous CA: CCs are on the same frequency band and adjacent in spectrum. Example: 2 x 20 MHz on B3 (1805-1845 MHz), noted 3C.

Intra-band non-contiguous CA: CCs are on the same band but separated by a spectral gap. Less common, used when the operator has fragmented spectrum on the same band.

Inter-band CA: CCs are on different bands. Example: B3 (1800 MHz) + B7 (2600 MHz), noted 3A-7A. This is the most common case.

NR-DC (NR Dual Connectivity): in 5G SA, aggregation of NR CCs on different bands without LTE anchor. Example: n78 + n1.

EN-DC (E-UTRA NR Dual Connectivity): combination of LTE CA + NR CA in 5G NSA. Example: B3+B7 (LTE) + n78 (NR), noted 3A-7A_n78A.

Bandwidth classes

3GPP nomenclature uses alphabetical classes to define the aggregated bandwidth per band:

Class	Max aggregated bandwidth (LTE)	Max CCs	Example
A	20 MHz	1	B7A = 1 CC of max 20 MHz
B	25 MHz	2 (intra-band contiguous)	Limited usage
C	40 MHz	2 (intra-band contiguous)	B3C = 2 x 20 MHz contiguous
D	60 MHz	3	Rare in LTE

For NR FR1, classes are extended:

Class	Max aggregated bandwidth (NR FR1)	Typical example
A	100 MHz	n78A = 1 CC of 100 MHz
C	200 MHz	n78C = 2 x 100 MHz
D	400 MHz	Primarily FR2 usage

Common CA combos in deployment

LTE Carrier Aggregation

The most deployed CA combinations in Europe and Africa:

Combo	Bands	Total BW	Theoretical DL throughput (2x2 MIMO, 256QAM)	Coverage
3A	B3 only (1800 MHz)	20 MHz	~150 Mbps	Baseline
3A-7A	B3 + B7 (2600 MHz)	40 MHz	~300 Mbps	Urban
1A-3A	B1 + B3	40 MHz	~300 Mbps	Urban/Suburban
3A-20A	B3 + B20 (800 MHz)	30 MHz	~225 Mbps	Rural/Indoor
1A-3A-7A	B1 + B3 + B7	60 MHz	~450 Mbps	Dense urban
1A-3A-7A-20A	B1+B3+B7+B20	70 MHz	~525 Mbps	4CA max
3C	B3 intra-band 2CC	40 MHz	~300 Mbps	Operator with 2x20 MHz B3

EN-DC (5G NSA)

EN-DC combinations deployed in 2025-2026:

Combo	LTE anchor + NR	Total BW	Theoretical DL throughput	Note
3A_n78A	B3 + n78 (100 MHz)	120 MHz	~1.5 Gbps	Basic NSA config
1A-3A_n78A	B1+B3 + n78	140 MHz	~1.7 Gbps	Common
3A-7A_n78A	B3+B7 + n78	140 MHz	~1.7 Gbps	Urban
3A_n78C	B3 + n78 (200 MHz)	220 MHz	~2.5 Gbps	2CC NR, 4x4 MIMO
1A-3A-7A_n78A	3CA LTE + n78	160 MHz	~2 Gbps	Premium config

Theoretical throughput formula

The maximum theoretical throughput for a CA configuration is calculated as follows:

DL_throughput_max (Mbps) = Sum(i=1 to N_CC) [ BW_i x Eff_i x MIMO_i x (1 - OH_i) x SF ]

Where:

• N_CC = number of active Component Carriers
• BW_i = bandwidth of CC i in MHz
• Eff_i = maximum spectral efficiency (bits/s/Hz)
  • 64QAM: ~5.55 bits/s/Hz
  • 256QAM: ~7.41 bits/s/Hz
  • 1024QAM (NR): ~9.02 bits/s/Hz
• MIMO_i = number of spatial MIMO layers (2 or 4)
• OH_i = protocol overhead (~14% LTE, ~8% NR)
• SF = scaling factor (0.75 or 1.0 depending on combo)

Example: 3A-7A with 256QAM and 2x2 MIMO

CC B3: 20 MHz x 7.41 x 2 x 0.86 = 255 Mbps
CC B7: 20 MHz x 7.41 x 2 x 0.86 = 255 Mbps
Total = 510 Mbps theoretical

Example: 3A-7A_n78A with 256QAM, 2x2 MIMO LTE, 4x4 MIMO NR

CC B3:  20 MHz x 7.41 x 2 x 0.86  = 255 Mbps
CC B7:  20 MHz x 7.41 x 2 x 0.86  = 255 Mbps
CC n78: 100 MHz x 7.41 x 4 x 0.92 = 2729 Mbps
Total = 3239 Mbps (~3.2 Gbps) theoretical

Under real field conditions, expect 30 to 60% of theoretical throughput depending on radio conditions (SINR, cell load, distance).

Field verification of CA

RRC messages related to CA

Carrier Aggregation is entirely controlled by RRC messages. Understanding these messages is essential for field diagnostics.

SCell addition: the network sends an RRCConnectionReconfiguration containing an IE sCellToAddModList. This message defines:

• The frequency and PCI of the SCell
• The physical configuration (PDSCH, CQI, antenna ports)
• The initial state (activated or deactivated)

SCell activation: a MAC CE (Control Element) Activation/Deactivation activates the SCell. The terminal begins receiving data on this carrier.

SCell deactivation: a MAC CE deactivates the SCell. This can be triggered by:

• Inactivity timer (sCellDeactivationTimer, typically 2-8 seconds without data)
• Scheduler decision (resource release)
• Degraded radio conditions

SCell removal: an RRCConnectionReconfiguration with sCellToReleaseList removes the SCell from the configuration.

Typical CA activation sequence

Temporal sequence:

T0: UE connected on PCell (B3)
T1: RRCConnectionReconfiguration [sCellToAddModList: B7, PCI=201]
    -> SCell B7 added but not activated
T2: MAC CE Activation [SCell index 1: ACTIVATED]
    -> SCell B7 activated, scheduling possible on 2 CCs
T3: Data transmitted on PCell (B3) + SCell (B7)
    -> Throughput doubled if radio conditions OK
T4: No data for 4 seconds
T5: MAC CE Deactivation [SCell index 1: DEACTIVATED]
    -> SCell B7 deactivated (timer expired)
T6: New data arrives
T7: MAC CE Activation [SCell index 1: ACTIVATED]
    -> SCell B7 reactivated

How to verify CA in real time

With HiCellTek, CA verification is performed in real time:

1. CA status bar: permanent display of the number of active CCs and their bands
2. Per-CC detail: for each Component Carrier, view: band, EARFCN/NR-ARFCN, PCI, RSRP, SINR, bandwidth, MCS, BLER
3. RRC messages: RRCConnectionReconfiguration messages are decoded and displayed with relevant IEs (sCellToAddModList, sCellToReleaseList)
4. Timeline: chronological visualization of SCell activations/deactivations

For an in-depth understanding of RRC message decoding, see our Layer 3 LTE/5G decoding guide.

Troubleshooting CA problems

Problem 1: SCell never added

Symptom: the terminal stays on a single carrier even though the area is configured for CA.

Diagnostics:

1. Check UE Capabilities: does the terminal support the CA combo for this area?
2. Check eNB/gNB configuration: is CA enabled on the site?
3. Check neighbor measurements: does the terminal report the candidate SCell in its Measurement Reports?
4. Check the addition threshold: does the candidate SCell RSRP exceed the configured threshold (s-MeasConfig)?

Common cause: CA combo incompatibility between the terminal and network configuration. The terminal supports B3+B7 but not B3+B1, while the site is configured for B3+B1.

For analyzing UE Capabilities and supported CA combos, see our UE Capabilities MRDC and CA Combos guide.

Problem 2: SCell added but never activated

Symptom: the RRCConnectionReconfiguration message contains the SCell, but the activation MAC CE never arrives.

Diagnostics:

1. Check SCell RSRP: if RSRP is too weak, the scheduler may decide not to activate
2. Check SCell load: if the secondary cell is saturated, activation may be delayed
3. Check timers: some configurations activate the SCell only when significant downlink traffic is present

Common cause: insufficient radio conditions on the SCell. SCell RSRP is below the activation threshold (typically -110 dBm).

Problem 3: SCell activated then deactivated rapidly (flapping)

Symptom: the SCell alternates between activated and deactivated every 2-5 seconds.

Diagnostics:

1. Check the sCellDeactivationTimer: if the timer is too short (e.g., 2 seconds) and traffic is intermittent, the SCell deactivates between bursts
2. Check SINR stability on the SCell: fluctuating SINR can trigger scheduler deactivations
3. Analyze the traffic pattern: flapping may be normal if traffic is bursty (web browsing vs continuous streaming)

Remediation:

• Increase the sCellDeactivationTimer (8 seconds recommended)
• Verify isolation between SCell and interfering cells
• Optimize SCell tilt/power to stabilize SINR

Problem 4: CA active but disappointing throughput

Symptom: 2CA or 3CA active, but throughput does not increase proportionally.

Diagnostics:

1. Check SINR per CC: if an SCell has an SINR of 2 dB, it contributes little to throughput
2. Check MCS per CC: a low MCS (QPSK/16QAM instead of 256QAM) indicates degraded radio conditions
3. Check BLER per CC: a BLER > 10% on an SCell means massive retransmissions that cancel the CA gain
4. Check transport load (backhaul): if the backhaul is the bottleneck, adding radio CCs changes nothing

Real throughput estimation formula:

Actual_throughput ~ Sum(CC) [ BW_CC x Spectral_eff(SINR_CC) x MIMO_CC x (1 - BLER_CC) x (1 - OH) ]

A CC with SINR = 2 dB uses a spectral efficiency of ~1 bit/s/Hz instead of 7.4 bits/s/Hz with 256QAM. Its throughput contribution is marginal.

Problem 5: EN-DC not activated (no 5G)

Symptom: the terminal stays on LTE only in an area covered by 5G NR.

EN-DC specific diagnostics:

1. UE-MRDC-Capability: does the terminal support EN-DC? (see UE Capabilities)
2. MeasObjectNR: does the network send NR measurements in the MeasurementConfiguration?
3. B1 Event (NR): does the terminal report a B1 event (serving LTE + neighbor NR meets threshold)?
4. SCG Configuration: does the RRCConnectionReconfiguration contain an nr-Config with SCG configuration?
5. SCG Failure: are there SCGFailureInformation messages indicating an NR configuration failure?

Common causes:

• NR band not supported in the terminal’s MRDC combos
• B1 threshold too high (NR not strong enough to trigger addition)
• NR timing advance issue (terminal cannot synchronize with the gNB)

Field optimization of CA

Key parameters to verify

Parameter	Role	Recommended value
sCellDeactivationTimer	Duration before deactivating inactive SCell	8 seconds (rf40)
s-MeasConfig	RSRP threshold to trigger SCell measurements	-85 dBm
a1-Threshold (event A1)	PCell RSRP threshold to stop inter-freq measurements	-75 dBm
a2-Threshold (event A2)	PCell RSRP threshold to start inter-freq measurements	-80 dBm
a4-Threshold (event A4)	Candidate SCell RSRP threshold	-95 dBm
b1-ThresholdNR (EN-DC)	Threshold to add the NR leg	-100 dBm (NR RSRP)

Cluster optimization strategy

To maximize the CA benefit across a site cluster:

1. Map coverage per band: drive test per band to identify where each CC is available with sufficient SINR
2. Align coverage zones: SCells must cover the same areas as the PCell to maximize aggregation duration
3. Optimize SCell SINR: an SCell with SINR < 5 dB has marginal throughput contribution
4. Validate UE Capabilities: ensure the majority of the terminal fleet supports the configured combos
5. Monitor SCell activation rate: percentage of time SCell is active vs configured

CA performance indicators

Indicator	Formula	Target
SCell configuration rate	Sessions with SCell configured / Total sessions	> 90% in CA zone
SCell activation rate	Time SCell active / Time SCell configured	> 70%
CA throughput gain	Throughput with CA / Throughput without CA	> 1.5x for 2CA
SCell failure rate	SCell addition failures / Addition attempts	< 5%

Business impact of CA

Carrier Aggregation is not just a technical parameter: it is a network performance lever with direct impact on user experience and operator competitiveness.

Impact on user throughput:

• 2CA: average gain of 50-80% (not 100% because radio conditions differ between CCs)
• 3CA: average gain of 100-150%
• EN-DC (LTE+NR): average gain of 200-500%

Impact on cell capacity:

• Aggregating underused bands (e.g., B7 in rural areas) distributes traffic and offloads the PCell
• The capacity gain is sometimes more significant than the per-user throughput gain

Impact on QoE:

• Bandwidth-hungry services (4K streaming, HD video conferencing, cloud gaming) directly benefit from CA
• Application latency decreases thanks to simultaneous scheduling on multiple CCs

For a comprehensive view of RAN optimization KPIs including CA, see our 10 essential RAN KPIs guide.

Conclusion

Carrier Aggregation is the cornerstone of throughput performance in LTE and 5G NR. Mastering its operation, knowing how to verify its activation in real time, and diagnosing SCell problems are essential skills for any network optimization engineer.

HiCellTek provides complete visibility into CA directly from the field: real-time Component Carrier status, decoding of RRC messages for SCell addition/activation/removal, UE Capabilities with supported CA combos, and structured data export for optimization reports. Discover the full 5G NR and LTE-A capabilities on the 5G network testing tool page.

---

Want to diagnose and optimize Carrier Aggregation on your network? Contact our team: sales@hicelltek.com or visit hicelltek.com.