KR20130018185A - Apparatus for developing reusable interface software - Google Patents

Abstract

PURPOSE: A connection software development device for developing reusable connection software is provided to classify data into a user definition structure, and to reconstruct a topic with a form used in a combat system, thereby designing and developing a connection device. CONSTITUTION: A first connection software generation unit(110) generates first connection software connecting a first data obtaining device obtaining data for a target and a data processing device processing the data for the target. When a second data obtaining device is added, a rule generation unit generates a defined rule between the second data obtaining device and the data processing device. A second connection software development unit(120) reflects the defined rule on the first connection software. The second connection software development unit develops second connection software connecting the second data obtaining device and the data processing device. [Reference numerals] (110) First connection software generation unit; (120) Second connection software development unit; (130) Power supply unit; (140) Main control unit

Description

Apparatus for developing reusable interface software

The present invention relates to an apparatus for developing reusable interlocking software. More specifically, the present invention relates to a device for developing interlocking software for interworking between two different devices as reusable interlocking software.

In order for existing combat system systems to work with various radar or sonar systems, interlocking forces are required. However, such an interlocking stage is inconvenient to proceed separately design and development for each interlocking equipment. Moreover, similar interlocks all have to be re-developed (for example, even if something has already been developed for a sonar, this development cannot be applied to other sonars). .

The present invention has been made to solve the above problems, the data for the data from the various types of interlocking equipment using a rule-based technique to classify the data into a user-defined structure and to use in the combat system The purpose of the present invention is to propose a coordinated software development apparatus capable of reconfiguring a topic. The present invention proposes a method for developing interlocking device software that can be reused by redefining only classification rules in the companion device.

However, the objects of the present invention are not limited to those mentioned above, and other objects not mentioned can be clearly understood by those skilled in the art from the following description.

SUMMARY OF THE INVENTION The present invention has been made to achieve the above object, and includes a first interlocking software for interlocking a first data acquisition device for acquiring data for a target and a data processing device for processing data for the target. Interlocking software generation unit; A rule generation unit generating a rule defined between the second data acquisition device and the data processing device when a second data acquisition device is added; And a second interlocking software development unit for developing second interlocking software for interlocking the second data acquiring device and the data processing device by reflecting the defined rule to the first interlocking software. We propose a software development device.

Preferably, the second interlocking software development unit uses a rule including a communication scheme defined between the second data acquisition device and the data processing device as the rule.

Preferably, the first coordinated software generation unit uses the type of the target, the type of the target, the position of the target, the distance to the target, and the moving direction of the target as data for the target.

Preferably, the interlocking software development apparatus interlocks data between the first data acquiring apparatus and the data processing apparatus using the first interlocking software, or acquires the second data using the second interlocking software. The apparatus further includes a data interlocking unit for interlocking data between the apparatus and the data processing apparatus.

Preferably, when interlocking data using the first interlocking software, the data interlocking unit comprises: a message structure generating unit for generating a user defined message structure for the first data acquiring device; A data parsing unit for parsing data obtained by the first data obtaining apparatus using the message structure; A message generator configured to generate a message including the parsed data based on a communication method defined between the first data acquisition device and the data processing device; And a message transmitter for transmitting the generated message to the data processing apparatus.

Preferably, the data interlocking unit further includes a data storage unit storing the data acquired by the first data acquiring device in the form of a queue.

Preferably, the data parser uses a message structure related to an interworking standard between the first data acquisition device and the data processing device as the message structure.

The present invention can obtain the following effects by classifying data from various types of interlocking equipment into a user-defined structure using a rule-based technique and reconfiguring the topic into a form for use in a combat system. . First, design and development can be integrated for each interlocking equipment. Second, similarly developed devices can be reused for already developed ones, which reduces development costs and reduces development schedules.

1 is a block diagram schematically illustrating a reusable interlocking software development apparatus according to a preferred embodiment of the present invention.
FIG. 2 is a block diagram specifically illustrating a configuration added to the companion software development apparatus shown in FIG. 1.
3 is a conceptual diagram illustrating a linkage system between a conventional radar system and a combat system.
4 is a block diagram schematically illustrating an apparatus for developing interlocking software according to an embodiment of the present invention.
FIG. 5 is a conceptual diagram illustrating an interlocking system including the interlocking software development apparatus shown in FIG. 4.
FIG. 6 is an internal detailed view of the interlock software development apparatus shown in FIG. 5.
FIG. 7 is a block diagram illustrating an internal configuration of the system interworking module illustrated in FIG. 6.
FIG. 8 is a block diagram illustrating an internal configuration of the raw data buffer illustrated in FIG. 6.
FIG. 9 is a block diagram illustrating an internal configuration of the message parsing module illustrated in FIG. 6.
FIG. 10 is a block diagram illustrating an internal configuration of a generic DDS message transmission / reception module illustrated in FIG. 6.
FIG. 11 is a block diagram showing an internal configuration of the message structure shown in FIG.
12 is a block diagram illustrating an internal configuration of the message transmission / reception module 660 illustrated in FIG. 6.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals are used to designate the same or similar components throughout the drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. In addition, the preferred embodiments of the present invention will be described below, but it is needless to say that the technical idea of the present invention is not limited thereto and can be variously modified by those skilled in the art.

1 is a block diagram schematically illustrating a reusable interlocking software development apparatus according to a preferred embodiment of the present invention. According to FIG. 1, the reusable interlocking software development apparatus 100 (hereinafter, abbreviated as interlocking software development apparatus) may include a first interlocking software generating unit 110, a second interlocking software developing unit 120, a power supply unit 130, and the like. The main control unit 140 is included.

The first interlocking software generation unit 110 performs a function of generating first interlocking software for interlocking the first data acquisition device and the data processing device. In the above description, the first data acquisition apparatus refers to an apparatus for acquiring data for a target, and the data processing apparatus refers to an apparatus for processing data for a target.

The first interlocking software generation unit 110 may use the type of the target, the type of the target, the location of the target, the distance to the target, and the moving direction of the target as data for the target. The first data acquisition device or the second data acquisition device may be implemented as a radar or sonar. When the data acquisition apparatuses are radars, the data acquisition apparatuses acquire position, direction, and altitude as information on the target using electromagnetic waves reflected from the target. On the other hand, when the data acquisition apparatuses are sonar, the data acquisition apparatuses may acquire distance, azimuth, and the like as information on a target using ultrasonic waves reflected from the target, and target the target using different acoustic information according to the type or shape of the target. The type and shape of the can also be obtained as information about the target.

When the second data acquisition device is added, the second interlocking software development unit 120 reflects a rule defined between the second data acquisition device and the data processing device to the first interlocking software to interlock the second data acquisition device and the data processing device. It performs the function of developing the second interlocking software. As will be described later, the first data acquisition device and the second data acquisition device have the same concept as the information input device, and the data processing device has the same concept as the message processing device.

The second interlocking software development unit 120 uses a rule including a communication method defined between the second data acquisition device and the data processing device as a rule used when the second data acquisition device and the data processing device are interlocked.

The second coordinated software development unit 120 may use a rule for enabling the data processing apparatus to process data acquired by the second data acquisition apparatus as the rule. In this case, the companion software development apparatus 100 may further include a rule generator (not shown) for generating the rule. The rule generator may generate the rule, for example, including a predetermined communication scheme between the second data acquisition device and the data processing device.

The power supply unit 130 performs a function of supplying power to each component of the interlocking software development apparatus 100.

The main control unit 140 performs a function of controlling the overall operation of each component of the interlocking software development apparatus 100.

FIG. 2 is a block diagram specifically illustrating a configuration added to the companion software development apparatus shown in FIG. 1. According to FIG. 2, the companion software development apparatus 100 may further include a data linker 150.

The data interlocking unit 150 interlocks data between the first data acquisition device and the data processing device by using the first interlocking software, or data between the second data acquisition device and the data processing device by using the second interlocking software. Performs the function of interlocking.

When interlocking data using the first interlocking software, the data interlocking unit 150 stores the message structure generating unit 151, the data parsing unit 152, the message generating unit 153, the message transmitting unit 154, and the data storage. It may include a unit 155. In the present embodiment, even when data is interlocked using the second interlocking software, the data interlocking unit 150 may include the same components as described above.

The message structure generation unit 151 performs a function of generating a user-defined message structure for the first data acquisition device.

The data parsing unit 152 parses the data acquired by the first data acquiring device using the generated message structure. The data parser 152 may use a message structure related to an interworking standard between the first data acquisition device and the data processing device as the message structure.

The message generator 153 performs a function of generating a message including the parsed data based on a communication method defined between the first data acquisition device and the data processing device.

The message transmitter 154 performs a function of transmitting the generated message to the data processing device.

The data interlocking unit 150 may further include a data storage unit 155. The data storage unit 155 stores the data acquired by the first data acquisition device in the form of a queue.

As described above, the present invention proposes an apparatus for developing interlocking software for interworking between an information input apparatus such as a radar or a sonar and a message processing apparatus. Hereinafter, an embodiment of this apparatus will be described.

3 is a conceptual diagram illustrating a linkage system between a conventional radar system and a combat system.

According to FIG. 3, a message interlocked with one interlocking system 311, 312, and 313 for each interlocking end 321, 322, and 323, and a linkage with the interlocking end 321, 322, and 323 in the combat system 330. Processing units 331, 332, and 333 are provided. In the related art, interlocking units need to be developed separately for each interlocking system, and the transmission / reception message processing unit is independently developed for each device even within the combat system. When a new interlocking system 314 is added, a new interlocking unit 324 and a message processing unit 325 ) Has caused a new development.

The present invention is proposed to solve the problem according to FIG. 3, which will be described below with reference to FIGS. 4 to 6. 4 is a block diagram schematically illustrating an apparatus for developing interlocking software according to an embodiment of the present invention. FIG. 5 is a conceptual diagram illustrating an interlocking system including the interlocking software development apparatus shown in FIG. 4. FIG. 6 is an internal detailed view of the interlock software development apparatus shown in FIG. 5. First, referring to FIG. 4, an interworking device software development apparatus 400 will be described.

The interlocking device software development apparatus 400 is a reusable generic integrated interlocking device using a rule-based technique, and includes an interlocking software generation unit 410, an interworking component 420, and a power supply unit 430. And a main control unit 440. The interlocking software generating apparatus 400 may further include a message structure generating unit 450, an input information storing unit 460, an input information parsing unit 470, and a message transmitting unit 480.

The interlocking software generation unit 410 performs a function of generating interlocking software constituting interlocking between the information input device and the message processing device based on the information necessary for interlocking. Here, the information input device includes a radar, a sonar, and the like, and the message processing device is provided in, for example, a combat system.

When the new information input device is detected, the interworking configuration unit 420 includes a function related to user definition in the interlocking software to automatically configure the interworking between the new information input device and the message processing device.

The power supply unit 430 performs a function of supplying power to each component constituting the interlocking device software development apparatus 400.

The main controller 440 performs a function of controlling the overall operation of each component constituting the interlocking software development apparatus 400.

The message structure generation unit 450 performs a function of generating a user-defined message structure for each information input device.

The input information storage unit 460 stores the input information input from the first information input device which is a specific one selected from various information input devices.

The input information parser 470 parses the input information using a message structure related to the first information input device.

The message transmitter 480 transmits a message including parsed input information to a message processing apparatus.

Next, an interlocking system including the interlocking software development apparatus 400 will be described with reference to FIG. 5. In FIG. 5, the interworking system includes a combat system 530 including interworking schemes, Rule-based interworking stages 511 to 514, a user-defined message structure DB 520, and an interlocking stage send / receive client 531. Speak the system that contains. The interlocking device software development apparatus 400 of FIG. 4 refers to each interlocking end in FIG. 5.

The interworking system is a rule-based system. Rule-based system refers to a system that derives results by analyzing various input data based on predefined rules. The generic interworking stage 511 to 514 design defines a message structure satisfying the interworking scheme ICD (Interface Control Document) in the database 520. The interlocking units 511 to 514 can be used without S / W redevelopment according to the ICD, and there is no need to redevelop the transmission / reception client 531 of the combat system 530 for each new interlocking system.

Next, the internal configuration of the interlocking stage shown in FIG. 5 will be described in detail with reference to FIG. 6.

The generic interlocking end of FIG. 6 is an example of a rule-based interlocking end 511 located at the top of FIG. 5, and the other interlocking ends 512 to 514 shown in FIG. Of course.

The system interworking module 610 includes communication modules of various media (Ethernet, RS422, RS232, etc.) for transmitting and receiving information with the system 600. In addition, the system interworking module 610 selects how the user communicates with the DB. Also, the system interworking module 610 stores the received raw data in the raw data buffer 620. The system interworking module 610 has the same concept as the interlocking software generation unit 410 of FIG. 4. The row data buffer 620 has the same concept as the input information storage unit 460 of FIG. 4.

The message parsing module 630 parses the raw data buffer 620 using the message parsing structure defined in the message structure DB 650. The message parsing module 630 has the same concept as the input information parsing unit 470 of FIG. 4. The message structure DB 650 stores the message structure generated by the message structure generation unit 450 of FIG. 4.

Generic DDS message transmission and reception module 640 transforms the parsed data into a generic form for DDS transmission. The transformation changes to the generic message structure defined in the message structure DB 650. The generic DDS message transmission / reception module 640 has the same concept as the message transmission unit 480 of FIG. 4.

The message transmission / reception module 660 is provided in the combat system 530 and receives the DDS message by referring to the generic message structure in the message structure DB 650.

FIG. 7 is a block diagram illustrating an internal configuration of the system interworking module illustrated in FIG. 6. According to FIG. 7, the system interworking module 610 includes a communication interworking module 611, a raw data transmission interface 612, and a raw data reception processing module 613.

The communication interworking module 611 is a module capable of transmitting / receiving information with the interlocking system 600 using various types of communication (TCP-IP / UDP, RS232, RS422, Syncro, etc.) media according to the type of the system. .

The raw data transmission interface 612 is an interface provided externally so that raw data (linked message) can be transmitted to the interlocking scheme 600.

The raw data reception processing module 613 is a module that receives raw data from the interlocking scheme 600 and processes the data. In this case, the processed data is stored in the raw data buffer 620.

FIG. 8 is a block diagram illustrating an internal configuration of the raw data buffer illustrated in FIG. 6. According to FIG. 8, the raw data buffer 620 includes a raw data storage interface 621, a raw data queue 622, and a raw data load interface 623.

The raw data storage interface 621 is an interface provided for storing raw data in the raw data queue 622.

The raw data load interface 623 is an interface provided for loading data stored in the raw data queue 622.

The raw data queue 622 stores the data input through the storage interface 621 as raw data in a queue-type storage.

FIG. 9 is a block diagram illustrating an internal configuration of the message parsing module illustrated in FIG. 6. According to FIG. 9, the message parsing module 630 includes raw data loading 631, raw data parsing 632, message raw data conversion 633, and raw data transmission request 634.

The message raw data conversion 633 is a component that converts message information received from the generic DDS message transmission module 640 into raw data format.

The raw data transmission request 634 is a configuration for transmitting raw data generated using the raw data transmission interface of the system interworking module 610.

The raw data loading 631 is a configuration for loading raw data using the raw data loading interface of the raw data buffer 620.

Raw data parsing 632 is a configuration for transmitting the loaded raw data to the generic DDS message sending / receiving module 640 by separating the data in the form of system-linked message structure information received in the message structure 650.

FIG. 10 is a block diagram illustrating an internal configuration of a generic DDS message transmission / reception module illustrated in FIG. 6. According to FIG. 10, the generic DDS message transmission / reception module 640 converts a system interworking message to DDS message conversion 641, a DDS message transmission 642, a DDS message reception 643, and a DDS message to system interworking message conversion 644. ).

The system interlocking message to DDS message conversion 641 converts the message information received from the message parsing module 630 into a DDS message to generate a DDS message and deliver the message to the DDS message transmission 642.

The DDS message transmission 642 is a component that transmits the generated DDS message to the message transmission / reception module 660 of the combat system. Sending DDS messages 642 follows the OMG DDS standard.

The DDS message reception 643 is a component for receiving a DDS message from the message transmission / reception module 660 of the combat system. Receiving a DDS message 643 also follows the OMG DDS standard.

The DDS message to system interworking message conversion 644 converts the DDS message received from the combat system into the interworking message type of the corresponding system and delivers the message information to the message parsing module 630.

FIG. 11 is a block diagram showing an internal configuration of the message structure shown in FIG. According to FIG. 11, the message structure 650 includes an information storage interface 651 and an information query interface 652.

The information inquiry interface 652 is an interface for inquiring system interworking message structure information, DDS message structure information, and the like.

The information storage interface 651 is an interface that can create / update / delete system interworking message structure information, DDS message structure information, and the like.

12 is a block diagram illustrating an internal configuration of the message transmission / reception module 660 illustrated in FIG. 6. According to FIG. 12, the message sending / receiving module 660 performs the DDS message receiving 661, the DDS message receiving interface 662, the user screen 663, the DDS message sending interface 664, and the DDS message sending 665. Include.

The DDS message reception 661 is a component for receiving a DDS message transmitted by the generic interworking terminal. At this time, the DDS message reception 661 conforms to the OMG DDS standard.

The DDS message transmission 665 is configured to transmit message information input by the user to the Geneirc interworking terminal.

The DDS message receiving interface 662 is an interface for obtaining received DDS message information.

The DDS message transmission interface 664 is an interface for inputting data for transmitting DDS message information input by a user to the DDS.

The user screen 663 is a screen for displaying the information of the received message and transmitting the message information input by the user.

It is to be understood that the present invention is not limited to these embodiments, and all elements constituting the embodiment of the present invention described above are described as being combined or operated in one operation. That is, within the scope of the present invention, all of the components may be selectively coupled to one or more of them. In addition, although all of the components may be implemented in one independent hardware, each or some of the components of the components are selectively combined to perform some or all of the functions combined in one or a plurality of hardware It may be implemented as a computer program having a. In addition, such a computer program may be stored in a computer readable medium such as a USB memory, a CD disk, a flash memory, etc., and read and executed by a computer to implement an embodiment of the present invention. The recording medium of the computer program may include a magnetic recording medium, an optical recording medium, a carrier wave medium, and the like.

Furthermore, all terms including technical or scientific terms have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined in the Detailed Description. Terms used generally, such as terms defined in a dictionary, should be interpreted to coincide with the contextual meaning of the related art, and shall not be interpreted in an ideal or excessively formal sense unless explicitly defined in the present invention.

It will be apparent to those skilled in the art that various modifications, substitutions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims. will be. Accordingly, the embodiments disclosed in the present invention and the accompanying drawings are not intended to limit the technical spirit of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by the embodiments and the accompanying drawings. . The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

100: interlocking software development device 110: first interlocking software generating unit
120: second interlocking software development unit 130: power supply unit
140: main control unit 150: data interworking unit
151: message structure generation unit 152: data parsing unit
153: message generator 154: message transmitter
155: data storage

Claims (7)

A first interlocking software generation unit generating first interlocking software for interlocking a first data acquiring device for acquiring data for a target and a data processing device for processing data for the target;
A rule generation unit generating a rule defined between the second data acquisition device and the data processing device when a second data acquisition device is added; And
A second interlocking software development unit for developing second interlocking software for interlocking the second data acquisition device and the data processing device by reflecting the defined rule to the first interlocking software;
Reusable interlocking software development apparatus comprising a. The method of claim 1,
And the second interlocking software development unit uses a rule including a communication method determined between the second data acquisition device and the data processing device as the rule. The method of claim 1,
The first interlocking software generating unit uses the type of the target, the form of the target, the position of the target, the distance to the target, and the moving direction of the target as data for the target. Development device. The method of claim 1,
The data is interlocked between the first data acquisition device and the data processing device using the first interlocking software, or data is interposed between the second data acquisition device and the data processing device using the second interlocking software. Data linkage to link
Reusable interlocking software development apparatus further comprising a. The method of claim 4, wherein
When interlocking data using the first interlocking software, the data interlocking unit
A message structure generation unit for generating a user defined message structure for the first data acquisition device;
A data parsing unit for parsing data obtained by the first data obtaining apparatus using the message structure;
A message generator configured to generate a message including the parsed data based on a communication method defined between the first data acquisition device and the data processing device; And
Message transmission unit for transmitting the generated message to the data processing device
Reusable interlocking software development apparatus comprising a. The method of claim 5, wherein
Data storage unit for storing the data obtained by the first data acquisition device in the form of a queue
Reusable interlocking software development apparatus further comprising a. The method of claim 5, wherein
And the data parsing unit uses a message structure related to an interworking standard between the first data acquisition device and the data processing device as the message structure.

Images