Heterogeneous data translation system

• US 5,339,434 A
• Filed: 12/07/1992
• Issued: 08/16/1994
• Est. Priority Date: 12/07/1992
• Status: Expired due to Fees

• Current Assignee: TRW Limited (Zeppelin - Stiftung der Stadt Friedrichshafen)
• Original Assignee: TRW Limited (Zeppelin - Stiftung der Stadt Friedrichshafen)
• Inventors: Rusis, Edvin A.
• Primary Examiner(s): Heckler, Thomas M.
• Application Number:
  US07/986,214
• Time in Patent Office: 617 Days
• Field of Search: 364/DIG. 1 MS File, 395/700
• US Class Current: 709/246
• CPC Class Codes: H04L 69/06 Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus facilitating the exchange of data between application programs written in a higher level language and running on separate heterogeneous computer platforms, without concern for possible differences in internal data formats in the separate platforms. Each message format to be the subject of exchange among heterogeneous computer platforms is preregistered with each such platform by writing and executing a computer program that contains a definition of the message format in the higher level language. Preregistration produces a message description file in each platform, which is used at initialization time to generate a field descriptor tree in each platform. When a message is to be transmitted, it is first translated to a universal meta format, making use of the field descriptor tree, and on receipt at another platform is translated back to the native format of the receiving platform. Thus, data messages are exchanged without concern for the internal data formats used by the separate platforms.

Claims

1. A method for exchanging data between application programs running on heterogeneous computer platforms having different internal data formats, the method comprising the steps of:

preregistering each message format with each of the platforms that will be involved in the exchange of data, wherein the step of preregistering a message format generates a definition of the message format in a message description file;

initializing each platform to contain field descriptors for each message format preregistered with the platform, wherein the initializing step uses the message descriptor files to generate the field descriptors, and each field descriptor completely defines a field in the message format;

prior to transmission of a message from a platform, translating the message from its native format to a meta format, using the field descriptors obtained from preregistering the message format;

transmitting the message in meta format from one platform to another;

receiving the message at another platform; and

translating the received message from the meta format to the native format of the receiving platform, using the field descriptors obtained from preregistering the message format, whereby application programs running on heterogeneous platforms can communicate without regard to possible differences in internal message and memory formats.

2. A method as defined in claim 1, wherein the step of preregistering each message format includes:

writing a program that includes a definition of each message format to be involved in communication between platforms;

compiling and executing the program on each platform, to produce a message description file; and

storing the message description file for later use.

3. A method as defined in claim 2, wherein the initializing step includes:

retrieving the stored message description file; and

generating a memory-resident field descriptor tree from the message description file, for use during the translating steps.

4. A method as defined in claim 1, wherein the step of translating to a meta format includes:

converting, if necessary, each field of the message to a meta field that is fixed in length for each data type except for character data, and is large enough to accommodate any message field of that type; and

assembling the converted meta fields into a continuous data stream without gaps.

5. A method as defined in claim 4, wherein the step of converting each field of the message to a meta field includes:

converting integer based message fields to four-byte meta fields with the least significant bit appearing first;

converting floating-point message fields to meta fields of 128 bits in length, including a 16-bit exponent and a 112-bit fraction, each with the most significant bit appearing first.

6. Apparatus for exchanging data between application programs running on heterogeneous computer platforms having different internal data formats, the apparatus comprising:

means for preregistering each message format with each of the platforms that will be involved in the exchange of data, wherein the means for preregistering a message format generates a definition of the message format in a message description file;

means for initializing each platform to contain field descriptors for each message format preregistered with the platform, wherein the means for initializing uses the message descriptor files to generate the field descriptors, and each field descriptor completely defines a field in the message format;

for use prior to transmission of a message from a platform, means for translating the message from its native format to a meta format, using the field descriptors obtained from preregistering the message format;

means for transmitting the message in meta format from one platform to another;

means for receiving the message at another platform; and

means for translating the received message from the meta format to the native format of the receiving platform, using the field descriptors obtained from preregistering the message format, whereby application programs running on heterogeneous platforms can communicate without regard to possible differences in internal message and memory formats.

7. Apparatus as defined in claim 6, wherein the means for preregistering each message format includes:

means for compiling and executing a program written to include a definition of each message format to be involved in communication between platforms, to produce a message description file; and

means for storing the message description file for later use.

8. Apparatus as defined in claim 7, wherein the means for initializing includes:

means for retrieving the stored message description file; and

means for generating a memory-resident field descriptor tree from the message description file, for use by the means for translating.

9. Apparatus as defined in claim 6, wherein the means for translating the message to a meta format includes:

means for convening, if necessary, each field of the message to a meta field that is fixed in length for each data type except for character data, and is large enough to accommodate any message field of that type; and

means for assembling the converted meta fields into a continuous data stream without gaps.

10. Apparatus as defined in claim 9, wherein the means for converting each field of the message to a meta field includes:

means for convening integer based message fields to four-byte meta fields with the least significant bit appearing first;

means for convening floating-point message fields to meta fields of 128 bits in length, including a 16-bit exponent and a 112-bit fraction, each with the most significant bit appearing first.