A spacecraft injection data parsing and verifying method and device

Abstract

The application provides a spacecraft injection data analysis and verification method and device, which can be used in the technical field of spacecraft control. The method comprises the following steps: obtaining data source code of injection data; the injection data is generated according to preset input parameters; using the configuration information data dictionary of the injection data constructed in advance to analyze the data source code to obtain an analysis result; and verifying the injection data according to the preset input parameters and the analysis result. The spacecraft injection data analysis and verification method and device provided by the application effectively shield the differences of different spacecraft injection formats and realize the standardized analysis and verification of remote control injection data.

Description

Technical Field

[0001] This application relates to the field of spacecraft control technology, and in particular to a method and apparatus for analyzing and verifying injected data in a spacecraft. Background Technology

[0002] Operations such as switching control, state transitions, attitude and orbit control, time synchronization, and maintenance of onboard software and flight procedures for various subsystems of the spacecraft all require the injection of remote control commands through the uplink of the ground telemetry and control system. Because remote control commands can directly change the operational state of the spacecraft, their reliability and safety requirements are extremely high.

[0003] Spacecraft commands primarily consist of direct commands, indirect commands, and injected data. Direct and indirect commands are static source code; their names clearly reflect their function, and their correctness can be ensured through a single verification. Therefore, these commands are typically generated, verified, and approved before spacecraft launch. Injected data, however, is more complex and flexible. It usually contains one or more injection parameters, which ground flight control personnel fill in according to mission requirements to generate the injected data. Because the injected data source code is dynamic, the ground-based injection generation software must undergo review and approval by multiple personnel before being injected onto the spacecraft to ensure its correctness. However, the injected data source code actually used for execution is a binary file, which is difficult to verify manually and has poor readability.

[0004] The remote control data formats for different spacecraft models are not standardized, especially for spacecraft manufactured by different research and development departments, whose remote control interfaces differ significantly. Currently, the traditional PCM remote control system is still used by most spacecraft in orbit. However, an increasing number of newly developed spacecraft are adopting the subcontracted remote control system proposed by the Advisory Committee on Space Data Systems (CCSDS). Ground flight control centers need to handle uplink control tasks for different spacecraft models. For flight control tasks with different remote control systems and injection formats, corresponding injection data parsing and verification software must be developed, which results in low system versatility. This problem urgently needs to be solved. Summary of the Invention

[0005] To address the problems in the prior art, this application provides a method and apparatus for analyzing and verifying injected data from spacecraft, which can at least partially solve the problems existing in the prior art.

[0006] Firstly, this application provides a method for analyzing and verifying spacecraft injected data, including:

[0007] Obtain the data source code for the injected data; the injected data is generated based on preset input parameters.

[0008] The data source code is parsed using a pre-built configuration information data dictionary of the injected data to obtain the parsing result;

[0009] The injected data is verified based on the preset input parameters and the parsing results.

[0010] Furthermore, the step of pre-constructing the configuration information data dictionary includes:

[0011] Obtain the attribute information and pre-constructed frame structure information of the injected data;

[0012] The configuration information data dictionary is constructed based on the attribute information and the frame structure information.

[0013] Furthermore, the step of pre-constructing the frame structure information includes:

[0014] Obtain structural index information and structural details; the structural index information includes: injected structural identifier, substructure identifier, and substructure name; the structural details include multiple fields; the attributes of the fields include field type; the field type includes data substructure and instruction encoding;

[0015] The frame structure information is generated based on the structure index information and the structure details.

[0016] Furthermore, the step of parsing the data source code using a pre-built configuration information data dictionary of the injected data includes:

[0017] The data source code and the frame structure information are used for search and matching;

[0018] If the match is successful, a parsing result is generated based on the information obtained from the match; if the match fails, a verification result indicating verification failure is returned.

[0019] Further, the step of verifying the injected data based on the preset input parameters and the parsing result includes:

[0020] The parsing result is validated to obtain the first validation result;

[0021] Verify whether the preset input parameters and the input parameters in the parsing result are consistent to obtain a second verification result;

[0022] A parsing and verification file is generated based on the parsing results, the first verification result, and the second verification result.

[0023] Secondly, this application provides a spacecraft injected data analysis and verification device, comprising:

[0024] A data acquisition unit is used to acquire the data source code of the injected data; the injected data is generated according to preset input parameters.

[0025] The data parsing unit is used to parse the data source code using a pre-built configuration information data dictionary of the injected data to obtain the parsing result;

[0026] The data verification unit is used to verify the injected data based on the preset input parameters and the parsing results.

[0027] Furthermore, it also includes:

[0028] The first information acquisition unit is used to acquire the attribute information and pre-constructed frame structure information of the injected data;

[0029] The data dictionary construction unit is used to construct the configuration information data dictionary based on the attribute information and the frame structure information.

[0030] Furthermore, it also includes:

[0031] The second information acquisition unit is used to acquire structure index information and structure details; the structure index information includes: injection structure identifier, substructure identification code and substructure name; the structure details include multiple fields; the attributes of the fields include field type; the field type includes data substructure and instruction code;

[0032] A frame structure information construction unit is used to generate the frame structure information based on the structure index information and the structure details.

[0033] Furthermore, the data parsing unit includes:

[0034] The data matching module is used to perform search matching using the data source code and the frame structure information;

[0035] The data parsing module is used to generate a parsing result based on the information obtained from the matching if the match is successful; otherwise, it returns a verification result indicating that the verification failed.

[0036] Furthermore, the data verification unit includes:

[0037] The first data verification module is used to verify the legality of the parsing result and obtain the first verification result;

[0038] The second data verification module is used to verify whether the preset input parameters and the input parameters in the parsing result are consistent, and to obtain a second verification result.

[0039] The parsing verification file generation module is used to generate a parsing verification file based on the parsing result, the first verification result, and the second verification result.

[0040] Thirdly, this application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any of the above embodiments.

[0041] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods described in any of the above embodiments.

[0042] Fifthly, this application provides a computer program product, which includes a computer program that, when executed by a processor, implements the method described in any of the above embodiments.

[0043] The spacecraft injection data parsing and verification method and apparatus provided in this application acquire the data source code of the injection data, which is generated according to preset input parameters. The data source code is parsed using a pre-constructed configuration information data dictionary of the injection data to obtain a parsing result. The injection data is verified based on the preset input parameters and the parsing result. This effectively masks the differences in injection formats between different spacecraft and achieves standardized parsing and verification of remote-controlled injection data. Specifically, by acquiring the data source code of the injection data, offline data parsing and verification, as well as online real-time parsing and verification of uplink injection data, are supported. By using a pre-constructed configuration information data dictionary of the injection data to parse the data source code, the differences in injection formats between different spacecraft are effectively masked, adapting to dual-remote control systems and multi-model injection format parsing and verification. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application 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 this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application;

[0046] Figure 2 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application;

[0047] Figure 3 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application;

[0048] Figure 4 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application;

[0049] Figure 5 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application;

[0050] Figure 6 This is a schematic diagram of the structure of a spacecraft injection data parsing and verification device provided in an embodiment of this application;

[0051] Figure 7 This is a schematic diagram of the structure of a spacecraft injection data parsing and verification device provided in an embodiment of this application;

[0052] Figure 8 This is a schematic diagram of the structure of a spacecraft injection data parsing and verification device provided in an embodiment of this application;

[0053] Figure 9 This is a schematic diagram of the structure of a spacecraft injection data parsing and verification device provided in an embodiment of this application;

[0054] Figure 10 This is a schematic diagram of the structure of a spacecraft injection data parsing and verification device provided in an embodiment of this application;

[0055] Figure 11 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of this application;

[0056] Figure 12 This is a schematic diagram of an injection frame structure index tree provided in an embodiment of this application;

[0057] Figure 13 This is a flowchart illustrating the parsing and injection of source code provided in one embodiment of this application. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments and their descriptions are used to explain this application, but are not intended to limit this application. 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.

[0059] The following describes the specific implementation process of the spacecraft injection data parsing and verification method provided in this application embodiment, taking the server as the execution subject as an example.

[0060] Figure 1 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application, as shown below. Figure 1As shown, the spacecraft injection data parsing and verification method provided in this application includes:

[0061] S101: Obtain the data source code for the injected data; the injected data is generated based on preset input parameters;

[0062] S102: The data source code is parsed using a pre-built configuration information data dictionary of the injected data to obtain the parsing result;

[0063] S103: Verify the injected data based on the preset input parameters and the parsing results.

[0064] from Figure 1 As can be seen from the flowchart, the spacecraft injection data parsing and verification method provided in this application obtains the data source code of the injection data; the injection data is generated according to preset input parameters; the data source code is parsed using a pre-built configuration information data dictionary of the injection data to obtain the parsing result; the injection data is verified according to the preset input parameters and the parsing result, thereby effectively shielding the differences in injection formats of different spacecraft and realizing standardized parsing and verification of remote control injection data.

[0065] Each step is explained in detail below.

[0066] S101: Obtain the data source code for the injected data; the injected data is generated based on preset input parameters;

[0067] Specifically, when ground flight control personnel generate or inject data, or before injecting input data provided by external systems, the server obtains the data source code of the injected data for parsing and verification. Specifically, before injecting input data provided by external systems, the server begins parsing and verification by receiving manually sent commands.

[0068] S102: The data source code is parsed using a pre-built configuration information data dictionary of the injected data to obtain the parsing result;

[0069] Specifically, the server matches the configuration information data dictionary of the injected data with the data source code of the injected data to parse the data source code of the injected data. The configuration information data dictionary of the injected data is pre-built and used to describe the configuration information of the injected data.

[0070] Figure 2 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application, as shown below. Figure 2 As shown, the steps for pre-constructing the configuration information data dictionary include:

[0071] S201: Obtain the attribute information and pre-constructed frame structure information of the injected data;

[0072] Specifically, the server obtains the attribute information of the injected data input by the operator through the interactive device and the pre-built frame structure information to construct a configuration information data dictionary for the injected data. The attribute information of the injected data includes the injected data symbol, injected data name, instruction code, and identifiers. The injected data symbol is unique. Different injected data symbols may have the same instruction code or identifiers, but when both the instruction code and identifiers are the same, the injected data symbol must be the same. Therefore, the injected data symbol or the (instruction code, identifiers) tuple can serve as the primary key of the injected data attribute table in the database. The server obtains the attribute information of the injected data and the pre-built frame structure information to construct a configuration information data dictionary for the injected data. The (instruction code, identifiers) tuple obtained using the frame structure information corresponds to the injected data symbol and injected data name in the attribute information.

[0073] Figure 3 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application, as shown below. Figure 3 As shown, the steps for pre-constructing the frame structure information include:

[0074] S301: Obtain structure index information and structure details; the structure index information includes: injection structure identifier, substructure identifier, and substructure name; the structure details include multiple fields; the attributes of the fields include field type; the field type includes data substructure and instruction code;

[0075] Specifically, the server obtains the structure index information and detailed structure information input by the operator through the interactive device to construct the frame structure information of the injected data. The structure index information consists of: the injection structure identifier, the substructure identifier, and the substructure name. The detailed structure information corresponding to the structure index information contains multiple fields. Among them, the field type can be a data substructure, pointing to the next level, thereby constructing a tree-structured configuration information for the injected data frame structure.

[0076] In one embodiment, each field in the structure details is described by attributes such as field description, field type, length, data type, field value, byte order, repetition count, conversion formula, and default value.

[0077] Field descriptions are used to describe the actual meaning of the fields so that binding personnel can quickly understand the function of the fields;

[0078] Field types are categorized according to their function, including: identification characters, input parameters, fixed values, data field length, data substructure, instruction encoding, number of data fields, instruction code, padding code, checksum, injected data block, BCH code, frame sequence number, packet sequence number, random code, instruction data block, digital signature and proxy data block, etc.

[0079] Data types are used to describe the physical data type of the field source code. When parsing data, data conversion is required based on the data type. The main types include: unsigned integer, signed integer, floating-point, time type, and data block, etc.

[0080] The field value is used to constrain the legal value range of the field, so as to perform field physical meaning comparison and legality verification; the content of the field value is determined according to the field type: when the field type is a fixed value, the field value is the corresponding fixed value; when the field type is a data substructure, the field value is the injection structure identifier of the next layer; when the field type is an input parameter, the field value is the parameter's legal enumeration value or value range.

[0081] Byte order describes the order in which bytes are arranged during storage, including little-endian and big-endian byte order;

[0082] The repetition count is the number of times the field appears in the data;

[0083] Conversion formulas are used to describe dimensional conversion formulas or complex calculation formulas between source code values ​​and physical values.

[0084] S302: Generate the frame structure information based on the structure index information and the structure details.

[0085] Specifically, in order to construct a configuration information data dictionary for injected data and shield the impact of remote control system and differences in remote control interfaces of different subsystems, the server pre-constructs frame structure information, which includes structure index information and corresponding detailed structure information.

[0086] S202: Construct the configuration information data dictionary based on the attribute information and the frame structure information.

[0087] Specifically, in order to shield the effects of remote control mechanisms and differences in remote control interfaces of different subsystems, the server pre-builds a configuration information data dictionary for the injected data. This configuration information data dictionary includes the attribute information and frame structure information of the injected data.

[0088] Figure 4 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application, as shown below. Figure 4 As shown, S102 includes:

[0089] S401: Perform a search and matching using the data source code and the frame structure information;

[0090] Specifically, the server searches and matches nodes in the frame structure tree level by level based on the given data source code. Matching begins with the details of the current node. If the source code does not completely match the information of the current node, it continues to try matching with the node's sibling nodes. During this process, a tree structure is used for layer-by-layer searching to ensure that all potential matching nodes are covered.

[0091] During the matching process, if a substructure of data is encountered, the server temporarily records the current breakpoint position and then continues the matching operation at the next level of the substructure. This layer-by-layer matching method allows the server to effectively process nested complex data structures. If the source code matches successfully at a certain substructure level, the server backtracks to the breakpoint position of the previous level and continues to process the unfinished matching fields from that level until all levels and fields have been processed, or backtracks to the root node of the frame structure tree.

[0092] S402: If the match is successful, generate a parsing result based on the information obtained from the match; if the match fails, return a verification result indicating that the verification failed.

[0093] Specifically, during the matching process, the server not only performs structural matching but also parses the source code of each field to extract the corresponding physical values. Simultaneously, the server records the matched identification code, instruction code (if the structural details include an instruction code field), checksum, and input parameters. After successfully traversing and matching the injection frame structure tree, the server constructs a unique identification string using the recorded identification codes for each substructure level. It then combines this string with the matched instruction code to retrieve the corresponding code and name of the injected data from the configuration information data dictionary. The final parsing result includes the identification string, instruction code, input parameters, checksum, injected data code, and injected data name.

[0094] If, during the matching process, the data source code of the injected data cannot match any node in the frame structure tree, it is judged as a verification failure, indicating that the injected source code does not meet the predetermined injection format requirements.

[0095] In one embodiment, based on the identification string and instruction encoding, the server can find the code and name corresponding to the injected data from the attribute information of the injected data, and further confirm the source and purpose of the injected data.

[0096] S103: Verify the injected data based on the preset input parameters and the parsing results.

[0097] Specifically, the server parses the data source code using a pre-built configuration information data dictionary of the injection data. After obtaining the parsing result, it verifies the data source code of the parsed injection data based on the preset input parameters when generating the injection data and the parsing result.

[0098] Figure 5 This is a flowchart illustrating a spacecraft injection data parsing and verification method according to an embodiment of this application, as shown below. Figure 5 As shown, S103 includes:

[0099] S501: Perform a validity check on the parsing result to obtain the first verification result;

[0100] Specifically, after the server receives the parsing results of the injected data, in order to ensure the integrity and legality of the data, the server performs legality checks on the fields in the parsing results according to preset rules to verify whether they conform to the specifications and obtain the first verification result.

[0101] In one embodiment, the validity check includes field format check, numerical range check, instruction validity check, and condition rule check, such as verifying whether the check code in the parsing result is correct, verifying whether the input parameter in the parsing result exceeds the predetermined value range, or verifying whether the data type of the input parameter conforms to the rule.

[0102] S502: Verify whether the preset input parameters and the input parameters in the parsing result are consistent, and obtain a second verification result;

[0103] Specifically, the server automatically parses the input parameters from the data source code and compares them with the parameters manually entered during data generation to obtain a second verification result. If any invalid or inconsistent fields are found, the server marks them in the output and prompts manual verification, which helps to efficiently locate the problematic fields in the subsequent review process.

[0104] S503: Generate a parsing and verification file based on the parsing result, the first verification result, and the second verification result.

[0105] Specifically, if the injected source code is successfully matched but there are problems with the values ​​of certain fields, the server generates a parsing verification file based on the parsing results, the first verification results, and the second verification results. The server then marks the verification information in the corresponding fields of the parsing verification file to facilitate further manual review and processing.

[0106] In one embodiment, the parsing and verification file of the injected data is a human-machine readable XML format file, which includes information such as the name of the injected data, the symbol, the data source code, and input parameters. When outputting the parsing and verification file, it is possible to customize the information that needs to be output.

[0107] In one embodiment, issues with the values ​​of certain fields may include verification failure, input parameters exceeding the predetermined value range, or invalid data types of input parameters.

[0108] In one embodiment, after completing the parsing and verification of the injected data, the server also provides a human-readable online display through a display device.

[0109] In one embodiment, the injection source code to be parsed is: "7625F011EA……020122AA000000010000……6985H".

[0110] The server-pre-built configuration information data dictionary for injected data is shown in Tables 1-4. This dictionary includes the attribute information and frame structure information of the injected data. The attribute information is shown in Table 4, and the frame structure information for the six-layer injected data is shown in Tables 1-3 (only partial information for layers 1, 2, and 6 is shown). The corresponding injected frame structure index tree is shown below. Figure 12 As shown, the parsing process of the above-mentioned injection source code to be parsed is as follows: Figure 13 As shown.

[0111] Table 1

[0112]

[0113]

[0114] Table 2

[0115]

[0116] Table 3

[0117]

[0118] Table 4

[0119]

[0120] The matching process begins with the first layer of injected frame structure information. The first 24 bits of the injected data source code, "7625F0H", successfully match the first and second fields in the detailed information of the F0H substructure in L1. Since the second field is a recognition character, the recognition character for this layer is recorded as F0H and added to the injected data recognition character string. The third field is a data substructure; based on its field value, the L2 structure information needs to be searched.

[0121] The process sequentially matches the detailed information of the substructures in the L2 index. The subsequent source code is 11H, while the first field of the detailed information of the 22H substructure in the L2 structure is 22H, resulting in a match failure. Therefore, the matching of this substructure is terminated, and the matching of the next substructure in the same layer continues. The 11H substructure in the L2 index completely matches the injected source code information, so the current layer's identification character 11H is appended to the identification string of the injected data, resulting in the new identification string "F0H 11H". The search continues for the lower-level frame structure information until the lowest-level frame structure (the leaf node of the frame structure information tree) is parsed, and the process backtracks to the root node to complete the parsing. The final injected data identification string is "F0H 11H 0004H 000001B1111H 0201H", and two input parameters are parsed: 22H and 000000010000H. The correction trend is 22H. The physical meanings of these values, determined by the field values, are: subtracting the time difference from the current relative time, with a time difference of 1 second. Using the identified strings and instruction codes recorded during the parsing process (no instruction code field in this data), the injected data code S0001 and name "Subsystem 1 Time Synchronization" can be identified from the attribute information of the injected data. The two parsed input parameters are then compared and verified against the manually entered parameters during data generation. Finally, the results are input into the parsing and verification XML file to complete this parsing and verification process.

[0122] This application provides a method for parsing and verifying spacecraft injection data. The method involves acquiring the data source code of the injection data, which is generated based on preset input parameters. The data source code is parsed using a pre-constructed configuration information data dictionary to obtain a parsing result. The injection data is then verified based on the preset input parameters and the parsing result. This effectively masks the differences in injection formats across different spacecraft, achieving standardized parsing and verification of remote-controlled injection data. Specifically, acquiring the data source code supports both offline data parsing and verification, as well as online real-time parsing and verification of uplink injection data. Parsing the data source code using a pre-constructed configuration information data dictionary effectively masks the differences in injection formats across different spacecraft, adapting to dual-remote control systems and multiple injection format parsing and verification methods.

[0123] Based on the same inventive concept, this application also provides a spacecraft injection data parsing and verification device, which can be used to implement the method described in the above embodiments, as described in the following embodiments. Since the principle of the spacecraft injection data parsing and verification device in solving the problem is similar to that of the spacecraft injection data parsing and verification method, the implementation of the spacecraft injection data parsing and verification device can refer to the implementation of the software performance benchmark determination method, and repeated details will not be elaborated further. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0124] Figure 6 This is a schematic diagram of the structure of a spacecraft injection data parsing and verification device provided in an embodiment of this application, as shown below. Figure 6 As shown, the device includes:

[0125] Data acquisition unit 601 is used to acquire the data source code of the injected data; the injected data is generated according to preset input parameters;

[0126] The data parsing unit 602 is used to parse the data source code using a pre-built configuration information data dictionary of the injected data to obtain the parsing result;

[0127] The data verification unit 603 is used to verify the injected data based on the preset input parameters and the parsing results.

[0128] Figure 7 This is a schematic diagram of the structure of a spacecraft injection data analysis and verification device provided in an embodiment of this application. Figure 6 Based on the embodiments, further, such as Figure 7 As shown, the spacecraft injection data analysis and verification device provided in this application also includes:

[0129] The first information acquisition unit 701 is used to acquire the attribute information and pre-constructed frame structure information of the injected data;

[0130] The data dictionary construction unit 702 is used to construct the configuration information data dictionary based on the attribute information and the frame structure information.

[0131] Figure 8 This is a schematic diagram of the structure of a spacecraft injection data analysis and verification device provided in an embodiment of this application. Figure 7 Based on the embodiments, further, such as Figure 8 As shown, the spacecraft injection data analysis and verification device provided in this application also includes:

[0132] The second information acquisition unit 801 is used to acquire structure index information and structure details; the structure index information includes: injected structure identifier, substructure identification code and substructure name; the structure details include multiple fields; the attributes of the fields include field type; the field type includes data substructure and instruction code;

[0133] The frame structure information construction unit 802 is used to generate the frame structure information based on the structure index information and the structure details.

[0134] Figure 9 This is a schematic diagram of the structure of a spacecraft injection data analysis and verification device provided in an embodiment of this application. Figure 7 Based on the embodiments, further, such as Figure 9 As shown, the spacecraft injection data analysis and verification device provided in this application also includes:

[0135] Data matching module 901 is used to perform search matching using the data source code and the frame structure information;

[0136] The data parsing module 902 is used to generate a parsing result based on the information obtained from the matching if the match is successful; if the match fails, it returns a verification result indicating that the verification failed.

[0137] Figure 10 This is a schematic diagram of the structure of a spacecraft injection data analysis and verification device provided in an embodiment of this application. Figure 6 Based on the embodiments, further, such as Figure 10 As shown, the spacecraft injection data analysis and verification device provided in this application also includes:

[0138] The first data verification module 1001 is used to verify the legality of the parsing result and obtain a first verification result;

[0139] The second data verification module 1002 is used to verify whether the preset input parameters and the input parameters in the parsing result are consistent, and to obtain a second verification result.

[0140] The parsing verification file generation module 1003 is used to generate a parsing verification file based on the parsing result, the first verification result, and the second verification result.

[0141] This application provides a method for parsing and verifying spacecraft injection data. The method involves acquiring the data source code of the injection data, which is generated based on preset input parameters. The data source code is parsed using a pre-constructed configuration information data dictionary to obtain a parsing result. The injection data is then verified based on the preset input parameters and the parsing result. This effectively masks the differences in injection formats across different spacecraft, achieving standardized parsing and verification of remote-controlled injection data. Specifically, acquiring the data source code supports both offline data parsing and verification, as well as online real-time parsing and verification of uplink injection data. Parsing the data source code using a pre-constructed configuration information data dictionary effectively masks the differences in injection formats across different spacecraft, adapting to dual-remote control systems and multiple injection format parsing and verification methods.

[0142] Figure 11 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of this application, as shown below. Figure 11 As shown, the electronic device may include a processor 1101, a communications interface 1102, a memory 1103, and a communication bus 1104, wherein the processor 1101, the communications interface 1102, and the memory 1103 communicate with each other via the communication bus 1104. The processor 1101 can call logical instructions in the memory 1103 to execute the following methods: obtaining the data source code of the injected data; the injected data is generated according to preset input parameters; parsing the data source code using a pre-constructed configuration information data dictionary of the injected data to obtain a parsing result; and verifying the injected data according to the preset input parameters and the parsing result.

[0143] Furthermore, the logical instructions in the aforementioned memory 1103 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0144] This embodiment discloses a computer program product, which includes a computer program stored on a computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer can execute the methods provided in the above-described method embodiments, such as: obtaining the data source code of the injected data; the injected data is generated according to preset input parameters; parsing the data source code using a pre-constructed configuration information data dictionary of the injected data to obtain a parsing result; and verifying the injected data according to the preset input parameters and the parsing result.

[0145] This embodiment provides a computer-readable storage medium storing a computer program that causes the computer to execute the methods provided in the above-described method embodiments, such as: obtaining the data source code of the injected data; the injected data being generated according to preset input parameters; parsing the data source code using a pre-constructed configuration information data dictionary of the injected data to obtain a parsing result; and verifying the injected data according to the preset input parameters and the parsing result.

[0146] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application 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.

[0147] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. 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... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0148] 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 1One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0149] 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.

[0150] 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 this application. 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.

[0151] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for analyzing and verifying injected data from a spacecraft, characterized in that, include: Obtain the data source code for the injected data; The injected data is generated based on preset input parameters; The data source code is parsed using a pre-built configuration information data dictionary of the injected data to obtain the parsing result; The injected data is verified based on the preset input parameters and the parsing results; The steps for pre-constructing the configuration information data dictionary include: Obtain the attribute information and pre-constructed frame structure information of the injected data; The configuration information data dictionary is constructed based on the attribute information and the frame structure information; The steps for pre-constructing the frame structure information include: Obtain structural index information and structural details; the structural index information includes: injected structural identifier, substructure identifier, and substructure name; the structural details include multiple fields; the attributes of each field include field description, field type, length, data type, field value, byte order, repetition count, conversion formula, and default value; the field types are divided according to their functions, including: identifier, input parameter, fixed value, data field length, data substructure, instruction encoding, number of data fields, instruction code, padding code, checksum, injected data block, BCH code, frame sequence number, packet sequence number, random code, instruction data block, digital signature, and proxy data block; The frame structure information is generated based on the structure index information and the structure details; The step of parsing the data source code using a pre-built configuration information data dictionary of injected data includes: The data source code and the frame structure information are used for search and matching; If the match is successful, a parsing result is generated based on the information obtained from the match; if the match fails, a verification result indicating verification failure is returned. Specifically, after completing the traversal of the injection frame structure tree and successfully matching, a unique identification string is constructed using the identification code corresponding to each layer of the substructure. Combined with the instruction code obtained from the match, the code and name of the injected data are retrieved from the configuration information data dictionary. The final parsing result includes the identification string, instruction code, input parameters, verification code, injected data code, and injected data name. The search and matching using the data source code and the frame structure information includes: Based on the given data source code, the nodes in the frame structure tree are searched and matched level by level; the matching starts from the details of the current node; if the source code does not completely correspond to the information of the current node, the matching with the sibling nodes of the current node is continued; a tree structure is used to search level by level to ensure that all potential matching nodes are covered. If a substructure of data is encountered, the current breakpoint position is temporarily recorded, and then the matching operation continues at the next level of the substructure. If the source code is successfully matched in a certain substructure level, the process backtracks to the breakpoint position of the previous level and continues to process the unfinished matching fields from that level until all levels and fields have been processed, or backtracks to the root node of the frame structure tree.

2. The spacecraft injected data parsing and verification method according to claim 1, characterized in that, The step of verifying the injected data based on the preset input parameters and the parsing result includes: The parsing result is validated to obtain the first validation result; Verify whether the preset input parameters and the input parameters in the parsing result are consistent to obtain a second verification result; A parsing and verification file is generated based on the parsing results, the first verification result, and the second verification result.

3. A spacecraft injected data analysis and verification device, characterized in that, include: The data acquisition unit is used to acquire the data source code for the injected data. The injected data is generated based on preset input parameters; The data parsing unit is used to parse the data source code using a pre-built configuration information data dictionary of the injected data to obtain the parsing result; The data verification unit is used to verify the injected data based on the preset input parameters and the parsing results; The first information acquisition unit is used to acquire the attribute information and pre-constructed frame structure information of the injected data; A data dictionary construction unit is used to construct the configuration information data dictionary based on the attribute information and the frame structure information; The second information acquisition unit is used to acquire structural index information and structural details; The structure index information includes: injected structure identifier, substructure identifier, and substructure name; the structure details include multiple fields; the attributes of each field include field description, field type, length, data type, field value, byte order, repetition count, conversion formula, and default value; the field types are divided according to their functions, including: identifier, input parameter, fixed value, data field length, data substructure, instruction encoding, number of data fields, instruction code, padding code, checksum, injected data block, BCH code, frame sequence number, packet sequence number, random code, instruction data block, digital signature, and proxy data block; A frame structure information construction unit is used to generate the frame structure information based on the structure index information and the structure details; The data acquisition unit includes: The data matching module is used to perform search matching using the data source code and the frame structure information; The data parsing module is used to generate a parsing result based on the information obtained from the matching if the match is successful; if the match fails, it returns a verification result indicating that the verification failed. Specifically, after completing the traversal of the injection frame structure tree and successfully matching, a unique identification string is constructed using the identification code corresponding to each substructure recorded. Combined with the instruction code obtained from the matching, the code and name of the injected data are retrieved from the configuration information data dictionary. The final parsing result includes the identification string, instruction code, input parameters, verification code, injected data code, and injected data name. The data matching module is specifically used for: Based on the given data source code, the nodes in the frame structure tree are searched and matched level by level; the matching starts from the details of the current node; if the source code does not completely correspond to the information of the current node, the matching with the sibling nodes of the current node is continued; a tree structure is used to search level by level to ensure that all potential matching nodes are covered. If a substructure of data is encountered, the current breakpoint position is temporarily recorded, and then the matching operation continues at the next level of the substructure. If the source code is successfully matched in a certain substructure level, the process backtracks to the breakpoint position of the previous level and continues to process the unfinished matching fields from that level until all levels and fields have been processed, or backtracks to the root node of the frame structure tree.

4. 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 according to any one of claims 1 to 2.

5. 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 according to any one of claims 1 to 2.

6. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method described in any one of claims 1 to 2.

Images