Message Interchange Gateway for Cross-Protocol Session Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging systems are often incompatible due to differences in protocol orientation (stateless vs. session-oriented) and proprietary implementations, preventing message exchange between different systems.
Innovation Solution
A message interchange gateway (MIG) system that includes an ingress module, session manager, message queue, and session handlers to facilitate message transfer between disparate messaging systems, enabling communication between stateless and session-oriented systems, as well as systems using different protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If messaging systems use different protocols or proprietary implementations, then each system can be optimized for its specific functionality, but message exchange between different systems becomes impossible
Solution Approach 1:
The patent introduces a gateway system that acts as an intermediary between different messaging systems. The gateway receives messages from one messaging system, translates them into the appropriate format and protocol for the target system, and forwards them. This mediator approach enables message exchange between incompatible systems without requiring changes to the original systems, thus resolving the contradiction between maintaining system optimization and enabling cross-system communication.
Solution Approach 2:
The gateway is designed with multi-functionality to handle multiple messaging systems and protocols simultaneously. It can adapt to different message formats, session management approaches (stateless vs session-oriented), and protocol variations. This universal design allows a single gateway to facilitate communication across diverse messaging systems, enabling message exchange capability without requiring separate solutions for each system pair.
2Ease of operation
If a messaging system is stateless, then it has simpler architecture and easier operation, but it cannot properly communicate with session-oriented systems where messages need to be threaded and associated
Solution Approach 1:
The gateway acts as a protocol translator and adapter between stateless and session-oriented messaging systems. When a message arrives from a stateless system, the gateway creates appropriate session context and threading for the session-oriented target system. Conversely, when receiving from a session-oriented system, the gateway extracts and forwards only the necessary message content without session context to the stateless system. This mediation enables protocol compatibility while preserving the operational simplicity of each system's native approach.
Solution Approach 2:
The gateway dynamically changes message parameters including format, structure, and contextual information based on the target system's requirements. For session-oriented systems, it adds session identifiers, message threading information, and contextual parameters. For stateless systems, it removes or simplifies these parameters. This parameter transformation enables the same message content to be compatible with different protocol requirements without changing the core messaging functionality.
3Reliability
If messaging systems are designed with proprietary implementations, then they can be optimized for specific supplier requirements, but they become unable to exchange messages with third party systems
Solution Approach 1:
The gateway serves as a proprietary-implementation-agnostic intermediary that interfaces with multiple different messaging systems. It maintains reliable communication with each proprietary system using their native protocols while simultaneously providing standardized cross-system message exchange capabilities. This allows each system to retain its optimized proprietary implementation for reliable operation while the gateway enables adaptability for inter-system communication.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A message interchange gateway for transferring messages between a first party and a second party includes an ingress module, arranged to accept at least one message from the first party, a session manger arranged to accept the at least one message from the ingress module, the session manager being further arranged in co-operation with a storage device having data, a message queuing module having at least one session-based message queue, and at least a first session handler having a first session. The first session handler is arranged in co-operation with a first session- based message queue for the processing of the at least one message according to an instruction from the session manager. The instruction is at least partially based on the data, and the first session handler is further arranged to dispatch, after processing, the at least one message from the first session-based message queue to the second party.