E2 Node Configuration Updates for Near-RT RIC Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing communication systems, particularly in the context of 6G, face challenges in efficiently managing the configuration updates of E2 nodes due to the increasing complexity and diversity of connected devices and services, necessitating improved protocols for seamless integration and management.
Innovation Solution
The proposed solution involves a method and apparatus for E2 node configuration updates through an E2 node and a Near-real-time (RT) radio access network intelligent controller (RIC) interaction, utilizing message exchanges that include interface types, component identifiers, and configuration information to facilitate dynamic and efficient updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the E2 node configuration update protocol is enhanced to support diverse 6G devices and services, then the adaptability and service capability are improved, but the protocol complexity and implementation difficulty increase
Solution Approach 1:
The configuration update message is segmented into distinct fields including component identifier, interface type, configuration data, and version information. This segmentation allows the protocol to handle diverse configuration parameters systematically without requiring a completely new protocol for each device type, thus improving adaptability while maintaining manageable complexity.
Solution Approach 2:
The E2 node configuration update protocol is designed as a universal framework that can accommodate multiple device types, interface types, and configuration scenarios through a single message structure. The protocol uses type identifiers and flexible data fields to serve diverse 6G devices and services without requiring separate specialized protocols, balancing versatility with implementation simplicity.
2Manufacturing precision
If comprehensive configuration information is exchanged between E2 node and RIC, then the configuration accuracy and completeness are improved, but the message size and processing overhead increase
Solution Approach 1:
The protocol extracts only the essential configuration fields needed for accurate E2 node configuration updates, such as component identifier, interface type, and specific configuration parameters. Non-essential or redundant information is omitted, ensuring configuration accuracy is maintained while message size is kept manageable for efficient transmission between E2 node and RIC.
3Productivity
If real-time configuration updates are implemented, then the system responsiveness and service delivery are improved, but the processing time and network load increase
Solution Approach 1:
The configuration update message includes pre-structured fields for component identifier, interface type, and version information that allow the RIC and E2 node to quickly parse and process updates without requiring complex analysis. This preliminary structuring of data enables real-time configuration updates with minimal processing time, improving service delivery speed while controlling the time loss associated with message handling.
Data Source
AI summary
The disclosure relates to a 5th generation (5G) or 6th generation (6G) communication system for supporting a higher data transmission rate than a 4th generation (4G) communication system such as long term evolution (LTE). A method performed by an E2 node is provided. The method includes receiving, by the E2 node from a Near-real time (RT) radio access network (RAN) intelligent controller (RIC), an E2 node configuration query message, transmitting, by the E2 node to the Near-RT RIC, an E2 node configuration update message, and receiving, by the E2 node from the Near-RT RIC, an E2 node configuration update acknowledge message, wherein the E2 node configuration query message includes an interface type and a component identifier corresponding to an E2 node component, wherein the E2 node configuration update message includes the interface type, the component ID, and E2 node component information corresponding to the E2 node component, and wherein the E2 node component information includes a request part of E2 node component configuration information and a response part of the E2 node component configuration information.