Session Binding Cleanup for Stale Wireless Network Sessions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless communication networks face inefficiencies in removing session binding data due to session stagnation, leading to stale session data accumulation that reduces the accuracy and performance of the Binding Support Function (BSF) by storing large quantities of outdated data.
Innovation Solution
A method and system for detecting stale sessions, involving a policy controller that sends a policy update request to a session controller, receives a confirmation of session termination, and directs a binding data store to delete associated session binding data, ensuring timely cleanup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the PCF stores session data for terminated sessions due to SMF failure to notify, then session data can be retained for potential future use, but the BSF accumulates large quantities of stale session bindings that reduce accuracy and performance
Solution Approach 1:
The PCF proactively initiates a binding data cleanup procedure by sending a cleanup request to the BSF before the stale session data accumulates to problematic levels. This preliminary action prevents the BSF from being overwhelmed by stale data while maintaining the ability to retain session data for legitimate future use.
Solution Approach 2:
The system implements a feedback mechanism where the PCF monitors session status and triggers cleanup operations based on session termination events. The BSF receives feedback about which bindings to remove and executes the cleanup, ensuring data accuracy is maintained through continuous monitoring and responsive action.
2Loss of information
If the BSF stores large quantities of stale session binding data, then historical session information is preserved, but computational efficiency and system performance are reduced
Solution Approach 1:
The system extracts and removes only the necessary stale binding data from the BSF while preserving useful historical session information. The cleanup procedure selectively removes bindings associated with terminated sessions that are no longer needed, rather than deleting all historical data, thus maintaining computational efficiency without losing valuable information.
Solution Approach 2:
The PCF performs preliminary identification and classification of stale bindings before the BSF executes cleanup. This preliminary action allows the system to distinguish between truly stale data that should be removed and historical data that may be useful, enabling selective removal that protects computational efficiency while preserving information.
3Reliability
If the SMF fails to notify the PCF of session termination, then session setup errors can be avoided, but stale session data accumulates and binds to the BSF
Solution Approach 1:
The PCF initiates a proactive cleanup procedure by sending a cleanup request to the BSF before the stale session data becomes problematic. This preliminary action reduces the time required for eventual cleanup operations and prevents the accumulation of excessive stale data, addressing the time loss issue while maintaining session setup reliability.
Solution Approach 2:
The system uses feedback mechanisms to monitor session status and trigger timely cleanup operations. The PCF receives feedback about session termination events and proactively initiates cleanup procedures, ensuring that stale data is removed in a timely manner without requiring continuous monitoring or intervention.
Data Source
AI summary
Various embodiments include a wireless communication network that comprises network circuitry. The network circuitry executes a policy controller, session controller, and binding data store. The policy controller detects a stale session condition for a wireless user device and transfers a policy update request to the session controller for a session associated with the user device. The policy controller receives a message from the session controller that indicates the session associated with the user device does not exist. The policy controller deletes session data for the user device in response to the message and directs the binding data store to delete session binding data associated with the user device. The binding data store receives the direction from the policy controller, deletes the session binding data, and transfers an indication that the session binding data is deleted to the policy controller. The policy controller receives the indication from the binding data store.