HLA to XML Conversion Bridge Using Schema Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional communication between XML or JMS components and HLA components requires a bridge for translation, necessitating new Java code for each new message type, which is inefficient and cumbersome.
Innovation Solution
A method that establishes connections to HLA and ESB, subscribes to channels, receives XML documents defining message formats, extracts data from HLA and XML messages, and converts them between formats without requiring additional code by using appropriate XML documents.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a bridge is used to translate between XML/JMS and HLA message formats, then communication between different services is enabled, but new Java code must be created for each new message type which is inefficient and cumbersome
Solution Approach 1:
The patent uses XML schema documents as templates that define the structure and format of messages. Instead of writing custom Java code for each message type, the system copies and reuses the schema document format to describe different message types, allowing the bridge to automatically generate translation logic based on these schema templates.
Solution Approach 2:
The patent changes the approach from code-based configuration to data-based configuration. By using XML schema documents with parameters like element names, data types, and structures, the system allows dynamic adaptation to new message types by simply providing new schema documents rather than modifying Java code.
2Reliability
If traditional bridge translation is used between XML/JMS and HLA, then message format conversion is achieved, but the process requires manual Java code creation for each message type
Solution Approach 1:
The bridge automatically generates translation logic by reading and parsing XML schema documents. The system serves itself by using the schema documents to configure its own translation behavior, eliminating the need for manual Java code creation for each new message type while maintaining accurate field mapping.
Solution Approach 2:
XML schema documents are created in advance to define the structure of messages before actual translation occurs. This preliminary definition of message formats allows the bridge to prepare translation rules ahead of time, improving both accuracy and speed when actual message translation is needed.
3Manufacturing precision
If new Java code is created for each new message type in the bridge, then precise field mapping is achieved, but the development process becomes inefficient and cumbersome
Solution Approach 1:
The patent introduces XML schema documents as an intermediary layer between the message formats and the bridge translation logic. These schema documents serve as a middle language that precisely defines field mappings and structures without requiring direct Java code, thereby maintaining precision while simplifying the development process.
Data Source
AI summary
A method includes establishing a connection and subscribing to at least one channel of a High Level Architecture (HLA) federation and an Enterprise Service Bus (ESB). The method further includes receiving a text file defining the format of an HLA message; a first extensible Markup Language (XML) document conforming to a first schema that defines data within a first message type; and a second XML document conforming to a second schema that defines data within a second message type. The method further includes receiving a first HLA message over the at least one HLA channel, extracting at least one piece of data from the first HLA message, generating a first XML message, and publishing the first XML message over the at least one ESB channel. The method also includes receiving a second XML message over the at least one ESB channel, extracting at least one piece of data from the second XML message, generating a second HLA message conforming to the text file, and publishing the second HLA message over the at least one HLA channel.