Entity Reference System for Messaging Threads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing messaging systems lack efficient methods for enhancing user interactions by clearly referencing entities within messaging threads, such as users, media, products, and locations, which can lead to confusion and missed notifications.

Innovation Solution

Implementing an entity reference system that predicts and suggests entities in a message thread, generates messages with entity references, and augments these references with additional information and controls, allowing users to interact more effectively with mentioned entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If entity references are added to messaging threads to improve user interaction clarity, then user experience and interaction effectiveness are improved, but system complexity and processing requirements increase

Engineering Contradiction:
Improveuser interaction clarityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system pre-generates entity reference suggestions and augmentation elements before the user needs them. When a user types a message, the system has already prepared relevant entity references (users, media, products, locations) and their augmentation elements, making them immediately available for insertion. This eliminates the need for complex real-time processing during message composition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer between the user and the messaging system that handles entity reference generation and augmentation. This intermediary component processes messages, identifies entities, generates references, and adds augmentation elements without requiring the core messaging system to be complex. The intermediary acts as a buffer that manages the complexity separately from the main messaging functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the system predicts and suggests entities in real-time to enhance user interaction, then interaction effectiveness is improved, but processing time and computational resources increase

Engineering Contradiction:
Improveinteraction effectivenessVSAvoidprocessing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system applies different processing levels to different parts of the messaging system. Entity reference prediction and suggestion are performed locally on the client device using lightweight algorithms, while more complex augmentation element generation is performed server-side. This local processing approach minimizes latency and provides immediate suggestions to users without requiring extensive server processing time.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs preliminary entity identification and reference generation based on the context already available in the messaging thread. By analyzing the conversation context in advance and pre-generating relevant entity references before the user completes their message, the system reduces the processing time required during actual message sending. The augmentation elements are also prepared in advance based on predicted entity references.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If augmentation elements are added to entity references to provide additional information, then information completeness is improved, but message complexity and data transmission volume increase

Engineering Contradiction:
Improveinformation completenessVSAvoiddata transmission volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential augmentation elements needed for each entity reference rather than including all possible information. The system identifies and extracts key attributes (such as user profile pictures, product images, location pins) that are most relevant to the context, omitting redundant or less important information. This selective extraction maintains information completeness while minimizing data transmission volume.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies partial augmentation by adding only certain types of augmentation elements based on the entity type and context, rather than uniformly augmenting all entity references. For example, user entities may receive profile picture and status augmentations, while product entities receive image and price augmentations. This partial approach provides sufficient information for each context without unnecessarily increasing data transmission volume for all entities.

Inventive Principle:
Principle #16Partial or excessive action

4Adaptability or versatility

If the system generates and manages entity references with augmentation elements, then user notification and interaction capabilities are improved, but privacy security requirements and system overhead increase

Engineering Contradiction:
Improveinteraction capabilitiesVSAvoidprivacy security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary privacy checks and permission validations before generating and sending entity references with augmentation elements. User consent for data sharing, image usage, and location information is obtained in advance and stored. When generating entity references, the system checks these pre-established permissions to ensure privacy compliance, preventing unauthorized information disclosure while maintaining interaction capabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary privacy management layer that sits between the entity reference generation system and the data sources. This intermediary component handles permission verification, data filtering, and compliance checking, ensuring that only authorized information is included in augmentation elements. It manages privacy security requirements separately from the interaction functionality, allowing versatile user interactions while maintaining reliable privacy protection.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11411903B1Techniques for generating entity references in a messaging thread
Publication Date: 2022.08.09 META PLATFORMS INC
  • US11411903B1 patent drawing
  • US11411903B1 patent drawing
  • US11411903B1 patent drawing

AI summary

Techniques for entity references in messaging groups. A client device may receive a notification in a messaging application that an entity reference to a user associated with the client device appears in a group messaging thread. The group messaging thread may have, as participants, one or more other users associated with one or more other client devices. A notification of the appearance of the entity reference may be displayed in a user interface of the messaging application.