UDR Synchronization via Alias Profiles for 5G Data Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increase in 5G subscribers stresses the storage capacity of Unified Data Registries (UDRs) in wireless communication networks, leading to instability and inefficiencies in data migration and fallback processes.
Innovation Solution
A method and system for synchronizing UDRs during data migration from a first UDR to a second UDR, involving the receipt of provisioning data updates, identification of subscriber profiles, and performing delta updates on alias profiles to maintain synchronization and enable seamless fallback.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If additional UDRs are instantiated to increase storage capacity, then the storage capacity of the network is improved, but the reliability of the network deteriorates due to instability of newly instantiated UDRs
Solution Approach 1:
The patent creates alias profiles in advance during the migration process. Before the actual data migration is complete, alias profiles are pre-established in the source UDR to serve as fallback options. This preliminary preparation ensures that when a new UDR becomes unstable, the system can immediately switch to the pre-configured alias profile without delay, thus resolving the contradiction between increasing storage capacity and maintaining reliability.
Solution Approach 2:
The patent implements a cushioning mechanism by maintaining alias profiles as backup copies in the source UDR. These alias profiles act as a buffer or safety net that compensates for the potential failures of newly instantiated UDRs. The alias profiles are updated in parallel with the migration process, providing continuous backup capability that prevents reliability deterioration when new UDRs become unstable.
2Quantity of substance
If subscriber profiles are migrated to new UDRs, then the storage capacity utilization is improved, but the complexity of the migration process increases
Solution Approach 1:
The patent segments the migration process into distinct phases: creating alias profiles, migrating subscriber profiles, and updating alias profiles with delta changes. This segmentation allows each phase to be managed independently and simplifies the overall complex migration process. By dividing the migration into manageable segments, the system can efficiently utilize storage capacity while reducing the complexity of coordination between multiple UDRs.
Solution Approach 2:
The patent uses alias profiles as copies of subscriber profiles stored in the source UDR. Instead of directly transferring all data repeatedly, the system creates reference copies (alias profiles) that point to the actual subscriber data. This copying mechanism simplifies the migration process by allowing multiple UDRs to access the same subscriber data without physical duplication of all profile information, thus reducing migration complexity while improving storage capacity utilization.
3Reliability
If delta updates are performed on alias profiles, then the synchronization between UDRs is improved, but the processing time increases
Solution Approach 1:
The patent implements continuous synchronization by performing delta updates on alias profiles in parallel with the ongoing data migration process. Instead of completing all migrations before updating aliases, the system continuously applies updates to both the new UDR and the alias profiles in the source UDR. This continuous action ensures synchronization is maintained throughout the migration process, improving reliability without significant time penalty since updates occur concurrently rather than sequentially.
Data Source
AI summary
Various embodiments comprise a wireless communication network to synchronize Unified Data Registries (UDRs) during data migration. In some examples, the wireless communication network comprises a provisioning orchestrator, UDR provisioning controllers, and a migration controller. The provisioning orchestrator receives an update for a subscriber profile, determines the subscriber profile has been migrated to the second UDR based on the subscriber Identifier (ID), and directs the second UDR provisioning controller to implement the provisioning data update. The second UDR provisioning controller updates the subscriber profile stored on the second UDR and triggers a synchronization update on the first UDR. The data migration controller detects the trigger and audits the first UDR to identify a subscription alias for the subscriber profile. The migration controller directs the first UDR provisioning controller to update the alias. The first UDR provisioning controller updates the alias to synchronize the first UDR with the second UDR.