Centralized Message Thread Management for Cross-Client Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current instant messaging archiving systems store message threads locally on software clients, making them inaccessible from other clients, and lack centralized storage, which restricts access and continuity across different clients and environments.

Innovation Solution

A server with a message thread management module that centrally stores and manages message threads, allowing access from any software client, preserving continuity and user participation lists, and includes a rights management system for secure message transmission based on user permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If message threads are stored locally on software clients, then each client can access its own message history, but the messages become inaccessible from other clients and cannot be accessed when traveling without the specific software client

Engineering Contradiction:
Improveaccessibility of message threads across different clientsVSAvoidloss of message thread access when changing clients
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces a server as an intermediary component that receives, stores, and manages message threads centrally. The server acts as a mediator between multiple software clients, allowing any client to access any message thread by querying the server. This resolves the contradiction by moving storage from local client memory to a centralized server, enabling cross-client accessibility while preserving all message history.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If message threads are stored centrally on a server, then access is available from any software client, but the system complexity increases and requires additional infrastructure

Engineering Contradiction:
Improvecross-client accessibility of messagesVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the server universal by designing it to handle multiple functions: storing message threads, managing user accounts, handling different software client protocols, and providing search capabilities. This multi-functional approach consolidates what would otherwise require multiple separate systems into a single server, reducing overall system complexity while maintaining cross-client accessibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If all message threads are made accessible to all users, then continuity is preserved across clients, but security and access control become more difficult to manage

Engineering Contradiction:
Improvemessage thread accessibilityVSAvoidmessage access security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements local quality by associating specific access rights with specific users and message threads. Instead of uniform access control, the server evaluates each access request individually based on the user's identity and the specific thread being accessed. This allows the system to provide broad accessibility while maintaining granular security control, as each user receives appropriate access rights for their specific needs without having universal access to all messages.

Inventive Principle:
Principle #3Local quality

4Device complexity

If message threads are stored locally without centralized management, then system simplicity is maintained, but message continuity and context are lost when switching clients

Engineering Contradiction:
Improvesystem architecture simplicityVSAvoidmessage context continuity
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by having the server pre-store and organize all message threads before clients need to access them. When a user switches clients or travels, the message history is already prepared and waiting on the server, eliminating the need for re-synchronization or data transfer. This preliminary storage action ensures continuity is automatically maintained without adding complex real-time synchronization mechanisms.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP1850546B1Management of messages threads
Publication Date: 2019.06.05 ORANGE SA
  • EP1850546B1 patent drawingFigure 1~2

AI summary

The server (21) has an instant messaging module (9) for controlling sending of a message having a given subject by a software client (29) towards another software client (31, 35), and a thread control module (25) for receiving the message from the instant messaging module. A message base (27) sends another message having the given subject for a subject towards the control module. The control module is placed between the instant messaging module and a rights control base (33). Independent claims are also included for the following: (1) a method for retrieving a set of previously exchanged messages (2) an instant messaging system comprising a server (3) a computer program comprising instructions to perform a method for retrieving a set of previously exchanged messages (4) a recording medium comprising instructions to perform a method for retrieving a set of previously exchanged messages.