NRT-RIC R1-O1 Protocol for Multi-Vendor rApp Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing O-RAN architectures lack a standardized R1 application protocol for non-real-time radio access network intelligence controllers (NRT-RIC) to manage and optimize RAN operations across multiple vendor environments, hindering effective communication and interoperability between NRT-RIC and rApps.

Innovation Solution

Implementing an R1-O1 application protocol within the NRT-RIC framework to enable communication between NRT-RIC and rApps, allowing the exchange of R1 services and data models, including network information, configuration management, performance management, and fault management, thereby standardizing the management of rApps from multiple vendors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If O-RAN disaggregates RAN functions into centralized unit, distributed unit, and radio unit with open protocols, then multivendor operability is enabled, but standardized application protocol for NRT-RIC management is lacking

Engineering Contradiction:
Improvemultivendor operabilityVSAvoidprotocol standardization
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent defines a universal R1 application protocol that serves multiple functions: managing network information, configuration, performance, and faults across different vendor rApps. This standardized protocol enables the NRT-RIC to communicate with various vendor-specific rApps through a common interface, resolving the contradiction between multivendor operability and protocol standardization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Extent of automation

If NRT-RIC implements modular applications for RAN optimization, then automation and optimization capabilities are enhanced, but communication and interoperability between NRT-RIC and rApps is hindered

Engineering Contradiction:
Improveautomation of RAN operationsVSAvoidcommunication interoperability
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The patent introduces the R1 application protocol as an intermediary layer between the NRT-RIC and vendor-specific rApps. This protocol standardizes the communication interface, enabling reliable interoperability while allowing the NRT-RIC to implement automated optimization functions through modular applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If rApps from multiple vendors are deployed in O-RAN environment, then service diversity is increased, but management and standardization of these applications becomes difficult

Engineering Contradiction:
Improveservice diversityVSAvoidapplication management
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the management of diverse rApps into standardized categories: network information management, configuration management, performance management, and fault management. The R1 application protocol provides standardized procedures for each category, making it easier to manage diverse vendor applications through a unified framework.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260067654A1Apparatuses and methods for implementing an r1-o1 application protocol within a telecommunications network
Publication Date: 2026.03.05 RAKUTEN MOBILE INC
  • US20260067654A1 patent drawing
  • US20260067654A1 patent drawing
  • US20260067654A1 patent drawing

AI summary

Apparatuses and methods for a non-real-time radio access network intelligence controller (NRT-RIC) framework in an open radio access network (O-RAN). The apparatus includes: a memory storing instructions; and at least one processor configured to implement the NRT-RIC framework to: receive, from an rApp hosted by an NRT-RIC, at least one request of at least one R1-O1 related service via an R1 interface within the O-RAN architecture; and send, from the NRT-RIC framework to the rApp, at least one response of the at least one R1-O1 related service via the R1 interface; wherein the at least one request and the at least one response are implemented as data types comprising a plurality of R1 data models of an R1 application protocol that enable the NRT-RIC framework and the rApp to produce and/or consume data of the at least one R1-O1 related service in the NRT-RIC.