Automatic Thread Unsuppressing via Contact Ranking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices lack an efficient method to automatically unsuppress threads based on contact ranking criteria, leading to suppressed threads being hidden from the user interface without notification, even when important contacts are involved in the conversation.

Innovation Solution

A device and method that utilize a processor to receive messages associated with suppressed threads, automatically unsuppressing them when the message is from a flagged contact in the contact list, using a ranking engine to flag contacts based on organizational charts, previous threads, and time criteria, and moving or unflagging the threads to ensure they are displayed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If threads are suppressed to reduce clutter in the user interface, then the interface becomes cleaner and more organized, but important messages from flagged contacts may be hidden without notification

Engineering Contradiction:
Improveuser interface organizationVSAvoidimportant messages hidden
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system continuously monitors incoming messages and automatically evaluates whether suppressed threads should be unsuppressed based on real-time conditions (flagged contacts, new recipients). This feedback mechanism ensures important messages are automatically recovered without user intervention while maintaining interface cleanliness for non-important threads.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The messaging system performs self-service by automatically evaluating and unsuppressing threads when important contacts are involved. The ranking engine and message evaluation logic enable the system to autonomously manage thread visibility without requiring manual user action, balancing interface organization with important message delivery.

Inventive Principle:
Principle #25Self-service

2Reliability

If all messages from flagged contacts are automatically displayed, then important messages are ensured to be visible, but the user interface becomes cluttered with less important messages

Engineering Contradiction:
Improveimportant message visibilityVSAvoidinterface clutter
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies different visibility rules to different threads based on their specific characteristics. Threads involving flagged contacts receive priority treatment (unsuppressed and potentially visually flagged), while other threads maintain their suppressed state. This localized quality approach ensures important messages are visible without uniformly displaying all messages.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system uses visual flagging (color changes or visual indicators) to highlight messages from flagged contacts within the interface. This allows important messages to be distinguished through visual cues without requiring all messages to be displayed in the main view, thereby maintaining interface organization while ensuring important message visibility.

Inventive Principle:
Principle #32Color changes

3Ease of operation

If manual suppression of threads is allowed, then users can organize their message views according to preference, but users must manually re-enable important threads when they miss messages

Engineering Contradiction:
Improvemessage organization controlVSAvoidtime to re-enable threads
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary evaluation of incoming messages against the contact ranking database before thread suppression occurs. By pre-identifying messages from flagged contacts and marking them for potential unsuppression, the system eliminates the need for manual re-enabling later, saving user time while maintaining organizational control.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The continuous monitoring and automatic unsuppression mechanism provides real-time feedback when important contacts send messages. This feedback loop automatically reverses suppression decisions when warranted, eliminating the manual intervention time users would otherwise need to spend re-enabling important threads.

Inventive Principle:
Principle #23Feedback

4Extent of automation

If a ranking engine is implemented to flag important contacts, then message prioritization becomes automated, but the system complexity increases

Engineering Contradiction:
Improvemessage prioritizationVSAvoidsystem structure
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The contact ranking database serves multiple functions: it identifies important contacts for automatic unsuppression, enables visual flagging of their messages, and supports message prioritization. This multi-functionality reduces overall system complexity by using a single data structure for multiple purposes rather than requiring separate mechanisms for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The ranking engine automatically evaluates contacts and assigns rankings without requiring manual user configuration. The system self-services by continuously maintaining the contact ranking database based on interaction patterns, organizational charts, and message history, reducing the complexity burden on users while providing sophisticated automation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4227874A1Method, system and apparatus for automatically unsuppressing threads
Publication Date: 2023.08.16 MALIKIE INNOVATIONS LTD
  • EP4227874A1 patent drawingFigure 1
  • EP4227874A1 patent drawingFigure 2
  • EP4227874A1 patent drawingFigure 3

AI summary

A method, system and apparatus for automatically unsuppressing threads are provided. A message associated with a suppressed thread is received, using a communication interface of device. The suppressed thread is automatically unsuppressed by a processor of the device when one or more of: the message is from a contact that is flagged in a contact list; and, the contact that is flagged in the contact list has been added as a recipient of the message as compared to at least a last message in the suppressed thread.