Proxy Server Co-Browsing Session State Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional user collaboration and co-browsing tools, such as those offered by LIVELOOK and ORACLE 'Service Cloud', are limited in providing a fully customized approach to user collaboration and engagement, especially in managing browser interactions and maintaining user session states across multiple devices in a co-browsing environment.
Innovation Solution
A method and apparatus that utilize a proxy server to manage user profiles, create sessions for accessing live web pages, store browser status commands, and facilitate co-browsing by loading data presentations, authorizing requests, and providing live data to participating user devices, allowing for real-time synchronization and 'Snap Back' functionality to revert to previous browser states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional co-browsing tools are used, then basic collaboration functionality is provided, but full customization of user collaboration and engagement is not achieved
Solution Approach 1:
The system segments user profiles into distinct entities with independently configurable function lists. Each user profile can be customized with specific functions assigned from available functions, allowing granular control over collaboration capabilities without requiring complete system redesign.
Solution Approach 2:
The system dynamically assigns and reassigns functions to user profiles based on collaboration needs. Functions can be added, removed, or modified in real-time, enabling the system to adapt to changing collaboration requirements while maintaining a manageable core structure.
2Reliability
If proxy server is used to manage browser sessions, then user identity anonymity is achieved, but browser status synchronization across devices becomes complex
Solution Approach 1:
The proxy server acts as an intermediary that manages browser sessions and stores browser status commands centrally. This mediator approach allows multiple devices to participate in co-browsing while maintaining user anonymity, as the proxy server handles identity management and session coordination without requiring direct peer-to-peer device communication.
Solution Approach 2:
The system creates and maintains copies of browser status commands across multiple devices through the proxy server. When a user interacts with a web page, the browser status commands are captured and distributed to participating devices, enabling synchronization without requiring complex direct device-to-device state management.
3Adaptability or versatility
If multiple user devices participate in co-browsing, then collaboration capability is enhanced, but maintaining session state synchronization increases system complexity
Solution Approach 1:
The system merges session state management into a centralized proxy server that handles all participating devices. Instead of each device maintaining independent session states, the proxy server consolidates browser status commands and distributes them to all devices, reducing overall system complexity while enabling multi-device collaboration.
Solution Approach 2:
The system implements feedback mechanisms where browser status commands from participating devices are captured, processed, and distributed back to all devices in real-time. This continuous feedback loop maintains session state synchronization across devices without requiring complex manual coordination.
Data Source
AI summary
Sharing data with various user devices may be performed by receiving a request from a first user device to connect to a session with a live web page collaboration application managed by a proxy server, loading a data presentation via a master page of a master application operated by the proxy server, receiving at least one co-browsing request from at least one other user device, authorizing the at least one co-browsing request, and providing live data from the data presentation to the first user device and the at least one other user device actively participating in the session.


