SOA Message Converter for Heterogeneous Communication Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-homogenous communication systems between entities of different technological infrastructures hinder seamless communication, leading to manual processing, additional costs, and exclusion of entities with incompatible IT systems, especially between large and small enterprises.
Innovation Solution
An enterprise resource platform (ERP) system that determines an output channel for service-oriented architecture (SOA) service requests, converts them into formats associated with the receiving entity, and selects templates with predefined semantics for transmission, enabling communication across different communication systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If standard communication protocols (SOA) are used for system internal communications, then communication efficiency and automation are improved, but compatibility with entities using non-standard communication systems deteriorates
Solution Approach 1:
The patent introduces a message converter as an intermediary component that translates between SOA service request format and entity-specific communication formats. The converter receives standardized SOA service requests and automatically converts them into appropriate formats (SMS, MMS, fax, email) based on the target entity's communication capabilities, enabling seamless communication between homogeneous SOA systems and heterogeneous external entities without manual intervention
Solution Approach 2:
The system dynamically changes communication parameters including message format, transmission channel, and semantic representation based on the target entity's classification. The message converter adjusts these parameters automatically by selecting appropriate templates and semantics from predefined sets, allowing the same SOA service request to be transmitted through multiple different communication channels with different formats as needed
2Adaptability or versatility
If manual processing is used for non-homogenous communication systems, then compatibility is maintained, but processing time and costs increase
Solution Approach 1:
The message converter operates autonomously to perform format conversion and message transmission without requiring manual human intervention. The system automatically determines the appropriate output channel based on entity classification, selects suitable templates and semantics, converts the message format, and transmits through the selected channel, thereby eliminating manual processing steps while maintaining compatibility across different communication systems
Solution Approach 2:
The system performs preliminary actions by pre-defining multiple output channels, templates, and semantics before actual communication occurs. Entity classifications and corresponding communication preferences are established in advance, allowing the message converter to quickly retrieve and apply the appropriate conversion rules when processing SOA service requests, significantly reducing processing time compared to ad-hoc manual conversion
3Adaptability or versatility
If manual conversion of communication formats is performed, then compatibility between different systems is achieved, but operational complexity and costs increase
Solution Approach 1:
The message converter is designed as a universal component that handles multiple communication formats (SMS, MMS, fax, email) through a single integrated system. It maintains a repository of multiple templates and semantics that can be selectively applied based on the target entity's requirements, eliminating the need for separate manual conversion processes for each communication type and reducing operational complexity
Solution Approach 2:
The conversion process is made dynamic and adaptive rather than static and rigid. The message converter automatically adjusts its behavior based on real-time inputs including entity classification, available output channels, and message content. This dynamic selection of templates and semantics simplifies operations by eliminating the need for manual configuration and decision-making for each conversion task
4Extent of automation
If standardized SOA services are used, then automation and efficiency are improved, but exclusion of entities with incompatible IT systems occurs
Solution Approach 1:
The message converter serves as an intermediary that bridges the gap between automated SOA service requests and diverse external entities with incompatible IT systems. It automatically translates standardized service requests into entity-specific formats and handles responses back to the SOA system, thereby including entities that would otherwise be excluded from automated communication while maintaining the automation benefits of SOA architecture
Solution Approach 2:
The system dynamically changes communication parameters including format, channel, and semantic representation based on the target entity's capabilities. By automatically adjusting these parameters according to entity classification and available output channels, the system maintains high automation levels while adapting to include entities with varying IT infrastructures, from SMS-capable mobile devices to email systems and fax machines
Data Source
AI summary
Selecting an output channel, from a plurality of output channels of a communication system associated with a database management system, for transmission of an entity document to an entity from the database management system. The determining based on an entity classification of the entity within the database management system. Responsive to receiving a service-orientated-architecture service request for the entity at the database management system, the service-orientated-architecture (SOA) service request is converted to a message having a format associated with the entity classification of the entity. Converting the SOA includes selecting, based on a content of the SOA service request, a template, having a predefined set of semantics, associated with the entity classification of the entity, selecting a semantic that corresponds to the SOA service request, and transmitting the message with the selected semantic through the output channel.