Principle
Carrier Aggregation (CA) allows terminals to aggregate multiple Component Carriers simultaneously, achieving a wider effective bandwidth in both downlink and uplink directions, thereby improving peak data rates. LTE-Advanced uses CA as one of its core capabilities; IoT gateways can gain significant advantages when high throughput is needed (such as video backhaul or firmware upgrades) by selecting Cat.6+ modules that support CA in combination with a matching carrier network.
Frequency Bands and Combinations
CA supports intra-band contiguous, intra-band non-contiguous, and inter-band combinations, with specific combinations defined by carriers and the 3GPP band table. Module datasheets list supported band combinations (e.g., B1+B3); if the deployed network combination is not on the list, aggregation is not possible. Antennas and filters must cover all involved bands, making RF design more complex than single-carrier.
IoT Trade-offs
Low-speed meter-reading applications usually do not require CA; gateways and industrial camera scenarios can be evaluated. Higher Cat levels often come with increased power consumption and cost, which need to match the business model.
Engineering Practice Supplement
Combining "LTE Carrier Aggregation" with the module lifecycle: during the EVT phase, verify reference design and antenna solutions; during the DVT phase, perform conducted/radiated baseline measurements and thermal imaging; during the PVT phase, finalize calibration and test scripts. Before certification, check the target country regulations and carrier registration requirements to avoid missing bands or SAR items. On the production line, retain golden samples for comparison and implement spot-checking rules; after-sales can trace software versions, calibration parameters, and key component batches based on serial numbers. If the customer requires remote operation and maintenance, design strategies for secure upgrades, rollback, and emergency shutdowns simultaneously.
The following are additional tips related to cellular IoT project delivery: it is recommended to keep screen recordings of typical scenarios, screenshots of key indicators, and summaries of masked packet captures during the acceptance phase; in the mass production phase, change records should be kept for software and hardware versions, calibration parameters, and key component batches to facilitate problem attribution, customer audits, and long-term maintenance. When payment or personal information is involved, also check whether log masking and key rotation strategies are executable.
A combination missing from the specification will not aggregate
Carrier aggregation means the terminal uses two or more component carriers at once and the scheduler treats them as one wider pipe. The bandwidth may be contiguous in one band, non-contiguous in one band, or spread across another band. The condition is strict: the combination the operator has enabled in the live network must appear in the module’s supported-combination table, and the antenna, filters, and front-end switches must cover every participating band. A category that supports only a single carrier does not become faster because the base station has turned aggregation on.
Meter reading and short messages do not need this capability. The power, antenna count, and certification combinations it costs are not justified. A video gateway or a bulk upgrade is the case worth evaluating. Judge sustained rate, not a peak screenshot. A secondary carrier exists only while the channel allows it, and coverage at the edge falls back to the primary carrier.
When a secondary carrier drops, the rate falls in a step
A common mistake is to extrapolate an aggregated rate from a single-carrier drive test, or to tune both pieces of spectrum to their best only in the lab. In the field, as soon as the secondary carrier’s radio quality is poor, the scheduler stops using it. The user sees the rate drop a step, not slow down smoothly. The log should distinguish “a secondary carrier was never configured” from “it was configured and then released.” Another mistake is an antenna matched only on the primary band. Reflection on the secondary band is high, protection reduces transmit power after aggregation is set up, and the primary carrier gets worse as well.
A cross-band combination is more sensitive to isolation and matching. Layout of the two antennas is in antenna isolation and MIMO. If the service actually runs on the next generation, also confirm the session is still there when falling back to 5G or from 5G back to a single carrier. Do not put a combination that is not in the specification into the delivery list.
If the primary carrier fails, the secondary does not remain alone
Aggregation assumes a connection on the primary carrier. When the primary cell reselects or the radio link fails, the secondary carrier is released with it. The service breaks and is rebuilt on the new cell. It does not shrink smoothly to half the bandwidth. If the application treats that step as congestion and keeps retransmitting, it fills the send queue during the rebuild window. Recognize radio re-establishment, pause a large file, and resume after the primary carrier is stable again. Averaging the rate hides this interruption as “the network is a bit slow.”
An average rate hides a secondary carrier leaving
When the secondary carrier comes and goes, the hourly average rate still looks fine while the service stalls in bursts. Statistics should record separately the time a secondary carrier is present and the time only the primary remains, and mark the moment the secondary is released. Without that split, optimization keeps raising transmit power, while the real cause is that the combination was never established or the antenna is mismatched on the secondary band.