A general protocol interface checking device and method for simulation test

Abstract

The embodiment of the present application discloses a universal protocol interface checking device and method for simulation test. In a specific embodiment, the device comprises a protocol interface checking device generation wizard component for creating at least one protocol interface checking component; and the protocol interface checking component for realizing the protocol interface checking function. The embodiment can effectively solve the problem that the independently developed simulation application program is difficult to debug the network and protocol interface alone due to the role attribute caused by the distribution in the LVC simulation; and the present application decouples the device and the model protocol through the wizard mode, so that the method is more universal and general.

Description

Technical Field

[0001] This invention relates to the field of simulation testing. More specifically, it relates to a universal protocol interface verification device and method for simulation testing. Background Technology

[0002] LVC simulation experiments involve various interaction standards and architectures, such as the DIS standard (IEEE Std 1278, Distributed Interactive Simulation), the HLA standard (IEEE Std 1516, IEEE Standard for Modeling), the TENA architecture (Test and Training Enabling Architecture), and the OMG DDS specification (Object Management Group Data Distributed Service), which is gradually becoming a research hotspot with the popularization of the Logistics Network. Each architecture or standard specification implies a simulation object model format. For example, DIS uses Protocol Data Units (PDUs), HLA defines Object Model Templates (OMTs), and TENA defines the TENA Meta-Model. Applications use the corresponding simulation object model format to define the data content they interact with, i.e., the model protocol. In LVC simulation experiments, model protocols are characterized by complexity, variability, and inconsistency, and a single joint digital simulation experiment generally involves multiple model protocols.

[0003] LVC simulation application interaction involves sending and receiving data packets generated after the model protocol has been serialized. Therefore, sending and receiving the model protocol is the foundation of LVC simulation application interaction and constitutes an important protocol interface.

[0004] LVC simulation experiments involve different applications simulating different model elements, which are interconnected and work together to complete the simulation. Each successful LVC simulation requires troubleshooting network issues, protocol interface problems, and model calculation issues during integration and debugging. Due to the distributed nature of LVC simulation experiments, independently developed simulation applications struggle to independently resolve network and protocol interface issues related to other applications. Summary of the Invention

[0005] The purpose of this invention is to provide a universal protocol interface verification device and method for simulation experiments, so as to solve at least one of the problems existing in the prior art.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] The first aspect of the present invention provides a universal protocol interface verification device for simulation experiments, the device comprising:

[0008] A protocol interface verification device generation wizard component is used to create at least one protocol interface verification component;

[0009] The protocol interface verification component is used to implement the protocol interface verification function.

[0010] Optionally, the protocol interface verification device generates a wizard component that can be started and run directly in response to double-clicking or command line input.

[0011] Optionally, the protocol interface verification component can be started and run directly in response to double-clicking or command line.

[0012] Optionally, the protocol interface verification device generation wizard component includes a visualization module, a compiler configuration module, a protocol parser loading module, a protocol configuration module, a parameter pre-configuration module, a protocol interface verification component template module, a file generation module, and a component generation module; wherein

[0013] The visualization module is used to provide a wizard-style interface window and controls for inputting configuration information;

[0014] The compiler configuration module is used to configure and schedule the compiler, and to set compile-time and link-time dependencies;

[0015] The protocol parser loading module is used to configure and schedule the model protocol parser and parse the application model protocol configured by the user.

[0016] The protocol configuration module is used to specify the application model protocol and the content of the protocol interface verification;

[0017] The parameter pre-configuration module is used to configure the setting parameters of the protocol interface verification component;

[0018] The protocol interface verification component template module is used to provide protocol interface verification component template content;

[0019] The file generation module is used to generate the program implementation file of the protocol interface verification component based on the configuration information and the content of the protocol interface verification component template.

[0020] The component generation module is used to schedule and monitor the compiler to compile the program implementation file, and to provide real-time feedback on compilation information and generate the protocol interface verification component.

[0021] Optionally, the protocol interface verification component includes a configuration module, a data path module, an operation control module, a model protocol sending and construction module, and a model protocol receiving and verification module; wherein

[0022] The configuration module is used to configure the operating parameters of the protocol interface verification component;

[0023] The data path module is used to establish a data transmission or reception path;

[0024] The operation control module is used to control the operation of the protocol interface verification component;

[0025] The model protocol sending construction module is used to send the data content of the application model protocol;

[0026] The model protocol receiving and verification module is used to receive the application model protocol and verify the data content.

[0027] Optionally, the protocol interface verification device generation wizard component and the protocol interface verification component are deployed on the same or different computers.

[0028] Optionally, the protocol interface verification component and the simulation test are deployed on the same or different computers.

[0029] A second aspect of the present invention provides a verification method for a general protocol interface verification device used in simulation experiments, characterized in that the method includes...

[0030] Use the protocol interface verification device to generate a wizard component and create at least one protocol interface verification component.

[0031] Implement the protocol interface verification function using the protocol interface verification component.

[0032] Optionally, the creation of at least one protocol interface verification component includes

[0033] Configure the relevant parameters of the protocol interface verification component;

[0034] Configure the protocol parser and the computer environment for the protocol parser;

[0035] Configure the model protocol;

[0036] Configure the compiler and the computer environment for the compiler;

[0037] Generate the program implementation file for the protocol interface verification component;

[0038] The compiler is scheduled to compile and link to generate the protocol interface verification component.

[0039] Optionally, the implementation of the protocol interface verification function includes

[0040] Run the test to be verified;

[0041] Start the protocol interface verification component and establish a link with the test to be verified;

[0042] When the interfaces to be verified are different model protocols, verify whether the model protocol interfaces are correct respectively.

[0043] After the model protocol interface verification is completed, the protocol interface verification component is turned off.

[0044] The beneficial effects of this invention are as follows:

[0045] This invention provides a general protocol interface verification device for simulation experiments, which can effectively solve the problem in LVC simulation where independently developed simulation applications are difficult to debug network and protocol interfaces due to the role attributes caused by distributed systems. Moreover, this invention decouples the device from the model protocol through a wizard-driven approach, making the method more universal and applicable. Attached Figure Description

[0046] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

[0047] Figure 1 This diagram illustrates a general protocol interface verification device for simulation experiments provided in an embodiment of the present invention. Detailed Implementation

[0048] To more clearly illustrate the present invention, the following description, in conjunction with embodiments and accompanying drawings, further explains the invention. Similar components in the drawings are indicated by the same reference numerals. Those skilled in the art should understand that the specific description below is illustrative rather than restrictive and should not be construed as limiting the scope of protection of the present invention.

[0049] LVC simulation experiments involve different applications simulating different model elements, which are interconnected and work together to complete the simulation. Each successful LVC simulation requires troubleshooting network issues, protocol interface problems, and model calculation issues during integration and debugging. Due to the distributed nature of LVC simulation experiments, independently developed simulation applications struggle to independently resolve network and protocol interface issues related to other applications.

[0050] In view of this, one embodiment of the present invention provides a general protocol interface verification device for simulation experiments. The device includes a protocol interface verification device generation wizard component for creating at least one protocol interface verification component; the protocol interface verification component is used to implement the protocol interface verification function.

[0051] Specifically, this embodiment provides a model protocol-independent universal protocol interface testing device. Firstly, by pairwise matching of LVC application protocol interfaces, it addresses the problem in LVC simulation experiments where independently developed simulation applications struggle to debug network and protocol interfaces independently due to the role attributes resulting from distributed architecture. That is, if an LVC application sends a model protocol, the device in this embodiment has the capability to receive and verify that model protocol; if an LVC application receives a model protocol, the device in this embodiment has the capability to send specified data using that model protocol. Secondly, addressing the coupling issue between the device and the model protocol, by analyzing traditional protocol interface verification devices, it decouples the specific, differentiated model protocol code from the general, procedural program framework, generating and constructing the protocol interface verification device in a "wizard" manner. The "wizard" establishes a connection between the protocol interface verification device and the specific model protocol. When a model protocol is added or changed, the "wizard" can generate and construct a protocol interface verification device adapted to the added or changed model protocol.

[0052] Furthermore, a wizard-based, simulation model-independent general protocol interface verification device for LVC simulation includes two components: a protocol interface verification device generation wizard component and a protocol interface verification component. This embodiment relies on both components to function; that is, it must include at least the protocol interface verification device generation wizard component and one or more protocol interface verification components. Neither component can be omitted. The one or more protocol interface verification components are isomorphic, with identical deployment methods and operating procedures. They can be used in parallel within the same scenario.

[0053] In one possible implementation, the protocol interface verification device generates a wizard component that is launched directly in response to a double-click or command line.

[0054] In one possible implementation, the protocol interface verification component is started and run directly in response to double-clicking or command line input.

[0055] Specifically, the protocol interface verification device generation wizard component is an independent, executable application. Physically, it is an executable device that users can launch and run directly by double-clicking or using the command line.

[0056] Furthermore, the protocol interface verification component is an independent, executable application, physically taking the form of an executable device, which users can start and run directly by double-clicking or via command line.

[0057] In one possible implementation, the protocol interface verification device's wizard component includes a visualization module, a compiler configuration module, a protocol parser loading module, a protocol configuration module, a parameter pre-configuration module, a protocol interface verification component template module, a file generation module, and a component generation module. The visualization module provides a wizard-style interface window and controls for inputting configuration information. The compiler configuration module configures and schedules the compiler and sets compile-time and link-time dependencies. The protocol parser loading module configures and schedules the model protocol parser and parses the user-configured application model protocol. The protocol configuration module specifies the application model protocol and the content of the protocol interface verification. The parameter pre-configuration module configures the setting parameters of the protocol interface verification component. The protocol interface verification component template module provides the template content for the protocol interface verification component. The file generation module generates the program implementation file of the protocol interface verification component based on the configuration information and the template content. The component generation module schedules and monitors the compiler to compile the program implementation file and provides real-time feedback on compilation information and generates the protocol interface verification component.

[0058] Specifically, such as Figure 1 As shown, the protocol interface verification device generation wizard component ① includes eight modules: visualization module, compiler configuration module, protocol parser loading module, protocol configuration module, parameter pre-configuration module, protocol interface verification component template module, file generation module, and component generation module.

[0059] The visualization module provides a visual wizard-style interface window, where users can input relevant configuration information through controls such as input boxes, option boxes, and buttons;

[0060] The compiler configuration module is used to configure and schedule the compiler required for the compilation and linking of the protocol interface verification component ②, and has the function of setting compile-time dependencies and link-time dependencies;

[0061] The protocol parser loading module is used to configure and schedule specific interaction standard specifications or architecture model protocol parsers④, and supports parsing user-configured application model protocols;

[0062] The protocol configuration module is used to specify the application model protocol (⑤) and the specific content of the protocol interface verification.

[0063] The parameter pre-configuration module is used to configure one or more pre-set parameters of the protocol interface verification component ②;

[0064] The protocol interface verification component template module provides general, procedural protocol interface verification component template content.

[0065] The file generation module is used to output the program implementation file of the protocol interface verification component ② based on the user's customized input and the template of the protocol interface verification component ②.

[0066] The component generation module is used to schedule and monitor the configured compiler ③ to compile the program implementation file of the protocol interface verification component ②, provide real-time feedback on compilation information, and generate the protocol interface verification component ②.

[0067] In one possible implementation, the protocol interface verification component includes a configuration module, a data path module, an operation control module, a model protocol sending construction module, and a model protocol receiving verification module; wherein the configuration module is used to configure the operating parameters of the protocol interface verification component; the data path module is used to establish a sending or receiving data path; the operation control module is used to control the operation of the protocol interface verification component; the model protocol sending construction module is used to send the data content of the application model protocol; and the model protocol receiving verification module is used to receive the application model protocol and verify the data content.

[0068] Specifically, the protocol interface verification component ② includes five modules: configuration module, data path module, operation control module, model protocol sending construction module, and model protocol receiving verification module.

[0069] The configuration module is used to configure the running parameters of the protocol interface verification component ②, including data path parameters, runtime parameters, etc.

[0070] The data path module is used to establish or disconnect the link with the simulation experiment, and to establish a data transmission or reception path;

[0071] The operation control module is used to control the operation of the protocol interface verification component ②, and provides control modes such as start, pause, and stop;

[0072] The Model Protocol ⑤ sending construction module provides a visual window ⑩, configuration file ⑨ and other methods to construct the data content of Model Protocol ⑤ according to user-specified data and send it;

[0073] The model protocol receiving and verification module receives the model protocol (⑤) and provides methods such as a visual window (⑧) and a readable file (⑦) to verify the content of the model protocol data (⑤).

[0074] In one possible implementation, the protocol interface verification device generation wizard component and the protocol interface verification component are deployed on the same or different computers.

[0075] Specifically, the protocol interface verification device generation wizard component ① and the protocol interface verification component ② can be deployed on the same computer or on different computers.

[0076] In one possible implementation, the protocol interface verification component and the simulation test are deployed on the same or different computers.

[0077] Specifically, during protocol interface verification, the protocol interface verification component ② runs in an interconnected network environment, just like the simulation test resource ⑥ to be verified. The protocol interface verification component ② can be deployed on the same computer as the resource ⑥ to be verified or other simulation test resources, or it can be deployed on a separate computer.

[0078] This embodiment provides a wizard-based universal protocol interface verification device, which can effectively solve the problem in LVC simulation where independently developed simulation applications are difficult to debug network and protocol interfaces due to the role attributes caused by distributed systems. Moreover, this invention decouples the device from the model protocol through a wizard approach, making the method more universal and applicable.

[0079] Another embodiment of the present invention provides a verification method for a general protocol interface verification device for simulation experiments. The method includes using a protocol interface verification device generation wizard component to create at least one protocol interface verification component; and using the protocol interface verification component to implement the protocol interface verification function.

[0080] Specifically, the operation of the general protocol interface verification device in this embodiment includes two processes: the protocol interface verification component creation process and the protocol interface verification function execution process.

[0081] In one possible implementation, creating at least one protocol interface verification component includes configuring relevant parameters of the protocol interface verification component; configuring a protocol parser and its computer environment; configuring a model protocol; configuring a compiler and its computer environment; generating the program implementation file of the protocol interface verification component; and scheduling the compiler to compile and link to generate the protocol interface verification component.

[0082] Specifically, the creation process of protocol interface verification component ② is the process by which the user uses the protocol interface verification device to create protocol interface verification component ② using the wizard component ①. It includes the following steps:

[0083] Configure the relevant parameters of the protocol interface verification component ②, including the name of the protocol interface verification component ②, running parameters, etc.

[0084] Configure the protocol parser (④) and its dependent computer environment;

[0085] Configuration model protocol ⑤;

[0086] Configure the compiler for the programming language, and the computer environment it depends on;

[0087] Generate the program implementation file for protocol interface verification component ②;

[0088] The scheduler compiler compiles and links to generate protocol interface verification components.

[0089] In one possible implementation, the protocol interface verification function includes running the test to be verified; starting the protocol interface verification component and establishing a link with the test to be verified; verifying whether the model protocol interface is correct when the interface to be verified is a different model protocol; and closing the protocol interface verification component after the model protocol interface verification is completed.

[0090] Specifically, the protocol interface verification function execution process is the process by which the user uses the protocol interface verification component ② to complete the corresponding protocol interface verification function. This includes the following steps:

[0091] Run the test application to be verified (⑥);

[0092] Start the protocol interface verification component ② and establish a link with the test to be verified;

[0093] If the interface to be verified is the sending model protocol ⑤, then use the model protocol receiving verification function to check the content of the protocol model data to be verified in the receiving window ⑧ in the visualization window or the readable file ⑦. If the content of the protocol model data meets expectations, it means that the sending model protocol ⑤ interface to be verified is correct; otherwise, it means that there is a problem with the sending model protocol ⑤ interface to be verified.

[0094] If the interface to be verified is the receiving model protocol ⑤, then use the model protocol sending construction verification function. Specify the data of model protocol ⑤ in the sending window ⑩ in the visualization window or the configuration file ⑨, and send it to the test application to be verified. If the test application to be verified receives the data correctly and the data processing is as expected, it means that the receiving model protocol ⑤ interface to be verified is correct; otherwise, it means that there is a problem with the receiving model protocol ⑤ interface to be verified.

[0095] After the model protocol interface verification is completed (⑤), close the protocol interface verification component (②).

[0096] LVC simulation testing is an increasingly widespread simulation testing mode. Cross-regional joint testing is commonplace. Back-to-back pre-debugging and changes or adjustments to model protocols are inevitable. This method can effectively improve device quality, lower technical barriers, and save testing costs, and has broad application prospects.

[0097] In the description of this invention, it should be noted that the terms "upper," "lower," etc., indicating the orientation or positional relationship are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Unless otherwise expressly specified and limited, the terms "installed," "connected," and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication between two elements. For those skilled in the art, the specific meaning of the above terms in this invention can be understood according to the specific circumstances.

[0098] It should also be noted that in the description of this invention, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0099] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the implementation of the present invention. For those skilled in the art, other variations or modifications can be made based on the above description. It is impossible to exhaustively list all the implementation methods here. All obvious variations or modifications derived from the technical solutions of the present invention are still within the protection scope of the present invention.

Claims

1. A general protocol interface verification device for simulation experiments, characterized in that, The device includes A protocol interface verification device generation wizard component is used to create at least one protocol interface verification component; Protocol interface verification component, used to implement protocol interface verification function; The protocol interface verification device generation wizard component includes a visualization module, a compiler configuration module, a protocol parser loading module, a protocol configuration module, a parameter pre-configuration module, a protocol interface verification component template module, a file generation module, and a component generation module; wherein... The visualization module is used to provide a wizard-style interface window and controls for inputting configuration information; The compiler configuration module is used to configure and schedule the compiler, and to set compile-time and link-time dependencies; The protocol parser loading module is used to configure and schedule the model protocol parser and parse the application model protocol configured by the user. The protocol configuration module is used to specify the application model protocol and the content of the protocol interface verification; The parameter pre-configuration module is used to configure the setting parameters of the protocol interface verification component; The protocol interface verification component template module is used to provide protocol interface verification component template content; The file generation module is used to generate the program implementation file of the protocol interface verification component based on the configuration information and the content of the protocol interface verification component template. The component generation module is used to schedule and monitor the compiler to compile the program implementation file, and to provide real-time feedback on compilation information and generate the protocol interface verification component. The protocol interface verification component includes a configuration module, a data path module, an operation control module, a model protocol sending and construction module, and a model protocol receiving and verification module. in The configuration module is used to configure the operating parameters of the protocol interface verification component; The data path module is used to establish a data transmission or reception path; The operation control module is used to control the operation of the protocol interface verification component; The model protocol sending construction module is used to send the data content of the application model protocol; The model protocol receiving and verification module is used to receive the application model protocol and verify the data content.

2. The universal protocol interface verification device for simulation experiments according to claim 1, characterized in that, The protocol interface verification device generates a wizard component, which can be started and run directly by double-clicking or command line.

3. The universal protocol interface verification device for simulation experiments according to claim 2, characterized in that, The protocol interface verification component is activated by double-clicking or directly starting from the command line.

4. The universal protocol interface verification device for simulation experiments according to claim 1, characterized in that, The protocol interface verification device generation wizard component and the protocol interface verification component are deployed on the same or different computers.

5. The universal protocol interface verification device for simulation experiments according to claim 4, characterized in that, The protocol interface verification component and simulation test are deployed on the same or different computers.

6. A verification method for a general protocol interface verification device for simulation experiments as described in any one of claims 1-5, characterized in that, The method includes Use the protocol interface verification device to generate a wizard component and create at least one protocol interface verification component. Implement the protocol interface verification function using the protocol interface verification component.

7. The verification method for the general protocol interface verification device for simulation experiments according to claim 6, characterized in that, The creation of at least one protocol interface verification component includes Configure the relevant parameters of the protocol interface verification component; Configure the protocol parser and the computer environment for the protocol parser; Configure the model protocol; Configure the compiler and the computer environment for the compiler; Generate the program implementation file for the protocol interface verification component; The compiler is scheduled to compile and link to generate the protocol interface verification component.

8. The verification method of the general protocol interface verification device for simulation experiments according to claim 7, characterized in that, The implementation of the protocol interface verification function includes: Run the test to be verified; Start the protocol interface verification component and establish a link with the test to be verified; When the interfaces to be verified are different model protocols, verify whether the model protocol interfaces are correct respectively. After the model protocol interface verification is completed, the protocol interface verification component is turned off.

Images