Shared Service Profile Management in Wireless Core Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless core networks experience unnecessary redundant service profile data transfers and storage due to the lack of shared service profile support between the Serving Mobility Management Entity (SME) and the Home Subscriber Server (HSS), leading to increased traffic and storage requirements for both initial registrations and profile updates.
Innovation Solution
Implementing a system that allows the HSS to recognize and manage shared service profiles, using a shared profile identifier to reduce redundant data transfers by enabling the MME to retrieve and store shared service profiles efficiently, thereby optimizing data management between the HSS and MME through an enhanced DIAMETER S6a interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the HSS sends complete service profile data to the MME for each user registration, then the MME can process user requests independently, but redundant data transfers and storage occur when multiple users share the same service profile
Solution Approach 1:
The service profile is segmented into two parts: a shared service profile identifier (stored in HSS) and user-specific profile data (transferred to MME). When multiple users share the same service profile, only the identifier is transferred, while the actual profile data remains in the HSS, reducing redundant data transfers and storage.
Solution Approach 2:
A shared service profile identifier acts as an intermediary between the HSS and MME. Instead of transferring complete profile data for each user, the HSS transfers only the identifier, which the MME uses to reference the actual profile data stored in the HSS, thereby reducing network traffic and storage requirements.
2Productivity
If the MME stores complete service profiles for all users, then user service requests can be processed without additional HSS queries, but storage requirements and maintenance complexity increase significantly
Solution Approach 1:
The service profile storage is segmented between HSS and MME. The HSS stores the master copy of shared service profiles, while the MME stores only user-specific profile data and references to shared profiles. This segmentation reduces MME storage requirements and simplifies profile management while maintaining processing efficiency.
Solution Approach 2:
The HSS serves multiple functions: it acts as both the authentication server and the centralized service profile repository. By maintaining the master copy of shared service profiles, the HSS can serve multiple users with identical profiles without requiring each MME to store redundant data, thereby reducing overall system complexity.
3Adaptability or versatility
If the HSS updates service profiles for all users individually, then each user's profile can be customized, but the update process becomes inefficient when multiple users share the same profile
Solution Approach 1:
Profile updates are segmented into shared profile updates and user-specific updates. When a service profile is updated, the HSS updates the master copy and automatically notifies all MMEs that reference this shared profile. This allows efficient bulk updates for shared profiles while maintaining the ability to customize user-specific data without redundant update operations.
Solution Approach 2:
The system implements a feedback mechanism where the HSS notifies MMEs of shared profile updates. When the HSS updates a shared service profile, it sends update notifications to relevant MMEs, which then update their local caches. This feedback loop ensures all users sharing the same profile receive updates efficiently without requiring individual update operations for each user.
Data Source
AI summary
Systems and method are provided to reduce redundant data transfers for service profiles within a wireless core network. A network device in the core network receives, from a mobility management entity (MME), a user profile request. The user profile request includes a user identifier for an end device. The network device determines that a user profile corresponding to the user identifier includes a shared service profile and determines, when the user profile includes a shared service profile, whether the MME has stored the shared service profile. When the MME has not stored the shared service profile, the network device sends, to the MME, the shared service profile and a shared profile identifier for the shared service profile. The network device sends, to the MME, a response to the user profile request, the response including the user identifier and the shared profile identifier for the shared service profile.