E2 Service Model Abstraction for O-RAN xApp Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Open Radio Access Networks (O-RAN), there are interoperability issues between extended applications (xApps) and E2 nodes due to unsupported service models, leading to complex subscription management and version monitoring, which complicates data collection and xApp development.
Innovation Solution
Implementing a service model abstraction layer and calculator to abstract service models from xApps, allowing them to focus on required parameters rather than specific service models, and facilitating unified standard interfaces for data communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If xApps directly subscribe to E2 nodes using specific service models, then data collection can be achieved, but interoperability issues arise due to unsupported service models and version differences
Solution Approach 1:
The patent introduces an intermediary layer (service model adapter or abstraction layer) between the xApp and the E2 node. This intermediary translates service model subscriptions from the xApp's supported models into the service models supported by the E2 node, enabling communication without direct compatibility. The intermediary handles version monitoring and model mapping, resolving interoperability issues while maintaining adaptability.
Solution Approach 2:
The patent creates a universal service model interface that can work with multiple different E2 node service models. The xApp subscribes to a standardized service model, and the system automatically adapts this subscription to work with various E2 node implementations. This universal interface approach allows a single xApp to operate across different network configurations without requiring multiple specialized service model implementations.
2Adaptability or versatility
If xApps support multiple service models and monitor versions, then compatibility with different E2 nodes is improved, but system complexity increases
Solution Approach 1:
The patent extracts the service model complexity from the xApp and places it in a separate management component. The xApp only needs to support a single, simplified service model, while the extracted complexity of supporting multiple models and monitoring versions is handled by the intermediary layer. This separation reduces xApp complexity while maintaining compatibility across different E2 nodes.
Solution Approach 2:
The system implements self-service mechanisms where the intermediary automatically detects which service models are supported by the E2 node and configures appropriate subscriptions without manual intervention. Version monitoring and model mapping are performed automatically by the system, eliminating the need for complex manual configuration and reducing operational complexity.
3Reliability
If xApps implement version monitoring and multiple service model subscriptions, then interoperability is maintained, but development complexity and time increase
Solution Approach 1:
The patent implements preliminary action by pre-defining service model mappings and compatibility rules in the intermediary layer. During system initialization, the intermediary automatically establishes the appropriate service model subscriptions based on the E2 node's capabilities. This preliminary configuration eliminates the need for xApps to implement complex version monitoring logic, significantly reducing development time while maintaining interoperability.
Solution Approach 2:
The intermediary handles all version monitoring and service model translation automatically, shielding xApp developers from these complexities. Developers only need to write xApps using the simplified service model interface, while the intermediary manages the complex tasks of version detection, model mapping, and subscription management. This approach drastically reduces development time while ensuring reliable interoperability.
Data Source
AI summary
A system can comprise a near real-time radio access network intelligent controller that comprises an application and a service model component, wherein the service model component is configured to receive respective indications of supported service models and key performance indicators from respective network nodes of a group of network nodes that is part of a radio access network, wherein the service model component is configured to receive a request from the application for a key performance indicator, wherein the service model component is configured to subscribe to a network node of the group of network nodes for the key performance indicator, wherein the network node supports a service model that is unsupported by the application and that is supported by the service model component, and wherein the key performance indicator is returned to the application via a communications protocol that is supported by the application.