Description
The Network Status Continuous Report Request (NCR) is a network management mechanism introduced in 3GPP Release 13, allowing the network to request user equipment (UE) to continuously report various status parameters. It operates within the management plane, typically initiated by the network's management system or operations, administration, and maintenance (OAM) entities. NCR enables the collection of real-time data on radio conditions, mobility events, and UE performance, which is transmitted to the network for analysis. This function is part of the broader self-organizing network (SON) and minimization of drive tests (MDT) frameworks, aimed at automating network optimization and reducing operational costs.
Architecturally, NCR involves interactions between the OAM system, the radio access network (RAN), and the UE. The network sends an NCR request message to the UE, specifying the parameters to be reported, such as reference signal received power (RSRP), reference signal received quality (RSRQ), cell identities, and timing information. The UE then continuously monitors these parameters and sends reports back to the network at defined intervals or upon triggering events. The reports are aggregated and processed by network management systems to generate insights into network performance, coverage issues, and interference patterns.
How NCR works involves several steps: first, the network configures the UE with reporting criteria via RRC signaling or management protocols. The UE enters a continuous reporting mode, collecting data based on these criteria. Reports are formatted according to specified templates and transmitted using established signaling channels, often leveraging existing measurement reporting mechanisms but with enhanced continuity. The network uses this data for purposes like coverage optimization, handover parameter tuning, and identification of radio link failures. NCR supports both logged and immediate reporting modes, depending on network requirements.
Key components include the NCR configuration parameters, reporting triggers, and data structures for encapsulating status information. The mechanism integrates with existing measurement and reporting procedures in LTE and NR, extending them for continuous, network-requested monitoring. It plays a critical role in enabling proactive network management, allowing operators to detect and resolve issues before they impact users. By providing a standardized way to gather UE-side data, NCR enhances the efficiency of network optimization processes.
Purpose & Motivation
NCR was created to address the need for real-time, continuous network status monitoring from the UE perspective, which traditional drive tests and periodic reporting could not fully satisfy. Prior approaches, like manual drive tests, were costly, time-consuming, and provided only snapshot data. NCR enables automated, continuous data collection, solving problems related to dynamic network conditions and sporadic issues that intermittent measurements might miss. It supports the evolution toward self-optimizing networks by providing a rich dataset for analytics and automation.
Historical context includes the push for SON and MDT in 3GPP, which aimed to reduce operational expenses and improve network performance. NCR builds on earlier MDT features by allowing network-initiated continuous reporting, rather than relying solely on UE-triggered or logged measurements. This addresses limitations of previous methods, which often had gaps in data coverage or required UE cooperation only during specific events. NCR ensures that operators have a steady stream of information for ongoing optimization.
Motivations for NCR include the increasing complexity of networks with dense deployments and heterogeneous environments, where continuous monitoring is essential for maintaining quality of service. It solves challenges in detecting transient issues, optimizing mobility parameters, and enhancing user experience in real-time. By integrating with management systems, NCR facilitates data-driven decision-making, supporting advanced use cases like predictive maintenance and AI-based network optimization.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (383 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the NCR (Network Status Continuous Report Request) function was not explicitly introduced or defined in the provided grounding context or list of Change Request titles. The listed CRs and specification text focus on other reporting and notification mechanisms, such as location reporting for UEs in RRC_INACTIVE state, Area of Interest reporting, and various subscription status notifications, but do not specify the creation or enhancement of an "NCR" function.
- Data Volume Reporting for Option 4/7 TS 23.501CR0661
- Introduce reportCGI towards NR neighbour cell TS 36.300CR1145
- Delay budget report and MAC CE adaptation for NR for TS 38.300 TS 38.300CR0042
- Delay budget report and MAC CE adaptation for NR for TS 38.306 TS 38.306CR0013
- CR to direct current report for UL and SUL TS 38.331CR1013
- Alignment with TS 23.502 on Service Request procedure TS 23.501CR0034
+ 67 more changes
In Release 16, enhancements were made to the Network Status Continuous Report Request (NCR) function to support more granular and efficient reporting mechanisms. Specifically, this included the introduction of **autonomous gap in CGI reporting** and **Uplink Tx DC location reporting for two carrier uplink CA**, enabling new UE measurement and reporting capabilities without constant network supervision. Furthermore, Release 16 clarified and corrected procedures related to **Small Data Rate Control and Exception Reporting** and **Location reporting**, refining the network's ability to request and manage these continuous reports.
- Handling of Stored Small Data Rate Control Status at Subsequent PDU Session Establishment TS 23.501CR1252
- Network request re-activation of user-plane resources TS 23.501CR1351
- Network request re-activation of user-plane resources TS 23.501CR1586
- Aperiodic CSI-RS Triggering for UE reporting beamSwitchTiming values of 224 and 336 TS 38.214CR0060
- Behaviour for triggered with a CSI report for non-active BWP TS 38.214CR0061
- Introducing autonomous gap in CGI reporting TS 38.306CR0226
+ 73 more changes
In Release 17, the NCR (Network Status Continuous Report Request) function was enhanced to support continuous location reporting for a UE in RRC_INACTIVE state whenever the UE changes cells, as specified in the location reporting procedures. This was introduced alongside clarifications for NG-RAN location reporting in RRC_INACTIVE and the reporting of TAIs corresponding to the Selected PLMN.
- Introduction of architecture for AF requested support of Time Sensitive Communication and Time Synchronization TS 23.501CR2833
- Updates to AF requests to influence traffic routing TS 23.501CR2913
- Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] TS 36.300CR1363
- Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] TS 38.300CR0474
- CR on the CBM/IBM reporting-38306 TS 38.306CR0690
- Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] TS 38.306CR0747
+ 50 more changes
In Release 18, the new NCR (Network Status Continuous Report Request) function introduced support for reporting the RAN timing synchronization status change from the AMF to the TSCTSF and for discontinuous coverage reporting. It also included enhancements to the measurement report procedure and introduced specific performance and RRM test requirements for NCR-MT within the NG-RAN specifications.
- Reporting the RAN timing synchronization status change from AMF to TSCTSF TS 23.501CR3807
- Introduction of support for Jitter Measurement and End of Data Burst reporting to the NG-RAN TS 23.501CR3875
- Support for network timing synchronization status and reporting KI1 - description TS 23.501CR3892
- Ensuring that a geographical area requested for a time sync service coincides with a RA TS 23.501CR4133
- Discontinuous coverage reporting TS 23.501CR4685
- Big CR to TS 38.106 Introduction of NCR TS 38.106CR0050
+ 132 more changes
In Release 19, the NCR (Network Status Continuous Report Request) function was enhanced with the introduction of an expected EIRP mask core requirement, as specified for NR. Furthermore, the release clarified and updated procedures for QoS monitoring and reporting during UPF relocation and PDU session release, and introduced Available Bitrate Reporting when the Serving RAN Node changes.
- Support of Slice change based on AF request TS 23.501CR5764
- AF request and functionalities enhancement to support N6 delay measurement TS 23.501CR5443
- CR to TS 38.106 for introduction of expected EIRP mask core requirement for NCR TS 38.106CR0112
- TEI19 Counting of CSI-RS resource referred by N CSI reporting settings [SimCSI_count] TS 38.214CR0681
- Introduction of control parameters for on-demand posSIB request [OdPosSIB_Req] TS 38.300CR1009
- Support Aerial UE Flight Information Reporting TS 38.300CR1031
+ 31 more changes
Explore further
Broader topics and technologies where NCR plays a role.
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 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 28.313 vk00 | Management and orchestration; SON for 5G networks | Rel-20 |
| TS 28.658 vj00 | E-UTRAN NRM IRP Information Service | Rel-19 |
| TR 28.841 vi01 | Technical Report on IoT NTN Enhancements | Rel-18 |
| TS 29.153 vj00 | Ns Reference Point Protocol between SCEF and RCAF | Rel-19 |
| TS 32.511 vj00 | ANR Management Concepts & Requirements | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 38.106 vj20 | NR Repeater Radio Transmission and Reception | Rel-19 |
| TS 38.114 vj00 | EMC Requirements for NR Repeaters and NCR | Rel-19 |
| TS 38.115 vj20 | NR Repeater RF Conformance Testing Part 1 | Rel-19 |
| TS 38.201 vj00 | NR Physical Layer General Description | Rel-19 |
| TS 38.211 vj10 | NR Physical Channels and Modulation | Rel-19 |
| TS 38.212 vj10 | NR Multiplexing and Channel Coding | Rel-19 |
| TS 38.213 vj10 | NR Physical Layer Control Procedures | Rel-19 |
| TS 38.214 vj10 | NR Physical Layer Procedures for Data | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.304 vj00 | UE RRC_IDLE and RRC_INACTIVE Procedures | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.321 vj00 | NR MAC Protocol Specification | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TR 38.867 vi00 | Technical Report | Rel-18 |