Localized UDR Sub-Segmentation for Scalable 5G Subscriber Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional unified data repositories (UDRs) in wireless communication networks rely on a single database, creating a single point of failure and are strained by the increasing number of 5G subscribers, leading to storage capacity issues and challenges in providing market-based promotions and managing network outages.
Innovation Solution
Segment and sub-segment the UDR into multiple segments and subsegments based on geographic regions, reducing connection requirements and enabling targeted market-based solutions with improved resilience and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single monolithic UDR database is used to store all subscriber profiles, then data retrieval is straightforward, but the system creates a single point of failure and cannot scale to handle increasing 5G subscriber loads
Solution Approach 1:
The UDR database is segmented into multiple independent database segments (DB1, DB2, DB3, etc.), each storing a portion of subscriber profiles. This segmentation eliminates the single point of failure by distributing data across multiple repositories, while each segment maintains standard database structures for straightforward retrieval operations.
2Quantity of substance
If a single UDR database stores the entire subscription base, then storage capacity is consolidated, but the system becomes strained by increasing 5G subscriber numbers and cannot provide localized market-based solutions
Solution Approach 1:
Each database segment is assigned to specific geographic regions or market areas, enabling localized subscriber profile storage. This allows the system to provide market-based promotions and tailored services by accessing profiles from the appropriate regional database segment, while collectively handling large-scale subscriber storage across all segments.
Solution Approach 2:
The system adds a geographic/market dimension to the database architecture by organizing database segments along regional lines. This dimensional organization enables simultaneous achievement of large-scale storage capacity and localized market adaptability, as the routing function can direct requests to the appropriate regional segment.
3Ease of operation
If a monolithic UDR is used, then connection management is simple, but the system cannot minimize the impact of network traffic or provide resilient operation during outages
Solution Approach 1:
The database is divided into multiple independent segments that can operate autonomously during network outages. If one segment becomes inaccessible, the routing function can redirect requests to other segments, providing outage resilience while maintaining relatively simple connection management through centralized routing control.
4Productivity
If all subscriber profiles are stored in one UDR database, then data access is centralized, but the system creates heavy reliance on a single data repository
Solution Approach 1:
Subscriber profiles are distributed across multiple database segments, eliminating the single point of failure. The routing function maintains efficient data access by intelligently directing requests to the appropriate segment, achieving both distributed reliability and centralized access efficiency.
Data Source
AI summary
Systems, methods, and devices are disclosed herein for sub-segmenting UDR segments in a 4G or 5G core network. Sub-segmentation of the UDR supports faster call flows, resource distribution flexibility, and regional promotion deployment. A wireless communication network in accordance with the present disclosure includes a UDR made up of two or more database segments, a lookup database that stores information indicating where each subscriber profile is stored, and at least one routing function. Each database segment of the UDR is further segmented into two or more subsegments. The at least one routing function is configured to receive requests for subscriber information, obtain the subscriber information from the UDR segment and subsegment identified by the lookup database, and respond to the request with the subscriber information.