A Data Exchange Method between LVC-DE Distributed Synthetic Environment and pRTI System

Abstract

The present invention provides a data exchange method between an LVC-DE distributed synthesis environment and a pRTI system. S1 declares a TENA object instance. The LVC-DE distributed synthesis environment uses the TENA object model as the data structure for describing information exchange, and uses the TENA object instance as the basic unit for information exchange. The TENA object model description file conforms to the TDL (TENA Definition Language) specification. Declare a pRTI object instance. The pRTI system uses the pRTI object instance as the basic unit for information exchange, and the pRTI object class and interaction class are used as the data structure for describing information exchange. The object class and interaction class are stored in the FOM (Federation Object Model) file. By means of the proposed data exchange method between the LVC-DE distributed synthesis environment and the pRTI system, it is possible to solve the problems that the existing data exchange method between the LVC-DE distributed synthesis environment and the pRTI system depends on custom development, lacks generality, has high requirements for the user's programming ability, and has a long development cycle. By generating an association file, generality is improved without custom development.

Description

Technical Field

[0001] The present invention relates to the field of data of LVC-DE distributed synthetic environment and pRTI system. Specifically, it relates to a data exchange method between LVC-DE distributed synthetic environment and pRTI system. Background Art

[0002] As part of the common technical framework for modeling and simulation advocated by the High Level Architecture (HLA) Simulation Master Plan (MSMP), it is not targeted at a specific application field but applicable to the development and integration of all fields. With the development of simulation technology, especially interactive simulation technology, HLA has been widely used in the development and integration of modeling and simulation systems. For simulation systems adopting the HLA architecture, the operation of the simulation system and the interaction and coordination among simulation members are all realized through the Run Time Infrastructure (RTI). pRTI is a platform-independent software developed by Pitch AIS. Currently, there are a large number of simulation systems based on pRTI in the simulation field. Therefore, realizing the data exchange between the LVC-DE distributed synthetic environment and the pRTI system is of great significance for enhancing the application scenarios of the two heterogeneous systems.

[0003] The existing data exchange method between the LVC-DE distributed synthetic environment and the pRTI system is to develop an independent software program in a programming manner according to a fixed data model to complete the data mapping association between the two systems. The implementation principle of this method is simple, but when it is necessary to replace other data models or modify the data model, it is necessary to re-edit the data exchange software program, lacking generality. In addition, since this program needs to be customized for each matching data model, there are problems such as long development time and high requirements for users' programming ability. Therefore, we make improvements and propose a data exchange method between the LVC-DE distributed synthetic environment and the pRTI system. Summary of the Invention

[0004] The purpose of the present invention is to address the problems raised in the existing background art. To achieve the above-mentioned invention purpose, the present invention provides the following technical solution: A data exchange method between LVC-DE distributed synthetic environment and pRTI system. S1: Declare a TENA object instance. The LVC-DE distributed synthetic environment uses the TENA object model as the data structure for describing information exchange, and uses the TENA object instance as the basic unit for information exchange. The TENA object model description file conforms to the TDL (TENA Definition Language) specification.

[0005] S2 declares a pRTI object instance. The pRTI system uses the pRTI object instance as the basic unit for information exchange, and the pRTI object class and interaction class are used as data structures to describe information exchange. The object class and interaction class are stored in the FOM (Federation Object Model) file;

[0006] S3 associates the TENA object instance with the pRTI object instance. After the declaration of the TENA object instance and the pRTI object instance is completed, it is necessary to establish a mapping relationship between the two, providing rules for the subsequent data exchange between the LVC-DE distributed synthesis environment and the pRTI system;

[0007] S4 performs data exchange. To adapt to different development environments, the present invention uses a gateway program to subscribe to and publish LVC-DE distributed synthesis environment data, and uses a pRTI communication program to subscribe to and publish pRTI system data. The two programs communicate using a pipeline and use clear text string messages. After the gateway program runs, the gateway program starts the pRTI communication program. The gateway program receives the LVC-DE distributed synthesis environment data information, displays the mapping relationship and data, and sends the LVC-DE distributed synthesis environment data information to the pRTI communication program through pipeline communication, and receives the pRTI system data information sent by the pRTI communication program.

[0008] As a preferred technical solution of the present invention, S1 declares a TENA object instance, including the following processes:

[0009] S1-1 selects a TENA object model description file and saves the path address of the object model description file;

[0010] S1-2 opens the TENA object model description file according to the path address and reads all the contents of the file;

[0011] S1-3 judges the structure identifier of each line of the TENA object model description file line by line;

[0012] S1-4-1 If the structure identifier is of types such as local class, class, message, etc., go to step S1-5;

[0013] S1-4-2 If the structure identifier is of enumeration type, save the enumeration name and enumeration content, store them in the data structure, and go to step S1-3;

[0014] S1-4-3 If the structure identifier is an end symbol, go to step S1-7;

[0015] S1-5 within the class / local class / message structure processing branch, judges the type identifier of each line content in the structure;

[0016] S1-6-1 If the content identifier is data, store the data type and name in the data structure, and go to step S1-5;

[0017] S1-6-2 If the content identifier is a method, store the method return type, name, parameter input / output types, parameter data types, parameter names, error value types, and error value names in the data structure, and go to step S1-5;

[0018] S1-6-3 If the content identifier is an end symbol, go to step S1-3;

[0019] S1-7 Rearrange the data structure according to the inheritance and aggregation relationships to form a TENA object model column diagram;

[0020] S1-8 Select the TENA object model name for which to declare a TENA object instance, and input the TENA object instance name.

[0021] As a preferred technical solution of the present invention, declaring a pRTI object instance in S2 includes the following steps:

[0022] S2-1 Select the pRTI system FOM file and save the object model file path address;

[0023] S2-2 Open the pRTI system FOM file according to the path address and read all the contents of the file;

[0024] S2-3 Search for the sub-element keyword "objects" and perform object class data model parsing;

[0025] S2-4 Judge each sub-element keyword;

[0026] S2-5-1 If the sub-element keyword is "attribute", parse the attribute name and type, and store them in the data structure, then go to step S2-4;

[0027] S2-5-2 If the sub-element keyword is "objectClass", parse the object class name and store it in the data structure, then go to step S2-4;

[0028] S2-5-3 If the sub-element keyword is an end symbol, go to step S2-6;

[0029] S2-6 Search for the element keyword "interactions" and perform interaction class object model parsing;

[0030] S2-7 Judge each sub-element keyword;

[0031] S2-8-1 If the keyword of the child element is "parameter", parse the parameter name and parameter type, store them in the data structure, and go to step S2-7;

[0032] S2-8-2 If the keyword of the child element is "interactionClass", parse the interaction class name, store it in the data structure, and go to step S2-7;

[0033] S2-8-3 If the keyword of the child element is the end symbol, go to step S2-9;

[0034] S2-9 Search for the element keyword "fixedRecordData", parse the fixed data name, parse the child elements to obtain the data name and data type, and store the corresponding interaction class parameter type and object class attribute type in the data structure;

[0035] S2-10 Sort out the data structure according to the nesting relationship to form a pRTI system object model column diagram;

[0036] S2-11 Select the pRTI object class or interaction class name for which the pRTI object instance is to be declared, input the pRTI object instance name, and establish a pRTI publication object instance column diagram and a subscription object instance column diagram.

[0037] As a preferred technical solution of the present invention, S3 associating the TENA object instance with the pRTI object instance

[0038] includes the following steps:

[0039] S3-1 Read the pRTI object instance column diagram generated in step S2-11 and expand all the attributes of the object instance;

[0040] S3-2 Read the TENA object instance column diagram generated in step S1-8 and expand all the attributes of the object instance;

[0041] S3-3 Select a certain attribute of the TENA object instance to map with a certain attribute of the pRTI object instance pRTI object instance pRTI object instance, establish a mapping column diagram, and the mapping content includes the subscription and publication relationship, the TENA object instance type, the TENA object instance name, the TENA object instance attribute name, the TENA object instance attribute data type, the pRTI object instance type, the pRTI object instance name, the pRTI object instance attribute name, and the pRTI object instance attribute data type. The rules that the mapping needs to follow include: one TENA object instance or pRTI object instance can be mapped to multiple pRTI object instances or TENA object instances, the same attribute can be mapped to multiple publication attributes, and only one subscription attribute can be mapped;

[0042] S3-4 Select the main attribute. After the main attribute of the ordered data type is updated, publish the data type. Save the mapping relationship and store it as the associated description file.xml.

[0043] As a preferred technical solution of the present invention, S4 performing data exchange includes the following steps:

[0044] S4a-1 The gateway program starts, creates a pipeline for communicating with the pRTI communication program, and the pipeline name is the gateway program name;

[0045] S4a-2 Parse the gateway association description file generated in step S3, create a TENA object instance column diagram, join the LVC-DE distributed synthesis environment according to the association description file, and order and publish the corresponding TENA object instance;

[0046] S4a-3 Start the pRTI communication program, and the startup parameters are the gateway association description file and the pipeline name;

[0047] S4a-4 After the pipeline receives a new pRTI communication program connection signal, create a local socket to communicate with the pRTI communication program;

[0048] S4a-5 Start the heartbeat sending timer with a delay of 3000 milliseconds, and start the pRTI communication program survival determination timer with a delay of 30000 milliseconds;

[0049] S4a-6 Determine whether the heartbeat timer triggers a signal. If so, execute step S4a-7; otherwise, continue to execute the loop;

[0050] S4a-7 Send a heartbeat message to the pRTI communication program;

[0051] S4a-8 Determine whether the pRTI communication program survival determination timer triggers a signal. If so, execute step S4a-9; otherwise, continue to execute the loop;

[0052] S4a-9 Pop up a window to prompt: "The participant has lost connection";

[0053] S4a-10 Determine whether LVC-DE distributed synthesis environment update data is received. If so, execute step (4a-11); otherwise, continue to execute the loop;

[0054] S4a-11 Parse the LVC-DE distributed synthesis environment data and send the corresponding pRTI system data message to the pRTI communication program;

[0055] S4a-12 Determine whether the button is clicked to join the pRTI system;

[0056] S4a-13 Send a join system message to the pRTI communication program;

[0057] S4a-14 Determine whether the button is clicked to exit the pRTI system;

[0058] S4a-15 Send a system exit message to the pRTI communication program;

[0059] S4a-16 Determine whether a communication message from the pRTI communication program is received. If it is a data message, execute step S4a-17-1. If it is a heartbeat message, execute step S4a-17-2. If it is a system join feedback message, execute step S4a-17-3. If no message is received, continue to execute the loop;

[0060] S4a-17-1 Receive a data message, parse the data content and store it in the object instance data column diagram;

[0061] S4a-17-2 Receive a heartbeat message, and update the survival determination timer delay time of the pRTI communication program again;

[0062] S4a-17-3 Receive a join feedback message, and parse the message content according to the message format;

[0063] S4a-18 Determine whether the received data message is the main attribute of the object instance. If so, execute step (4a-20), otherwise continue to execute the loop;

[0064] S4a-19 Determine the message content. If it is start, execute step (4a-21-1). If it is error, execute step (4a-21-2);

[0065] S4a-20 Update the object instance data to the LVC-DE distributed synthesis environment;

[0066] S4a-21-1 Pop up a window to prompt: "Join successful";

[0067] S4a-21-2 Pop up a window to prompt: "Join failed";

[0068] S4a-22 Determine whether the program is closed. If so, end the basic process, otherwise continue to execute the loop.

[0069] As a preferred technical solution of the present invention, S4 performs data exchange in which the pRTI communication program receives pRTI system data information and sends the pRTI system data information to the gateway program through pipeline communication. Receiving the LVC-DE distributed synthesis environment data information sent by the gateway program includes the following steps:

[0070] S4b-1 The pRTI communication program starts, parses the communication pipeline name, and joins the pipeline;

[0071] S4b-2 Parse the gateway association description file and create a data structure column diagram according to the object instance;

[0072] S4b-3 Start the heartbeat sending timer with a delay of 3000 milliseconds, and start the gateway survival determination timer with a delay of 30000 milliseconds;

[0073] S4b-4 Determine whether the heartbeat timer triggers a signal. If so, execute step S4b-5; otherwise, continue to execute the loop;

[0074] S4b-5 Send a heartbeat message to the gateway program;

[0075] S4b-6 Determine whether the gateway survival determination timer triggers a signal. If so, execute step S4b-7; otherwise, continue to execute the loop;

[0076] S4b-7 Close the pRTI communication program and end the process;

[0077] S4b-8 Determine whether pRTI system update data is received. If so, execute step S4b-9; otherwise, continue to execute the loop;

[0078] S4b-9 Parse the pRTI object instance data and send a data message corresponding to the LVC-DE distributed synthesis environment object instance to the gateway program.

[0079] As a preferred technical solution of the present invention, it further includes: S4b-10 Determine whether a communication message from the gateway program is received. If it is a data message, execute step S4b-11-1; if it is a heartbeat message, execute step S4b-11-2; if it is a join system message, execute step S4b-11-3; if no message is received, continue to execute the loop;

[0080] S4b-11-1 Receive a data message, parse the data content and store it in the object instance data column diagram;

[0081] S4b-11-2 Receive a heartbeat message and update the gateway survival determination timer delay time again;

[0082] S4b-11-3 Receive a join system message, join the pRTI system according to the federation name and agent name stored in the gateway association description file, and subscribe to and publish object instances;

[0083] S4b-11-4 Receive a quit system message and quit the heterogeneous system according to the federation name and agent name stored in the gateway association description file;

[0084] S4b-12 Determine whether the received data message is the main attribute of the object instance. If so, execute step S4b-14; otherwise, continue to execute the loop;

[0085] S4b-13 Determine whether the addition to the pRTI system is successful. If so, execute step S4b-15-1; otherwise, execute step S4b-15-2;

[0086] S4b-14 Update the object instance data to the LVC-DE distributed synthesis environment;

[0087] S4b-15-1 Send a successful addition message;

[0088] S4b-15-2 Send a failed addition message.

[0089] As a preferred technical solution of the present invention, when data is updated in the pRTI system or the LVC-DE distributed synthesis environment, it further includes S5a-1 Receive the object instance data published by the LVC-DE distributed synthesis environment;

[0090] S5a-2 Determine whether the object instance received from the LVC-DE distributed synthesis environment is the TENA object instance ordered in the association mapping. If so, execute S5a-3; otherwise, end this operation;

[0091] S5a-3 Analyze the object instance data received from the LVC-DE distributed synthesis environment according to the basic data type and store it in the corresponding position of the data in the mapping information column diagram;

[0092] S5a-4 Determine whether the main attribute is updated according to the content of the mapping information column diagram. If the main attribute is updated, execute S5a-5; if the main attribute is not updated, end this operation;

[0093] S5a-5 Call the DataWriter() function, fill the data parsed in S5a-4 into the data of the pRTI object instance associated with the object instance published by the LVC-DE distributed synthesis environment, and send this data to the pRTI communication program;

[0094] S5a-6 The pRTI communication program analyzes the data passed by the gateway program and publishes the correct data to the pRTI system.

[0095] As a preferred technical solution of the present invention, the process of the pRTI system updating data to the LVC-DE distributed synthesis environment further includes: S5b-1 The pRTI communication program receives the object instance data published by the pRTI system;

[0096] S5b-2 Determine whether the object instance received from the pRTI system is the pRTI object instance ordered in the association mapping. If so, execute S5b-3; otherwise, end this operation;

[0097] S5b-3 Analyze the object instance data received from the pRTI system according to the basic data type and store it in the corresponding position of the data in the mapping information column diagram;

[0098] S5b-4 determines whether the main attribute is updated according to the mapped content in the figure. If the main attribute is updated, execute S5a-5; if the main attribute is not updated, end this operation.

[0099] The pRTI communication program in S5b-5 calls the DataSend() function, fills the data parsed in S5b-3 into the data of the TENA object instance associated with the object instance published by the pRTI system, and sends the data to the gateway program.

[0100] The gateway program in S5b-6 parses the data sent by the pRTI communication program and publishes the data to the LVC-DE distributed synthesis environment.

[0101] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0102] In the solution of the present invention: through the proposed LVC-DE distributed synthesis environment and the pRTI system data exchange method, it can solve the problems that the existing LVC-DE distributed synthesis environment and the pRTI system data exchange method rely on customized development, lack generality, have high requirements for users' programming ability, and have a long development cycle. By generating associated files, generality is improved and customized development is not required; by modifying the source code of the executable program and compiling, the work of user programming is reduced, the development cycle is shortened, and it has been successfully applied to the LVC-DE distributed synthesis environment system, and can achieve efficient matching between the LVC-DE distributed synthesis environment and the system. The actual test results show that the data exchange method proposed by the present invention reduces the development cycle to more than 85% compared with the existing method that only relies on customized development, and users no longer need to perform programming operations. Description of the Drawings

[0103] Figure 1 It is a flowchart of declaring TENA object instances provided by the present invention;

[0104] Figure 2 It is a flowchart of declaring pRTI object instances provided by the present invention;

[0105] Figure 3 It is a flowchart of associating TENA object instances with pRTI object instances provided by the present invention;

[0106] Figure 4 It is a basic flowchart of the working process of the gateway program provided by the present invention;

[0107] Figure 5 It is a basic flowchart of the pRTI communication program process provided by the present invention;

[0108] Figure 6This is the basic flowchart of the process of updating data from the LVC-DE distributed synthesis environment provided by the present invention to the pRTI system;

[0109] Figure 7 This is the basic flowchart of the process of updating data from the pRTI system provided by the present invention to the LVC-DE distributed synthesis environment;

[0110] Figure 8 This is the format diagram of the heartbeat message sent by the gateway executable program provided by the present invention;

[0111] Figure 9 This is the format diagram of the data message sent by the gateway executable program provided by the present invention;

[0112] Figure 10 This is the format diagram of the join system message sent by the gateway executable program provided by the present invention;

[0113] Figure 11 This is the format diagram of the exit system message sent by the gateway executable program provided by the present invention;

[0114] Figure 12 This is the format diagram of the data message sent by the gateway executable program provided by the present invention;

[0115] Figure 13 This is the format diagram of the heartbeat message sent by the gateway executable program provided by the present invention;

[0116] Figure 14 This is the format diagram of the join feedback message sent by the pRTI communication program provided by the present invention. Detailed implementation manners

[0117] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Apparently, the described embodiments are specific implementations of the present invention and do not cover all embodiments.

[0118] Therefore, the following detailed description of the embodiments of the present invention is not intended to limit the scope of the present invention claimed, but is merely illustrative of some embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts fall within the scope of protection of the present invention.

[0119] It should be noted that, without conflict, the embodiments in the present invention and the features and technical solutions in the embodiments may be combined with each other. It should be noted that similar reference numerals and letters denote similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0120] Embodiment: Please refer to Figures 1-7 , Figures 8-14 , a data exchange method between the LVC-DE distributed synthesis environment and the pRTI system. S1 declares a TENA object instance. The LVC-DE distributed synthesis environment uses the TENA object model as the data structure for describing information exchange, uses the TENA object instance as the basic unit of information exchange, and the TENA object model description file conforms to the TDL (TENA Definition Language) specification;

[0121] S2 declares a pRTI object instance. The pRTI system uses the pRTI object instance as the basic unit of information exchange, and the pRTI object class and interaction class as the data structure for describing information exchange. The object class and interaction class are stored in the FOM (Federation Object Model) file;

[0122] S3 associates the TENA object instance with the pRTI object instance. After the declaration of the TENA object instance and the pRTI object instance is completed, it is necessary to establish a mapping relationship between the two to provide rules for the subsequent data exchange between the LVC-DE distributed synthesis environment and the pRTI system;

[0123] S4 performs data exchange. To adapt to different development environments, the present invention uses a gateway program to order and publish LVC-DE distributed synthesis environment data, uses a pRTI communication program to order and publish pRTI system data. The two programs communicate using a pipeline and use plain text string messages. After the gateway program runs, the gateway program starts the pRTI communication program. The gateway program receives the LVC-DE distributed synthesis environment data information, displays the mapping relationship and data, and sends the LVC-DE distributed synthesis environment data information to the pRTI communication program through pipeline communication, and receives the pRTI system data information sent by the pRTI communication program.

[0124] S1 declares a TENA object instance, including the following processes:

[0125] S1-1 selects a TENA object model description file and saves the path address of the object model description file;

[0126] S1-2 opens the TENA object model description file according to the path address and reads all the content of the file;

[0127] S1-3 judges the structure identifier of each line of the TENA object model description file line by line;

[0128] S1-4-1 If the structure identifier is of types such as local class, class, message, etc., go to step S1-5;

[0129] If the structure identifier is of the enumeration type, save the enumeration name and content, store them in the data structure, and go to step S1-3;

[0130] S1-4-3 If the structure identifier is an end symbol, go to step S1-7;

[0131] S1-5 Within the class / local class / message structure processing branch, judge the type identifier of each line content in the structure;

[0132] S1-6-1 If the content identifier is data, store the data type and name in the data structure, and go to step S1-5;

[0133] S1-6-2 If the content identifier is a method, store the method return type, name, parameter input / output types, parameter data types, parameter names, error value types, and error value names in the data structure, and go to step S1-5;

[0134] S1-6-3 If the content identifier is an end symbol, go to step S1-3;

[0135] S1-7 Rearrange the data structure according to the inheritance and aggregation relationships to form a TENA object model column diagram;

[0136] S1-8 Select the TENA object model name for which to declare a TENA object instance, and input the TENA object instance name.

[0137] Definition format of the "${module name}.tdl" file:

[0138]

[0139]

[0140] S2 Declaring a pRTI object instance includes the following steps:

[0141] S2-1 Select the pRTI system FOM file, and save the file path address of the object model;

[0142] S2-2 Open the pRTI system FOM file according to the path address, and read all the content of the file;

[0143] S2-3 Search for the sub-element keyword "objects" to perform object class data model parsing;

[0144] S2-4 Judge each sub-element keyword;

[0145] S2-5-1 If the sub-element keyword is "attribute", parse the attribute name and type, and store them in the data structure, then go to step S2-4;

[0146] If the child element keyword is objectClass, parse the object class name and store it in the data structure, then go to step S2-4;

[0147] If the child element keyword is the end symbol, go to step S2-6;

[0148] Search for the element keyword interactions and perform parsing of the interaction class object model;

[0149] Judge each child element keyword;

[0150] If the child element keyword is parameter, parse the parameter name and parameter type and store them in the data structure, then go to step S2-7;

[0151] If the child element keyword is interactionClass, parse the interaction class name and store it in the data structure, then go to step S2-7;

[0152] If the child element keyword is the end symbol, go to step S2-9;

[0153] Search for the element keyword fixedRecordData, parse the fixed data name, parse the child elements to obtain the data name and data type, and store the corresponding interaction class parameter types and object class attribute types in the data structure;

[0154] Sort out the data structure according to the nesting relationship to form a pRTI system object model column diagram;

[0155] Select the pRTI object class or interaction class name for which to declare a pRTI object instance, input the pRTI object instance name, and establish a pRTI published object instance column diagram and a subscribed object instance column diagram.

[0156] S2 Declare a pRTI object instance, the definition format of the "${module name}.xml" file:

[0157] <?xml version="1.0" encoding="UTF-8"?

[0158] <!DOCTYPE objectModel SYSTEM "hla.dtd">

[0159] <objectModel DTDversion="1516.2"name="DWKFOMTemplate.xml" type="FOM"version="1.0"date="2011-03-23"purpose="OMT modeling template" appDomain="HLARTI Verification"sponsor="DWK"pocName="Digital Weapon Kit"pocOrg=""pocPhone="010-58732755"pocEmail="" references="http: / / www.appsoft.com.cn">

[0160] <objects>

[0161] <objectClass name="HLAobjectRoot" sharing="Neither">

[0162] <attribute name="HLAprivilegeToDeleteObject" dataType="NA" updateType="NA" updateCondition="NA" ownership="DivestAcquire" sharing="PublishSubscribe" dimensions="NA" transportation="HLAreliable" order="TimeStamp" / >

[0163]

[0164] < / objects>

[0165] <interactions>

[0166] <interactionClass name="HLAinteractionRoot" sharing="Neither" dimensions="NA" transportation="HLAreliable" order="TimeStamp">

[0167] <parameter name="HLAreportPeriod" dataType="HLAseconds" semantics="Number of seconds between updates of instance" / >

[0168]

[0169] < / interactions>

[0170] <datatypes>

[0171] <enumerateddatatypes>

[0172] <enumeratedData name="HLAboolean" representation="HLAinteger32BE" semantics="Standard boolean type">

[0173] <enumerator name="HLAfalse" values="0" / >

[0174] <enumerator name="HLAtrue" values="1" / >

[0175]

[0176] < / enumerateddatatypes>

[0177] <fixedrecorddatatypes>

[0178] <fixedRecordData name="JCB_BaseData_GuideType" encoding="HLAfixedRecord">

[0179] <field name="ml" dataType="UInt32" / >

[0180] <field name="m" dataType="UInt16" / >

[0181] < / fixedrecorddatatypes>

[0182] < / datatypes>

[0183]

[0184] The S3 association of TENA object instances with pRTI object instances includes the following steps:

[0185] S3-1 Read the pRTI object instance column diagram generated in step S2-11, and expand all the attributes of the object instance;

[0186] S3-2 Read the TENA object instance column diagram generated in step S1-8, and expand all the attributes of the object instance;

[0187] S3-3 Select a certain attribute of the TENA object instance to map with a certain attribute of the pRTI object instance, establish a mapping column diagram, and the mapping content includes the order release relationship, TENA object instance type, TENA object instance name, TENA object instance attribute name, TENA object instance attribute data type, pRTI object instance type, pRTI object instance name, pRTI object instance attribute name, and pRTI object instance attribute data type. The rules that the mapping needs to follow include: one TENA object instance or pRTI object instance can correspond to and map multiple pRTI object instances or TENA object instances, the same attribute can map multiple published attributes, and only one order attribute can be mapped;

[0188] S3-4 Select the main attribute. When the main attribute of the ordered data type is updated, publish this data type externally. Save the mapping relationship and store it as an associated description file.xml.

[0189] The code for associating the TENA object instance with the pRTI object instance in S3 is as follows:

[0190] <Attribute association information>

[0191] <Class diagram information>

[0192] <Column A diagram information number = "Number of pRTI object instances">

[0193] <Column A sub - information name = "Object instance data type" id = "Object instance name" relation = "Subscription - publication relationship" / >

[0194] < / Column A diagram information>

[0195] <Column B diagram information number = "Number of TENA object instances">

[0196] <Column B sub - information name = "Object instance data type" id = "Object instance name" relation = "Subscription - publication relationship" / >

[0197] < / Column B diagram information>

[0198] < / Class diagram information>

[0199] <Gateway information struct = "pRTI" Aname = "pRTI heterogeneous system object model file path" Bname = "TENA system object model file path" model = "openDDS" / >

[0200] <Attribute subscription information>

[0201] <Subscription class information type = "" stream = "A2B" name = "TENA system object instance data type" id = "Object instance name">

[0202] <Subscription attribute information targetName = "TENA instance attribute name" fromAttrName = "pRTI instance attribute name" mainState = "Main attribute flag" targetAttr = "TENA system object instance attribute data type" fromName = "pRTI system object instance data type" fromAttrType = "Data type" fromClassID = "pRTI system object instance name" / >

[0203] < / Subscription class information>

[0204] <Publication class information type="" stream="B2A" name="pRTI system object instance data type" id="pRTI system object instance name">

[0205] <Publication attribute information targetName="pRTI system object instance name" fromAttrName="TENA system object instance attribute name" mainState="Main attribute identifier" targetAttr="pRTI system object instance attribute data type" fromName="TENA system object instance name" fromAttrType="TENA system object instance attribute data type" fromClassID="TENA system object instance name" / >

[0206] < / Publication class information>

[0207] < / Attribute subscription information>

[0208] < / Attribute association information>

[0209] S4 performs data exchange including the following steps:

[0210] S4a-1 The gateway program starts, creates a pipeline for communicating with the pRTI communication program, and the pipeline name is the gateway program name;

[0211] S4a-2 Parses the gateway association description file generated in step S3, creates a TENA object instance column diagram, joins the LVC-DE distributed synthesis environment according to the association description file, subscribes to and publishes the corresponding TENA object instance;

[0212] S4a-3 Starts the pRTI communication program, and the startup parameters are the gateway association description file and the pipeline name;

[0213] S4a-4 After the pipeline receives a new pRTI communication program connection signal, creates a local socket to communicate with the pRTI communication program;

[0214] S4a-5 Starts the heartbeat sending timer with a delay of 3000 milliseconds, and starts the pRTI communication program survival determination timer with a delay of 30000 milliseconds;

[0215] S4a-6 Determines whether the heartbeat timer triggers a signal. If so, executes step S4a-7; otherwise, continues to execute the loop;

[0216] S4a-7 Sends a heartbeat message to the pRTI communication program;

[0217] S4a-8 Determine whether the pRTI communication program survival judgment timer triggers a signal. If yes, execute step S4a-9; otherwise, continue to execute the loop.

[0218] S4a-9 Pop up a prompt: "The participant has lost connection".

[0219] S4a-10 Determine whether LVC-DE distributed synthesis environment update data is received. If yes, execute step (4a-11); otherwise, continue to execute the loop.

[0220] S4a-11 Analyze the LVC-DE distributed synthesis environment data and send the corresponding pRTI system data message to the pRTI communication program.

[0221] S4a-12 Determine whether the button is clicked to join the pRTI system.

[0222] S4a-13 Send a join system message to the pRTI communication program.

[0223] S4a-14 Determine whether the button is clicked to exit the pRTI system.

[0224] S4a-15 Send an exit system message to the pRTI communication program.

[0225] S4a-16 Determine whether a communication message from the pRTI communication program is received. If it is a data message, execute step S4a-17-1; if it is a heartbeat message, execute step S4a-17-2; if it is a join system feedback message, execute step S4a-17-3; if no message is received, continue to execute the loop.

[0226] S4a-17-1 Receive a data message, analyze the data content and store it in the object instance data column diagram.

[0227] S4a-17-2 Receive a heartbeat message and update the delay time of the pRTI communication program survival judgment timer again.

[0228] S4a-17-3 Receive a join feedback message and analyze the message content according to the message format.

[0229] S4a-18 Determine whether the received data message is the main attribute of the object instance. If yes, execute step (4a-20); otherwise, continue to execute the loop.

[0230] S4a-19 Judge the message content. If it is "start", execute step (4a-21-1); if it is "error", execute step (4a-21-2).

[0231] S4a-20 Update the object instance data to the LVC-DE distributed synthesis environment.

[0232] The pop-up window of S4a-21-1 prompts: "Join successfully";

[0233] The pop-up window of S4a-21-2 prompts: "Join failed";

[0234] S4a-22 determines whether the program is closed. If so, the basic process ends; otherwise, the loop continues.

[0235] In S4 for data exchange, the pRTI communication program receives pRTI system data information and sends the pRTI system data information to the gateway program through pipe communication. Receiving the LVC-DE distributed synthetic environment data information sent by the gateway program includes the following steps:

[0236] S4b-1 The pRTI communication program starts, parses the communication pipe name, and joins the pipe;

[0237] S4b-2 Parses the gateway association description file and creates a data structure column diagram according to the object instance;

[0238] S4b-3 Starts the heartbeat sending timer with a delay of 3000 milliseconds and starts the gateway survival determination timer with a delay of 30000 milliseconds;

[0239] S4b-4 Determines whether the heartbeat timer triggers a signal. If so, execute step S4b-5; otherwise, continue to execute the loop;

[0240] S4b-5 Sends a heartbeat message to the gateway program;

[0241] S4b-6 Determines whether the gateway survival determination timer triggers a signal. If so, execute step S4b-7; otherwise, continue to execute the loop;

[0242] S4b-7 Closes the pRTI communication program and ends the process;

[0243] S4b-8 Determines whether pRTI system update data is received. If so, execute step S4b-9; otherwise, continue to execute the loop;

[0244] S4b-9 Parses the pRTI object instance data and sends a data message corresponding to the LVC-DE distributed synthetic environment object instance to the gateway program.

[0245] S4b-10 Determines whether a communication message from the gateway program is received. If it is a data message, execute step S4b-11-1; if it is a heartbeat message, execute step S4b-11-2; if it is a join system message, execute step S4b-11-3; if no message is received, continue to execute the loop;

[0246] S4b-11-1 Receives a data message and parses the data content to store it in the object instance data column diagram;

[0247] S4b-11-2 receives a heartbeat message and updates the gateway survival determination timer delay time again;

[0248] S4b-11-3 receives a join system message, joins the pRTI system according to the federation name and agent name stored in the gateway association description file, and subscribes to and publishes object instances;

[0249] S4b-11-4 receives a leave system message and exits the heterogeneous system according to the federation name and agent name stored in the gateway association description file;

[0250] S4b-12 determines whether the received data message is the main attribute of the object instance. If so, it executes step S4b-14; otherwise, it continues to execute the loop;

[0251] S4b-13 determines whether the joining of the pRTI system is successful. If so, it executes step S4b-15-1; otherwise, it executes step S4b-15-2;

[0252] S4b-14 updates the object instance data to the LVC-DE distributed synthesis environment;

[0253] S4b-15-1 sends a join success message;

[0254] S4b-15-2 sends a join failure message.

[0255] When data is updated in the pRTI system or the LVC-DE distributed synthesis environment, it also includes S5a-1 receiving the object instance data published by the LVC-DE distributed synthesis environment;

[0256] S5a-2 determines whether the object instance received from the LVC-DE distributed synthesis environment is the TENA object instance subscribed in the association mapping. If so, it executes S5a-3; otherwise, it ends this operation;

[0257] S5a-3 parses the object instance data received from the LVC-DE distributed synthesis environment according to the basic data type and stores it in the corresponding position of the data in the mapping information column diagram;

[0258] S5a-4 determines whether the main attribute is updated according to the content of the mapping information column diagram. If the main attribute is updated, it executes S5a-5; if the main attribute is not updated, it ends this operation;

[0259] S5a-5 calls the DataWriter() function, fills the data parsed in S5a-4 into the data of the pRTI object instance associated with the object instance published by the LVC-DE distributed synthesis environment, and sends this data to the pRTI communication program;

[0260] The S5a-6pRTI communication program analyzes the data transmitted by the gateway program and publishes the correct data to the pRTI system.

[0261] The process of the pRTI system updating data to the LVC-DE distributed synthetic environment further includes: The S5b-1pRTI communication program receives the object instance data published by the pRTI system;

[0262] S5b-2 determines whether the object instance received from the pRTI system is the pRTI object instance ordered in the association mapping. If it is, execute S5b-3; otherwise, end this operation;

[0263] S5b-3 analyzes the object instance data received from the pRTI system according to the basic data type and stores it in the corresponding position of the data in the mapping information column diagram;

[0264] S5b-4 determines whether the main attribute has been updated according to the content of the mapping information column diagram. If the main attribute is updated, execute S5a-5; if the main attribute is not updated, end this operation;

[0265] The S5b-5pRTI communication program calls the DataSend() function, fills the data analyzed in S5b-3 into the data of the TENA object instance associated with the object instance published by the pRTI system, and sends the data to the gateway program;

[0266] The S5b-6 gateway program analyzes the data sent by the pRTI communication program and publishes the data to the LVC-DE distributed synthetic environment.

[0267] The above embodiments are only used to illustrate the present invention and do not limit the technical solutions described in the present invention. Although this specification has described the present invention in detail with reference to the above embodiments, the present invention is not limited to the above specific implementation manners. Therefore, any modification or equivalent replacement of the present invention; and all technical solutions and their improvements that do not depart from the spirit and scope of the invention are covered by the scope of the claims of the present invention.

Claims

1. A data exchange method between the LVC-DE distributed synthesis environment and the pRTI system, characterized in that It includes the following steps: S1: Declare a TENA object instance. The LVC-DE distributed synthesis environment uses the TENA object model as the data structure for describing information exchange, with the TENA object instance as the basic unit of information exchange. The TENA object model description file complies with the TDL specification; S2: Declare a pRTI object instance. The pRTI system uses the pRTI object instance as the basic unit of information exchange, and the pRTI object class and interaction class as the data structure for describing information exchange. The object class and interaction class are stored in the FOM file; S3: Associate the TENA object instance with the pRTI object instance. After the declaration of the TENA object instance and the pRTI object instance is completed, a mapping relationship needs to be established between the two to provide rules for the subsequent data exchange between the LVC-DE distributed synthesis environment and the pRTI system; S4: Execute data exchange. To adapt to different development environments, use the gateway program to order and publish the data of the LVC-DE distributed synthesis environment, and use the pRTI communication program to order and publish the data of the pRTI system. The two programs communicate using a pipeline and use clear-text string messages. After the gateway program runs, the gateway program starts the pRTI communication program. The gateway program receives the data information of the LVC-DE distributed synthesis environment, displays the mapping relationship and data, sends the data information of the LVC-DE distributed synthesis environment to the pRTI communication program through pipeline communication, and receives the data information of the pRTI system sent by the pRTI communication program; The said S1 includes the following steps: S1-1: Select the TENA object model description file and save the path address of the object model description file; S1-2: Open the TENA object model description file according to the path address and read all the contents of the file; S1-3: Judge the structure identifier of each line of the TENA object model description file line by line; The said S2 includes the following steps: S2-1: Select the pRTI system FOM file and save the path address of the object model file; S2-2: Open the pRTI system FOM file according to the path address and read all the contents of the file; S2-3: Search for the sub-element keyword "objects" and perform object class data model parsing; S2-4: Judge each sub-element keyword; S2-5-1: If the sub-element keyword is "attribute", parse the attribute name and attribute type and store them in the data structure, then go to S2-4; The said S4 includes the following steps: S4a-2: Parse the gateway association description file generated by S3, create a list of TENA object instances, add them to the LVC-DE distributed synthesis environment according to the association description file, and order and publish the corresponding TENA object instances; S4a-3: Start the pRTI communication program with the gateway association description file and the pipeline name as the startup parameters; S4a-4: After the pipeline receives a new connection signal from the pRTI communication program, create a local socket to communicate with the pRTI communication program; S4a-5: Start the heartbeat sending timer with a delay of 3000 milliseconds, and start the pRTI communication program survival determination timer with a delay of 30000 milliseconds; S4a-6: Determine whether the heartbeat timer triggers a signal. If yes, execute S4a-7; otherwise, continue to execute the loop; S4a-7: Send a heartbeat message to the pRTI communication program; S4a-8: Determine whether the pRTI communication program survival determination timer triggers a signal. If yes, execute S4a-9; otherwise, continue to execute the loop; S4a-9: Pop up a window to prompt "The participant has lost connection".

2. A data exchange method between an LVC-DE distributed synthesis environment and a pRTI system according to claim 1, characterized in that After executing the said S1-3, continue to execute the following steps: S1-4-1: If the structure identifier is of types such as local class or message, go to step S1-5; S1-4-2: If the structure identifier is of enumeration type, save the enumeration name and content, store them in the data structure, and go to S1-3; S1-4-3: If the structure identifier is an end symbol, go to S1-7; S1-5: Within the processing branch of the local class or message type structure, judge the type identifier of each line of content in the structure; S1-6-1: If the content identifier is data, store the data type and name in the data structure, and go to S1-5; S1-6-2: If the content identifier is a method, store the method return type, name, parameter input / output type, parameter data type, parameter name, error value type, and error value name in the data structure, and go to S1-5; S1-6-3: If the content identifier is an end symbol, go to S1-3; S1-7: Re-organize the data structure according to the inheritance and aggregation relationships to form a TENA object model list; S1-8: Select the TENA object model name for which to declare a TENA object instance, and input the TENA object instance name.

3. A method for data exchange between an LVC-DE distributed synthesis environment and a pRTI system according to claim 2, characterized in that, After executing the said S2-5-1, continue to execute the following steps: S2-5-2: If the sub-element keyword is objectClass, parse the object class name and store it in the data structure, and go to S2-4; S2-5-3: If the sub-element keyword is an end symbol, go to S2-6; S2-6: Search for the element keyword interactions and perform interactive class object model parsing; S2-7: Judge each sub-element keyword; S2-8-1: If the sub-element keyword is parameter, parse the parameter name and type, and store them in the data structure, and go to S2-7; S2-8-2: If the sub-element keyword is interactionClass, parse the interaction class name and store it in the data structure, and go to S2-7; S2-8-3: If the sub-element keyword is an end symbol, go to S2-9; S2-9: Search for the element keyword fixedRecordData, parse the fixed data name, parse the sub-elements to obtain the data name and type, and store the corresponding interactive class parameter type and object class attribute type in the data structure; S2-10: Re-organize the data structure according to the nesting relationship to form a pRTI system object model list; S2-11: Select the pRTI object class or interaction class name for which the pRTI object instance is to be declared, input the pRTI object instance name, and establish a list of pRTI publication object instances and a list of subscription object instances.

4. A data exchange method between an LVC-DE distributed synthesis environment and a pRTI system according to claim 3, characterized in that The said S3 includes the following steps: S3-1: Read the list of pRTI object instances generated by S2-11 and expand all the attributes of the object instances; S3-2: Read the list of TENA object instances generated by S1-8 and expand all the attributes of the object instances; S3-3: Select a certain attribute of the TENA object instance to map with a certain attribute of the pRTI object instance, establish a mapping list, and the mapping content includes the subscription-publishing relationship, the name of the TENA object instance attribute, the data type of the TENA object instance attribute, the name of the pRTI object instance attribute, and the data type of the pRTI object instance attribute; the rules to be followed for mapping include: one TENA object instance or pRTI object instance can be mapped to multiple pRTI object instances or TENA object instances, the same attribute can be mapped to multiple publishing attributes, but only one subscription attribute can be mapped; S3-4: Select the main attribute, and when the main attribute of the subscribed data type is updated, publish this data type externally; Save the mapping relationship and store it as an associated description file.xml.

5. A data exchange method between an LVC-DE distributed synthesis environment and a pRTI system according to claim 4, characterized in that After executing the said S4a-9, continue to execute the following steps: S4a-10: Determine whether LVC-DE distributed synthesis environment update data is received. If so, execute S4a-11; otherwise, continue to execute the loop; S4a-11: Parse the LVC-DE distributed synthesis environment data and send the corresponding data message of the pRTI system to the pRTI communication program; S4a-12: Determine whether the button is clicked to join the pRTI system; S4a-13: Send a join system message to the pRTI communication program; S4a-14: Determine whether the button is clicked to exit the pRTI system; S4a-15: Send an exit system message to the pRTI communication program; S4a-16: Determine whether a communication message of the pRTI communication program is received. If it is a data message, execute S4a-17-1; if it is a heartbeat message, execute S4a-17-2; if it is a join system feedback message, execute S4a-17-3; if no message is received, continue to execute the loop; S4a-17-1: Receive a data message and parse the data content and store it in the object instance data list; S4a-17-2: Receive a heartbeat message and update the delay time of the pRTI communication program survival determination timer again; S4a-17-3: Receive a join system feedback message and parse the message content according to the message format; S4a-18: Determine whether the received data message is the main attribute of the object instance. If so, execute S4a-20; otherwise, continue to execute the loop; S4a-19: Determine the message content. If it is start, execute S4a-21-1; if it is error, execute S4a-21-2; S4a-20: Update the object instance data to the LVC-DE distributed synthesis environment; S4a-21-1: Pop-up prompt "Join successful". S4a-21-2: Pop-up prompt "Join failed". S4a-22: Determine whether the program is closed. If yes, end the basic process; If not, continue the loop.

6. A method for data exchange between an LVC-DE distributed synthesis environment and a pRTI system according to claim 5, characterized in that In the data exchange executed in S4, the pRTI communication program receives the pRTI system data information and sends the pRTI system data information to the gateway program through pipe communication. The steps for receiving the LVC-DE distributed synthetic environment data information sent by the gateway program are as follows: S4b-1: The pRTI communication program starts, parses the communication pipe name, and joins the pipe; S4b-2: Parse the gateway association description file and create a data structure list according to the object instance; S4b-3: Start the heartbeat sending timer with a delay of 3000 milliseconds, and start the gateway survival determination timer with a delay of 30000 milliseconds; S4b-4: Determine whether the heartbeat timer triggers a signal. If yes, execute S4b-5; otherwise, continue the loop; S4b-5: Send a heartbeat message to the gateway program; S4b-6: Determine whether the gateway survival determination timer triggers a signal. If yes, execute S4b-7; otherwise, continue the loop; S4b-7: Close the pRTI communication program and end the process; S4b-8: Determine whether the pRTI system update data is received. If yes, execute S4b-9; otherwise, continue the loop; S4b-9: Parse the pRTI object instance data and send the data message of the corresponding LVC-DE distributed synthetic environment object instance to the gateway program.

7. A data exchange method between an LVC-DE distributed synthesis environment and a pRTI system according to claim 6, characterized in that After executing S4b-9, continue to execute the following steps: S4b-10: Determine whether the communication message from the gateway program is received. If it is a data message, execute S4b-11-1; if it is a heartbeat message, execute S4b-11-2; if it is a join system message, execute S4b-11-3; if no message is received, continue the loop; S4b-11-1: Receive a data message, parse the data content and store it in the object instance data list; S4b-11-2: Receive a heartbeat message and update the delay time of the gateway survival determination timer again; S4b-11-3: Receive a join system message, join the pRTI system according to the federation name and agent name stored in the gateway association description file, and order and publish the object instance; S4b-11-4: Receive an exit system message and exit the heterogeneous system according to the federation name and agent name stored in the gateway association description file; S4b-12: Determine whether the received data message is the main attribute of the object instance. If yes, execute S4b-14; otherwise, continue the loop; S4b-13: Determine whether the joining of the pRTI system is successful. If yes, execute S4b-15-1; otherwise, execute S4b-15-2; S4b-14: Update the object instance data to the LVC-DE distributed synthetic environment; S4b-15-1: Send a join successful message; S4b-15-2: Send a join failed message.

8. A data exchange method between an LVC-DE distributed synthesis environment and a pRTI system according to claim 7, characterized in that When data is updated in the pRTI system or the LVC-DE distributed synthetic environment, the following steps are also included: S5a-1: Receive the object instance data published by the LVC-DE distributed synthesis environment; S5a-2: Determine whether the object instance received from the LVC-DE distributed synthesis environment is the TENA object instance ordered in the association mapping. If so, execute S5a-3; otherwise, end this operation; S5a-3: Parse the object instance data received from the LVC-DE distributed synthesis environment according to the basic data type and store it in the corresponding position of the mapping information list; S5a-4: Determine whether the main attribute has been updated according to the content of the mapping information list. If the main attribute is updated, execute S5a-5; if the main attribute is not updated, end this operation; S5a-5: Call the DataWriter() function, fill the data parsed in S5a-4 into the data of the pRTI object instance associated with the object instance published by the LVC-DE distributed synthesis environment, and send this data to the pRTI communication program; S5a-6: The pRTI communication program parses the data passed by the gateway program and publishes the correct data to the pRTI system.

9. A data exchange method between an LVC-DE distributed synthesis environment and a pRTI system according to claim 8, characterized in that The process when the pRTI system updates data to the LVC-DE distributed synthesis environment further includes the following steps: S5b-1: The pRTI communication program receives the object instance data published by the pRTI system; S5b-2: Determine whether the object instance received from the pRTI system is the pRTI object instance ordered in the association mapping. If so, execute S5b-3; if not, end this operation; S5b-3: Parse the object instance data received from the pRTI system according to the basic data type and store it in the corresponding position of the mapping information list; S5b-4: Determine whether the main attribute has been updated according to the content of the mapping information list. If the main attribute is updated, execute S5a-5; if the main attribute is not updated, end this operation; S5b-5: The pRTI communication program calls the DataSend() function, fills the data parsed in S5b-3 into the data of the TENA object instance associated with the object instance published by the pRTI system, and sends the data to the gateway program; S5b-6: The gateway program parses the data sent by the pRTI communication program and publishes the data to the LVC-DE distributed synthesis environment.

Images