Cloud Messaging Bus for Electronic Payment Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic payment infrastructure faces challenges in efficiently communicating between components due to the use of different protocols and APIs, leading to delays and difficulties in adapting to new components.
Innovation Solution
A cloud-based messaging system that receives, stores, and translates messages between components using a common protocol, allowing for efficient communication without requiring each component to know the specific protocols and APIs of others, facilitating flexible configuration of transaction processing systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different protocols and APIs are used for each component, then each component can operate independently with its own specifications, but communication between components becomes complex and difficult to adapt when new components are added
Solution Approach 1:
The patent introduces a message bus as an intermediary component that sits between different payment system components. The message bus provides a standardized communication interface that translates between different component protocols and a common message format, eliminating the need for direct protocol compatibility between components. This allows new components to be added without modifying existing components, as they all communicate through the standardized message bus interface.
2Productivity
If new components are added to the system, then system functionality and versatility are improved, but integration delays and adaptation difficulties increase
Solution Approach 1:
The message bus is designed as a universal communication infrastructure that can handle multiple types of messages and support various component types through a single standardized interface. The system uses a common message format with standardized fields that can accommodate different payment processing functions (authorizations, settlements, refunds, etc.) without requiring protocol changes. This universality allows new components to be integrated quickly by simply connecting them to the existing message bus infrastructure.
3Productivity
If each component uses its own specific protocol and API, then component design flexibility is maintained, but communication efficiency and transaction processing speed decrease
Solution Approach 1:
The patent transforms communication parameters by converting diverse component-specific protocols and APIs into a unified message bus protocol. The system changes the parameter space of communication by establishing standardized message formats, transmission protocols, and data structures that all components must adhere to when interacting through the message bus. This parameter standardization enables efficient routing, filtering, and processing of messages, significantly improving transaction processing efficiency while maintaining component design flexibility through the standardized interface.
Data Source
AI summary
A method of cloud based messaging includes receiving a message and a message topic from a message sender, storing the message topic and the message on a message queue, retrieving the message from the message queue, translating the message from a message bus protocol to a recipient protocol and transmitting the translated message to a message recipient.