Satellite model updating method, computer device and storage medium

Abstract

The present application relates to a satellite model update method, computer equipment and storage medium. It includes: obtaining a lightweight incremental model sent by a ground server; determining whether the lightweight incremental model is a shared model; if so, storing the lightweight incremental model in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network; if not, storing the lightweight incremental model in the private directory of the target satellite. The information in the private directory of the target satellite is not shared with other satellites in the satellite network. The above scheme can improve the efficiency of the onboard model update of each satellite in the satellite network, while improving the stability of the onboard model update.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a satellite model updating method, a computer device and a storage medium. Background Art

[0002] In recent years, satellite launch technology has developed rapidly, the technology of launching multiple satellites with one rocket has gradually matured, the number of satellites in low-Earth orbit has continued to increase, and satellite constellation plans represented by satellite networks have emerged in an endless stream. The communication window between a single satellite and the ground station is short and cannot be connected to the ground for a long time. The satellite network solves this problem well. It uses network communication between satellites to connect each satellite into a network. As long as one satellite is connected to the ground station, other satellites can be connected to the ground through the satellite network. This has greatly promoted the development of satellite technology and is beneficial for satellites to provide better and richer services to the outside world.

[0003] However, on the one hand, with the development of artificial intelligence technology, the models on satellites need to evolve continuously to meet business requirements. However, the computing power of satellites is limited, and the models need to be updated by relying on the powerful computing power and data resources of ground stations. Therefore, the updated models need to be transmitted from the ground to the satellite. On the other hand, if a single satellite is used to transmit and update one by one on the ground, there will be problems of short window period and long time consumption. If a satellite network is used to transmit and update batches of satellites synchronously on the ground at one time, due to the limitations of inter-satellite communication technology, there will be unstable data synchronization between satellites, especially with the development of artificial intelligence large model technology, the number of model parameters is often large.

[0004] Therefore, how to simply and efficiently implement large model updates for each satellite in a satellite network while improving the stability of model updates is an urgent problem to be solved. Summary of the invention

[0005] Based on this, it is necessary to provide a satellite model update method, computer equipment and storage medium that can simply and efficiently implement large model updates of each satellite in the satellite network and improve the stability of model updates in response to the above technical problems.

[0006] In a first aspect, the present application provides a satellite model updating method, the satellite model updating method being executed by a server of a target satellite, the method comprising:

[0007] Obtain the lightweight incremental model sent by the ground server;

[0008] Determining whether the lightweight incremental model is a shared model;

[0009] If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0010] If not, the lightweight incremental model is stored in a private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0011] In one embodiment, before obtaining the lightweight incremental model sent by the ground server, the method further includes:

[0012] The model update parameters are sent to the ground server so that the ground server updates the model to be updated according to the satellite model copy and the model update parameters, determines the incremental update model, and lightweights and versions the incremental update model to determine the lightweight incremental model.

[0013] In one embodiment, after storing the lightweight incremental model in the synchronization directory of the target satellite, the method further includes:

[0014] Determine, from a satellite network, a satellite to be updated that needs to share a model with the target satellite;

[0015] A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization catalog of the target satellite based on the shared network.

[0016] In one of the embodiments, after a model sharing network is constructed between the target satellite and the satellite to be updated so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, the method further includes:

[0017] Determining whether the synchronization directory of the satellite to be updated successfully saves the lightweight incremental model based on the model version number of the lightweight incremental model;

[0018] If not, the ground server is notified to send the lightweight incremental model to the private directory of the satellite to be updated.

[0019] In one embodiment, a model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization catalog of the target satellite based on the shared network, including:

[0020] Acquire a model loading request of the lightweight incremental model sent by a candidate satellite based on a satellite network;

[0021] Determining a to-be-updated satellite having model loading authority of the lightweight incremental model from the candidate satellites based on the model loading request;

[0022] A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, and stores the lightweight incremental model in the synchronization directory of the satellite to be updated.

[0023] In one embodiment, after storing the lightweight incremental model in the synchronization directory of the target satellite, the method further includes:

[0024] After obtaining the model privatization instruction corresponding to the lightweight incremental model, determining whether the lightweight incremental model is stored in the private directory of the target satellite;

[0025] If not, the lightweight incremental model is transmitted to the private directory of the target satellite, and the lightweight incremental model is deleted from the synchronization directory of the target satellite.

[0026] In one embodiment, the satellite model updating method further includes:

[0027] Acquire a model function test program of the lightweight incremental model from the ground server, and store the model function test program in a private directory of the target satellite;

[0028] Running the model function test program, and saving the running process data and running result data of the model function test program;

[0029] Determining whether the lightweight incremental model is valid according to the operation process data and the operation result data;

[0030] If so, a service configuration file corresponding to the lightweight incremental model is obtained from the ground server, and the service configuration file is stored in a private directory of the target satellite to make the lightweight incremental model effective.

[0031] In one embodiment, after determining whether the lightweight incremental model is valid according to the operation process data and the operation result data, the method further includes:

[0032] If not, the lightweight incremental model is deleted from the storage space of the target satellite, and information indicating that the lightweight incremental model is invalid is fed back to the ground server, so that the ground server resends the lightweight incremental model.

[0033] In a second aspect, the present application further provides a computer device, the computer device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0034] Obtain the lightweight incremental model sent by the ground server;

[0035] Determining whether the lightweight incremental model is a shared model;

[0036] If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0037] If not, the lightweight incremental model is stored in a private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0038] In a third aspect, the present application further provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the following steps are implemented:

[0039] Obtain the lightweight incremental model sent by the ground server;

[0040] Determining whether the lightweight incremental model is a shared model;

[0041] If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0042] If not, the lightweight incremental model is stored in a private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0043] The satellite model update method, computer device and storage medium obtain the lightweight incremental model sent by the ground server; determine whether the lightweight incremental model is a shared model; if so, store the lightweight incremental model in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network; if not, store the lightweight incremental model in the private directory of the target satellite. The information in the private directory of the target satellite is not shared with other satellites in the satellite network. This solves the problem that when updating large models of each satellite in the satellite network, the updated lightweight incremental models are uploaded one by one, resulting in low model update efficiency, and batch transmission of lightweight incremental models will cause unstable data synchronization. The above scheme divides the storage space of satellites in the satellite network into a synchronization directory and a private directory. Files in the synchronization directory can be shared between satellite networks, while files in the private directory are not shared. When multiple satellites in the satellite network need to update the same onboard model, the lightweight incremental model determined by the ground server after updating the onboard model is sent to the synchronization directory of a target satellite, and model sharing is achieved based on the synchronization directory of the target satellite, thereby achieving the effect of updating the onboard models on each satellite in the satellite network, which can improve the efficiency of updating the onboard models of each satellite in the satellite network and improve the stability of the onboard model update. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 A schematic diagram of a flow chart of a satellite model updating method in one embodiment;

[0045] Figure 2 A schematic flow chart of a satellite model updating method in another embodiment;

[0046] Figure 3 A schematic flow chart of a satellite model updating method in another embodiment;

[0047] Figure 4 A schematic flow chart of a satellite model updating method in another embodiment;

[0048] Figure 5 It is a structural block diagram of a satellite model updating device in one embodiment;

[0049] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

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

[0051] In one embodiment, Figure 1 As shown, a satellite model updating method is provided. The satellite model updating method provided in this embodiment is executed by a server of the target satellite. In this embodiment, the method includes the following steps:

[0052] S110. Obtain a lightweight incremental model sent by a ground server.

[0053] The ground server refers to a server established at a ground station, which is used to obtain the working conditions of each satellite in the satellite network and guide the operation of each satellite. The lightweight incremental model refers to the model determined by the ground server after updating the onboard model of the target satellite based on the onboard model copy of the target satellite. It should be noted that the satellite stores an original onboard model and different versions of lightweight incremental models corresponding to the original onboard model.

[0054] Specifically, the target satellite in the satellite network can periodically send its operating parameters to the ground server. The ground server can update the onboard model stored on the target satellite according to the operating parameters of the target satellite and the copy of the onboard model of the target satellite stored in the ground server, determine the lightweight incremental model sent by the ground server, and the server of the target satellite can obtain the lightweight incremental model from the ground server based on the transmission link between the target satellite and the ground server, and store the lightweight incremental model in the storage space of the target satellite. The satellite network is a network composed of multiple satellites in space, which can adopt microwave or laser forms for network communication. The communication between satellites can be one-to-one or many-to-many, that is, one satellite can communicate with multiple satellites.

[0055] S120: Determine whether the lightweight incremental model is a shared model.

[0056] It should be noted that the satellites in the satellite network may store the same onboard model. If the target satellite obtains a lightweight incremental model of the same onboard model, the lightweight incremental model can be used as a shared model and shared among the satellites in the satellite network.

[0057] S130: If yes, store the lightweight incremental model in the synchronization directory of the target satellite.

[0058] The information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network.

[0059] It should be noted that the storage space of each satellite in the satellite network is divided into a synchronization directory and a private directory. Files under the synchronization directory can be synchronized to other satellites in the satellite network through the satellite network, and files under the private directory will not be synchronized to other satellites in the satellite network.

[0060] For example, the directory / mnt / sync in the storage space of each satellite in the satellite network can be set as the synchronization directory. The files in the synchronization directory will be automatically synchronized or synchronized on demand to other satellites in the satellite network. The synchronization directory mainly stores model files that need to be synchronized; the directory / mnt / private is set as a non-synchronized private directory, and the files in the private directory will not be synchronized to other satellites.

[0061] Specifically, if the lightweight incremental model is a model that needs to be shared with other satellites in the satellite network, the lightweight model is stored in the synchronization directory of the target satellite.

[0062] S140: If not, store the lightweight incremental model in the private directory of the target satellite.

[0063] The information in the target satellite's private catalog is not shared with other satellites in the satellite network.

[0064] Specifically, if the lightweight incremental model is a model that is not shared with other satellites in the satellite network, the lightweight incremental model is stored in a private directory of the target satellite.

[0065] Exemplarily, when the target satellite completes loading of the lightweight incremental model, it can also feedback the model loading completion information to the ground server. If the ground server does not receive the model loading completion information fed back by the target satellite within a preset time, it can be determined that the transmission link between the target satellite and the target satellite has failed. The target satellite that can upload the lightweight incremental model can be reselected from other satellites in the satellite network, and the lightweight incremental model can be uploaded to the synchronization directory of the reselected target satellite.

[0066] In the above satellite model update method, the lightweight incremental model sent by the ground server is obtained; it is determined whether the lightweight incremental model is a shared model; if so, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network; if not, the lightweight incremental model is stored in the private directory of the target satellite. The information in the private directory of the target satellite is not shared with other satellites in the satellite network. This solves the problem that when updating large models of each satellite in the satellite network, the updated lightweight incremental models are uploaded one by one, resulting in low model update efficiency, and batch transmission of lightweight incremental models will cause unstable data synchronization. The above scheme divides the storage space of satellites in the satellite network into a synchronization directory and a private directory. Files in the synchronization directory can be shared between satellite networks, while files in the private directory are not shared. When multiple satellites in the satellite network need to update the same onboard model, the lightweight incremental model determined by the ground server after updating the onboard model is sent to the synchronization directory of a target satellite, and model sharing is achieved based on the synchronization directory of the target satellite, thereby achieving the effect of updating the onboard models on each satellite in the satellite network, which can improve the efficiency of updating the onboard models of each satellite in the satellite network and improve the stability of the onboard model update.

[0067] In one embodiment, before obtaining the lightweight incremental model sent by the ground server, the method further includes:

[0068] The model update parameters are sent to the ground server, so that the ground server updates the model to be updated according to the onboard model copy and the model update parameters, determines the incremental update model, and performs lightweight and versioning processing on the incremental update model to determine the lightweight incremental model.

[0069] Among them, model lightweighting refers to reducing the data size of the model so that it can be loaded and rendered faster on browsers or other devices.

[0070] Specifically, the model update parameters are sent to the ground server, and the ground server determines the satellite model that needs to be updated based on the model update parameters and the satellite model copy saved by the ground station, and updates the satellite model based on the model update parameters, and uses the updated satellite model as the incremental update model. The ground server can also perform lightweight processing on the incremental update model, and version the lightweight processed model, and use the versioned model as the lightweight incremental model. The method for lightweight processing of the satellite model can be: for each parameter contained in the target satellite model, quantize the decimal place of the parameter to a specified number of places, so as to obtain a lightweight target satellite model.

[0071] Exemplarily, when lightweight processing is performed on the incremental update model, low-bit quantization techniques such as INT8 or INT4 can be used to quantize the parameters with long decimal places in the satellite model that needs to be updated into parameters with fewer decimal places. Among them, the specified number of bits can be determined according to the specific performance requirements and the resource status of the satellite. For example, it can be set to 2 or 4 bits, etc., and this specification does not impose specific restrictions on this. Those skilled in the art should understand that the longer the number of bits of a data, the larger the storage space it occupies in the computer. Low-bit quantization can convert data with longer bits into data with shorter bits, greatly reducing the size of the model with almost no loss of model performance.

[0072] It should be noted that the onboard model is a deep learning model with tens of millions or even hundreds of millions of parameters, and the model has powerful expression and learning capabilities. The onboard model is a trained neural network model carried on the satellite. It can serve as the basis for other models, and perform secondary training and fine-tuning on its basis to adapt to new data and tasks in different scenarios. The ground station uses the computing power of the ground server to train and fine-tune the onboard model copy, and generates an incremental model parameter file. The incremental model parameter file and the onboard model before the update together constitute a new onboard model. Since the onboard model before the update has been deployed in the target satellite, the ground server does not need to repeatedly upload the onboard model before the update to the target satellite, and only needs to upload the parameter file corresponding to the lightweight incremental model. Usually, the storage space occupied by the parameter file corresponding to the lightweight incremental model is much smaller than the storage space occupied by the onboard model.

[0073] In the above scheme, after the ground server updates the model to be updated according to the onboard model copy and model update parameters, it further performs lightweight operations on the updated incremental update model, which can reduce the storage resources occupied by the updated onboard model in the satellite, reduce the model size, and improve the model's reasoning speed.

[0074] In one embodiment, Figure 2 As shown, after the lightweight incremental model is stored in the synchronization directory of the target satellite, it also includes:

[0075] S210: Determine, from the satellite network, a satellite to be updated that needs to share a model with the target satellite.

[0076] It should be noted that when updating the onboard models of each satellite in the satellite network, there may be a situation where only some satellites need to update the models. Therefore, when sharing the lightweight incremental model through the synchronization directory of the target satellite, it is also necessary to determine the satellites to be updated that need to share the model with the target satellite.

[0077] S220: construct a model sharing network between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory based on the shared network.

[0078] It should be noted that the satellite servers of each satellite in the satellite network are equipped with a task trigger system. The task trigger system uses a stack and priority mode, and can trigger the execution of different business programs as needed, including triggering in different orders and at different times. The trigger can be set to automatic or manual. The tasks and programs that need to be executed on the satellite are usually issued by the ground station. The task trigger system deployed on the satellite can execute tasks and programs according to the task instructions.

[0079] Specifically, when the synchronization program of the mission trigger system in the target satellite is triggered, the satellite to be updated is determined according to the mission instruction, so as to build a model sharing network between the target satellite and the satellite to be updated, and synchronize the relevant parameter files of the lightweight incremental model to the synchronization files of the satellite to be updated. Satellites that have not joined the model sharing network cannot load the relevant parameter files of the lightweight incremental model from the synchronization directory of the target satellite. The satellite to be updated loads the relevant parameter files of the lightweight incremental model in the synchronization directory based on the shared network to achieve the effect of batch updating the onboard models in the satellite to be updated.

[0080] The above scheme can build a model sharing network between the satellites to be updated that need model updating according to actual needs, improve the flexibility when updating the onboard models corresponding to each satellite in the satellite network, and avoid waste of resources.

[0081] In one embodiment, Figure 3 As shown, after a model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, it also includes:

[0082] S310: Determine whether the synchronization directory of the satellite to be updated successfully saves the lightweight incremental model based on the model version number of the lightweight incremental model.

[0083] It should be noted that the model name of the lightweight incremental model generally includes the model version number information. For example, the model name of the lightweight incremental model may be quant_incremental_model.2024.9.29.001.gguf, and the model version number is 2024.9.29.001.

[0084] Specifically, after the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, the model version number of the lightweight incremental model is compared with the model version numbers of each satellite model stored in the synchronization directory of the satellite to be updated. If there is a satellite model with the same model version number as the lightweight incremental model in the synchronization directory of the satellite to be updated, it is determined that the synchronization directory of the satellite to be updated has successfully saved the lightweight incremental model; if there is no satellite model with the same model version number as the lightweight incremental model in the synchronization directory of the satellite to be updated, it is determined that the synchronization directory of the satellite to be updated has failed to successfully save the lightweight incremental model.

[0085] S320: If not, notify the ground server to send the lightweight incremental model to the private directory of the satellite to be updated.

[0086] Specifically, if the synchronization directory of the satellite to be updated fails to successfully save the lightweight incremental model, a notification message of failure to update the satellite model is sent to the ground server, informing the ground server to send the lightweight incremental model to the private directory of the satellite to be updated. The notification message of failure to update the satellite model may include the satellite number of the satellite to be updated and the model name of the lightweight incremental model.

[0087] The above scheme can promptly notify the ground server to send the lightweight incremental model directly to the private directory of the satellite to be updated when it is determined that the satellite to be updated has failed to successfully load the lightweight incremental model, thereby ensuring that the satellite to be updated can update the model in a timely and effective manner.

[0088] In one embodiment, a model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, including:

[0089] Based on the satellite network, the lightweight incremental model sent by the candidate satellite is obtained; based on the model loading request, the satellite to be updated with the model loading authority of the lightweight incremental model is determined from the candidate satellites; a model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, and stores the lightweight incremental model in the synchronization directory of the satellite to be updated.

[0090] The candidate satellites may be all satellites in the satellite network or some satellites in the satellite network. The model loading request may include the model name of the lightweight incremental model and the satellite identifier of the candidate satellite.

[0091] Specifically, after the target satellite has completed loading the lightweight incremental model from the ground server, the ground server may send the satellite identifier of the target satellite and the model name of the lightweight incremental model to each satellite in the satellite network. After receiving the model name of the lightweight incremental model, each satellite in the satellite network may determine whether it has a model loading requirement for the lightweight incremental model according to the model name of the lightweight incremental model. For example, if the storage space of a satellite in the satellite network stores the original model corresponding to the lightweight incremental model, the satellite has a model loading requirement for the lightweight incremental model. If some satellites in the satellite network have a model loading requirement for the lightweight incremental model, these satellites may be used as candidate satellites, and a model loading request for the lightweight incremental model may be sent to the target satellite based on the satellite network. The satellite identifier of the candidate satellite may be determined according to the model loading request, and whether the candidate satellite has the model loading authority for the lightweight incremental model may be determined according to the satellite identifier of the candidate satellite. The candidate satellite with the model loading authority for the lightweight incremental model may be used as a satellite to be updated. A model sharing network is constructed between the target satellite and the satellite to be updated so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, and stores the lightweight incremental model in the synchronization directory of the satellite to be updated. It can be understood that after the satellite to be updated stores the lightweight incremental model in its synchronization directory, it also has the authority to share the lightweight incremental model with other satellites in the satellite network.

[0092] The above scheme verifies the authority of the candidate satellites according to the model loading request sent by the candidate satellites in the satellite network, and uses the candidate satellites that pass the verification as the satellites to be updated, and builds a model sharing network between the satellites to be updated and the target satellites, so that the satellites to be updated can load the lightweight incremental model from the synchronization directory of the target satellite, which can ensure the security of the model data. At the same time, the lightweight incremental model loaded by the satellite to be updated is stored in its synchronization directory, so that the satellite to be updated also has the authority to share the lightweight incremental model with other satellites in the satellite network.

[0093] In one embodiment, after storing the lightweight incremental model in the synchronization directory of the target satellite, the method further includes:

[0094] After obtaining the model privatization instruction corresponding to the lightweight incremental model, determine whether the lightweight incremental model is stored in the private directory of the target satellite; if not, transfer the lightweight incremental model to the private directory of the target satellite and delete the lightweight incremental model from the synchronization directory of the target satellite.

[0095] Specifically, if the satellite trigger system configured in the server of the target satellite receives the model privatization instruction corresponding to the lightweight incremental model, it determines whether the lightweight incremental model is already stored in the update model corresponding to the onboard model stored in the private directory of the target satellite based on the version number of the lightweight incremental model. If so, the lightweight incremental model is directly deleted from the synchronization directory of the target satellite. If not, it is necessary to transfer the relevant parameter files of the lightweight incremental model to the private directory of the target satellite, and delete the lightweight incremental model from the synchronization directory of the target satellite.

[0096] It should be noted that the method for privatizing the model parameter files stored in the synchronization directory of other satellites in the satellite network is consistent with the method for privatizing the lightweight incremental model in the synchronization directory of the target satellite, and will not be repeated here.

[0097] In the above scheme, when privatizing the lightweight incremental model, it is first determined whether the lightweight incremental model is stored in the private directory of the target satellite. If not, the model parameter file corresponding to the lightweight incremental model is transmitted to the private directory of the target satellite, which can avoid invalid transmission of the lightweight incremental model and waste of resources.

[0098] In one embodiment, Figure 4 As shown, the satellite model updating method further includes:

[0099] S410, obtaining a model function test program of the lightweight incremental model from a ground server, and storing the model function test program in a private directory of the target satellite.

[0100] The model function test program is written by the R&D personnel and uploaded to the ground server. The model function test program can be used to perform model verification on the lightweight incremental model to determine whether the model function of the lightweight incremental model is normal. The server of the target satellite can load the model function test program of the lightweight incremental model from the ground server and store the model function test program in the private directory of the target satellite.

[0101] S420, running the model function test program, and saving the running process data and running result data of the model function test program.

[0102] Specifically, the model function test program is run without affecting the target satellite's on-orbit mission to verify whether the model function of the lightweight incremental model is normal, and the running process data and running result data of the model function test program are saved.

[0103] S430: Determine whether the lightweight incremental model is valid according to the operation process data and the operation result data.

[0104] Specifically, the running process data is compared with the process data corresponding to the model function test program for consistency, and the running result data is compared with the result data corresponding to the model function test program for consistency. If the running process data is consistent with the process data corresponding to the model function test program, and the running result data is consistent with the result data corresponding to the model function test program, then the model function of the lightweight incremental model is determined to be normal and the lightweight incremental model is a valid model; if the running process data is inconsistent with the process data corresponding to the model function test program, or the running result data is inconsistent with the result data corresponding to the model function test program, then the model function of the lightweight incremental model is determined to be abnormal and the lightweight incremental model is an invalid model.

[0105] S440: If yes, obtain a service configuration file corresponding to the lightweight incremental model from the ground server, and store the service configuration file in a private directory of the target satellite to make the lightweight incremental model effective.

[0106] Specifically, if the lightweight incremental model is a valid model, a service configuration file corresponding to the lightweight incremental model is obtained from the ground server, and the service configuration file is stored in a private directory of the target satellite to make the lightweight incremental model effective.

[0107] Furthermore, after determining that the lightweight incremental model is a valid model, the information that the lightweight incremental model is a valid model can also be sent to the ground server, so that after the ground server receives the information that the lightweight incremental model is a valid model, the lightweight incremental model is tested in the ground station for business scenarios, that is, the lightweight incremental model is tested based on the business scenario data when the target satellite performs an operation task, and the test results are obtained. The R&D personnel can evaluate whether the model performance of the lightweight incremental model meets expectations based on the test results. If not, the lightweight incremental model can be adjusted, or the business history configuration file saved by the ground station can be uploaded to the private directory of the target satellite. The server of the target satellite performs model data rollback on the lightweight incremental model based on the business history configuration file. Among them, model data rollback refers to undoing the most recent operation in the data warehouse or database and restoring it to the previous state.

[0108] It should be noted that the method of performing validity verification and business scenario testing on the lightweight incremental model stored in the storage space of other satellites in the satellite network is consistent with the above-mentioned method of performing validity verification and business scenario testing on the lightweight incremental model of the target satellite, and will not be repeated here.

[0109] The above scheme is based on the model function test program of the lightweight incremental model loaded from the ground server to test whether the lightweight incremental model is a valid model, and loads the business configuration file from the ground server when the lightweight incremental model is determined to be a valid model to make the lightweight incremental model effective. This can ensure the reliability of the lightweight incremental model and avoid satellite failure problems caused by model errors.

[0110] In one embodiment, after determining whether the lightweight incremental model is valid according to the operation process data and the operation result data, the method further includes:

[0111] If not, the lightweight incremental model is deleted from the storage space of the target satellite, and information that the lightweight incremental model is invalid is fed back to the ground server, so that the ground server resends the lightweight incremental model.

[0112] Specifically, if the lightweight incremental model is an invalid model, the model parameter file of the lightweight incremental model is deleted from the synchronization directory or private directory of the target satellite, and the information that the lightweight incremental model is invalid is fed back to the ground server. After the ground server receives the information that the lightweight incremental model is invalid, the R&D personnel can adjust the lightweight incremental model, and the server of the target satellite can reload the adjusted lightweight incremental model from the ground server.

[0113] The above scheme can reload the lightweight incremental model from the ground server in time when the lightweight incremental model is an invalid model, thereby ensuring the operational stability of each satellite in the satellite network.

[0114] Exemplarily, based on the above embodiment, the satellite model updating method includes:

[0115] The model update parameters are sent to the ground server. The ground server determines the satellite model that needs to be updated based on the model update parameters and the satellite model copy saved by the ground station, and updates the satellite model based on the model update parameters, and uses the updated satellite model as the incremental update model. The ground server can also perform lightweight processing on the incremental update model, and version the lightweight processed model, and use the versioned model as the lightweight incremental model. The method for lightweight processing of the satellite model can be: for each parameter contained in the target satellite model, quantize the number of decimal places of the parameter to a specified number of places, thereby obtaining a lightweight target satellite model.

[0116] The target satellite in the satellite network can periodically send its operating parameters to the ground server. The ground server can update the onboard model stored on the target satellite according to the operating parameters of the target satellite and the onboard model copy of the target satellite saved by the ground server, determine the lightweight incremental model sent by the ground server, and the server of the target satellite can obtain the lightweight incremental model from the ground server based on the transmission link between the target satellite and the ground server, and store the lightweight incremental model in the storage space of the target satellite. Determine whether the lightweight incremental model is a shared model.

[0117] The storage space of each satellite in the satellite network is divided into a synchronization directory and a private directory. Files in the synchronization directory can be synchronized to other satellites in the satellite network through the satellite network, and files in the private directory will not be synchronized to other satellites in the satellite network.

[0118] If the lightweight incremental model is a model that needs to be shared with other satellites in the satellite network, the lightweight model is stored in the synchronization directory of the target satellite. If the lightweight incremental model is a model that is not shared with other satellites in the satellite network, the lightweight incremental model is stored in the private directory of the target satellite.

[0119] When updating the onboard models of each satellite in the satellite network, there may be a situation where only some satellites need to update the models. Therefore, when the lightweight incremental model is shared through the synchronization directory of the target satellite, it is also necessary to determine the satellite to be updated that needs to share the model with the target satellite. When the synchronization program of the mission trigger system in the target satellite is triggered, the satellite to be updated is determined according to the mission instruction to build a model sharing network between the target satellite and the satellite to be updated, and the relevant parameter files of the lightweight incremental model are synchronized to the synchronization files of the satellite to be updated. Satellites that have not joined the model sharing network cannot load the relevant parameter files of the lightweight incremental model from the synchronization directory of the target satellite. The satellite to be updated loads the relevant parameter files of the lightweight incremental model in the synchronization directory based on the shared network to achieve the effect of batch updating the onboard models in the satellite to be updated.

[0120] After the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, the model version number of the lightweight incremental model is compared with the model version numbers of each satellite-borne model stored in the synchronization directory of the satellite to be updated. If there is a satellite-borne model with the same model version number as the lightweight incremental model in the synchronization directory of the satellite to be updated, it is determined that the synchronization directory of the satellite to be updated successfully saves the lightweight incremental model; if there is no satellite-borne model with the same model version number as the lightweight incremental model in the synchronization directory of the satellite to be updated, it is determined that the synchronization directory of the satellite to be updated has failed to successfully save the lightweight incremental model.

[0121] If the synchronization directory of the satellite to be updated fails to successfully save the lightweight incremental model, a notification message of failure to update the satellite model is sent to the ground server, informing the ground server to send the lightweight incremental model to the private directory of the satellite to be updated. The notification message of failure to update the satellite model may include the satellite number of the satellite to be updated and the model name of the lightweight incremental model.

[0122] If the satellite trigger system configured in the server of the target satellite receives the model privatization instruction corresponding to the lightweight incremental model, it determines whether the lightweight incremental model is already stored in the update model corresponding to the onboard model stored in the private directory of the target satellite based on the version number of the lightweight incremental model. If so, the lightweight incremental model is directly deleted from the synchronization directory of the target satellite. If not, it is necessary to transfer the relevant parameter files of the lightweight incremental model to the private directory of the target satellite, and delete the lightweight incremental model from the synchronization directory of the target satellite.

[0123] Obtain the model function test program of the lightweight incremental model from the ground server, and store the model function test program in the private directory of the target satellite. Run the model function test program without affecting the target satellite's on-orbit mission to verify whether the model function of the lightweight incremental model is normal, and save the running process data and running result data of the model function test program. Compare the running process data with the process data corresponding to the model function test program for consistency, and compare the running result data with the result data corresponding to the model function test program for consistency. If the running process data is consistent with the process data corresponding to the model function test program, and the running result data is consistent with the result data corresponding to the model function test program, then it is determined that the model function of the lightweight incremental model is normal and the lightweight incremental model is a valid model; if the running process data is inconsistent with the process data corresponding to the model function test program, or the running result data is inconsistent with the result data corresponding to the model function test program, then it is determined that the model function of the lightweight incremental model is abnormal and the lightweight incremental model is an invalid model. If the lightweight incremental model is a valid model, obtain the service configuration file corresponding to the lightweight incremental model from the ground server, and store the service configuration file in the private directory of the target satellite to make the lightweight incremental model effective. After determining that the lightweight incremental model is a valid model, the information that the lightweight incremental model is a valid model can also be sent to the ground server, so that after the ground server receives the information that the lightweight incremental model is a valid model, the lightweight incremental model is tested in a business scenario at the ground station, that is, the lightweight incremental model is tested based on the business scenario data when the target satellite performs an operation mission, and the test results are obtained. The R&D personnel can evaluate whether the model performance of the lightweight incremental model meets expectations based on the test results. If not, the lightweight incremental model can be adjusted, or the business history configuration file saved by the ground station can be uploaded to the private directory of the target satellite. The server of the target satellite rolls back the model data of the lightweight incremental model based on the business history configuration file.

[0124] In the above satellite model update method, the lightweight incremental model sent by the ground server is obtained; it is determined whether the lightweight incremental model is a shared model; if so, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network; if not, the lightweight incremental model is stored in the private directory of the target satellite. The information in the private directory of the target satellite is not shared with other satellites in the satellite network. This solves the problem that when updating large models of each satellite in the satellite network, the updated lightweight incremental models are uploaded one by one, resulting in low model update efficiency, and batch transmission of lightweight incremental models will cause unstable data synchronization. The above scheme divides the storage space of satellites in the satellite network into a synchronization directory and a private directory. Files in the synchronization directory can be shared between satellite networks, while files in the private directory are not shared. When multiple satellites in the satellite network need to update the same onboard model, the lightweight incremental model determined by the ground server after updating the onboard model is sent to the synchronization directory of a target satellite, and model sharing is achieved based on the synchronization directory of the target satellite, thereby achieving the effect of updating the onboard models on each satellite in the satellite network, which can improve the efficiency of updating the onboard models of each satellite in the satellite network and improve the stability of the onboard model update.

[0125] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0126] Based on the same inventive concept, the embodiment of the present application also provides a satellite model updating device for implementing the satellite model updating method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more satellite model updating device embodiments provided below can refer to the limitations on the satellite model updating method above, and will not be repeated here.

[0127] In one embodiment, Figure 5As shown, a satellite model updating device is provided, which is applied to a server of a target satellite. The satellite model updating device comprises: an incremental model acquisition module 501, a shared model determination module 502, a synchronization directory update module 503 and a private directory update module 504, wherein:

[0128] The incremental model acquisition module 501 is used to acquire the lightweight incremental model sent by the ground server;

[0129] A shared model determination module 502, used to determine whether the lightweight incremental model is a shared model;

[0130] A synchronization directory updating module 503 is used to store the lightweight incremental model in the synchronization directory of the target satellite if yes; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0131] The private directory updating module 504 is used to store the lightweight incremental model in the private directory of the target satellite if no; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0132] Exemplarily, the incremental model acquisition module 501 is further used for:

[0133] The model update parameters are sent to the ground server, so that the ground server updates the model to be updated according to the onboard model copy and the model update parameters, determines the incremental update model, and performs lightweight and versioning processing on the incremental update model to determine the lightweight incremental model.

[0134] Exemplarily, the synchronous directory update module 503 is further used for:

[0135] Determine from the satellite network the satellite to be updated that needs to share the model with the target satellite;

[0136] A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network.

[0137] Exemplarily, the synchronous directory update module 503 is further used for:

[0138] Determine whether the synchronization directory of the satellite to be updated successfully saves the lightweight incremental model based on the model version number of the lightweight incremental model;

[0139] If not, the ground server is notified to send the lightweight incremental model to the private directory of the satellite to be updated.

[0140] Exemplarily, the synchronous directory update module 503 is further used for:

[0141] Obtaining a model loading request of a lightweight incremental model sent by a candidate satellite based on a satellite network;

[0142] Determine, from the candidate satellites, a satellite to be updated that has a model loading authority for a lightweight incremental model based on the model loading request;

[0143] A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, and stores the lightweight incremental model in the synchronization directory of the satellite to be updated.

[0144] Exemplarily, the synchronous directory update module 503 is further used for:

[0145] After obtaining the model privatization instruction corresponding to the lightweight incremental model, determining whether the lightweight incremental model is stored in the private directory of the target satellite;

[0146] If not, the lightweight incremental model is transmitted to the private directory of the target satellite, and the lightweight incremental model is deleted from the synchronization directory of the target satellite.

[0147] Exemplarily, the satellite model updating device further includes:

[0148] A test program acquisition module is used to acquire a model function test program of a lightweight incremental model from a ground server and store the model function test program in a private directory of a target satellite;

[0149] The test program running module is used to run the model function test program and save the running process data and running result data of the model function test program;

[0150] A model validity verification module is used to determine whether the lightweight incremental model is valid based on the operation process data and operation result data;

[0151] The service configuration file acquisition module is used to obtain the service configuration file corresponding to the lightweight incremental model from the ground server if the lightweight incremental model is valid, and store the service configuration file in the private directory of the target satellite to make the lightweight incremental model effective.

[0152] Exemplarily, the satellite model updating device further includes:

[0153] The model invalid information sending module is used to delete the lightweight incremental model from the storage space of the target satellite if the lightweight incremental model is invalid, and to feed back the information that the lightweight incremental model is invalid to the ground server so that the ground server resends the lightweight incremental model.

[0154] 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 6 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. 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 input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a satellite model updating method is realized. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen 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 covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0155] Those skilled in the art will understand that Figure 6 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.

[0156] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0157] Step 1: Obtain the lightweight incremental model sent by the ground server;

[0158] Step 2: Determine whether the lightweight incremental model is a shared model;

[0159] Step 3: If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0160] Step 4: If not, the lightweight incremental model is stored in the private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0161] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0162] Step 1: Obtain the lightweight incremental model sent by the ground server;

[0163] Step 2: Determine whether the lightweight incremental model is a shared model;

[0164] Step 3: If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0165] Step 4: If not, the lightweight incremental model is stored in the private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0166] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0167] Step 1: Obtain the lightweight incremental model sent by the ground server;

[0168] Step 2: Determine whether the lightweight incremental model is a shared model;

[0169] Step 3: If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on the model sharing network;

[0170] Step 4: If not, the lightweight incremental model is stored in the private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network.

[0171] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0172] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

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

[0174] 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 satellite model updating method, characterized in that: The satellite model updating method is executed by a server of the target satellite, and the method comprises: Obtain the lightweight incremental model sent by the ground server; Determining whether the lightweight incremental model is a shared model; the shared model is a lightweight incremental model in which the same onboard model is stored between satellites; If yes, the lightweight incremental model is stored in the synchronization directory of the target satellite; the information in the synchronization directory of the target satellite can be shared with other satellites in the satellite network based on a model sharing network; the model sharing network is constructed between the target satellite and the satellite to be updated; If not, the lightweight incremental model is stored in a private directory of the target satellite; the information in the private directory of the target satellite is not shared with other satellites in the satellite network; Acquire a model function test program of the lightweight incremental model from the ground server, and store the model function test program in a private directory of the target satellite; Running the model function test program, and saving the running process data and running result data of the model function test program; Determining whether the lightweight incremental model is valid according to the operation process data and the operation result data; If so, a service configuration file corresponding to the lightweight incremental model is obtained from the ground server, and the service configuration file is stored in a private directory of the target satellite to make the lightweight incremental model effective.

2. The method according to claim 1, characterized in that Before obtaining the lightweight incremental model sent by the ground server, it also includes: The model update parameters are sent to the ground server so that the ground server updates the model to be updated according to the satellite model copy and the model update parameters, determines the incremental update model, and lightweights and versions the incremental update model to determine the lightweight incremental model.

3. The method according to claim 1, characterized in that After storing the lightweight incremental model in the synchronization directory of the target satellite, the method further includes: Determine, from a satellite network, a satellite to be updated that needs to share a model with the target satellite; A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization catalog of the target satellite based on the shared network.

4. The method according to claim 3, characterized in that After building a model sharing network between the target satellite and the satellite to be updated so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, the method further includes: Determining whether the synchronization directory of the satellite to be updated successfully saves the lightweight incremental model based on the model version number of the lightweight incremental model; If not, the ground server is notified to send the lightweight incremental model to the private directory of the satellite to be updated.

5. The method according to claim 3, characterized in that: A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, including: Acquire a model loading request of the lightweight incremental model sent by a candidate satellite based on a satellite network; Determining a to-be-updated satellite having model loading authority of the lightweight incremental model from the candidate satellites based on the model loading request; A model sharing network is constructed between the target satellite and the satellite to be updated, so that the satellite to be updated loads the lightweight incremental model in the synchronization directory of the target satellite based on the shared network, and stores the lightweight incremental model in the synchronization directory of the satellite to be updated.

6. The method according to claim 1, characterized in that After storing the lightweight incremental model in the synchronization directory of the target satellite, the method further includes: After obtaining the model privatization instruction corresponding to the lightweight incremental model, determining whether the lightweight incremental model is stored in the private directory of the target satellite; If not, the lightweight incremental model is transmitted to the private directory of the target satellite, and the lightweight incremental model is deleted from the synchronization directory of the target satellite.

7. The method according to claim 1, characterized in that After determining whether the lightweight incremental model is valid according to the operation process data and the operation result data, the method further includes: If not, the lightweight incremental model is deleted from the storage space of the target satellite, and information indicating that the lightweight incremental model is invalid is fed back to the ground server, so that the ground server resends the lightweight incremental model.

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

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images