Transparent Reconnection via Token-Based Session Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
When two systems communicate, unintended interruptions disrupt applications, requiring reestablishment of the communication session, especially in secured systems where authentication is necessary, leading to potential application disruptions.
Innovation Solution
A local server or operating system masks the interruption by using a reconnection token to reestablish the communication session, ensuring that at least one application remains unaffected, with the token being submitted within a predefined time and potentially combined with authentication information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the communication session is reestablished after an interruption in a secured system, then the communication can be restored, but the authentication process must be repeated which disrupts applications
Solution Approach 1:
The system performs preliminary actions by pre-establishing authentication credentials and communication parameters before the interruption occurs. When an interruption happens, these pre-established elements are reused to rapidly reestablish the communication session without requiring reauthentication, thus avoiding application disruption while maintaining security.
Solution Approach 2:
An intermediary mechanism is introduced between the user system and accessible system that handles the reconnection process. This intermediary manages the reuse of authentication information and communication parameters, coordinating the reestablishment process to minimize disruption to applications while ensuring secure communication restoration.
2Reliability
If authentication information is resubmitted after an interruption, then security is maintained, but the reestablishment process becomes more complex and time-consuming
Solution Approach 1:
The system discards the need to resubmit authentication information by recovering and reusing the original authentication credentials that were valid before the interruption. This allows the system to maintain security by continuing to use the same authentication information while dramatically reducing the time required for reestablishment, as no new authentication data needs to be collected or verified.
Solution Approach 2:
The useful action of authentication is made continuous by maintaining the validity of authentication information across interruptions. Instead of treating authentication as a one-time event that must be repeated, the system enables continuous use of the same authentication credentials throughout the communication session, even across interruptions, thereby eliminating reauthentication time while preserving security.
3Ease of operation
If the communication session is reestablished transparently, then applications are unaffected, but the system complexity increases due to masking mechanisms
Solution Approach 1:
The system implements self-service by enabling automatic detection and handling of communication interruptions without requiring external intervention or complex manual masking mechanisms. The system autonomously manages the reestablishment process by reusing existing authentication information and communication parameters, achieving transparent recovery with minimal added complexity compared to manual intervention approaches.
Data Source
AI summary
In the event of an unintentional interruption, a token issued by a host system to a client system is used to reestablish communications without disrupting applications on the client system. If the host system provided an Internet Protocol address to the client system to be used during the interrupted communications session, the host system reserves the communications address during an interruption in communications for a period sufficient to permit reestablishment of communications using the reserved address.