Tracking Deregistration Causes in Wireless Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication networks lack efficient mechanisms to track and manage the deregistration of user devices, leading to suboptimal network operations and difficulty in identifying and troubleshooting issues related to device deregistration.
Innovation Solution
The implementation of a system where a first network element determines the cause of user device deregistration and generates a notification message, which is communicated to a second network element. This second element purges subscriber data from a data repository and updates the subscriber profile with the cause of deregistration, using specific cause codes and attributes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the network purges subscriber data upon deregistration, then network resources are released efficiently, but the ability to track and analyze deregistration causes is lost
Solution Approach 1:
The system performs preliminary action by capturing and storing deregistration cause information in the subscriber profile before the subscriber data is purged from the data repository. This ensures that the cause information is preserved even after the actual subscriber data is removed, allowing both efficient resource release and ongoing tracking of deregistration reasons.
Solution Approach 2:
The subscriber profile acts as an intermediary storage mechanism between the data repository and the network management system. It temporarily holds the deregistration cause information, allowing the system to purge subscriber data from the repository while maintaining the ability to track and analyze deregistration causes through the profile.
2Loss of information
If the network maintains detailed subscriber data for tracking purposes, then deregistration analysis is improved, but network storage requirements increase
Solution Approach 1:
The system extracts only the essential deregistration cause information from the complete subscriber data and stores it separately in the subscriber profile. This extraction approach maintains tracking capability while minimizing storage requirements, as only critical cause codes and attributes are retained rather than all subscriber data.
Solution Approach 2:
The system applies local quality by storing different types of information in different locations: complete subscriber data is stored in the data repository, while only the critical deregistration cause information is stored in the subscriber profile. This differentiated storage approach optimizes both tracking capability and storage efficiency.
3Reliability
If the network implements comprehensive deregistration tracking, then network operation optimization is enabled, but system complexity increases
Solution Approach 1:
The subscriber profile serves multiple functions: it stores standard subscriber information, maintains deregistration cause information, and enables both immediate tracking and historical analysis. This multi-functionality reduces system complexity by using an existing structure for multiple purposes rather than creating separate specialized systems.
Solution Approach 2:
The system implements tracking through parameter changes in the subscriber profile, specifically adding cause code and cause attribute fields. This approach maintains reliability by using structured data that can be analyzed, while managing complexity through simple field additions rather than complex new systems.
Data Source
AI summary
Technology is disclosed herein for operating a wireless network including deregistering a user device from the network. In an implementation, a first network element deregisters the user device from the wireless network. The first network element determines a cause of the deregistration from among a plurality of possible causes and generates a notification message indicating the cause of the deregistration. The first network element communicates the notification message to a second network element which purges subscriber data from a data repository of the network and updates a subscriber profile of the user device with the cause of the deregistration. In an implementation, the first network element is an Access and Mobility Management function (AMF), the second network element is a Unified Data Management function (UDM), and the data repository is a Unified Data Repository (UDR) of the network.