XR Session State Tracking for Consistent Multi-User Relaunch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing XR environments lack an effective method for determining and saving the state of applications or sessions, especially in multi-user communication scenarios, which hinders consistent and seamless interaction among users.
Innovation Solution
A system and method for collecting and storing session state information in XR environments, including application and session state data, to enable consistent re-launching of applications and sessions based on saved state information, utilizing modules like state tracking and data stores to manage and retrieve this information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If state information is collected and stored for multi-user communication sessions, then application and session re-launching consistency is improved, but system complexity increases
Solution Approach 1:
The state tracking system is segmented into distinct functional modules: a state tracking module that collects state information, a data store that stores the state information, and a session management module that retrieves and applies state information. This segmentation allows each module to have a specific responsibility, reducing overall system complexity while maintaining reliability.
Solution Approach 2:
A state tracking module acts as an intermediary between the communication session and the data store. This intermediary automatically collects, stores, and retrieves session state information, shielding the complexity of state management from both the session logic and the data storage mechanisms, thereby improving reliability without significantly increasing perceived system complexity.
2Adaptability or versatility
If session state data is stored for all applications in multi-user sessions, then user experience continuity is improved, but data storage requirements increase
Solution Approach 1:
The system stores state information with differentiated detail levels based on application type and session context. Critical session state data is stored with high fidelity to ensure continuity, while less critical application state data may be stored with reduced detail or selectively, optimizing storage usage while maintaining user experience continuity.
Solution Approach 2:
The state tracking module dynamically adjusts which parameters are tracked and stored based on session context, application requirements, and storage availability. By changing the granularity and completeness of stored state data based on parameters such as session importance and application criticality, the system maintains continuity where needed while reducing overall storage requirements.
Data Source
AI summary
A state of a multi-user communication session is saved in response to detection of an application state saving event, or a session state saving event. During runtime, application state saving events may be detected for each application executing during a session. Application state parameters are saved in response to each application state saving event, from which the application may be launched to the saved state. In response to a state saving event, the most recent application state information for each application executing in the session are collected and stored such that the multi-user communication session may be launched to the saved state, including each application executing in the session.