Satellite node bulk upgrade method and system

Abstract

The application relates to a satellite node batch upgrading method and system, wherein the method comprises the following steps: receiving a creation request of a satellite node upgrading task; creating a main task record with a unique identifier in a satellite node upgrading task table according to the creation request; and creating a corresponding subtask record in a satellite node upgrading node state table for a target satellite node; the subtask record contains a unique identifier and a subtask state; the unique identifier is used to determine the association between the main task record and the subtask record; sending an upgrading request constructed based on the main task record to the target satellite node through a satellite-ground communication framework; determining the corresponding subtask record of the target satellite node in the satellite node upgrading node state table according to the state information returned by the target satellite node, and updating the subtask state in the subtask record. Through the application, the problem of inaccurate satellite node upgrading state management in the related art is solved, and accurate management of the satellite node upgrading state is realized.

Description

Technical Field

[0001] This application relates to the field of space-based system technology, and in particular to methods and systems for batch upgrading of satellite nodes. Background Technology

[0002] With the rapid development of space-based systems, the number of satellites in orbit is growing exponentially. Batch upgrades of satellite nodes have become a crucial link in ensuring the system's functional iteration and long-term stable operation. An efficient and reliable batch upgrade technology for satellite nodes is of paramount importance to ensuring the stability and security of satellite systems.

[0003] In existing technologies, batch upgrades of satellite nodes typically integrate upgrade task information and the status information of all nodes into a single record or logical unit. The drawback of these existing technologies is that they strongly bind task information to the individual execution status information of each satellite node, lacking a more detailed status tracking mechanism to accurately grasp the upgrade progress of each satellite node.

[0004] There is currently no effective solution to the problem of inaccurate satellite node upgrade status management in related technologies. Summary of the Invention

[0005] This embodiment provides a method and system for batch upgrading satellite nodes to solve the problem of inaccurate satellite node upgrade status management in related technologies.

[0006] Firstly, this embodiment provides a method for batch upgrading satellite nodes, applicable to a batch upgrading system for satellite nodes. The system includes a satellite-to-ground communication framework, ground workstations connected to the satellite-to-ground communication framework, and at least one target satellite node. The method is applicable to the ground workstation side. The method includes:

[0007] Receive requests to create satellite node upgrade tasks;

[0008] According to the creation request, a main task record with a unique identifier is created in the pre-built satellite node upgrade task table; and a corresponding sub-task record is created for the target satellite node in the pre-built satellite node upgrade node status table; the sub-task record contains the unique identifier and the sub-task status; the unique identifier is used to determine the association between the main task record and the sub-task record;

[0009] The upgrade request, constructed based on the master mission record, is sent to the target satellite node through the satellite-to-ground communication framework;

[0010] Based on the status information returned by the target satellite node, determine the subtask record corresponding to the target satellite node in the satellite node upgrade node status table, and update the subtask status in the subtask record.

[0011] In some embodiments, creating a corresponding subtask record for the target satellite node in a pre-built satellite node upgrade node status table includes:

[0012] After sorting the main task records according to their creation time and removing duplicates, they are inserted into the satellite node upgrade receiving queue.

[0013] The main task record is obtained sequentially from the satellite node upgrade receiving queue by the satellite node upgrade controller, and the sub-task record associated with the main task record is created based on the main task record.

[0014] In some embodiments, sending the upgrade request constructed based on the master mission record to the target satellite node includes:

[0015] The subtask record associated with the main task record is queried based on the unique identifier of the main task record;

[0016] The upgrade request is determined based on the sub-task record associated with the main task record;

[0017] The upgrade request is sent asynchronously to the target satellite node through the aforementioned satellite-to-ground communication framework.

[0018] In some embodiments, after updating the subtask status corresponding to the target satellite node in the satellite node upgrade node status table based on the status information, the method further includes:

[0019] Based on the sub-task status of the target satellite node in the satellite node upgrade node status table and the predefined status aggregation rules, the main task status is determined; the main task status is recorded in the main task record.

[0020] In some embodiments, determining the main task status based on the sub-task status of the target satellite node in the satellite node upgrade node status table and predefined status aggregation rules includes:

[0021] The subtask state is taken as the state to be aggregated, and the state is aggregated according to the state aggregation rule to obtain the final aggregated state; the aggregated state is taken as the main task state.

[0022] In some embodiments, the state aggregation rule includes:

[0023] The predefined progress state is the first priority. When the state to be aggregated contains the progress state, the lowest level state value in the progress state is taken as the final aggregated state.

[0024] The predefined abnormal state is the second priority. When the state to be aggregated contains the abnormal state but does not contain the state in progress, the abnormal state is taken as the final aggregated state.

[0025] The completion state is the third priority. When the state to be aggregated includes the completion state but does not include the progress state or the abnormal state, the completion state is taken as the final aggregation state.

[0026] In some embodiments, the progress state includes a pending state, an uploading state, and an upgrading state; the abnormal state includes a failure state, an overwrite state, an overwrite failure state, a timeout state, a cancellation state, and a cancellation failure state.

[0027] The pending status is used to indicate that the upgrade request has not been sent;

[0028] The "Uploading in Progress" status is used to characterize the status of the upgrade request being uploaded; the "Uploading in Progress" status level is higher than the "Pending Processing" status.

[0029] The "Upgrading in Progress" status is used to characterize the status of the upgrade request execution; the "Upgrading in Progress" status level is higher than the "Uploading in Progress" status.

[0030] The failure status is used to indicate that the upgrade request was not completed correctly;

[0031] The coverage status is used to characterize the state in which the upgrade request successfully overwrites the previous upgrade request.

[0032] The overwrite failure status is used to characterize the state in which the upgrade request overwrites the previous failed upgrade request.

[0033] The timeout status is used to characterize the state where the upgrade request failed to be sent or the database transaction processing failed.

[0034] The cancellation status is used to indicate that the upgrade request was successfully cancelled;

[0035] The cancellation failure status is used to indicate that the cancellation of the upgrade request failed.

[0036] Secondly, this embodiment provides a method for batch upgrading satellite nodes, applicable to a batch upgrading system for satellite nodes. The system includes a satellite-to-ground communication framework and ground workstations connected to the satellite-to-ground communication framework, as well as at least one target satellite node. The method is applicable to the target satellite node side. The method includes:

[0037] Receive upgrade requests sent by the satellite-to-ground communication framework;

[0038] Based on the satellite upgrade module, the upgrade request is parsed into binary files, configuration data, and upgrade commands;

[0039] Based on the binary file, the configuration data, and the upgrade command, the target satellite node is upgraded using the satellite upgrade module.

[0040] In some embodiments, after parsing the upgrade request into binary files, configuration data, and upgrade commands, the process includes:

[0041] The binary file is then transferred to a locally specified cache directory.

[0042] The configuration data and the upgrade command are persisted to the local database through the cache manager.

[0043] Thirdly, this embodiment provides a satellite node batch upgrade system, including a satellite-to-ground communication framework and ground workstations respectively connected to the satellite-to-ground communication framework, and at least one target satellite node; the ground workstation is configured to execute the satellite node batch upgrade method described in the first aspect above, and the target satellite node is configured to execute the satellite node batch upgrade method described in the second aspect above.

[0044] Compared with related technologies, the satellite node batch upgrade method and system provided in this embodiment receive a satellite node upgrade task creation request; based on the creation request, create a main task record with a unique identifier in a pre-built satellite node upgrade task table; and create a corresponding sub-task record for the target satellite node in a pre-built satellite node upgrade node status table. The sub-task record contains a unique identifier and a sub-task status; the unique identifier is used to determine the association between the main task record and the sub-task record; the upgrade request based on the main task record is sent to the target satellite node through a satellite-to-ground communication framework; based on the status information returned by the target satellite node, the corresponding sub-task record of the target satellite node in the satellite node upgrade node status table is determined, and the sub-task status in the sub-task record is updated. By introducing a dual-table status association architecture based on a unique identifier and a multi-dimensional status definition and state machine covering the entire upgrade lifecycle, the problem of inaccurate satellite node upgrade status management in related technologies is solved, and precise management of satellite node upgrade status is achieved.

[0045] Details of one or more embodiments of this application are set forth in the following drawings and description to make other features, objects and advantages of this application more readily apparent. Attached Figure Description

[0046] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0047] Figure 1 This is a hardware structure block diagram of a satellite node batch upgrade system provided in an embodiment of this application;

[0048] Figure 2 This is a flowchart of a method for batch upgrading satellite nodes on the ground workstation side, provided in an embodiment of this application;

[0049] Figure 3 This is a flowchart illustrating the process of sending an upgrade request to a target satellite node, as provided in one embodiment of this application.

[0050] Figure 4 This is a schematic diagram of the process of transitioning between states provided in an embodiment of this application;

[0051] Figure 5 This is a schematic diagram of the structure of a satellite node upgrade operation provided in an embodiment of this application;

[0052] Figure 6 This is a flowchart illustrating a node upgrade task insertion event provided in an embodiment of this application;

[0053] Figure 7This is a flowchart illustrating a node upgrade task deletion event provided in an embodiment of this application;

[0054] Figure 8 This is a flowchart of a method for batch upgrading satellite nodes applicable to the target satellite node side, provided by an embodiment of this application.

[0055] In the diagram: 100, ground workstation; 200, satellite-to-ground communication framework; 300, target satellite node. Detailed Implementation

[0056] To better understand the purpose, technical solution, and advantages of this application, the application is described and illustrated below in conjunction with the accompanying drawings and embodiments.

[0057] Unless otherwise defined, the technical or scientific terms used in this application shall have the general meaning understood by one of ordinary skill in the art to which this application pertains. Words such as “a,” “an,” “an,” “the,” “the,” and “these” used in this application do not indicate quantitative limitation and may be singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that comprises a series of steps or modules (units) is not limited to the listed steps or modules (units) but may include steps or modules (units) not listed, or may include other steps or modules (units) inherent to these processes, methods, products, or devices. Words such as “connected,” “linked,” and “coupled” used in this application are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. “Multiple” used in this application refers to two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. Normally, the character " / " indicates that the objects before and after it are in an "or" relationship. The terms "first," "second," "third," etc., used in this application are merely to distinguish similar objects and do not represent a specific order of objects.

[0058] The method embodiments provided in this example can be executed on a terminal, computer, or similar computing device. For example, it can run on a terminal. Figure 1 This is a hardware structure block diagram of the satellite node batch upgrade system in this embodiment. For example... Figure 1 As shown, the terminal may include a ground workstation 100, a satellite-to-ground communication frame 200, and one or more ( Figure 1(Only one target satellite node 300 is shown in the diagram.) The ground station 100 generates and sends upgrade requests; the satellite-to-ground communication framework 200 acts as a communication bridge, encapsulating and asynchronously transmitting upgrade requests; the target satellite node 300 receives upgrade requests and executes upgrade tasks. After completion, it feeds back its status information to the ground station 100 via the satellite-to-ground communication framework 200, thus forming a closed-loop upgrade control and status synchronization path. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the terminal described above. For example, the terminal may also include components that are larger than... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown are illustrated.

[0059] This embodiment provides a method for batch upgrading of satellite nodes applicable to ground workstations. Figure 2 This is a flowchart of the satellite node batch upgrade method applicable to the ground workstation side in this embodiment, as shown below. Figure 2 As shown, the process includes the following steps:

[0060] Step S110: Receive the request to create a satellite node upgrade task.

[0061] Specifically, requests to create satellite node upgrade tasks can be received through an open programmable interface (API) or a graphical user interface (GUI). There are no restrictions on the method of receiving these requests. Furthermore, requests can originate from system users, automated scheduled task scripts, or upstream operations and maintenance management systems; the method of creating these requests is also unrestricted.

[0062] Step S120: Based on the creation request, create a main task record with a unique identifier in the pre-built satellite node upgrade task table; and create a corresponding sub-task record for the target satellite node in the pre-built satellite node upgrade node status table; the sub-task record contains a unique identifier and a sub-task status; the unique identifier is used to determine the association between the main task record and the sub-task record.

[0063] Specifically, the received creation request is parsed, and key information is extracted. Then, a globally unique identifier is generated for the upgrade task. This unique identifier remains unchanged throughout the task's lifecycle, enabling unique identification and end-to-end tracking. Based on this unique identifier, a main task record with this unique identifier is created in the pre-built satellite node upgrade task table. Simultaneously, for each target satellite node specified in the creation request, a corresponding subtask record is created in the pre-built satellite node upgrade node status table. Each subtask record includes, but is not limited to, a unique identifier, the target satellite node's node identifier, and the subtask status. The fields included in the subtask record are not limited here.

[0064] Step S130: The upgrade request based on the master task record is sent to the target satellite node through the satellite-to-ground communication framework; based on the status information returned by the target satellite node, the subtask record corresponding to the target satellite node in the satellite node upgrade node status table is determined, and the subtask status in the subtask record is updated.

[0065] Specifically, the ground station sends independent upgrade requests to each target satellite node based on the upgrade request constructed from the master mission record, through the satellite-to-ground communication framework. The ground station receives and parses the status information returned by the target satellite nodes, accurately locates the corresponding sub-task record in the satellite node upgrade node status table based on the unique identifier and node identifier contained therein, and updates its sub-task status according to predefined state machine rules.

[0066] Through the above steps, a correlation mechanism between the main task and satellite node sub-tasks based on unique identifiers and a multi-dimensional state description method were established, which solved the problem of inaccurate satellite node upgrade state management and realized refined state tracking and observable task progress control throughout the entire life cycle of large-scale satellite node upgrades.

[0067] The steps described above are explained in detail below:

[0068] In some embodiments, step S120, which involves creating a corresponding subtask record for the target satellite node in a pre-built satellite node upgrade node status table, includes the following steps:

[0069] After sorting the main task records by their creation time and removing duplicates, they are inserted into the satellite node upgrade receiving queue.

[0070] The satellite node upgrade controller retrieves the main task record sequentially from the satellite node upgrade receive queue and creates a sub-task record associated with the main task record.

[0071] Specifically, firstly, after receiving the satellite node upgrade message from the task distribution module, the satellite node upgrade receiving queue queries the satellite node upgrade task table `upgrade_table` through the data read / write client. All created but unprocessed main upgrade tasks are retrieved, sorted by creation time, and deduplicated before being inserted into the queue, thus forming an ordered, non-duplicate queue of pending tasks. Among these, created but unprocessed tasks are those where the `created_at` field is not empty, but the `job_start_time` field is empty.

[0072] Secondly, the satellite node upgrade controller, acting as a consumer, sequentially retrieves task messages from the head of the satellite node upgrade receiving queue. The controller parses the task message and, based on the specified list of target satellite nodes, creates a corresponding subtask record for each target satellite node in the satellite node upgrade node status table. Each newly created subtask record contains a unique identifier for the main task, the node identifier of the target satellite node, and the initialized subtask status.

[0073] This embodiment ensures that all pending tasks are consumed by the controller in an orderly, fair, and non-duplicative manner, fundamentally avoiding data races and processing conflicts that may result from concurrent creation. The controller, as the sole consumer, retrieves tasks from the queue sequentially and is responsible for creating all associated subtask records, guaranteeing the consistency between the creation of subtask records and the main task information.

[0074] In some embodiments, step S130 involves sending an upgrade request based on the master mission record to the target satellite node, such as... Figure 3 As shown, it includes the following steps:

[0075] Step S131: Query the subtask record associated with the main task record based on the unique identifier of the main task record;

[0076] Step S132: Determine the upgrade request based on the subtask records associated with the main task record;

[0077] Step S133: Achievingly send an upgrade request to the target satellite node via the satellite-to-ground communication framework.

[0078] Specifically, firstly, based on the unique identifier of the main task record, the satellite node upgrade node status table is queried to obtain a set of all subtask records associated with the main task. Based on the retrieved set of subtask records and the information in the main task record, the controller independently constructs an upgrade request for each target satellite node.

[0079] Secondly, the controller calls the asynchronous send interface of the satellite-to-ground communication framework to send the constructed upgrade requests to their respective target satellite nodes. It also updates the subtask record in the satellite node upgrade node status table of the target satellite node, and updates the main task record in the satellite node upgrade task table, assigning a value to the job_start_time field in the main task record to indicate that the task has started processing.

[0080] Meanwhile, in order to reduce the number of database queries and operations, a local cache is added to record the status data of all nodes. For example, the data can be stored according to the unique identifier, node identifier, and node status of the main upgrade task record. The cache is queried, updated, and then written to the database in a unified manner.

[0081] This embodiment demonstrates a highly efficient, reliable, and scalable processing chain from task readiness to instruction distribution. By employing the asynchronous transmission mode of the satellite-to-ground communication framework, request distribution is decoupled from node responses, preventing delays or blockages in individual node communication from impacting the overall progress of batch tasks.

[0082] In some embodiments, after updating the subtask status corresponding to the target satellite node in the satellite node upgrade node status table based on the status information, the following steps are also included:

[0083] Based on the sub-task status of the target satellite node in the satellite node upgrade node status table and the predefined status aggregation rules, the main task status is determined; the main task status is recorded in the main task record.

[0084] Specifically, after the subtask status corresponding to the target satellite node is updated, the current status set of all subtask records associated with the same unique identifier of the main task is obtained by querying the satellite node upgrade node status table. Then, the status set is aggregated according to predefined status aggregation rules to obtain the main task status, and the main task status is updated in the corresponding main task record in the satellite node upgrade task table. The main task status can also be determined using a timed state snapshot method or a system-automated overwrite method; there are no restrictions on the method used to determine the main task status.

[0085] This embodiment achieves real-time aggregation of the execution status of distributed nodes into a unified overall task status. This allows ground operations personnel to intuitively grasp the global progress of batch upgrade tasks through a single master task status, thereby improving the efficiency of status monitoring for large-scale satellite node upgrade operations.

[0086] In some embodiments, the main task status is determined based on the subtask status of the target satellite node in the satellite node upgrade node status table and predefined status aggregation rules, including the following steps:

[0087] The subtask states are treated as states to be aggregated, and the states are aggregated according to the state aggregation rules to obtain the final aggregated state; the aggregated state is then used as the main task state.

[0088] Specifically, the states of all subtasks associated with the same unique identifier for the main task are collected in real time, forming a set of states to be aggregated. This set is used as input to call a predefined state aggregation rule for calculation. This rule converges multiple state values ​​in the set into a single state value that can represent the overall progress of the task, i.e., the aggregated state. Finally, this aggregated state is used as the main task state and updated to the corresponding record in the satellite node upgrade task table.

[0089] This embodiment achieves a mapping from massive, distributed node-level execution states to a unified, integrated task-level management and control state. This allows ground operations personnel to quickly and accurately grasp the overall progress and anomalies of batch upgrade tasks through a single main task status field, without needing to examine the detailed status of each satellite node individually.

[0090] In some embodiments, the state aggregation rules include:

[0091] The predefined progress state is the first priority. When the state to be aggregated contains a progress state, the lowest-level state value in the progress state is taken as the final aggregated state.

[0092] Predefined abnormal states have the second priority. When the state to be aggregated contains an abnormal state but does not contain a state in progress, the abnormal state will be used as the final aggregated state.

[0093] The completion state is the third priority. When the state to be aggregated includes the completion state but does not include the progress state or the abnormal state, the completion state will be the final aggregated state.

[0094] Specifically, when the status of any associated subtask changes, the status of all subtasks under the same main task is obtained in real time, forming a set of states to be aggregated. Then, the set of states to be aggregated is logically judged and converged according to a three-level priority rule: First, the set is filtered to see if there is an ongoing state; if an ongoing state exists, the lowest-level state value among the ongoing states is directly output as the aggregation result; if no ongoing state exists, it is checked for any abnormal state; if an abnormal state exists, any abnormal state among the abnormal states is output as the aggregation result; if neither an ongoing nor an abnormal state exists, but a completed state exists, the completed state is output as the aggregation result. Finally, this aggregation result is updated in the corresponding main task record of the satellite node upgrade task table.

[0095] This embodiment defines a set of deterministic and computationally efficient state convergence logic. It maps complex multi-node, multi-state scenarios into a single, intuitive state value with clear business semantics, enabling the ground control system to grasp the overall situation of batch upgrade tasks in real time and accurately with extremely low information processing overhead.

[0096] In some of these embodiments, the states include pending state, uploading state, and upgrading state; abnormal states include failure state, overwrite state, overwrite failure state, timeout state, cancellation state, and cancellation failure state.

[0097] The pending status indicates that the upgrade request has not yet been sent.

[0098] The "Uploading in Progress" status indicates that the upgrade request is in progress; the "Uploading in Progress" status is at a higher level than the "Pending" status.

[0099] The "Upgrading in Progress" status indicates the progress of the upgrade request; the "Upgrading in Progress" status is at a higher level than the "Uploading in Progress" status.

[0100] Failure status is used to indicate that the upgrade request was not completed correctly;

[0101] Override status is used to indicate that the upgrade request has successfully overridden the previous upgrade request.

[0102] The overwrite failure status is used to indicate that the upgrade request failed to overwrite the previous upgrade request.

[0103] Timeout status is used to indicate that the upgrade request failed to be sent or the database transaction failed to be processed.

[0104] The cancellation status indicates that the upgrade request was successfully cancelled.

[0105] The cancellation failure status is used to indicate that the cancellation of the upgrade request failed.

[0106] Specifically, the three sub-states of the upgrade process constitute an irreversible progressive sequence that strictly corresponds to the physical upgrade process. The "Pending Processing" state indicates that the task is ready but the satellite-to-ground link has not yet been activated for transmission; the "Uploading" state indicates that the upgrade request is being transmitted through the satellite-to-ground communication framework, and the "Uploading" state has a higher priority than the "Pending Processing" state in the state aggregation rules; the "Upgrading" state corresponds to the critical upgrade process being carried out by the satellite node, a stage that cannot be interrupted by external security measures, and the "Upgrading" state has a higher priority than the "Uploading" state in the state aggregation rules.

[0107] After the upgrade task is created, it enters an initial pending state. Then, the ground station sends an upgrade request to the target satellite node. For example... Figure 4As shown, after an upgrade request is sent, there are two different paths with different results.

[0108] The successful upgrade path is as follows: the upgrade request is successfully sent and the database transaction processing is normal. After receiving a confirmation message from the target satellite node, the status changes from pending to uploading. Once the satellite node begins executing the upgrade operation, the status changes to upgrading; when the upgrade is successfully completed, the status finally changes to completed.

[0109] The exception path is as follows: If an upgrade request fails to be sent while in the pending state, the task status is marked as timed out; if a database operation fails while in the upload state, the task status is marked as timed out; if a task cancellation request is initiated while in the pending or upload state, the status changes to canceled if successful, and canceled if unsuccessful; if a new upgrade request is received while in the pending or upload state, the status changes to overwrite if the old task is successfully overwritten, and overwrite if unsuccessful. If an upgrade fails while in the upgrade state, the task status changes to failed.

[0110] This embodiment constructs a deterministic state machine model covering the entire lifecycle and all possible scenarios of satellite node upgrades. By mapping each abnormal situation to an independent state with clear business semantics, the ground control system can accurately identify the causes of failures during the upgrade process. This provides a direct basis for automated anomaly diagnosis and targeted recovery strategies.

[0111] The present embodiment will now be described and illustrated through preferred embodiments.

[0112] Users create satellite nodes through open programmable interfaces to upgrade the main task, such as... Figure 5 As shown, a master task record is generated at the data storage location (such as a database) via a data read / write client. The satellite node receiving queue queries the master task record through the data read / write client, sorts and deduplicates it according to the master record's creation time, and inserts it into the queue. The satellite node upgrade controller retrieves the upgrade master task from the receiving queue and queries or creates the corresponding subtasks through the data read / write client. Afterward, a satellite node upgrade request is generated and sent to the satellite-to-ground communication framework.

[0113] The satellite-to-ground communication framework transmits satellite node upgrade requests to the target satellite node. Upon receiving the upgrade request, the target satellite node's module persists the data through the cache manager and upgrades the target satellite node. After the upgrade is complete, it returns status update information through the satellite-to-ground communication framework. The satellite node resource manager receives this information and updates the satellite node's status accordingly.

[0114] When the satellite node upgrade controller retrieves upgrade tasks according to queue priority and triggers an insertion event, such as Figure 6 As shown, first check if the node subtask corresponding to the current upgrade task already exists: if it exists, return success directly, indicating that the upgrade task has been processed; if it does not exist, create the node subtask corresponding to the upgrade task.

[0115] The system queries the subtasks corresponding to each satellite node under this upgrade task to determine if any subtasks are in progress. If an in progress subtask exists, its status is further checked to see if it is in a pending or uploading state. If so, a coverage request is sent to the satellite-to-ground communication framework, and then the success of the coverage request is verified: if the coverage request is successfully sent, the task status is set to the coverage state; if the coverage request fails to send, the task status is set to the coverage failure state. If the subtask status is neither in a pending nor uploading state, the step of sending the coverage request is skipped, and the task status is directly set to the coverage failure state. Afterward, the system continues to loop and check whether any subtasks corresponding to each satellite node are in progress.

[0116] If no subtask is in progress, an upgrade request is sent to each satellite node via the space-to-ground communication framework, and the success of the request transmission is determined: if the transmission fails, it checks if the retry count has been reached; if so, the status is set to timeout; otherwise, the transmission is retried. If the transmission succeeds, a database transaction operation is executed to update the data table, and the transaction operation is verified for success: if the transaction fails, it checks if the retry count has been reached; if so, the status is set to timeout; otherwise, the transaction is re-executed. If the transaction succeeds, the process ends.

[0117] If the user actively deletes the upgrade request, such as Figure 7 As shown, after a deletion event is triggered, the system first checks whether any subtasks with the same target version exist on each satellite node under the upgrade task. If none exist, it directly proceeds to the node status check stage. If they exist, it further determines whether their status is pending or uploading. If so, a cancellation request is sent to the corresponding satellite node via the satellite-to-ground communication framework. If cancellation is successful, the status is set to cancelled; otherwise, it is set to cancelled failed. If neither exists, the status is directly set to cancelled failed. Afterward, the system continues to loop, checking whether any subtasks with the same target version exist on each satellite node under the upgrade task.

[0118] Upon entering the node status check phase, determine if the node status has changed: If the node status has not changed, the process ends directly. If the node status has changed, execute the database transaction operation, update the data table, and verify if the transaction was successful: If the transaction fails, check if the retry count has been reached; if it has, set the task status to timeout; if not, re-execute the transaction. If the transaction succeeds, the process ends.

[0119] This embodiment provides a method for batch upgrading of satellite nodes applicable to the target satellite node side. Figure 8 This is a flowchart of the satellite node batch upgrade method applicable to the target satellite node side in this embodiment, as shown below. Figure 8 As shown, the process includes the following steps:

[0120] Step S310: Receive an upgrade request sent by the satellite-to-ground communication framework;

[0121] Step S320: Based on the satellite upgrade module, the upgrade request is parsed into a binary file, configuration data, and upgrade command;

[0122] Step S330: Based on the binary file, configuration data, and upgrade command, the target satellite node is upgraded using the satellite upgrade module.

[0123] Specifically, first, the protocol conversion middleware receives the upgrade request sent by the satellite-to-ground communication framework and assigns it to the satellite upgrade module. The satellite upgrade module performs a verification operation. If the verification fails, it sends an asynchronous upgrade failure message to the ground workstation through the satellite-to-ground communication framework. If the verification succeeds, it parses the upgrade request into a binary file, configuration data, and upgrade commands. The configuration data is necessary data simplified according to the satellite-to-ground communication application layer protocol; the satellite then restores it to YAML for use. The upgrade command includes the unique identifier of the main upgrade task, node identifier, node name, and checksum, etc. There are no restrictions on the types of fields included in the upgrade command.

[0124] Secondly, the parsed files are persisted to a local database. The satellite upgrade module retrieves upgrade instructions from the database and updates the upgrade status to "upgrading in progress." If multiple upgrade instructions exist, the one with the latest timestamp is executed. Asynchronous messages indicating successful upgrades for other instructions are sent to the ground via the satellite-to-ground communication scheduling framework, and the mission status is changed to "completed."

[0125] Finally, the configuration data is restored to a complete YAML file, then the binary file is copied to the running directory and the configuration is updated. The satellite core process is then restarted to complete the upgrade. Upon successful upgrade, a status message indicating success is sent to the ground station via the satellite-to-ground communication framework, and binary files with timestamps earlier than this upgrade are automatically cleaned up. If sending the asynchronous message via the satellite-to-ground communication framework fails, multiple retries are performed. If all retries fail, this step is stopped until the next upgrade request is received.

[0126] This embodiment implements an autonomous and reliable upgrade process on the target satellite node side. Local databases and file systems ensure the recoverability of the task state in case of crashes, and resource reclamation mechanisms guarantee the integrity of the upgrade process and the sustainability of storage space, enabling the satellite node to independently and securely complete software upgrade operations.

[0127] In some embodiments, after parsing the upgrade request into binary files, configuration data, and upgrade commands, the following steps are included:

[0128] Save the binary file to the specified local cache directory;

[0129] The configuration data and upgrade commands are persisted to the local database through the cache manager.

[0130] Specifically, after parsing the upgrade request, the target satellite node transforms the volatile communication data into a persistent local state. The binary file is transferred to an isolated cache directory by timestamp, while the configuration data and upgrade commands are persisted to the local database through the cache manager, and then confirmed receipt is sent via the satellite-to-ground communication framework.

[0131] Data persistence is implemented to prevent data loss and upgrade failures caused by factors such as normal satellite shutdown upon departure or unexpected crashes and restarts of the satellite upgrade module. Once the satellite upgrade module recovers, the node upgrade tasks in the local database can be queried directly through the cache manager, and the upgrade operation can continue. If the satellite core process fails to run stably after the upgrade, the user must submit another upgrade task request to re-execute the upgrade process.

[0132] In this embodiment, the target satellite node achieves upgrade task reception and upgrade data persistence. Through the coordinated operation of the satellite upgrade module and the cache manager, even if the satellite restarts at any time after receiving the file but before executing the upgrade, it can restore the task context from the local database. This avoids the loss of upgrade tasks due to single points of failure on the satellite and significantly improves the robustness of the entire upgrade process.

[0133] This embodiment also provides a satellite node batch upgrade system, including a satellite-to-ground communication framework, ground workstations connected to the satellite-to-ground communication framework, and at least one target satellite node. The ground workstation is configured to execute any of the satellite node batch upgrade methods applicable to the ground workstation side in the above embodiments. The target satellite node is configured to execute any of the satellite node batch upgrade methods applicable to the target satellite node side in the above embodiments.

[0134] It should be noted that all information and data involved in this application are authorized by the user or fully authorized by all parties and will be used legally.

[0135] It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. All other embodiments derived by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application.

[0136] Obviously, the accompanying drawings are merely some examples or embodiments of this application. Those skilled in the art can apply this application to other similar situations based on these drawings without any creative effort. Furthermore, it is understood that although the work done in this development process may be complex and lengthy, for those skilled in the art, certain design, manufacturing, or production modifications made based on the technical content disclosed in this application are merely conventional technical means and should not be considered as insufficient disclosure of this application.

[0137] The term "embodiment" in this application refers to a specific feature, structure, or characteristic described in connection with an embodiment that may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily imply the same embodiment, nor does it imply that it is mutually exclusive with or independent of other embodiments. It will be clearly or implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0138] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of patent protection. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims

1. A method for batch upgrading satellite nodes, characterized in that, A system suitable for batch upgrades of satellite nodes, the system comprising a satellite-to-ground communication framework and ground workstations respectively connected to the satellite-to-ground communication framework, and at least one target satellite node; The method is applicable to the ground workstation side; the method includes: Receive requests to create satellite node upgrade tasks; According to the creation request, a main task record with a unique identifier is created in the pre-built satellite node upgrade task table; and a corresponding sub-task record is created for the target satellite node in the pre-built satellite node upgrade node status table; the sub-task record contains the unique identifier and the sub-task status; the unique identifier is used to determine the association between the main task record and the sub-task record; The upgrade request, constructed based on the master mission record, is sent to the target satellite node through the satellite-to-ground communication framework; Based on the status information returned by the target satellite node, determine the subtask record corresponding to the target satellite node in the satellite node upgrade node status table, and update the subtask status in the subtask record.

2. The method for batch upgrading satellite nodes according to claim 1, characterized in that, The step of creating a corresponding subtask record for the target satellite node in the pre-built satellite node upgrade node status table includes: After sorting the main task records according to their creation time and removing duplicates, they are inserted into the satellite node upgrade receiving queue. The main task record is obtained sequentially from the satellite node upgrade receiving queue by the satellite node upgrade controller, and the sub-task record associated with the main task record is created based on the main task record.

3. The method for batch upgrading satellite nodes according to claim 1, characterized in that, Sending the upgrade request constructed based on the master mission record to the target satellite node includes: The subtask record associated with the main task record is queried based on the unique identifier of the main task record; The upgrade request is determined based on the sub-task record associated with the main task record; The upgrade request is sent asynchronously to the target satellite node through the aforementioned satellite-to-ground communication framework.

4. The method for batch upgrading satellite nodes according to claim 1, characterized in that, After updating the sub-task status corresponding to the target satellite node in the satellite node upgrade node status table based on the status information, the method further includes: Based on the sub-task status of the target satellite node in the satellite node upgrade node status table and the predefined status aggregation rules, the main task status is determined; the main task status is recorded in the main task record.

5. The satellite node batch upgrade method according to claim 4, characterized in that, The determination of the main task status based on the sub-task status of the target satellite node in the satellite node upgrade node status table and predefined status aggregation rules includes: The subtask state is taken as the state to be aggregated, and the state is aggregated according to the state aggregation rule to obtain the final aggregated state; the aggregated state is taken as the main task state.

6. The method for batch upgrading satellite nodes according to claim 5, characterized in that, The state aggregation rules include: The predefined progress state is the first priority. When the state to be aggregated contains the progress state, the lowest level state value in the progress state is taken as the final aggregated state. The predefined abnormal state is the second priority. When the state to be aggregated contains the abnormal state but does not contain the state in progress, the abnormal state is taken as the final aggregated state. The completion state is the third priority. When the state to be aggregated includes the completion state but does not include the progress state or the abnormal state, the completion state is taken as the final aggregation state.

7. The method for batch upgrading satellite nodes according to claim 6, characterized in that, The states in progress include pending, uploading, and upgrading; the abnormal states include failure, overwrite, overwrite failure, timeout, cancellation, and cancellation failure. The pending status is used to indicate that the upgrade request has not been sent; The "Uploading in Progress" status is used to characterize the status of the upgrade request being uploaded; the "Uploading in Progress" status level is higher than the "Pending Processing" status. The "Upgrading in Progress" status is used to characterize the status of the upgrade request execution; the "Upgrading in Progress" status level is higher than the "Uploading in Progress" status. The failure status is used to indicate that the upgrade request was not completed correctly; The coverage status is used to characterize the state in which the upgrade request successfully overwrites the previous upgrade request. The overwrite failure status is used to characterize the state in which the upgrade request overwrites the previous failed upgrade request. The timeout status is used to characterize the state where the upgrade request failed to be sent or the database transaction processing failed. The cancellation status is used to indicate that the upgrade request was successfully cancelled; The cancellation failure status is used to indicate that the cancellation of the upgrade request failed.

8. A method for batch upgrading satellite nodes, characterized in that, A system suitable for batch upgrades of satellite nodes, the system comprising a satellite-to-ground communication framework and ground workstations respectively connected to the satellite-to-ground communication framework, and at least one target satellite node; The method is applicable to the target satellite node side; the method includes: Receive an upgrade request sent by the satellite-to-ground communication framework; the upgrade request is constructed based on the master task record; the master task record has a unique identifier; Based on the satellite upgrade module, the upgrade request is parsed into binary files, configuration data, and upgrade commands; Save the binary file to the local specified cache directory; The configuration data and the upgrade command are persisted to the local database through the cache manager; Based on the binary file, the configuration data, and the upgrade command, the target satellite node is upgraded using the satellite upgrade module.

9. A satellite node batch upgrade system, comprising a satellite-to-ground communication framework and ground workstations respectively connected to the satellite-to-ground communication framework, and at least one target satellite node; characterized in that, The ground workstation is configured to perform the steps of the satellite node batch upgrade method according to any one of claims 1 to 7, and the target satellite node is configured to perform the steps of the satellite node batch upgrade method according to claim 8.

Images