UDM Subscriber Data Synchronization with Change-Only Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face inefficiencies in managing and synchronizing subscriber data and events across different wireless networks, leading to unnecessary resource consumption and data transmission, particularly due to the lack of awareness of changes in subscriber identifiers and equipment identifiers.
Innovation Solution
Implementing a UDM device that stores subscriber data persistently and subscribes to receive data changes from HSS, allowing it to report only when actual changes occur, thereby reducing unnecessary data transmission and conserving computing resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UDM device receives data for every monitoring event occurrence, then complete subscriber data synchronization is achieved, but unnecessary data transmission and processing occurs consuming computing resources
Solution Approach 1:
The UDM device stores subscriber data locally in advance and maintains an understanding of what data has been received. When monitoring events occur, the UDM compares incoming data with stored data to determine if actual changes occurred, thereby avoiding processing unchanged data transmissions.
Solution Approach 2:
The UDM device implements a feedback mechanism where it tracks which subscriber data has been received and compares it with new incoming data. This feedback loop enables the system to identify when data has actually changed and only then trigger processing and notification, eliminating unnecessary resource consumption.
2Quantity of substance
If the UDM device stores data temporarily rather than persistently, then memory usage is reduced, but data cannot be retained across network handoffs and monitoring events
Solution Approach 1:
The UDM device performs preliminary storage of subscriber data in a persistent manner before network handoffs or monitoring events occur. This advance storage ensures that data is available and can be compared with new incoming data to determine if changes occurred, enabling reliable data retention across network events.
3Reliability
If the HSS synchronizes data with the UDM for all subscribers, then complete data synchronization is achieved, but the HSS cannot efficiently determine if data has changed without storing all subscriber data
Solution Approach 1:
The UDM device stores subscriber data locally in advance, creating a baseline understanding of which data has been received. When the HSS attempts to synchronize data, the UDM can quickly determine based on its stored data whether actual changes occurred, eliminating the need for the HSS to store all subscriber data and simplifying the data management process.
Data Source
AI summary
In some implementations, a network device may store first data associated with a monitoring event, wherein the first data is associated with a subscriber and is stored as persistent data in a memory associated with the network device. The network device may receive second data associated with an occurrence of the monitoring event. The network device may determine that the second data indicates a change to the first data. The network device may provide the second data to a network exposure function (NEF) based on the second data indicating the change to the first data, wherein the second data is not provided to the NEF when the second data does not indicate the change to the first data.