Subscriber Identity Management in Telecommunications Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy provisioning systems struggle with managing multiple identities of a subscriber across different applications, as they do not consider implications on other applications' data, potentially leading to incorrect operations such as removing shared identities.
Innovation Solution
A common subscriber database is introduced to manage subscriber identities, with features like lock-flags and timestamps to prevent incorrect operations, and a provisioning client that handles adding or removing associations between identities and applications, ensuring identities are only removed when no longer needed by any application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a common subscriber database is introduced to manage multiple identities across different applications, then the coordination and accuracy of identity management is improved, but the device complexity and operational difficulty increase
Solution Approach 1:
The system segments identity management into distinct application-specific views (HLR, HSS, AAA) while maintaining a unified underlying database structure. Each application interacts with its specific data portion through dedicated interfaces, reducing perceived complexity while ensuring coordinated management across all applications.
Solution Approach 2:
The patent introduces intermediary components including a provisioning client and database management system that mediate between external provisioning systems and the common subscriber database. These intermediaries handle the complexity of multi-application coordination, transaction management, and conflict resolution, shielding users from the underlying system complexity while ensuring reliable identity management.
2Ease of operation
If legacy provisioning systems operate independently for single applications, then the operational simplicity is maintained, but the risk of incorrect operations affecting other applications increases
Solution Approach 1:
The system implements feedback mechanisms where the database management system monitors and tracks identity associations across all applications in real-time. When a provisioning operation is requested, the system provides feedback about the current state of identity usage, preventing operations that would compromise data integrity while allowing safe operations to proceed.
Solution Approach 2:
Before executing provisioning operations, the system performs preliminary checks to verify that the operation will not negatively impact other applications. The lock-flag mechanism and timestamp validation are preliminary actions that prevent incorrect operations before they can occur, ensuring data integrity while maintaining operational simplicity for users.
3Quantity of substance
If identities are shared across multiple applications, then the resource efficiency is improved, but the difficulty of detecting and managing associations increases
Solution Approach 1:
The database management system acts as an intermediary that automatically tracks and manages identity associations across applications. It maintains internal data structures that record which identities are shared with which applications, eliminating the need for manual tracking while enabling efficient resource utilization through shared identities.
Solution Approach 2:
The system provides automated feedback about identity association states through the provisioning interface. When querying or modifying identities, the system returns information about which applications are using each identity, enabling operators to make informed decisions about resource allocation while the system handles the complex tracking automatically.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A method comprising receiving a request to change first information relating to a first identity of a subscriber in a database; obtaining information from said database relating to said first identity and at least one other identity of said subscriber; determining from the obtained information if said requested change can be made, in dependence on if said first identity is at least partially shared.