Federated Messaging System with Reference Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing unified messaging system architectures face challenges such as high costs, data replication, synchronization conflicts, and complexity in managing heterogeneous message formats across different messaging services, making them unsuitable for large-scale or public implementations.

Innovation Solution

A federated messaging system that centrally manages messages across multiple services, translating messages into a compatible format using a referencing database and interface managers, allowing unified access without modifying existing messaging devices or replicating data, and notifying events in real-time across all services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If messages are replicated across all messaging devices to enable unified access, then users can access messages from any terminal, but storage costs increase and synchronization conflicts occur

Engineering Contradiction:
Improveunified message accessVSAvoidstorage space requirement
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent introduces a reference database as an intermediary component that stores metadata (headers, routing information, format descriptors) about messages without replicating the actual message bodies across all devices. This reference database acts as a central coordination point that enables unified access while avoiding the storage overhead and synchronization conflicts of full replication.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message data is segmented into two parts: message headers/metadata stored centrally in the reference database, and message bodies stored locally in their original format at the source messaging device. This segmentation allows the system to provide unified access through the reference database while avoiding full replication of all message data across all devices.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If messages are replicated across all messaging devices to enable unified access, then users can access messages from any terminal, but synchronization conflicts become difficult to resolve

Engineering Contradiction:
Improveunified message accessVSAvoidsynchronization consistency
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The reference database serves as a mediator that maintains a single source of truth for message metadata and routing information. By centralizing this coordination function, the system eliminates synchronization conflicts that would otherwise arise from multiple devices maintaining identical copies of message data.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If a centralized messaging server is used to store all messages, then data replication is avoided, but the system requires costly data migrations and is incompatible with existing closed messaging devices

Engineering Contradiction:
Improvedata replicationVSAvoidsystem implementation complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

Rather than requiring a centralized server to store all message bodies, the patent uses a reference database that stores only metadata and routing information. This intermediary approach avoids the need for costly data migrations from existing messaging devices while still providing centralized coordination benefits.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts only the essential coordination functions (message metadata, routing information, format descriptors) from a hypothetical centralized server and places them in a reference database. The actual message bodies remain distributed at their source devices, eliminating the need for data migrations while retaining centralized coordination capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

4Ease of operation

If message formats are standardized across all messaging services, then unified access is simplified, but adaptability to handle diverse message formats is reduced

Engineering Contradiction:
Improveunified access simplicityVSAvoidmessage format compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by storing message format descriptors and transformation rules locally in the reference database for each messaging service. This allows the system to maintain a unified access interface while adapting to diverse message formats through service-specific transformation capabilities.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes parameters dynamically by using format descriptors and transformation rules that adapt the message representation based on the target service requirements. This allows unified access without imposing a single standardized format, as messages can be transformed into appropriate formats for different services.

Inventive Principle:
Principle #35Parameter changes

5Adaptability or versatility

If translation services are added to handle diverse message formats, then adaptability to different formats is improved, but system complexity and processing time increase

Engineering Contradiction:
Improvemessage format compatibilityVSAvoidtranslation processing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining format descriptors and transformation rules in the reference database for each messaging service. This preparation work is done in advance, so that actual message translation during operation can proceed efficiently without complex real-time processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9832146B2System and method for managing federated messagings
Publication Date: 2017.11.28 ORANGE SA
  • US9832146B2 patent drawing
  • US9832146B2 patent drawing
  • US9832146B2 patent drawing

AI summary

The invention relates to a system for managing messagings comprising a plurality of messagings and adapted for receiving and storing messages intended for at least one user furnished with a plurality of terminals for accessing said messagings. Such a system furthermore comprises: means for centralized management of any event specific to any message stored with said respective messagings; means for processing messages stored by at least one of said messagings to render said messages compatible with at least one second messaging of said plurality of messagings.