Description
Network-Controlled Repeater is a radio access network element that extends coverage by receiving and retransmitting RF signals, but unlike a simple repeater it can be configured, monitored, and controlled by the network. In 3GPP specifications, the concept is associated with NR repeater studies and requirements, where the repeater may be managed through OAM or through interfaces to a donor node. Its purpose is to improve coverage, capacity, and service quality in areas where direct base station transmission is weak, blocked, or inefficient.
Architecturally, an NCR typically sits between a donor gNB and user equipment. It may have RF front-end components, antennas, amplification or forwarding logic, a control unit, and a management interface. The user plane path receives downlink signals from the donor side and retransmits them toward the coverage area, while uplink signals from UEs are forwarded back toward the donor. The control path allows the network to change operating parameters such as on/off state, gain, beam direction, timing, frequency handling, power, or spatial filtering, depending on the implementation and specification profile.
A network-controlled repeater works by combining RF forwarding with network visibility. When deployed, it can be activated only when needed, for example when traffic is present, when a coverage gap is detected, or when a specific service requires extension. It can report measurements, alarms, and status information so operators can manage it like part of the RAN rather than as an unmanaged device. If interference or self-oscillation is detected, the network can reduce gain, mute a beam, change timing, or deactivate the repeater to protect the cell.
Key features include dynamic control, interference avoidance, measurement reporting, energy saving, and support for dense or difficult environments. In indoor, rural, urban shadowing, and millimeter-wave scenarios, coverage can be limited by walls, foliage, blockage, or distance. A simple amplifier may solve range but can also create uncontrolled interference. NCR addresses this by allowing the network to coordinate the repeater with neighboring cells, beams, and traffic patterns. It can also be integrated into network management workflows for deployment, monitoring, and troubleshooting.
NCR differs from full relay or integrated access and backhaul nodes because it is generally focused on RF extension rather than complete base station functions. It may not terminate full protocol stacks or provide independent cell management. Instead, it acts as a network-managed coverage enhancer. This makes it potentially simpler and lower cost than a full node, while still providing the operational control needed in modern 3GPP networks. For engineers, NCR is important as a mechanism to extend NR coverage while keeping the repeater under network control.
Purpose & Motivation
Network-Controlled Repeater exists because coverage extension is a persistent problem in mobile networks, especially as frequencies rise and deployments become denser. Traditional repeaters were often passive or semi-static devices that amplified signals without network awareness. They could improve signal strength, but they also introduced risks such as self-oscillation, uplink interference, uncontrolled gain, poor coordination with neighboring cells, and lack of monitoring or maintenance visibility.
As 5G and advanced NR deployments require precise beam management, interference control, and energy efficiency, unmanaged repeaters became less acceptable. Operators needed a way to use repeater-like coverage extension while keeping the device under network control. NCR addresses this by allowing the network to activate, configure, monitor, and coordinate the repeater. This is particularly useful for indoor coverage, rural extension, shadowed urban areas, and millimeter-wave scenarios where blockage can create unpredictable coverage holes.
The concept also responds to the need for cost-effective capacity and coverage improvement. A full base station or integrated access and backhaul node may be overkill when the main requirement is RF extension. NCR provides a middle path: it extends coverage while preserving network-level control, measurement, and management. This makes repeaters more deployable in commercial networks because they can be integrated into operations, troubleshooting, and optimization processes rather than treated as isolated equipment.
What changed in its specifications
The latest release-to-release comparison of specifications that define NCR. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Self-Configuration of RAN Network Entities removes extensive self-configuration management procedures, requirements, and data handling text, and alters some normative conditions.
Full comparison in TS 28.313 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (25 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- BigCR for introduction of performance requirements for NCR-MT in TS 38.115-1 TS 38.115CR0029
- Introduction of NCR in TS 38.304 TS 38.304CR0345
- CR for TS 38.114, Correction on terminology of NCR and RF repeater TS 38.114CR0018
- CR on FRCs of NCR MT Demodulation Performance in 38.115-1 TS 38.115CR0033
- CR on Propagation Condition of NCR-MT for 38.115-1 TS 38.115CR0034
- Draft BigCR for introduction of performance requirements for NCR-MT (TS38.115-1, Rel-18) TS 38.115CR0032
+ 15 more changes
Defining Specifications
3GPP specifications that define or reference NCR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 28.313 vk10 | SON for 5G Networks Management | Rel-20 read |
| TS 28.658 vk00 | E-UTRAN NRM Information Service | Rel-20 read |
| TR 28.841 vi01 | Technical Report on IoT NTN Enhancements | Rel-18 read |
| TS 29.153 vj00 | Ns Reference Point Protocol between SCEF and RCAF | Rel-19 read |
| TS 32.511 vj00 | ANR Management Concepts & Requirements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 38.106 vk00 | NR Repeaters: RF Requirements (TS 38.106) | Rel-20 read |
| TS 38.114 vj00 | EMC Requirements for NR Repeaters and NCR | Rel-19 read |
| TS 38.115 vj20 | Repeater Conformance Testing - Part 2: Radiated | Rel-19 read |
| TS 38.201 vj00 | NR Physical Layer General Description | Rel-19 read |
| TS 38.211 vj50 | NR Physical Channels and Signals | Rel-19 read |
| TS 38.212 vj40 | NR Multiplexing and Channel Coding | Rel-19 read |
| TS 38.213 vj50 | NR Physical Layer Control Procedures | Rel-19 read |
| TS 38.214 vj50 | NR Physical Layer Data Channel Procedures | Rel-19 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.304 vj30 | NR UE Idle and Inactive State Procedures | Rel-19 read |
| TS 38.306 vj40 | NR UE Radio Access Capability Parameters | Rel-19 read |
| TS 38.321 vj40 | NR MAC Protocol Specification | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |
| TR 38.867 vi00 | Technical Report | Rel-18 read |