Satellite constellation-oriented satellite-borne software on-orbit rapid reconstruction method, system and equipment

Abstract

The invention relates to a satellite constellation-oriented satellite-borne software on-orbit rapid reconstruction method, system and equipment. The method comprises the following steps: a ground terminal selects one or more domestic visible satellites as node satellites, sends reconstruction files and list information of satellites to be reconstructed to the node satellites, and uploads reconstruction data frames frame by frame by analyzing reconstruction telemetry information returned by the node satellites; the node satellites send reconstruction start instructions and list information of satellites to be reconstructed to other satellites in the list through inter-satellite links, and notify the other satellites to enter a reconstruction mode; after all the satellites enter the reconstruction mode, mutually sending reconstruction telemetry information of the satellites, processing the reconstruction telemetry information sent by the satellites of the opposite side, autonomously supplementing the missing reconstruction data frames of the satellites of the opposite side, and carrying out multiple rounds of verification on the received data frames; and after reconstruction of all satellites is completed, the ground end sends a reconstruction ending instruction to the node satellites, and reconstruction is ended. According to the method, efficient reconstruction of massive satellite low-orbit constellations can be realized.

Description

Technical Field

[0001] The present application relates to the technical field of spacecraft software reconstruction, and in particular to a method, system and device for rapid on-orbit reconstruction of on-board software for satellite constellations. Background Art

[0002] In recent years, low-orbit constellations represented by the Starlink constellation have driven a global upsurge in the construction of low-orbit satellite constellations. Low-orbit satellite constellations have shown many disruptive characteristics and trends in terms of mass development, rapid deployment, and application services, greatly innovating and reshaping the overall landscape of satellite communications, navigation, remote sensing, and other fields. my country is also actively building low-orbit constellations. However, due to the low orbital altitude of low-orbit satellites, multiple satellites must be deployed to achieve full coverage of the earth. Therefore, the number of satellites in a low-orbit constellation is often hundreds or thousands, and the massive number of satellites poses a great challenge to the maintenance and upgrade of low-orbit constellations.

[0003] Most traditional spacecraft have the function of software reconstruction on orbit, which can be completed by re-constructing the program on the ground. Traditional reconstruction methods mostly adopt the method of single satellite injection and single satellite reconstruction. For giant low-orbit constellations containing a large number of satellites, the reconstruction workload increases exponentially. Traditional reconstruction methods are difficult to meet the rapid reconstruction requirements of giant low-orbit constellations. Summary of the invention

[0004] Based on this, it is necessary to provide a method, system and equipment for rapid on-orbit reconstruction of on-board software for satellite constellations in response to the above-mentioned technical problems, so as to achieve efficient reconstruction of massive low-orbit satellite constellations.

[0005] A method for rapid on-orbit reconstruction of onboard software for a satellite constellation, the method comprising: Step 1: Generate a reconstruction file and a list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items; wherein the reconstruction file includes an executable file and configuration parameters of all satellites to be reconstructed; Step 2: The ground terminal selects one or more visible satellites in the territory as node satellites, and sends a reconstruction start instruction and a list of satellites to be reconstructed to the node satellites; Step 3: After receiving the reconstruction start command, the node satellite enters the reconstruction mode, saves the list of satellites to be reconstructed locally, and then transmits the reconstruction telemetry information of the satellite back to the ground end; Step 4: The ground end analyzes the reconstructed telemetry information sent back by the node satellite, and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames; Step 5, after entering the reconstruction mode and collecting all the reconstruction data frames, the node satellite communicates with other satellites through the intersatellite link, and obtains the satellite to be reconstructed in the list with a reconstruction label that needs to be reconstructed by querying the locally stored list of satellites to be reconstructed, and notifies the satellite to be reconstructed to enter the reconstruction mode and update its reconstruction label to being reconstructed by sending a reconstruction start instruction and the list of satellites to be reconstructed. The satellite to be reconstructed that enters the reconstruction mode also notifies other satellites to be reconstructed in the list with a reconstruction label that needs to be reconstructed to enter the reconstruction mode by querying the locally stored list of satellites to be reconstructed, and sending a reconstruction start instruction and the list of satellites to be reconstructed information, until all the satellites to be reconstructed in the list enter the reconstruction mode; Step 6: After the node satellite and all the satellites to be reconstructed in the list enter the reconstruction mode, the satellites communicate with each other through the intersatellite link, and each satellite informs each other of the reconstruction status of the satellite by sending the reconstruction telemetry information of the satellite to each other, and determines whether the other satellite has received all the reconstructed data frames by parsing the reconstruction telemetry information sent by the other satellite. If not, further determine whether there are any reconstructed data frames not received by the other satellite stored locally. If so, send the reconstructed data frame to the other satellite until the other satellite has received all the reconstructed data frames; otherwise, no processing is performed; Step 7, each satellite verifies the received reconstructed data frames, caches the reconstructed data frames that pass the verification in the local cache area, and packs the frame number of the locally cached reconstructed data frames, the total number of received reconstructed data frames, and the minimum frame number of the missing reconstructed data frames into the reconstructed telemetry information of the satellite; Step 8, after all the satellites to be reconstructed in the list have collected all the reconstructed data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on all the reconstructed data frames cached locally. If the overall check passes, the executable file in the reconstruction file and the configuration parameters corresponding to the satellite are stored and read back for verification. If the read back verification passes, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction correct; if the read back verification or the overall verification fails, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction error; Step 9, when each satellite receives the reconstructed telemetry information of the other satellite and the reconstruction status thereof is correct, it updates the locally stored list of satellites to be reconstructed, updates the reconstruction tag of the other satellite in the list to completed reconstruction, and subsequently stops sending the reconstructed telemetry information of the satellite to the other satellite; Step 10: After the reconstruction tags of all satellites to be reconstructed in the list are updated to complete reconstruction, the ground end sends a reconstruction end instruction to the node satellite, and the node satellite traverses and forwards the reconstruction end instruction to all satellites to be reconstructed in the list through the intersatellite link. All satellites to be reconstructed and the node satellite exit the reconstruction mode, and the reconstruction is completed.

[0006] In one embodiment, generating a reconstruction file and a list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items includes: The ground terminal or the satellite itself generates an executable file of the onboard software configuration item according to the satellite to be reconstructed and the corresponding onboard software configuration item, and obtains the reconstruction file by splicing the executable file with the configuration parameters of all the satellites to be reconstructed; The ground terminal or the satellite itself generates a list of satellites to be reconstructed according to the serial numbers of the satellites to be reconstructed and the corresponding reconstruction tags; wherein the reconstruction tags include no need for reconstruction, need for reconstruction, being reconstructed, and completed reconstruction.

[0007] In one embodiment, the ground terminal selects one or more satellites visible in the territory as node satellites, and sends a reconstruction start instruction and a list of satellites to be reconstructed to the node satellites, including: The ground end selects one or more domestic visible satellites as node satellites, and determines whether the node satellite is in the list of satellites to be reconstructed. If so, the reconstruction start instruction and the list of satellites to be reconstructed are sent to the node satellite; otherwise, one or more domestic visible satellites in the list of satellites to be reconstructed are reselected as node satellites; wherein, the reconstruction start instruction is divided into the whole-network satellite reconstruction start instruction and the partial satellite reconstruction start instruction, and the whole-network satellite reconstruction start instruction includes the whole-network reconstruction start enable flag, the code of the configuration item to be reconstructed, the version number of the configuration item to be reconstructed, the total number of reconstruction data frames of the configuration item to be reconstructed, and the total checksum of the program.

[0008] In one embodiment, the ground end analyzes the reconstructed telemetry information sent back by the node satellite and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames, including: The reconstructed telemetry information of each satellite includes the satellite number, the reconstruction configuration item code, the reconstruction configuration item version number, the reconstruction status, the total number of reconstructed data frames received, and the minimum frame number of the missing reconstructed data frames. The reconstruction status includes not reconstructed, reconstruction started, reconstruction correct, and reconstruction error. The ground end parses the reconstruction state and the total number of reconstructed data frames received in the reconstruction telemetry information sent back by the node satellite. If the reconstruction state of the node satellite is not reconstructed, continue to send the reconstruction start command to the node satellite; otherwise, further judge whether the node satellite has received all the reconstructed data frames according to the total number of reconstructed data frames received in the reconstruction telemetry information. If not, upload the reconstructed data frames to the node satellite frame by frame; if all are received, stop uploading; wherein, the reconstructed data frame includes the frame number of the reconstructed data frame, the reconstruction configuration item code, the reconstruction configuration item version number and the reconstruction valid data; If the ground terminal sends the set number of reconstruction start commands to the node satellite continuously, but the reconstruction status of the node satellite is still not reconstructed, other visible satellites in the country in the list of satellites to be reconstructed are replaced as new node satellites; If the node satellite leaves the country or becomes unavailable during the reconstruction of the data frame on the ground end, other visible satellites in the country in the list of satellites to be reconstructed will be replaced as new node satellites, and the reconstruction data frames will be retransmitted to the new node satellite until all the reconstructed data frames are injected.

[0009] In one embodiment, by parsing the reconstructed telemetry information sent by the other party's satellite, determining whether the other party's satellite has received all the reconstructed data frames includes: By parsing the total number of reconstructed data frames received in the reconstructed telemetry information sent by the other satellite, it is determined whether the other satellite has received all the reconstructed data frames. If not, it is further determined whether the local stores the minimum frame number of the missing reconstructed data frame in the reconstructed telemetry information sent by the other satellite. If so, it is sent to the other satellite; otherwise, no processing is performed.

[0010] In one embodiment, the overall verification and readback verification include: After receiving all the reconstructed data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on the executable files in all the reconstructed data frames in the local cache and the configuration parameters corresponding to the satellite, compares the checksum of the executable file with the total checksum of the program in the reconstruction start instruction, and compares the checksum of the configuration parameters corresponding to the satellite with the checksum of the configuration parameters in the reconstruction file. If the two comparison results are consistent, it means that the overall check is passed, and the executable file and the configuration parameters corresponding to the satellite are written into the non-volatile memory; otherwise, it means that the overall check fails, and the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction error; After the executable file and the configuration parameters corresponding to the satellite are written into the non-volatile memory, the data is read back from the non-volatile memory and verified. The checksum of the executable file is compared with the total checksum of the program in the reconstruction start instruction, and the checksum of the configuration parameters corresponding to the satellite is compared with the checksum of the configuration parameters in the reconstruction file. If the two comparison results are consistent, it means that the read-back verification is passed, and the reconstruction status in the reconstruction telemetry information of the satellite is updated to reconstruction correct; otherwise, it means that the read-back verification fails, and the reconstruction status in the reconstruction telemetry information of the satellite is updated to reconstruction error.

[0011] In one of the embodiments, for a satellite to be reconstructed whose reconstruction status in the reconstructed telemetry information is a reconstruction error, the ground end resends a reconstruction start command to the satellite to be reconstructed when it enters the next time, and the satellite to be reconstructed re-enters the reconstruction mode and applies to obtain reconstruction data frames from other satellites to be reconstructed.

[0012] In one of the embodiments, the method also includes: when each satellite to be reconstructed enters the reconstruction mode and enters into communication with the ground end, the reconstruction telemetry information of the satellite is transmitted back to the ground end, and the ground end grasps the reconstruction progress in real time by analyzing the reconstruction telemetry information of each satellite to be reconstructed.

[0013] A system for rapid on-orbit reconstruction of on-board software for a satellite constellation, the system being used to execute the above-mentioned method for rapid on-orbit reconstruction of on-board software for a satellite constellation, the system comprising: a ground terminal, one or more node satellites visible within the territory selected by the ground terminal, and a plurality of satellites to be reconstructed, wherein the satellites communicate with each other via inter-satellite links.

[0014] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented: Step 1: Generate a reconstruction file and a list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items; wherein the reconstruction file includes an executable file and configuration parameters of all satellites to be reconstructed; Step 2: The ground terminal selects one or more visible satellites in the territory as node satellites, and sends a reconstruction start instruction and a list of satellites to be reconstructed to the node satellites; Step 3: After receiving the reconstruction start command, the node satellite enters the reconstruction mode, saves the list of satellites to be reconstructed locally, and then transmits the reconstruction telemetry information of the satellite back to the ground end; Step 4: The ground end analyzes the reconstructed telemetry information sent back by the node satellite, and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames; Step 5, after entering the reconstruction mode and collecting all the reconstruction data frames, the node satellite communicates with other satellites through the intersatellite link, and obtains the satellite to be reconstructed in the list with a reconstruction label that needs to be reconstructed by querying the locally stored list of satellites to be reconstructed, and notifies the satellite to be reconstructed to enter the reconstruction mode and update its reconstruction label to being reconstructed by sending a reconstruction start instruction and the list of satellites to be reconstructed. The satellite to be reconstructed that enters the reconstruction mode also notifies other satellites to be reconstructed in the list with a reconstruction label that needs to be reconstructed to enter the reconstruction mode by querying the locally stored list of satellites to be reconstructed, and sending a reconstruction start instruction and the list of satellites to be reconstructed information, until all the satellites to be reconstructed in the list enter the reconstruction mode; Step 6: After the node satellite and all the satellites to be reconstructed in the list enter the reconstruction mode, the satellites communicate with each other through the intersatellite link, and each satellite informs each other of the reconstruction status of the satellite by sending the reconstruction telemetry information of the satellite to each other, and determines whether the other satellite has received all the reconstructed data frames by parsing the reconstruction telemetry information sent by the other satellite. If not, further determine whether there are any reconstructed data frames not received by the other satellite stored locally. If so, send the reconstructed data frame to the other satellite until the other satellite has received all the reconstructed data frames; otherwise, no processing is performed; Step 7, each satellite verifies the received reconstructed data frames, caches the reconstructed data frames that pass the verification in the local cache area, and packs the frame number of the locally cached reconstructed data frames, the total number of received reconstructed data frames, and the minimum frame number of the missing reconstructed data frames into the reconstructed telemetry information of the satellite; Step 8, after all the satellites to be reconstructed in the list have collected all the reconstructed data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on all the reconstructed data frames cached locally. If the overall check passes, the executable file in the reconstruction file and the configuration parameters corresponding to the satellite are stored and read back for verification. If the read back verification passes, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction correct; if the read back verification or the overall verification fails, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction error; Step 9, when each satellite receives the reconstructed telemetry information of the other satellite and the reconstruction status thereof is correct, it updates the locally stored list of satellites to be reconstructed, updates the reconstruction tag of the other satellite in the list to completed reconstruction, and subsequently stops sending the reconstructed telemetry information of the satellite to the other satellite; Step 10: After the reconstruction tags of all satellites to be reconstructed in the list are updated to complete reconstruction, the ground end sends a reconstruction end instruction to the node satellite, and the node satellite traverses and forwards the reconstruction end instruction to all satellites to be reconstructed in the list through the intersatellite link. All satellites to be reconstructed and the node satellite exit the reconstruction mode, and the reconstruction is completed.

[0015] Compared with the existing reconstruction methods, the above-mentioned on-orbit rapid reconstruction method, system and device for satellite constellation-oriented on-board software have the following beneficial effects: 1. Reconstruct the entire network of satellites or part of the satellites through intersatellite links. The ground end only needs to inject the reconstruction file once, avoiding the need to inject the reconstruction file for each satellite one by one, effectively reducing the workload of the ground end. And by splicing the configuration parameters of multiple satellites to be reconstructed into one reconstruction file, the ground end does not need to send the configuration parameters to each satellite to be reconstructed separately, reducing the workload of ground operations.

[0016] 2. When uploading the reconstructed file on the ground side, there is no need to select a specific satellite. As long as it is visible within the territory, it can be injected. In addition, the node satellite can be replaced during the injection process, and it is no longer limited by the curvature of a single satellite. When replacing the node satellite, the breakpoint resume method can be used to continue the injection. There is no need to repeatedly inject the injected reconstructed data frame, which reduces the requirements on the ground side.

[0017] 3. When a satellite to be reconstructed misses a frame, there is no need for the ground end to supplement the frame. The other satellites to be reconstructed in the constellation can autonomously send the missing reconstructed data frame to the satellite by parsing the minimum frame number of the missing reconstructed data frame in the reconstructed telemetry information of the satellite, thus avoiding the sending of duplicate frames, effectively utilizing the bandwidth of the inter-satellite link, reducing the reconstruction workload, and improving the reconstruction efficiency of the entire network.

[0018] 4. When a reconstruction error occurs in a satellite to be reconstructed, the ground end only needs to re-inject the reconstruction start command into it. The satellite can autonomously apply for reconstruction data frames from other satellites in the constellation until the reconstruction process is completed. There is no need for the ground end to upload the reconstruction file again, which further improves the reconstruction efficiency.

[0019] 5. Each satellite to be reconstructed performs three rounds of verification on the received reconstructed data frames. The first round of frame-by-frame verification can ensure that all reconstructed data frames are received. The second round of overall verification can ensure whether all reconstructed data frames cached locally are correct. The third round of reconstruction verification can ensure the correctness and integrity of the stored data and ensure the successful reconstruction of each satellite. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a flowchart of a method for rapid on-orbit reconstruction of onboard software for a satellite constellation in one embodiment; Figure 2 A schematic diagram of the composition of a reconstructed file in one embodiment; Figure 3 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0022] In one embodiment, Figure 1 As shown, a method for rapid on-orbit reconstruction of onboard software for a satellite constellation is provided, comprising the following steps: Step 1: Generate a reconstruction file and a list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items; wherein the reconstruction file includes an executable file and configuration parameters of all satellites to be reconstructed.

[0023] Specifically, step 1 includes: The ground end or the satellite itself generates the executable file of the onboard software configuration item according to the satellite to be reconstructed and the corresponding onboard software configuration item. Considering that different satellites have different parameters, the reconstruction file also includes the satellite ID to be reconstructed and the corresponding configuration parameters. Considering that the configuration parameters of a single satellite are limited, Figure 2 As shown in the figure, the configuration parameters of multiple satellites to be reconstructed are spliced ​​into one reconstruction file. Figure 2 Where N is the number of satellites to be reconstructed.

[0024] By splicing the configuration parameters of multiple satellites to be reconstructed into one reconstruction file, the ground end no longer needs to send configuration parameters to each satellite to be reconstructed separately, reducing the ground operation workload. This method is not only applicable to the case where the configuration items of each satellite to be reconstructed are exactly the same, but also to the case where the executable files are the same but the configuration parameters are different.

[0025] The ground terminal or the satellite itself further generates the satellite list information to be reconstructed according to the serial number of the satellite to be reconstructed and the corresponding reconstruction tag; wherein the reconstruction tag includes no need for reconstruction, need for reconstruction, being reconstructed and completed reconstruction. The content of the satellite list information to be reconstructed is shown in Table 1.

[0026] Table 1 Satellite list information to be reconstructed

[0027] Step 2: The ground terminal selects one or more visible satellites in the territory as node satellites, and sends the reconstruction start instruction and the list of satellites to be reconstructed to the node satellites.

[0028] Specifically, step 2 includes: The ground terminal selects one or more satellites visible in the country as node satellites, and determines whether the node satellite is in the list of satellites to be reconstructed. If so, the reconstruction start instruction and the list of satellites to be reconstructed are sent to the node satellite; otherwise, one or more satellites visible in the country in the list of satellites to be reconstructed are reselected as node satellites. The selection of node satellites makes it unnecessary to select specific satellites when reconstructing files on the ground terminal. As long as they are visible in the country, they can be injected, and multiple node satellites are no longer limited by the arc of a single satellite.

[0029] Among them, the reconstruction start command is divided into the whole network satellite reconstruction start command and the partial satellite reconstruction start command, which can realize the reconstruction of the whole network satellite or partial satellite. The content of the whole network satellite reconstruction start command is shown in Table 2, including the whole network reconstruction start enable flag, the code of the configuration item to be reconstructed, the version number of the configuration item to be reconstructed, the total number of reconstruction data frames of the configuration item to be reconstructed, and the total checksum of the program.

[0030] Table 2: Network-wide satellite reconstruction start command

[0031] Step 3: After receiving the reconstruction start command, the node satellite enters the reconstruction mode, saves the list of satellites to be reconstructed locally, and then transmits the reconstruction telemetry information of the satellite back to the ground end.

[0032] Specifically, in step 3, after receiving the reconstruction start instruction, the node satellite enters the reconstruction mode and updates the reconstruction state in the reconstruction telemetry information of the satellite to the reconstruction start. Among them, the node satellite communicates with the satellite to be reconstructed in the satellite list to be reconstructed through the intersatellite link, or the satellites to be reconstructed in the satellite list to be reconstructed communicate with each other through the intersatellite link. The content of the reconstruction telemetry information of each satellite is shown in Table 3, including the satellite number of the satellite, the reconstruction configuration item code, the reconstruction configuration item version number, the reconstruction state, the total number of reconstructed data frames received, and the minimum frame number of the missing reconstructed data frame. The reconstruction state includes not reconstructed, reconstruction started, reconstruction correct and reconstruction error.

[0033] Table 3 Reconstructed telemetry information

[0034] Step 4: The ground end analyzes the reconstructed telemetry information sent back by the node satellite, and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames.

[0035] Specifically, step 4 includes: the ground end analyzes the reconstruction state and the total number of reconstructed data frames received in the reconstruction telemetry information sent back by the node satellite. If the reconstruction state of the node satellite is not reconstructed, continue to send the reconstruction start command to the node satellite; otherwise, further judge whether the node satellite has received all the reconstructed data frames according to the total number of reconstructed data frames received in the reconstruction telemetry information. If not, upload the reconstructed data frames to the node satellite frame by frame; if all are received, stop uploading. Based on this step, the ground end only needs to upload the reconstruction file once, avoiding the ground end from injecting the reconstruction file to each satellite one by one, effectively reducing the workload of the ground end.

[0036] If the ground terminal sends the set number of reconstruction start instructions to the node satellite continuously, but the reconstruction status of the node satellite is still not reconstructed, other domestic visible satellites in the list of satellites to be reconstructed are replaced as new node satellites.

[0037] If the node satellite leaves the country or becomes unavailable during the reconstructed data frame on the ground side, other visible satellites in the country in the list of satellites to be reconstructed are replaced as new node satellites, and the reconstructed data frames are retransmitted breakpoint to the new node satellite until all reconstructed data frames are injected. The retransmission breakpoint method can ensure the continuous injection of reconstructed data frames, without the need to repeatedly inject the injected reconstructed data frames, thus reducing the requirements on the ground side.

[0038] The content of the reconstructed data frame is shown in Table 4, including the frame number of the reconstructed data frame, the reconstructed configuration item code, the reconstructed configuration item version number and the reconstructed valid data.

[0039] Table 4 Reconstructed data frame

[0040] Step 5: After entering the reconstruction mode and collecting all the reconstruction data frames, the node satellite communicates with other satellites through the intersatellite link, and obtains the satellites to be reconstructed in the list with the reconstruction label as needing to be reconstructed by querying the locally stored list of satellites to be reconstructed, and notifies the satellite to be reconstructed to enter the reconstruction mode and update its reconstruction label as being reconstructed by sending a reconstruction start instruction and the list of satellites to be reconstructed. The satellite to be reconstructed that enters the reconstruction mode also notifies other satellites to be reconstructed in the list with the reconstruction label as needing to be reconstructed to enter the reconstruction mode by querying the locally stored list of satellites to be reconstructed, and sending a reconstruction start instruction and the list of satellites to be reconstructed information, until all the satellites to be reconstructed in the list enter the reconstruction mode.

[0041] Specifically, in step 5, if the locally stored list information of satellites to be reconstructed is queried, and the reconstruction tag of the satellite to be reconstructed is that reconstruction is not required, reconstruction has been completed, or is being reconstructed, no processing is performed; only when the reconstruction tag is that reconstruction is required, a reconstruction start instruction and the list information of satellites to be reconstructed are sent to the satellite to be reconstructed, and the satellite to be reconstructed is notified to enter the reconstruction mode and update its reconstruction tag to be reconstructed.

[0042] Furthermore, when each satellite to be reconstructed enters the reconstruction mode and communicates with the ground end, it transmits the reconstruction telemetry information of the satellite to the ground end. The ground end understands the reconstruction progress in real time by analyzing the reconstruction telemetry information of each satellite to be reconstructed.

[0043] Step 6: After the node satellite and all the satellites to be reconstructed in the list enter the reconstruction mode, the satellites communicate with each other through inter-satellite links, and each satellite informs each other of the reconstruction status of its own satellite by sending its own reconstruction telemetry information to each other, and determines whether the other satellite has received all the reconstructed data frames by parsing the reconstruction telemetry information sent by the other satellite. If not, further determine whether there are any reconstructed data frames that have not been received by the other satellite stored locally. If so, send the reconstructed data frame to the other satellite until the other satellite has received all the reconstructed data frames; otherwise, no processing is performed.

[0044] Specifically, in step 5 and step 6, before sending the reconstruction start instruction or the list information of satellites to be reconstructed or the reconstruction telemetry information to other satellites, the satellite first determines whether the currently communicating satellite is in the list of satellites to be reconstructed. It sends the information only when the other satellite is in the list, otherwise it does not send the information.

[0045] Specifically, in step 6, by parsing the reconstructed telemetry information sent by the other party's satellite, it is determined whether the other party's satellite has received all the reconstructed data frames, including: by parsing the total number of reconstructed data frames received in the reconstructed telemetry information sent by the other party's satellite, it is determined whether the other party's satellite has received all the reconstructed data frames; if not, it is further determined whether the local stores the minimum frame number of the missing reconstructed data frame in the reconstructed telemetry information sent by the other party's satellite; if so, it is sent to the other party's satellite; otherwise, no processing is performed.

[0046] Based on this step, when a satellite to be reconstructed misses a frame, there is no need for the ground end to supplement the frame. Other satellites to be reconstructed in the constellation can autonomously send the missing reconstructed data frame to the satellite by parsing the minimum frame number of the reconstructed data frame missing in the reconstructed telemetry information of the satellite, thereby avoiding the sending of duplicate frames, effectively utilizing the bandwidth of the inter-satellite link, reducing the reconstruction workload, and improving the reconstruction efficiency of the entire network.

[0047] Step 7, each satellite verifies the received reconstructed data frames, caches the reconstructed data frames that pass the verification into the local cache area, and packages the frame number of the locally cached reconstructed data frames, the total number of reconstructed data frames received, and the minimum frame number of the missing reconstructed data frames into the reconstructed telemetry information of the satellite.

[0048] Furthermore, if the currently received reconstructed data frame is a duplicate frame, the new reconstructed data frame is used to overwrite the original reconstructed data frame in the cache.

[0049] Step 8: After all the satellites to be reconstructed in the list have received all the reconstructed data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on all the reconstructed data frames cached locally. If the overall check passes, the executable file in the reconstruction file and the configuration parameters corresponding to the satellite are stored and a read-back check is performed. If the read-back check passes, the reconstruction status in the reconstructed telemetry information of the satellite is updated to reconstruction correct; if the read-back check or the overall check fails, the reconstruction status in the reconstructed telemetry information of the satellite is updated to reconstruction error.

[0050] Specifically, the overall verification in step 8 includes: after each satellite to be reconstructed has collected all the reconstructed data frames of the reconstruction file, it performs an overall verification on the executable files in all the reconstructed data frames in the local cache and the configuration parameters corresponding to the satellite, compares the checksum of the executable file with the total checksum of the program in the reconstruction start instruction, and compares the checksum of the configuration parameters corresponding to the satellite with the checksum of the configuration parameters in the reconstruction file. If the two comparison results are consistent, it means that the overall verification is passed, and the executable file and the configuration parameters corresponding to the satellite are written into the non-volatile memory; otherwise, it means that the overall verification fails, and the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction error.

[0051] Specifically, the read-back verification in step 8 includes: after the executable file and the configuration parameters corresponding to the satellite are written into the non-volatile memory, the data is read back from the non-volatile memory and verified, the checksum of the executable file is compared with the total program checksum in the reconstruction start instruction, and the checksum of the configuration parameters corresponding to the satellite is compared with the checksum of the configuration parameters in the reconstruction file. If the two comparison results are consistent, it means that the read-back verification is passed, and the reconstruction status in the reconstruction telemetry information of the satellite is updated to reconstruction correct; otherwise, it means that the read-back verification fails, and the reconstruction status in the reconstruction telemetry information of the satellite is updated to reconstruction error.

[0052] By performing multiple rounds of verification on the reconstructed data frames, it can be ensured that each satellite has received all the reconstructed data frames, and the integrity and correctness of the stored data can be ensured, thereby ensuring the correctness of the reconstruction of each satellite.

[0053] Furthermore, for a satellite to be reconstructed whose reconstruction status in the reconstructed telemetry information is a reconstruction error, the ground terminal resends a reconstruction start command to the satellite to be reconstructed when it enters the next time, and the satellite to be reconstructed re-enters the reconstruction mode and applies for reconstructed data frames from other satellites to be reconstructed. There is no need for the ground terminal to upload the reconstruction file again, which further improves the reconstruction efficiency.

[0054] Step 9: When each satellite receives the reconstructed telemetry information from the other satellite and the reconstruction status is correct, it updates the locally stored list of satellites to be reconstructed, updates the reconstruction tag of the other satellite in the list to completed reconstruction, and subsequently stops sending the reconstructed telemetry information of the satellite to the other satellite.

[0055] Step 10: After the reconstruction tags of all satellites to be reconstructed in the list are updated to complete reconstruction, the ground end sends a reconstruction end instruction to the node satellite, and the node satellite traverses and forwards the reconstruction end instruction to all satellites to be reconstructed in the list through the intersatellite link. All satellites to be reconstructed and the node satellite exit the reconstruction mode, and the reconstruction is completed.

[0056] Among them, the reconstruction end instruction also includes the whole-network satellite reconstruction end instruction and the partial satellite reconstruction end instruction. The content of the whole-network satellite reconstruction end instruction is shown in Table 5, including the whole-network reconstruction end enable flag, the code of the configuration item to be reconstructed and the version number of the configuration item to be reconstructed.

[0057] Table 5: Whole network satellite reconstruction end command

[0058] In one embodiment, a system for rapid on-orbit reconstruction of on-board software for a satellite constellation is provided. The system is used to execute the above-mentioned method for rapid on-orbit reconstruction of on-board software for a satellite constellation. The system includes: a ground terminal, one or more node satellites visible within the territory selected by the ground terminal, and several satellites to be reconstructed, and the satellites communicate with each other through inter-satellite links.

[0059] For specific limitations on the on-orbit rapid reconstruction system of on-board software for satellite constellations, please refer to the limitations on the on-orbit rapid reconstruction method of on-board software for satellite constellations mentioned above, which will not be repeated here.

[0060] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 3As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for rapid on-orbit reconstruction of satellite-borne software for a satellite constellation is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0061] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0062] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented: Step 1: Generate a reconstruction file and a list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items; wherein the reconstruction file includes an executable file and configuration parameters of all satellites to be reconstructed; Step 2: The ground terminal selects one or more visible satellites in the territory as node satellites, and sends a reconstruction start instruction and a list of satellites to be reconstructed to the node satellites; Step 3: After receiving the reconstruction start command, the node satellite enters the reconstruction mode, saves the list of satellites to be reconstructed locally, and then transmits the reconstruction telemetry information of the satellite back to the ground end; Step 4: The ground end analyzes the reconstructed telemetry information sent back by the node satellite, and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames; Step 5, after entering the reconstruction mode and collecting all the reconstruction data frames, the node satellite communicates with other satellites through the intersatellite link, and obtains the satellite to be reconstructed in the list with a reconstruction label that needs to be reconstructed by querying the locally stored list of satellites to be reconstructed, and notifies the satellite to be reconstructed to enter the reconstruction mode and update its reconstruction label to being reconstructed by sending a reconstruction start instruction and the list of satellites to be reconstructed. The satellite to be reconstructed that enters the reconstruction mode also notifies other satellites to be reconstructed in the list with a reconstruction label that needs to be reconstructed to enter the reconstruction mode by querying the locally stored list of satellites to be reconstructed, and sending a reconstruction start instruction and the list of satellites to be reconstructed information, until all the satellites to be reconstructed in the list enter the reconstruction mode; Step 6: After the node satellite and all the satellites to be reconstructed in the list enter the reconstruction mode, the satellites communicate with each other through the intersatellite link, and each satellite informs each other of the reconstruction status of the satellite by sending the reconstruction telemetry information of the satellite to each other, and determines whether the other satellite has received all the reconstructed data frames by parsing the reconstruction telemetry information sent by the other satellite. If not, further determine whether there are any reconstructed data frames not received by the other satellite stored locally. If so, send the reconstructed data frame to the other satellite until the other satellite has received all the reconstructed data frames; otherwise, no processing is performed; Step 7, each satellite verifies the received reconstructed data frames, caches the reconstructed data frames that pass the verification in the local cache area, and packs the frame number of the locally cached reconstructed data frames, the total number of received reconstructed data frames, and the minimum frame number of the missing reconstructed data frames into the reconstructed telemetry information of the satellite; Step 8, after all the satellites to be reconstructed in the list have collected all the reconstructed data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on all the reconstructed data frames cached locally. If the overall check passes, the executable file in the reconstruction file and the configuration parameters corresponding to the satellite are stored and read back for verification. If the read back verification passes, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction correct; if the read back verification or the overall verification fails, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction error; Step 9, when each satellite receives the reconstructed telemetry information of the other satellite and the reconstruction status thereof is correct, it updates the locally stored list of satellites to be reconstructed, updates the reconstruction tag of the other satellite in the list to completed reconstruction, and subsequently stops sending the reconstructed telemetry information of the satellite to the other satellite; Step 10: After the reconstruction tags of all satellites to be reconstructed in the list are updated to complete reconstruction, the ground end sends a reconstruction end instruction to the node satellite, and the node satellite traverses and forwards the reconstruction end instruction to all satellites to be reconstructed in the list through the intersatellite link. All satellites to be reconstructed and the node satellite exit the reconstruction mode, and the reconstruction is completed.

[0063] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0064] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for rapid on-orbit reconstruction of satellite-borne software for a satellite constellation, characterized in that: The method comprises: Step 1, generating a reconstruction file and a list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items; wherein the reconstruction file includes an executable file and configuration parameters of all satellites to be reconstructed; Step 2: The ground terminal selects one or more visible satellites in the territory as node satellites, and sends a reconstruction start instruction and a list of satellites to be reconstructed to the node satellites; Step 3, after receiving the reconstruction start instruction, the node satellite enters the reconstruction mode, saves the list information of the satellites to be reconstructed locally, and then transmits the reconstruction telemetry information of the satellite back to the ground end; Step 4: The ground end analyzes the reconstructed telemetry information sent back by the node satellite, and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames; Step 5, after entering the reconstruction mode and collecting all the reconstruction data frames, the node satellite communicates with other satellites through the intersatellite link, and obtains the satellite to be reconstructed in the list with a reconstruction label that needs to be reconstructed by querying the locally stored list of satellites to be reconstructed, and notifies the satellite to be reconstructed to enter the reconstruction mode and update its reconstruction label to being reconstructed by sending the reconstruction start instruction and the list of satellites to be reconstructed. The satellite to be reconstructed that enters the reconstruction mode also notifies other satellites to be reconstructed in the list with a reconstruction label that needs to be reconstructed to enter the reconstruction mode by querying the locally stored list of satellites to be reconstructed, and sending the reconstruction start instruction and the list of satellites to be reconstructed information, until all the satellites to be reconstructed in the list enter the reconstruction mode; Step 6: After the node satellite and all the satellites to be reconstructed in the list enter the reconstruction mode, the satellites communicate with each other through the intersatellite link, and each satellite informs each other of the reconstruction status of the satellite by sending the reconstruction telemetry information of the satellite to each other, and determines whether the other satellite has received all the reconstructed data frames by parsing the reconstruction telemetry information sent by the other satellite. If not, further determine whether there are any reconstructed data frames not received by the other satellite stored locally. If so, send the reconstructed data frame to the other satellite until the other satellite has received all the reconstructed data frames; otherwise, no processing is performed; Step 7, each satellite verifies the received reconstructed data frames, caches the reconstructed data frames that pass the verification in the local cache area, and packs the frame number of the locally cached reconstructed data frames, the total number of received reconstructed data frames, and the minimum frame number of the missing reconstructed data frames into the reconstructed telemetry information of the satellite; Step 8, after all the satellites to be reconstructed in the list have collected all the reconstructed data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on all the reconstructed data frames cached locally. If the overall check passes, the executable file in the reconstruction file and the configuration parameters corresponding to the satellite are stored and read back for verification. If the read back verification passes, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction correct; if the read back verification or the overall verification fails, the reconstruction state in the reconstructed telemetry information of the satellite is updated to reconstruction error; Step 9, when each satellite receives the reconstructed telemetry information of the other satellite and the reconstruction status thereof is correct, it updates the locally stored list of satellites to be reconstructed, updates the reconstruction tag of the other satellite in the list to completed reconstruction, and subsequently stops sending the reconstructed telemetry information of the satellite to the other satellite; Step 10: After the reconstruction tags of all satellites to be reconstructed in the list are updated to complete reconstruction, the ground end sends a reconstruction end instruction to the node satellite, and the node satellite traverses and forwards the reconstruction end instruction to all satellites to be reconstructed in the list through the intersatellite link. All satellites to be reconstructed and the node satellite exit the reconstruction mode, and the reconstruction is completed.

2. The method according to claim 1, characterized in that Generate the reconstruction file and the list of satellites to be reconstructed according to the satellites to be reconstructed and the corresponding onboard software configuration items, including: The ground terminal or the satellite itself generates an executable file of the onboard software configuration item according to the satellite to be reconstructed and the corresponding onboard software configuration item, and obtains a reconstruction file by splicing the executable file with the configuration parameters of all the satellites to be reconstructed; The ground terminal or the satellite itself generates a list of satellites to be reconstructed according to the serial numbers of the satellites to be reconstructed and the corresponding reconstruction tags; wherein the reconstruction tags include no need for reconstruction, need for reconstruction, being reconstructed, and completed reconstruction.

3. The method according to claim 1, characterized in that The ground terminal selects one or more visible satellites in the country as node satellites, and sends the reconstruction start instruction and the list of satellites to be reconstructed to the node satellites, including: The ground end selects one or more domestic visible satellites as node satellites, and determines whether the node satellite is in the list of satellites to be reconstructed. If so, a reconstruction start instruction and information of the list of satellites to be reconstructed are sent to the node satellite; otherwise, one or more domestic visible satellites in the list of satellites to be reconstructed are reselected as node satellites; wherein the reconstruction start instruction is divided into a whole-network satellite reconstruction start instruction and a partial satellite reconstruction start instruction, and the whole-network satellite reconstruction start instruction includes a whole-network reconstruction start enable flag, a code of a configuration item to be reconstructed, a version number of the configuration item to be reconstructed, a total number of reconstruction data frames of the configuration item to be reconstructed, and a total program checksum.

4. The method according to claim 1, characterized in that The ground end analyzes the reconstructed telemetry information sent back by the node satellite and uploads the reconstructed data frames of the reconstructed file to the node satellite frame by frame until the node satellite receives all the reconstructed data frames, including: The reconstructed telemetry information of each satellite includes the satellite number, the reconstruction configuration item code, the reconstruction configuration item version number, the reconstruction status, the total number of reconstructed data frames received, and the minimum frame number of the missing reconstructed data frames. The reconstruction status includes not reconstructed, reconstruction started, reconstruction correct, and reconstruction error. The ground end parses the reconstruction state and the total number of reconstructed data frames received in the reconstruction telemetry information sent back by the node satellite. If the reconstruction state of the node satellite is not reconstructed, continue to send the reconstruction start command to the node satellite; otherwise, further judge whether the node satellite has received all the reconstructed data frames according to the total number of reconstructed data frames received in the reconstruction telemetry information. If not, upload the reconstructed data frames to the node satellite frame by frame; if all are received, stop uploading; wherein, the reconstructed data frame includes the frame number of the reconstructed data frame, the reconstruction configuration item code, the reconstruction configuration item version number and the reconstruction valid data; If the ground terminal sends the set number of reconstruction start commands to the node satellite continuously, but the reconstruction status of the node satellite is still not reconstructed, other visible satellites in the country in the list of satellites to be reconstructed are replaced as new node satellites; If the node satellite leaves the country or becomes unavailable during the reconstruction of the data frame on the ground end, other visible satellites in the country in the list of satellites to be reconstructed will be replaced as new node satellites, and the reconstruction data frames will be retransmitted to the new node satellite until all the reconstructed data frames are injected.

5. The method according to claim 1, characterized in that By parsing the reconstructed telemetry information sent by the other satellite, it is determined whether the other satellite has received all the reconstructed data frames, including: By parsing the total number of reconstructed data frames received in the reconstructed telemetry information sent by the other satellite, it is determined whether the other satellite has received all the reconstructed data frames. If not, it is further determined whether the local stores the minimum frame number of the missing reconstructed data frame in the reconstructed telemetry information sent by the other satellite. If so, it is sent to the other satellite; otherwise, no processing is performed.

6. The method according to claim 1, characterized in that The overall verification and read-back verification include: After receiving all the reconstruction data frames of the reconstruction file, each satellite to be reconstructed performs an overall check on the executable files in all the reconstruction data frames cached locally and the configuration parameters corresponding to the satellite, compares the checksum of the executable file with the total checksum of the program in the reconstruction start instruction, and compares the checksum of the configuration parameters corresponding to the satellite with the checksum of the configuration parameters in the reconstruction file. If the two comparison results are consistent, it means that the overall check is passed, and the executable file and the configuration parameters corresponding to the satellite are written into the non-volatile memory; otherwise, it means that the overall check fails, and the reconstruction state in the reconstruction telemetry information of the satellite is updated to reconstruction error; After the executable file and the configuration parameters corresponding to the satellite are written into the non-volatile memory, the data is read back from the non-volatile memory and verified, the checksum of the executable file is compared with the total checksum of the program in the reconstruction start instruction, and the checksum of the configuration parameters corresponding to the satellite is compared with the checksum of the configuration parameters in the reconstruction file. If the two comparison results are consistent, it means that the read-back verification is passed, and the reconstruction status in the reconstruction telemetry information of the satellite is updated to reconstruction correct; otherwise, it means that the read-back verification fails, and the reconstruction status in the reconstruction telemetry information of the satellite is updated to reconstruction error.

7. The method according to claim 1 or 6, characterized in that: For a satellite to be reconstructed whose reconstruction status in the reconstructed telemetry information is reconstruction error, the ground end resends a reconstruction start command to the satellite to be reconstructed when it enters the next time. The satellite to be reconstructed re-enters the reconstruction mode and applies to obtain reconstruction data frames from other satellites to be reconstructed.

8. The method according to claim 1, characterized in that The method also includes: when each satellite to be reconstructed enters the reconstruction mode and enters into communication with the ground end, the reconstruction telemetry information of the satellite is transmitted back to the ground end, and the ground end grasps the reconstruction progress in real time by analyzing the reconstruction telemetry information of each satellite to be reconstructed.

9. An on-orbit rapid reconstruction system for satellite-borne software for satellite constellations, characterized in that: The system is used to execute the on-orbit rapid reconstruction method of satellite-borne software for a satellite constellation as described in any one of claims 1-8, and the system includes: a ground terminal, one or more node satellites visible within the territory selected by the ground terminal, and several satellites to be reconstructed, and the satellites communicate with each other through inter-satellite links.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

Images