RIC Interface Messaging for Operator-Specific 5G Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing radio access networks lack the ability to support operator-specific services and service models, particularly in the context of 5G communication systems, which require differentiated service support and efficient communication protocols between network entities.
Innovation Solution
The implementation of an interface between a radio access network intelligent controller (RIC) and network nodes, including base stations, to generate, transmit, and interpret messages using operator-specific service models, enabling customized communication and control over O-DU, O-CU-CP, and O-CU-UP entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing radio access network protocols are used, then basic communication functionality is maintained, but operator-specific services and differentiated service support cannot be provided
Solution Approach 1:
The communication protocol is segmented into standard parts (for basic functionality) and operator-specific extensions (for customized services). The operator-specific service model messages are defined as separate, modular extensions that can be added to the existing protocol framework without replacing the entire protocol stack, allowing operators to customize services while maintaining compatibility with standard communication mechanisms.
Solution Approach 2:
The E2 interface and service model framework are designed to be universal, supporting both standard 3GPP services and operator-specific services through a unified message structure. The same interface infrastructure handles multiple types of services by interpreting different service model identifiers and message types, eliminating the need for separate protocol implementations for different service types.
2Adaptability or versatility
If standardized interfaces are used, then interoperability is ensured, but customized service models and operator-specific control capabilities are limited
Solution Approach 1:
The interface design applies local quality by maintaining standardized behavior for common operations while allowing operator-specific customizations in dedicated message types and service model definitions. The E2 interface uses type-specific message structures where standard messages ensure interoperability and operator-specific messages provide customization, with each message type having optimized characteristics for its specific purpose.
Solution Approach 2:
The E2 interface acts as an intermediary layer between the standardized O-RAN architecture and operator-specific service requirements. It translates operator-specific service model intentions into standardized control messages that can be processed by compliant network elements, while simultaneously allowing operators to define custom service models that extend beyond standard capabilities through a controlled extension mechanism.
3Productivity
If basic message transmission is implemented, then communication functionality is achieved, but efficient operator-specific service support and network intelligence are insufficient
Solution Approach 1:
The service model definitions, including operator-specific parameters and message structures, are pre-configured and registered in the RIC before runtime operations. This preliminary setup allows the interface to efficiently process service-specific messages during operation without requiring complex runtime interpretation or configuration, improving service delivery efficiency while managing complexity through advance preparation.
Solution Approach 2:
The message structure incorporates an additional dimension for service model identification and operator-specific parameters alongside the standard protocol fields. This dimensional extension allows messages to carry both standardized control information and operator-customized service parameters in a unified structure, enabling efficient differentiated service support without requiring separate message protocols for different service types.
Data Source
AI summary
A method in an apparatus configured to use an interface between a radio access network intelligent controller (RIC) and a node including a base station operates in a radio access network; comprises: generating first information associated with an RIC service; generating second information indicating a type of message to be used for transmitting the first information; and transmitting a message including the first information and the second information.