UE Context Reporting for Near-RT RIC in Split RAN
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current O-RAN systems struggle to effectively trigger RAN nodes to report UE context information when new UEs associate or when UE context information changes, particularly in split architectures where CU and DU are separated.
Innovation Solution
Implement context logic circuitry to enhance E2 Service Model (E2SM) REPORT and QUERY services, enabling near-RT RIC to trigger RAN nodes to report UE context information, including mechanisms for split architectures, using event triggers and query services to capture UE context changes and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If E2SM REPORT and QUERY services are enhanced to trigger RAN nodes to report UE context information, then the near-RT RIC can efficiently retrieve and maintain UE context information, but the device complexity and system architecture complexity increase
Solution Approach 1:
The patent segments the RAN node into separate CU (Central Unit) and DU (Distributed Unit) components in split architectures. The context logic circuitry is specifically implemented in the CU to handle E2SM REPORT and QUERY services, while the DU focuses on radio access functions. This segmentation allows the complex context management functionality to be isolated in the CU without complicating the DU architecture.
Solution Approach 2:
The patent introduces an E2 interface as an intermediary between the near-RT RIC and RAN nodes (CU/DU). This standardized interface mediates the communication for UE context information retrieval, providing a clean separation between the intelligence controller (RIC) and the radio access network elements. The E2 interface handles the complexity of context management protocols, shielding the underlying CU/DU architecture from direct interaction with the RIC.
2Loss of time
If event triggers and query services are implemented to capture UE context changes and updates, then the timeliness of UE context information is improved, but the processing overhead and system resource consumption increase
Solution Approach 1:
The patent implements event-triggered reporting mechanisms where the CU monitors for specific events (UE context changes, updates, or modifications) and triggers E2SM REPORT messages only when such events occur. This event-driven approach replaces continuous periodic reporting, reducing processing overhead while maintaining timely information updates. The context logic circuitry in the CU efficiently detects and responds to relevant events without unnecessary continuous communication.
3Adaptability or versatility
If the system supports both traditional architectures and split architectures (CU and DU separated), then the adaptability and versatility of the system is improved, but the device complexity and configuration complexity increase
Solution Approach 1:
The patent designs the context logic circuitry with universal functionality that can operate in multiple architectural configurations. The same context management mechanisms (E2SM REPORT, E2SM QUERY, event triggers) function effectively whether the RAN node is a traditional integrated architecture or a split CU-DU architecture. The context logic in the CU handles both cases uniformly, allowing the system to adapt to different deployment scenarios without requiring separate implementation paths.
Data Source
AI summary
Logic may determine user equipment (UE) context information associated with a UE, the UE context information comprising new information related to establishment of a new connection with the UE or related to an update of the UE context information for an existing connection with the UE. Logic may identify an event trigger associated with new information. And logic may respond to a query from the near-RT RIC for UE context information associated with the UE, wherein the UE supports a non-grid of beams mode for beamforming.