Inferensys

Glossary

Non-Real-Time RAN Intelligent Controller (Non-RT RIC)

A logical function within the O-RAN architecture that hosts rApps and provides AI/ML-driven policy and configuration guidance to the Near-RT RIC over the A1 interface for long-term network optimization.
Engineer optimizing context window usage on laptop, token usage charts visible, technical work session.
O-RAN ARCHITECTURE

What is Non-Real-Time RAN Intelligent Controller (Non-RT RIC)?

A logical function within the O-RAN architecture that hosts rApps and provides AI/ML-driven policy and configuration guidance to the Near-RT RIC over the A1 interface for long-term network optimization.

The Non-Real-Time RAN Intelligent Controller (Non-RT RIC) is a logical function within the Service Management and Orchestration (SMO) framework that executes AI/ML workflows with a latency greater than one second to provide policy-based guidance, enrichment information, and model management to the Near-RT RIC via the A1 interface. It hosts rApps, which are modular applications that analyze historical network data, predict long-term trends, and generate optimization policies for goals like energy saving and coverage enhancement.

Operating outside the near-real-time control loop, the Non-RT RIC handles non-time-critical tasks including AI/ML model training, validation, and lifecycle management before deploying inference models to the Near-RT RIC for execution. It translates high-level business intents into machine-executable policies and provides enrichment data—such as predicted traffic patterns—enabling the Near-RT RIC to make more informed, context-aware decisions for closed-loop automation across the RAN.

ARCHITECTURAL CAPABILITIES

Key Functional Characteristics

The Non-RT RIC provides the centralized intelligence layer for the O-RAN architecture, operating on time scales greater than one second to enable long-term policy guidance and AI/ML model lifecycle management.

01

Policy-Based Guidance over A1

The Non-RT RIC communicates declarative policies and enrichment information to the Near-RT RIC via the standardized A1 interface. Unlike direct control commands, these policies define high-level optimization targets—such as maximizing energy efficiency or guaranteeing slice SLAs—while allowing the Near-RT RIC to autonomously determine the specific radio resource management actions. This hierarchical separation of concerns ensures that long-term business objectives are enforced without micromanaging millisecond-level control loops.

> 1s
Control Loop Latency
02

rApp Hosting and Execution Environment

The Non-RT RIC serves as the exclusive hosting platform for rApps—modular, microservice-based applications that leverage AI/ML analytics to generate optimization recommendations. Each rApp addresses a specific use case:

  • Traffic steering rApps analyze historical patterns to optimize load distribution policies
  • Energy saving rApps predict cell utilization to recommend carrier shutdown schedules
  • Anomaly detection rApps identify degradation trends before failures occur rApps consume data from the R-NIB and output policy guidance, never executing direct RAN control.
03

AI/ML Model Lifecycle Management

The Non-RT RIC orchestrates the complete end-to-end lifecycle of machine learning models used throughout the RAN:

  • Training: Leverages offline data lakes with historical network telemetry to train models without real-time constraints
  • Validation: Tests model accuracy against held-out datasets before deployment
  • Deployment: Pushes trained model artifacts to the Near-RT RIC for inference execution by xApps
  • Monitoring: Continuously tracks model drift by comparing live inference accuracy against baselines
  • Rollback: Automatically reverts to previous model versions if performance degrades
04

Intent Translation Engine

A critical component that converts high-level business intents expressed in natural language or declarative syntax into machine-executable policies. For example, an operator intent stating 'Ensure premium subscribers receive at least 50 Mbps during peak hours' is decomposed into:

  • Specific QoS Class Identifier (QCI) mappings
  • Resource block allocation priorities
  • Inter-frequency load balancing thresholds This translation layer bridges the gap between business operations and network engineering, enabling true intent-based networking within the O-RAN framework.
05

Conflict Mitigation Coordination

Multiple rApps operating simultaneously may generate contradictory policy recommendations—for instance, an energy-saving rApp requesting cell shutdown while a capacity rApp demands additional carriers. The Non-RT RIC implements conflict detection and resolution mechanisms that:

  • Analyze overlapping policy scopes across rApps
  • Apply operator-defined priority rules to resolve contradictions
  • Coordinate with the Near-RT RIC to ensure only coherent, non-conflicting guidance is enforced This safeguard prevents the network instability that could arise from uncoordinated autonomous optimization loops.
06

Data Aggregation and Enrichment

The Non-RT RIC ingests and processes long-term performance data from multiple sources to provide contextual enrichment to the Near-RT RIC:

  • Historical PM (Performance Measurement) counters from the O1 interface
  • UE mobility patterns and geolocation trends
  • External data sources such as weather forecasts or event schedules
  • Cross-cell and cross-vendor topology information This enriched data enables xApps to make more informed near-real-time decisions by understanding broader temporal and spatial context beyond their immediate E2 data streams.
NON-RT RIC CLARIFIED

Frequently Asked Questions

Clear, technical answers to the most common questions about the Non-Real-Time RAN Intelligent Controller's role, interfaces, and AI-driven optimization logic.

The Non-Real-Time RAN Intelligent Controller (Non-RT RIC) is a logical function within the O-RAN Service Management and Orchestration (SMO) framework that provides AI/ML-driven policy and configuration guidance for long-term network optimization, operating on a timescale greater than 1 second. It hosts rApps, which are microservice-based applications that consume enriched data from the network to perform predictive analytics, model training, and policy generation. The Non-RT RIC communicates its guidance to the Near-RT RIC over the A1 interface, using declarative policies and enrichment information to steer the near-real-time control loops without directly executing them. This separation of concerns allows the Non-RT RIC to focus on computationally intensive tasks like offline model training and intent translation, while the Near-RT RIC handles latency-sensitive radio resource management.

ARCHITECTURAL COMPARISON

Non-RT RIC vs. Near-RT RIC

Functional and operational differences between the two logical controllers in the O-RAN intelligent control plane

FeatureNon-RT RICNear-RT RIC

Control loop latency

1 second

10ms to 1 second

Primary interface

A1 Interface

E2 Interface

Hosted application type

rApps

xApps

AI/ML training capability

Direct RAN node control

Policy generation

Resides within SMO framework

Typical optimization scope

Network-wide, long-term

Cell-level, near-real-time

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.