Injection data comparison method and device
By parsing the configuration file of the spacecraft injected data and automatically comparing the spacecraft injected data with the inverse calculation file, the problems of inconsistent injected data formats and different sources of parameter values are solved, achieving efficient and reliable data comparison and improving the efficiency of spacecraft operation control.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-19
- Publication Date
- 2026-04-10
AI Technical Summary
The inconsistent data formats and varying sources of parameter values injected into spacecraft make manual verification time-consuming and labor-intensive, making it difficult to guarantee the accuracy of the injected data.
An injection data comparison method and apparatus are provided. By parsing the injection configuration file, the instruction type is determined and processed accordingly. The injected data is automatically compared with the instruction information in the reverse calculation file, and the data consistency is ensured by using preset comparison rules.
It improves the efficiency of data verification for spacecraft injection, ensures the reliability and accuracy of the injected data, reduces errors in manual comparison, and meets the automation requirements of spacecraft operation control.
Smart Images

Figure CN121835647A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of aerospace telemetry and control technology, specifically to a method and apparatus for injecting data comparison. Background Technology
[0002] In the daily operation and control of spacecraft, the ground operation control center needs to inject a large amount of data into the spacecraft every day to complete various tasks. Therefore, ensuring the correctness of all injected data is a key and challenging issue that urgently needs to be addressed. However, the formats of this injected data are inconsistent, numerous and disorganized, and the parameter values in the injected data come from different sources.
[0003] The daily operation and control of spacecraft mainly includes two core components: attitude control and orbit control, which are explained in detail below: Attitude control: By adjusting the satellite's three attitude parameters—roll, pitch, and yaw—we ensure that the satellite's coordinate system remains consistent with a reference coordinate system (such as a geocentric inertial coordinate system or an orbital coordinate system). For example, roll corresponds to a rollover maneuver around the flight direction, pitch corresponds to a pitching or tilting maneuver, and yaw corresponds to a turning maneuver around a vertical line.
[0004] Track control: This involves adjusting the spacecraft's orbit, including orbit adjustments and system checks during the launch phase, to ensure the spacecraft operates stably in the target orbit.
[0005] In addition, daily control also relies on the coordinated operation of components such as inertial devices, jet actuators, and optical sensors (such as sun sensors and earth sensors) to achieve precise attitude and orbit control.
[0006] Currently, the correctness of injected data is ensured through manual verification. The process involves locating parameter values in the injected data based on the injection configuration file. If the value is not a parameter value but rather a source of that value, the parameter value must be retrieved from the source. Finally, the retrieved parameter value is compared one-to-one with the parameter values in the reverse calculation file. Some parameter values require special conversions; the source of the parameter values may be in TXT, binary, or XML text formats, and the element interfaces of the text content are diverse, making manual verification extremely time-consuming and labor-intensive. Summary of the Invention
[0007] To address the problems in the prior art, embodiments of the present invention provide an injection data comparison method and apparatus, which can at least partially solve the problems existing in the prior art.
[0008] On one hand, the present invention proposes an injection data comparison method, comprising: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0009] The instruction types include a first instruction type and a second instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to the instruction processing method includes: If the instruction type is determined to be the first instruction type, then the first instruction type is converted to the second instruction type, and the corresponding plan file is read according to the instruction parameter value of the first instruction type to obtain the final instruction parameter value of the first instruction type.
[0010] The step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the second instruction type, then the instruction parameter value in the injected configuration file is determined as the final instruction parameter value of the second instruction type.
[0011] The instruction type further includes a third instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the third instruction type, the first instruction information corresponding to the third instruction type is parsed, and the step of determining whether the instruction type is the first instruction type or the second instruction type is executed according to the parsing result.
[0012] The instruction type further includes a fourth instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the fourth instruction type, then the corresponding instruction plan source code file is read to obtain the final instruction parameter value of the fourth instruction type.
[0013] The step of comparing the processed first instruction information with the second instruction information in the injected reverse calculation file to obtain the injected data comparison result includes: If it is determined that the first comparison result between the first instruction information and the second instruction information is inconsistent, then the first instruction information and the second instruction information are compared using a preset reverse calculation comparison rule. The preset inverse calculation comparison rules include the mapping relationship between rule names and rule values; If the second comparison result is determined to be consistent, then the injected data comparison result is determined to be the first injected data comparison result that is consistent with the comparison result.
[0014] On one hand, the present invention proposes an injected data comparison device, comprising: The parsing unit is used to parse the injection configuration file to obtain the first instruction information; The determining unit is configured to determine, based on the first instruction information, the instruction processing method corresponding to each instruction type; The comparison unit is used to process the first instruction information corresponding to each instruction type according to the instruction processing method, and compare the processed first instruction information with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0015] In another aspect, embodiments of the present invention provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the following method: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0016] This invention provides a computer-readable storage medium, comprising: The computer-readable storage medium stores a computer program that, when executed by a processor, implements the following method: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0017] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the following method: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0018] The injection data comparison method and apparatus provided in this invention parses the injection configuration file to obtain first instruction information; determines the instruction processing method corresponding to each instruction type based on the first instruction information; processes the first instruction information corresponding to each instruction type according to each instruction processing method; compares the processed first instruction information with the second instruction information in the injection back-calculation file to obtain the injection data comparison result. This method can improve the efficiency of spacecraft injection data comparison and ensure the reliability and correctness of the injection data. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings: Figure 1 This is a flowchart illustrating an injection data comparison method provided in an embodiment of the present invention.
[0020] Figure 2 This is a schematic diagram of the structure of the injection data comparison method provided in another embodiment of the present invention.
[0021] Figure 3 This is a schematic diagram of the structure of an injection data comparison device provided in an embodiment of the present invention.
[0022] Figure 4 This is a schematic diagram of the physical structure of a computer device provided in an embodiment of the present invention. Detailed Implementation
[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments and descriptions of the present invention are used to explain the present invention, but are not intended to limit the present invention. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.
[0024] Explanation of relevant terms: Injected data: The hexadecimal data source code generated by the injection generation software of the ground control system based on the spacecraft injection frame format file mainly contains instruction information. The ground control system is the software system in the ground operation control center.
[0025] Injection configuration file: A text-based descriptive file that describes the various configuration information required for generating injection data. It mainly contains the instruction codes and parameter information that need to be manually entered into the injection data, serving as the medium for human-computer interaction.
[0026] Injection data file: An XML-formatted descriptive file generated by injection generation software based on the injection configuration file and injection frame format information. It mainly contains injection data blocks and injection data names.
[0027] Injection reverse engineering file: An XML-formatted descriptive file used by reverse engineering software to reverse-engineer the injected data file. Its main function is to parse the instruction information in the injected data source code into human-readable descriptive text.
[0028] Planning document: An XML-formatted descriptive file that pre-prepared for spacecraft operations, including injection command execution plans and telemetry and control (TT&C) arc tracking plans. It primarily contains the command parameter values required for the injection configuration file.
[0029] Figure 1 This is a flowchart illustrating an embodiment of the injected data comparison method provided by the present invention, as shown below. Figure 1 As shown, the injected data comparison method provided in this embodiment of the invention is applied to a network topology containing computing nodes; each computing node contains a preset number of graphics processors; the injected data comparison method includes: Step S1: Parse the injection configuration file to obtain the first instruction information.
[0030] Step S2: Determine the instruction processing method corresponding to each instruction type based on the first instruction information.
[0031] Step S3: Process the first instruction information corresponding to each instruction type according to the instruction processing method, and compare the processed first instruction information with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0032] In step S1 above, the device parses the injection configuration file to obtain the first instruction information. The device can be a computer device that executes this method. The acquisition, storage, use, and processing of data in the technical solution of this application all comply with relevant regulations. The first instruction information may specifically include instruction code and parameter information.
[0033] In step S2 above, the device determines the instruction processing method corresponding to each instruction type based on the first instruction information. The instruction types include the first instruction type, i.e., special instructions, as explained below: For injection data generated through special instructions, the instruction information mainly comes from the plan file. The original filled values of instructions and parameters in this type of injection data cannot be directly obtained from the injection configuration file. The injection configuration file can only obtain the corresponding special instruction information, and the special instruction parameter values are generally the plan file name, time period, or other filtering conditions. It is necessary to perform corresponding instruction mapping to convert them into ordinary instructions, as shown in Table 1, and the final instruction parameter values need to be obtained by reading and parsing the plan file.
[0034] Table 1
[0035] The instruction types include the second instruction type, namely ordinary instructions, as shown in Table 2: Table 2
[0036] For injection data generated directly through ordinary commands, most of the command parameters (such as the first row of Table 2) can be directly obtained from the injection configuration file without any other special processing.
[0037] Some command parameters (such as the second row of Table 2) require special handling: the source of the command parameter value F is identified by the plan file such as the injection command execution plan or the measurement and control arc tracking plan. In this case, the command parameter value CmdPlan.xml is the plan file name. This file needs to be read and parsed to obtain the parameter value through the command parameter value path.
[0038] Instruction types include a third instruction type, namely nested instructions, as described below: For injected data generated through nested instructions, i.e., injected data where the parameter values are other instruction information (as shown in the third row of Table 2), the instruction parameter values cannot be directly obtained from the injection configuration file. Further parsing of the other instruction information is required to obtain them.
[0039] The instruction types include a fourth instruction type, namely instructions provided by external systems, as described below: Some key injection data is generated directly from binary instruction source code files provided by other external systems. In this case, the instruction parameter values originate from B, and the parameter value is the binary filename of the CmdData.bin instruction source code. The instruction parameter values must be obtained by reading the binary file, as shown in the fourth row of Table 2. The reverse engineering software does not perform reverse engineering on this type of instruction source code, therefore there is no comparison object. For this type of injection data, it can be determined whether the injection data source code in the reverse engineering file contains this instruction source code; if it does, the reverse engineering comparison will be consistent.
[0040] In step S3 above, the device processes the first instruction information corresponding to each instruction type according to each instruction processing method, and compares the processed first instruction information with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result. Instruction types include a first instruction type and a second instruction type; correspondingly, processing the first instruction information corresponding to each instruction type according to each instruction processing method includes: If the instruction type is determined to be the first instruction type, then the first instruction type is converted to the second instruction type, and the corresponding plan file is read according to the instruction parameter value of the first instruction type to obtain the final instruction parameter value of the first instruction type.
[0041] The step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the second instruction type, then the instruction parameter value in the injected configuration file is determined as the final instruction parameter value of the second instruction type.
[0042] The instruction type also includes a third instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the third instruction type, the first instruction information corresponding to the third instruction type is parsed, and the step of determining whether the instruction type is the first instruction type or the second instruction type is executed according to the parsing result.
[0043] The instruction type also includes a fourth instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the fourth instruction type, then the corresponding instruction plan source code file is read to obtain the final instruction parameter value of the fourth instruction type.
[0044] like Figure 2 As shown, the explanation is as follows: Step 1: Parse the injection configuration file to obtain instruction information.
[0045] Step 2: Based on the instruction mapping relationship in Table 1, determine the instruction code and whether it is a special instruction. If it is a special instruction, convert it into the corresponding ordinary instruction, and read the corresponding plan file to obtain the final instruction parameter value based on the special instruction parameter value. Finally, insert the converted instruction information into the injection configuration instruction information list and jump to Step 4. If it is not a special instruction, iterate through all instruction parameters.
[0046] Step 3: Select the value retrieval method for the parameter based on its source. If it is S, parse out the nested instruction and skip to Step 2; if it is V, directly use the parameter value from the injection configuration file; if it is B, read the corresponding instruction plan source code file to obtain the final instruction parameter value. Finally, insert the processed instruction information into the injection configuration instruction information list.
[0047] Step 4: Parse the inverse calculation file to obtain the inverse calculation instruction information, and insert it into the inverse calculation result instruction information list.
[0048] Step 5: Traverse the list of injection configuration command information and the list of reverse calculation result command information, and compare the command code, command parameter type and command parameter value one by one to see if they are consistent. If they are not all consistent, further comparison is performed according to the comparison rules, and finally the comparison result is given.
[0049] It should be noted that if the instruction code, instruction parameter type, and instruction parameter value are all compared one by one and the comparison results are all consistent, then the injection data comparison result can be directly determined as the first injection data comparison result with consistent comparison results.
[0050] If the comparison results according to the comparison rules are consistent, then the comparison result of the injected data can also be determined as the first comparison result of the injected data that is consistent with the comparison result.
[0051] If the comparison results according to the comparison rules are not consistent, then the comparison result of the injected data can be determined as the second comparison result of the injected data that is inconsistent with the comparison result.
[0052] Furthermore, it can also display discrepancies in the comparison results for personnel to analyze and review.
[0053] If there are inconsistencies, the inconsistencies should be clearly stated.
[0054] The preset inverse calculation comparison rules, namely the above comparison rules, are further explained as follows: Due to inherent defects in the reverse calculation software and the limitations of computer systems in storing floating-point data, the calculated instruction parameter values cannot match the original instruction parameter values. Therefore, comparison rules, as shown in Table 3, are configured to perform approximate matching, fuzzy matching, or equivalent matching of the instruction parameter values. This allows for automatic reverse calculation and comparison of all injected data.
[0055] Table 3
[0056] For example, for rule ID1, if the difference between two values is between 1 and 1000, they can be considered to be an approximate match.
[0057] The approximate matching is explained as follows: Approximate matching allows for fuzzy searches and is suitable for range or fault-tolerant scenarios, but requires data sorting.
[0058] Approximate matching uses algorithms to identify similar values or ranges, such as finding intervals or fuzzy keywords. For example, if the parameter is set to TRUE, the system will first locate the maximum value less than or equal to the target value and then return the corresponding result. Therefore, the data column must be sorted in ascending order.
[0059] Typical use cases for approximate matching include: Numerical range query: For example, calculate the tiered tax based on the tax rate table and find the actual tax rate bracket payable.
[0060] Error-tolerant search: Handles spelling errors (e.g., “New Yrok” matches “New York”) or synonym replacements (e.g., “mobile phone” matches “telephone”).
[0061] Grade matching: Students' grades are graded in segments (90-100 is grade A, 80-89 is grade B).
[0062] For rule ID2, if the difference between two values is less than 0.5, they can be considered to be a fuzzy match.
[0063] The following explains fuzzy matching: Regular expression fuzzy matching rules: Greedy matching: using Symbols such as +, ?, {m,} and {m,n} match as much content as possible by default.
[0064] Non-greedy matching: Add a ? after the greedy matching symbol, such as Use ?, +, etc., to achieve minimum matching.
[0065] Special sequences: formed by escaping characters followed by backticks, such as \d matching digits and \s matching whitespace characters.
[0066] Position markers: such as ^ to match the beginning of a string, Match the end.
[0067] SQL fuzzy matching rules: LIKE operator: "%": Matches zero or more arbitrary characters (e.g., A% matches strings that start with A).
[0068] "_": Matches a single arbitrary character (e.g., A___ matches a string that starts with A and has a length of 4).
[0069] NOT LIKE: Exclude records that match the pattern (e.g., NOT LIKE 'A%' excludes strings that start with A).
[0070] Regular expression extensions: Some databases support REGEXP or RLIKE, providing more complex pattern matching.
[0071] Differences in application scenarios: Exact match: The field exactly matches the search term (e.g., = or EXACT match).
[0072] Fuzzy matching: Supports partial matching (such as LIKE or regular expressions), and can break down search terms into unit concepts.
[0073] For rule ID3, for example, if X is a string and Y is a number, it can be considered an equivalent match.
[0074] Furthermore, the instruction type includes a first instruction type and a second instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method includes: If the instruction type is determined to be the first instruction type, then the first instruction type is converted to the second instruction type, and the corresponding plan file is read according to the instruction parameter values of the first instruction type to obtain the final instruction parameter values of the first instruction type. This can be referred to the above embodiments for explanation, and will not be repeated here.
[0075] Furthermore, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method also includes: If the instruction type is determined to be the second instruction type, then the instruction parameter value in the injected configuration file is determined as the final instruction parameter value of the second instruction type. This can be referred to the above embodiments for explanation, and will not be repeated here.
[0076] Furthermore, the instruction type also includes a third instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the third instruction type, then the first instruction information corresponding to the third instruction type is parsed, and the step of determining whether the instruction type is the first instruction type or the second instruction type is executed based on the parsing result. This can be referred to the above embodiments for explanation, and will not be repeated here.
[0077] Furthermore, the instruction type also includes a fourth instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the fourth instruction type, then the corresponding instruction plan source code file is read to obtain the final instruction parameter values for the fourth instruction type. This can be referred to the above embodiments for further explanation, and will not be repeated here.
[0078] Further, the step of comparing the processed first instruction information with the second instruction information in the injected reverse calculation file to obtain the injected data comparison result includes: If it is determined that the first comparison result between the first instruction information and the second instruction information is inconsistent, then the first instruction information and the second instruction information are compared using a preset reverse calculation comparison rule; this can be referred to the above embodiment for explanation, and will not be repeated here.
[0079] The preset inverse calculation comparison rules include the mapping relationship between rule names and rule values; this can be referred to the above embodiments for explanation, and will not be repeated here.
[0080] If the second comparison result is determined to be consistent, then the injected data comparison result is determined to be the first injected data comparison result that is consistent with the previous comparison result. This can be referred to the above embodiments for further explanation, and will not be repeated here.
[0081] The injected data comparison method provided in this invention classifies spacecraft injected data into four categories: ordinary commands, special commands, and nested commands. Corresponding processing methods are designed for each category, and an automatic reverse calculation and comparison device for the injected data is implemented. This device has been applied to some actual spacecraft operation and control work. Practice shows that this device can meet the automatic reverse calculation and comparison requirements for almost all types of injected data, can replace manual labor in completing large-scale input-output comparison work of injected data, reduces a significant amount of manpower and time, decreases the probability of manual comparison errors, and greatly improves the efficiency of spacecraft operation and control.
[0082] The injection data comparison method provided in this embodiment of the invention parses the injection configuration file to obtain first instruction information; determines the instruction processing method corresponding to each instruction type based on the first instruction information; processes the first instruction information corresponding to each instruction type according to each instruction processing method; compares the processed first instruction information with the second instruction information in the injection back-calculation file to obtain the injection data comparison result. This method can improve the efficiency of spacecraft injection data comparison and ensure the reliability and correctness of the injection data.
[0083] Figure 3 This is a schematic diagram of the structure of an injection data comparison device provided in an embodiment of the present invention, as shown below. Figure 3 As shown, the injected data comparison device provided in this embodiment of the invention includes a parsing unit 301, a determining unit 302, and a comparison unit 303, wherein: The parsing unit 301 is used to parse the injection configuration file to obtain the first instruction information; the determining unit 302 is used to determine the instruction processing method corresponding to each instruction type according to the first instruction information; the comparison unit 303 is used to process the first instruction information corresponding to each instruction type according to each instruction processing method, and compare the processed first instruction information with the second instruction information in the injection reverse calculation file to obtain the injection data comparison result.
[0084] Specifically, the parsing unit 301 in the device is used to parse the injection configuration file to obtain the first instruction information; the determining unit 302 is used to determine the instruction processing method corresponding to each instruction type according to the first instruction information; the comparison unit 303 is used to process the first instruction information corresponding to each instruction type according to each instruction processing method, and compare the processed first instruction information with the second instruction information in the injection reverse calculation file to obtain the injection data comparison result.
[0085] The injection data comparison device provided in this embodiment of the invention parses the injection configuration file to obtain first instruction information; determines the instruction processing method corresponding to each instruction type according to the first instruction information; processes the first instruction information corresponding to each instruction type according to each instruction processing method; compares the processed first instruction information with the second instruction information in the injection back calculation file to obtain the injection data comparison result. This can improve the efficiency of spacecraft injection data comparison and ensure the reliability and correctness of the injection data.
[0086] In the above optional embodiments, the instruction type includes a first instruction type and a second instruction type; correspondingly, the comparison unit 303 is specifically used for: If the instruction type is determined to be the first instruction type, then the first instruction type is converted to the second instruction type, and the corresponding plan file is read according to the instruction parameter value of the first instruction type to obtain the final instruction parameter value of the first instruction type.
[0087] In the above optional embodiments, the comparison unit 303 is further specifically used for: If the instruction type is determined to be the second instruction type, then the instruction parameter value in the injected configuration file is determined as the final instruction parameter value of the second instruction type.
[0088] In the above optional embodiments, the instruction type further includes a third instruction type; correspondingly, the comparison unit 303 is further specifically used for: If the instruction type is determined to be the third instruction type, the first instruction information corresponding to the third instruction type is parsed, and the step of determining whether the instruction type is the first instruction type or the second instruction type is executed according to the parsing result.
[0089] In the above optional embodiments, the instruction type further includes a fourth instruction type; correspondingly, the comparison unit 303 is further specifically used for: If the instruction type is determined to be the fourth instruction type, then the corresponding instruction plan source code file is read to obtain the final instruction parameter value of the fourth instruction type.
[0090] In the above optional embodiments, the comparison unit 303 is specifically used for: If it is determined that the first comparison result between the first instruction information and the second instruction information is inconsistent, then the first instruction information and the second instruction information are compared using a preset reverse calculation comparison rule. The preset inverse calculation comparison rules include the mapping relationship between rule names and rule values; If the second comparison result is determined to be consistent, then the injected data comparison result is determined to be the first injected data comparison result that is consistent with the comparison result.
[0091] The embodiments of the present invention provide an injection data comparison device that can be used to execute the processing flow of the above method embodiments. Its functions will not be repeated here, but can be referred to the detailed description of the above method embodiments.
[0092] Figure 4 This is a schematic diagram of the physical structure of a computer device provided in an embodiment of the present invention, such as... Figure 4 As shown, the computer device includes: a memory 401, a processor 402, and a computer program stored in the memory 401 and executable on the processor 402. When the processor 402 executes the computer program, it implements the following method: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0093] This embodiment discloses a computer program product, which includes a computer program that, when executed by a processor, implements the following method: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0094] This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the following method: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
[0095] Compared with existing technologies, the injection data comparison method provided in this invention involves parsing the injection configuration file to obtain first instruction information; determining the instruction processing method corresponding to each instruction type based on the first instruction information; processing the first instruction information corresponding to each instruction type according to the instruction processing method; comparing the processed first instruction information with the second instruction information in the injection back-calculation file to obtain the injection data comparison result. This method can improve the efficiency of spacecraft injection data comparison and ensure the reliability and correctness of the injection data.
[0096] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0097] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1A device that provides the functions specified in one or more boxes.
[0098] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0099] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0100] In the description of this specification, the references to terms such as "an embodiment," "a specific embodiment," "some embodiments," "for example," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0101] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for injecting data comparison, characterized in that, include: Parse the injection configuration file to obtain the first instruction information; Determine the instruction processing method corresponding to each instruction type based on the first instruction information; The first instruction information corresponding to each instruction type is processed according to the instruction processing method. The processed first instruction information is then compared with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
2. The injected data comparison method according to claim 1, characterized in that, The instruction types include a first instruction type and a second instruction type; correspondingly, the processing of the first instruction information corresponding to each instruction type according to the instruction processing method includes: If the instruction type is determined to be the first instruction type, then the first instruction type is converted to the second instruction type, and the corresponding plan file is read according to the instruction parameter value of the first instruction type to obtain the final instruction parameter value of the first instruction type.
3. The injected data comparison method according to claim 2, characterized in that, The step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the second instruction type, then the instruction parameter value in the injected configuration file is determined as the final instruction parameter value of the second instruction type.
4. The injected data comparison method according to claim 3, characterized in that, The instruction type also includes a third instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the third instruction type, the first instruction information corresponding to the third instruction type is parsed, and the step of determining whether the instruction type is the first instruction type or the second instruction type is executed according to the parsing result.
5. The injected data comparison method according to claim 4, characterized in that, The instruction type also includes a fourth instruction type; correspondingly, the step of processing the first instruction information corresponding to each instruction type according to each instruction processing method further includes: If the instruction type is determined to be the fourth instruction type, then the corresponding instruction plan source code file is read to obtain the final instruction parameter value of the fourth instruction type.
6. The method for comparing injected data according to any one of claims 1 to 5, characterized in that, The step of comparing the processed first instruction information with the second instruction information in the injected reverse calculation file to obtain the injected data comparison result includes: If it is determined that the first comparison result between the first instruction information and the second instruction information is inconsistent, then the first instruction information and the second instruction information are compared using a preset reverse calculation comparison rule. The preset inverse calculation comparison rules include the mapping relationship between rule names and rule values; If the second comparison result is determined to be consistent, then the injected data comparison result is determined to be the first injected data comparison result that is consistent with the comparison result.
7. An injected data comparison device, characterized in that, include: The parsing unit is used to parse the injection configuration file to obtain the first instruction information; The determining unit is configured to determine, based on the first instruction information, the instruction processing method corresponding to each instruction type; The comparison unit is used to process the first instruction information corresponding to each instruction type according to the instruction processing method, and compare the processed first instruction information with the second instruction information injected into the reverse calculation file to obtain the injection data comparison result.
8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.
10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.