Message Storage Clustering with Template Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Messaging services face inefficiencies in storage and retrieval due to redundant message content, leading to excessive storage space consumption, maintenance overhead, and infrastructure costs, as many messages have similar content with only specific information varying between them.

Innovation Solution

Messages are clustered based on their structure, with constant content stored once in templates and variable content stored per message, using a signature calculated from element paths in the document object model to identify and retrieve messages efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If every message is stored in perpetuity for every user, then message retrieval completeness is improved, but storage space consumption increases significantly

Engineering Contradiction:

Improvemessage retrieval completenessVSAvoidstorage space consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The message content is segmented into two distinct parts: common content that is identical across multiple messages, and unique content that varies between messages. The common content is extracted and stored once in a shared repository, while only the unique portions are stored individually for each message. This segmentation allows complete message reconstruction without storing redundant data, resolving the contradiction between retrieval completeness and storage efficiency.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of storing complete message copies for every user, the system creates a template copy containing only the common content structure and placeholders. When a message needs to be retrieved, the unique content is inserted into the template to reconstruct the full message. This copying approach maintains message integrity while dramatically reducing storage requirements by eliminating redundant common content across multiple message instances.

Inventive Principle:

Principle #26Copying

2Speed

If redundant message content is stored for each message instance, then message retrieval speed is improved, but maintenance overhead increases

Engineering Contradiction:

Improvemessage retrieval speedVSAvoidmaintenance overhead

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

Multiple message instances that share common content are merged into a single stored representation. The system identifies and combines the common elements across messages into one shared storage location, while maintaining references to the unique elements. This merging reduces the total number of storage operations and retrieval operations, lowering maintenance overhead while preserving fast access through the organized structure of shared and unique content segments.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If complete messages are stored for each user account, then message accuracy is improved, but energy consumption increases

Engineering Contradiction:

Improvemessage accuracyVSAvoidenergy consumption

Core Design Contradiction:

ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The common content portion is extracted from individual message instances and separated into a shared repository. Only the essential unique content that differentiates each message is retained in user-specific storage. This extraction reduces the total data volume that requires energy-intensive storage operations, while the structured retrieval process ensures complete and accurate message reconstruction by combining the extracted common content with the unique content portions.

Inventive Principle:

Principle #2Taking out (Extraction)

4Manufacturing precision

If similar message content is stored redundantly, then message reconstruction accuracy is improved, but infrastructure cost increases

Engineering Contradiction:

Improvemessage reconstruction accuracyVSAvoidinfrastructure cost

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

Messages are segmented into common and unique content portions, with each segment stored in an optimized location. The common content segment is stored once in a shared repository, while unique content segments are stored individually. This segmentation maintains complete message reconstruction accuracy because both segments are preserved and systematically combined during retrieval, while dramatically reducing infrastructure costs by eliminating redundant storage of common content across multiple message instances.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS10949449B2Systems and methods for efficient electronic message storage and retrieval

Publication Date: 2021.03.16 YAHOO ASSETS LLC

AI summary

One or more computing devices, systems, and/or methods for efficiently storing and retrieving electronic communication are provided. Messages with the same structure are grouped into a same cluster. A template is created for the cluster. The template is populated with constant values that are the same amongst the messages. Variable values that are different amongst the messages are stored within user account repositories for each message. In this way, the constant values are merely stored once for the messages within the cluster. A template within a general repository and variable values within a user account repository may be used to reconstruct a message.