5G UDR Data Synchronization via Inconsistency Indications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G core networks, data inconsistencies in the Unified Data Repository (UDR) lead to inefficiencies in data regeneration and restoration across Network Function consumers, causing excessive signaling and potential overloads, especially in massive IoT deployments, without providing clear indicators of restoration progress to operators.
Innovation Solution
A method for synchronizing data across network functions by providing an indication of potential registration data inconsistency, allowing Network Exposure Functions (NEFs) to gradually restore data based on UE activity, thereby avoiding excessive signaling and allowing operators to track restoration progress.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Network Functions regenerate and restore data in the UDR to bring back consistency, then data consistency between consumer NFs and the UDR is improved, but excessive signaling and potential overloads occur
Solution Approach 1:
The system performs preliminary actions by having the UDR proactively notify consumer NFs about potential data inconsistencies before they actually occur. This allows NFs to prepare for data regeneration in advance, rather than reacting to inconsistencies after they've caused problems, thereby reducing the need for excessive corrective signaling.
Solution Approach 2:
The patent implements a feedback mechanism where the UDR monitors its own data state and provides feedback notifications to consumer NFs when inconsistencies are detected. This feedback loop enables NFs to synchronize their local data with the UDR only when necessary, rather than continuously exchanging data, thus reducing signaling overhead while maintaining data consistency.
2Reliability
If data regeneration is performed across all consumer NFs, then data consistency is restored, but network overload and inefficiency increase
Solution Approach 1:
The patent applies local quality by enabling each consumer NF to independently determine whether it needs to perform data regeneration based on specific conditions. Instead of forcing all NFs to regenerate data uniformly, each NF assesses its own data state and regenerates only when necessary, optimizing network resources and maintaining productivity while ensuring data consistency where needed.
Solution Approach 2:
The system performs partial action by having only those consumer NFs that actually need data regeneration execute the restoration process. The UDR identifies which NFs have inconsistent data and notifies only those specific NFs, avoiding the excessive action of forcing all NFs to regenerate data, thus maintaining network efficiency while restoring consistency where required.
3Reliability
If traditional data restoration methods are used, then data consistency is achieved, but clear indicators of restoration progress are not provided to operators
Solution Approach 1:
The patent implements comprehensive feedback mechanisms that provide operators with real-time information about data restoration progress. The UDR and consumer NFs exchange notifications that include status information, allowing operators to monitor which NFs have received inconsistency notifications, which have completed regeneration, and which are still in progress, thus preventing information loss about restoration state.
Solution Approach 2:
The system introduces an intermediary role for the UDR that acts as a coordinator between consumer NFs and the network operator. The UDR collects restoration status information from NFs and provides aggregated progress indicators to operators, serving as an intermediary that translates complex distributed restoration processes into understandable progress metrics for operators.
Data Source
AI summary
Embodiments described herein relate to methods and apparatuses for synchronizing data at a second network function. A method in a first network function includes: receiving, from the second network function, an indication of potential registration data inconsistency associated with one or more wireless devices; receiving a registration request for a first wireless device from a third network function, wherein the registration request includes a first indication indicating that a reason for the registration request is potential data inconsistency; and responsive to receiving the registration request, updating the registration data at the second network function.