Data Processing Method, Computer Device and Storage Medium for Rocket Test Equivalent Device

Abstract

The present invention provides a data processing method, a computer device, and a storage medium for a rocket test equivalent. The method includes: serializing the fault entity object to generate a binary fault data stream; calling a fault sending interface to send the binary fault data stream, enabling the on-board equipment to deserialize the received binary fault data stream to generate a fault entity object, and performing fault injection according to the fault entity object. The present invention solves the problems in the data processing method of the existing rocket test equivalent, such as the lack of a fault injection mechanism and slow data processing efficiency. By constructing a fault entity object according to the fault type and sending the fault entity object to the on-board equipment, the injection and response of faults are realized, and the system operation efficiency is improved through the serialization and deserialization operations of the fault entity object.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a data processing method, computer equipment and storage medium for a rocket test equivalent. Background Art

[0002] The rocket test launch real-installation training system is used for teaching and training of multiple types of launch vehicles such as the Long March and Kuaizhou. It realizes semi-physical simulation training of onboard equipment, ground test, launch control, launch support and guarantee systems, and supports multi-functional teaching and training in the principles of mobile launch equipment, calculation of key elements, rocket assembly test, rocket launch control, and launch organization. The rocket test launch real-installation training system uses equivalent software to simulate the operations of related positions in the rocket test, launch and control process. The equivalent mainly includes control system equivalents, measurement system equivalents, power system equivalents, etc. Each type of system equivalent can be divided into on-rocket simulation equivalents, front-end simulation equivalents, and back-end simulation equivalents according to their purpose and usage scenarios. It can be seen that the simulation equivalent is the core module of the rocket test launch real-installation training system, providing key software technical support for the effective and smooth implementation of the rocket test, launch and control process. In the test, launch and control process of rocket simulation training, how to provide a stable and reliable data processing method to achieve real-time, accurate and efficient data flow between equivalent devices, and to achieve real-time, accurate and comprehensive analysis and judgment of the internal data of the equivalent devices has become a core research topic in the rocket test and launch actual training system.

[0003] The equivalent devices in traditional rocket test and launch training systems only process key data processes such as test and launch control instructions and telemetry data processing, and often ignore other processes, such as fault injection processes. This leads to deficiencies in the operability, liveliness and human-computer interaction of the rocket simulation training system. In addition, the data processing efficiency of the rocket test equivalent device is slow, and problems such as data accumulation and loss often occur, which cannot meet the real-time and accuracy processing requirements.

[0004] It can be seen that the data processing method of the rocket test equivalent in the prior art has the problems of lack of fault injection mechanism and slow data processing efficiency. Summary of the invention

[0005] In view of the deficiencies in the prior art, the data processing method, computer device and storage medium of the rocket test equivalent provided by the present invention solve the problems of lack of fault injection mechanism and slow data processing efficiency in the data processing method of the rocket test equivalent in the prior art. Fault injection and fault response are achieved by constructing a fault entity object according to the fault type and sending the fault entity object to the on-rocket device. In addition, the system operation efficiency is improved by serializing and deserializing the fault entity object.

[0006] In a first aspect, the present invention provides a data processing method for a rocket test equivalent, and the method includes: constructing a corresponding fault entity object according to a fault type; serializing the fault entity object to generate a binary fault data stream; calling a fault sending interface to send the binary fault data stream, so that the on-board equipment deserializes the received binary fault data stream to generate a fault entity object, and performs fault injection according to the fault entity object.

[0007] Optionally, when the fault entity object includes a parameter attribute, a data block status value attribute, and a data block real-time value attribute, serializing the fault entity object to generate a binary fault data stream includes: sequentially performing binary conversion on the parameter attribute, the data block status value attribute, and the data block real-time value attribute in the fault entity object to respectively obtain a parameter value array, a status value byte array, and a real-time value byte array; splicing and packing the parameter value array, the status value byte array, and the real-time value byte array according to a preset rule to obtain the binary fault data stream.

[0008] Optionally, when the fault entity object includes a parameter attribute, a data block status value attribute, and a data block real-time value attribute, deserializing the received binary fault data stream to generate a fault entity object includes: splitting the binary fault data stream into data segments according to a communication protocol to respectively obtain a parameter attribute data segment, a data block status data segment, and a data block real-time value data segment; deserializing the parameter attribute data segment, the data block status data segment, and the data block real-time value data segment to obtain the parameter attribute, the data block status value attribute, and the data block real-time value attribute.

[0009] Optionally, performing binary conversion on the data block real-time value attribute in the fault entity object to obtain a real-time value byte array includes: converting each real-time value into a corresponding binary data array according to the offset and field length of each real-time value in the data block real-time value attribute; splicing all the binary data arrays to obtain the real-time value byte array.

[0010] Optionally, performing binary conversion on the data block status value attribute in the fault entity object to obtain a status value byte array includes: constructing a target byte array according to the total number of status values in the data block real-time value attribute; performing binary conversion on each status value in the data block status value attribute to obtain the binary Bit value of each status value; storing the binary Bit value of each status value into the target byte array in sequence to obtain the status value byte array.

[0011] Optionally, deserializing the real-time value data segment of the data block to obtain the real-time value attribute of the data block, including: obtaining the offset and field length corresponding to each real-time value in the real-time value attribute of the data block; in the real-time value data segment of the data block, extracting the target data segment with the field length starting from the offset; respectively performing binary reverse conversion on all target data segments to obtain all real-time values in the real-time value attribute of the data block.

[0012] Optionally, deserializing the status data segment of the data block to obtain the status value attribute of the data block, including: according to the communication protocol, obtaining the sequence number of each real-time value in the real-time value attribute of the data block; storing the binary Bit values of each status value into the target byte array in sequence to obtain the status value byte array; performing binary reverse conversion on all the byte Bit values to obtain all status values in the status value attribute of the data block.

[0013] Optionally, performing fault injection according to the fault entity object, including: obtaining a list of fault parameter values according to the fault command name in the fault entity object; updating the real-time value of the on-board equipment parameter according to the list of fault parameter values.

[0014] In a second aspect, the present invention provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented: constructing a corresponding fault entity object according to the fault type; serializing the fault entity object to generate a binary fault data stream; calling a fault sending interface to send the binary fault data stream, so that the on-board equipment deserializes the received binary fault data stream to generate a fault entity object, and performs fault injection according to the fault entity object.

[0015] In a third aspect, the present invention provides a readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: constructing a corresponding fault entity object according to the fault type; serializing the fault entity object to generate a binary fault data stream; calling a fault sending interface to send the binary fault data stream, so that the on-board equipment deserializes the received binary fault data stream to generate a fault entity object, and performs fault injection according to the fault entity object.

[0016] Compared with the prior art, the beneficial effects of the present invention are:

[0017] The present invention constructs a fault entity object according to the fault type and sends the fault entity object to the on-board equipment, thereby realizing the injection of faults and the response to faults, and improving the authenticity and interactivity of the rocket test launch actual equipment training system. Further, the present invention improves the data processing efficiency and transmission efficiency by serializing and deserializing the fault entity object, enabling the communication parties to transmit through binary data streams, thereby realizing the fast and accurate processing and transmission of system data and improving the system operation efficiency. Description of the Drawings

[0018] Figure 1 The figure shows a schematic flow chart of a data processing method for a rocket test simulator provided by an embodiment of the present invention;

[0019] Figure 2 The figure shows a schematic diagram of serializing a fault entity object provided by an embodiment of the present invention;

[0020] Figure 3 The figure shows a schematic diagram of serializing the real-time value of a data block provided by an embodiment of the present invention;

[0021] Figure 4 The figure shows a schematic diagram of serializing the status value of a data block provided by an embodiment of the present invention;

[0022] Figure 5 The figure shows a schematic diagram of deserializing a fault entity object provided by an embodiment of the present invention;

[0023] Figure 6 The figure shows a schematic diagram of deserializing the real-time value of a data block provided by an embodiment of the present invention;

[0024] Figure 7 The figure shows a schematic diagram of deserializing the status value of a data block provided by an embodiment of the present invention;

[0025] Figure 8 The figure shows a schematic flow chart of fault injection and response provided by an embodiment of the present invention. Detailed Embodiments

[0026] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0027] Figure 1 The figure shows a schematic flow chart of a data processing method for a rocket test simulator provided by an embodiment of the present invention; AsFigure 1 As shown, the data processing method of the rocket test equator specifically includes the following steps:

[0028] Step S101: Construct a corresponding fault entity object according to the fault type.

[0029] It should be noted that to improve the authenticity of the rocket test launch actual equipment training system, the equator can be set with multiple fault modes to realize the real simulation of the hardware and software faults of the on-board, front-end and back-end equators. The test commander and instructor can inject various types of faults at any time through the fault injection software on the terminal computer. The fault types in this embodiment include, but are not limited to, GNSS signal anomaly, pressure sensor data anomaly, voltage and current anomaly of a certain device, resistance anomaly of the initiator loop, inertial measurement unit (IMU) data anomaly, image anomaly, power distribution failure, on-board equipment failure, network communication anomaly, inability to receive telemetry data, servo zero position anomaly, IMU to navigation anomaly, battery activation anomaly, and ignition failure.

[0030] In this embodiment, the fault entity object includes parameter attributes, data block status value attributes, and data block real-time value attributes. Among them, the parameter attributes include, but are not limited to, fault type, fault command name, source IP address, and frame name. The data block real-time value attributes include multiple real-time values, and the data block status value attributes include the status of each real-time value, and the status includes normal or abnormal.

[0031] Step S102: Serialize the fault entity object to generate a binary fault data stream.

[0032] In this embodiment, when the fault entity object includes parameter attributes, data block status value attributes, and data block real-time value attributes, serializing the fault entity object to generate a binary fault data stream includes: performing binary conversion on the parameter attributes, data block status value attributes, and data block real-time value attributes in the fault entity object in sequence to obtain a parameter value array, a status value byte array, and a real-time value byte array respectively; splicing and packing the parameter value array, the status value byte array, and the real-time value byte array according to a preset rule to obtain the binary fault data stream.

[0033] It should be noted that at the bottom layer of network data communication, the data transmitted by both communication parties is a binary data stream. To improve data processing efficiency, the equalizer software provides serialization and deserialization operations for the fault entity object NetTrans. Object serialization is to convert NetTrans into a binary data stream, and deserialization is to parse the binary data stream into the fault entity object NetTrans. In addition, to improve communication transmission efficiency, the status value and real-time value included in the fault entity object NetTrans need to be serialized separately. The processed status value byte array is assigned to the block_status_ attribute of NetTrans, and the processed real-time value byte array is assigned to the block_data_ attribute of NetTrans. In this embodiment, the NetTrans object serialization is implemented based on QBuffer and QDataStream, as Figure 2 shown. QBuffer is used as a data storage buffer to store the serialized binary data result. QDataStream first uses QBuffer as the data output storage area, and then performs binary conversion processing on each attribute in the NetTrans object in the form of a data stream, and sequentially pushes them to the QBuffer data buffer. The serialization processing order of NetTrans attributes is freely agreed upon. After the agreement is made, the deserialization is performed in this order. Finally, the content in the QBuffer data buffer is copied to the QByteArray array as the output.

[0034] In this embodiment, the binary conversion of the data block real-time value attribute in the fault entity object is performed to obtain a real-time value byte array, including: converting each real-time value into a corresponding binary data array according to the offset and field length of each real-time value in the data block real-time value attribute; concatenating all the binary data arrays to obtain a real-time value byte array.

[0035] It should be noted that block_status_ and block_data_ in the NetTrans object are the most core attributes. First, all the real-time values included in block_data_ and the status values included in block_status_ need to be serialized.

[0036] For the detailed real-time value serialization process, see Figure 3As shown, traverse the list of real-time values. For each real-time value Block in the list of real-time values, first convert the real-time value of each Block into a Byte binary data array based on the offset and length, then splice all the converted Byte binary arrays, and finally assign the spliced binary array to the block_data_ property in the NetTrans object, and assign the processed real-time value byte array to the block_data_ property in the NetTrans object; where the offset is the difference between the current real-time value sequence number and the first real-time value sequence number.

[0037] In this embodiment, perform binary conversion on the data block status value attribute in the fault entity object to obtain a status value byte array, including: constructing a target byte array according to the total number of status values in the data block real-time value attribute; performing binary conversion on each status value in the data block status value attribute to obtain the binary Bit value of each status value; storing the binary Bit value of each status value into the target byte array in sequence to obtain a status value byte array.

[0038] It should be noted that the status value serialization process refers to Figure 4 As shown, for status value serialization, first create a new byte array with the array length being the total number of real-time values divided by 8, plus one. Then traverse the list of status values, obtain the status value of each real-time value, convert it into 0 or 1, and then assign it to a certain Bit of a certain byte in the byte array in sequence, and assign the processed status value byte array to the block_status_ property in the NetTrans object.

[0039] Step S103, call the fault sending interface to send the binary fault data stream, so that the on-board device deserializes the received binary fault data stream to generate a fault entity object, and perform fault injection according to the fault entity object.

[0040] In this embodiment, when the fault entity object includes a parameter attribute, a data block status value attribute, and a data block real-time value attribute, deserializing the received binary fault data stream to generate a fault entity object includes: splitting the binary fault data stream into data segments according to the communication protocol to obtain a parameter attribute data segment, a data block status data segment, and a data block real-time value data segment; deserializing the parameter attribute data segment, the data block status data segment, and the data block real-time value data segment to obtain the parameter attribute, the data block status value attribute, and the data block real-time value attribute.

[0041] It should be mainly noted that the deserialization of the NetTrans object is also implemented based on QBuffer and QDataStream. For details, see Figure 5As shown in the figure. The QBuffer serves as a data storage buffer for storing the binary data received from the outside. The QDataStream uses the QBuffer as the data input storage area and processes the binary data in the QBuffer sequentially. First, the binary stream in the QBuffer is split into multiple data segments, and then each data segment is parsed into the attribute values corresponding to the NetTrans object. The process of deserializing the attributes of the NetTrans object is consistent with the established order during serialization.

[0042] Optionally, deserializing the real-time value data segment of the data block to obtain the real-time value attribute of the data block, including: obtaining the offset and field length corresponding to each real-time value in the real-time value attribute of the data block; in the real-time value data segment of the data block, extracting the target data segment with the field length starting from the offset; respectively performing binary reverse conversion on all target data segments to obtain all real-time values in the real-time value attribute of the data block.

[0043] It should be noted that the real-time value deserialization process is as Figure 6 shown. Traverse the real-time value list to obtain the offset S1 and length Len of each real-time value, then extract the byte segment B1 with a length of Len starting from the offset S1 in the block_data_ byte array, and then perform reverse conversion on B1 according to the Block type to obtain the real-time value Val. Finally, assign all real-time values Val to the real-time value attribute of the Block.

[0044] Optionally, deserializing the data block status data segment to obtain the data block status value attribute, including: according to the communication protocol, obtaining the sequence number of each real-time value in the real-time value attribute of the data block; storing the binary Bit values of each status value in order into the target byte array to obtain the status value byte array; performing binary reverse conversion on all the byte Bit values to obtain all status values in the data block status value attribute.

[0045] It should be noted that the status value deserialization process is as Figure 7 shown: Traverse the real-time value list to obtain the sequence number S1 of each real-time value in the real-time value list, then divide S1 by 8 to obtain the quotient S2 and the remainder S3. Read the S2nd byte B1 in the block_status_ array with S2 as the sequence number, then obtain the bit value with the sequence number S3 of the byte B1, and finally assign the Bit value to the data block status value attribute.

[0046] Compared with the prior art, the beneficial effects of the present invention are:

[0047] The present invention constructs a fault entity object according to the fault type and sends the fault entity object to the on-board equipment, thereby realizing fault injection and fault response, and enhancing the authenticity and interactivity of the rocket test launch actual equipment training system. Further, the present invention improves the data processing efficiency and transmission efficiency by serializing and deserializing the fault entity object, enabling both communication parties to transmit through binary data streams, thereby realizing fast and accurate processing and transmission of system data and enhancing the system operation efficiency.

[0048] In another embodiment of the present invention, fault injection based on the fault entity object includes: obtaining a list of fault parameter values according to the fault command name in the fault entity object; and updating the real-time value of the on-board equipment parameters according to the list of fault parameter values.

[0049] In this embodiment, to improve the authenticity of the rocket test launch actual equipment training system, the emulator can be set with multiple fault modes to realize the real simulation of hardware and software faults of on-board, front-end, and back-end emulators. The test commander and instructors can inject various types of faults at any time through the fault injection software on the terminal computer, such as abnormal GNSS signals, abnormal pressure sensor data, abnormal voltage and current of a certain device, abnormal resistance value of the initiator circuit, abnormal inertial measurement unit (IMU) data, abnormal images, power distribution failure, on-board equipment failure, network communication anomaly, inability to receive telemetry data, servo zero position anomaly, IMU to navigation anomaly, battery activation anomaly, ignition failure, etc. This process mainly includes fault command sending and response processing, as detailed in Figure 8 shown.

[0050] (1) The fault command sending process is as follows:

[0051] Step 1: Select and click the fault button to construct a NetTrans entity object corresponding to the fault;

[0052] Step 2: Add the NetTrans entity object to the ClientManager send cache queue;

[0053] Step 3: Traverse the ClientManager send cache queue, check if the buffer is empty, and wait in a loop;

[0054] Step 4: Take out the fault NetTrans object to be sent and serialize it into binary data;

[0055] Step 5: Package the fault binary data stream and call the TcpClient send interface to send the fault data;

[0056] Step 6: After sending, enter Step 3;

[0057] (2) The fault response processing process is as follows:

[0058] Step 1: The SocketWorker receives a binary data packet, and the TcpServer deserializes the binary data packet to generate a NetTrans fault entity object;

[0059] Step 2: Search the local fault information table based on the CmdName attribute of the NetTrans object. If not found, stop processing;

[0060] Step 3: Traverse the parameter value list corresponding to the fault;

[0061] Step 4: Extract the content of each fault parameter, including the parameter name and the real-time fault value;

[0062] Step 5: Refresh the real-time value of the device parameter and enter Step 3;

[0063] In another embodiment of the present invention, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented: constructing a corresponding fault entity object according to the fault type; serializing the fault entity object to generate a binary fault data stream; calling a fault sending interface to send the binary fault data stream, enabling the on-board device to deserialize the received binary fault data stream to generate a fault entity object, and performing fault injection according to the fault entity object.

[0064] In yet another embodiment of the present invention, a readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: constructing a corresponding fault entity object according to the fault type; serializing the fault entity object to generate a binary fault data stream; calling a fault sending interface to send the binary fault data stream, enabling the on-board device to deserialize the received binary fault data stream to generate a fault entity object, and performing fault injection according to the fault entity object.

[0065] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0066] It should be noted that in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

Claims

1. A data processing method for a rocket test equivalent device, characterized in that, the method includes: Constructing a corresponding fault entity object according to the fault type; Serializing the fault entity object to generate a binary fault data stream; Invoking a fault sending interface to send the binary fault data stream, so that the on-board device deserializes the received binary fault data stream to generate a fault entity object, and performs fault injection according to the fault entity object; When the fault entity object includes parameter attributes, data block status value attributes, and data block real-time value attributes, serializing the fault entity object to generate a binary fault data stream includes: Performing binary conversion on the parameter attributes, data block status value attributes, and data block real-time value attributes in the fault entity object in sequence to obtain a parameter value array, a status value byte array, and a real-time value byte array respectively; Splicing and packing the parameter value array, the status value byte array, and the real-time value byte array according to a preset rule to obtain the binary fault data stream; When the fault entity object includes parameter attributes, data block status value attributes, and data block real-time value attributes, deserializing the received binary fault data stream to generate a fault entity object includes: According to the communication protocol, splitting the binary fault data stream into data segments to obtain a parameter attribute data segment, a data block status data segment, and a data block real-time value data segment; Deserializing the parameter attribute data segment, the data block status data segment, and the data block real-time value data segment to obtain the parameter attributes, the data block status value attributes, and the data block real-time value attributes; Performing binary conversion on the data block status value attributes in the fault entity object to obtain a status value byte array, including: Constructing a target byte array according to the total number of status values in the data block real-time value attributes; Performing binary conversion on each status value in the data block status value attributes to obtain the binary Bit value of each status value; Storing the binary Bit values of each status value into the target byte array in sequence to obtain a status value byte array; Deserializing the data block status data segment to obtain the data block status value attributes, including: According to the communication protocol, obtaining the sequence number of each real-time value in the data block real-time value attributes; Storing the binary Bit values of each status value into the target byte array in sequence to obtain a status value byte array; Performing binary reverse conversion on all byte Bit values in the status value byte array to obtain all status values in the data block status value attributes.

2. The data processing method for a rocket test equivalent device according to claim 1, characterized in that, Performing binary conversion on the data block real-time value attributes in the fault entity object to obtain a real-time value byte array, including: Converting each real-time value into a corresponding binary data array according to the offset and field length of each real-time value in the data block real-time value attributes; Splicing all binary data arrays to obtain a real-time value byte array.

3. The data processing method for a rocket test equivalent device according to claim 1, characterized in that, Deserialize the real-time value data segment of the data block to obtain the real-time value attributes of the data block, including: Obtain the offset and field length corresponding to each real-time value in the real-time value attributes of the data block; In the real-time value data segment of the data block, extract the target data segment of the field length with the offset as the starting position; Perform binary reverse conversion on all target data segments respectively to obtain all real-time values in the real-time value attributes of the data block.

4. The data processing method of the rocket test equivalent device according to any one of claims 1-2, characterized in that Fault injection is performed according to the fault entity object, including: Obtain a list of fault parameter values according to the fault command name in the fault entity object; Update the real-time values of the parameters of the on-board equipment according to the list of fault parameter values.

5. A computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 are implemented.

6. A readable storage medium, on which a computer program is stored, characterized in that When the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 3 are implemented.

Images