Network Data Ingestion Channels for Real-Time Configuration Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data ingestion mechanisms for managing configuration data in wireless networks are inefficient, consuming high resources and requiring large storage space, with a need for improved mechanisms to process and manage huge volumes of data in near real-time.

Innovation Solution

A method and system for data ingestion that categorizes and channels configuration data based on pre-defined data types and attributes, such as telecommunication circles, locations, and network nodes, allowing for real-time processing and optimized storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If current data ingestion mechanisms are used to manage configuration data, then data can be stored and processed, but processing speed is slow and resource consumption is high

Engineering Contradiction:
Improvedata processing speedVSAvoidresource consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent segments the monolithic data ingestion process into multiple specialized modules: data reception module, data categorization module, channel determination module, and data pushing module. Each module handles specific aspects of data processing independently, improving overall processing speed while reducing resource consumption through specialized optimization of each segment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the operational parameters by implementing channel-based data routing where data is categorized by type (configuration data, performance data, fault data, etc.) and routed through different channels. This parameter change from unified processing to channelized processing enables parallel processing paths, significantly improving throughput and reducing resource bottlenecks.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If huge volumes of configuration data are stored, then comprehensive data management is achieved, but storage space requirements increase significantly

Engineering Contradiction:
Improvedata management completenessVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent extracts only the essential and changed configuration data for storage and processing, rather than storing all raw data volumes. The data categorization module identifies and extracts relevant configuration parameters, and the system pushes only changed data through specific channels, reducing storage requirements while maintaining complete data management capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary data categorization and filtering before storage, organizing data into structured channels based on data type and attributes. This preliminary action creates an optimized storage structure where data is pre-organized by category (configuration, performance, fault data) and attributes (telecommunication circle, location, network node), reducing redundant storage and improving retrieval efficiency.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If data is processed in real-time, then near real-time management is achieved, but computational capacity requirements increase

Engineering Contradiction:
Improvedata management time delayVSAvoidcomputational capacity
Core Design Contradiction:
Loss of timeVSPower

Solution Approach 1:

The patent segments real-time data processing into parallel channel-based streams, where each data type (configuration, performance, fault) is processed independently through dedicated channels. This segmentation enables simultaneous processing of multiple data streams without requiring peak computational capacity for all data simultaneously, reducing overall power requirements while maintaining real-time processing capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the processing approach by implementing event-driven processing where only changed data triggers processing actions. The system monitors for data changes and processes only when necessary, rather than continuously processing all data. This parameter change from continuous processing to event-triggered processing significantly reduces computational capacity requirements while maintaining near real-time responsiveness.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If configuration data is categorized and channelized, then data processing efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedata processing efficiencyVSAvoidsystem structural complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal channel determination module that handles multiple data types and categories through a single integrated system. The module uses standardized attributes (telecommunication circle, location, network node) to route various data types through appropriate channels, providing multi-functional capability without requiring separate processing systems for each data type. This universality improves processing efficiency while controlling system complexity through consolidation.

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

Data Source

PatentUS20260012814A1System and method for data ingestion in a network
Publication Date: 2026.01.08 JIO PLATFORMS LTD
  • US20260012814A1 patent drawing
  • US20260012814A1 patent drawing
  • US20260012814A1 patent drawing

AI summary

A method for data ingestion for utilization and consumption of data in network nodes is disclosed. The method includes receiving data associated with a network node, categorizing the received data based on one or more pre-defined data types, storing the categorized data in a database module (304). The method reserves at least one channel for the stored data. The at least one channel is reserved based on a pre-defined data type and a plurality of attributes associated with the network node. The method determines if there is a changed configuration data associated with the stored data at the network node. Responsive to determining that there is the changed configuration data, determining the at least one reserved channel for the changed configuration data based on the pre-defined data type and the plurality of attributes associated with the network node and pushing the changed configuration data over the determined reserved channel.