NTC

Non-contiguous Test Configuration

Other →
Introduced in Rel-10

NTC is a standardized test configuration for evaluating radio performance under non-contiguous spectrum operation, defining carrier aggregation scenarios with gaps between component carriers to ensure consistent testing.

Category
Other
Introduced
Rel-10
Where
Radio Access Network › NG-RAN (5G)
Specifications
4 specs
NTC Description Purpose Detected Changes Specifications

Description

The Non-contiguous Test Configuration (NTC) is a crucial framework defined within 3GPP specifications for conformance and performance testing of User Equipment (UE) and network infrastructure. It specifically addresses the complexities introduced by Carrier Aggregation (CA) when the aggregated component carriers (CCs) are not adjacent in the frequency domain, meaning there are spectral gaps between them. This non-contiguous operation is common in real-world deployments due to fragmented spectrum allocations held by operators. The NTC provides a standardized set of parameters and scenarios that test equipment manufacturers and certification bodies must use to verify that a device or base station can correctly handle the radio frequency (RF) challenges, such as managing separate local oscillators, power amplifiers, and filters for disparate frequency blocks, and maintaining synchronization and data aggregation across them.

Architecturally, an NTC scenario is defined by specifying the exact frequency bands for the Primary Cell (PCell) and one or more Secondary Cells (SCells), along with the gap size between them. Key components of the test include the RF requirements for each CC, such as output power, unwanted emission limits, and receiver sensitivity, which must be met simultaneously. The configuration also dictates the bandwidth of each CC (e.g., 10 MHz, 20 MHz) and the specific CA band combination being tested (e.g., Band 1 + Band 3). The test procedures, detailed in specs like 38.521 (UE conformance) and 38.113 (base station), measure performance metrics like throughput, error vector magnitude (EVM), and adjacent channel leakage ratio (ACLR) under these non-contiguous conditions.

Its role in the network ecosystem is foundational for ensuring interoperability and performance. By mandating a common testing baseline, NTC guarantees that UEs from different manufacturers will perform reliably on any network employing non-contiguous CA, a key technique for achieving high data rates. It validates the UE's ability to perform scheduling, hybrid automatic repeat request (HARQ), and channel state information (CSI) reporting across disjoint frequency resources. Without such standardized test configurations, performance under non-contiguous operation could be inconsistent, leading to potential service degradation, dropped connections, or an inability to fully utilize the operator's available spectrum assets, ultimately hindering the user experience and network efficiency.

Purpose & Motivation

NTC was created to solve the critical problem of ensuring reliable and high-performance operation in Carrier Aggregation scenarios where an operator's available spectrum is fragmented. Historically, early LTE deployments often used contiguous spectrum blocks, which simplified RF design and testing. However, as spectrum became a scarce resource, operators frequently acquired disjoint frequency blocks across different bands (e.g., through auctions or refarming). While CA technology theoretically enabled aggregation of these blocks, the practical RF implementation—handling separate power amplifiers, managing inter-modulation distortion, and meeting stringent emission masks for non-adjacent channels—introduced new complexities that existing contiguous CA tests did not cover.

The primary motivation was to establish a unified, rigorous testing methodology that reflects real-world deployment challenges. Prior to NTC standardization, vendors might test non-contiguous CA using proprietary or inconsistent methods, making it difficult to compare device performance or guarantee network-wide interoperability. This lack of standardization risked suboptimal user experiences, such as lower-than-expected data rates or increased call drops when a UE aggregated non-contiguous carriers. By introducing NTC in Release 10 alongside enhanced CA features, 3GPP provided a clear benchmark, enabling the industry to confidently deploy advanced CA features, maximize spectral efficiency, and deliver on the promised gigabits-per-second data rates of 4G and 5G, regardless of spectrum fragmentation.

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-10, normative work from Rel-16.

Rel-16 1 change

In Release 16, the specification introduced new test configurations denoted by "CNC" and "C/NC" for Base Stations declared to be capable of both contiguous and non-contiguous operation, with the choice depending on whether the manufacturer's declared parameters for these two modes are identical or not. This provides a structured framework for EMC testing of non-contiguous capabilities alongside the existing configurations for NB-IoT (NI, NG) and multi-band operation. The changes ensure conformance testing accurately reflects the BS's declared operational capabilities.

  • Draft CR to TS 38.175: IAB EMC test configurations and performance requirements (updated) TS 38.175CR0016
Rel-17 3 changes

In Release 17, the specifications for Non-contiguous Test Configuration (NTC) were refined, introducing distinct test configuration designations "CNC" and "C/NC" to be used based on whether a base station's declared parameters for contiguous and non-contiguous operation are identical or not. This provided clearer testing rules for Multi-Standard Radio (MSR) base stations capable of non-contiguous operation. Additionally, corrections were made to the test configurations for Capability Set 7 (CS7) to ensure accurate conformance testing.

  • CR on TS 37.113 MSR base station test configuration and performance criteria R17 TS 37.113CR0123
  • CR to TS 37.113 MSR base station test configuration R17 TS 37.113CR0118
  • [RInImp9-RFmulti, TEI15] CR to TS 37.113: Test configurations correction for CS7, Rel-17 TS 37.113CR0136

Explore further

Broader topics and technologies where NTC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 37.113 vj00 EMC Requirements for Multi-Standard Radio Base Stations Rel-19
TS 38.113 vj00 NR Base Station EMC Specification Rel-19
TS 38.175 vj00 EMC for NR IAB Nodes Rel-19
TR 38.903 vj00 Test Tolerances & Measurement Uncertainties Rel-19