Definition
Carrier Aggregation (CA) bundles multiple LTE carriers (CC, Component Carrier) or 5G NR carriers together, allowing terminals to simultaneously use multiple carriers to transmit data, thereby increasing peak rates and system capacity. LTE-A supports aggregation of up to 5 carriers (100MHz), while 5G NR supports more flexible bandwidth combinations. CA is a key technology for 4G+ and 5G to meet the large bandwidth requirements of eMBB.
Types and Deployment
- Intra-band contiguous: adjacent carriers within the same frequency band, simple to implement, e.g., B3 20MHz+20MHz
- Intra-band non-contiguous: non-adjacent carriers within the same frequency band, requires terminal to support multiple RFs, e.g., B1 non-contiguous
- Inter-band: aggregation of carriers in different frequency bands, e.g., B3+B8, B1+B3, requires terminal multi-band capability
Primary and Secondary Carriers and Scheduling
Primary carrier (PCC/PCell) carries critical signaling and part of the data; secondary carrier (SCC/SCell) increases bandwidth. Terminals need to support the corresponding CA combinations (e.g., Cat.6 2CA, Cat.12 3CA). The scheduler can distribute data across multiple carriers to achieve load balancing and rate enhancement.
Typical Use Cases
4G+ and 5G high-speed scenarios, such as video surveillance, OTA upgrades, and large file transfers. IoT devices can benefit from CA networks when high data throughput is needed (such as video uplink and firmware upgrades). SimtoLink can provide customers with high bandwidth requirements with module selection supporting CA and data plans.
Carrier aggregation allows 4G/5G networks to support higher bandwidth, enabling IoT devices to have a better experience in scenarios requiring large data transmission (such as video surveillance and OTA upgrades). SimtoLink's IoT SIM cards support carrier aggregation networks and can provide customized data plans and connection management solutions for customers with high bandwidth demands.
The peak does not appear the moment a secondary carrier is activated
The primary carrier handles camping and critical signaling. A secondary carrier is bandwidth added on demand. After attach, the device usually sends first on the primary carrier only. The base station activates a secondary carrier after it sees a sustained buffer. Activation can be measurement, random access, or direct activation, and it costs from several milliseconds to a longer configuration time on the air. A short IoT message is often finished before the secondary carrier wakes, so the captured rate is still single-carrier. To judge whether aggregation is in effect, see whether the secondary carrier stays activated while the service continues, not whether a neighboring carrier is present in the cell broadcast.
A secondary carrier can be downlink only, or both downlink and uplink. A downlink-only combination helps video viewing and barely helps a camera uploading. A downlink speed test that shows the rate doubling does not prove the uplink is aggregated. Firmware or video upload should look on its own at which carriers the uplink grants land on.
The band combination in the capability signaling must match the live network
The device lists the band combinations it supports in the capability report. The base station can activate only a combination on that list. If the live network is inter-band aggregation of two specific bands, and the module only declared a contiguous intra-band combination, aggregation does not happen. There is no clear service-layer error code. The rate simply stays at the primary-carrier bandwidth. Changing the antenna or the data plan does not rewrite the capability bits. Line up three columns: module capability, the combination configured on the base station, and the band currently camped on.
Radio capability is also limited by antenna count and duplex mode. If there are not enough receive paths open at one time, hardware stops at two carriers even when the protocol allows three. Thermal throttling or a weak supply can make the module shut a secondary-carrier path on its own. The rate falls back under high load and is easy to misread as a base-station rate limit. Read the module radio state and the base-station secondary-carrier count together.
A large file still will not go up when uplink stays on the primary carrier
Many IoT modules support fewer uplink carrier-aggregation combinations than downlink. If the primary carrier sits on a band with good coverage and narrow bandwidth, the uplink ceiling is that narrow bandwidth. A wider downlink secondary carrier still cannot carry the backhaul. When choosing the camping band, the primary carrier itself needs enough uplink bandwidth, not only a downlink peak. After a handover to another layer, the old secondary-carrier combination can all go invalid and must be activated again. At the handover instant the rate drops to a single carrier.
What SimtoLink can do is supply a communication module that supports the relevant combination, and a data tier that matches the service. If the card’s subscribed rate is below single-carrier capability, aggregation will not lift throughput above the subscribed cap. When the platform shows uplink stuck far below the laboratory peak, separate three cases: the secondary carrier was not activated, the uplink combination is not supported, or the subscription or the aggregate bit rate was hit first. Those three live in module capability, base-station configuration, and plan policy. One restart does not prove all of them at once.
Downlink gives up a short gap while a secondary carrier is measured
Before a secondary carrier is activated, the device often has to measure other frequencies. Measurement needs gaps, and downlink on the primary carrier pauses inside a gap. If gaps are packed tightly, primary-carrier rate falls before the secondary carrier has contributed any bandwidth, and total throughput can be temporarily worse. For a very short service, measurement cost exceeds aggregation gain, and “turning aggregation on” looks slower. Compare the share of time spent in measurement gaps with how long the secondary carrier stays active afterward. Aggregation pays when the transfer lasts much longer than the gaps. A report of a few dozen bytes is not worth interrupting the primary carrier to measure.
When secondary-carrier quality gets worse, the base station can deactivate it and the device returns to a single carrier. Deactivation is not a fault. It is the scheduler reacting to the channel. If the log records every deactivation as a disconnect, alarms flood at the cell edge. A SimtoLink module should report secondary-carrier state as its own event. The card’s subscribed cap is still the ceiling on total rate. If the state stays deactivated for a long time and the primary-carrier level is good, check whether the capability combination matches the current frequency, rather than concluding that the base station has no carrier aggregation.