Global Internet Message Threads for Contextual Visibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud platform users often miss important information and engage in redundant work due to limited visibility of messages exchanged between groups they are not part of, leading to inaccurate message interpretation and negative impacts on individuals and organizations.

Innovation Solution

Implementing global internet message threads that store and display messages based on thread identifiers, allowing users to view all messages associated with a thread regardless of their involvement, and providing context for improved interpretation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If user-specific message threads are implemented, then message privacy and relevance to individual users are improved, but message visibility and contextual understanding deteriorate

Engineering Contradiction:
Improvemessage contextVSAvoidmessage viewing access
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system segments message threads into two levels: user-specific threads (visible only to participants) and global threads (visible to all users). This segmentation allows the system to simultaneously provide privacy for individual conversations while enabling broader contextual access through global threads that aggregate messages across user groups.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Global threads serve as an intermediary mechanism that bridges the gap between user-specific message privacy and organizational-wide contextual understanding. These threads act as a mediator that allows users to access relevant message contexts without directly participating in the original conversations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If global message visibility is implemented, then contextual understanding and system efficiency are improved, but message privacy and user-specific relevance deteriorate

Engineering Contradiction:
Improvesystem efficiencyVSAvoidmessage privacy
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system applies different visibility qualities to different message threads: user-specific threads maintain private, localized access for participants only, while global threads provide broader organizational visibility. This local quality differentiation allows the system to optimize for privacy where needed and for efficiency where appropriate.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The message thread system dynamically adjusts visibility based on thread characteristics and user roles. Threads can transition between private and global visibility states, allowing the system to adapt to different operational contexts and balance privacy requirements with efficiency needs.

Inventive Principle:
Principle #15Dynamics

3Reliability

If user-specific threads are used, then message privacy is maintained, but redundant work and information loss increase

Engineering Contradiction:
Improvemessage privacyVSAvoidredundant work
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary organization of messages into global threads that aggregate communications across user groups. This preliminary action allows users to access relevant contextual information before engaging in new communications, preventing redundant work and information loss while maintaining privacy for individual conversations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11057331B2Construction of global internet message threads
Publication Date: 2021.07.06 SALESFORCE INC
  • US11057331B2 patent drawing
  • US11057331B2 patent drawing
  • US11057331B2 patent drawing

AI summary

Methods, systems, and devices supporting global message threads are described. A thread server may receive a communication message associated with a first set of user identifiers (e.g., the author and recipients of the message) and may extract a thread identifier from the message. The thread identifier may associate the message with one or more additional messages (e.g., from the same thread of messages), where the one or more additional messages may be associated with different user identifiers. The thread server may upsert the received communication message to a stored set of messages associated with a root indicating the thread identifier. If the thread server receives a query indicating the thread identifier from a user, the thread server may retrieve all of the messages associated with the thread identifier from persistent memory based on the query, including messages that are not associated with the user identifier for the querying user.