R1-O1 Data Models for Multi-Vendor O-RAN Configuration Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing O-RAN architecture lacks standardized R1-O1 CM data models for effective communication and management of network elements across multiple vendor environments, hindering efficient configuration and optimization.

Innovation Solution

Implementing a non-real-time radio access network intelligence controller (NRT-RIC) framework with specified R1-O1 CM data models for retrieving, reading, and writing configuration management data, enabling standardized communication and management of network elements via the R1 interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If O-RAN architecture uses multiple vendors for network elements, then vendor-specific hardware and software can be provided, but standardized communication and management across vendors becomes difficult

Engineering Contradiction:
Improvemulti-vendor supportVSAvoidcommunication standardization
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal R1-O1 CM data model that enables the NRT-RIC framework to communicate with network elements from multiple vendors through a standardized interface. The data model defines common configuration management attributes and operations that work across different vendor implementations, allowing the system to manage diverse network elements uniformly without requiring vendor-specific protocols.

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

2Ease of manufacture

If vendor-specific implementation is used, then each vendor can optimize their hardware and software, but configuration management and optimization across the network becomes inefficient

Engineering Contradiction:
Improvevendor implementation flexibilityVSAvoidconfiguration management efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent introduces the R1-O1 CM data model as an intermediary layer between the NRT-RIC framework and vendor-specific network elements. This data model acts as a standardized interface that translates general configuration management operations into vendor-specific commands, enabling efficient centralized management while preserving vendor implementation flexibility and optimization capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If no standardized R1-O1 CM data models are implemented, then implementation flexibility is maintained, but effective communication and management of network elements is hindered

Engineering Contradiction:
Improveimplementation flexibilityVSAvoidcommunication effectiveness
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent defines specific parameter structures within the R1-O1 CM data model that standardize how configuration management information is exchanged between the NRT-RIC framework and network elements. By establishing standardized parameters for configuration retrieval, reading, and writing operations, the system ensures reliable and effective communication while maintaining implementation flexibility through the modular data model design.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250338099A1Apparatus and method for implementing r1-o1 data models for o1 related services within a telecommunications network
Publication Date: 2025.10.30 RAKUTEN MOBILE INC
  • US20250338099A1 patent drawing
  • US20250338099A1 patent drawing
  • US20250338099A1 patent drawing

AI summary

An apparatus for a non-real-time radio access network intelligence controller (NRT-RIC) framework in an O-RAN. The apparatus includes a memory storing instructions; and at least one processor configured to implement the NRT-RIC framework of an NRT-RIC by executing the instructions to: receive, from an rApp a first request for retrieving a configuration schema of a network element in the O-RAN, the first request comprising a first R1-O1 data model identifying the network element, and the first request being received via an R1 interface; and send, from the NRT-RIC framework, a first response to the requested configuration schema, the first response comprising a second R1-O1 data model identifying the network element and identifying a configuration management (CM) attribute of the network element, wherein the R1 interface enables the NRT-RIC framework and the rApp to produce and consume at least one O1 interface related R1 service in the NRT-RIC.