Digital intelligent cloud edge software pushing method and system for satellite communication scene

Abstract

The invention provides a digital intelligent cloud edge software pushing method and system for a satellite communication scene, and relates to the field of satellite communication, and the method comprises the following steps: predicting to obtain a bandwidth state and a link available time period of a satellite within a set time length in the future; sending a detection signaling, and obtaining target resource state information from feedback information responding to the detection signaling; the target resource state information comprises a software deployment environment, an available storage space and a previous interrupt retention data volume of a software package; judging whether all software pushing conditions are met or not; and when the target resource state information meets the software pushing condition, performing software pushing in the link available time period within the set duration, and dynamically adjusting the code rate of software pushing according to the bandwidth state.

Description

Technical Field

[0001] This invention relates to the field of satellite communication, and in particular to a digital cloud-edge software push method and system for satellite communication scenarios. Background Technology

[0002] The "Digital and Intelligent Infrastructure Cloud Base" is a comprehensive platform that uses a cloud computing platform as its foundation to provide computing power support and cloud-native services such as big data and artificial intelligence for upper-layer application businesses. As the central cloud, the "Digital and Intelligent Infrastructure Cloud Base" is the core carrier of cloud-edge collaboration, possessing functions such as resource pooling, data aggregation, and basic computing power support. However, the existing cloud base is mainly adapted to communication scenarios such as terrestrial fiber optics and 5G networks, and has not been optimized for satellite communication scenarios.

[0003] Existing cloud-edge software push methods for satellite scenarios typically involve simply adapting ground-based cloud-edge push solutions (such as push based on protocols like FTP) to satellite links. The core process is as follows: the cloud directly generates a complete software installation package and initiates a "one-size-fits-all" push to edge nodes via the satellite link. During the push process, the completion is determined solely by the "send-confirm" mechanism, without dynamically adjusting based on the characteristics of the satellite link and the status of the edge nodes.

[0004] Furthermore, the cloud pushes software update packages to all edge nodes at specific intervals, using a fixed bitrate and without considering satellite bandwidth fluctuations; and the software packages are transmitted as complete files. Edge nodes only provide feedback after receiving the update; if the link is interrupted midway, the update needs to be re-pushed.

[0005] Therefore, existing cloud-edge software push methods for satellite scenarios have the following drawbacks:

[0006] 1. Using complete software packages for push notifications without considering satellite bandwidth limitations results in long bandwidth consumption times for large software packages (e.g., over 100MB) during a single push. This leads to low push efficiency and significant bandwidth waste.

[0007] 2. Satellite links are prone to temporary interruptions due to weather, obstructions, electromagnetic interference, etc., and have weak resilience to link interruptions. Current technology lacks a mechanism for resuming interrupted transmissions, requiring the retransmission of the entire packet after an interruption. However, the bandwidth may be even lower after the satellite link is restored, further increasing retransmission time and resulting in high retransmission costs.

[0008] 3. Because satellite bandwidth fluctuates dynamically with orbital position and weather conditions, current technology uses a fixed bitrate for push notifications. When the bitrate exceeds the real-time bandwidth, data packets are lost, ultimately leading to push failure. This results in a failure to adapt to dynamic changes in the link, leading to a high push failure rate.

[0009] 4. Edge node systems vary significantly in terms of computing power, storage, and network. Existing technologies do not assess node resources before pushing data, resulting in a lack of edge node resource matching. This leads to some nodes failing to install due to insufficient storage after receiving the data, wasting push bandwidth. Consequently, remote installation is prone to failure. Summary of the Invention

[0010] To address the technical problems existing in the prior art, the present invention aims to provide a digital and intelligent cloud-edge software push method and system for satellite communication scenarios, ensuring that the pushed software packages match the resources of edge nodes and improving the local installation success rate. It also aims to achieve dynamic adaptation of the push strategy to the satellite link, reducing the push failure rate.

[0011] To achieve the above-mentioned objectives, this invention provides a digital cloud-edge software push method for satellite communication scenarios, comprising the following steps:

[0012] The bandwidth status and link availability of satellites within a set future timeframe can be predicted.

[0013] Send a probe signaling message and obtain the target resource status information from the feedback information in response to the probe signaling message;

[0014] The target resource status information includes the software deployment environment, available storage capacity, and the amount of data retained from previous interruptions of the software package.

[0015] Determine if all software push conditions are met;

[0016] The software push conditions include: the software deployment environment matches the deployment environment required by the software to be pushed; and after subtracting the portion of the data retained before the software package was interrupted, the remaining data amount of the software package to be pushed is less than the available storage amount.

[0017] When the target resource status information meets the software push conditions, software push is performed during the link availability period within the set time period, and the software push bitrate is dynamically adjusted according to the bandwidth status.

[0018] According to a technical solution of the present invention, the intelligent cloud-edge software push method for satellite communication scenarios further includes:

[0019] Before sending the probe signal, compare the version of the software to be pushed with the pre-stored current software version of the target software;

[0020] If the version of the software to be pushed is higher than the current version of the target software, then the probe signaling is sent; otherwise, the probe signaling is not sent.

[0021] According to a technical solution of the present invention, in the intelligent cloud-edge software push method for satellite communication scenarios, the bandwidth status and link availability period of the satellite within a set future time period are predicted, specifically:

[0022] Based on the satellite link status prediction network, historical satellite data is used as input to predict the satellite's bandwidth status and link availability time in the next 1 to 3 hours.

[0023] The satellite link state prediction network is one of the pre-trained Long Short-Term Memory Network (LSTM) or Time Difference Convolutional Network (TCN).

[0024] The historical data consists of satellite orbit position, weather, bandwidth, and interruption records for a set historical date; the bandwidth status is represented by a bandwidth-time curve.

[0025] According to a technical solution of the present invention, in the intelligent cloud-edge software push method for satellite communication scenarios, the following steps are included before software push:

[0026] The software package to be pushed is split into multiple software sub-blocks according to the preset sub-block data volume; then, according to the preset priority standard, the multiple software sub-blocks are divided into different priorities.

[0027] According to a technical solution of the present invention, in the intelligent cloud-edge software push method for satellite communication scenarios, the specific process of software push includes:

[0028] According to priority order, the corresponding software sub-blocks are transmitted sequentially;

[0029] After transmitting the last software sub-block, receive the integrity verification result of the software copy;

[0030] The software copy is generated by splicing together all the transmitted software sub-blocks;

[0031] If the integrity verification of the software copy passes, the software push is confirmed to be complete;

[0032] Otherwise, retransmit the corresponding software sub-block.

[0033] According to a technical solution of the present invention, in the intelligent cloud-edge software push method for satellite communication scenarios, the specific process of software push further includes:

[0034] Record the progress of software sub-block transmission when the link is interrupted;

[0035] When the link is restored, transmission is resumed according to the transmission progress of the software sub-block.

[0036] According to a technical solution of the present invention, in the intelligent cloud-edge software push method for satellite communication scenarios, the software push conditions further include:

[0037] The amount of data to be pushed by the software should not exceed the product of the available link time period and the corresponding bandwidth.

[0038] According to a technical solution of the present invention, in the intelligent cloud-edge software push method for satellite communication scenarios, the bitrate of software push is dynamically adjusted based on bandwidth status. The specific process includes:

[0039] When the bandwidth changes, the bitrate is adjusted to match the preset bandwidth-bitrate mapping relationship.

[0040] This invention also provides a digital cloud-edge software push system for satellite communication scenarios, including a cloud center platform, the cloud center platform comprising:

[0041] The satellite link management module is used to predict the bandwidth status and link availability of satellites within a set time period in the future;

[0042] The software push module is used for:

[0043] Send a probe signaling message and obtain the target resource status information from the feedback information in response to the probe signaling message;

[0044] The target resource status information includes the software deployment environment, available storage capacity, and the amount of data retained from previous interruptions of the software package.

[0045] Determine if all software push conditions are met;

[0046] The software push conditions include: the software deployment environment matches the deployment environment required by the software to be pushed; and after subtracting the portion of the data retained before the software package was interrupted, the remaining data amount of the software package to be pushed is less than the available storage amount.

[0047] When the target resource status information meets the software push conditions, software push is performed during the link availability period within the set time period, and the software push bitrate is dynamically adjusted according to the bandwidth status.

[0048] According to a technical solution of the present invention, a digital cloud-edge software push system for satellite communication scenarios further includes multiple edge nodes, wherein the edge nodes include:

[0049] Data receiving server, used for:

[0050] Respond to the probe signaling and send back feedback information including target resource status information;

[0051] After receiving the software package, perform an integrity check on the software package and send out the integrity check result;

[0052] The target container environment is used to install packages that have passed integrity verification.

[0053] Compared with the prior art, the present invention has the following advantages:

[0054] 1. Based on AI algorithms, analyze historical link data to predict future satellite link bandwidth fluctuation trends in real time, providing a basis for push scheduling. Improve the bandwidth utilization efficiency of cloud-edge software push in satellite communication scenarios, and reduce invalid pushes and redundant transmissions;

[0055] 2. Divide the software package into multiple sub-blocks as needed, and sort them according to the requirements of edge nodes and the importance of the sub-blocks. Only push the necessary sub-blocks to the nodes that need to be updated. This enhances the resilience of the push process against link interruptions and reduces the cost of retransmission after an interruption.

[0056] 3. Before pushing, obtain the real-time status of edge nodes through lightweight signaling. If the node status information is insufficient, pause the push and report back to the cloud. Ensure that the pushed software package matches the edge node resources to improve the local installation success rate.

[0057] 4. The push period is selected based on link prediction results. During the push process, the link status is monitored in real time. If bandwidth suddenly drops, the bit rate is automatically reduced; if the link is interrupted, the received sub-blocks are recorded, and only the unfinished portion is resumed upon recovery. The push scheme is automatically adjusted to adapt to dynamically changing satellite communication links, reducing the push failure rate. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are merely some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative effort.

[0059] Figure 1 The diagram illustrates the structure of a digital cloud-edge software push system for satellite communication scenarios according to an embodiment of the present invention.

[0060] Figure 2 A flowchart illustrating a digital cloud-edge software push method for satellite communication scenarios according to an embodiment of the present invention;

[0061] Figure 3The diagram illustrates the principle of software resume transmission after link interruption and recovery in a digital cloud-edge software push method for satellite communication scenarios according to an embodiment of the present invention. Detailed Implementation

[0062] The description of the embodiments in this specification should be taken in conjunction with the accompanying drawings, which should form part of the complete specification. In the drawings, the shape or thickness of the embodiments may be exaggerated and may be indicated in a simplified or convenient manner. Furthermore, parts of the various structures in the drawings will be described separately; it is worth noting that elements not shown in the figures or not described in words are in a form known to those skilled in the art.

[0063] The descriptions of the embodiments herein, including any references to directions and orientations, are for ease of description only and should not be construed as limiting the scope of the invention. The following description of preferred embodiments involves combinations of features, which may exist independently or in combination; the invention is not particularly limited to the preferred embodiments. The scope of the invention is defined by the claims. Specific Implementation Method 1

[0065] like Figures 1-3 As shown, the present invention provides a digital cloud-edge software push method for satellite communication scenarios, characterized by the following steps:

[0066] S1. Predict the bandwidth status and link availability of satellites within a set future timeframe;

[0067] S3. Send a probe signaling message and obtain the target resource status information from the feedback information of the response to the probe signaling message;

[0068] Target resource status information includes the software deployment environment, available storage, and the amount of data retained from previous interruptions of the software package;

[0069] Determine if all software push conditions are met;

[0070] The conditions for software push include: the software deployment environment matches the deployment environment required by the software to be pushed; and after considering the amount of data retained by the software package during previous interruptions, the remaining amount of data in the software package to be pushed is less than the available storage.

[0071] S4. When the target resource status information meets the software push conditions, software push is performed during the link availability period within the set time, and the software push bitrate is dynamically adjusted according to the bandwidth status.

[0072] In this embodiment, such as Figure 2 As shown, the execution process of the method is as follows (executed in the order of S1, S3, and S4):

[0073] S1. Satellite link status prediction:

[0074] The cloud center platform predicts and outputs bandwidth curves (i.e., time-bandwidth correspondence) and link availability (including: link availability periods, such as 10:00-10:15; link interruption periods, such as 10:15-10:20) for the next hour based on historical satellite data. This provides a basis for push scheduling.

[0075] Store the satellite link status prediction results for use in subsequent steps.

[0076] S3. Target Node Resource and Status Assessment:

[0077] The cloud center platform sends a lightweight probe signaling message to the target node. This probe signaling message includes instructions such as the deployment environment, available storage, and the size of the received software package. The signaling message is transmitted through the satellite control link (occupying less than 10KB of bandwidth).

[0078] After receiving the probe signaling, the target node returns target resource status information, such as "Operating system CentOS, Python 3.6, available storage is 200MB, and information on the software packages remaining from the last interruption that have been received."

[0079] If the deployment environment matches the requirements of the software package to be installed, and the available storage is greater than or equal to the remaining total size of the software package (e.g., if the remaining storage is 170MB and the available storage is 200MB, which is greater than or equal to 170MB), then the target node will be included in the push queue; otherwise, it will be marked as a node not to be pushed for the time being.

[0080] S4. Dynamic Push Execution and Adjustment:

[0081] Based on the satellite link status prediction results of S1, the cloud center platform selects the optimal push time period (such as predicting that the bandwidth will be stable at 3Mbps from 10:00 to 10:30) to establish a satellite link and push software packages.

[0082] Furthermore, when the cloud center platform pushes software packages, it monitors the current satellite bandwidth in real time (e.g., collecting data once every 5 seconds). If the actual bandwidth is lower than the predicted value, it automatically reduces the bitrate of the software push to the target bitrate.

[0083] This implementation method, through link prediction and dynamic bitrate adjustment, can avoid packet loss caused by insufficient bandwidth and adapt to the fluctuating characteristics of satellite links.

[0084] By using probe signaling to detect the resource status of target nodes, it is possible to ensure that the transmitted software meets the requirements of the node deployment environment, reducing invalid operations such as "unable to install after reception." This significantly improves the success rate of remote software installation. Specific Implementation Method Two

[0086] This embodiment is a further explanation of embodiment one. This embodiment also includes:

[0087] S2. Before sending the probe signaling, compare the version of the software to be pushed with the current software version of the pre-stored push target;

[0088] If the version of the software to be pushed is higher than the current version of the target software, a probe signaling is sent; otherwise, no probe signaling is sent.

[0089] In this embodiment, before sending the probe signaling, the cloud center platform compares the current version of the target node software (the software to be sent is version V2.0, but some target nodes have version V1.8, which requires an update; while some target nodes have version V2.0, which does not require an update) pre-stored in the cloud center platform, filters out the target nodes that only need updating, and forms a list of target nodes to be pushed. The software is only pushed to the target nodes that need updating. Specific Implementation Method 3

[0091] This embodiment is a further explanation of embodiment two. In this embodiment, in S1, the bandwidth status and link availability period of the satellite within a set future time period are predicted, specifically as follows:

[0092] Based on the satellite link status prediction network, historical satellite data is used as input to predict the satellite's bandwidth status and link availability time in the next 1 to 3 hours.

[0093] The satellite link state prediction network is one of the pre-trained Long Short-Term Memory (LSTM) network and Time Difference Convolutional Network (TCN).

[0094] Historical data consists of satellite orbital positions, weather, bandwidth, and interruption records for a set historical date; bandwidth status is represented by a bandwidth-time curve.

[0095] In this embodiment, the cloud center platform collects historical satellite data (such as satellite orbit position, weather, bandwidth, and interruption records for the past 7 days), and uses the LSTM cloud center platform to predict and output the bandwidth curve (i.e., time-bandwidth correspondence) and link availability (including link availability periods, such as 10:00-10:15 link availability; and link interruption periods, such as 10:15-10:20 potential interruption) based on the historical satellite data.

[0096] The cloud center platform stores the satellite link status prediction results for use in subsequent steps.

[0097] The LSTM described above can be replaced by other similar networks, such as GRU and TCN. Usually, no special modifications are needed; only the appropriate hyperparameters need to be set based on historical satellite data during training, and fine-tuning should be performed, according to existing techniques in the field. Specific Implementation Method Four

[0099] This embodiment is a further explanation of embodiments one to three. In this embodiment, before pushing the software in S4, the following steps are also included:

[0100] The software package to be pushed is split into multiple software sub-blocks according to the preset sub-block data volume; then, according to the preset priority standard, the multiple software sub-blocks are divided into different priorities.

[0101] In this embodiment, in order to improve the efficiency of pushing software packages and reduce the probability of needing to re-push software packages due to satellite link interruption, the software packages to be pushed can be split in step S2 based on rules such as data volume threshold and division of functional modules in the software package.

[0102] The cloud center platform obtains the software packages to be pushed (such as version V2.0, size 200MB) from the software package management server. It can split the packages into 20 software sub-blocks (numbered B1-B20) at 10MB / block and create a priority standard according to the requirements. Based on the priority standard, the software sub-blocks are marked with importance (e.g., B1-B5 are core functional blocks with the highest priority; B6-B20 are additional functional blocks with the second highest priority).

[0103] The software package is split into multiple software sub-blocks, which can be sorted according to the needs of the target node (whether an update is needed) and the importance of the software sub-blocks (core functional blocks take priority). Only the necessary software sub-blocks are pushed to the target nodes that need to be updated.

[0104] By dividing the software into multiple (small-sized) sub-blocks and pushing them on demand to target nodes that only need updating, invalid transmissions can be reduced, and the number of nodes that can be pushed can be increased under the same bandwidth. This significantly improves bandwidth utilization. Detailed Implementation Method Five

[0106] This embodiment is a further explanation of embodiment four. In this embodiment, the specific process of software push includes:

[0107] S4.1. Transmit the corresponding software sub-blocks in sequence according to priority.

[0108] S4.2 After transmitting the last software sub-block, receive the integrity verification result of the software copy;

[0109] The software copy is generated by concatenating all the transmitted software sub-blocks;

[0110] S4.3 If the integrity verification of the software copy passes, then confirm that the software push is complete;

[0111] Otherwise, retransmit the corresponding software sub-block.

[0112] This embodiment involves the specific implementation of step S4, which assumes that the software package to be pushed is split on the cloud center platform.

[0113] After the cloud center platform establishes a satellite link with the target node, it sorts the software sub-blocks according to priority (e.g., push B4-B5 first, then push B6-B20).

[0114] After receiving all software sub-blocks, the target node assembles them into a software copy and performs integrity verification using methods such as MD5 check, SHA-256 hash check, and CRC cyclic redundancy check. After verification, it sends the integrity verification result to the cloud center platform. If the integrity verification passes, the target node installs the software and sends a "successfully installed" message to the cloud center platform. If the integrity verification fails, the result includes the identifier of the missing software sub-blocks (such as hash values, UUIDs, etc.). Upon receiving the integrity verification result, the cloud center platform retransmits the corresponding software sub-blocks. After retransmission, the target node performs integrity verification again until the software is successfully installed or the set number of retransmissions is reached. Specific Implementation Method Six

[0116] This embodiment is a further explanation of embodiment five. In this embodiment, the specific process of software push also includes:

[0117] Record the progress of software sub-block transmission when the link is interrupted;

[0118] When the link is restored, transmission is resumed according to the progress of software sub-block transmission.

[0119] In this embodiment, step S4 involves handling the situation where a link interruption occurs during the process of pushing the software package.

[0120] like Figure 3 As shown, if the link is interrupted (e.g., interrupted at 10:10), the cloud center platform records that sub-blocks have been pushed (e.g., B4 has been completely transmitted, and B5 has been transmitted to 80%); after the link is restored (10:15), only the remaining 20% ​​of B5 and subsequent software sub-blocks will continue to be transmitted.

[0121] The aforementioned breakpoint resume mechanism ensures that after an interruption, only the incomplete software sub-blocks need to be transmitted (e.g., after an interruption at 50%, only 50% needs to be resumed, instead of 100%). This significantly reduces the amount of data to be resumed. Detailed Implementation Method Seven

[0123] This embodiment is a further explanation of one of embodiments one through three, five through six. In this embodiment, the software push conditions also include:

[0124] The amount of data to be pushed by the software should not exceed the product of the available link time period and the corresponding bandwidth.

[0125] In this embodiment, by calculating and ensuring that the data volume of the software to be pushed is no greater than 90% of the product of the available link time period and the corresponding bandwidth (reserving 10% redundancy), it is ensured that the transmission will not be interrupted due to the data volume exceeding the link carrying capacity during the software push process, thus ensuring the stability and reliability of the software push. Detailed Implementation Method Eight

[0127] This embodiment is a further explanation of embodiment seven. In this embodiment, the bandwidth status in S4 dynamically adjusts the bitrate pushed by the software. The specific process includes:

[0128] When the bandwidth changes, the bitrate is adjusted to match the preset bandwidth-bitrate mapping relationship.

[0129] In this implementation, the cloud center platform triggers a bitrate adjustment process when it detects that the actual bandwidth (e.g., 2.5Mbps) is lower than the predicted value.

[0130] The preset bandwidth-bitrate mapping relationship can be a preset bandwidth-bitrate mapping table (e.g., when the actual bandwidth is 2.5Mbps, the push bitrate is reduced from 3Mbps to 2.5Mbps), or a mapping relationship calculated by a formula, or a mapping relationship obtained based on a prediction model. Detailed Implementation Method Nine

[0132] This embodiment of a digital cloud-edge software push system for satellite communication scenarios includes a cloud center platform, which includes:

[0133] The satellite link management module is used to predict the bandwidth status and link availability of satellites within a set time period in the future;

[0134] The software push module is used for:

[0135] Send probe signals and obtain target resource status information from the feedback information in response to the probe signals;

[0136] Target resource status information includes the software deployment environment, available storage, and the amount of data retained from previous interruptions of the software package;

[0137] Determine if all software push conditions are met;

[0138] The conditions for software push include: the software deployment environment matches the deployment environment required by the software to be pushed; and after considering the amount of data retained by the software package during previous interruptions, the remaining amount of data in the software package to be pushed is less than the available storage.

[0139] When the target resource status information meets the software push conditions, the software is pushed during the link availability period within the set time, and the software push bitrate is dynamically adjusted according to the bandwidth status. Detailed Implementation Method Ten

[0141] This embodiment is a further explanation of embodiment nine. In this embodiment, multiple edge nodes are also included, including:

[0142] Data receiving server, used for:

[0143] Respond to probe signaling and send back feedback information including target resource status information;

[0144] After receiving the software package, perform an integrity check on the software package and send out the integrity check result;

[0145] The target container environment is used to install packages that have passed integrity verification.

[0146] In this embodiment, the intelligent cloud-edge software push method and system for satellite communication scenarios of the present invention are implemented based on an intelligent cloud infrastructure.

[0147] Overall architecture as follows Figure 1 As shown, the intelligent cloud base serves as the cloud center platform, and the edge nodes serve as the target nodes, forming a cloud-edge collaborative software remote push architecture through communication satellites.

[0148] The intelligent cloud infrastructure is based on a cloud platform and includes two modules.

[0149] 1. Software push module, which has the capabilities of software splitting, software push, and power outage resume download;

[0150] II. Satellite link management module, which has functions such as link availability, link establishment, and bandwidth prediction.

[0151] An edge node consists of two parts:

[0152] 1. Data receiving server, responsible for receiving data from communication satellites and pushing it to the installation environment;

[0153] 2. The target container environment is the target container for the software (application) to be run on the edge node.

[0154] The specific implementation process is as follows:

[0155] S1. Satellite link status prediction:

[0156] The satellite link management module predicts and outputs the bandwidth curve (i.e., the time-bandwidth correspondence) and link availability (including: link availability periods, such as 10:00-10:15; link interruption periods, such as 10:15-10:20) for the next hour based on historical satellite data. This provides a basis for push scheduling.

[0157] The satellite link status prediction results are stored in the link status database of the satellite link management module for use in subsequent steps.

[0158] S2. The software push module splits the software package to be pushed based on rules such as data volume threshold and the division of functional modules in the software package.

[0159] The software push module obtains the software package to be pushed (e.g., version V2.0, size 200MB) from the software package management server. It can be divided into 20 software sub-blocks (numbered B1-B20) at 10MB / block. A priority standard is created according to the requirements, and the importance of the software sub-blocks is marked based on the priority standard (e.g., B1-B5 are core functional blocks with the highest priority; B6-B20 are additional functional blocks with the second highest priority).

[0160] The software package is split into multiple software sub-blocks, which can be sorted according to the needs of edge nodes (whether an update is needed) and the importance of the software sub-blocks (core functional blocks take priority). Only the necessary software sub-blocks are pushed to the edge nodes that need to be updated.

[0161] The software push module compares the current version of the edge node software pre-stored in the cloud center platform (the software to be sent is version V2.0, but some edge nodes are version V1.8, so an update is needed; while some edge nodes are version V2.0, so no update is needed), filters out the target nodes that only need updating, and forms a list of edge nodes to be pushed. The software is only pushed to the edge nodes that need updating.

[0162] S3. Edge Node Resource and Status Assessment:

[0163] The satellite link management module sends lightweight probe signals to edge nodes. These probe signals include instructions such as the deployment environment, available storage, and the size of received software packages. The signals are transmitted via the satellite control link (occupying less than 10KB of bandwidth).

[0164] After receiving the probe signaling, the edge node feeds back the target resource status information of the edge node, such as "Operating system CentOS, Python 3.6, available storage is 200MB, B1-B3 (the numbers of the package sub-blocks left over from the last interruption) have been received".

[0165] The software push module determines whether the deployment environment matches the requirements of the software package to be installed, and whether the available storage is greater than or equal to the remaining total size of the software package. For example, if the remaining storage is 170MB and the available storage is 200MB, which is greater than or equal to 170MB, then the edge node is included in the push queue; otherwise, it is marked as a node that will not be pushed for the time being.

[0166] S4. Dynamic Push Execution and Adjustment:

[0167] Based on the satellite link status prediction results from S1, the satellite link management module selects the optimal push period (e.g., predicting that the bandwidth will be stable at 3Mbps from 10:00 to 10:30) to establish a satellite link and push software packages.

[0168] Furthermore, when the satellite link management module pushes the software package, it monitors the current satellite bandwidth in real time (e.g., collecting data once every 5 seconds). If the actual bandwidth is lower than the predicted value, it automatically reduces the bitrate of the software push to the target bitrate.

[0169] If the link is interrupted (e.g., interrupted at 10:10), the cloud center platform records that sub-blocks have been pushed (e.g., B4 has been completely transmitted, and B5 has been transmitted to 80%). After the link is restored (10:15), only the remaining 20% ​​of B5 and subsequent software sub-blocks will continue to be transmitted.

[0170] After receiving all software sub-blocks, the data receiving server at the edge node assembles them into a software copy and performs integrity verification using methods such as MD5 check, SHA-256 hash check, and CRC cyclic redundancy check. After verification, it sends the integrity verification result to the cloud center platform. If the integrity verification passes, the software is installed into the target container environment of the edge node, and the cloud center platform reports a "successful installation" message. If the integrity verification fails, the result includes the identifier of the missing software sub-blocks (such as hash values, UUIDs, etc.). Upon receiving the integrity verification result, the cloud center platform retransmits the corresponding software sub-blocks. After retransmission, the edge node performs integrity verification again until the software is successfully installed or the set number of retransmissions is reached.

[0171] The present invention provides a digital cloud-edge software push method and system for satellite communication scenarios, wherein the method comprises the following steps: predicting the bandwidth status and link availability period of the satellite within a set future time period; sending a probe signaling message and obtaining target resource status information from the feedback information of the response to the probe signaling message; the target resource status information includes the software deployment environment, available storage capacity, and the amount of data retained from previous interruptions of the software package; determining whether all software push conditions are met; the software push conditions include: the software deployment environment matches the deployment environment required by the software to be pushed; and after considering the corresponding part of the data retained from previous interruptions of the software package, the remaining data volume of the software package to be pushed is less than the available storage capacity; when the target resource status information meets the software push conditions, the software is pushed during the link availability period within the set time period, and the bitrate of the software push is dynamically adjusted according to the bandwidth status.

[0172] Furthermore, it should be noted that the present invention can be provided as a method, apparatus, or computer program product. Therefore, embodiments of the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, embodiments of the present invention can take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0173] Embodiments of the present invention are described with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0174] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing terminal equipment to cause a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0175] It should also be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0176] Finally, it should be noted that the above description represents a preferred embodiment of the present invention. It should be pointed out that although preferred embodiments have been described, those skilled in the art, once they understand the basic inventive concept of the present invention, can make various improvements and modifications without departing from the principles described herein. These improvements and modifications should also be considered within the scope of protection of the present invention. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present invention.

Claims

1. A digital cloud-edge software push method for satellite communication scenarios, characterized in that, The steps are as follows: The bandwidth status and link availability of satellites within a set future timeframe can be predicted. Send a probe signaling message and obtain the target resource status information from the feedback information in response to the probe signaling message; The target resource status information includes the software deployment environment, available storage capacity, and the amount of data retained from previous interruptions of the software package. Determine if all software push conditions are met; The software push conditions include: the software deployment environment matches the deployment environment required by the software to be pushed; and after subtracting the amount of data retained before the software package was interrupted, the remaining amount of data in the software package to be pushed is less than the available storage amount. When the target resource status information meets the software push conditions, software push is performed during the link availability period within the set time period, and the software push bitrate is dynamically adjusted according to the bandwidth status.

2. The intelligent cloud-edge software push method for satellite communication scenarios according to claim 1, characterized in that, Also includes: Before sending the probe signal, compare the version of the software to be pushed with the pre-stored current software version of the target software; If the version of the software to be pushed is higher than the current version of the target software, then the probe signaling is sent; otherwise, the probe signaling is not sent.

3. The intelligent cloud-edge software push method for satellite communication scenarios according to claim 2, characterized in that, The predicted bandwidth status and link availability periods of the satellite within a specified future timeframe are as follows: Based on the satellite link status prediction network, historical satellite data is used as input to predict the satellite's bandwidth status and link availability time in the next 1 to 3 hours. The satellite link state prediction network is one of the pre-trained Long Short-Term Memory Network (LSTM) or Time Difference Convolutional Network (TCN). The historical data consists of satellite orbit position, weather, bandwidth, and interruption records for a set historical date; the bandwidth status is represented by a bandwidth-time curve.

4. The intelligent cloud-edge software push method for satellite communication scenarios according to any one of claims 1 to 3, characterized in that, Before pushing the software, the following steps are also included: The software package to be pushed is split into multiple software sub-blocks according to the preset sub-block data volume; then, according to the preset priority standard, the multiple software sub-blocks are divided into different priorities.

5. The intelligent cloud-edge software push method for satellite communication scenarios according to claim 4, characterized in that, The specific process of software push includes: According to priority order, the corresponding software sub-blocks are transmitted sequentially; After transmitting the last software sub-block, receive the integrity verification result of the software copy; The software copy is generated by splicing together all the transmitted software sub-blocks; If the integrity verification of the software copy passes, the software push is confirmed to be complete; Otherwise, retransmit the corresponding software sub-block.

6. The intelligent cloud-edge software push method for satellite communication scenarios according to claim 5, characterized in that, The specific process of software push also includes: Record the progress of software sub-block transmission when the link is interrupted; When the link is restored, transmission is resumed according to the transmission progress of the software sub-block.

7. The intelligent cloud-edge software push method for satellite communication scenarios according to any one of claims 1-3 and 5-6, characterized in that, Software push conditions also include: The amount of data to be pushed by the software should not exceed the product of the available link time period and the corresponding bandwidth.

8. The intelligent cloud-edge software push method for satellite communication scenarios according to claim 7, characterized in that, The software push bitrate is dynamically adjusted based on bandwidth status. The specific process includes: When the bandwidth changes, the bitrate is adjusted to match the preset bandwidth-bitrate mapping relationship.

9. A digital cloud-edge software push system for satellite communication scenarios, characterized in that, Including a cloud center platform, the cloud center platform includes: The satellite link management module is used to predict the bandwidth status and link availability of satellites within a set time period in the future; The software push module is used for: Send a probe signaling message and obtain the target resource status information from the feedback information in response to the probe signaling message; The target resource status information includes the software deployment environment, available storage capacity, and the amount of data retained from previous interruptions of the software package. Determine if all software push conditions are met; The software push conditions include: the software deployment environment matches the deployment environment required by the software to be pushed; and after considering the portion of the data retained by the software package during previous interruptions, the remaining data amount of the software package to be pushed is less than the available storage amount. When the target resource status information meets the software push conditions, software push is performed during the link availability period within the set time period, and the software push bitrate is dynamically adjusted according to the bandwidth status.

10. The intelligent cloud-edge software push system for satellite communication scenarios according to claim 9, characterized in that, It also includes multiple edge nodes, which include: Data receiving server, used for: Respond to the probe signaling and send back feedback information including target resource status information; After receiving the software package, perform an integrity check on the software package and send out the integrity check result; The target container environment is used to install packages that have passed integrity verification.

Images