Per-Enterprise Subscriber Data Management in Multi-Tenant Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing subscriber data for multiple enterprise entities in a multi-tenant network environment is complex and costly due to the need for efficient resource allocation and data isolation, especially in 5GaaS offerings, where pre-deployment of subscriber data management (SDM) functionality is often based on market forecasts and requires effective multi-tenancy considerations.
Innovation Solution
A multi-tenant cloud-hosted mobility service with a subscriber data management (SDM) system that allows enterprises to select where subscriber data is stored through GUIs and APIs, enabling the deployment of specific SDM services and on-premise solutions based on enterprise preferences, ensuring data separation and cost-effective operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If subscriber data management functionality is pre-deployed based on market forecasts, then service readiness is improved, but resource allocation efficiency deteriorates
Solution Approach 1:
The system enables dynamic provisioning of SDM services where enterprises can select and deploy services on-demand based on actual needs rather than pre-deployment. The service deployment is dynamically adjusted according to enterprise preferences and data storage requirements, allowing the system to adapt to changing demands without wasting resources on forecast-based pre-provisioning.
Solution Approach 2:
Enterprises are empowered to self-select and self-deploy appropriate SDM services through GUIs and APIs. The system allows enterprises to autonomously determine where subscriber data is stored and which service model to use, eliminating the need for operator-based pre-deployment decisions and improving both service readiness and resource efficiency.
2Productivity
If multiple enterprise entities share a multi-tenant network environment, then operational costs are reduced, but data isolation requirements increase complexity
Solution Approach 1:
The system segments data isolation requirements by implementing enterprise-specific virtualization within the shared multi-tenant environment. Each enterprise entity receives logically isolated SDM services that maintain data separation through virtualization techniques, allowing cost-effective sharing of physical infrastructure while preserving strict data isolation boundaries through software-based segmentation.
Solution Approach 2:
The patent introduces an intermediary layer that manages data isolation between multiple enterprise entities in the shared environment. This intermediary mechanism handles the complexity of data separation transparently, allowing enterprises to share infrastructure costs while the intermediary ensures proper data isolation without requiring each enterprise to implement complex isolation mechanisms independently.
3Adaptability or versatility
If enterprises have choice in selecting SDM service types and storage locations, then service adaptability is improved, but system complexity increases
Solution Approach 1:
The system implements a universal SDM service framework that can accommodate multiple service types and storage locations through a common architecture. The multi-tenant platform provides unified interfaces and standardized service models that work across different deployment scenarios, allowing enterprises to select from various configurations without increasing overall system complexity through standardization and multi-functionality.
Solution Approach 2:
The system uses service templates and configuration copying mechanisms that allow enterprises to select and replicate proven SDM service configurations. Rather than requiring custom configuration for each enterprise, the system provides pre-defined service models that can be copied and adapted, reducing the complexity burden of providing extensive service customization options.
Data Source
AI summary
Provided herein are techniques to provide per-enterprise subscriber data management (SDM) in multi-tenant network environment. In one instance, a method may include obtaining, by an SDM system, input information indicating SDM services requested for an enterprise entity in which the input information includes a multi-tenancy service attribute for the enterprise entity and indicates whether subscriber data for is to be provided on-premise for the enterprise entity. The method may further include identifying a particular SDM service of the SDM system for storing the subscriber data, deploying the particular SDM service via the SDM system, and deploying one or more on-premise SDM services at each of one or more on-premise locations of the enterprise entity for storing the subscriber data based on determining that the subscriber data is to be provided on-premise for the enterprise entity.