Deferred Message Storage via Template Parameter Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing deferred message systems consume excessive network traffic and storage space, and do not support roaming of message history records, as they require repeated download of message templates and storage of all messages in the server database.

Innovation Solution

The solution involves separating message templates and parameters, pre-downloading message templates, and storing only message parameters in the server database, allowing for efficient delivery and storage of deferred messages, and enabling message history roaming by retaining parameters in the server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all deferred messages are stored in the server database, then message history can be accessed, but storage space consumption increases significantly

Engineering Contradiction:

Improvemessage history accessibilityVSAvoidstorage space consumption

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The message data is segmented into two parts: message parameters (stored in server database) and message templates (stored locally in client). This segmentation allows the server to store only essential parameter data while clients store template data, significantly reducing server storage requirements while maintaining message history accessibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Message templates are copied from the server to local client storage. Instead of storing complete message content in the server database, the system stores template copies locally in clients and only keeps parameter data on the server, reducing server storage consumption while enabling message reconstruction when needed.

Inventive Principle:

Principle #26Copying

2Loss of information

If message templates are downloaded repeatedly, then complete messages can be displayed, but network traffic increases significantly

Engineering Contradiction:

Improvemessage content completenessVSAvoidnetwork traffic consumption

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

Message templates are downloaded and stored in local client storage in advance, before they are needed for message display. This preliminary action eliminates the need for repeated downloads during message retrieval, significantly reducing network traffic while ensuring complete message content can be displayed when parameters are received.

Inventive Principle:

Principle #10Preliminary action

3Loss of energy

If message templates are stored locally, then network traffic is reduced, but message history roaming across devices is lost

Engineering Contradiction:

Improvenetwork traffic reductionVSAvoidmessage history roaming capability

Core Design Contradiction:

Loss of energyVSAdaptability or versatility

Solution Approach 1:

The system segments message data into parameters (stored on server) and templates (stored locally). This segmentation enables message history roaming because the essential parameter data remains accessible on the server across different devices, while local template storage reduces network traffic. When users access from different devices, parameters are retrieved from the server and combined with locally cached templates.

Inventive Principle:

Principle #1Segmentation

4Ease of operation

If complete messages are stored in database, then message retrieval is simple, but database maintenance complexity increases

Engineering Contradiction:

Improvemessage retrieval simplicityVSAvoiddatabase maintenance complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The message storage system is segmented into parameter storage (server database) and template storage (local client). This segmentation simplifies database maintenance because the server database only stores compact parameter data rather than complete message content, reducing database size and maintenance complexity while message retrieval remains simple through parameter lookup and template combination.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11159465B2Service apparatus and method for providing deferred message, and storage medium

Publication Date: 2021.10.26 TENCENT TECHNOLOGY (SHENZHEN) CO LTD

AI summary

A service apparatus and method for providing a deferred message, and a storage medium. The service method for providing a deferred message comprises: receiving a message parameter sent by a first client and to be forwarded to a second client (S1); determining whether a user associated with the second client is online (S2); if the user associated with the second client is not online, determining that the message parameter to be forwarded is a message parameter of a deferred message, and saving the message parameter into a database of a server (S3); and when receiving an online prompt of the user associated with the second client, delivering the message parameter to the second client (S4). The method can significantly reduce the network traffic and occupation of the storage space.