Unified Chat Threads for Web and Application Activity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing chat-based interactions with generative AI models fail to maintain a holistic context when resumed, as they do not store or restore web pages and applications launched during conversations, leading to an incomplete user experience.
Innovation Solution
Storing data related to web and application activity during conversations and restoring this context when the conversation is resumed, including opening web pages and launching applications as part of the thread's context.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If only chat interface data is stored for thread restoration, then storage complexity is low, but context completeness is insufficient
Solution Approach 1:
The patent merges chat interface data with web browser data and application window data into a unified thread data structure. This integration allows comprehensive context restoration by combining multiple data sources (chat messages, web pages, application states) into a single coherent thread representation that can be restored together.
Solution Approach 2:
The patent implements a nested data structure where thread data contains chat data, which in turn may contain references to web browser data and application window data. This nesting allows hierarchical organization of context information, enabling restoration of complex multi-layered contexts while maintaining manageable data structures.
2Adaptability or versatility
If web pages and applications are tracked during threads, then context restoration capability is improved, but system complexity increases
Solution Approach 1:
The patent creates a universal thread data structure that can accommodate multiple types of data (chat messages, web URLs, application identifiers) within a single framework. This multi-functional approach allows the same thread restoration mechanism to handle diverse context types without requiring separate systems for each data type.
Solution Approach 2:
The patent introduces thread data as an intermediary layer between the chat interface and the underlying web browser/application systems. This mediator captures and stores references to external contexts (web pages, applications) without requiring direct integration with each specific system, simplifying the overall architecture while enabling comprehensive context tracking.
3Ease of operation
If comprehensive thread data is restored, then user experience continuity is improved, but data processing requirements increase
Solution Approach 1:
The patent performs preliminary actions by continuously tracking and storing web browser data and application window data during the thread's active period. This ongoing data capture ensures that when restoration is needed, the context information is already prepared and available, eliminating the need for complex real-time reconstruction processes.
Solution Approach 2:
The patent creates simplified copies of external context data (storing URLs instead of full web pages, storing application identifiers instead of complete application states). These copies capture the essential information needed for restoration while requiring minimal storage space and processing power, enabling efficient context recovery without duplicating entire external systems.
Data Source
AI summary
Examples relate to systems and methods for restoring threads including context of the threads outside of a chat interface. During a thread including multiple queries and responses, one or more of the responses may include links to web pages and/or to other applications (e.g., presentation applications, word-processing applications). During interactions with the thread, one or more of the links may be selected. The selection of the links causes the corresponding web pages to be loaded and/or the corresponding applications to be launched. The web pages that are opened and/or the applications that are launched during an ongoing thread are stored as thread data for the ongoing thread. Then, when the thread is resumed at a later time, not only is the chat interface populated with the prior queries and responses of the thread, but the web pages and/or applications are also restored.