Satellite-borne software reconstruction method and device and electronic equipment

Abstract

The invention provides a satellite-borne software reconstruction method and device and electronic equipment, and relates to the technical field of satellite software reconstruction. The method is applied to a satellite system, the satellite system corresponds to at least one computing node of a processing planning computer in a satellite, each computing node is used for processing a corresponding type of file, and the method comprises the following steps: obtaining an original file of target satellite-borne software, coding and compressing the original file to obtain a target transmission file, and sending the target transfer file to a processing planning computer to enable the processing planning computer to store the target transfer file in the target computing node, sending a reconstruction instruction to the processing planning computer, triggering the processing planning computer to decompress the target transfer file, and reconstructing the target computing node based on the original file. On the basis of the mode, the uploading time of the satellite-borne software is shortened, and the efficiency of loading new software by the satellite is improved.

Description

Technical Field

[0001] The present application mainly relates to the field of satellite software reconstruction technology, and in particular to a satellite-borne software reconstruction method, device and electronic equipment. Background Art

[0002] Onboard software upload means that when the software functions on the satellite need to be significantly changed, the ground system (such as the tracking and control station) uploads the new onboard software to the satellite through the tracking and control link and replaces the original software. At present, with the increasing complexity of satellite missions, software development work has become more complicated, and the software upload data blocks are getting larger and larger. In this case, the ground system may not be able to upload the required complete onboard software to the satellite in a short period of time, which brings difficulties to the operation and maintenance management of the satellite. Summary of the invention

[0003] The purpose of the present application is to provide a satellite-borne software reconstruction method, device and electronic equipment for reducing the time of satellite-borne software loading and improving the efficiency of loading new software on satellites.

[0004] To achieve the above-mentioned object, in a first aspect of the present application, a satellite-borne software reconstruction method is provided, which is applied to a satellite system, wherein the satellite system corresponds to at least one computing node of a processing planning computer in a satellite, and each computing node is used to process a corresponding type of file, and the method comprises:

[0005] Acquire an original file of the target onboard software, encode and compress the original file, and obtain a target transmission file, wherein the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file;

[0006] Sending the target transmission file to the processing planning computer, triggering the processing planning computer to select a target computing node associated with the file type from the at least one computing node, and storing the target transmission file in the target computing node, during the storage process: performing data verification on the received target transmission file based on the data length and the accumulated checksum;

[0007] Sending a reconstruction instruction to the processing planning computer triggers the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0008] In an optional implementation manner, encoding and compressing the original file to obtain a target transmission file includes:

[0009] Read multiple bytes of the original file in sequence according to the byte order of the original file, and perform the following operations each time the bytes are read:

[0010] Determine whether the value of a read byte is zero; if so, generate a first compressed element and a first key element corresponding to the byte according to the value of the byte; otherwise, read the next i candidate bytes whose values ​​are zero, and generate a second compressed element and a second key element corresponding to the byte and the next i candidate bytes according to the values ​​of the byte and the next i candidate bytes, wherein i is an integer greater than or equal to 0 and less than or equal to 32;

[0011] Obtaining a compression package corresponding to the original file according to the generated first compression elements and second compression elements, and obtaining a key package corresponding to the original file according to the generated first key elements and second key elements;

[0012] The file type, the target storage address, the data length and the accumulated checksum are respectively carried into the compressed package and the key package to obtain the corresponding target transmission file.

[0013] In an optional implementation, the sending the target transmission file to the processing planning computer includes:

[0014] The target transmission file is divided into a plurality of transmission file frames of a specified packet length, and the plurality of transmission file frames are respectively sent to a transponder in the satellite through a high-speed link channel, so that the transponder sends the target transmission file to the processing planning computer.

[0015] In an optional implementation, sending a reconstruction instruction to the processing planning computer to trigger the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file includes:

[0016] Sending a remote control instruction to the processing planning computer to trigger the processing planning computer to decompress the target transmission file to obtain the original file; and

[0017] A node write instruction is sent to the processing planning computer to trigger the processing planning computer to enter a reconstruction mode, and in the reconstruction mode, the target computing node is reconstructed based on the original file.

[0018] In an optional implementation, after sending the node reconstruction instruction to the processing planning computer, the method further includes:

[0019] A node restart instruction is sent to the processing planning computer, triggering the processing planning computer to restart the target computing node.

[0020] In a second aspect of the present application, a satellite-borne software reconstruction method is provided, the method being applied to a processing planning computer having at least one computing node in a satellite, the processing planning computer corresponding to a satellite system, each computing node being used to process a corresponding type of file, the method comprising:

[0021] receiving a target transmission file sent by the satellite system, wherein the target transmission file is obtained by encoding and compressing an original file of target onboard software by the satellite system, and the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file;

[0022] A target computing node associated with the file type is selected from the at least one computing node, and the target transmission file is stored in the target computing node. During the storage process: based on the data length and the accumulated checksum, data verification is performed on the received target transmission file;

[0023] In response to the reconstruction instruction sent by the satellite system, the target transmission file is decompressed to obtain the original file, and the target computing node is reconstructed based on the original file.

[0024] In an optional implementation, the performing data verification on the received target transmission file based on the data length and the accumulated checksum includes:

[0025] When m bytes of the target transmission file are received, a current length and a current checksum corresponding to the m bytes are calculated, where m is a preset integer;

[0026] Determine whether the current length matches the data length, and determine whether the current checksum matches the accumulated checksum; wherein:

[0027] If the current length matches the data length, and the current checksum matches the accumulated checksum, it is determined that the target transmission file passes the data check.

[0028] In a third aspect of the present application, a satellite-borne software reconstruction device is provided, the device is applied to a satellite system, the satellite system corresponds to at least one computing node of a processing planning computer in a satellite, each computing node is used to process a corresponding type of file, the device comprises:

[0029] A software compression module is used to obtain an original file of the target onboard software, encode and compress the original file, and obtain a target transmission file, wherein the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file;

[0030] A file transmission module, configured to send the target transmission file to the processing planning computer, trigger the processing planning computer to select a target computing node associated with the file type from the at least one computing node, and store the target transmission file in the target computing node, and during the storage process: perform data verification on the received target transmission file based on the data length and the accumulated checksum;

[0031] An instruction reconstruction module is used to send a reconstruction instruction to the processing planning computer, trigger the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0032] In a fourth aspect of the present application, a satellite-borne software reconstruction device is provided, the device is applied to a processing planning computer having at least one computing node in a satellite, the processing planning computer corresponds to a satellite system, each computing node is used to process a corresponding type of file, the device comprises:

[0033] A file receiving module is used to receive a target transmission file sent by the satellite system, wherein the target transmission file is obtained by the satellite system encoding and compressing an original file of the target onboard software, and the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file;

[0034] A node storage module, configured to select a target computing node associated with the file type from the at least one computing node, and store the target transmission file in the target computing node, and during the storage process: perform data verification on the received target transmission file based on the data length and the accumulated checksum;

[0035] The software reconstruction module is used to respond to the reconstruction instruction sent by the satellite system, decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0036] In a fifth aspect of the present application, an electronic device is provided, comprising a memory and a processor, wherein the memory stores instructions, and when the instructions are called by the processor, the processor executes the method described in any one of the first aspect or the second aspect.

[0037] Compared with the prior art, this application has the following advantages:

[0038] The present application provides a satellite-borne software reconstruction method, device and electronic device, which compresses the original file of the target satellite-borne software through the ground system, and triggers the satellite to store the target transmission file in the target computing node until the ground system initiates a reconstruction instruction to the satellite to decompress the target transmission file, thereby reducing the on-board software loading time and improving the efficiency of the satellite loading new satellite service software. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings are included to provide a further understanding of the present application. They are included and constitute a part of the present application. The accompanying drawings illustrate embodiments of the present application and together with the present specification serve to explain the principles of the present application. In the accompanying drawings:

[0040] Figure 1 is a flow chart of a satellite-borne software reconstruction method provided by an embodiment of the present application;

[0041] Figure 2 This is a schematic diagram of a high-speed link provided by an embodiment of the present application;

[0042] Figure 3 is a flow chart of another onboard software reconstruction method provided by an embodiment of the present application;

[0043] Figure 4 It is a logical schematic diagram of data verification provided by an embodiment of the present application;

[0044] Figure 5 is a logical schematic diagram of reconstructing a target computing node provided by an embodiment of the present application;

[0045] Figure 6 This is a schematic diagram of a satellite-borne software reconstruction device provided by an embodiment of the present application;

[0046] Figure 7 It is a schematic diagram of another onboard software reconstruction device provided by an embodiment of the present application;

[0047] Figure 8 This is a schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0049] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0050] Unless otherwise specifically stated, the relative arrangement, numerical expressions and numerical values ​​of the parts and steps set forth in these embodiments do not limit the scope of the present application. At the same time, it should be understood that, for ease of description, the sizes of the various parts shown in the accompanying drawings are not drawn according to the actual proportional relationship. The technology, method and equipment known to those of ordinary skill in the relevant field may not be discussed in detail, but in appropriate cases, the technology, method and equipment should be considered as a part of the authorization specification. In all examples shown and discussed here, any specific value should be interpreted as being merely exemplary, rather than as a limitation. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so that once a certain item is defined in an accompanying drawing, it does not need to be further discussed in subsequent drawings.

[0051] In addition, it should be noted that the use of words such as "first" and "second" to define components is only for the convenience of distinguishing the corresponding components. If not otherwise stated, the above words have no special meaning and cannot be understood as limiting the scope of protection of this application. In addition, although the terms used in this application are selected from well-known and commonly used terms, some terms mentioned in the specification of this application may be selected by the applicant at his or her discretion, and their detailed meanings are explained in the relevant parts of the description of this article. In addition, it is required to understand this application not only by the actual terms used, but also by the meaning implied by each term.

[0052] The embodiments of the present application describe a satellite-borne software reconstruction method and a system for its application. It should be understood that the system is composed of all physical devices or equipment involved in the satellite-borne software reconstruction method. For example, the system may include a ground system (such as a tracking and control station) and a satellite. Alternatively, it may also include various physical devices, communication equipment, etc. that constitute the communication link between the ground system and the satellite.

[0053] In the embodiments described in the present application, the hardware system of the satellite includes a processing planning computer and at least one computing node. Each computing node is used to process a corresponding type of file. For example, each computing node can refer to a slave computer to be uploaded or reconstructed. Each slave computer can process a corresponding type of file (e.g., programmable array logic FPGA software).

[0054] To make the objectives, technical solutions and advantages of the present invention more clear, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0055] Flowcharts are used in the present application to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed accurately in order. On the contrary, various steps may be processed in reverse order or simultaneously. At the same time, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0056] See also Figure 1 FIG. 1 is a flowchart of a satellite-borne software reconstruction method provided by the present application. The method is applied to a satellite system. The satellite system corresponds to at least one computing node of a processing planning computer in a satellite. Each computing node is used to process a corresponding type of file. The method includes:

[0057] S101, obtaining the original file of the target satellite-borne software, encoding and compressing the original file to obtain the target transmission file.

[0058] The target transmission file includes at least: the file type of the original file, the target storage address of the original file, the data length of the original file, and the accumulated checksum of the original file.

[0059] In an optional implementation, encoding and compressing the original file to obtain the target transmission file includes:

[0060] Step 1: read multiple bytes of the original file in sequence according to the byte order of the original file, and perform the following operations each time the bytes are read:

[0061] Determine whether the value of a byte read is zero; if so, generate a first compressed element and a first key element corresponding to the byte according to the value of the byte, otherwise, read the next i candidate bytes whose values ​​are zero, and generate a second compressed element and a second key element corresponding to the byte and the next i candidate bytes according to the values ​​of the byte and the next i candidate bytes, where i is an integer greater than or equal to 0 and less than or equal to 32.

[0062] The target satellite-borne software is low-speed interface FPGA software as an example for subsequent description. The original file size of the low-speed interface FPGA software is 11176KB, and the low-speed interface FPGA software can be processed by the computing node a in the satellite.

[0063] Referring to Table 1 below, the data in the original file of the target transmission file provided by an embodiment of the present application is as follows:

[0064] Table 1

[0065]

[0066] The original file is encoded and compressed according to step 1, specifically as follows: the data of the first line (i.e., the first byte) is read as 00110000, and a first compression element 00110000 and a first key element 1 corresponding to the first byte are generated; the data of the second line (i.e., the second byte) is read as 00000010, and a first compression element 00000010 and a first key element 1 corresponding to the second byte are generated; ...; the data of the 5th to 8th lines (i.e., the 5th to 8th bytes) are read as 00000000, and the first compression element 00000010 and a first key element 1 corresponding to the 5th to 8th bytes are generated. The data of the 9th row (i.e., the 9th byte) is read as 00110000, and a first compressed element 00110000 and a first key element 1 corresponding to the 9th byte are generated... and so on. Referring to Table 2 below, the compressed elements (including all first compressed elements and second compressed elements) and key elements (including all first key elements and second key elements) generated according to step 1 in one embodiment of the present application are as follows:

[0067] Table 2

[0068]

[0069] Step 2: Obtain a compressed package corresponding to the original file based on the generated first compression elements and second compression elements, and obtain a key package corresponding to the original file based on the generated first key elements and second key elements.

[0070] The generated key elements are aggregated into a compressed package corresponding to the above original file, and the generated key elements are aggregated into a key package corresponding to the above original file.

[0071] Taking the target satellite-borne software as low-speed interface FPGA software as an example, the size of the key package generated by the original file of the software is 512KB, and the size of the compressed package is 4114KB. Therefore, the above method can effectively compress the original file and reduce the amount of data that needs to be transmitted to the satellite later.

[0072] Step 3, carry the file type, target storage address, data length and cumulative checksum into the compressed package and key package respectively to obtain the corresponding target transmission file.

[0073] Furthermore, the present application enhances the security of the compressed package and the key package transmitted on the link by carrying the file type, target storage address, data length and cumulative checksum into the compressed package and the key package respectively.

[0074] Taking the target satellite-borne software as low-speed interface FPGA software as an example, referring to Table 3 below, the information added to the compressed package and key package provided in an embodiment of the present application is as follows:

[0075] Table 3

[0076] information Compressed package Key Package File Type 0xF0 0xF0 Target storage address 0x70040000 0x70040000 Data length 0x1012 0x0200 Accumulate checksum 0xB1C483A 0x0128B106

[0077] Optionally, a corresponding compressed package identifier 0x02 is added to the compressed package, and a corresponding key package identifier 0x01 is added to the key, so as to distinguish the compressed package from the key package.

[0078] S102, sending the target transfer file to the processing planning computer, triggering the processing planning computer to select a target computing node associated with the file type from at least one computing node, and storing the target transfer file in the target computing node. During the storage process: based on the data length and the accumulated checksum, the received target transfer file is subjected to data verification.

[0079] Optionally, when the satellite enters, the target transmission file is sent to the processing planning computer, and the target computing node in the processing planning computer temporarily stores the received target transmission file. Optionally, the target computing node can store the target transmission file in a double rate synchronous dynamic random access memory DDR and perform data verification on it based on the data length and the accumulated checksum.

[0080] In an optional embodiment, sending the target transmission file to the processing planning computer includes:

[0081] The target transmission file is divided into a plurality of transmission file frames of specified packet lengths, and the plurality of transmission file frames are respectively sent to a transponder in a satellite through a high-speed link channel, so that the transponder sends the target transmission file to a processing planning computer.

[0082] For example, see Figure 2 As shown, in one embodiment of the present application, the high-speed link includes: a measurement and control front end, a ground inspection, a ground antenna, a satellite antenna, a transponder, and a satellite service computer. Specifically, after the satellite system generates a target transmission file, the measurement and control front end divides the target transmission file into transmission file frames of a specified packet length, and sends the transmission file frames to the satellite antenna through the ground inspection and the ground antenna. After the satellite antenna receives the transmission file frame, it is processed and forwarded by the transponder in the satellite and the satellite service computer, and the planning processing computer receives the target transmission file.

[0083] S103, sending a reconstruction instruction to the processing planning computer, triggering the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0084] In an optional implementation, sending a reconstruction instruction to a processing planning computer triggers the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file, including:

[0085] Sending a remote control command to the processing planning computer to trigger the processing planning computer to decompress the target transmission file to obtain the original file; and

[0086] A node write instruction is sent to the processing planning computer, triggering the processing planning computer to enter a reconstruction mode, and in the reconstruction mode, the target computing node is reconstructed based on the original file.

[0087] Taking the target satellite-borne software as low-speed interface FPGA software as an example, referring to Table 4 below, the decompressed original file provided by an embodiment of the present application is as follows:

[0088] Table 4

[0089]

[0090] In an optional implementation, after sending the node reconstruction instruction to the processing planning computer, the method further includes:

[0091] Send a node restart instruction to the processing planning computer, triggering the processing planning computer to restart the target computing node.

[0092] See also Figure 3FIG. 1 is a flowchart of another satellite-borne software reconstruction method provided by the present application. The method is applied to a processing planning computer having at least one computing node in a satellite. The processing planning computer corresponds to a satellite system. Each computing node is used to process a corresponding type of file. The method includes:

[0093] S301, receiving a target transmission file sent by a satellite system.

[0094] Optionally, when the satellite enters, receive the target transmission file sent by the satellite system.

[0095] The target transmission file is obtained by encoding and compressing the original file of the target onboard software by the satellite system, and the target transmission file at least includes: the file type of the original file, the target storage address of the original file, the data length of the original file, and the cumulative checksum of the original file.

[0096] S302, selecting a target computing node associated with the file type from at least one computing node, and storing the target transmission file in the target computing node. During the storage process: performing data verification on the received target transmission file based on the data length and the accumulated checksum.

[0097] Optionally, the target computing node may store the target transmission file in a double rate synchronous dynamic random access memory DDR, and perform data verification on the file based on the data length and the accumulated checksum.

[0098] In an optional implementation, based on the data length and the accumulated checksum, data verification is performed on the received target transmission file, including:

[0099] When m bytes of the target transmission file are received, the current length and the current checksum corresponding to the m bytes are calculated, where m is a preset integer;

[0100] Determine whether the current length matches the data length, and determine whether the current checksum matches the accumulated checksum; where:

[0101] If the current length matches the data length, and the current checksum matches the accumulated checksum, it is determined that the target transfer file passes the data check.

[0102] For example, see Figure 4 FIG. 1 is a logical diagram of data verification provided by an embodiment of the present application. In this embodiment, the processing planning computer performs data verification on the target transmission file, specifically executing the following logical steps:

[0103] S401, receiving a target transmission file.

[0104] S402: Determine a target computing node according to the type of the carried file.

[0105] S403, determining the storage address to be written according to the carried target storage address.

[0106] S404, judging the compressed package and the key package according to the carried identifier; if it is a compressed package, executing S405, if it is a key package, executing S407.

[0107] S405, determine whether the current length of the key package matches the carried key package data length; if so, execute S406, otherwise, execute S410.

[0108] S406, determine whether the current checksum of the key package matches the cumulative checksum of the carried key package; if so, execute S410, otherwise, execute S410.

[0109] S407, determine whether the current length of the compressed packet matches the length of the compressed packet data carried; if so, execute S408, otherwise, execute S410.

[0110] S408, determine whether the current checksum of the compressed package matches the cumulative checksum of the carried key package; if so, execute S409, otherwise, execute S410.

[0111] S409, passed verification.

[0112] S410, verification error, reconstruction failed.

[0113] S303, in response to the reconstruction instruction sent by the satellite system, decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0114] In an optional implementation, in response to the reconstruction instruction sent by the satellite system, decompressing the target transmission file includes:

[0115] In response to the remote control command sent by the satellite system, the target transmission file is decompressed to obtain the original file. And,

[0116] In response to the node write instruction sent by the satellite system, a reconstruction mode is entered, and in the reconstruction mode, the target computing node is reconstructed based on the original file.

[0117] In an optional implementation, after reconstructing the target computing node based on the original file, the method further includes: restarting the target computing node in response to a node restart instruction sent by the satellite system.

[0118] For example, see Figure 5As shown, it is a logical schematic diagram of reconstructing the target computing node provided by an embodiment of the present application. In this embodiment, the processing planning computer reconstructs the target computing node based on the original file, and specifically performs the following logical steps:

[0119] S501, receiving a reconstruction instruction.

[0120] S502, decompress the target transmission file to obtain the original file.

[0121] S503, receiving a node write instruction.

[0122] S504, entering a reconstruction mode, in which the target computing node is reconstructed based on the original file.

[0123] S505: Receive a node restart instruction.

[0124] S506, restart the target computing node.

[0125] Based on the above method, the present application compresses the original files of the target onboard software through the satellite system, and the satellite stores the target transmission files in the target computing node until the satellite system initiates a reconstruction instruction to the satellite to decompress the target transmission files, thereby reducing the onboard software loading time and improving the efficiency of the satellite loading new satellite service software.

[0126] For further information, see Figure 6 FIG. 1 is a schematic diagram of a satellite-borne software reconstruction device provided by an embodiment of the present application. The device is applied to a satellite system. The satellite system corresponds to at least one computing node of a processing planning computer in a satellite. Each computing node is used to process a corresponding type of file. The device includes:

[0127] The software compression module 601 is used to obtain the original file of the target satellite-borne software, encode and compress the original file, and obtain the target transmission file, wherein the target transmission file at least includes: the file type of the original file, the target storage address of the original file, the data length of the original file, and the accumulated checksum of the original file;

[0128] The file transmission module 602 is used to send the target transmission file to the processing planning computer, trigger the processing planning computer to select a target computing node associated with the file type from at least one computing node, and store the target transmission file in the target computing node. During the storage process: based on the data length and the accumulated checksum, the received target transmission file is subjected to data verification;

[0129] The instruction reconstruction module 603 is used to send a reconstruction instruction to the processing planning computer, trigger the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0130] In an optional implementation, the original file is encoded and compressed to obtain a target transmission file, and the software compression module 601 is used to:

[0131] Read multiple bytes of the original file in sequence according to the byte order of the original file, and perform the following operations each time the bytes are read:

[0132] Determine whether the value of a read byte is zero; if so, generate a first compressed element and a first key element corresponding to the byte according to the value of the byte; otherwise, read the next i candidate bytes whose values ​​are zero, and generate a second compressed element and a second key element corresponding to the byte and the next i candidate bytes according to the values ​​of the byte and the next i candidate bytes, wherein i is an integer greater than or equal to 0 and less than or equal to 32;

[0133] Obtaining a compression package corresponding to the original file according to the generated first compression elements and second compression elements, and obtaining a key package corresponding to the original file according to the generated first key elements and second key elements;

[0134] The file type, the target storage address, the data length and the accumulated checksum are respectively carried into the compressed package and the key package to obtain the corresponding target transmission file.

[0135] In an optional implementation, the target transmission file is sent to the processing planning computer, and the file transmission module 602 is used to:

[0136] The target transmission file is divided into a plurality of transmission file frames of a specified packet length, and the plurality of transmission file frames are respectively sent to a transponder in the satellite through a high-speed link channel, so that the transponder sends the target transmission file to the processing planning computer.

[0137] In an optional implementation, the sending of the reconstruction instruction to the processing planning computer triggers the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file, and the instruction reconstruction module 603 is used to:

[0138] Sending a remote control instruction to the processing planning computer to trigger the processing planning computer to decompress the target transmission file to obtain the original file; and

[0139] A node write instruction is sent to the processing planning computer to trigger the processing planning computer to enter a reconstruction mode, and in the reconstruction mode, the target computing node is reconstructed based on the original file.

[0140] In an optional implementation, after sending the node reconstruction instruction to the processing plan computer, the instruction reconstruction module 603 is further used to:

[0141] A node restart instruction is sent to the processing planning computer, triggering the processing planning computer to restart the target computing node.

[0142] See also Figure 7 FIG. 1 is a schematic diagram of another onboard software reconstruction device provided by an embodiment of the present application. The device is applied to a processing planning computer having at least one computing node in a satellite. The processing planning computer corresponds to a satellite system. Each computing node is used to process a corresponding type of file. The device includes:

[0143] The file receiving module 701 is used to receive a target transmission file sent by a satellite system, wherein the target transmission file is obtained by encoding and compressing an original file of a target onboard software by the satellite system, and the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file;

[0144] The node storage module 702 is used to select a target computing node associated with the file type from at least one computing node, and store the target transmission file in the target computing node. During the storage process: based on the data length and the accumulated checksum, the received target transmission file is subjected to data verification;

[0145] The software reconstruction module 703 is used to respond to the reconstruction instruction sent by the satellite system, decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

[0146] In an optional implementation, the data check is performed on the received target transmission file based on the data length and the accumulated checksum, and the node storage module 702 is used to:

[0147] When m bytes of the target transmission file are received, a current length and a current checksum corresponding to the m bytes are calculated, where m is a preset integer;

[0148] Determine whether the current length matches the data length, and determine whether the current checksum matches the accumulated checksum; wherein:

[0149] If the current length matches the data length, and the current checksum matches the accumulated checksum, it is determined that the target transmission file passes the data check.

[0150] See also Figure 8The present application also provides an electronic device, the electronic device comprising:

[0151] Memory 801; and

[0152] Processor 802, the memory 801 stores instructions, and when the instructions are called by the processor, the processor executes the steps of any of the above-mentioned onboard software reconstruction methods.

[0153] It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or other general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0154] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronously connected dynamic random access memory, and direct memory bus random access memory.

[0155] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.

[0156] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only used as an example and does not constitute a limitation of the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements and amendments to the present application. Such modifications, improvements and amendments are suggested in the present application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of the present application.

[0157] At the same time, the present application uses specific words to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, some features, structures or characteristics in one or more embodiments of the present application can be appropriately combined.

[0158] Some aspects of the present application may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor may be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program codes. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes ...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs ...), smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

[0159] A computer-readable medium may include a propagated data signal containing computer program code, such as in baseband or as part of a carrier wave. The propagated signal may have a variety of manifestations, including electromagnetic, optical, etc., or a suitable combination. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which may be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit a program for use. The program code on the computer-readable medium may be propagated via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above mediums.

[0160] Similarly, it should be noted that in order to simplify the description of the disclosure of this application and thus help understand one or more embodiments of the invention, in the above description of the embodiments of this application, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the object of this application are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0161] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of the present application are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0162] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions may be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the essential spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A satellite-borne software reconstruction method, characterized in that: Applied to a satellite system, the satellite system corresponds to at least one computing node of a processing planning computer in a satellite, each computing node is used to process a corresponding type of file, the method comprising: Acquire an original file of the target onboard software, encode and compress the original file, and obtain a target transmission file, wherein the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file; Sending the target transmission file to the processing planning computer, triggering the processing planning computer to select a target computing node associated with the file type from the at least one computing node, and storing the target transmission file in the target computing node, during the storage process: performing data verification on the received target transmission file based on the data length and the accumulated checksum; A reconstruction instruction is sent to the processing planning computer, triggering the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

2. The method according to claim 1, characterized in that The encoding and compressing of the original file to obtain the target transmission file includes: Read multiple bytes of the original file in sequence according to the byte order of the original file, and perform the following operations each time the bytes are read: Determine whether the value of a read byte is zero; if so, generate a first compressed element and a first key element corresponding to the byte according to the value of the byte; otherwise, read the next i candidate bytes whose values ​​are zero, and generate a second compressed element and a second key element corresponding to the byte and the next i candidate bytes according to the values ​​of the byte and the next i candidate bytes, wherein i is an integer greater than or equal to 0 and less than or equal to 32; Obtaining a compression package corresponding to the original file according to the generated first compression elements and second compression elements, and obtaining a key package corresponding to the original file according to the generated first key elements and second key elements; The file type, the target storage address, the data length and the accumulated checksum are respectively carried into the compressed package and the key package to obtain the corresponding target transmission file.

3. The method according to claim 1 or 2, characterized in that The sending of the target transmission file to the processing planning computer comprises: The target transmission file is divided into a plurality of transmission file frames of a specified packet length, and the plurality of transmission file frames are respectively sent to a transponder in the satellite through a high-speed link channel, so that the transponder sends the target transmission file to the processing planning computer.

4. The method according to claim 1 or 2, characterized in that: The sending of the reconstruction instruction to the processing planning computer, triggering the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file, includes: Sending a remote control instruction to the processing planning computer to trigger the processing planning computer to decompress the target transmission file to obtain the original file; and A node write instruction is sent to the processing planning computer to trigger the processing planning computer to enter a reconstruction mode, and in the reconstruction mode, the target computing node is reconstructed based on the original file.

5. The method according to claim 4, characterized in that After sending the node reconstruction instruction to the processing plan computer, the method further includes: A node restart instruction is sent to the processing planning computer, triggering the processing planning computer to restart the target computing node.

6. A satellite-borne software reconstruction method, characterized in that: A processing planning computer having at least one computing node in a satellite, the processing planning computer corresponding to the satellite system, each computing node being used to process a corresponding type of file, the method comprising: receiving a target transmission file sent by the satellite system, wherein the target transmission file is obtained by encoding and compressing an original file of target onboard software by the satellite system, and the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file; A target computing node associated with the file type is selected from the at least one computing node, and the target transmission file is stored in the target computing node. During the storage process: based on the data length and the accumulated checksum, data verification is performed on the received target transmission file; In response to the reconstruction instruction sent by the satellite system, the target transmission file is decompressed to obtain the original file, and the target computing node is reconstructed based on the original file.

7. The method according to claim 6, characterized in that The performing data verification on the received target transmission file based on the data length and the accumulated checksum includes: When m bytes of the target transmission file are received, a current length and a current checksum corresponding to the m bytes are calculated, where m is a preset integer; Determine whether the current length matches the data length, and determine whether the current checksum matches the accumulated checksum; wherein: If the current length matches the data length, and the current checksum matches the accumulated checksum, it is determined that the target transmission file passes the data check.

8. A satellite-borne software reconstruction device, characterized in that: Applied to a satellite system, the satellite system corresponds to at least one computing node of a processing planning computer in a satellite, each computing node is used to process a corresponding type of file, and the device comprises: A software compression module is used to obtain an original file of the target onboard software, encode and compress the original file, and obtain a target transmission file, wherein the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file; A file transmission module, configured to send the target transmission file to the processing planning computer, trigger the processing planning computer to select a target computing node associated with the file type from the at least one computing node, and store the target transmission file in the target computing node, and during the storage process: perform data verification on the received target transmission file based on the data length and the accumulated checksum; An instruction reconstruction module is used to send a reconstruction instruction to the processing planning computer, trigger the processing planning computer to decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

9. A satellite-borne software reconstruction device, characterized in that: A processing planning computer having at least one computing node in a satellite, the processing planning computer corresponding to the satellite system, each computing node being used to process a corresponding type of file, the device comprising: A file receiving module is used to receive a target transmission file sent by the satellite system, wherein the target transmission file is obtained by the satellite system encoding and compressing an original file of the target onboard software, and the target transmission file at least includes: a file type of the original file, a target storage address of the original file, a data length of the original file, and an accumulated checksum of the original file; A node storage module, configured to select a target computing node associated with the file type from the at least one computing node, and store the target transmission file in the target computing node, and during the storage process: perform data verification on the received target transmission file based on the data length and the accumulated checksum; The software reconstruction module is used to respond to the reconstruction instruction sent by the satellite system, decompress the target transmission file, obtain the original file, and reconstruct the target computing node based on the original file.

10. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores instructions, and when the instructions are called by the processor, the processor executes the method according to any one of claims 1 to 7.

Images