Network Services Hub for Cross-System Subscriber Query Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large network providers face inefficiencies in accessing and coordinating information across multiple systems, leading to a difficult and time-consuming process for managing network services and subscriber data.
Innovation Solution
The Network Services Manager (NSM) provides a centralized hub for accessing and integrating network data from various systems, offering a graphical user interface and application programming interface to streamline data retrieval and management, enabling efficient access to subscriber information across different systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple separate systems are used to manage different network functions, then system specialization and functional clarity are improved, but access complexity and time to retrieve subscriber information increase
Solution Approach 1:
The patent introduces a Network Services Manager as an intermediary system that sits between user applications and multiple network subsystems. This manager receives subscriber identifier queries, automatically determines which systems to access based on the identifier type, retrieves information from the appropriate systems, and consolidates results. This mediator approach maintains the benefits of specialized systems while eliminating the time loss from manual system navigation.
Solution Approach 2:
The Network Services Manager is designed as a universal access point that can handle multiple types of subscriber identifiers (phone numbers, email addresses, usernames) and route them to appropriate specialized systems. This multi-functional interface consolidates access to numerous specialized systems into a single universal entry point, reducing access complexity while maintaining system specialization.
2Loss of information
If multiple external systems are queried to gather complete subscriber information, then information comprehensiveness is improved, but query complexity and processing time increase
Solution Approach 1:
The Network Services Manager performs preliminary actions by pre-establishing knowledge of which systems store which types of information and what identifier formats each system accepts. When a query arrives, this pre-planned routing logic immediately directs the request to the correct systems without requiring complex real-time decision-making. This preliminary organization of access paths reduces query complexity while ensuring comprehensive information retrieval.
Solution Approach 2:
The patent segments the information retrieval process into distinct stages: identifier validation, system selection, parallel query execution, and result consolidation. Each stage handles a specific aspect of the complex query process, breaking down the overall complexity into manageable segments. This segmentation allows the system to query multiple external systems comprehensively while maintaining organized, tractable processing.
3Reliability
If manual processes are used to access different systems for subscriber information, then system autonomy and security are improved, but operational efficiency and customer service quality deteriorate
Solution Approach 1:
The Network Services Manager implements self-service by automatically performing system selection, query formulation, and information consolidation without requiring manual intervention. The system autonomously determines which external systems to query based on the subscriber identifier provided, executes the queries, and aggregates results. This automation maintains system autonomy and security boundaries while dramatically improving operational efficiency and customer service responsiveness.
Data Source
AI summary
A computer-implemented method for managing network services for a cellular network provider including receiving a user selection of an identifier type and a query input of a first subscriber identifier associated with a subscriber. Based on the user selection of the identifier type, querying IAM using the first subscriber identifier. In response to querying the IAM, receiving a first set of subscriber information associated with the subscriber, where the first set of subscriber information includes a second subscriber identifier associated with the subscriber. In response to receiving the second subscriber identifier, querying a first additional system using the second subscriber identifier. In response to querying the first additional system using the second subscriber identifier, receiving a second set of subscriber information associated with the subscriber, and populating one or more fields of the GUI with the first and second set of subscriber information.