RIC Platform Extensions and Adapters for O-RAN Vendor Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The O-RAN standard lacks defined interfaces for the RIC platform to communicate with network functions for different vendor services, hindering efficient operation and vendor perspective integration.
Innovation Solution
Implementing platform extensions and network function adapters that enable the RIC to communicate with external network vendor services by determining parameters and generating responses based on network functions, using observability frameworks and inventory data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the O-RAN standard is used for RIC platform control, then standardization and interoperability are improved, but the ability to interface with different vendor services is worsened due to lack of defined interface specifications
Solution Approach 1:
The patent introduces platform extensions and network function adapters as intermediary components between the RIC platform and vendor-specific network functions. These adapters translate and normalize communications, allowing the standardized RIC platform to interface with diverse vendor services without direct complexity exposure. The adapter layer mediates the interaction, converting vendor-specific protocols into standardized RIC interface formats.
Solution Approach 2:
The patent segments the interface architecture into distinct layers: the core RIC platform, platform extensions, and vendor-specific adapters. This segmentation isolates the standardized control plane from vendor-specific implementations, allowing each layer to be developed and maintained independently. The adapters handle vendor-specific complexities while the RIC platform maintains standardization.
2Adaptability or versatility
If vendor-specific network functions are integrated directly into the RIC platform, then service functionality is improved, but operational efficiency is worsened due to lack of standardized communication protocols
Solution Approach 1:
The network function adapters serve as intermediaries that enable vendor-specific services to be integrated into the RIC platform while maintaining standardized communication protocols. The adapters translate vendor-specific service requests into standardized RIC commands and responses, ensuring operational efficiency is maintained despite the diversity of vendor implementations.
Solution Approach 2:
The patent creates a universal adapter framework that can handle multiple vendor services through a common interface structure. The platform extensions provide multi-functional capabilities that work across different vendor implementations, allowing a single standardized interface to support diverse service functionalities without requiring separate integration paths for each vendor.
3Adaptability or versatility
If platform extensions and adapters are added to enable vendor service integration, then vendor perspective integration is improved, but system complexity is worsened
Solution Approach 1:
The patent segments the complexity into manageable components by separating the core RIC platform from vendor-specific adaptations. Platform extensions and adapters are added as modular, independent components that can be selectively deployed based on vendor requirements. This segmentation contains complexity within isolated adapter modules rather than propagating it throughout the entire system.
Solution Approach 2:
The adapters act as intermediary components that encapsulate vendor-specific complexity, preventing it from propagating to the core RIC platform. By placing the complexity burden on isolated adapter layers rather than the core system, the overall architecture maintains simplicity at critical interfaces while still supporting diverse vendor implementations.
Data Source
AI summary
A method of using a RAN intelligent controller (RIC) platform extension may include (i receiving a network function from a RIC platform, the network function including an intent, (ii) determining the intent of the network function, (iii) generating a response to the network function based on the intent, wherein the response to the network function includes configuration data for one or more network vendor services, (iv) determining one or more parameters for the one or more network vendor services using network function adapters, and (v) sending the configuration data to the one or more network vendor services using the one or more determined parameters.