RAN Parser Identity Correlation Across Vendors and Wireless Technologies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing RAN parsers are vendor and technology-specific, making them inflexible and requiring centralized deployment, which hinders real-time data processing and correlation of user identities across different mobile network technologies.
Innovation Solution
A Cloud Native Parser that converts input data into a vendor-agnostic format, enabling real-time correlation and encryption of user identities across multiple technologies, allowing deployment at the edge or central locations, and utilizing a REST API for in-memory storage management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RAN parsers are vendor and technology-specific, then they can be simpler in design, but they become inflexible and require centralized deployment which reduces adaptability
Solution Approach 1:
The parser is divided into modular components: a vendor-specific message reader layer that handles format conversion, and a vendor-agnostic procedural data record generator layer that processes standardized data. This segmentation allows the system to maintain simplicity in each layer while achieving overall vendor-agnostic capability through the interface between layers.
Solution Approach 2:
A standardized intermediate data structure is introduced between vendor-specific input formats and the procedural data record generation logic. This intermediary layer translates various vendor formats into a common representation, enabling the core processing logic to remain vendor-agnostic without directly handling multiple format complexities.
2Speed
If RAN parsers require centralized deployment, then data processing can be more controlled, but real-time data processing and correlation capabilities are reduced
Solution Approach 1:
The centralized parser architecture is segmented into independent, deployable units that can be distributed to edge locations. Each unit maintains the complete vendor-agnostic processing capability, allowing real-time processing at the edge while the system as a whole provides centralized control through standardized data collection and correlation interfaces.
Solution Approach 2:
The parser design implements universal processing logic that can function independently at distributed edge locations or be coordinated centrally. The same vendor-agnostic procedural data record generation logic serves both distributed real-time processing needs and centralized data correlation requirements, enabling flexible deployment configurations.
3Loss of information
If user identity correlation is performed across multiple vendor technologies, then data correlation capability is improved, but computational complexity increases
Solution Approach 1:
User identity information is extracted and correlated at the procedural data record generation stage, before detailed processing occurs. The parser identifies and extracts relevant identity correlators from vendor-specific messages, then uses these extracted elements for correlation across technologies, reducing the computational burden of comparing complete datasets from multiple vendors.
Solution Approach 2:
The system transforms vendor-specific identity parameters into standardized parameter representations during the format conversion phase. By changing the parameter representation to a common format early in the processing pipeline, the correlation operation becomes simpler and more efficient, as it operates on standardized rather than vendor-specific parameter structures.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method (100) includes receiving (102) data from (i) a data stream from one or more sources or (ii) one or more files, wherein the one or more sources and the one or more files are from systems associated with a mobile network; analyzing (104) and summarizing relevant information from the data stream, wherein the relevant information includes data associated with user identities; transforming (106) the relevant information includes into a common output format, wherein the common output format is a same format for one or more vendor's equipment and one or more wireless technologies; and storing (108) the relevant information in in-memory storage.