Description
The NCR-node (Network-Controlled Repeater node) is a RAN node introduced in 3GPP Release 18 as part of the Network-Controlled Repeater framework. It is defined as a RAN node comprising two functional components: the NCR-MT (Mobile Termination) and the NCR-Fwd (Forwarding entity). Together these components allow the node to act as a network-managed repeater that extends coverage while remaining under the control of the gNB.
The NCR-MT provides the control-plane connectivity between the NCR-node and the controlling gNB. It behaves in a manner analogous to a UE's mobile termination, maintaining a link to the gNB over which it receives side control information. This side control information is used to configure the NCR-Fwd. The NCR-MT therefore serves as the management and control channel for the repeater, enabling the gNB to turn the repeater on or off, adjust its transmit power, steer beams, and coordinate its operation with the rest of the network.
The NCR-Fwd performs the actual amplify-and-forward relaying of uplink and downlink RF signals between the gNB and the UE. It operates over a backhaul link toward the gNB and an access link toward the UE. Because the forwarding is controlled via the NCR-MT, the NCR-node avoids the interference and instability problems associated with traditional uncontrolled analog repeaters. The node does not terminate user-plane protocol layers for the UE; it transparently relays the RF signal, keeping complexity and cost low.
The architecture of the NCR-node is described in TS 38.300, which covers the overall NG-RAN architecture and the role of NCR. TS 38.321 specifies the MAC layer procedures used by the NCR-MT to receive and act on side control information. The split between NCR-MT and NCR-Fwd is central to the design: it separates the control plane (management of the repeater) from the data plane (RF forwarding), allowing each function to be optimized independently. This mirrors, at a high level, the separation of concerns seen in other RAN nodes, though the NCR-node is far simpler than a gNB or IAB node.
In the network, the NCR-node functions as a coverage extension element. It is deployed where additional coverage or capacity is needed but where a full base station or IAB node would be uneconomical. Because it is a standardized RAN node with defined control interfaces, it can be integrated into network planning, mobility management, and interference coordination. The NCR-node thus represents 3GPP's standardized approach to making repeaters first-class, manageable citizens of the radio access network.
Purpose & Motivation
The NCR-node was created to bring repeaters under standardized network control. Before Release 18, repeaters were largely vendor-specific, uncontrolled RF devices that amplified whatever they received. While inexpensive, they could amplify interference and noise, create feedback loops, and make network optimization difficult. The NCR-node solves this by defining a RAN node with an explicit control component (NCR-MT) that receives side control information from the gNB, allowing the network to manage the repeater's behavior.
The NCR-node addresses the economic challenge of coverage extension, particularly in higher frequency bands where propagation is harsh and site deployment is costly. By providing a low-complexity, backhaul-free relay that is nonetheless controllable, the NCR-node fills a gap between uncontrolled analog repeaters and full base stations or IAB nodes. It enables operators to extend coverage into holes and cell edges without the capital and operational expense of a complete gNB deployment.
Standardizing the NCR-node also enables multi-vendor interoperability and consistent network management. Operators can deploy NCR-nodes from different vendors and manage them through standardized procedures, integrating them into interference coordination, energy saving, and mobility strategies. This standardization was a key motivation for the Release 18 work on Network-Controlled Repeaters.
What changed in its specifications
The latest release-to-release comparison of specifications that define NCR-node. Each summary describes the whole specification, not only this term.
Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.
Full comparison in TS 38.300 →Rel-19 adds sub-band full duplex handling to the NR Random Access procedure. It covers new second-PRACH-occasion RO type selection, power settings, Msg1 repetition, and RSRP threshold settings.
Full comparison in TS 38.321 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference NCR-node, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.321 vj40 | NR MAC Protocol Specification | Rel-19 read |