IMS Home Subscriber Server Data Sharing for Non-Alias Users
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing IP multimedia subsystem (IMS) architecture is inefficient in storing data for non-alias user identities, leading to redundant data storage and increased memory usage, as well as inefficient notification and management processes due to the requirement of identical service configurations for all services among user identities.
Innovation Solution
A method is introduced to select non-alias user identities, analyze their common data sets, create a single instance of common configuration elements, and store this data in a Home Subscriber Server (HSS) as a transparent data set, reducing redundant data storage and enhancing notification efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If the HSS stores separate copies of service configuration data for each user identity, then data retrieval is straightforward, but memory usage increases and redundant data is stored
Solution Approach 1:
The patent merges service configuration data that is common across multiple user identities into a single shared repository data element. Instead of storing separate copies for each user identity, the system creates one instance of common configuration data that can be referenced by multiple user identities, thereby reducing memory usage while maintaining efficient access through the shared reference mechanism.
Solution Approach 2:
The repository data element is designed to serve multiple user identities simultaneously. A single repository data element can be shared across many user identities that have the same service configuration requirements, making the data storage structure universal and multi-functional rather than dedicated to a single user identity.
2Adaptability or versatility
If the system requires identical service configurations for all services among user identities to be considered aliases, then data can be shared efficiently, but flexibility is reduced and service customization is limited
Solution Approach 1:
The patent segments service configuration data into two distinct parts: service profile information (which defines service subscriptions) and service configuration information (which defines specific service parameters). This segmentation allows user identities to share service configuration data for common services while maintaining the ability to have different service profiles, thereby increasing flexibility without significantly increasing data management complexity.
Solution Approach 2:
The system applies different sharing rules to different types of data. Service configuration data that is common across user identities is shared in the repository, while service profile information remains specific to each user identity. This local quality approach allows flexibility in service configuration sharing while maintaining user-specific service profiles.
3Ease of operation
If the HSS stores redundant copies of data for non-alias user identities, then data access is simplified, but memory optimization is prevented and notification efficiency decreases
Solution Approach 1:
The patent introduces an intermediary mechanism where the HSS acts as a mediator between user identities and the shared repository data. When a user identity needs access to service configuration data, the HSS retrieves it from the shared repository data element rather than requiring direct access to redundant copies. This intermediary approach maintains ease of operation while eliminating redundant data storage.
4Productivity
If multiple application servers manage service data for different user identities separately, then service independence is maintained, but notification efficiency and management coordination decrease
Solution Approach 1:
The patent merges the management of common service configuration data into a single shared repository that can be accessed by multiple application servers. Instead of each application server managing separate copies of data for different user identities, they all access the same repository data element, which improves notification efficiency since updates to the shared data can be efficiently communicated to all relevant application servers.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for storing data in an IP multimedia subsystem (IMS) is disclosed. The method comprises: i) selecting a first user and a second user, which are not aliases; ii) analysing first and second data sets associated with the first and second users respectively to identify common data elements in each of the first and second data sets, the first and second datasets being useable by a first application server within the IMS to satisfy service requests on behalf of the first and second users; iii) creating a data structure containing a single instance of the identified common data elements; and iv) storing the data structure in a home subscriber server (HSS) within the IMS.