Stateless and Stateful Data Store for Network Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Monitoring and troubleshooting modern communication networks, particularly 4G and 5G networks, is challenging due to their complexity and the incessant exchange of high-speed data, which demands real-time performance maintenance for quality of service and user experience.
Innovation Solution
A storage architecture comprising a stateless and stateful data store, with a new generation node (NG-node) that extracts and processes protocol data units (PDUs) to generate stateless and stateful records, utilizing identifier indices to efficiently store and retrieve data, enabling effective monitoring and troubleshooting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a traditional single-type data store is used for network monitoring, then the storage structure is simple, but the data processing efficiency and retrieval speed deteriorate due to the need to handle both stateless and stateful data
Solution Approach 1:
The storage architecture is segmented into two distinct stores: a stateless data store for stateless records and a stateful data store for stateful records. This segmentation allows each store to be optimized for its specific data type, improving processing efficiency while maintaining manageable complexity through clear functional separation.
Solution Approach 2:
Each data store is designed with local quality optimizations specific to its data type. The stateless data store uses structures optimized for stateless record retrieval, while the stateful data store uses structures optimized for stateful record management with identifier indices, allowing each component to operate at peak efficiency for its specific function.
2Loss of time
If all data is stored in a single data store, then the storage system is simple, but the query complexity and data retrieval time increase due to the need to search through mixed data types
Solution Approach 1:
The data store is segmented into stateless and stateful sections, allowing queries to be directed to the appropriate section based on data type. This reduces retrieval time by eliminating unnecessary searches through mixed data types while maintaining a manageable structure through clear segmentation.
Solution Approach 2:
The NG-node acts as an intermediary that classifies incoming data as stateless or stateful and routes it to the appropriate data store. This intermediary function simplifies query processing by pre-sorting data before storage, reducing the complexity of subsequent retrieval operations.
3Measurement precision
If stateful data is stored without efficient indexing, then the storage structure is simple, but the query performance deteriorates when searching for specific identifier indices
Solution Approach 1:
Identifier indices are created as part of the stateful data store structure in advance, enabling fast queries for specific identifier indices. This preliminary structuring of data with indexed fields allows for rapid retrieval without requiring complex search operations during query processing.
Solution Approach 2:
The data store uses different indexing parameters for stateful data compared to stateless data. Stateful data employs identifier index-based retrieval mechanisms that change the query parameter from full-data-search to index-based-lookup, significantly improving query processing speed for specific identifier searches.
Data Source
AI summary
A data store configured to store data generated by activity of network elements (NEs) of a communications network, the data store comprising: a stateless Base-index data store configured to store stateless Base-index records, each stateless Base-index record comprising a copy of at least a portion of data comprised in a protocol data unit (PDU) generated by an NE and a stateless Base-index vector comprising a value for at least one intrinsic Base-index from a selection of intrinsic Base indices, which value may be used to associate the PDU with a temporary feature of the network; and a stateful identifier index (ID-index) store configured to store stateful ID-index records, each stateful ID-index stateful record comprising an identifier index (ID-index) vector.


