Unified Messaging Thread for Cross-Context Message Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users of conversational-type messaging applications often face confusion when trying to access information exchanged in both one-to-one and one-to-many conversations, as they need to search multiple conversations to find context, leading to discontinuity and inefficiency.
Innovation Solution
Implementing a method where 1:Many messages are populated into an existing or newly created 1:1 conversation with the same recipient, ensuring all correspondence is accessible in a single messaging screen, regardless of the original context, thereby creating a unified access point for all messages with a particular recipient.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users exchange messages in both 1:1 and 1:Many conversations with the same recipient, then message coverage and communication flexibility are improved, but message continuity and ease of access deteriorate as users must search multiple conversations
Solution Approach 1:
The patent merges 1:Many messages and 1:1 messages into a single unified conversation thread. When a user receives a 1:Many message, the system automatically creates or updates a 1:1 conversation with each recipient, populating it with the 1:Many message content. This allows all messages with a particular recipient to be accessed in one location, resolving the contradiction by combining multiple message types into a single accessible stream.
Solution Approach 2:
The unified conversation mechanism serves multiple functions simultaneously: it acts as both a 1:Many message distribution channel and a 1:1 conversation history repository. The system universally handles different message types (1:1 and 1:Many) through a single interface, allowing users to access all correspondence with any recipient regardless of the original message type, thereby improving ease of operation while maintaining adaptability.
2Loss of information
If users search multiple conversations to find exchanged information, then complete information retrieval is possible, but time consumption and operational efficiency worsen
Solution Approach 1:
The system performs preliminary organization of messages by automatically creating or updating 1:1 conversation threads with appropriate 1:Many message content before the user needs to access them. This preliminary structuring ensures that when users need to retrieve information, it is already organized and accessible in a single location, eliminating the need for time-consuming searches across multiple conversations while maintaining complete information retrieval.
3Reliability
If separate 1:1 and 1:Many conversation streams are maintained, then message context accuracy is preserved, but system complexity and navigation difficulty increase
Solution Approach 1:
The patent combines the management of 1:1 and 1:Many conversations into a unified system where a single conversation thread can contain both types of messages. The system maintains message context accuracy by preserving the original message type indicators and content while integrating them into one accessible stream, thereby reducing navigation complexity without sacrificing context reliability.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A system and method are provided for managing messages in conversational-type messaging applications. To provide continuity across all conversations with a particular recipient, an existing or not-yet-created 1:1 conversation can be populated with 1:Many messages that include the same recipient in the list of addressees. In this way, any 1:1 chat or conversation with a particular recipient will contain all correspondences with that recipient, regardless of whether the message was sent or received in a 1:1 or 1:Many context. As such, the user has access to all information that has been exchanged with that recipient in one messaging screen to avoid the need to traverse multiple messaging screens to obtain the context or information related to the recipient that the user requires.