Messaging System Protocol Conversion via Program Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging systems face complexity and incompatibility issues when handling messages between systems operating on different protocols, leading to unmanageable interconnections and the need for reconfiguration with each change or addition, especially when coordinating data between multiple systems with varying formats and capabilities.
Innovation Solution
A method and apparatus that convert input messages from multiple protocols into a common protocol using program data stored in a program data store, creating message objects with labels for input ports, specifying processes and destinations, and enabling conversion between protocols for processing, sharing processing facilities, and handling exceptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If systems use different message formatting protocols to meet specific user requirements and interface with different equipment, then system adaptability and versatility are improved, but device complexity and the number of required interfaces increase significantly
Solution Approach 1:
The patent introduces a messaging system that acts as an intermediary between systems using different protocols. The system includes a message receiver that accepts messages from various sources, a message converter that transforms messages between different protocols, and a message sender that delivers converted messages to destination systems. This mediator architecture allows systems to maintain their own protocols while achieving interoperability through the conversion layer, thus improving adaptability without proportionally increasing interface complexity.
Solution Approach 2:
The messaging system is designed with universal components that can handle multiple protocols and message types. The message converter can transform between different protocols, and the system can route messages to multiple destinations. This multi-functional design allows a single system to interface with various equipment using different protocols, reducing the need for separate dedicated interfaces for each protocol combination.
2Adaptability or versatility
If the number of systems requiring interconnection increases, then system versatility is improved, but the number of required interfaces and reconfiguration effort increase exponentially
Solution Approach 1:
The messaging system serves as a central intermediary that manages all interconnections between systems. Instead of requiring direct interfaces between every pair of systems (n(n-1) interfaces), all communication goes through the messaging system which handles protocol conversion and routing. This reduces the number of required interfaces from exponential to linear growth with the number of systems.
Solution Approach 2:
The system uses message templates and conversion rules that can be copied and reused across multiple system interactions. Once a protocol conversion rule is established for a particular protocol pair, it can be reused for multiple message exchanges and even adapted for similar protocol variations, reducing the configuration effort for adding new systems.
3Adaptability or versatility
If protocol conversion is implemented to enable message coordination, then system interoperability is improved, but processing complexity increases
Solution Approach 1:
The protocol conversion process is segmented into distinct functional components: message reception, message conversion, and message sending. Each component handles a specific aspect of the conversion process, making the overall complex task manageable through modular processing. The message converter is further segmented into protocol-specific conversion routines that can be independently developed and maintained.
Data Source
AI summary
Input messages are received at respective ports (10, 11, 12) of a message controller 4 from a plurality of external devices (100, 110, 120) which use different protocols. When an incoming message arrives at an input port a message object is created, the message object including a label identifying the respective input port. The conversion and subsequent handling of the messages uses program data which is retrieved from a program data store (5) according to the label indicating the input port. The program data retrieved is thus specified by the input port and allows conversion of messages into a common protocol to allow subsequent processing of the messages. This architecture allows the same program data to be called for external devices using the same protocol. Other processes may also be called from the program data store, covering functions such as validation, data enrichment, and exception handling processes.