O-RAN E2 Interface Snapshot Retrieval for Near-RT RIC Data Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing subscription-based communication mechanism in Open Radio Access Networks (O-RAN) does not support instantaneous retrieval of RAN information, leading to issues with data synchronization, delayed onboarding of xAPPs, and handling rapidly varying RAN data, which are not addressed by current methods.

Innovation Solution

Implementing an information request/response procedure over the E2 interface using an E2 Service Model (E2SM) container and E2 Application Protocol (E2AP) message for Near-RT RIC to retrieve RAN information, allowing one-time snapshot retrieval and subsequent periodical updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If subscription-based communication is used over E2 interface, then periodic data synchronization is achieved, but instantaneous retrieval of RAN information is not possible

Engineering Contradiction:
Improvedata synchronizationVSAvoidtime delay in data retrieval
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the data retrieval mechanism into two independent parts: (1) subscription-based periodic synchronization for maintaining data consistency, and (2) on-demand instantaneous retrieval for immediate data access. This segmentation allows both time-delayed periodic updates and instantaneous retrieval to coexist without interfering with each other, resolving the contradiction between reliable synchronization and fast data access.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a dynamic retrieval mechanism that adapts to different data access scenarios. The system can switch between periodic subscription-based retrieval and on-demand instantaneous retrieval based on the specific needs of xAPPs. This dynamic approach allows the system to optimize between synchronization reliability and retrieval speed depending on the operational context.

Inventive Principle:
Principle #15Dynamics

2Productivity

If subscription-based communication is used, then periodic data updates are received, but one-time retrieval of current data snapshot is not facilitated

Engineering Contradiction:
Improveperiodic data update efficiencyVSAvoidone-time data retrieval capability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent makes the E2 interface universally capable by enabling it to support multiple data retrieval modes: periodic subscription-based updates for continuous synchronization and on-demand one-time retrieval for immediate access. This multi-functionality allows the same interface to serve different operational needs, including both productivity-focused periodic updates and ease-of-operation-focused one-time snapshots.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary mechanism (the information request/response procedure with E2SM container) that mediates between the E2 node and xAPPs for one-time data retrieval. This intermediary layer enables on-demand access without disrupting the existing periodic subscription-based communication, allowing both periodic updates and one-time retrieval to function simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Stability of the object's composition

If periodical data mirroring is used for rapidly varying RAN data, then data synchronization is maintained, but data synchronization may be lost due to high variability

Engineering Contradiction:
Improvedata synchronization stabilityVSAvoiddata change rate
Core Design Contradiction:
Stability of the object's compositionVSSpeed

Solution Approach 1:

The patent implements a feedback mechanism where xAPPs can detect data inconsistency between their cached data and current E2 node data, and trigger on-demand retrieval when synchronization is lost or suspected. This feedback loop allows the system to respond to rapid data changes dynamically, maintaining synchronization stability even when data varies rapidly by immediately retrieving updated data upon detection of inconsistency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent enables xAPPs to proactively retrieve data snapshots when they detect potential synchronization issues or when immediate data access is needed, rather than passively waiting for periodic updates. This preliminary action approach allows the system to anticipate and compensate for data synchronization losses caused by rapid data changes.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If subscription-based communication is used for xAPP onboarding, then continuous data updates are received, but delayed onboarding of xAPPs results in missed periodical data

Engineering Contradiction:
Improvecontinuous data updatesVSAvoidonboarding delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent enables new xAPPs to perform preliminary one-time data retrieval upon onboarding before the regular periodic update cycle begins. This allows delayed-onboarded xAPPs to immediately access current data snapshots without missing any periodic updates, effectively eliminating the time loss associated with onboarding delays while maintaining continuous data update productivity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12598543B2Systems and methods for retrieving RAN information
Publication Date: 2026.04.07 RADISYS INDIA PTE LTD
  • US12598543B2 patent drawing
  • US12598543B2 patent drawing
  • US12598543B2 patent drawing

AI summary

Present disclosure generally relates to wireless telecommunication networks, and more particularly relates to systems and methods for retrieving Radio Access Network (RAN) information over E2 interface of Open Radio Access Network (O-RAN), using information request response procedure. System determines, if Radio Access Network (RAN) information is required by Near-RT RIC, based on occurrence of non-subscription-based O-RAN use case scenarios or deployment scenarios in Near-RT RIC. Further, system builds E2 Service Model (E2SM) container with required type of information, when RAN information is required. Furthermore, system encodes built E2SM container in E2 Application Protocol (E2AP) message. Thereafter, system transmits E2AP message as RAN information request to E2 node via E2 interface associated with O-RAN. Additionally, system receives RAN information response corresponding to RAN information request, from E2 node. The RAN information response is transmitted by E2 node as E2AP response message by encoding E2SM container with requested RAN information.