Distributed Message Queue for Scalable SMS Transfer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current SMS message transfer systems face limitations due to hardware costs, scalability issues, and inefficiencies in software-based systems, which restrict their ability to handle large volumes of messages and implement modern protocols effectively.

Innovation Solution

A distributed message transfer system with a message queue architecture that allows for scalable, efficient, and flexible message processing across multiple servers and geographical domains, utilizing JSON formatting for efficient message translation and handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware-based SMS systems are used, then reliability is improved, but device complexity and cost increase

Engineering Contradiction:

Improvemessage transfer reliabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces hardware-based SMS gateways with a software-based message transfer system that runs on standard server infrastructure. The message transfer node implements SMS protocol handling entirely in software, eliminating the need for specialized telecommunications hardware while maintaining message transfer functionality.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The message transfer node is designed to handle multiple messaging protocols (SMS, MMS, email, chat) and can serve multiple carriers and applications simultaneously. This universal design allows a single software platform to replace multiple specialized hardware systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Device complexity

If software-based message transfer systems are implemented, then device complexity is reduced, but productivity and scalability worsen

Engineering Contradiction:

Improvesystem complexityVSAvoidmessage processing capacity

Core Design Contradiction:

Device complexityVSProductivity

Solution Approach 1:

The system architecture divides message processing into independent message transfer nodes that can be distributed across multiple servers. Each node handles specific message queues and can be scaled independently, allowing the software system to achieve high throughput and capacity comparable to hardware systems.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a message queue as an intermediary component between message sources and destinations. This queue-based architecture enables asynchronous message processing, buffering high-volume message flows, and decoupling system components to improve overall productivity and scalability.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If traditional message transfer systems are used, then ease of operation is maintained, but adaptability to modern protocols worsens

Engineering Contradiction:

Improvesystem operabilityVSAvoidprotocol compatibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The message transfer node is designed with multi-protocol support, capable of handling SMS, MMS, email, and various chat protocols simultaneously. This universal architecture maintains ease of operation through a unified interface while providing broad adaptability to different messaging standards and carriers.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system employs dynamic protocol routing and adaptive message handling that can adjust to different protocol requirements in real-time. The message transfer node dynamically selects appropriate processing paths based on message type, carrier requirements, and destination, maintaining operational simplicity while supporting diverse protocols.

Inventive Principle:

Principle #15Dynamics

4Productivity

If distributed message queue architecture is implemented, then productivity and scalability are improved, but device complexity increases

Engineering Contradiction:

Improvemessage processing capacityVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The message queue is segmented into multiple distributed queues across different servers, with each queue handling specific message types or carrier routes. This segmentation enables parallel message processing, improving productivity while keeping individual queue components manageable in complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent combines multiple distributed message transfer nodes into a unified system managed by a central configuration and monitoring platform. This merging approach allows the system to leverage the scalability of distributed architecture while maintaining operational simplicity through centralized control and standardized interfaces.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10178162B2Message transfer system, method of transferring messages and software product

Publication Date: 2019.01.08 WEBTEXT HLDG

AI summary

A message transfer system, method of transferring message and a software product. A message transfer system (10) comprising:an interface to a send agent (70), arranged to facilitate an input of an at least one message to the message transfer system,an interface to a delivery agent (80), arranged to facilitate an output of the at least one message from the message transfer system,a message queue, arranged to facilitate a processing of the at least one message through the message transfer system (10) between the interface to a send agent (70) and the interface to a delivery agent (80),wherein,the message transfer system (10) further comprises a message transfer node (20 22 23 24 25 26 27), arranged to comprise the message queue (90) such that the message queue (90) is arranged as distributed.