NF Session Timestamp Handling for Conflicting Session Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G core networks, network function (NF) components retain stale session information due to incomplete communication of session terminations, leading to conflicting session identifiers and resulting in bad requests, which conventional auditing processes fail to prevent or resolve effectively.
Innovation Solution
Implement proactive and reactive systems in NF components to identify and remove conflicting session information by using triggers such as timestamp differences or threshold times, ensuring stale entries are removed before they cause issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional auditing processes are used to remove conflicting session information, then session information is eventually cleaned up, but bad requests occur before auditing removes the stale information and the process is inefficient
Solution Approach 1:
The system performs preliminary actions by proactively detecting conflicting session information through triggers (timestamp differences, threshold times) before bad requests occur. NF components continuously monitor session information and identify conflicts in advance, removing stale entries before they cause operational issues, rather than waiting for periodic auditing processes
Solution Approach 2:
The system implements feedback mechanisms where NF components monitor session information and use triggers (such as timestamp comparisons and threshold time evaluations) to detect conflicts. When conflicts are detected, the system provides feedback by automatically initiating removal processes, creating a closed-loop system that continuously maintains session information integrity without manual intervention
2Loss of information
If NF components retain all session information to ensure completeness, then no session data is lost, but conflicting stale session information accumulates causing bad requests
Solution Approach 1:
The system proactively identifies conflicting session information using triggers such as timestamp differences and threshold time evaluations before these conflicts cause harmful effects. By detecting and removing stale entries in advance, the system preserves only valid session information while preventing the accumulation of conflicting data that would lead to bad requests
Solution Approach 2:
The system changes the state of session information by evaluating parameters such as timestamps and threshold times to determine validity. When session information exceeds threshold time differences or shows timestamp conflicts, the system automatically removes the stale entries, dynamically adjusting the session information dataset to maintain integrity without manual intervention
Data Source
AI summary
Embodiments of the present disclosure are directed to systems and methods for improved identification and resolution of conflicting session information, such as when multiple session information entries are associated with a single session identifier. By communicating timestamps with the session information deposited in the NF component, the NF component may determine which session information is relevant to the request or which session information is stale and should be removed from its dataset.