Intent-Based RAN Service Management via Segmented APIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current APIs referred as R1 do not adequately support life-cycle management of Radio Access Network (RAN) services due to lack of interoperability and integration capabilities with external systems, and there is no standardization for life-cycle management within the O-RAN alliance defined standards.
Innovation Solution
The implementation of intent-based service management systems that use intent APIs to manage RAN services, allowing for automated configuration changes to align with desired service specifications, thereby enhancing interoperability and integration with external domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current R1 APIs are used for RAN service management, then existing system compatibility is maintained, but life-cycle management capability and interoperability with external systems are insufficient
Solution Approach 1:
The patent segments the service management functionality by introducing a dedicated life-cycle management module that handles service creation, modification, suspension, and termination separately from existing R1 API operations. This segmentation allows enhanced life-cycle management capabilities while maintaining compatibility with existing R1 APIs through defined interfaces.
Solution Approach 2:
The patent introduces an intermediary life-cycle management module that acts as a mediator between external systems and the RAN service management infrastructure. This intermediary translates external management requests into standardized operations, enabling improved interoperability without requiring changes to existing R1 API implementations.
2Productivity
If manual configuration management is used for RAN services, then system complexity is low, but management efficiency and service quality are poor
Solution Approach 1:
The patent implements self-service capabilities through automated configuration management that can autonomously perform service creation, modification, suspension, and termination based on received requests. The system automatically generates configuration parameters, validates service requirements, and executes management operations without manual intervention, significantly improving management efficiency.
Solution Approach 2:
The patent manages system complexity by dynamically adjusting configuration parameters based on service requirements. The life-cycle management module automatically determines optimal parameter values for different service states (creation, modification, suspension, termination) and applies appropriate parameter changes, reducing the need for complex manual configuration while maintaining system controllability.
3Adaptability or versatility
If RAN services are virtualized on generic hardware, then flexibility and vendor independence are improved, but life-cycle management integration with external systems becomes more difficult
Solution Approach 1:
The patent introduces a universal life-cycle management module that can interface with multiple external systems and vendors through standardized operations. This module provides multi-functional capabilities to handle service management requests from different sources (O-RAN Alliance systems, 3GPP systems, TMF systems) and translates them into unified internal operations, reducing integration complexity despite virtualized heterogeneous environments.
Data Source
AI summary
A method for configuring a system having a current specification is provided. The method includes receiving specification information identifying a first desired specification of a first requested service for the system and determining whether the system satisfies the first desired specification. Determining whether the system satisfies the first desired specification includes determining whether there are any discrepancies between the first desired specification and the current specification of the system. The method further includes after determining that there is a discrepancy between the first desired specification and the current specification of the system, identifying a first group of one or more configuration changes for the system for fixing said discrepancy and implementing in the system one or more configuration changes included in the first group.