NCR

Network Status Continuous Report Request

Management
Introduced in Rel-13
A network management function that requests continuous reporting of network status information from user equipment (UE). It enables real-time monitoring of radio conditions, mobility events, and performance metrics. This data is used for network optimization, troubleshooting, and enhancing user experience.

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.

Key Features

  • Enables network-initiated continuous status reporting from UE
  • Supports reporting of RSRP, RSRQ, cell IDs, and mobility events
  • Integrates with MDT and SON frameworks for automation
  • Provides both immediate and logged reporting modes
  • Configurable via RRC signaling for flexible parameter collection
  • Enhances real-time network monitoring and troubleshooting

Evolution Across Releases

Rel-13 Initial

Introduced NCR as part of enhanced MDT and SON capabilities. Initial architecture allowed the network to request continuous reporting of radio measurements and mobility information from UE. Supported parameters included basic LTE measurements like RSRP and RSRQ, with reporting triggered by network configuration.

Defining Specifications

SpecificationTitle
TS 23.501 3GPP TS 23.501
TS 28.313 3GPP TS 28.313
TS 28.658 3GPP TS 28.658
TS 28.841 3GPP TS 28.841
TS 29.153 3GPP TS 29.153
TS 32.511 3GPP TR 32.511
TS 36.300 3GPP TR 36.300
TS 38.106 3GPP TR 38.106
TS 38.114 3GPP TR 38.114
TS 38.115 3GPP TR 38.115
TS 38.201 3GPP TR 38.201
TS 38.211 3GPP TR 38.211
TS 38.212 3GPP TR 38.212
TS 38.213 3GPP TR 38.213
TS 38.214 3GPP TR 38.214
TS 38.300 3GPP TR 38.300
TS 38.304 3GPP TR 38.304
TS 38.306 3GPP TR 38.306
TS 38.321 3GPP TR 38.321
TS 38.331 3GPP TR 38.331
TS 38.867 3GPP TR 38.867