NRT-RIC R1-O1 Data Models for Multi-Vendor O-RAN Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing O-RAN architectures lack standardized R1-O1 CM data models for effective communication and management of network elements across multiple vendors, hindering efficient operation and optimization of radio access networks.
Innovation Solution
Implementing a non-real-time radio access network intelligence controller (NRT-RIC) framework that utilizes R1-O1 CM data models for retrieving, reading, and writing configuration management data to network elements, enabling standardized communication and management across different vendor platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If O-RAN disaggregates RAN functions into multiple vendor-specific components (CU, DU, RU), then device complexity and vendor diversity increase, but interoperability and standardized management deteriorate
Solution Approach 1:
The NRT-RIC framework acts as an intermediary layer between the O1 interface (standardized management interface) and the R1 interface (vendor-specific implementation interface). It translates standardized O1 CM data model requests into vendor-specific R1 data model operations, enabling multi-vendor interoperability without requiring each vendor to implement the full O1 standard directly.
Solution Approach 2:
The NRT-RIC framework provides universal functionality by implementing a standardized O1 CM data model that can manage multiple types of network elements from different vendors through a single unified interface, making the system adaptable to various vendor implementations while maintaining standardized management.
2Adaptability or versatility
If vendor-specific hardware and software are used in traditional RAN, then device complexity is reduced, but adaptability and multi-vendor support deteriorate
Solution Approach 1:
The system segments the management functionality into two distinct layers: the O1 interface layer with standardized CM data models for vendor-agnostic management, and the R1 interface layer with vendor-specific data models for actual implementation. The NRT-RIC framework bridges these layers, allowing each vendor to maintain simpler vendor-specific implementations while the system as a whole achieves multi-vendor support.
3Ease of operation
If standardized O1 interface is implemented across all network elements, then interoperability improves, but ease of operation deteriorates due to lack of vendor-specific optimizations
Solution Approach 1:
The NRT-RIC framework serves as a mediator that receives standardized O1 interface requests and translates them into vendor-specific R1 interface operations. This allows network operators to use standardized O1 CM data models for ease of operation while the framework handles the complexity of vendor-specific optimizations and implementations.
Solution Approach 2:
The framework changes the parameter representation between interfaces: it uses standardized O1 CM data model parameters at the management interface and transforms them into vendor-specific R1 data model parameters at the implementation interface, preserving both standardized management and vendor-specific optimizations.
Data Source
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.