KR102396923B1 - Performance verification method in data distribution service - Google Patents

Abstract

The present invention relates to a performance verification method, and more specifically, to a performance verification method for verifying data transfer performance between a publisher and a subscriber in a data distribution service. The performance verification method according to an embodiment of the present invention is a performance verification method for verifying data transfer performance between a publisher and a subscriber in a data distribution service (DDS) that uses an interface description language (IDL), and performance verification method includes: creating an interface description language; and analyzing a log generated while transmitting and receiving verification data generated using the created interface description language in a node providing the data distribution service.

Description

PERFORMANCE VERIFICATION METHOD IN DATA DISTRIBUTION SERVICE

The present invention relates to a performance verification method, and more particularly, to a performance verification method for verifying data transfer performance between a publisher and a subscriber in a data distribution service.

Modern warfare is rapidly changing to a network-centric warfare in which warfare is waged based on information superiority, and tactical data links are used as a key means of this. For example, the air defense command and control system of the Air Force operates various tactical data links to exchange tactical data between command and control systems.

In the case of operating various tactical data links as described above, interoperability problems occur due to message conversion delay and different message standards when interworking between different tactical data links. In addition, since the next air defense command and control system is equipped with various tactical data links and aims to share tactical information with the existing air defense command and control system, securing interoperability is recognized as an increasingly important issue.

Data Distribution Service (DDS) is communication middleware for creating a data distribution environment, and was established as an international standard in 2004 by Object Management Group (OMG), a standardization organization. Such a data distribution service has excellent interoperability between systems, and it is possible to propose a flexible tactical information exchange structure using it.

In the data distribution service, an Interface Description Language (IDL) is used to transfer data between a publisher who provides data and a subscriber who receives data. Such an interface definition language is a language that defines the structure of data transmitted between a publisher and a subscriber, and may be produced in various forms depending on the usage environment.

Conventionally, in order to verify data transfer performance between a publisher and a subscriber in a data distribution service, the log of the application installed in the publisher and the log of the application installed in the subscriber are compared to determine whether the operation is normal or erroneous. However, in case of verifying data delivery performance by such a process, whenever an interface definition language is produced, publishers and subscribers are subscribed to the data distribution service, and then the log generated during the actual data delivery process needs to be analyzed, which makes the procedure complicated. And, there was a problem that the verification process takes a lot of time.

KR 10-2012-0069449 A

The present invention provides a performance verification method that can easily verify data delivery performance between a publisher and a subscriber in a data distribution service.

The performance verification method according to an embodiment of the present invention provides data delivery performance between a publisher and a subscriber in a Data Distribution Service (DDS) using an Interface Description Language (IDL). A performance verification method for verification, comprising: producing an interface definition language; and a process of analyzing a log generated while transmitting/receiving verification data generated using the manufactured interface definition language within a node providing the data distribution service.

In addition, the performance verification method according to an embodiment of the present invention transmits data between a publisher and a subscriber in a Data Distribution Service (DDS) using an Interface Description Language (IDL). A performance verification method for verifying performance, comprising: producing an interface definition language; generating a mock issuer for issuing verification data according to the produced interface definition language; generating a mock subscriber for subscribing verification data from the mock publisher; and analyzing a log generated while transmitting verification data from the mock issuer to the mock subscriber.

The interface definition language may include a programming language used for communication between publishers and subscribers who use different languages.

The verification data may include a topic used to classify data in the data distribution service.

The process of generating the mock issuer may include: generating a source code for manufacturing the mock issuer by interpreting the produced interface definition language; and compiling the source code to produce a mock issuer.

The mock publisher may include a sending application that mimics the data sending function of the publisher.

The mock issuer may include: a mock issuer declaration unit for declaring subscription to the issuer in the data distribution service; and a topic transmission and log output unit for transmitting a topic to the simulated subscriber and outputting a log generated during topic transmission.

The mock issuer may further include a mock issuer deletion unit configured to delete the occupied memory in order to perform a data transmission function when the topic transmission to the mock subscriber is finished.

The generating of the simulated subscriber may include: generating a source code for creating a simulated subscriber by interpreting the produced interface definition language; and compiling the source code to produce a simulated subscriber.

The simulated subscriber may include a receiving application simulating the data reception function of the subscriber.

The simulated subscriber includes: a simulated subscriber declaration unit for declaring subscription to the data distribution service as a subscriber; and a topic receiving and log output unit for receiving a topic from the mock publisher and outputting a log generated during topic reception.

The mock subscriber may further include a mock subscriber deletion unit for deleting the memory occupied in order to perform a data reception function when the topic reception from the mock publisher is finished.

The process of analyzing the log may include generating an analyzer for receiving the log output from the simulated publisher and the simulated subscriber.

The analyzer may include an analysis application that analyzes the received log to evaluate data transfer performance between the mock publication and the mock subscription period.

Meanwhile, the recording medium according to an embodiment of the present invention may be a recording medium storing a computer program for performing any one of the above-described performance verification methods.

According to an embodiment of the present invention, by verifying the data transfer performance within the node that provides the data distribution service, it is possible to simply verify the data transfer performance between the publisher and the subscriber without actually subscribing the publisher and the subscriber when the interface definition language is produced. can

In addition, there is no need to create a separate verification tool to compare and analyze the log of each application installed in the publisher and subscriber, and before the publisher and subscriber subscribe to the data distribution service, the interface between the publisher and the subscriber according to the created interface definition language Data transfer performance can be predicted in advance.

1 is a diagram schematically illustrating a performance verification method according to an embodiment of the present invention;
2 is a diagram showing the structure of a mock issuer created according to an embodiment of the present invention.
3 is a diagram showing the structure of a simulated subscriber generated according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various different forms, and only the embodiments of the present invention allow the disclosure of the present invention to be complete, and the scope of the invention to those of ordinary skill in the art It is provided to fully inform In order to describe the invention in detail, the drawings may be exaggerated, and like reference numerals refer to like elements in the drawings.

1 is a diagram schematically illustrating a performance verification method according to an embodiment of the present invention.

Referring to FIG. 1 , in a performance verification method according to an embodiment of the present invention, a publisher and a subscriber in a Data Distribution Service (DDS) using an Interface Description Language (IDL) ) as a performance verification method for verifying data transfer performance between It includes the process of analyzing the log.

More specifically, in the performance verification method according to an embodiment of the present invention, a publisher and a subscriber in a Data Distribution Service (DDS) using an Interface Description Language (IDL). As a performance verification method for verifying data transfer performance between the interfaces, the process of producing an interface definition language (S100), the process of generating a mock issuer for issuing verification data according to the produced interface definition language (S300), the mock issuer It may include a process of generating a simulated subscriber for subscribing to the validation data from (S400) and a process of analyzing a log generated while transferring validation data from the simulated publisher to the simulated subscriber (S600).

Data Distribution Service (DDS) is a reliable real-time data communication middleware standard created by the need for standardization of a data-centric program model for a distributed environment based on a publish/subscribe model. The purpose of the data distribution service is to simplify the design and implementation of distributed applications by simplifying complex network programming so that data can be transmitted regardless of the location or existence of the application participating in the communication. The data distribution service standard consists of DCPS (DDSv1.2 API Standard), which describes the API standard, and RTPS (RTPS v2.1 Wire Protocol Standard), which describes the network layer communication protocol. Here, DCPS (Data Centric Publisher/Subscriber) is an interface standard that provides a data exchange function based on a publish/subscribe model.

Such a data distribution service dynamically forms a network data domain, and each embedded device or mobile device can provide a data communication environment in which free participation or withdrawal is possible through the network data domain. It can be used as suitable middleware that can be applied.

The data distribution service is provided by a node such as a server, a terminal, and other network devices. Nodes constitute a data distribution service network for data distribution services, and the data distribution service network is divided into domains, which are data sharing areas.

A domain may include one or more participants (Participant), where a participant may have one or more publishers or subscribers. In this case, the publisher may include a node such as a server, terminal, or other network device that provides data, and the subscriber may include a node such as a server, terminal, and other network device that receives data. Here, the publisher and the subscriber are objects that actually subscribe to the data distribution service and transfer data to each other, and are distinguished from a mock publisher and a mock subscriber, which will be described later, which are composed of an application.

In the process of producing the interface definition language ( S100 ), an interface definition language used for a data distribution service is created or modified. Here, the interface definition language may include a programming language used for communication between publishers and subscribers using different languages. The interface definition language is a language that defines the structure of data transmitted between a publisher and a subscriber for interworking between different tactical data links when various tactical data links are operated.

After the process of producing the interface definition language ( S100 ), the process of interpreting the interface definition language ( S200 ) may be performed. The process of analyzing the interface definition language ( S200 ) may be performed by analyzing the file syntax of the interface definition language. The interface definition language includes a file syntax for defining the data structure of data. Accordingly, in the process of interpreting the interface definition language ( S200 ), the data structure of data transmitted from the data distribution service is identified by analyzing the file syntax.

The process of generating a mock issuer ( S300 ) creates a mock issuer for issuing verification data according to the produced interface definition language. Here, the verification data may include a topic used to classify data in the data distribution service, and the mock issuer may include a transmission application that mimics the data transmission function of a publisher subscribing to the data distribution service. there is. That is, the real publisher subscribing to the data distribution service includes nodes such as servers, terminals, and other network devices that provide data, while the mock publisher is created within the nodes of the data distribution service to mimic the data transmission function of the publisher. It is different in that it is a sending application.

The process of generating the mock issuer (S300) includes a process of generating a source code for manufacturing a mock machine by interpreting the produced interface definition language (S310) and a step of compiling the source code to produce a mock machine (S320) can do.

In the process of generating the source code for the mock machine production ( S310 ), the source code for the mock machine production is generated by interpreting the produced interface definition language. A source code is a design file used in the production of an application, for example, software such as an application program, and is a design file configured to produce an application immediately when inputted to a computer. When such source code is input to the compiler, it is converted into a sending application that mimics the publisher's data sending function.

In the process of producing a mock issuer ( S320 ), the source code is compiled to produce a mock issuer. As described above, the source code generated in the process ( S310 ) of generating the source code for the production of the mock issuer stores all information necessary for the production of the application, for example, software such as the application program. Accordingly, in the process (S320) of manufacturing a mock issuer, such a source code is input to a compiler to produce a transmission application simulating the publisher's data transmission function.

2 is a diagram showing the structure of a mock issuer created according to an embodiment of the present invention.

Referring to FIG. 2 , the mock issuer 300 produced in the process of manufacturing the mock issuer ( S320 ) includes a mock issuer declaration unit 310 and the mock subscriber 400 for declaring subscription to a data distribution service as an issuer. ) to transmit a topic and may include a topic transmission and log output unit 320 for outputting a log generated during topic transmission.

The mock issuer declaration unit 310 declares a subscription to the data distribution service as an issuer. That is, the mock issuer declaration unit 310 is a functional unit installed in the transmission application that simulates the data transmission function, and performs a function of declaring subscription to the data distribution service as an issuer like an actual publisher subscribing to the data distribution service.

The topic transmission and log output unit 320 transmits a topic to the simulated subscriber 400 and outputs a log generated during topic transmission. That is, the topic transmission and log output unit 320 is also a functional unit installed in the transmission application that simulates the data transmission function, generates a topic, transmits the topic to the simulated subscriber 400, and outputs a log generated during topic transmission. perform the function

On the other hand, the mock issuer 300 may further include a mock issuer deletion unit 330 for deleting the memory occupied in order to perform a data transmission function when the topic transmission to the mock subscriber 400 is finished. As described above, the mock issuer 300 is a sending application that mimics the data transmission function of the publisher, and if such a sending application occupies the memory even after the transmission ends, the operation speed of the node performing the data distribution service is lowered can be Therefore, when the topic transmission to the mock subscriber 400 is finished, the mock issuer 300 further includes a mock issuer deletion unit 330 for deleting the memory occupied in order to perform the data transmission function. It can prevent the degradation of data transfer performance between the publisher and the subscriber.

In the process of generating a mock subscriber ( S400 ), a mock subscriber is created for subscribing to verification data from the mock publisher. Here, the simulated subscriber may include a reception application that simulates the data reception function of a subscriber subscribing to the data distribution service. That is, the real subscriber to the data distribution service includes nodes such as servers, terminals, and other network devices that receive data, while the simulated subscribers are created within the nodes of the data distribution service to imitate the subscriber's data reception function. It is different in that it is a receiving application.

The process of generating a simulated subscriber (S400) includes a process of generating a source code for producing a simulated subscriber by interpreting the produced interface definition language (S410) and a process of producing a simulated subscriber by compiling the source code (S420) can do.

In the process of generating the source code for the mock subscriber production ( S410 ), the source code for the mock subscriber production is generated by interpreting the produced interface definition language. A source code is a design file used in the production of an application, for example, software such as an application program, and is a design file configured to produce an application immediately when inputted to a computer. When such source code is input to the compiler, it is converted into a receiving application that mimics the subscriber's data receiving function.

In the process of producing a simulated subscriber (S420), the source code is compiled to produce a simulated subscriber. As described above, the source code generated in the process (S410) of generating the source code for the production of the simulated subscriber stores an application, for example, all information necessary for the production of software such as an application program. Therefore, in the process of manufacturing a simulated subscriber ( S420 ), such a source code is input to a compiler to produce a reception application simulating a subscriber's data reception function.

3 is a diagram showing the structure of a simulated subscriber generated according to an embodiment of the present invention.

Referring to FIG. 3, the simulated subscriber 400 produced in the process of manufacturing the simulated subscriber (S420) includes a simulated subscriber declaring unit 410 for declaring subscription to a publishing subscriber to the data distribution service and the simulated publisher ( 300), and may include a topic reception and log output unit 420 for outputting a log generated during topic reception.

The simulated subscriber declaring unit 310 declares a subscription to the data distribution service as a subscriber. That is, the simulated subscriber declaring unit 310 is a functional unit installed in the reception application that simulates the data reception function, and performs a function of declaring subscription to the data distribution service as a subscriber to the data distribution service like an actual subscriber subscribing to the data distribution service.

The topic receiving and log output unit 420 receives a topic from the simulated subscriber 300 and outputs a log generated during topic reception. That is, the topic reception and log output unit 420 is also a functional unit installed in the reception application that simulates the data reception function, generates a topic, receives a topic from the mock issuer 300, and outputs a log generated during topic reception perform the function

On the other hand, the mock subscriber 400 may further include a mock subscriber deletion unit 430 for deleting the memory occupied in order to perform a data reception function when the topic reception to the mock issuer 300 is finished. As described above, the simulated subscriber 400 is a sending application that mimics the subscriber's data reception function, and if the receiving application occupies the memory even after reception is terminated, the operation speed of the node performing the data distribution service is lowered. can be Accordingly, the simulated subscriber 400 further includes a simulated subscriber deletion unit 430 for deleting the occupied memory in order to perform a data reception function when the topic reception from the mock publication 400 is finished, and then performed It is possible to prevent the degradation of data transfer performance between the publisher and the subscriber.

Here, the process of generating the mock issuer (S300) and the process of generating the mock subscriber (S400) do not necessarily form a time-series relationship. That is, after the process of generating the mock publisher (S300) is performed, the process of generating the mock subscriber (S400) is performed, or after the process of generating the mock subscriber (S400) is performed, the process of creating the mock publisher ( S300) may be performed, and it goes without saying that the process of generating a mock issuer (S300) and the process of generating a mock subscriber (S400) may be performed simultaneously.

After the mock subscriber and the mock publisher are created, a process ( S500 ) of transferring verification data, that is, a topic, from the mock publisher to the mock subscriber may be performed.

In the process of delivering the topic ( S500 ), the topic generated by the mock issuer is delivered to the mock subscriber, and such topic delivery may be made through a wired or wireless network. In addition, in the process of delivering a topic ( S500 ), a topic is created and a log generated while transmitting the topic is output after being recorded in the above-described topic transmission and log output unit 320 , and is generated while receiving the topic. The log is output after being recorded in the above-described topic reception and log output unit 420 .

In the log analysis process ( S600 ), a log generated while transferring verification data from the mock issuer to the mock subscriber is analyzed. Here, the log means a record in which information generated while performing a function, such as a server, a terminal, or a computer of a network device, is stored according to time. In the log analysis process (S600), a topic is created and a log generated while sending a topic and a log generated while receiving a topic are analyzed to determine whether data transmission is being performed normally, otherwise there is an error in data transmission. Verify the data transfer performance by checking whether it has occurred.

In this case, the process of analyzing the log ( S600 ) may include the process of generating an analyzer for receiving the log output from the simulated publisher and the simulated subscriber. That is, the log analysis process ( S600 ) may be directly performed by a node such as a server, terminal, or network device that provides a data distribution service, but data transfer performance between the simulation publication and the simulation subscription period is obtained by analyzing the input log. It goes without saying that this can also be done by creating an analyzer, which is an analysis application for evaluation. Such an analyzer also deletes the memory occupied for the analysis when the analysis is finished, so that the data transfer performance between the publisher and the subscriber is prevented from being deteriorated.

Meanwhile, the performance verification method according to an embodiment of the present invention may be applied to a recording medium storing a computer program for performing the above method.

That is, the performance verification method according to an embodiment of the present invention may be implemented in the form of a computer-readable programming language code recorded on a computer-readable recording medium. The computer-readable recording medium may be any data storage device readable by the computer and capable of storing data. For example, the computer-readable recording medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical disk, hard disk drive, flash memory, solid state disk (SSD), or the like. In addition, the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between computers.

As such, according to an embodiment of the present invention, by verifying data transfer performance within a node that provides a data distribution service, data transfer performance between a publisher and a subscriber is simplified without actually subscribing the publisher and the subscriber when the interface definition language is produced. can be verified.

In addition, there is no need to create a separate verification tool to compare and analyze the log of each application installed in the publisher and subscriber, and before the publisher and subscriber subscribe to the data distribution service, the interface between the publisher and the subscriber according to the created interface definition language Data transfer performance can be predicted in advance.

In the above, preferred embodiments of the present invention have been described and illustrated using specific terms, but such terms are only for clearly explaining the present invention, and the embodiments of the present invention and the described terms are the spirit of the following claims And it is obvious that various changes and changes can be made without departing from the scope. Such modified embodiments should not be individually understood from the spirit and scope of the present invention, but should be said to fall within the scope of the claims of the present invention.

Claims (15)

delete A performance verification method for verifying data delivery performance between a publisher and a subscriber in a Data Distribution Service (DDS) using an Interface Description Language (IDL), comprising:
The process of creating an interface definition language;
generating a mock issuer for issuing verification data according to the produced interface definition language;
generating a mock subscriber for subscribing verification data from the mock publisher; and
and analyzing a log generated while transferring verification data from the mock publisher to the mock subscriber. 3. The method according to claim 2,
The interface definition language includes a programming language used for communication between publishers and subscribers who use different languages. 3. The method according to claim 2,
The verification data may include a topic used to classify data in the data distribution service. 3. The method according to claim 2,
The process of creating the mock issuer is:
The process of interpreting the produced interface definition language to generate a source code for creating a mock machine; and
Compiling the source code to produce a mock issuer; Performance verification method comprising a. 3. The method according to claim 2,
wherein the mock publisher includes a sending application that mimics the data sending function of the publisher. 5. The method according to claim 4,
The mock issuer,
a mock issuer declaration unit for declaring subscription to the issuer in the data distribution service; and
and a topic transmission and log output unit for transmitting a topic to the mock subscriber and outputting a log generated during topic transmission. 8. The method of claim 7,
The mock issuer,
The performance verification method further comprising a; when the transmission of the topic to the mock subscriber is finished, a mock issuer deletion unit for deleting the memory occupied in order to perform a data transmission function. 3. The method according to claim 2,
The process of creating the mock subscriber is,
The process of interpreting the produced interface definition language to generate a source code for creating a simulated subscriber; and
Compiling the source code to produce a simulated subscriber; Performance verification method comprising a. 3. The method according to claim 2,
The simulated subscriber is a performance verification method comprising a receiving application that simulates the data receiving function of the subscriber. 5. The method according to claim 4,
The mock subscriber,
a simulated subscriber declaration unit for declaring a subscription to the data distribution service as a subscriber; and
and a topic receiving and log output unit for receiving a topic from the mock publisher and outputting a log generated during topic reception. 12. The method of claim 11,
The mock subscriber,
When the topic reception from the mock publisher is finished, the mock subscriber deletion unit for deleting the memory occupied in order to perform a data reception function; the performance verification method further comprising a. 3. The method according to claim 2,
The process of analyzing the log is,
and generating an analyzer for receiving the log output from the mock publisher and the mock subscriber. 14. The method of claim 13,
The analyzer analyzes the received log to evaluate the performance of data transfer between the simulated publication and the simulated subscription period by analyzing the analysis application. A recording medium storing a computer program for performing the performance verification method according to any one of claims 2 to 14.

Images