Browser Session Synchronization Across Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web clients lack efficient synchronization of session data, particularly user interactions and form element data, between desktop and mobile devices, making it difficult to maintain consistent browsing experiences across different platforms.
Innovation Solution
A system and process for automatically synchronizing session data between web clients, involving a session monitoring module to detect updates, a notification module to transmit notifications, and a synchronization module to transfer data over a network, ensuring that navigation history, form element data, and other user inputs are synchronized between desktop and mobile web clients.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If session data synchronization between web clients is implemented, then browsing experience continuity is improved, but system complexity increases
Solution Approach 1:
The patent employs a server as an intermediary to facilitate session data synchronization between web clients. The server receives session data from one web client, processes it, and distributes it to other web clients, thereby enabling browsing continuity without requiring direct complex peer-to-peer communication between clients. This intermediary approach simplifies the overall system architecture while achieving the goal of seamless browsing experience across devices.
2Speed
If real-time synchronization of session data is implemented, then user interaction continuity is improved, but network bandwidth consumption increases
Solution Approach 1:
The patent implements selective synchronization by identifying and transmitting only specific session data elements that have changed (such as form element data, navigation history updates) rather than synchronizing entire session datasets. This partial action approach maintains real-time synchronization effectiveness while significantly reducing network bandwidth consumption compared to full data transfers.
Solution Approach 2:
The system employs periodic polling or event-triggered synchronization mechanisms where session data is updated and transmitted at specific intervals or when particular events occur (such as form submission, page navigation). This periodic action ensures timely synchronization while avoiding continuous data transmission, thereby optimizing network bandwidth utilization.
3Ease of operation
If comprehensive session data including form element data is synchronized, then user input portability is improved, but data transmission volume increases
Solution Approach 1:
The patent extracts and synchronizes only the essential session data elements required for browsing continuity, such as form element data, navigation history, and basic user interactions. By selectively extracting only the necessary data components rather than transmitting comprehensive session data, the system achieves user input portability across devices while minimizing data transmission volume.
Solution Approach 2:
The system creates simplified copies of session data that contain only the critical information needed for browsing continuity. Instead of transmitting complete and complex session datasets, the patent generates streamlined data representations that preserve essential user input information while reducing overall data size, enabling efficient synchronization across multiple web clients.
Data Source
AI summary
Configurations for automated synchronization of browser data from a desktop web client (e.g., a desktop web browner) to a web client on a mobile device are provided. In particular, session data including navigation history data of one or more visited web pages on the desktop web client can be synchronized with a mobile device. Initially, session data from the desktop web client can be received over a network. In some configurations, a notification can then be transmitted to a mobile device for indicating session data is available for synchronizing with a mobile web client on the mobile device. The session data is then transmitted to the mobile web client. On the mobile device, the received session data can be displayed in a window of the mobile web client.


