Subscriber Data Management via Unified Rule Engine
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing subscriber data in telecommunications networks are inefficient, particularly in handling inactive users, managing different access technologies, and providing flexible charging policies, leading to complex database usage and maintenance challenges.
Innovation Solution
A method and device that store subscriber data and rules for managing this data, allowing for processing and modification based on specific requests and parameters, such as time, application identity, and service type, to control data retention and provide flexible charging policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If subscriber data is cleaned from the register when inactive for a pre-defined period, then the load on the register is reduced, but the system becomes inefficient for different kinds of users
Solution Approach 1:
The patent applies local quality by implementing different cleaning policies for different user types. The system identifies specific user categories (e.g., prepaid vs. postpaid subscribers) and applies tailored retention periods and cleaning criteria to each group, rather than using a uniform cleaning policy for all users. This resolves the contradiction by making the cleaning process adaptable to different user needs while still reducing register load through selective data removal.
2Adaptability or versatility
If multiple stand-alone SQL/LDAP servers are provided for different access technologies, then user access information is available for each technology, but the system becomes complex and inefficient in terms of database usage
Solution Approach 1:
The patent merges multiple separate SQL/LDAP servers into a single unified server that handles multiple access technologies. The unified server maintains a single database structure that can serve different technology types (e.g., 2G, 3G, 4G) simultaneously, eliminating the need for separate servers for each technology. This reduces system complexity and improves database usage efficiency while maintaining adaptability to various access technologies through a standardized interface and unified data model.
3Adaptability or versatility
If each service application processes subscriber profile information from a centralized store, then flexible charging policies can be implemented, but the applications become complex and difficult to maintain
Solution Approach 1:
The patent introduces an intermediary component (a rule engine or policy decision point) that sits between the centralized subscriber profile store and the service applications. This intermediary processes the raw subscriber profile data and applies charging rules, transforming complex policy logic into simple, maintainable application code. The applications interact with the intermediary through standardized interfaces, gaining access to flexible charging capabilities without inheriting the complexity of policy management. This resolves the contradiction by isolating application complexity from policy complexity through the intermediary layer.
Data Source
AI summary
A method includes storing subscriber data at one or more locations, and storing, at least one of the one or more locations, one or more rules for managing the subscriber data at least one of the one or more locations. The subscriber data regarding at least one of the one or more locations is managed on the basis of the rules.