IMS Profile Recovery Through Application Servers for Session Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IMS restoration procedures cause service disruptions, unnecessary network bandwidth consumption, and data duplication issues due to unneeded communications and tearing down communication sessions when IMS nodes become unavailable.
Innovation Solution
Implementing profile recovery through application servers that allow for efficient reassignment of UEs to available nodes, reducing unneeded communications and avoiding session teardown, thereby maintaining service continuity and optimizing network bandwidth.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing IMS restoration procedures are used to handle unavailable IMS nodes, then the communication session can be restored, but service disruption occurs and network bandwidth is unnecessarily consumed
Solution Approach 1:
The patent applies preliminary action by pre-establishing backup bindings between UEs and alternative IMS nodes before failures occur. When a node becomes unavailable, the pre-configured backup bindings enable immediate session restoration without triggering unnecessary discovery procedures, thus reducing network bandwidth consumption while maintaining reliable session continuity.
Solution Approach 2:
The patent uses copying by creating and maintaining duplicate binding records in the data repository that map UEs to multiple potential serving nodes. These copied binding entries serve as ready-to-use alternatives, eliminating the need for real-time node discovery and profile recovery communications, thereby reducing network traffic while ensuring session restoration capability.
2Reliability
If existing IMS restoration procedures are used to handle unavailable IMS nodes, then the communication session can be restored, but service disruption and delay occur
Solution Approach 1:
The patent implements preliminary action by pre-configuring backup bindings that associate UEs with alternative IMS nodes before any failure occurs. This advance preparation eliminates the time-consuming node discovery and profile recovery processes, enabling instant session restoration while maintaining high reliability through pre-validated backup paths.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining active binding records that continuously point to available IMS nodes. When a node fails, the system seamlessly switches to pre-established backup bindings without interrupting the service flow, thereby eliminating restoration delays while ensuring continuous reliable communication.
3Reliability
If existing IMS restoration procedures are used to handle unavailable IMS nodes, then the communication session can be restored, but data duplication and incorrect data occur
Solution Approach 1:
The patent applies copying by creating duplicate binding records in the data repository that map UEs to multiple potential serving nodes. These copied bindings are carefully managed to reflect accurate, non-stale information, eliminating data duplication problems while ensuring that only valid, current node associations are maintained, thus preserving data accuracy during restoration.
4Productivity
If profile recovery is executed through application servers with efficient reassignment, then service continuity is maintained and network bandwidth is optimized, but the system complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-establishing backup bindings between UEs and alternative IMS nodes before failures occur. This advance preparation enables efficient restoration with minimal processing during actual failure events, improving productivity while managing system complexity through automated, pre-configured failover mechanisms rather than complex real-time decision-making.
Data Source
AI summary
Improved systems and method are described for addressing issues when an S-CSCF goes appears non-responsive or an application server appears non responsive. Profile recovery is executed through application servers which may allow additional options in efficiencies in maintain applications while recovering from the non-responsive devices.