Messenger Chat History Sync via Public Repository Merging

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing instant messenger systems face challenges in maintaining synchronized message lists across multiple devices with shared user accounts due to storage constraints and varying message retention policies, leading to inconsistent chat history displays.

Innovation Solution

A method for synchronizing messages between multiple messenger client devices using a public repository, where local data is uploaded and merged with public data to ensure consistent chat history display across devices, independent of server involvement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If messages are stored locally in each messenger client device, then message storage capacity is increased, but message synchronization across multiple devices deteriorates

Engineering Contradiction:

Improvemessage storage capacityVSAvoidmessage synchronization

Core Design Contradiction:

Quantity of substanceVSReliability

Solution Approach 1:

The system divides message storage into two segments: local repository for capacity and public repository for synchronization. Local storage handles quantity requirements while public storage ensures consistency across devices, resolving the contradiction between storage capacity and synchronization reliability

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A public repository acts as an intermediary between multiple messenger client devices. Each device uploads messages to and downloads messages from this intermediary storage, enabling synchronization across devices while maintaining local storage capacity

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of energy

If server storage period is limited, then resource consumption is reduced, but message availability across devices deteriorates

Engineering Contradiction:

Improveserver resource consumptionVSAvoidmessage availability

Core Design Contradiction:

Loss of energyVSLoss of information

Solution Approach 1:

The system extracts the message storage function from the messenger server to a separate public repository. The server only needs to store recent messages according to its retention policy, while the public repository preserves historical messages indefinitely, reducing server resource consumption while maintaining message availability

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Messages are uploaded to the public repository in advance before the server's retention period expires. This preliminary action ensures messages are preserved externally before server deletion, maintaining availability while allowing the server to enforce its storage period policy

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If different devices store messages independently, then device autonomy is maintained, but chat history consistency deteriorates

Engineering Contradiction:

Improvedevice autonomyVSAvoidchat history consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system merges device autonomy with chat history consistency by combining independent local storage with synchronized public storage. Each device maintains autonomous local storage while periodically merging with the public repository to ensure consistency, allowing both device independence and unified chat history

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS12587497B2Method for synchronizing messages between plurality of messenger client devices and messenger client device using same

Publication Date: 2026.03.24 SAMSUNG SDS CO LTD

AI summary

The disclosure relates to a method for synchronizing messages between a plurality of messenger client devices, and a messenger client device using the same, and the method for synchronizing messages between a plurality of messenger client devices to which a user account is shared according to an embodiment of the disclosure may include: accessing a pre-configured public repository and downloading public data including a previous chat list shared between the plurality of messenger client devices by a messenger client device; and generating merged data by merging the public data and local data including a previous chat list stored in a local repository of the messenger client device by the messenger client device.