KR101277330B1 - Apparatus for developing reusable interface software - Google Patents

Abstract

The present invention relates to a device for developing interlocking software for interworking between two different devices as reusable interlocking software. The present invention is a communication module selected from among communication modules of different types, receives data from a first device, stores it in a buffer, and selects a communication module to be used for communication with a database among communication modules; A message parsing module that extracts a message structure related to the first device from the database and parses the data using the message structure; And a Generic DDS message transmission/reception module that converts the parsed data into a message in a designated format to enable DDS transmission, and transmits the converted message to a second device to be interlocked with the first device. Suggest the device.

Description

Reusable interlocking device software development device {Apparatus for developing reusable interface software}

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

In order for the existing combat system system to interlock with various radar systems or sonar systems, an interlocking stage is required. However, such an interlocking stage has the inconvenience of separately designing and developing each interlocking equipment. Moreover, as similar interlocking devices need to be redeveloped (for example, even if they have already been developed for the sonar, the development cost is increased and the development schedule is expensive). .

The present invention has been devised to solve the above problems, and is a form for classifying data coming from various types of interlocking equipment into a user-defined structure using a rule-based technique and using it in a battle system. It is an object of the present invention to propose an interlocking device software development device capable of reconstituting low topics. The present invention proposes a method for developing an interlocking device software that can be reused by redefining only the classification rules on the interlocking device.

However, the object of the present invention is not limited to the above-mentioned matters, and other objects not mentioned will be clearly understood by those skilled in the art from the following description.

The present invention has been devised to achieve the above object, and receives data from a first device as a communication module selected from communication modules of different types and stores it in a buffer. Among the communication modules, communication is used for communication with a database. A system interlocking module for selecting a module; A message parsing module that extracts a message structure related to the first device from a database and parses the data using the message structure; And a Generic DDS message sending and receiving module that converts the parsed data into a message in a designated format to enable DDS (Data Distribution Service) transmission, and transmits the converted message to a second device to be interlocked with the first device. We propose an interlocking device software development device.

Preferably, the first device is either a radar or a sonar, and the second device is provided in a combat system.

Preferably, the buffer, Raw Data storage interface for receiving the data; A raw data queue for storing the received data in a queue-type storage; And a raw data loading interface for loading data stored in the storage.

Preferably, the database includes: an information inquiry interface for querying a message structure related to the first device and a message structure related to the second device; And an information storage interface for creating/updating/deleting a message structure related to the first device and a message structure related to the second device.

Preferably, the Generic DDS message transmitting and receiving module receives a message to be transmitted from the second device to the first device, and the received message includes information input by a user.

delete

delete

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 reorganizing topics into a form for use in a combat system. . First, design and development can be integrated for each linked device. Second, for similar interlocking devices, ones that have already been developed can be reused, thereby reducing development costs and reducing development schedules.

3 is a conceptual diagram showing an interlocking system between a conventional radar system and a combat system.
4 is a block diagram schematically showing an interlocking device software development device according to an embodiment of the present invention.
FIG. 5 is a conceptual diagram illustrating an interlocking system including the interlocking device software development device shown in FIG. 4.
FIG. 6 is an internal detailed view of the interlocking device software development device shown in FIG. 5.
FIG. 7 is a block diagram showing the internal configuration of the system interlocking module shown in FIG. 6.
FIG. 8 is a block diagram showing the internal configuration of the Raw Data Buffer shown in FIG. 6.
FIG. 9 is a block diagram showing the internal configuration of the message parsing module shown in FIG. 6.
FIG. 10 is a block diagram showing the internal configuration of the Generic DDS message transmission/reception module illustrated in FIG. 6.
FIG. 11 is a block diagram showing the internal structure of the message structure shown in FIG. 6.
FIG. 12 is a block diagram showing the internal configuration of the message transmission/reception module 660 illustrated in FIG. 6.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. First, when adding reference numerals to the components of each drawing, it should be noted that the same components have the same reference numerals as possible even though they are displayed on different drawings. In addition, in describing the present invention, when it is determined that detailed descriptions of related well-known structures or functions may obscure the subject matter of the present invention, detailed descriptions thereof will be omitted. In addition, although preferred embodiments of the present invention will be described below, the technical spirit of the present invention is not limited to or limited thereto, and can be variously implemented by a person skilled in the art.

3 is a conceptual diagram showing an interlocking system between a conventional radar system and a combat system.

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

According to Figure 3, each linking group (321, 322, 323) for each linking system (311, 312, 313) interlocked with the combat system 330, each linking group (321, 322, 323) interlocking message The processing units 331, 332, and 333 are provided. In the related art, since the interlocking stage must be separately developed for each interlocking system, and the transmission/reception message processing unit is independently developed for each equipment in the combat system, when a new interlocking system 314 is added, the new interlocking unit 324 and the message processing unit 325 ) Followed by the inconvenience of developing a new one.

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

The interlocking device software development device 400 is a reusable generic integrated interlocking device using a rule-based technique, the interlocking software generation unit 410, the interlocking configuration unit 420, and the power supply unit 430 And a main control unit 440. The interlocking device software development device 400 may further include a message structure generation unit 450, an input information storage unit 460, an input information parsing unit 470, and a message transmission unit 480.

The interlocking software generation unit 410 performs a function of generating interlocking software constituting interworking between an information input device and a message processing device based on 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 battle system. When the information input device is a radar, the position, direction, altitude, etc. obtained using electromagnetic waves reflected from the target are input. When the information input device is a sonar, a distance, azimuth, etc. obtained using ultrasonic waves reflected from a target may be input, or a type, a form, etc. of a target acquired using different acoustic information according to the type or shape of the target may be input. You can.

The interworking component 420 automatically configures interworking between the new information input device and the message processing device by including content related to user definition in the interlock software whenever a new information input device is detected.

The power supply unit 430 functions to supply power to each component constituting the interlocking device software development device 400.

The main control unit 440 functions to control the overall operation of each component constituting the interlocking device software development apparatus 400.

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

The input information storage unit 460 performs a function of storing input information input from a first information input device which is a specific one selected from various information input devices.

The input information parsing unit 470 parses input information using a message structure associated with the first information input device.

The message transmission unit 480 transmits a message including parsed input information to a message processing device.

Next, an interlocking system including the interlocking device software development device 400 will be described with reference to FIG. 5. In FIG. 5, the interlocking system includes a combat system 530 having interlocking systems, Rule-based interlocking groups 511 to 514, a user-defined message structure DB 520, and interlocking end transmission/reception clients 531. Refers to the inclusive system. The interlocking device software development device 400 of FIG. 4 means each interlocking end in FIG. 5.

The interworking system is a rule-based system. The rule-based system means a system that derives results by analyzing various input data based on predefined rules. The message structure that satisfies the interlocking system interface control document (ICD) is defined in the database 520 through the design of the generic interlocking stages 511 to 514. The interlocking stages 511 to 514 can be used without S/W redevelopment according to ICD, and there is no need to redevelop the transmitting and receiving clients 531 of the combat system 530 for each new interlocking scheme.

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

The generic linkage of FIG. 6 is an example of the Rule-based linkage 511 located at the top in FIG. 5, and other linkages 512 to 514 shown in FIG. 5 have the same internal configuration. Of course.

The system interworking module 610 includes communication modules of various media (Ethernet, RS422, RS232, etc.) to transmit and receive information with the system 600. In addition, the system interworking module 610 selects how the user will communicate with the DB. In addition, the system interworking module 610 stores the received raw data in the raw data buffer (Raw Data Buffer) 620. The system interlocking module 610 has the same concept as the interlocking software generating unit 410 of FIG. 4. The raw data buffer 620 is of 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 generator 450 of FIG. 4.

The Generic DDS message transmission/reception module 640 transforms the parsed data into a Generic form for DDS transmission. The transformation is changed 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 a DDS message by referring to the Generic message structure in the message structure DB 650.

FIG. 7 is a block diagram showing the internal configuration of the system interlocking module shown 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 that can transmit/receive information with the interworking system 600 using various types of communication (TCP-IP/UDP, RS232, RS422, Syncro, etc.) media according to the type of system. .

The raw data transmission interface 612 is an interface provided externally to transmit the raw data (interlocked message) to the interworking system 600.

The raw data receiving processing module 613 is a module that receives raw data from the interlocking system 600 and processes the data. At this time, the processed data is stored in the Raw Data Buffer (620).

FIG. 8 is a block diagram showing the internal configuration of the Raw Data Buffer shown 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 loading interface 623 is an interface provided to load data stored in the raw data queue 622.

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

FIG. 9 is a block diagram showing the internal configuration of the message parsing module shown in FIG. 6. According to FIG. 9, the message parsing module 630 includes a raw data loading 631, a raw data parsing 632, a message raw data conversion 633, and a 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 a raw data format.

The raw data transmission request 634 is a component that transmits the raw data generated using the raw data transmission interface of the system interworking module 610.

Raw data loading 631 is a component that loads raw data using the raw data loading interface of the raw data buffer 620.

Raw data parsing 632 is a component that separates data in the form of system-linked message structure information received from the message structure 650 and transmits the loaded raw data to the Generic DDS message transmission/reception module 640.

FIG. 10 is a block diagram showing the internal configuration of the 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 641, transmits a DDS message 642, receives a DDS message 643, and converts a DDS message to a system interworking message 644 ).

The system interworking message to DDS message conversion 641 is a configuration that converts message information received from the message parsing module 630 into a DDS message type to generate a DDS message and transmits the message to the DDS message transmission 642.

The DDS message transmission 642 is a configuration that transmits the generated DDS message to the message transmission/reception module 660 of the battle system. At this time, the DDS message transmission 642 follows the OMG DDS standard.

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

The DDS message to system interworking message conversion 644 is a configuration that converts the DDS message received from the combat system into the interworking message form of the corresponding system and delivers message information to the message parsing module 630.

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

The information inquiry interface 652 is an interface capable of inquiring system-linked message structure information, DDS message structure information, and the like.

The information storage interface 651 is an interface capable of generating/updating/deleting system linkage message structure information, DDS message structure information, and the like.

FIG. 12 is a block diagram showing the internal configuration of the message transmission/reception module 660 illustrated in FIG. 6. According to FIG. 12, the message transmission/reception module 660 receives DDS message reception 661, DDS message reception interface 662, user screen 663, DDS message transmission interface 664, and DDS message transmission 665. Includes.

The DDS message reception 661 is a configuration for receiving the DDS message transmitted by the Generic interworking end. At this time, the DDS message reception 661 complies with the OMG DDS standard.

The DDS message transmission 665 is a configuration that transmits message information input by the user to the Geneirc linkage terminal.

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

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

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

The fact that all components constituting the embodiments of the present invention described above are described as being combined or operated as one, the present invention is not necessarily limited to these embodiments. That is, within the object scope of the present invention, all of the components may be selectively combined and operated. Further, although all of the components may be implemented by one independent hardware, a part or all of the components are selectively combined to perform a part or all of 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 is stored in a computer readable recording medium (Computer Readable Media), such as a USB memory, CD disk, flash memory, etc., and read and executed by a computer, thereby implementing 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.

In addition, all terms, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the present invention pertains, unless otherwise defined in the detailed description. Commonly used terms, such as predefined terms, should be interpreted as being consistent with the contextual meaning of the related art, and should not be interpreted as an ideal or excessively formal meaning unless explicitly defined in the present invention.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains may make various modifications, changes, and substitutions without departing from the essential characteristics of the present invention. will be. Therefore, 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 explain the scope of the technical spirit of the present invention. . The scope of protection of the present invention should be interpreted by the claims below, and all technical spirits within the scope equivalent thereto should be interpreted as being included in the scope of the present invention.

400: interlocking device software development device 410: interlocking software generation unit
420: interlocking component 430: power supply
440: main control unit 450: message structure generation unit
460: input information storage unit 470: input information parsing unit
480: message transmission unit

Claims (7)

A system interworking module that receives data from a first device as a communication module selected from communication modules of different types and stores it in a buffer, and selects a communication module to be used for communication with a database among the communication modules;
A message parsing module that extracts a message structure related to the first device from a database and parses the data using the message structure; And
Generic DDS message sending/receiving module that converts parsed data into a message of a designated type to enable DDS (Data Distribution Service) transmission, and transmits the converted message to a second device to interwork with the first device
Interlocking device software development device comprising a. According to claim 1,
The buffer,
A raw data storage interface for receiving the data;
A raw data queue for storing the received data in a queue-type storage; And
Raw data loading interface to load data stored in the storage
Interlocking device software development device comprising a. According to claim 1,
The database,
An information inquiry interface for querying a message structure related to the first device and a message structure related to the second device; And
Information storage interface for creating/updating/deleting a message structure related to the first device and a message structure related to the second device
Interlocking device software development device comprising a. According to claim 1,
The Generic DDS message transmission/reception module receives a message to be transmitted from the second device to the first device, and the received message includes information input by a user. delete delete delete

Images