Gateway Session Identifier for Mobile HTTP Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile HTTP sessions between a wireless device and a gateway, interruptions due to IP address changes or physical barriers cause loss of data and require restarting sessions, as existing methods fail to maintain session information across these disruptions.
Innovation Solution
A method where the gateway creates a session identifier for the wireless device's request, stores partial data during interruptions, and resumes data transfer upon reconnection using the same session identifier, allowing continuous data transfer from the point of interruption without restarting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP address and port information are used to implement mobile HTTP sessions, then the gateway can identify and deliver communications to wireless devices, but the session information is lost when the wireless device changes IP address or loses connection
Solution Approach 1:
The gateway creates and stores session information in advance using a session identifier before any interruption occurs. This preliminary establishment of session data with a persistent identifier allows the session to be recovered after IP address changes or connection losses, preventing data loss and maintaining session continuity.
2Productivity
If the wireless device reconnects after IP address change or connection loss, then communication can be restored, but the session data must be retransmitted from the beginning
Solution Approach 1:
The gateway maintains session information continuously using a session identifier that persists across connection interruptions. When the wireless device reconnects, the pre-stored session information is immediately restored and data transfer continues from where it left off, eliminating the need to restart transmissions and maintaining continuous productive action.
3Adaptability or versatility
If HTTP cookies are used for session management, then session information can be maintained in fixed locations, but this method cannot be applied to mobile HTTP sessions between wireless devices and gateways
Solution Approach 1:
The session identifier mechanism serves multiple functions: it identifies the wireless device, maintains session state, enables recovery after interruptions, and works across different IP addresses and connection types. This universal approach replaces the location-specific HTTP cookie model with a flexible identifier-based system that adapts to mobile network conditions while maintaining reliable session management.
Data Source
AI summary
A method, system, and computer readable media are provided for maintaining a mobile session. A session identifier and an associated idle time period are created by the gateway as part of a session header between a wireless device and a content source. When an interruption occurs before a session request for information or data has been completed, the partially transferred information or data is buffered on the gateway, along with its associated session identifier. When the wireless device reconnects, using the associated session identifier header, then the buffered information or data is transferred from the gateway, to the wireless device. The resumed transfer of information or data occurs at the point where the partial transfer stopped, when the interruption occurred. The information or data is completely transferred from the content source to the wireless device, via the gateway.