UDM Node Subscription Request Management for 5G UDR Overload
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Standalone 5G networks face over-accumulation of subscription requests in the user data repository (UDR), leading to potential session breakdowns, dropped calls, and network outages due to the lack of mechanisms to manage stale entries.
Innovation Solution
Implementing a computer-implemented method and system at the user data management (UDM) node to regulate subscription requests by receiving new requests, retrieving subscriber profiles, and determining the number of preexisting requests; if exceeding a predetermined value, deleting old requests to make space for new ones, thereby preventing memory overload.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network nodes continuously send subscription requests to the UDM for status change notifications, then the network can maintain active session monitoring and service delivery, but the UDR database experiences over-accumulation of stale subscription requests leading to memory overload and network outages
Solution Approach 1:
The patent changes the state of subscription requests by introducing expiry timestamps and validity periods. The UDM node automatically manages the lifecycle of subscription requests by setting expiry times and actively removing stale entries, transforming the static accumulation problem into a dynamic management process where requests have defined validity periods and are systematically cleaned up before causing overload
Solution Approach 2:
The patent implements a feedback mechanism where the UDM node actively monitors the number of subscription requests per subscriber profile and compares it against threshold values. When thresholds are approached, the system triggers automated removal of stale requests, creating a closed-loop control system that prevents over-accumulation while maintaining reliable session monitoring
2Loss of information
If the UDR database stores all subscription requests without removal, then complete session history is maintained, but the database becomes vulnerable to overload situations causing session breakdowns and dropped calls
Solution Approach 1:
The patent transforms subscription requests from permanent records to temporary entries with defined validity periods. By introducing expiry timestamps and active management of request lifecycles, the system maintains session history only for the necessary duration, automatically removing stale entries to prevent database overload while preserving information during active sessions
Solution Approach 2:
The patent implements periodic cleanup operations where the UDM node actively removes expired subscription requests at defined intervals. This periodic action maintains the database in a healthy state by systematically eliminating stale entries before they cause overload, ensuring continuous reliable operation while preserving session history during its valid period
3Quantity of substance
If mass delete operations are initiated to clear accumulated subscription requests, then the UDR database is relieved of overload, but network outages and cascading service failures occur
Solution Approach 1:
The patent replaces mass delete operations with periodic, incremental cleanup of expired requests. By systematically removing stale entries in regular intervals rather than performing bulk deletions, the system gradually reduces the subscription request count while maintaining database stability and avoiding the harmful cascading effects of sudden mass deletions
Solution Approach 2:
The patent implements preliminary removal of expired subscription requests before they can accumulate to dangerous levels. By proactively managing and removing stale entries on an ongoing basis, the system prevents the buildup that would necessitate emergency mass delete operations, thereby maintaining continuous network service without outages
Data Source
AI summary
A computer-implemented method for protecting a user data repository (UDR) from over-accumulation of subscription requests in a subscriber profile of a subscriber of a 5G network may include receiving, from a network node on the 5G network, a new subscription request requesting a notification of status changes associated with the subscriber profile, retrieving the subscription profile from the UDR, and determining a number of preexisting subscription requests associated with a network function (NF) instance identification (ID) of the network node in the subscriber profile. If the number of preexisting subscription requests in the subscriber profile is equal to or greater than a predetermined value (X), the computer-implemented method may further include deleting at least one of the preexisting subscription requests from the subscriber profile and writing the new subscription request to the subscriber profile at the UDR.