NoN-RT RIC

Article by Abhijeet Kumar

What is Non-RT RIC?

In the simplest terms, the Non-Real-Time RIC is a software platform that operates within the Open RAN (O-RAN) architecture. Its primary role is to enable more intelligent management of radio resources and network functions, but it operates on a timescale of one second or longer. This differentiates it from the Near-Real-Time RIC (Near-RT RIC), which operates on a timescale of under one second.

Role in O-RAN

The O-RAN architecture is designed to be open and intelligent, with the Non-RT RIC playing a pivotal role in its intelligence layer. It sits above the Near-RT RIC and provides policy guidance and model management. This enables the network to adapt to changing conditions and user demands without human intervention.

Impact on Telecom Operators

For telecom operators, Non-RT RIC offers a path to more automated and optimized network operations, leading to reduced operational expenses and the ability to provide differentiated services. It's like having an intelligent assistant to make strategic decisions to improve the network.

The Functions of Non-RT RIC

Policy-Based Guidance

Non-RT RIC provides policies to the Near-RT RIC, which executes these policies in real time. This is akin to a manager setting goals for a team, who then work out how to achieve those goals.

AI and ML Integration

Integrating Artificial Intelligence (AI) and Machine Learning (ML) with Non-RT RIC enables predictive analytics and pattern recognition, leading to proactive network optimization.

Resource Management

It manages resources at a higher level by providing strategies for radio resource allocation, energy savings, and load balancing.

Deep Dive into Non-RT RIC Functions

Detailed Functions

Non-RT RIC performs several functions crucial to network management:

1. Service Management: It orchestrates and manages RAN services over more extended periods.
2. AI/ML Workflow Functions: Non-RT RIC hosts AI/ML workflows that process data and provide insights for network optimization.
3. Data Management: It handles large datasets and extracts actionable intelligence to guide the RAN's behaviour.
4. Policy Control: Non-RT RIC manages and controls the policies that govern the behavior of the Near-RT RIC and the RAN.

rAPPs: An Overview

rApps can be developed by various vendors and are meant to be interoperable across different non-RT RIC platforms due to the open architecture principles of O-RAN. They interact with the Non-RT RIC through defined interfaces, mainly the R1 interface, to perform various functions from analytics to policy management.

R1 Interface Functions

The R1 interface is a critical point of communication between the rApps and the Non-RT RIC. It serves multiple purposes:

1. Service Management Communication: It allows rApps to communicate with the RIC platform for managing and orchestrating RAN services.
2. Information Exchange: The R1 interface facilitates the exchange of information necessary for the rApps to execute their logic. This includes network data, policies, and models.
3. Policy Enforcement: Through R1, rApps can enforce policy decisions made at the Non-RT RIC level, which are then translated into actions at the Near-RT RIC or directly in the RAN.
4. Exposure of Capabilities: rApps can expose their capabilities and services to other network functions or applications via the R1 interface, making the system modular and extensible.

R1 Service Management and Exposure Functions

The R1 service management and exposure functions enable rApps to manage the lifecycle of services within the RAN. This includes:

• Deployment: Introducing new services into the RAN ecosystem.
• Operation: Ensuring services are running as intended and optimizing their performance.
• Scaling: Adjusting the resources allocated to services based on current demand and performance metrics.
• Termination: Removing services no longer needed or upgrading to newer versions.

Exposure functions are about making specific capabilities of rApps available to other parts of the network or even external systems. This might include sharing analytics results, optimization strategies, or available services that third parties could leverage.

rApps Management Functions

The management functions of rApps are focused on overseeing the various applications running on the Non-RT RIC. They include:

• Monitoring: Continuously tracking the performance and health of rApps to ensure they are functioning correctly.
• Configuration: Setting up and modifying the operational parameters of rApps to fit the needs of the network.
• Optimization: Fine-tuning the behavior of rApps to maximize network efficiency and resource utilization.
• Lifecycle Management: Managing the installation, update, and retirement of rApps within the Non-RT RIC.

• rAPPs Creation.

Creating rApps (RAN Intelligent Controller Applications) in the O-RAN (Open RAN) ecosystem involves several steps from design to deployment. rApps are applications that run on the Non-Real-Time RIC (Non-RT RIC) platform and provide advanced functionalities for managing and optimizing the Radio Access Network (RAN). Here’s a detailed process of creating rApps:

1. Understand O-RAN Architecture and Specifications

Before starting the development, it's crucial to understand the O-RAN architecture, focusing on the Non-RT RIC, its functionalities, interfaces (especially R1), and the O-RAN Alliance specifications and guidelines.

2. Define the rApp Use Case

Identify a specific use case for the rApp. It could be related to network optimization, spectrum management, energy savings, or other RAN functionalities. This step involves understanding the problem you want to solve or the optimization you want to achieve.

3. Design the rApp

Design the rApp with the chosen use case in mind, considering how it will interact with the RIC and the RAN components. Design considerations should include:

• Interface interactions (R1, A1, O1, etc.)
• Data requirements and sources
• Algorithms and models (if implementing AI/ML)
• Scalability and resilience

4. Develop the rApp

Develop the rApp according to the design:

• Use a programming language and framework that is supported by the Non-RT RIC platform.
• Follow best practices for software development, including version control, testing, and documentation.
• Implement the necessary interfaces, ensuring compliance with O-RAN specifications.

5. Integrate AI/ML Models (if applicable)

If the rApp uses AI/ML, develop or integrate pre-existing models. Train these models with relevant data and ensure they can be updated or retrained as needed.

6. Test the rApp

Conduct thorough testing of the rApp:

• Unit testing for individual components
• Integration testing for interactions with the RIC and simulated RAN components
• Performance testing to ensure that the rApp can handle the expected load

7. Simulate and Validate the rApp

Before deploying in a live environment, simulate the rApp's operation to validate its functionality and performance. This can be done using testbeds that mimic the RAN environment.

8. Security and Compliance Checks

Ensure the rApp meets the security standards required for network operations. It should also comply with any regulatory requirements.

9. Deployment

Once the rApp is tested and validated, deploy it to the Non-RT RIC platform:

• Package the rApp according to the platform's requirements.
• Use the RIC's deployment mechanisms to launch the rApp.
• Monitor the rApp as it begins operation to ensure it integrates smoothly with the live environment.

10. Lifecycle Management

After deployment, manage the rApp's lifecycle:

• Monitor its performance and stability.
• Update the rApp to address any issues, improve performance, or add features.
• Retire the rApp when it is no longer needed or replace it with an updated version.