KR20230011126A - Method and Apparatus for checking Integrated Equipment Based on Markup Language - Google Patents

Abstract

Disclosed are an integrated equipment inspection method based on markup language and a device therefor. The integrated equipment inspection device according to an embodiment of the present invention includes: a file generation module for generating an extended markup language (XML) file based on an interlocking control document (ICD) for each of a plurality of pieces of equipment; and an integrated equipment inspection module for performing inspection on at least one equipment to be inspected among the plurality of pieces of equipment based on the extended XML file for each of the plurality of pieces of equipment.

Description

Method and Apparatus for checking Integrated Equipment Based on Markup Language}

The present invention relates to a method for checking integrated equipment based on a markup language and an apparatus therefor.

The contents described in this section simply provide background information on the embodiments of the present invention and do not constitute prior art.

The development of weapon systems includes the development of various equipment. Equipment developed in relation to weapon systems must be inspected prior to actual use. It is required to develop an inspection equipment SW program to check whether the equipment is normal or abnormal.

Referring to FIG. 1A, communication between devices is performed based on an interface control document (ICD) agreed upon in advance, and each inspection equipment is based on the contents of the interlock control document by the equipment development entity 110. SW program 112 is implemented. Depending on the type of interlocking control document, the development of the inspection equipment SW program is performed separately for each equipment 114.

Referring to FIG. 1B , in the weapon system equipment development stage, the test subject prepares an interlocking control document for equipment inspection and communication with target equipment (S120). The interlocking control document defines the professional format (data format, size, content, and verification rules) used for communication with the equipment, and based on this, each equipment developer can perform professional transmission and reception and data processing functions with the equipment The SW program is implemented (S122). The inspection equipment SW program is managed for each equipment (S124). On the other hand, when a change in the interlocking control document occurs, the changed interlocking control document contents in the equipment development entity are applied to the inspection equipment SW program (S126).

Since the implementation of the inspection equipment SW program is performed by the equipment development entity for each device, time and cost are required for implementation. Changes cannot be made.

In addition, whenever the test subject performs a change in the interlocking control document, the equipment development subject must request the modification of the inspection equipment SW program to apply the changes in the interlocking control document, and the equipment inspection cannot be performed until the modification is completed.

The present invention generates an extended markup language file based on an interlocking control document for each of a plurality of equipment, and performs inspection on at least one equipment to be inspected based on the extended markup language file for each of a plurality of equipment The main purpose is to provide an integrated equipment inspection method based on markup language and a device therefor.

According to one aspect of the present invention, the integrated equipment inspection device for achieving the above object generates an extensible markup language (XML) file based on an interlocking control document (ICD) for each of a plurality of equipment file creation module; and an integrated equipment inspection module performing an inspection of at least one equipment to be inspected among a plurality of equipment based on the extended markup language (XML) file for each of a plurality of equipment.

In addition, according to another aspect of the present invention, the integrated equipment inspection method for achieving the above object is, in the file generation module, an extended markup language (XML) file based on the interlocking control document (ICD) for each of a plurality of equipment A file creation step that generates a; and an integrated equipment inspection step of performing inspection on at least one equipment to be inspected among a plurality of equipment based on the extended markup language (XML) file for each of the plurality of equipment in the integrated equipment inspection module. .

As described above, in the present invention, the implementation of the integrated inspection equipment SW program is performed only once for the first time, and then the expansion markup language file for each equipment is created to increase the scalability, time and cost of the equipment to be inspected without implementing additional SW. reduction effect can be obtained.

In addition, the present invention can perform integrated configuration management and batch change due to the use of a single SW program, and when the test subject needs to change the interlocking control document, it is XML rather than SW modification, which consumes a relatively large amount of time and cost. By modifying the contents of the file, you can get the effect of immediate correction and resumption of inspection.

1A and 1B are views for explaining a conventional equipment inspection method.
2 is a schematic block diagram of an integrated equipment inspection system according to an embodiment of the present invention.
3 is a diagram for explaining an integrated equipment inspection operation according to an embodiment of the present invention.
4 is a flowchart illustrating an integrated equipment inspection method according to an embodiment of the present invention.
5 is an exemplary view for explaining the operation of the integrated equipment inspection device according to an embodiment of the present invention.
6 is a flowchart illustrating an integrated equipment inspection method according to an embodiment of the present invention.
7 is an exemplary diagram for explaining an operation of an integrated equipment inspection device for a predetermined equipment according to an embodiment of the present invention.
8 is an exemplary diagram illustrating a data rule set of an extended markup language file according to an embodiment of the present invention.
9 is an exemplary diagram for explaining a detailed operation of an integrated equipment inspection device for a predetermined equipment according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted. In addition, although preferred embodiments of the present invention will be described below, the technical idea of the present invention is not limited or limited thereto and can be modified and implemented in various ways by those skilled in the art. Hereinafter, a method for checking integrated equipment based on a markup language proposed in the present invention and an apparatus therefor will be described in detail with reference to drawings.

2 is a schematic block diagram of an integrated equipment inspection system according to an embodiment of the present invention.

The integrated equipment inspection system 200 according to the present embodiment may include a user terminal 210 , an integrated equipment inspection device 220 and an inspection target equipment 230 . The integrated equipment inspection system 200 of FIG. 2 is according to an embodiment, and all blocks shown in FIG. 2 are not essential components, and some blocks included in the integrated equipment inspection system 200 in another embodiment are added. , may be changed or deleted.

The integrated equipment inspection system 200 generates an Extensible Markup Language (XML) file based on an Interface Control Document (ICD) for each of a plurality of equipment, and expands each of a plurality of equipment. Based on the markup language file, at least one inspection target equipment is inspected.

The user terminal 210 interworks with the integrated equipment inspection device 220 to perform an operation for controlling an operation to perform an integrated equipment inspection.

The user terminal 210 may be a terminal operated by a user such as an inspection manager for integral inspection of the inspection target equipment 230 or an inspection manager for controlling the integrated equipment inspection device 220 or a developer.

The user terminal 210 obtains an interlocking control document from a separate server or an external user, and transfers the contents of the interlocking control document to the integrated equipment inspection device 220 by referring to the interlocking control document obtained. Here, the interlocking control document is a document created in the process of developing various equipment related to the development of a weapon system, including interface control drawings, interface requirements specifications, and all documents that indicate physical and functional interfaces between related or interlocked systems or components. can do. Interlocking control document is a document that is generally written and used in the process of equipment development, so a detailed explanation will be omitted.

The user terminal 210 may transmit the contents of the interlocking control document to the integrated equipment inspection device 220 in a form requested by the integrated equipment inspection device 220 by a user's manipulation or input.

In addition, the user terminal 210 transmits an inspection control signal for an integrated equipment inspection to the integrated equipment inspection device 220 to perform an integrated inspection of the inspection target equipment 230 . Here, the inspection control signal may include identification information about the inspection target device 230 selected to perform inspection among a plurality of devices, inspection start information, and the like.

In addition, the user terminal 210 may receive an integrated inspection result when the integrated inspection device 220 completes an integrated inspection of the inspection target equipment 230 . Here, the integrated inspection result may include exhibition information of specialized data, data processing results, correction feedback information, and the like.

The integrated equipment inspection device 220 generates an extended markup language file based on the interlocking control document, and performs integrated inspection on the inspection target equipment 230 based on the extended markup language file. The integrated equipment inspection device 220 according to the present embodiment includes a file generation module 222 and an integrated equipment inspection module 224 . Here, the file generation module 222 and the integrated equipment inspection module 224 are described as modules included in the integrated equipment inspection device 220, but are not necessarily limited thereto, and separate devices or separate devices that perform each function It can be implemented as software installed on each of the hardware of

The file generation module 222 generates an extended markup language (XML) file based on the interworking control document (ICD) for each of a plurality of devices.

The file generation module 222 receives an interlocking control document (ICD) for each of a plurality of devices from the user terminal 210, and references each interlocking control document to an extended markup language (XML) file for each of a plurality of devices. create and save

The file creation module 222 provides an input interface that works with the user terminal 210 to input the contents of the interlocking control document based on a preset extended markup language data rule set (XML Data Rule set).

The file generation module 222 verifies whether the contents of the interlocking control document input through the input interface match the extended markup language data rule set, and then creates an XML file.

The file generation module 222 generates an extended markup language data rule set including a first verification rule (full text verification rule) for the entire text message and a second verification rule (data verification rule) for each of at least one data packet. Creates an extensible markup language (XML) file based on Here, the first verification rule (message verification rule) includes rule information on at least one of a full text message name, a total message size, the number of data, the number of text message features, and transmission/reception. In addition, the second verification rule (data verification rule) includes rule information on at least one of a data type, data basic value, data range (start, end), data size, and data name for each of the at least one data packet. .

The integrated equipment inspection module 224 performs inspection on at least one inspection target device among a plurality of devices based on an XML file for each of a plurality of devices.

The integrated equipment inspection module 224 selects at least one inspection target device among a plurality of devices and calls an extended markup language file corresponding to the selected inspection target device. The integrated equipment inspection module 224 performs inspection on inspection target equipment using the called extended markup language file.

The integrated equipment inspection module 224 preferentially stores the first verification rule (specialized verification rule) included in the extended markup language file corresponding to the selected equipment to be inspected, and the second verification included in the extended markup language file. Save the rules (data validation rules).

The integrated equipment inspection module 224 acquires specialized data from the selected inspection target equipment by generating a specialized transmission/reception event for the equipment to be inspected through the equipment interlocking interface, and based on the first verification rule (specialized verification rule), the specialized data Performs a first verification for

When the first verification is not passed, the integrated equipment inspection module 224 transmits the first verification result information on the expert data to the user terminal 210 . Here, the first verification result information includes information on data that does not satisfy rules or an error generated in the full text data for the full text verification rule.

When the first verification is passed, the integrated equipment inspection module 224 performs a second verification on at least one data packet included in the full text data using a second verification rule (data verification rule).

When the first verification is passed, the integrated equipment inspection module 224 checks the number of data packets included in the full text data and compares the number of data packets with a preset threshold value (eg, threshold value is 10).

If the number of data packets is less than the threshold value, the integrated equipment inspection module 224 performs a second verification on each data packet included in the full text data using a second verification rule.

On the other hand, if the number of data packets is greater than the threshold value, the integrated equipment inspection module 224 selects some data packets among the data packets included in the full text based on a predetermined condition, and performs second verification on the selected data packets. The second verification is performed using the rule. Here, the predetermined condition for selecting some data packets may be a condition related to data packet information (data size, identification number, etc.), a predetermined priority condition, or a random condition.

Although the integrated equipment inspection module 224 is described as performing a second verification after selecting a data packet using one of predetermined conditions, it is not necessarily limited thereto.

The integrated equipment inspection module 224 calculates a first score for each data packet using a condition related to data packet information (data size, identification number, etc.), and uses a pre-set priority condition to determine the data packet After calculating the second score for each, the second validation rule for some data packets with a high final score based on the final score obtained by summing the first score and the second score (eg, data packets with the top 10 final scores) The second verification may be performed using .

When the second verification passes, the integrated equipment inspection module 224 provides the specialized data display and data processing results to the user terminal 210 .

When the second verification is not passed, the integrated equipment inspection module 224 transmits second verification result information on the data packet to the user terminal 210 . Here, the second verification result information includes information about an error generated in a data packet for a data verification rule or a data packet that does not satisfy the rule.

The inspection target equipment 230 refers to various equipment developed in the development of a weapon system. Here, the inspection target equipment 230 is a command and control and communication weapon system, a surveillance and reconnaissance weapon system, a mobile weapon system, a ship weapon system, an air weapon system, a firepower weapon system, a defense weapon system, a launch weapon system, etc. could be equipment.

The inspection target equipment 230 may include at least one piece of equipment, and all or part of the at least one piece of equipment may be selected as an inspection target.

The equipment to be inspected 230 may interwork with the integrated equipment inspection device 220 to check whether the equipment is normal or abnormal after development is completed.

When the equipment interlocking interface is provided from the integrated equipment inspection device 220, the inspection target device 230 transmits specialized data to the integrated equipment inspection device 220 to correspond to the received message transmission/reception event.

3 is a diagram for explaining an integrated equipment inspection operation according to an embodiment of the present invention.

The file generation module 222 generates an extended markup language (XML) file based on the interworking control document (ICD) for each of a plurality of devices.

The file generating module 222 may generate an XML file using an XML file generating program. Specifically, the XML file generation program of the file generation module 222 receives the contents of the interlocking control document (ICD) for each of a plurality of devices, and refers to each interlocking control document as an extended markup language for each of a plurality of devices. (XML) file is created and saved.

The integrated equipment inspection module 224 performs an inspection of at least one equipment to be inspected among a plurality of equipments by using an integrated equipment inspection SW program based on an extended markup language (XML) file for each of a plurality of equipments.

The integrated equipment inspection module 224 selects at least one equipment to be inspected (equipment_A, equipment_B, and equipment_C) among a plurality of equipment.

The integrated equipment inspection SW program of the integrated equipment inspection module 224 calls an extended markup language file corresponding to the selected inspection target equipment. The integrated equipment inspection SW program performs inspection of the inspection target equipment using the called extended markup language file.

4 is a flowchart illustrating an integrated equipment inspection method according to an embodiment of the present invention.

In the weapon system equipment development stage, the test subject prepares an interlocking control document to perform equipment inspection and communication with the target equipment (S420).

In the integrated equipment checking device 220, each equipment development entity creates an extended markup language (XML) file based on the contents of the interlocking control document through the creation of an integrated equipment program (S420) (S430).

The integrated equipment inspection device 220 performs inspection on the inspection target equipment 230 using an extended markup language (XML) file (S440).

As a result of the inspection, the integrated equipment inspection device 220 corrects the extended markup language (XML) file corresponding to the interlock control document and repeats the inspection operation of the inspection target equipment 230 when the interlock control document needs to be modified. It is performed (S450).

In FIG. 4, each step is described as sequentially executed, but is not necessarily limited thereto. In other words, since it will be applicable to changing and executing the steps described in FIG. 4 or executing one or more steps in parallel, FIG. 4 is not limited to a time-series sequence.

5 is an exemplary view for explaining the operation of the integrated equipment inspection device according to an embodiment of the present invention.

Referring to FIG. 5, the XML file generating program of the file generating module 222 allows the user to input the contents of the interlocking control document based on a predefined extended markup language data rule set (XML Data Rule set). It has the ability to provide an interface.

The XML file generation program of the file generation module 222 verifies whether the extended markup language file complies with the extended markup language data rule set after inputting the contents of the interlocking control document, and stores the XML file as an output according to a user's command.

The integrated equipment inspection program of the integrated equipment inspection module 224 is loaded into a notebook physically connected to the equipment through Ethernet or serial, provides a device interworking interface, calls an extended markup language file, Sets up a set of extensible markup language data rules within the program.

The integrated equipment inspection program of the integrated equipment inspection module 224 performs data processing to the user when sending and receiving specialized data based on the stored extended markup language data rule set, and provides data display and processing result interface.

6 is a flowchart illustrating an integrated equipment inspection method according to an embodiment of the present invention.

The integrated equipment checking device 220 refers to the interlocking control document (ICD) for each of a plurality of devices and converts the interlocking control document into an extended markup language (XML) file (S610).

The integrated equipment inspection device 220 receives an interlocking control document (ICD) for each of a plurality of devices from the user terminal 210, and provides an extended markup language (XML) for each of a plurality of devices by referring to each interlocking control document. create a file

The integrated equipment checking device 220 stores the generated extensible markup language (XML) file (S620).

The integrated equipment inspection device 220 selects at least one inspection target device 230 from among a plurality of devices, and calls an extended markup language file corresponding to the selected inspection target device 230 (S630).

The integrated equipment inspection apparatus 220 performs data communication with the inspection target equipment 230 using the called extended markup language file to perform integrated equipment inspection (S640).

In FIG. 6, it is described that each step is sequentially executed, but is not necessarily limited thereto. In other words, since it will be applicable to changing and executing the steps described in FIG. 6 or executing one or more steps in parallel, FIG. 6 is not limited to a time-series sequence.

The integrated equipment inspection method according to the present embodiment described in FIG. 6 may be implemented as an application (or program) and recorded on a recording medium readable by a terminal device (or computer). All kinds of recording devices in which an application (or program) for implementing the integrated equipment inspection method according to the present embodiment is recorded and a recording medium readable by a terminal device (or computer) stores data that can be read by a computing system. or medium.

7 to 9 are exemplary diagrams for explaining the operation of the integrated equipment inspection device for predetermined equipment.

7 is an exemplary diagram for explaining the operation of an integrated equipment inspection device for a predetermined equipment according to an embodiment of the present invention, and FIG. 8 shows a data rule set of an extended markup language file according to an embodiment of the present invention. FIG. 9 is an exemplary diagram for explaining detailed operations of an integrated equipment inspection device for predetermined equipment according to an embodiment of the present invention.

The user refers to the contents of the interlocking control document for each device (S610) and converts the contents of the interlocking control document into an extended markup language file by inputting the contents to the extended markup language file generation program to fit the extended markup language form. An operation is performed (S620).

The format of the extended markup language is largely divided into one 'full message content' part containing the characteristics of the entire text message and n or more 'data content' parts containing the characteristics of each data packet composition. Same as The 'contents of the entire message' is a part about the message verification rule, and includes rule information on at least one of the message name, the size of the entire message, the number of data, the number of features of the message, and transmission/reception. In addition, the 'data content' part is a part for data validation rules, and rules for at least one of data type, data basic value, data range (start, end), data size, and data name for each of at least one data packet. contains information

A plurality of full texts can exist in one extended markup language file for each equipment, and the entered contents are saved in the form of an extended markup language file according to the format of the extended markup language data rule set (S630). .

The user calls the extended markup language file generated by executing the integrated equipment inspection program connected to the equipment (S640), and performs data communication with the equipment using the called extended markup language file to perform integrated inspection ( S650).

In step S640, the contents of the extended markup language in the called extended markup language file are read, the professional verification rules are stored in the integrated equipment inspection program (S642), and the data verification rules are stored in the integrated equipment inspection program (S644). Include steps.

Step S650 operates by including the following steps. When a data transmission/reception event occurs with the device (S652), the integrated equipment inspection program first performs type and validity verification of the corresponding message based on the message verification rule (S654). Thereafter, if the verification of step S654 passes, the contents of the data packet are verified (S656). Thereafter, for the verified packet, the integrated equipment inspection program performs specialized data display and related processing to provide the result to the user (S658).

The above description is only illustrative of the technical idea of the embodiment of the present invention, and those skilled in the art to which the embodiment of the present invention pertains may make various modifications and modifications within the scope not departing from the essential characteristics of the embodiment of the present invention. transformation will be possible. Therefore, the embodiments of the present invention are not intended to limit the technical idea of the embodiment of the present invention, but to explain, and the scope of the technical idea of the embodiment of the present invention is not limited by these examples. The protection scope of the embodiments of the present invention should be construed according to the claims below, and all technical ideas within the equivalent range should be construed as being included in the scope of the embodiments of the present invention.

200: integrated equipment inspection system
210: user terminal 220: integrated equipment inspection device
222: file generation module 224: integrated equipment inspection module
230: equipment to be inspected

Claims (12)

In the device for processing integrated equipment inspection in conjunction with a plurality of equipment,
A file generation module for generating an extended markup language (XML) file based on an interlocking control document (ICD) for each of a plurality of devices; and
An integrated equipment inspection module that performs inspection on at least one inspection target device among a plurality of devices based on the XML file for each of a plurality of devices.
Integrated equipment inspection device comprising a. According to claim 1,
The file creation module,
Receiving an interlocking control document (ICD) for each of a plurality of devices from the user terminal, and generating and storing an extended markup language (XML) file for each of the plurality of devices with reference to each of the interlocking control documents an integrated equipment checker. According to claim 2,
The file creation module,
Providing an input interface that works with a user terminal so that the contents of the interworking control document can be input based on a pre-set extended markup language data rule set (XML Data Rule set),
The integrated equipment inspection device, characterized in that for generating the extended markup language (XML) file after verifying whether the content of the interlocking control document input through the input interface matches the extended markup language data rule set. According to claim 3,
The file creation module,
The extended markup language based on an extended markup language data rule set including a first verification rule (full text verification rule) for the entire text and a second verification rule (data verification rule) for each of at least one data packet. (XML) file,
The first verification rule (message verification rule) includes rule information on at least one of a message name, a total message size, the number of data, the number of message features, and transmission/reception;
The second verification rule (data verification rule) includes rule information on at least one of a data type, a data basic value, a data range (start, end), a data size, and a data name for each of the at least one data packet. An integrated equipment inspection device, characterized in that. According to claim 1,
The integrated equipment inspection module,
Selecting at least one equipment to be inspected among a plurality of devices, calling an extended markup language file corresponding to the selected equipment to be inspected, and inspecting the equipment to be inspected using the called extended markup language file. An integrated equipment inspection device, characterized in that for performing. According to claim 5,
The integrated equipment inspection module,
The first verification rule (full text verification rule) included in the extended markup language file corresponding to the selected equipment to be inspected is preferentially stored, and the second verification rule (data verification rule) included in the extended markup language file is stored. Integrated equipment inspection device, characterized in that for storing. According to claim 6,
The integrated equipment inspection module,
A specialized transmission/reception event is generated for the equipment to be inspected through a device interworking interface to obtain specialized data from the selected equipment to be inspected, and first verify the specialized data based on the first verification rule (specialized verification rule). Integrated equipment inspection device, characterized in that for performing. According to claim 7,
The integrated equipment inspection module,
and performing a second verification on at least one data packet included in the specialized data using a second verification rule (data verification rule) if the first verification is passed. According to claim 8,
The integrated equipment inspection module,
An integrated equipment inspection device characterized in that when the second verification passes, display of specialized data and data processing results are provided to the user terminal. In the method of processing integrated equipment inspection in conjunction with a plurality of equipment in an integrated equipment inspection device,
In the file generation module, a file generation step of generating an extended markup language (XML) file based on the interlocking control document (ICD) for each of a plurality of devices; and
In an integrated equipment inspection module, an integrated equipment inspection step of performing inspection on at least one inspection target device among a plurality of devices based on the XML file for each of a plurality of devices.
Integrated equipment inspection method comprising a. According to claim 10,
The file creation step,
Receiving an interlocking control document (ICD) for each of a plurality of devices from the user terminal, and generating and storing an extended markup language (XML) file for each of the plurality of devices with reference to each of the interlocking control documents How to check integrated equipment. According to claim 10,
In the integrated equipment inspection step,
Selecting at least one equipment to be inspected among a plurality of devices, calling an extended markup language file corresponding to the selected equipment to be inspected, and inspecting the equipment to be inspected using the called extended markup language file. Integrated equipment inspection method, characterized in that for performing.

Images