O-RAN SMO Communication Through EMS Subscriptions and rApp Callbacks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current Service Management and Orchestration (SMO) framework in Open Radio Access Network (O-RAN) does not clearly define how the Element Management System (EMS) provides information to the Non-real time RAN Intelligent Controller (Non-RT RIC), leading to an incomplete SMO framework.
Innovation Solution
A method and system for communication in service management and orchestration that defines the operation process between the EMS and the Non-RT RIC, involving message exchanges and registration procedures to facilitate data transmission and interaction between the EMS and Non-RT RIC applications (rApps) through defined interfaces and protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the SMO framework adopts an open architecture with multiple vendors and disaggregated components, then supply chain diversity and network flexibility are improved, but system complexity and integration difficulty increase
Solution Approach 1:
The SMO framework acts as an intermediary layer between the EMS and Non-RT RIC, standardizing their interactions through defined interfaces and message formats. This mediator approach allows diverse vendor components to integrate seamlessly by translating between different implementations while maintaining a consistent abstraction layer, thus resolving the integration complexity issue while preserving supply chain diversity
Solution Approach 2:
The framework segments the SMO functionality into distinct modular components (EMS, Non-RT RIC, rApps) with clearly defined boundaries and interfaces. Each component can be independently developed, deployed, and managed by different vendors, reducing overall system complexity while enabling supply chain diversity through selective component integration
2Reliability
If the SMO framework defines detailed communication protocols between EMS and Non-RT RIC, then communication reliability is improved, but implementation complexity increases
Solution Approach 1:
The framework establishes homogeneous communication standards with unified message formats, standardized interface definitions, and consistent interaction patterns between EMS and Non-RT RIC. This homogeneity ensures reliable communication across different vendor implementations while reducing implementation complexity through reusable templates and standardized procedures
Solution Approach 2:
The communication framework employs universal message structures and standardized protocols that can handle multiple types of interactions (subscriptions, callbacks, data exchanges) through a single unified interface design. This multi-functionality approach improves communication reliability for all interaction types while reducing implementation complexity by avoiding the need for separate specialized protocols
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for communication in service management and orchestration is provided. The method includes receiving, by a Non-real time radio access network (RAN) Intelligent Controller (Non-RT RIC) framework, a first subscription message from an Element Management System (EMS), wherein the first subscription message is used to request second data used to run a Non-RT RIC application (rApp). The method includes transmitting, by the Non-RT RIC framework, a first callback message to the rApp according to the first subscription message to notify the rApp that the EMS requests the second data. The method includes transmitting, by the rApp, the second data to the EMS according to the first callback message