SaaS Session Mirroring via Browser Command Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users of Software as a Service (SaaS) applications face inefficiencies when transitioning between devices, as they must repeatedly rebuild context and authenticate to restore their application state, leading to decreased productivity and user experience.
Innovation Solution
A system that allows a server to store and replicate browser commands across different browsers on client devices, enabling seamless state migration and parallel execution of SaaS application sessions, while blocking duplicate traffic to prevent unintended actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a user transitions between devices for SaaS application access, then the user can continue working on different devices, but the user must repeatedly rebuild context and authenticate, resulting in loss of time and productivity
Solution Approach 1:
The system performs preliminary actions by capturing and storing browser commands during the first SaaS application session before device transition. These stored commands enable the second browser to rapidly reconstruct the application state without requiring the user to manually rebuild context, thus reducing transition time while maintaining adaptability across devices
Solution Approach 2:
The system creates a copy of the first SaaS application session state by replicating browser commands in the second browser. This copying mechanism allows the user to access the same application state on a different device without time loss, as the copied session includes all necessary context, settings, and navigation history
2Reliability
If the server stores and replicates browser commands for state migration, then seamless application state transfer is achieved, but network traffic and data processing requirements increase
Solution Approach 1:
The system extracts only the essential browser commands necessary for state migration from the complete session data. By taking out only the critical commands rather than transferring the entire session, the system maintains reliable state transfer while minimizing network traffic and energy consumption
Solution Approach 2:
The system performs partial action by selectively replicating only the necessary browser commands for state reconstruction, rather than copying all possible session data. This partial replication approach ensures reliable state transfer for the essential functionality while reducing unnecessary network traffic and processing overhead
3Ease of operation
If parallel SaaS application sessions are executed in first and second browsers, then seamless state migration is enabled, but duplicate network traffic may cause unintended actions
Solution Approach 1:
The server acts as an intermediary between the first and second browsers, mediating network traffic to distinguish between legitimate user actions and duplicate traffic. This intermediary function allows seamless state migration operation while preventing harmful duplicate actions by filtering and managing traffic from both parallel sessions
Data Source
AI summary
A computer system may include a client computing device configured to run a first Software as a Service (SaaS) application session from a SaaS server within a first browser. A server may cooperate with the at least one client computing device to run a second SaaS application session within a second browser mirroring a state of the first SaaS application session, and forward data traffic generated by the first SaaS application session to the SaaS server while blocking traffic generated by the second SaaS application session from passing to the SaaS server.