Multi-Terminal Message Synchronization With Shared Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The SMS messaging system is not compatible with multi-terminal systems where multiple terminals share a common identifier, as existing systems require separate identifiers for each terminal and do not account for message distribution to multiple recipients within a multi-terminal system.
Innovation Solution
A method involving a synchronization server that facilitates message transmission from a source terminal to a recipient terminal and associated terminals sharing a common identifier, using synchronization messages to ensure all terminals within the multi-terminal system receive the message, with optional retransmission through a network node.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the conventional SMS messaging system is applied to multi-terminal systems, then each terminal behaves independently using separate identifiers, but this creates incompatibility with multi-terminal systems where multiple terminals share a common identifier
Solution Approach 1:
The patent introduces a synchronization server as an intermediary component between terminals and the messaging system. This server mediates message distribution by receiving messages from source terminals and selectively distributing them to associated terminals through synchronization messages, thereby enabling multi-terminal compatibility without requiring fundamental changes to the conventional SMS architecture
Solution Approach 2:
The synchronization server performs multiple functions: it manages message distribution to multiple terminals, handles identifier mapping between shared and unique identifiers, and coordinates synchronization between terminals. This multi-functionality allows the system to support both conventional single-terminal messaging and multi-terminal scenarios using the same infrastructure
2Adaptability or versatility
If separate MSISDN identifiers are used for each recipient terminal in the control system, then message distribution to multiple terminals is possible, but this proves incompatible with multi-terminal systems where terminals share one and the same common identifier
Solution Approach 1:
The system implements feedback mechanisms where terminals send synchronization requests to the synchronization server, which then pushes relevant messages to appropriate terminals. This feedback loop enables automatic message distribution based on terminal associations without requiring manual configuration of multiple identifiers
Solution Approach 2:
The patent uses synchronization messages that copy message content from source terminals to associated terminals. Instead of requiring separate addressing for each terminal, the system creates copies of messages through the synchronization mechanism, allowing all associated terminals to receive the same message using a single common identifier
3Productivity
If conventional SMS architecture is used, then simple message transmission between single terminals is efficient, but message distribution to multiple terminals requires separate identifiers and increases network resource consumption
Solution Approach 1:
The patent merges multiple message distribution operations into a single synchronization process. Instead of sending separate messages to each terminal individually, the system bundles messages and distributes them through synchronization mechanisms, reducing the total number of network transactions and optimizing resource usage
Data Source
AI summary
A method, a synchronization server, a corresponding terminal, and a system for transmitting a message intended for a first terminal, referred to as a destination terminal, from a second terminal, referred to as a source terminal, to at least one third terminal, referred to as an associated terminal, sharing a same identifier with the source terminal. The method includes transmitting from the source terminal to a synchronization server a first synchronization message, in which the message intended for the destination terminal is inserted, and recovering by using the at least one associated terminal the message intended for the destination terminal from the synchronization server by using at least a second synchronization message.