KR20220022338A - System and method of building electronic warfare warning library - Google Patents

Abstract

Disclosed are a system and method for building an electronic warfare threat library. According to an embodiment of the present invention, the method may comprise: a step of designing and creating a threat library structure; a step of verifying the created threat library structure; a step of creating a threat library file based on the verified threat library structure; and a step of verifying the threat library file.

Description

Electronic warfare threat library construction system and electronic warfare threat library construction method {SYSTEM AND METHOD OF BUILDING ELECTRONIC WARFARE WARNING LIBRARY}

The present invention relates to an electronic warfare threat library construction system and an electronic warfare threat library construction method.

Electronic warfare is a general term for military activities that disrupt enemy networks, radars, and communications to inflict damage and secure the information superiority of friendly forces. Among the electronic warfare classifications, the Electronic Support (ES) field analyzes the characteristics of the collected enemy threat signal and compares the analysis result with the threat library to identify the type (characteristics) of the enemy threat. The electronic warfare threat library has a data structure that is dependent on the type (characteristic) of the enemy threat to be counteracted to the type (characteristic) of the response equipment mounted on the system, and provides extensive threat information throughout the system, such as mission planning, mission performance, and maintenance. should manage Each function such as electronic warfare threat library creation, management and input/output is used in electronic warfare ES equipment support software, operation software, and maintenance software.

In the conventional electronic warfare ES equipment development process, documents are mainly used to unify the threat library structure among various software. Each developer checks the document and manually develops or modifies the software according to the structure.

However, the conventional electronic warfare threat library-related software does not sufficiently reflect these characteristics, and it is difficult to port and reuse the functional module of the same software to other systems. There is a problem that a lot of effort and time are required to do this. In other words, in the case of the method of unifying the structure of the electronic warfare threat library through the conventional document, when a change occurs in the structure of the threat library, each software developer needs to check the document again and reflect it in each software, so a quick response is possible. it's difficult. In addition, when the environment such as the operating system and CPU in which each implemented software operates is different, there is a problem in that portability is not considered, such as newly implemented and used in each environment despite the same function. In addition, there is a problem in that reusability in similar businesses in the future is poor due to implementation dependent on the structure of the threat library used in the corresponding business.

The present invention provides an electronic warfare threat library construction software framework for the library of the types (characteristics) of the enemy threats to be counteracted in the actual operation of the electronic warfare equipment in a systematic structure and converting it into a form that can be loaded into the actual equipment. It is possible to provide an electronic warfare threat library construction system and an electronic warfare threat library construction method.

According to an embodiment of the present invention, a method for building an electronic warfare threat library in an electronic warfare threat library construction system may be disclosed. A method of constructing an electronic warfare threat library according to an embodiment includes the steps of designing and creating a threat library structure; verifying the created threat library structure; creating a threat library file based on the verified threat library structure; and verifying the threat library file.

In an embodiment, the method of constructing the electronic warfare threat library may further include receiving the threat library structure.

In an embodiment, designing and creating the threat library structure includes: defining a plurality of unit objects to be used in the threat library structure; defining a relationship between the plurality of unit objects to be linked when the threat library file is created; defining a holding variable of the plurality of unit objects; and defining variable activation conditions of the plurality of unit objects.

In an embodiment, the defining of the holding variables of the plurality of unit objects includes: defining a plurality of variables held by each of the plurality of unit objects; and editing a characteristic of each of the plurality of variables.

In an embodiment, the defining of the variable activation condition of the unit object includes: defining an activation condition of a plurality of variables of each of the plurality of unit objects; and editing a characteristic of the activation condition.

In one embodiment, the electronic warfare threat library construction method may further include receiving the threat library file.

In an embodiment, the step of creating a threat library file based on the verified threat library structure includes: adding a plurality of unit objects to be included in the threat library file; performing a connection between the plurality of unit objects; editing a plurality of variables of each of the plurality of unit objects; and generating information to be additionally included in the threat library file.

In an embodiment, the connecting between the plurality of unit objects may include: detecting a plurality of unit objects related to each other from the plurality of unit objects; and connecting the plurality of unit objects related to each other.

In an embodiment, the editing of the plurality of variables of each of the plurality of unit objects may include modifying values of the plurality of variables held by each of the plurality of unit objects.

In one embodiment, the electronic warfare threat library construction method may further include outputting the threat library file.

In an embodiment, outputting the threat library file may include outputting the threat library file as any one of a file for charging, conversion, and reporting.

According to an embodiment of the present invention, an electronic warfare threat library construction system may be disclosed. An electronic warfare threat library construction system according to an embodiment includes: a threat library structure processing unit for designing and creating a threat library structure and verifying the created threat library structure; a threat library file processing unit that creates a threat library file based on the verified threat library structure and verifies the threat library file; and an output unit for outputting the threat library file.

In an embodiment, the electronic warfare threat library construction system may further include a receiving unit for receiving the threat library structure.

In an embodiment, the threat library structure processing unit defines a plurality of unit objects to be used in the threat library structure, defines a relationship between the plurality of unit objects to be connected when the threat library file is created, and the plurality of A holding variable of a unit object of , and a variable activation condition of the plurality of unit objects may be defined.

In an embodiment, the threat library structure processing unit may define a plurality of variables owned by each of the plurality of unit objects, and edit characteristics of each of the plurality of variables.

In an embodiment, the threat library structure processing unit may define activation conditions for a plurality of variables of each of the plurality of unit objects, and edit characteristics of the activation conditions.

In an embodiment, the receiving unit may receive the threat library file.

In an embodiment, the threat library structure processing unit adds a plurality of unit objects to be included in the threat library file, performs a connection between the plurality of unit objects, and edits a plurality of variables of each of the plurality of unit objects and create information to be additionally included in the threat library file.

In an embodiment, the threat library structure processing unit may detect a plurality of unit objects related to each other from the plurality of unit objects, and connect the plurality of unit objects related to each other.

In an embodiment, the threat library structure processing unit may modify values of a plurality of variables held by each of the plurality of unit objects.

In an embodiment, the output unit may output the threat library file as any one file among a use for charging, a use for conversion, and a use for reporting.

In an embodiment, the electronic warfare threat library construction system may further include a storage unit for storing the threat library structure and the threat library file.

According to various embodiments of the present invention, the designed threat library structure can be managed in the form of XML that can be used as input to other parts. Therefore, if the structure of the threat library is changed due to changes in requirements in the future, if the user only modifies the XML file, the change can be automatically reflected in other functions, thereby preventing accidental errors. In addition, the development period can be shortened.

In addition, file input/output can be performed based on the threat library structure. Through this, whole or partial fileization may be possible, and the management of the threat library file may be efficiently performed.

In addition, even if the structure of the threat library is partially changed, it is possible to provide a function to convert and load an existing threat library file, thereby reducing the time to create a threat library, which takes a lot of time and effort.

In addition, it can be used in the development and operation of electronic warfare ES equipment that requires functions such as threat library creation, management, and input/output.

1 is a block diagram schematically showing an electronic warfare threat library construction system according to an embodiment of the present invention.
2 is an exemplary diagram illustrating the structure of a threat library according to an embodiment of the present invention.
3 is an exemplary diagram illustrating the structure of a threat library according to another embodiment of the present invention.
4 is a flowchart illustrating a method of building an electronic threat library according to an embodiment of the present invention.
5 is a flowchart illustrating a method of creating a threat library structure according to an embodiment of the present invention.
6 is an exemplary diagram illustrating a threat library structure after defining a unit object according to an embodiment of the present invention.
7 is an exemplary diagram illustrating the structure of a threat library after performing the step of defining a relationship between a plurality of unit objects according to an embodiment of the present invention.
8 is an exemplary diagram illustrating the electronic warfare threat library structure after defining the holding variables of a plurality of unit objects according to an embodiment of the present invention.
9 is an exemplary diagram illustrating the structure of a threat library after defining variable activation conditions of a plurality of unit objects according to an embodiment of the present invention.
10 is a flowchart illustrating a method of creating a threat library file according to an embodiment of the present invention.
11 is an exemplary diagram in which a unit object is added according to an embodiment of the present invention.
12A to 12C are exemplary diagrams of connecting unit objects according to an embodiment of the present invention.
13 is an exemplary diagram illustrating a threat library structure after adding a setting unit object and a beam extension unit object according to an embodiment of the present invention.
14 is an exemplary diagram illustrating the structure of a threat library after adding PW, which is an integer variable, to existing beam variable information according to an embodiment of the present invention.
15 is a diagram illustrating an example of outputting a threat library file as a conversion file according to an embodiment of the present invention.
16 is a diagram illustrating an example of writing additional information according to an embodiment of the present invention.

Embodiments of the present invention are exemplified for the purpose of explaining the technical spirit of the present invention. The scope of the rights according to the present invention is not limited to the embodiments presented below or specific descriptions of these embodiments.

All technical and scientific terms used in the present invention, unless otherwise defined, have the meanings commonly understood by those of ordinary skill in the art to which the present invention belongs. All terms used in the present invention are selected for the purpose of more clearly describing the present invention and not to limit the scope of the present invention.

As used herein, expressions such as "comprising", "including", "having", etc. are open-ended terms connoting the possibility of including other embodiments, unless otherwise stated in the phrase or sentence in which the expression is included. (open-ended terms).

Expressions in the singular in the present invention may include the meaning of the plural unless otherwise stated, and the same applies to expressions in the singular in the claims.

Expressions such as “first” and “second” used in the present invention are used to distinguish a plurality of components from each other, and do not limit the order or importance of the components.

As used herein, the term “unit” refers to software or hardware components such as field-programmable gate arrays (FPGAs) and application specific integrated circuits (ASICs). However, "units" are not limited to hardware and software. A “unit” may be configured to reside on an addressable storage medium, or it may be configured to refresh one or more processors. Thus, as an example, "part" includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, It includes segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Functions provided within components and “parts” may be combined into a smaller number of components and “parts” or separated into additional components and “parts”.

As used herein, the expression "based on" is used to describe one or more factors affecting the action or operation of a decision judgment, which are described in a phrase or sentence in which the expression is included, and the expression is a decision , does not exclude additional factors affecting the conduct or behavior of judgment.

In the present invention, when it is said that a certain element is "connected" or "connected" to another element, a certain element can be directly connected or connectable to another element, or a new other element It should be understood that the elements may be connected or may be connected via an element.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the accompanying drawings, the same or corresponding components are assigned the same reference numerals. In addition, in the description of the embodiments below, overlapping description of the same or corresponding components may be omitted. However, even if descriptions regarding components are omitted, it is not intended that such components are not included in any embodiment.

1 is a block diagram schematically showing an electronic warfare threat library construction system according to an embodiment of the present invention. Referring to FIG. 1 , the electronic warfare threat library construction system 100 according to an embodiment includes a receiving unit 110 , a threat library structure processing unit 120 , a threat library file processing unit 130 , an output unit 140 , and a storage unit ( 150 ) and a control unit 160 .

The receiver 110 may receive the threat library structure. Also, the receiver 110 may receive the threat library file. In an embodiment, the receiving unit 110 may receive a threat library structure pre-stored in the storage 150 . In another embodiment, the receiver 110 may receive a threat library structure pre-stored in an external memory device (not shown) connected to the electronic threat library construction system 100 . In another embodiment, the receiver 110 may receive a threat library structure pre-stored in an external device (not shown) connected to the electronic threat library building system 100 through a network (not shown).

In one embodiment, the threat library structure may have a form as shown in FIG. 2 . In another embodiment, the threat library structure may have a form as shown in FIG. 3 .

The threat library structure processing unit 120 may design a threat library structure. In an embodiment, the threat library structure processing unit 120 may design the threat library structure according to system requirements. Also, the threat library structure processing unit 120 may create a threat library structure. In an embodiment, the threat library structure processing unit 120 may create a threat library structure according to a defined format. Furthermore, the threat library structure processing unit 120 may verify the threat library structure. In an embodiment, the threat library structure processing unit 120 may verify whether the threat library structure complies with a defined format.

The threat library file processing unit 130 may create a threat library file. In an embodiment, the threat library file processing unit 130 may create a threat library file according to a threat library structure based on the threat library file received through the receiving unit 110 . Also, the threat library file processing unit 130 may verify the threat library file. In an embodiment, the threat library file processing unit 130 may verify whether the created threat library file complies with the threat library structure. Furthermore, the threat library file processing unit 130 may convert the threat library file.

The output unit 140 may output the threat library file created by the threat library file processing unit 130 . In an embodiment, the output unit 140 may output the threat library file as a file suitable for a purpose of charging, conversion, or reporting. In one embodiment, the conversion file may be used to convert the previously created threat library file when the threat library structure is changed. In one embodiment, the loading file may be used as an input of an electronic warfare program. The report file may be used for documents and the like by storing the threat library file in a form that can be read by a user.

The storage unit 150 may store a threat library structure. Also, the storage unit 150 may store a threat library file. In addition, the storage unit 150 may store commands or data related to at least one other component of the electronic warfare threat library construction system 100 . Moreover, the storage unit 150 may store software and/or programs.

In an embodiment, the storage 150 may include an internal memory or an external memory. The internal memory may include at least one of a volatile memory (eg, DRAM, SRAM, or SDRAM) and a non-volatile memory (eg, a flash memory, a hard drive, or a solid state drive (SSD)). The external memory may be functionally or physically connected to the electronic warfare threat library construction system 100 through various interfaces.

The control unit 160 may be connected to the receiving unit 110 , the receiving unit 110 , the threat library structure processing unit 120 , the threat library file processing unit 130 , the output unit 140 , and the storage unit 150 . The controller 160 may control the operations of the receiving unit 110 , the threat library structure processing unit 120 , the threat library file processing unit 130 , the output unit 140 , and the storage unit 150 .

Although process steps, method steps, algorithms, etc. are described in a sequential order in the flowcharts shown herein, such processes, methods, and algorithms may be configured to operate in any suitable order. In other words, the steps of the processes, methods, and algorithms described in various embodiments of the invention need not be performed in the order described herein. Also, although some steps are described as being performed asynchronously, in other embodiments some of these steps may be performed concurrently. Further, the exemplification of a process by description in the drawings does not imply that the exemplified process excludes other changes and modifications thereto, and that the exemplified process or any of its steps may be used in any of the various embodiments of the present invention. It is not meant to be essential to one or more, nor does it imply that the illustrated process is preferred.

4 is a flowchart illustrating a method of building an electronic warfare threat library according to an embodiment of the present invention. Referring to FIG. 4 , in step S402 , the electronic warfare threat library system 100 may determine whether a threat library structure is received. In an embodiment, the threat library structure processing unit 120 of the electronic warfare threat library system 100 may determine whether the threat library structure is received through the receiving unit 110 . For example, the threat library structure may be an existing threat library structure.

If it is determined in step S402 that the threat library structure has been received, in step S404, the electronic warfare threat library system 100 may design the threat library structure. In an embodiment, the threat library structure processing unit 120 of the electronic warfare threat library system 100 may analyze system requirements and design a threat library structure according to the analyzed requirements.

In step S406, the electronic warfare threat library system 100 may create a threat library structure based on the designed threat library structure. In an embodiment, the threat library structure processing unit 120 of the electronic warfare threat library system 100 may create a threat library structure according to the designed threat library structure. How to create a threat library structure will be described in detail below.

In step S408, the electronic warfare threat library system 100 may verify the created threat library structure. In an embodiment, the threat library structure processing unit 120 of the electronic warfare threat library system 100 may verify whether the created threat library structure complies with a defined format. For example, the threat library structure processing unit 120 may verify whether the created threat library structure complies with the format of the defined threat library structure as shown in FIG. 2 or FIG. 3 .

In step S410, the electronic warfare threat library system 100 may determine whether a threat library file is received. In an embodiment, the threat library file processing unit 130 of the electronic warfare threat library system 100 may determine whether a threat library file is received through the receiving unit 110 .

If it is determined that the threat library file has been received in step S410 , in step S412 , the electronic warfare threat library system 100 may create a threat library file. In an embodiment, the threat library file processing unit 130 of the electronic warfare threat library system 100 may create a threat library file based on the verified threat library structure.

In step S414, the electronic warfare threat library system 100 may verify the created threat library file. In an embodiment, the threat library file processing unit 130 of the electronic warfare threat library system 100 may verify whether the created threat library file complies with the threat library structure. In an embodiment, the threat library file processing unit 130 may convert the threat library file as needed.

In step S416, the electronic warfare threat library system 100 may output a verified threat library file. In an embodiment, the output unit 140 of the electronic warfare threat library system 100 may output the threat library file as a file suitable for any one of a use for charging, a use for conversion, and a use for reporting.

5 is a flowchart illustrating a method of creating a threat library structure according to an embodiment of the present invention. Referring to FIG. 5 , in step S302 , the threat library structure processing unit 120 may define a plurality of unit objects. In an embodiment, the threat library structure processing unit 120 may analyze software requirements and the like to define a plurality of unit objects to be used in the threat library structure.

According to an embodiment, the unit object may have an inheritance relationship. In this case, the type, description, and inheritance of each unit object may be set. This may be defined using the “Unit” tag shown in FIG. 2 . The type of unit object may be a value used when establishing a relationship between unit objects. Whether the unit object is inherited may be a value that determines whether to inherit relationship information and variable information of the parent unit object when the corresponding unit object is a child unit object. For example, the threat library structure processing unit 120 may define a mode, a threat, a beam, a frequency end, and a PRI end as unit objects. Accordingly, the threat library structure processing unit 120 may create a threat library structure after defining a unit object as shown in FIG. 6 . In FIG. 6 , the base unit object type and the type and description of each unit object were created through the "NX1DataDefinition" tag and the "Unit" tag. The base unit object type is used to store the threat library file for loading.

In step S504, the threat library structure processing unit 120 may define a relationship between a plurality of unit objects. In an embodiment, the threat library structure processing unit 120 may define a relationship between a plurality of unit objects to be linked when creating a threat library file. In this case, the relation target unit object type, description, and the maximum number of possible connections may be set.

For example, the threat library structure processing unit 120 may define a relationship between “mode-threat”, “threat-beam”, “beam-frequency stage”, and “beam-PRI stage” for a plurality of unit objects. . Accordingly, as shown in FIG. 7 , the threat library structure processing unit 120 may create a threat library structure after defining a relationship between a plurality of unit objects. In FIG. 7 , a connection relationship between each unit object may be created through a “link” tag. In this case, the maximum number of unit objects that can be connected may be limited through the “limit” attribute.

In step S506 , the threat library structure processing unit 120 may define holding variables of a plurality of unit objects. In an embodiment, the threat library structure processing unit 120 may define a plurality of variables to be held by each of a plurality of unit objects. Also, the threat library structure processing unit 120 may edit characteristics of each of the plurality of variables.

For example, the threat library structure processing unit 120 may define a beam name, which is a character variable, a scan right type, which is an enumerated variable, and a scan period/average frequency/average PRI, which is an integer variable, as retained variables of the beam unit object. In addition, the threat library structure processing unit 120 may define a value that is a range-type variable as a retained variable of the frequency and PRI unit objects. Accordingly, the threat library structure processing unit 120 may create the electronic warfare threat library structure after defining the holding variables of the unit object as shown in FIG. 8 . In FIG. 8 , integer type, range type, character type, enumeration type, and flag type variables may be created through "number", "ranged", "string", "enum", and "flag" tags. In this case, usable attribute values can be confirmed in FIGS. 2 and 3 .

In one embodiment, the variable may be divided into types of integer type, range type, character type, enumeration type, and flag type. This may be defined using the “number”, “ranged”, and tags shown in FIG. 2 and the “string”, “enum”, and “flag” tags shown in FIG. 3 . Each variable can have a name, a description, and whether it can be modified in common. Default value, minimum value, maximum value, resolution, and unit can be set for integer type and range type variable. For the range type, the lower and upper default values can be set. Character variables can be set with default values and string buffer sizes. Sub-items can be additionally defined for enumeration and flag-type variables. Each sub-item can be set with a name, description, and value. This may be defined using the “item” tag shown in FIG. 3 . In this case, the value must not overlap with other sub-items.

In step S508, the threat library structure processing unit 120 may define variable activation conditions of a plurality of unit objects. In one embodiment, the variable activation condition may be defined using the “condition” tag shown in FIG. 3 . Each variable is activated according to other variables or relationship information. In the variable activation condition, the condition target name, type, and value can be set. The condition target name can be the name of another variable or the type of the relation target unit object. Condition types include logical product, logical sum, equality, negation, more than, less than, less than, greater than, less than.

For example, the threat library structure processing unit 120 activates the scan cycle variable only when the scan type variable is circular, and connects the average frequency and average PRI variables with more than 0 “FrequencyLevel” and “PRILevel” unit objects, respectively. Variable activation conditions can be defined so that they are activated only when they occur. Accordingly, as shown in FIG. 9 , the threat library structure processing unit 120 may create a threat library structure after defining variable activation conditions of a plurality of unit objects. In FIG. 9 , by adding a “condition” tag under the variable tag, the corresponding variable may be activated according to the condition of another variable or unit object relationship. This is a function to specify the variables that can be edited by the threat library file creator.

10 is a flowchart illustrating a method of creating a threat library file according to an embodiment of the present invention. Referring to FIG. 10 , in step S1002 , the threat library file processing unit 130 may add a plurality of unit objects to be included in the threat library file. In an embodiment, the threat library file processing unit 130 may add a plurality of unit objects based on the threat library structure. In this case, unit objects of the types defined in the threat library structure may be added.

For example, 1 unit object "mode", 1 unit object "threat", 3 unit object "beam", 1 unit object "frequency stage", 1 unit object "PRI stage" When added, the threat library file processing unit 130 may add unit objects as shown in FIG. 11 .

In step S1004, the threat library file processing unit 130 may connect a plurality of unit objects. In an embodiment, the threat library file processing unit 130 may connect unit objects related to each other from a plurality of unit objects. In this case, the unit object cannot be connected in excess of the defined maximum number of possible connections.

For example, the threat library file processing unit 130 may connect the unit object “mode 1” and the unit object “threat 1” as shown in FIG. 12A . In FIG. 12A , when the unit object “mode 1” is selected, types of unit objects that can be connected are listed in the connection relationship list, and the unit object “threat 1” can be selected and connected. Also, the threat library file processing unit 130 may connect the unit object “threat 1” and the unit object “beams 1, 2, 3” as shown in FIG. 12B . In FIG. 12B , when the unit object “threat 1” is selected, types of unit objects that can be connected are listed in the connection relationship list, and the unit objects “beams 1, 2, 3” can be selected and connected. A function of outputting information of a connected unit object through a tooltip or the like may be included. In addition, the threat library file processing unit 130 connects the unit object "beam 3" and the unit object "frequency stage 1" as shown in FIG. 12c, and the unit object "beam 3" and the unit object "PRI stage 1" can connect

In step S1006, the threat library file processing unit 130 may edit the variables of the plurality of unit objects. In an embodiment, the threat library file processing unit 130 may modify values of variables held by each of the plurality of unit objects. In an embodiment, the range of values that can be input to the variables may be limited according to definitions. do. Also, whether the variables can be edited may be determined according to an activation condition.

In step S1008, the threat library file processing unit 130 may generate additional information. In an embodiment, the threat library file processing unit 130 may generate information to be additionally included in the threat library file. The information may include an underlying search band, ambiguity, and the like. According to an embodiment, in order to generate such information, a target unit object having information necessary to generate additional information should be designated.

For example, when the unit object is additionally defined as “setting” and “beam inheritance beam extension”, the beam retention variable is “integer PW” and the beam extension is additionally defined as an integer interval variable, the threat library file processing unit 130 may add a unit object as shown in FIG. 13 and add a beam retention variable as shown in FIG. 14 .

13 shows the threat library structure after adding a setting unit object and a beam extension unit object. In this case, the beam extension unit object is a unit object inheriting the existing beam unit object. Inheritance between unit objects is used to express a unit object with some added characteristics while having the same relationship information and holding variables of a specific unit object. The beam extension unit object has both relation information and variable information of the existing beam information, and additionally has an interval, which is an integer variable. In order to maintain the existing beam information, the name of the existing beam unit object is changed to Beam Common, and the beam and beam extension unit object are created under the "SubUnits" tag. 14 shows the threat library structure after adding PW, which is an integer variable, to the existing beam variable information.

15 shows an example of outputting a threat library file as a conversion file. 15 , it can be confirmed that previously created information of “mode 1”, “threat 1”, “beam 1, 2, 3”, “frequency stage 1”, and “PRI stage 1” is maintained. 16 shows an example in which additional information is prepared. In FIG. 16 , a “beam extension” unit object is added, and the newly added “integer PW” variable and “interval variable” can be edited.

According to the above-described embodiment, not limited to electronic warfare equipment, an operating system-independent function may be provided, and a standard data structure that is not dependent on interworking equipment (hardware) may be provided. Therefore, when used in other systems in the future, cost reduction and software reusability can be maximized by understanding the concept of the framework, using functions necessary for the system, and developing only additional necessary functions.

Although the above method has been described through specific embodiments, the above method may also be implemented as computer readable code on a computer readable recording medium. The computer-readable recording medium includes all types of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device. In addition, the computer-readable recording medium is distributed in a computer system connected through a network, so that the computer-readable code can be stored and executed in a distributed manner. And, functional programs, codes, and code segments for implementing the above embodiments can be easily inferred by programmers in the technical field to which the present invention pertains.

Although the technical spirit of the present invention has been described by the examples shown in some embodiments and the accompanying drawings above, it does not depart from the technical spirit and scope of the present invention that can be understood by those of ordinary skill in the art to which the present invention pertains. It should be understood that various substitutions, modifications, and alterations within the scope may be made. Further, such substitutions, modifications, and alterations are intended to fall within the scope of the appended claims.

100: electronic warfare threat library construction system, 110: receiver, 120: threat library structure processing unit, 130: threat library file processing unit, 140: output unit, 150: storage unit, 160: control unit

Claims (22)

A method of building an electronic warfare threat library in an electronic warfare threat library construction system, the method comprising:
designing and creating a threat library structure;
verifying the created threat library structure;
creating a threat library file based on the verified threat library structure; and
verifying the threat library file
A method of building an electronic warfare threat library that includes. The method of claim 1,
receiving the threat library structure;
A method of building an electronic warfare threat library further comprising a. The method of claim 1, wherein the step of designing and creating the threat library structure comprises:
defining a plurality of unit objects to be used in the threat library structure;
defining a relationship between the plurality of unit objects to be linked when the threat library file is created;
defining a holding variable of the plurality of unit objects; and
defining variable activation conditions of the plurality of unit objects
A method of building an electronic warfare threat library that includes. The method of claim 3 , wherein the defining a holding variable of the plurality of unit objects comprises:
defining a plurality of variables held by each of the plurality of unit objects; and
editing the properties of each of the plurality of variables;
A method of building an electronic warfare threat library that includes. The method of claim 3, wherein the step of defining the variable activation condition of the unit object comprises:
defining activation conditions of a plurality of variables of each of the plurality of unit objects; and
editing the characteristics of the activation condition;
A method of building an electronic warfare threat library that includes. The method of claim 1,
Receiving the threat library file
A method of building an electronic warfare threat library further comprising a. The method of claim 1, wherein creating a threat library file based on the verified threat library structure comprises:
adding a plurality of unit objects to be included in the threat library file;
performing a connection between the plurality of unit objects;
editing a plurality of variables of each of the plurality of unit objects; and
Generating information to be additionally included in the threat library file
A method of building an electronic warfare threat library that includes. The method of claim 7, wherein the connecting between the plurality of unit objects comprises:
detecting a plurality of unit objects related to each other from the plurality of unit objects; and
connecting the plurality of unit objects related to each other
A method of building an electronic warfare threat library that includes. The method of claim 7, wherein the editing of the plurality of variables of each of the plurality of unit objects comprises:
Correcting values of a plurality of variables held by each of the plurality of unit objects
A method of building an electronic warfare threat library that includes. 10. The method according to any one of claims 1 to 9,
Outputting the threat library file
A method of building an electronic warfare threat library further comprising a. The method of claim 10, wherein outputting the threat library file comprises:
Outputting the threat library file as any one of the use for charging, the use for conversion, and the use for reporting
A method of building an electronic warfare threat library that includes. As an electronic warfare threat library construction system,
a threat library structure processing unit that designs and creates a threat library structure and verifies the created threat library structure;
a threat library file processing unit that creates a threat library file based on the verified threat library structure and verifies the threat library file; and
Output unit for outputting the threat library file
Electronic warfare threat library building system that includes. 13. The method of claim 12,
Receiving unit for receiving the threat library structure
Electronic warfare threat library construction system further comprising. The method of claim 12, wherein the threat library structure processing unit
defining a plurality of unit objects to be used in the threat library structure;
define a relationship between the plurality of unit objects to be linked when the threat library file is created,
defining a holding variable of the plurality of unit objects,
An electronic warfare threat library construction system that defines variable activation conditions of the plurality of unit objects. The method of claim 14, wherein the threat library structure processing unit
defining a plurality of variables held by each of the plurality of unit objects,
Editing the characteristics of each of the plurality of variables, electronic warfare threat library construction system. The electronic warfare threat library construction system according to claim 14, wherein the threat library structure processing unit defines activation conditions of a plurality of variables of each of the plurality of unit objects and edits characteristics of the activation conditions. The system of claim 13, wherein the receiving unit receives the threat library file. The method of claim 12, wherein the threat library structure processing unit
adding a plurality of unit objects to be included in the threat library file;
performing a connection between the plurality of unit objects,
Edit a plurality of variables of each of the plurality of unit objects,
An electronic warfare threat library construction system for generating information to be additionally included in the threat library file. The method of claim 18, wherein the threat library structure processing unit
detecting a plurality of unit objects related to each other from the plurality of unit objects,
An electronic warfare threat library construction system that connects the plurality of related unit objects. The electronic warfare threat library construction system according to claim 18, wherein the threat library structure processing unit modifies values of a plurality of variables held by each of the plurality of unit objects. The electronic warfare threat library construction system according to claim 20, wherein the output unit outputs the threat library file as a file suitable for any one of a use for charging, a use for conversion, and a use for reporting. 22. The method according to any one of claims 12 to 21,
A storage unit for storing the threat library structure and the threat library file
Electronic warfare threat library construction system further comprising.

Images