Observability Framework for RAN Telemetry Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current radio access networks (RANs) face challenges in efficiently monitoring, collecting, and storing data to ensure proper operation, especially as networks grow in size, leading to inefficiencies in error detection and mitigation, which can impact user experience and resource utilization.
Innovation Solution
Implementing an observability framework (OBF) that automatically identifies and routes telemetry data from RAN nodes to appropriate storage based on severity, allowing critical messages to be immediately processed while less critical messages are analyzed and stored separately, enabling faster error detection and mitigation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all telemetry data is processed and stored with equal priority, then data completeness is maintained, but processing latency increases and critical errors are delayed
Solution Approach 1:
The patent applies local quality by differentiating processing priorities based on data characteristics. Critical telemetry data (indicating errors or anomalies) is routed to high-priority queues for immediate processing, while non-critical data is placed in low-priority queues. This selective quality assignment ensures that error detection capability is improved without unnecessary delay, as only relevant data receives urgent attention.
Solution Approach 2:
The patent introduces an intermediary component (the observability framework with priority queues) that mediates between data generation and storage. This intermediary analyzes incoming telemetry data, determines its priority level, and routes it to appropriate queues. This mediation mechanism resolves the contradiction by filtering and prioritizing data flow, ensuring critical errors are detected promptly while maintaining overall system reliability.
2Speed
If telemetry data is immediately processed and stored, then error detection speed is improved, but system resource consumption increases
Solution Approach 1:
The patent applies local quality by assigning different processing speeds and resource allocations to different data types. Critical data in high-priority queues receives immediate processing with higher resource allocation, while non-critical data in low-priority queues is processed at lower speeds with reduced resource consumption. This localized quality differentiation achieves fast error detection when needed without sustaining high resource consumption across all data processing operations.
Solution Approach 2:
The patent implements dynamics by making resource allocation adaptive rather than static. The system dynamically adjusts processing speed and resource consumption based on data priority and current system conditions. When critical errors are detected, resources are concentrated on those specific data streams for rapid processing. During normal operation, resource consumption is reduced by processing non-critical data at lower priorities, thus achieving fast error detection speed without continuously high resource consumption.
3Ease of operation
If data is stored in a single centralized location, then data management is simplified, but observability and access efficiency decrease
Solution Approach 1:
The patent applies segmentation by dividing the centralized storage into multiple priority-based queues (high-priority and low-priority queues). Each queue is managed independently with its own processing pipeline and access patterns. This segmentation maintains operational simplicity through standardized queue management interfaces while dramatically improving access efficiency, as critical data can be rapidly accessed from high-priority queues without being blocked by volume of non-critical data in lower queues.
Solution Approach 2:
The patent introduces an intermediary layer (the observability framework) that manages the segmented data structures. This intermediary provides a unified interface for data ingestion and management, maintaining ease of operation, while simultaneously enabling efficient access to specific data types through priority-based routing. The intermediary translates simple management operations into optimized access patterns across segmented storage, resolving the contradiction between management simplicity and access efficiency.
Data Source
AI summary
Data acquired from at least one source is provided for observability on a cloud network. The data is placed in a common language for observability on the network so that data can be targeted based on a telemetry characteristic. Data having a first telemetry characteristic is acquired and routed to a destination for observability, whereas data having a second telemetry characteristic may be routed to another destination to be stored for observability.


