Automated tactical datalink translator

• US 8,144,730 B2
• Filed: 12/13/2005
• Issued: 03/27/2012
• Est. Priority Date: 12/13/2005
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Maleport, Joel J., Resnik, Bryan P.
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): Hsiung, Hai-Chang
• Application Number:
  US11/301,453
• Publication Number:
  US 20070133601A1
• Time in Patent Office: 2,296 Days
• Field of Search: 370/466, 370/467, 717108-113
• US Class Current: 370/467
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

An automated system for translating datalink information and producing a computer code based on the translated datalink information. The computer code may subsequently be used to establish datalink communications between pieces of equipment having different communication protocols. The automated production of computer code reduces time and errors during software development for applications used in communicating between different datalinks.

Claims

1. A method for providing automated data translations for information to be transmitted between differing datalinks used in communications between various pieces of equipment, the method comprising:

storing specification requirements for a plurality of the differing datalinks in a data storage medium;

receiving information associated with a first datalink and a second datalink of the plurality of datalinks for translation by a translator;

converting the received information into metadata using the stored specification requirements for the first datalink and the second datalink;

matching terms in the metadata by a computing system;

mapping by the computing system constructs that are common between protocols associated with the first datalink and the second datalink based on the matched terms, wherein the common constructs include dissections of the protocols into a message and a field;

generating by the computing system datalink communication source code using the mapped common constructs, the generated datalink communication source code for facilitating communication between the first datalink and the second datalink;

combining the datalink communication source code with an application code to form an executable application; and

loading the executable application onto at least two pieces of equipment.

2. The method of claim 1, wherein storing specification requirements occurs using a graphical user interface.

3. The method of claim 1, wherein receiving information occurs using a graphical user interface.

4. The method of claim 1, wherein the translation step utilizes a plurality of conversion factors.

5. The method of claim 4, wherein the plurality of conversion factors are stored in the data storage medium.

6. The method of claim 1, wherein the data storage medium is a database.

7. The method of claim 1, wherein the specification requirements are tactical datalink definitions.

8. A non-transitory computer readable storage medium storing a computer readable program for providing automated data translations for use in maintaining communications across differing datalinks, said computer readable program being configured to operate a computer to:

store specification requirements for a plurality of differing datalinks in a data storage medium;

receive information associated with a first data link and a second datalink of the plurality of datalinks to be translated by a translator;

convert the received information into metadata using the stored specification requirements for the first datalink and the second datalink;

match terms in the metadata;

map constructs that are common between protocols associated with the first datalink and the second datalink based on the matched terms, wherein the common constructs include dissections of the protocols into a message and a field;

automatically generate datalink communication source code using the mapped common constructs, the generated datalink communication source code for use in facilitating communication between the first datalink and the second datalink;

combine the datalink communication source code with an application code to form an executable application; and

load the executable application onto at least two pieces of equipment.

9. The computer readable storage medium of claim 8, wherein the data storage medium is a database.

10. The computer readable storage medium of claim 8, wherein the specification requirements are tactical datalink definitions.

11. A computer system for generating an executable application for use in datalink communications, the system comprising:

a database for storing specification information for a plurality of different datalinks;

a translator for;

receiving information indicating translation is required between a first datalink and a second datalink of the plurality of datalinks;

converting the specification information associated with the first datalink into first metadata and the specification information associated with the second datalink into second metadata;

matching terms in the metadata; and

automatically generating datalink communication source code using constructs that are common between protocols associated with the first and second metadata based on the matched terms, wherein the constructs include dissections of the protocols into a message and a field; and

a compiler for combining the datalink communication source code and application code created by a software developer to form an executable application providing communication between the first datalink and the second datalink, wherein the executable application is loaded onto at least two pieces of equipment.

12. The system of claim 11 further comprising a graphical user interface for inputting specification information and indicating translation is required between the first datalink and the second datalink.

13. The system of claim 11, wherein a plurality of conversion factors are stored in the database.

14. The system of claim 11, wherein the converting step and generating step are automated.