Multi-satellite cooperative short message communication method and device, equipment and storage medium

Abstract

The embodiment of the application provides a kind of short message communication method, device and equipment of multi-star coordination and storage medium, for wireless communication technical field.The short message communication method of multi-star coordination includes: uplink signal is analyzed, to obtain terminal equipment information according to communication satellite screening candidate satellite set is obtained, channel quality evaluation is carried out to candidate satellite set, to obtain target satellite set according to channel quality score screening candidate satellite, according to target satellite quantity, data duplication is carried out to obtain data copy set to be sent data, according to target satellite ID and data copy set, task creation and data encapsulation are generated to generate sending task list, according to time sequence constraint, each sending task is sent priority determination and sequencing to generate sending sequence.The application is replaced by space redundancy to single-point transmission, and multi-star screening is carried out in combination with link sensing, which improves the reliable delivery rate and timeliness of short message under bad / unstable link.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a multi-satellite collaborative short message communication method, apparatus, device, and storage medium. Background Technology

[0002] Short message communication plays a fundamental role in modern communication systems, providing lightweight, low-bandwidth, high-coverage, and wide-reaching terminal connectivity. It is commonly used in scenarios such as alarms and emergency notifications, IoT terminal status reporting, telemetry, remote control, and control signaling. Its transmission methods include traditional mobile communication short messages (such as SMS or signaling bearers in GSM / 3G / 4G), narrowband IoT technologies (NB-IoT, LTE-M), low-power wide-area networks (LoRa, Sigfox), and satellite-oriented short message / short burst data services and lightweight application layer protocols (such as CoAP, MQTT-SN), covering various link types from terrestrial base stations to low-Earth orbit / medium-high Earth orbit satellites.

[0003] Existing short message communication methods mostly adopt single-path or single-service-domain transmission strategies: terrestrial networks exchange messages through base stations and core networks, relying on end-to-end acknowledgment and retransmission mechanisms to ensure reliability; LPWANs use gateway aggregation and simplified ACK mechanisms to reduce energy consumption; satellite short messages often use store-and-forward or direct single-satellite links, or are relayed by terrestrial gateways through fixed satellites. The overall process is mainly based on single-channel transmission / retry, with management and scheduling centrally controlled by specific networks or platforms. However, existing satellite communication methods that rely on single satellites or single-path transmission suffer packet loss and frequent retransmissions during transmission due to obstruction, transient fading, or satellite resource congestion. This results in insufficient guarantee of the timeliness and reliability of critical messages, while also incurring additional bandwidth and energy consumption costs, making it difficult to meet the needs of high-timeliness and high-reliability scenarios.

[0004] It should be noted that the above content is not necessarily prior art, nor is it intended to limit the scope of patent protection of this application. Summary of the Invention

[0005] This application provides a multi-satellite collaborative short message communication method, apparatus, device, and storage medium to solve or alleviate one or more of the technical problems mentioned above.

[0006] One aspect of this application provides a multi-satellite collaborative short message communication method, the method comprising: When a target uplink signal is received, the target uplink signal is parsed to obtain terminal device information, and communication satellites are filtered according to the terminal device information through a preset satellite database to obtain a candidate satellite set; Channel quality assessment is performed on each candidate satellite in the candidate satellite set to obtain a channel quality score for each candidate satellite, and the candidate satellites are then screened based on the channel quality scores to obtain a target satellite set; Based on the number of satellites in the target satellite set, the data to be sent is copied to obtain a data copy set. Then, based on the target satellite IDs in the target satellite set and the data copy set, tasks are created and data is encapsulated to generate a sending task list. The sending priority of each sending task in the sending task list is determined and sorted according to the preset timing constraints, and a sending sequence is generated.

[0007] Optionally, the terminal device information includes terminal positioning information, and the candidate satellite set includes candidate satellites and their corresponding communication durations; the step of filtering communication satellites based on the terminal device information using a preset satellite database to obtain the candidate satellite set includes: The real-time position information, real-time velocity, satellite beam tilt angle and orbital parameters of each satellite are obtained through a preset satellite database, and the signal coverage area of ​​each satellite is calculated based on the real-time position information, the satellite beam tilt angle and the orbital parameters. Based on the signal coverage area and the terminal positioning information, communication satellites are screened to obtain initial candidate satellites for the signal coverage terminal equipment; Based on the terminal positioning information and the satellite beam tilt angle corresponding to each initial candidate satellite, the communication blockage analysis and screening are performed using the preset terrain simulation model data to obtain candidate satellites whose signals are not blocked. The signal coverage time of each candidate satellite is calculated based on the terminal positioning information, the signal coverage area, and the real-time speed to obtain the communication duration of each candidate satellite.

[0008] Optionally, the process of performing channel quality assessment on each candidate satellite in the candidate satellite set to obtain a channel quality score for each candidate satellite includes: Based on the real-time location information of each candidate satellite and the terminal positioning information, the communication propagation characteristics are analyzed to obtain the communication loss index of each candidate satellite. The average communicable duration of the candidate satellite set is obtained by averaging the communicable duration and calculating the standard deviation based on the communicable duration and the average communicable duration to obtain the available time index of each candidate satellite. The received operational performance indicators, communication loss indicators, and available time indicators of each candidate satellite are normalized to obtain a standardized indicator set for each candidate satellite. The standardized indicator set is then fused using multiple factors to obtain the channel quality score for the corresponding candidate satellite.

[0009] Optionally, the communication loss indicators include path loss and signal-to-noise ratio; the step of analyzing the communication propagation characteristics of each candidate satellite based on the real-time location information of each candidate satellite and the terminal positioning information to obtain the communication loss indicators of each candidate satellite includes: The straight-line distance, relative azimuth angle, and relative elevation angle between the terminal device and the corresponding candidate satellite are calculated based on the real-time location information and the terminal positioning information. The satellite transmission gain and terminal reception gain are obtained based on the relative azimuth angle and the relative elevation angle through a preset gain mapping rule. The path loss of each candidate satellite is calculated based on the preset frequency band and the straight-line distance, and the theoretical received power of the terminal device to receive the corresponding candidate satellite is calculated based on the path loss, the satellite transmit gain and the terminal receive gain. The signal-to-noise ratio of the corresponding candidate satellite is calculated based on the theoretical received power, the preset noise baseline, and the preset receiver noise figure.

[0010] Optionally, the step of copying the data to be transmitted to obtain a data replica set based on the number of satellites in the target satellite set, and generating a transmission task list based on the target satellite IDs in the target satellite set and the data replica set, includes: The number of copies of the data to be sent is determined based on the number of satellites in the target satellite set, and a data replica set is obtained by copying the data according to the number of copies and the data to be sent. According to the preset data and satellite allocation strategy, the target satellite IDs in the target satellite set and the data replicas in the data replica set are allocated and combined to generate a data set to be sent; According to the preset short message protocol, each data group in the set of data to be sent is encapsulated to generate a sending task entry and corresponding metadata. The sending task entry and corresponding metadata are then associated and stored according to the preset task list to generate a sending task list.

[0011] Optionally, the step of determining and sorting the sending priorities of each sending task in the sending task list according to preset timing constraints, and generating a sending sequence, includes: The priority level of each transmission task in the transmission task list is determined according to the preset priority strategy and the channel quality score, and the corresponding communication duration is obtained according to the target satellite corresponding to each transmission task. Based on the preset timing constraints, the communicable duration, and the priority level, the sending time is allocated for each sending task to obtain the sending timestamp corresponding to each sending task. The sending tasks are sorted according to the sending timestamp and time order to generate a sending sequence.

[0012] Another aspect of this application provides a multi-satellite collaborative short message communication method applied to a terminal device, the method comprising: The received short message data is parsed and bit error checked, and satellite copies that pass the error check are recorded; The satellite copy is decrypted and verified using a preset local key, and the satellite copy that passes the key verification is decoded, restored, and its semantic integrity is checked to obtain a digest and corresponding metadata. The digest is compared with the saved preferred payload digest in the order of receipt time. When the digest matches the preferred payload digest, the digest is deleted and the metadata of the digest matches is counted. When the summary is inconsistent with the preferred payload summary, the metadata is judged and saved according to the preset conflict decision rules, and the corresponding preferred payload summary is generated according to the summary.

[0013] Another aspect of this application provides a multi-satellite collaborative short message communication device, the device comprising: The satellite filtering module is used to parse the target uplink signal to obtain terminal device information when the target uplink signal is received, and to filter communication satellites according to the terminal device information through a preset satellite database to obtain a candidate satellite set. The channel filtering module is used to perform channel quality assessment on each candidate satellite in the candidate satellite set to obtain a channel quality score for each candidate satellite, so as to filter the candidate satellites according to the channel quality score to obtain a target satellite set; The task generation module is used to copy the data to be sent according to the number of satellites in the target satellite set to obtain a data copy set, and to create and encapsulate tasks according to the target satellite IDs in the target satellite set and the data copy set to generate a sending task list. The sending sorting module is used to determine and sort the sending priorities of each sending task in the sending task list according to preset timing constraints, and generate a sending sequence.

[0014] Another aspect of this application provides a computer device, including: At least one processor; and A memory that is communicatively connected to the at least one processor; Wherein: the memory stores instructions that can be executed by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method as described above.

[0015] Another aspect of this application provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the method described above.

[0016] Another aspect of this application provides a computer program product including a computer program that, when executed by a processor, implements the method described above.

[0017] The embodiments of this application employing the above-described technical solution may have the following advantages: 1. By matching candidate satellites from a pre-set satellite library, scoring the channel quality of the candidate satellites, and selecting the target satellite set, the system performs multiple replications of the data, replacing single-point transmission with spatial redundancy (multiple satellites). Even if one or more satellites experience obstruction, channel abrupt changes, or short-term failures, the data can still be successfully delivered via other satellites, thereby significantly reducing the risk of packet loss due to single-point failures and improving message delivery success rate.

[0018] 2. Channel quality assessment and screening of candidate satellites are conducted to avoid sending copies to satellites with extremely poor channel conditions. This ensures that limited satellite resources are used to place copies in positions where they can be effective. Compared to indiscriminate broadcasting, this selective replication can reduce overall redundancy overhead and improve spectrum / bandwidth utilization while ensuring reliability.

[0019] 3. The combination of multi-copy parallel transmission and priority scheduling can reduce the number of repeated transmissions (retry) performed by the terminal or base station to ensure delivery, alleviate congestion of satellite links and backhaul links, reduce overall network load and energy consumption, and save a lot of control signaling and bandwidth resources, especially when the link is unstable. Attached Figure Description

[0020] The accompanying drawings exemplify embodiments and form part of the specification, serving together with the textual description to explain exemplary implementations of the embodiments. The illustrated embodiments are for illustrative purposes only and do not limit the scope of the claims. Throughout the drawings, the same reference numerals refer to similar but not necessarily identical elements.

[0021] Figure 1 The diagram illustrates the operating environment of the multi-satellite collaborative short message communication method according to Embodiment 1 of this application. Figure 2 A schematic flowchart of a multi-satellite collaborative short message communication method according to Embodiment 1 of this application is shown. Figure 3 This schematic diagram illustrates the functional block diagram of a multi-satellite collaborative short message communication device according to Embodiment 2 of this application; Figure 4A schematic diagram of the hardware architecture of a computer device according to Embodiment 3 of this application is shown. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0023] It should be noted that the descriptions involving "first," "second," etc., in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" or "second" may explicitly or implicitly include at least one feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0024] In the description of this application, it should be understood that the numerical labels before the steps do not indicate the order of the steps, but are only used to facilitate the description of this application and to distinguish each step, and therefore should not be construed as a limitation of this application.

[0025] For ease of understanding, an exemplary runtime environment is provided below: like Figure 1As shown in the diagram, the operating environment includes: base station 1, terminal device 2, and several satellites 3. Base station 1 acts as the central hub. Upon receiving advanced raw signals (such as emergency rescue commands), it first parses the terminal device's registration information (such as computing power) and precise positioning data. Then, through a dynamic filtering algorithm, combined with the terminal's location and the real-time satellite coverage (such as the LEO satellite constellation of the BeiDou system), it selects available satellites and evaluates channel quality, ultimately locking onto several target satellites with optimal signals. Base station 1 replicates the original data packets (the number of copies matching the number of target satellites), encapsulates the data packets and satellite IDs according to the RDSS protocol, and then prioritizes transmission tasks based on signal strength. Satellites 3 act as relay nodes, responsible for forwarding the data packets encapsulated by the base station across regions. Their low-Earth orbit characteristics significantly reduce transmission latency, while the multi-satellite redundancy mechanism avoids the risk of single-satellite signal obstruction. Terminal device 2 independently parses the data packets from each satellite in the receiving order, extracts the original content, and performs real-time comparison. Adopting the first-packet validity principle, when duplicate data is detected, subsequent copies are automatically discarded, saving computing power and avoiding storage redundancy. This "multi-path transmission-terminal deduplication" design ensures that critical information can still be delivered even in extreme environments. Figure 1 The short message satellite communication network formed by the various devices in the network, which uses multi-satellite redundancy and intelligent scheduling to overcome geographical limitations, will become the underlying support infrastructure for scenarios such as emergency rescue and oceanographic research, given the increasing abundance of satellite resources.

[0026] The technical solution of this application will be described below using base station 1 as the implementing entity through multiple embodiments. It should be understood that these embodiments can be implemented in many different forms and should not be construed as being limited to the embodiments described herein.

[0027] Example 1 like Figure 2 The diagram shows a flowchart of a multi-satellite collaborative short message communication method provided in an embodiment of this application. The multi-satellite collaborative short message communication method provided in this embodiment includes the following steps.

[0028] Step S1: When a target uplink signal is received, the target uplink signal is parsed to obtain terminal device information, and communication satellites are screened based on the terminal device information through a preset satellite database to obtain a candidate satellite set.

[0029] It should be understood that a target uplink signal is an uplink message sent by a terminal device to the base station, carrying actual service content and marked as requiring priority processing. Taking emergency rescue as an example, a target uplink signal can be a manually triggered emergency call message or an alarm message automatically generated by the terminal's built-in sensors or applications. After receiving the uplink signal sent by the terminal device, the base station determines whether the uplink signal is the target uplink signal by identifying whether the signal carries a specific identifier. This identifier can be an emergency level code agreed upon in the protocol, a specific service type code, or a special transaction ID agreed upon in advance during registration.

[0030] When the received uplink signal is the target uplink signal, the base station first parses the uplink signal layer by layer at the physical layer, link layer, and application layer to extract terminal registration information and terminal location information. The terminal registration information specifies the terminal's unique identifier, supported protocol versions, maximum receiveable message length, power consumption / operating mode indication, and authentication fields for message integrity verification. The terminal location information includes longitude, latitude, altitude, location confidence level, and timestamp. During the parsing process, the base station not only checks the frame integrity and authentication flags of the target uplink signal to determine the source's trustworthiness but also generates a time alignment token for subsequent timing alignment, serving as a unified benchmark in subsequent timing processing. The structured metadata obtained from the parsed signal is then used as a query key for preliminary matching against a pre-set satellite database. The satellite database refers to a dynamic database that stores satellite ephemeris and telemetry information, satellite antenna beam parameters and patterns, real-time transmit power strategies, orbital parameters, and satellite operation plans (including maintenance windows and restricted periods) provided by the operator or ground management center. This database can be obtained from the satellite operator's interface, precise ephemeris distribution system, or ground network synchronization link and is refreshed periodically. The real-time position and orbital velocity in the database use precise ephemeris or near-real-time orbital prediction as data sources to ensure timeliness. The base station retrieves the signal coverage boundaries of each satellite from the database based on the terminal's positioning information. These signal coverage boundaries are determined by the satellite antenna beam pointing, beamwidth, and satellite altitude. Therefore, the satellite's real-time position information, orbital parameters, and antenna beam tilt angle need to be mapped into a ground-projected coverage polygon or coverage trajectory. This mapping process is achieved by projecting the satellite's spatial position onto the Earth's surface and calculating the effective coverage radius in each direction using the antenna pattern, thus obtaining the signal coverage area of ​​each satellite at the current moment. After obtaining the signal coverage area, the base station performs spatial intersection and judgment based on the signal coverage area and the parsed terminal positioning information to select initial candidate satellites covering the terminal's location.

[0031] Subsequently, the base station performs occlusion assessment on the initial candidate satellites, using terrain and artificial structures as inputs. The terrain simulation model data used for occlusion assessment refers to a simulation dataset consisting of a digital elevation model, building base maps and height information, canopy or obstruction height models, and a set of 3D terrain features generated by aerial photography or lidar. This dataset can be obtained from the geographic information systems of national or local surveying and mapping departments, the most recent high-resolution acquisition results from commercial aerial surveying / lidar service providers, and supplementary field surveys. The data is labeled with the acquisition time and confidence level during import for subsequent dynamic updates and consistency verification. The terrain simulation model data is used to calculate the line-of-sight distance between the terminal location and the candidate satellite azimuth line and simulate the effects of building occlusion, surface undulation, and vegetation occlusion. By sampling the terrain elevation along the satellite-terminal connection line and comparing the connection line height, it is determined whether there are insurmountable occlusions. If the connection line is lower than the local terrain or building height at any point, it is determined as an occlusion and the satellite is removed from the candidate set. This retains candidate satellites whose signals are not obstructed to ensure the feasibility of subsequent transmission paths.

[0032] After completing the obstruction removal, the base station calculates the duration (i.e., the communicable duration) for each candidate satellite to provide effective communication to the terminal device based on the real-time velocity and trajectory of the candidate satellites obtained from the satellite database, the rate of change of antenna beam pointing, and the aforementioned coverage boundary. The calculation of the communicable duration is based on the relative motion between the satellite and the terminal position in the ground projection. Considering that the satellite altitude and orbital velocity will cause the coverage polygon to move and deform over time, the satellite projection is determined hourly or secondly by using time-seriesd orbit prediction to determine whether the terminal position is included in the satellite projection and the included duration is accumulated to obtain the length of a continuous visible time window. In addition, the sweeping behavior of the satellite beam pointing needs to be included in the time-series judgment to avoid misjudging short-term edge coverage as effective duration.

[0033] By selecting a candidate satellite set, redundant satellite delivery candidates are provided for high-priority BeiDou short message services. For example, for a rescue uplink command from a mountain emergency rescue terminal, after obtaining the accurate coordinates through parsing, multiple BeiDou short message relay satellites covering those coordinates are quickly screened through the satellite database. Satellites blocked by mountains or buildings are excluded using terrain simulation model data. This yields several candidate satellites that can receive and forward messages within the available communication time. The number of copies and the transmission priority are then determined based on channel quality scores and available communication time, thereby reducing retransmission delays caused by a single satellite being unreachable or temporarily blocked, and ensuring the timeliness and reliability of BeiDou short messages.

[0034] Step S2: Perform channel quality assessment on each candidate satellite in the candidate satellite set to obtain a channel quality score for each candidate satellite, and then filter the candidate satellites according to the channel quality scores to obtain a target satellite set.

[0035] It should be understood that the input data required for channel quality assessment comes from several clearly defined channels: terminal positioning information is obtained directly from uplink messages or inferred from base station positioning; the real-time position, velocity, attitude, and antenna beam pointing of candidate satellites should be read from a pre-set satellite database or operator telemetry interface; satellite-side operation and maintenance performance indicators (such as current load rate, historical frame success rate, forwarding / queueing delay) should be collected from the network operation database or statistics module with sampling timestamps; the antenna characteristics, equipment noise parameters, and service bandwidth of base stations and terminals are provided by equipment factory specifications and online monitoring and are used as constants or calibration values ​​in calculations. All collected data must be labeled with the collection time and confidence level before entering the evaluation link for subsequent determination of scoring confidence and back-up processing of missing data.

[0036] In the process of analyzing the communication propagation characteristics between candidate satellites and terminal devices, a geometric relationship analysis is first performed based on the real-time satellite position information and terminal positioning information to obtain geometric quantities such as straight-line distance, relative azimuth, and relative elevation angle. These geometric quantities can represent the communication link quality between the satellite and the terminal device. The straight-line distance is the spatial straight-line distance between the candidate satellite and the terminal device. The satellite's transmission power increases with distance, and correspondingly, the larger the straight-line distance, the more severe the link transmission delay, path loss, and signal attenuation. The relative azimuth angle is the horizontal angle (ranging from 0° to 360°) rotated clockwise from the terminal's due north direction to the satellite's projection line. The relative elevation angle is the angle between the terminal's line of sight and the horizontal plane. Further, the transmit / transmit gain is obtained based on the obtained geometric quantities. The gain mapping rule used in this application's embodiments obtains the gain value (i.e., satellite transmit gain and terminal receive gain) by interpolating or looking up a table at the corresponding azimuth-elevation point of the antenna pattern (including the satellite antenna pattern and the terminal antenna pattern), and approximates the gain using the main lobe / half-power angle parameters provided by the manufacturer when an accurate pattern is unavailable. The mapping process considers both the antenna's main lobe gain and the equivalent gain loss introduced by pointing error. Pointing error refers to the angular deviation between the actual main axis of the antenna beam and the theoretical / target direction at the transmitting or receiving end, usually expressed in degrees (degrees or radians). This deviation causes the actual gain of the antenna in the target direction to be lower than the antenna's nominal main lobe gain, thus reducing the signal power received by the terminal. The main sources of pointing error include satellite attitude control errors (attitude jitter, attitude measurement errors), satellite antenna pointing control deviations, ground or terminal antenna pointing control errors (installation errors, mechanical offsets, turntable tracking errors), platform vibration, and antenna calibration errors. By introducing pointing error as a gain adjustment term during the mapping process, the antenna's nominal gain is mapped to the actual usable gain, thus providing a closer estimate of the true received power.

[0037] It should be understood that the communication loss metrics obtained from propagation characteristic analysis include path loss and signal-to-noise ratio, which are obtained through the following process: After obtaining the transmit gain, receive gain, and straight-line distance, the antenna characteristics, pointing relationship, and space propagation conditions of the satellite and terminal ends are integrated into an engineering-usable estimate of the received power, which serves as the basis for subsequent path loss, signal-to-noise ratio, and scoring calculations. Specifically, firstly, the satellite transmit gain obtained from mapping is corrected by subtraction based on the pointing error to obtain the actual effective gain of the transmitter. Correspondingly, the terminal receive gain obtained from mapping is corrected by subtraction based on the pointing error to obtain the actual effective gain of the receiver. Finally, the preset satellite transmit power, the actual effective gain of the transmitter, and the actual effective gain of the receiver are superimposed, and then corrected by subtraction based on preset system loss terms (including feeder loss, polarization mismatch loss, and additional losses from antenna assembly) and path loss to obtain an estimate of the theoretical received power. Theoretical received power refers to the theoretically calculated power value of the satellite signal received by the terminal device under an ideal propagation model, representing the expected downlink signal power intensity received at the terminal antenna port. Path loss is used to quantitatively describe the attenuation of signal strength during space propagation. The standard free-space formula calculates the path loss based on the obtained straight-line distance and the factory-set L / S frequency band (i.e., the preset frequency band). middle, For path loss, The straight-line distance. , where L / S is the frequency band, and c is the speed of light in a vacuum.

[0038] After obtaining the theoretical received power, the signal-to-noise ratio (SNR) of each candidate satellite is calculated based on the theoretical received power, the noise baseline, and the receiver noise figure. SNR is a quantified comparison of signal strength with the background noise at the receiver, providing a direct physical indicator for bit error rate estimation, link reliability scoring, and scheduling decisions. The noise baseline is the noise power spectral density at standard temperature. Specifically, first, the noise power increment due to bandwidth is calculated based on the channel occupancy bandwidth. Then, the noise baseline constant, the noise power increment due to bandwidth, and the receiver noise figure are superimposed to obtain the receiver noise power. Subsequently, the theoretical received power is corrected by subtracting a term based on the receiver noise power to obtain the SNR of each candidate satellite.

[0039] Meanwhile, the processing of the communication duration takes the visible time window of the candidate satellite as input and combines the time evolution of the satellite trajectory and beam pointing to make a time-series determination. First, for each candidate satellite, the projection coverage is calculated to include the terminal location in a subdivided time step (e.g., by second or by ten seconds) within a short future time window, and the duration of continuous inclusion is accumulated to obtain the continuous visible time window length. Then, the average of this duration and the duration of all durations in the candidate set is calculated to obtain the average communication duration. Then, the standard deviation of the duration of each candidate satellite and the average is calculated to reflect the dispersion of the duration distribution. Finally, the available time index of a single satellite is defined as its standardized quantity relative to the average and standard deviation. The available time index reflects the advantage or disadvantage of a single satellite in terms of time availability relative to the candidate set.

[0040] Subsequently, the received operational performance indicators of each candidate satellite, the communication loss indicators obtained from the above processing, and the available time indicators are scaled uniformly according to engineering rules. The scale uniformity adopts an interpretable normalization strategy. For example, the original indicators that are better the larger or the smaller the better are mapped to a uniform scale interval (e.g., 0 to 1) through defined upper and lower bounds or quantiles. The normalization process needs to record the source and update time of the upper and lower bounds used and process them with a predetermined neutral value and reduced confidence when the sampling is missing, so as to ensure that the score will not produce misleading extreme values ​​when the data is incomplete. After normalization, multi-factor fusion is used to obtain the channel quality score and confidence level of the corresponding candidate satellite. The preferred fusion strategy is linear weighted fusion to balance interpretability and configurability. That is, several normalized indicators are weighted according to configurable weights and normalized to output the score. At the same time, the confidence level is calculated based on the timeliness and completeness of the indicators to characterize the reliability of the score. As an optional enhancement embodiment, a supervised model trained based on historical samples can be used to replace linear fusion to improve the fitting ability of complex nonlinear relationships, but the scope of weights does not limit the specific model.

[0041] After obtaining the channel quality scores of each candidate satellite, they are sorted from highest to lowest to form a priority queue. Based on a preset scoring threshold and an upper limit on the number of target satellites, satellites are selected from this priority queue to enter the target satellite set. Simultaneously, redundancy and parallelism checks are performed on the selection results to avoid a decrease in redundancy due to high overlap in the visible time windows of the selected satellites. In cases of high overlap, the scores of satellites with high overlap are reduced according to their redundancy marginal contribution, or alternative satellites are added to ensure the target set is complementary in space and time. The entire evaluation and selection process records snapshots of the original indicators used for scoring, normalized parameters, and fusion weights. When a sudden change in a key indicator is detected before transmission (e.g., satellite telemetry shows a reduction in transmit power), the scores are recalculated and the target set is dynamically replaced. This ensures that in time-sensitive scenarios such as emergency rescue, the most advantageous satellite selection is made based on the latest link and maintenance information. This provides a reliable and traceable measurement basis for redundant delivery and priority scheduling when subsequently replicating messages according to the number of target satellites and generating transmission tasks.

[0042] Step S3: Based on the number of satellites in the target satellite set, copy the data to be sent to obtain a data copy set, and based on the target satellite IDs in the target satellite set and the data copy set, create tasks and encapsulate data to generate a sending task list.

[0043] After obtaining the target satellite set, the first step is to determine the number of copies of the data to be transmitted based on the number of target satellites and generate a data replica set accordingly. Spatial redundancy is achieved through a one-to-one replica-satellite mapping, thereby reducing retransmission delays caused by single-point failures in short message transmission scenarios with high timeliness requirements. The determination of the number of copies is based on a comprehensive reference of the actual visible time window of available satellites in the target satellite set, the channel quality score of each satellite, and the system policy. The number of copies is equal to the number of target satellites by default, but when constrained by limited resources or policies (such as satellite carrying capacity limits or ground transmission bandwidth limitations), a maximum allowed replica limit or a strategy of prioritizing high-scoring subsets can be adopted to ensure feasibility. Specifically, the replication operation first performs consistency verification and transaction processing on the original data to be transmitted, that is, assigning a unique transaction identifier (transactionID) to the data to be transmitted and generating a time alignment token and a transaction timestamp. The transaction identifier is used for subsequent replica ownership determination and deduplication at the terminal, and the time alignment token is used for time reference comparison during multi-source reception. Verification items include message digests (such as SHA-256) or message authentication codes (MAC) for integrity verification and anti-tampering checks at the terminal. Subsequently, the length of the data to be sent is checked to determine whether segmentation is necessary. Given that BeiDou short messages have an upper limit on the length of a single message, if the data to be sent exceeds the length that a single message can carry, it is segmented according to the protocol, and a segment header (containing the segment sequence number, the total number of segments and the transaction ID) is generated for each segment. An independent integrity check value is also calculated for each segment to support the segmentation reassembly and verification of the terminal. The goal of the segmentation strategy is to ensure the carryability of a single downlink frame in the target satellite link while minimizing the reassembly failure rate at the terminal.

[0044] Subsequently, this embodiment employs a random allocation method to randomly assign and combine target satellite IDs and data replicas. Random allocation refers to using a pseudo-random number generator to randomly arrange the target satellite ID list and sequentially aligning the arrangement with the data replicas in the data replica set. This achieves a one-to-one mapping between each target satellite and each data replica, ensuring that each transmission task is uniquely bound to a single target satellite ID, and that this binding relationship remains fixed before transmission. To ensure reproducibility and security, the random sequence can be generated using a transaction ID and a time alignment token as a random seed. This avoids predictability in the mapping and allows for post-transmission verification of the allocation correspondence based on the same seed. After mapping, each pair of data replicas and target satellite IDs is constructed into a data group to be transmitted, and all data groups to be transmitted form a set of data groups to be transmitted.

[0045] Finally, the protocol encapsulation stage begins. This encapsulation is based on the adopted short message protocol (e.g., RDSS). During encapsulation, the target satellite ID, transaction ID, segmentation indicator, time alignment token, priority flag, payload length, and integrity checksum are explicitly written into the control header. If the payload is encrypted, an encryption indicator header is retained within the encapsulation to allow the receiving end to identify the decryption request. The presence of the control header enables satellite relays and ground gateways to quickly identify the destination and verification information of the task during forwarding and recording. Each completed encapsulation unit generates a transmission task entry. This entry is established as a persistent record in the task management subsystem. The entry content includes, but is not limited to, the task ID, associated transaction ID, replica sequence number, target satellite ID, encapsulated protocol unit byte string, initial priority flag, generation timestamp, and task status field. Persistence ensures that the transmission queue can be fully recovered during system restarts or fault recovery, and provides an immutable chain of evidence for subsequent auditing and fault tracing. The mission list consists of a set of such entries and is written to the launch queue. After entering the launch queue, missions are sorted based on the target satellite's communication information (such as previously evaluated channel quality scores or real-time signal strength indicators) to generate the final launch order. The sorting rule can be to prioritize launches from high to low signal strength or score, so as to prioritize the use of satellites with better link conditions under limited launch resources, thereby improving the first launch success rate without changing the "complete copy of each satellite" principle. The sorting is only used to determine the launch priority and does not affect the established copy-satellite one-to-one binding relationship. To ensure that there are appropriate remedial strategies for extremely low probability edge coverage or sudden unavailability during the launch process, the launch mission management module retains a copy of the alternative satellite mapping table in the previously encapsulated metadata. However, the default and preferred behavior is to launch according to the randomly bound target satellite ID and the sorting order. Emergency remapping and recapsulation of the mission are only triggered when a clear and verifiable unavailability signal is detected at the launch execution level (such as local network or satellite telemetry feedback indicating that the target satellite is temporarily offline or the transmission power is reduced). This remapping is time- and control-constrained to avoid causing unnecessary scheduling delays within millisecond-level launch slots. The entire replication-allocation-encapsulation-list generation process records all kinds of metadata during execution, including transaction snapshots, verification digests of each copy, random seeds for allocation, mapping relationships, and encapsulation header fields. This allows the terminal to perform deduplication and content comparison based on the transaction ID and copy sequence number after receiving multiple copies, and report the reception results. For example, for an emergency rescue text, after evaluating and selecting four target satellites, four identical payload copies are generated and randomly bound to the IDs of the four satellites. Then, an independent RDSS protocol unit (including the transmission task entry and corresponding metadata) is generated for each copy.

[0046] Step S4: Determine and sort the sending priorities of each sending task in the sending task list according to the preset timing constraints, and generate a sending sequence.

[0047] It should be understood that the main purpose of priority determination during the transmission sequence generation process is to combine service urgency with link availability, ensuring that tasks with high urgency and reliable links receive priority transmission opportunities, while tasks with high urgency but weak links are scheduled for early transmission or staggered transmission protection is added to reduce the risk of retransmission, thus balancing timeliness and success rate. Channel quality represents the current probability of link success; therefore, this application uses the channel quality scores obtained from the above steps for each target satellite to determine the priority level of the transmission task corresponding to the target satellite. The higher the channel quality score of the target satellite, the higher the priority level of the corresponding transmission task.

[0048] In another optional implementation, a configurable set of weighted rules is used to synthesize the comprehensive priority value of each task in the construction of the priority strategy. The weights include urgency level weight, channel quality weight, remaining visible time weight, and task size weight. Urgency level represents the inherent priority of the service, channel quality represents the probability of success of the current link, remaining visible time reflects the scarcity of available time, and task size, as a load indicator, affects scheduling granularity and concurrency strategy. The specific values ​​of each weight are given by the operation and maintenance strategy or pre-configured settings, and can be gradually optimized during system operation based on historical performance through online learning or experience calibration. The priority value is calculated using explicit engineering rules, such as first dividing tasks into several queues according to urgency level, and then sorting them within each queue according to a weighted score of comprehensive link + time. This hierarchical queuing strategy retains the strong constraints of service priority while allowing flexible selection among tasks of the same priority. The confidence level of the overall score should also be calculated simultaneously. The confidence level is determined by the timeliness of key input items. For example, if a certain operation and maintenance indicator in the channel quality exceeds the sampling time limit, the confidence level will be reduced, thereby promoting the use of alternative satellites or extended redundancy in low confidence situations.

[0049] During the transmission time allocation phase, the transmission time of each task needs to be constrained within the visible time window of its target satellite, while simultaneously satisfying the frame time slot granularity at the protocol level, the guard interval required for each transmission by the ground transmitter, and the receiving and processing capabilities of the satellite. The allocation process is implemented using a time slot model or a continuous time model. First, the visible window is divided into available transmission segments, and the earliest and latest available transmission times within each segment are considered. Then, the earliest feasible transmission time is allocated to tasks according to priority from high to low, in order to complete critical tasks as early as possible and leave time windows for subsequent retransmissions. To avoid excessive concurrency on one or more satellites simultaneously, the allocation algorithm introduces a staggered strategy and concurrency limits. The staggered strategy reduces the probability of collisions by adding a minimum guard interval to adjacent tasks. This interval is set based on frame duration, satellite processing latency, and network-side concurrent capacity, and is automatically widened in high-concurrency risk scenarios. The concurrency limit is determined by the current capacity provided by the network operator or satellite telemetry. If a satellite reports a critical receiving buffer or excessive scheduling occupancy, its acceptable concurrency is temporarily reduced, and some tasks are remapped to alternative satellites or postponed. To balance timeliness and success rate, the allocation algorithm also supports an early-deadline-first mode, prioritizing tasks whose windows are about to close to avoid missing the window. This is determined by the ratio of the required transmission time of the task to the remaining time until the end of the window. If this ratio is closer to or exceeds a threshold, the task is prioritized for scheduling.

[0050] After time allocation is completed, the base station reads the communicable start and end times of the target satellite corresponding to each transmission task and obtains the estimated transmission duration of the task (the transmission duration is estimated from the encapsulated frame size, the modulation and coding used, and the physical rate of the satellite link). Then, it searches for the earliest time point within the communicable duration so that there is still enough continuous time to complete the transmission from that point until the end of the communicable duration. At the same time, this time point must meet the protection interval constraints with the tasks scheduled before and after it, and must be compatible with the satellite's concurrency limits. If the preferred time point is limited, it attempts to make slight adjustments to the time slot backward or forward within the same allocable time period. If this cannot be met, it is marked as pending remapping and triggers the replacement process for alternative satellites. To support extreme time-sensitive scenarios, time allocation allows for a conservative priority arrangement, that is, when feasible, it prioritizes launching at a slightly earlier time to reserve retransmission space, but when concurrency resources are tight, the retransmission budget is made up by generating additional copies or allocating to multiple satellites. All timestamp allocation decisions are written to the allocation log with detailed metadata, including the reasons for the selection, conflict resolution records, the protection interval used, and the referenced concurrency threshold, so that they can be traced during the transmission phase or in subsequent audits.

[0051] When generating the final transmission sequence by chronological order, the sorting needs to balance the advantage of first-mover advantage with link reliability. These two factors are sometimes contradictory. To achieve this balance, a hierarchical sorting strategy is adopted: the first layer sorts by the absolute order of transmission timestamps to ensure time consistency; the second layer, in cases where timestamps are the same or close, performs a secondary sort based on task priority and confidence level to determine the transmission order; the third layer introduces a slight stagger for consecutive tasks that may cause satellite congestion in a short period of time to avoid instantaneous peaks. After sorting, the transmission sequence is written into the transmission queue and linked to the transmission control unit. The transmission control unit advances the transmission according to the sequence and records the acknowledgment waiting window after each transmission. If an acknowledgment is received from the superior within the acknowledgment window, the task is marked as completed and a possible replica cancellation process is triggered to save resources. If no acknowledgment is received, the remaining visible duration of the task and the overall retransmission strategy determine whether to retry in the current or subsequent window or to upgrade the priority of the remaining replicas for retransmission. During the launch process, the link telemetry and satellite operation and maintenance status are monitored in real time. If the target satellite suddenly fails or the communication time is reduced, the launch control unit should be able to suspend the corresponding transmission mission within a safe interval and trigger the alternative mapping logic to obtain an alternative target satellite for replacement, so as to ensure the robustness of the overall transmission of the corresponding transmission mission.

[0052] The following describes the data processing process transmitted to the terminal device using the multi-satellite collaborative short message communication method of this application from the perspective of the terminal device: After the terminal device receives the short message data relayed by the satellite, it first performs frame synchronization and signal demodulation at the physical transceiver link to restore the symbol stream on the radio frequency into frame structured data. The physical layer processing includes frame boundary identification, preamble detection, and bit error checking (e.g., CRC check). If the frame fails the error check, it is marked as unusable and relevant reception parameters are recorded for diagnosis; otherwise, the complete frame is handed over to the link layer and the upper-layer protocol parsing module. The link layer parsing extracts control fields from the frame header. These control fields include at least the transaction ID (used to identify the logical message being sent), segment sequence number (used for reassembling segmented messages), source satellite ID (used to record the source of the copy), message priority flag, timestamp and time alignment token (used for timing consistency processing between the end side and the network side), and message integrity verification fields (such as message digest or message authentication code, MAC). While extracting the control header, the terminal records the local reception time for each frame and compares this time with the timestamp of the control header to evaluate transmission delay and clock deviation, thereby providing a time reference for subsequent deduplication and timing analysis.

[0053] After initial parsing and metadata recording, the payload decoding module performs necessary encoding and restoration operations on the frame payload. If the payload is compressed, it is decompressed first; if encrypted, it is decrypted under the authorization of the local key management module. The key management module uses pre-registered key materials or dynamic session keys as a basis and performs necessary integrity and source verification. After decryption or decompression, integrity verification is performed on the payload, such as calculating SHA-256 digests and comparing them with the digest field in the message header, or verifying the message authentication code / digital signature to confirm the authentication attributes of the message source. If the verification fails, the copy is marked as untrusted and written to the diagnostic log. At the same time, depending on the strategy, it is decided whether to make the copy a low-priority candidate for subsequent conflict resolution. After integrity and authentication verification is completed, the structured business content of the payload is extracted and semantic checks are performed on the business fields, such as verifying the legality of latitude and longitude formats, event type codes, and timestamp consistency. Only payloads that pass the semantic legality judgment enter the subsequent deduplication and merging logic. The deduplication and copy comparison mechanism is based on transaction identifiers and payload digests. If there is no confirmed "preferred payload" for this transaction, the current copy is set as the first candidate, and its digest, source satellite ID, reception time, and received signal quality (e.g., RSSI / SNR) are recorded as preferred metadata. A deduplication window is opened locally. The length of the window is determined by the message priority, terminal resources, and policy configuration. Higher-priority messages generally have shorter windows to speed up processing but still allow enough time to receive multiple satellite copies that may arrive. If subsequent copies of the same transaction are received within the window, each copy undergoes the same parsing, integrity check, and digest calculation. Then, its digest is compared with the saved preferred payload digest in chronological order of reception time. If the digests match, it is considered a duplicate copy. To save storage and energy, the payload text of the duplicate copy is deleted or marked as recyclable, while its metadata (source satellite ID, reception time, SNR) is retained to record system behavior and for subsequent performance statistics. If the digests do not match, the conflict resolution process begins, and appropriate handling is taken according to the pre-defined conflict decision rules: if there are version number or sequence number fields between the payloads, the latest version is selected according to the version and sequence number rules. Alternatively, the system can merge patches. If version information is not available, the system will select the payload to be retained based on the comparison of received signal quality, the credibility of the signature version, or the freshness of the message timestamp. The criteria for selection can be priority based on the received SNR, the timestamp closer to the current time, or the signature authority. After the selected payload is confirmed to be retained, the payload that was originally considered the first choice and the payload that was subsequently judged as the second choice will be recorded as "replaced" or "deleted" respectively, and their metadata will be written to the log to support subsequent traceability and auditing. If the payload can be spliced ​​into a complete service (e.g., segmentation or incremental patch), the system will perform reorganization or merging according to the segment number or patch sequence, and the overall integrity and semantic consistency will be verified after merging.

[0054] In parallel with content comparison, a set of reception quality metrics is maintained for each received copy, including instantaneous SNR, RSSI, bit error rate estimation, received carrier-to-noise ratio, and antenna pointing and environmental noise information during reception. Reception quality information is used for two purposes: first, as a reference for selecting retained copies when conflicts occur; and second, as a link performance metric when sending receipts or reporting to the ground network. Receipt fields may include the source satellite ID of the retained copy, a list of deleted copies, and the reception timestamp and SNR of each copy. Therefore, when the base station or network operator receives the receipt, it can be used to adjust subsequent scheduling weights and redundancy strategies. If multiple received satellite copies are completely identical in content, signature, and timestamp, after verifying the first usable copy and delivering it to the upper-layer application, the remaining copies are cleaned up according to the duplicate processing logic to release storage and reduce power consumption. However, necessary metadata should be retained for statistical purposes before cleanup.

[0055] To support segmented messages and reassembly, the terminal maintains a segmented cache and a reassembly timer. The segmented cache is organized by transaction ID, and each segment contains metadata including the segment sequence number and the total number of segments. Each received segment is written to the cache and the reassembly bitmap is updated after it passes integrity verification. Once all segments are received or reassembly is complete, an overall verification is performed, and the complete service is delivered to the upper-layer application. If reassembly is not completed within a preset timeout, failure handling is triggered. Depending on message priority, a retransmission request can be initiated to the base station or an alarm can be generated. The retransmission request includes the transaction ID and missing segment information so that the base station can identify and trigger retransmission. Before upper-layer delivery, a final security policy check is performed. For example, the signature chain of rescue instructions containing operation commands is re-verified to prevent intermediate tampering. Only authenticated services can trigger local control actions or alarm mechanisms; unauthenticated services are reported to the management center for manual or higher-level automated logic to determine whether to execute.

[0056] The multi-satellite collaborative short message communication method provided in this embodiment parses the uplink signal to obtain a candidate satellite set by filtering communication satellites based on the obtained terminal device information. Channel quality is then assessed on the candidate satellite set, and target satellites are obtained by filtering the candidate satellites based on the channel quality score. Data to be transmitted is copied according to the number of target satellites to obtain a data replica set. Tasks are created and data is encapsulated based on the target satellite IDs and the data replica set to generate a transmission task list. Transmission priorities are determined and sorted according to timing constraints to generate a transmission sequence. This application improves the reliability and timeliness of short messages under poor / unstable link conditions by replacing single-point transmission with spatial redundancy and combining link awareness for multi-satellite filtering. It also optimizes bandwidth, energy consumption, and system observability with controllable overhead, making it particularly suitable for application scenarios with strict requirements for reliability and timeliness, such as emergency rescue and low-power IoT alarms.

[0057] Example 2 like Figure 3 The diagram shown illustrates the functional block diagram of a multi-satellite collaborative short message communication device according to an embodiment of this application. This device can be divided into one or more program modules, which are stored in a storage medium and executed by one or more processors to complete the embodiment of this application. The program module referred to in this embodiment is a series of computer program instruction segments capable of performing a specific function. The following description will specifically introduce the function of each program module in this embodiment. Figure 3 As shown, the multi-satellite collaborative short message communication device 1000 may include: a satellite selection module 1100, a channel selection module 1200, a task generation module 1300, and a transmission sequencing module 1400, wherein: The satellite filtering module 1100 is used to parse the target uplink signal to obtain terminal device information when the target uplink signal is received, and to filter communication satellites according to the terminal device information through a preset satellite database to obtain a candidate satellite set. The channel screening module 1200 is used to perform channel quality assessment on each candidate satellite in the candidate satellite set to obtain a channel quality score for each candidate satellite, so as to screen the candidate satellites according to the channel quality score to obtain a target satellite set; The task generation module 1300 is used to copy the data to be sent according to the number of satellites in the target satellite set to obtain a data copy set, and to create tasks and encapsulate data according to the target satellite ID in the target satellite set and the data copy set to generate a sending task list. The sending sorting module 1400 is used to determine and sort the sending priorities of each sending task in the sending task list according to preset timing constraints, and generate a sending sequence.

[0058] As an optional embodiment, the satellite screening module 1100 is specifically used for: The real-time position information, real-time velocity, satellite beam tilt angle and orbital parameters of each satellite are obtained through a preset satellite database, and the signal coverage area of ​​each satellite is calculated based on the real-time position information, the satellite beam tilt angle and the orbital parameters. Based on the signal coverage area and the terminal positioning information, communication satellites are screened to obtain initial candidate satellites for the signal coverage terminal equipment; Based on the terminal positioning information and the satellite beam tilt angle corresponding to each initial candidate satellite, the communication blockage analysis and screening are performed using the preset terrain simulation model data to obtain candidate satellites whose signals are not blocked. The signal coverage time of each candidate satellite is calculated based on the terminal positioning information, the signal coverage area, and the real-time speed to obtain the communication duration of each candidate satellite.

[0059] As an optional embodiment, the channel filtering module 1200 is used for: Based on the real-time location information of each candidate satellite and the terminal positioning information, the communication propagation characteristics are analyzed to obtain the communication loss index of each candidate satellite. The average communicable duration of the candidate satellite set is obtained by averaging the communicable duration and calculating the standard deviation based on the communicable duration and the average communicable duration to obtain the available time index of each candidate satellite. The received operational performance indicators, communication loss indicators, and available time indicators of each candidate satellite are normalized to obtain a standardized indicator set for each candidate satellite. The standardized indicator set is then fused using multiple factors to obtain the channel quality score for the corresponding candidate satellite.

[0060] As an optional embodiment, the channel filtering module 1200 is also used for: The straight-line distance, relative azimuth angle, and relative elevation angle between the terminal device and the corresponding candidate satellite are calculated based on the real-time location information and the terminal positioning information. The satellite transmission gain and terminal reception gain are obtained based on the relative azimuth angle and the relative elevation angle through a preset gain mapping rule. The path loss of each candidate satellite is calculated based on the preset frequency band and the straight-line distance, and the theoretical received power of the terminal device to receive the corresponding candidate satellite is calculated based on the path loss, the satellite transmit gain and the terminal receive gain. The signal-to-noise ratio of the corresponding candidate satellite is calculated based on the theoretical received power, the preset noise baseline, and the preset receiver noise figure.

[0061] As an optional embodiment, the channel filtering module 1200 is also used for: The candidate satellites are sorted according to the channel quality score to obtain the first candidate satellite queue; Target satellites are selected from the first candidate satellite queue based on the preset quality scoring threshold and the channel quality scores of each candidate satellite to obtain the target satellite set.

[0062] As an optional embodiment, the task generation module 1300 is specifically used for: The number of copies of the data to be sent is determined based on the number of satellites in the target satellite set, and a data replica set is obtained by copying the data according to the number of copies and the data to be sent. According to the preset data and satellite allocation strategy, the target satellite IDs in the target satellite set and the data replicas in the data replica set are allocated and combined to generate a data set to be sent; According to the preset short message protocol, each data group in the set of data to be sent is encapsulated to generate a sending task entry and corresponding metadata. The sending task entry and corresponding metadata are then associated and stored according to the preset task list to generate a sending task list.

[0063] As an optional embodiment, the sending sorting module 1400 is specifically used for: The priority level of each transmission task in the transmission task list is determined according to the preset priority strategy and the channel quality score, and the corresponding communication duration is obtained according to the target satellite corresponding to each transmission task. Based on the preset timing constraints, the communicable duration, and the priority level, the sending time is allocated for each sending task to obtain the sending timestamp corresponding to each sending task. The sending tasks are sorted according to the sending timestamp and time order to generate a sending sequence.

[0064] Example 3 Figure 4 This illustration schematically depicts the hardware architecture of a computer device 10000 suitable for implementing a multi-satellite collaborative short message communication method according to Embodiment 3 of this application. In some embodiments, the computer device 10000 may be a terminal device such as a smartphone, wearable device, tablet computer, personal computer, vehicle terminal, game console, virtual device, workbench, digital assistant, set-top box, or robot. In other embodiments, the computer device 10000 may be a rack server, blade server, tower server, or cabinet server (including independent servers or server clusters composed of multiple servers), etc. Figure 4 As shown, the computer device 10000 includes, but is not limited to: a memory 10010, a processor 10020, and a network interface 10030 that can communicate and be linked with each other via a system bus. Wherein: The memory 10010 includes at least one type of computer-readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 10010 may be an internal storage module of the computer device 10000, such as the hard disk or memory of the computer device 10000. In other embodiments, the memory 10010 may also be an external storage device of the computer device 10000, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 10000. Of course, the memory 10010 may also include both the internal storage module and the external storage device of the computer device 10000. In this embodiment, the memory 10010 is typically used to store the operating system and various application software installed on the computer device 10000, such as the program code for a multi-satellite collaborative short message communication method. Furthermore, the memory 10010 can also be used to temporarily store various types of data that have already been output or will be output.

[0065] In some embodiments, processor 10020 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other chip. Processor 10020 is typically used to control the overall operation of computer device 10000, such as performing control and processing related to data interaction or communication with computer device 10000. In this embodiment, processor 10020 is used to run program code stored in memory 10010 or process data.

[0066] Network interface 10030 may include a wireless network interface or a wired network interface, which is typically used to establish a communication link between computer device 10000 and other computer devices. For example, network interface 10030 is used to connect computer device 10000 to an external terminal via a network, establishing a data transmission channel and communication link between computer device 10000 and the external terminal. The network may be an intranet, the Internet, GSM, WCDMA, 4G, 5G, Bluetooth, Wi-Fi, or other wireless or wired networks.

[0067] It should be pointed out that, Figure 4 Only computer devices with components 10010-10030 are shown; however, it should be understood that it is not required to implement all of the shown components, and more or fewer components may be implemented instead.

[0068] In this embodiment, the multi-satellite collaborative short message communication method stored in memory 10010 can also be divided into one or more program modules and executed by one or more processors (such as processor 10020) to complete the embodiment of this application.

[0069] Obviously, those skilled in the art should understand that the modules or steps of the embodiments of this application described above can be implemented using general-purpose computer devices. They can be centralized on a single computer device or distributed across a network of multiple computer devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computer device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the embodiments of this application are not limited to any particular combination of hardware and software.

[0070] It should be noted that the above are merely preferred embodiments of this application and do not limit the scope of patent protection of this application. Any equivalent structural or procedural changes made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of this application.

Claims

1. A multi-satellite collaborative short message communication method, applied to a short message base station, characterized in that, The method includes: When a target uplink signal is received, the uplink signal is parsed to obtain terminal device information. Real-time position information, real-time velocity, satellite beam tilt angle, and orbital parameters of each satellite are obtained through a preset satellite database. The signal coverage area of ​​each satellite is calculated based on the real-time position information, satellite beam tilt angle, and orbital parameters. Communication satellites are screened based on the signal coverage area and terminal positioning information to obtain initial candidate satellites that can cover the terminal device. Communication obstruction analysis and screening are performed using preset terrain simulation model data based on the terminal positioning information and the corresponding satellite beam tilt angles of each initial candidate satellite to obtain candidate satellites whose signals are not obstructed. The signal coverage time of each candidate satellite is calculated based on the terminal positioning information, the signal coverage area, and the real-time velocity to obtain the communicable duration of each candidate satellite. The terminal device information includes terminal positioning information, and the candidate satellite set includes candidate satellites and their corresponding communicable durations. Based on the real-time location information and the terminal positioning information, the straight-line distance, relative azimuth angle, and relative elevation angle between the terminal device and the corresponding candidate satellite are calculated. Satellite transmit gain and terminal receive gain are obtained based on the relative azimuth angle and relative elevation angle using a preset gain mapping rule. The path loss of each candidate satellite is calculated based on a preset frequency band and the straight-line distance. The theoretical received power of the terminal device receiving the corresponding candidate satellite is then calculated based on the path loss, the satellite transmit gain, and the terminal receive gain. The signal-to-noise ratio (SNR) of the corresponding candidate satellite is calculated based on the theoretical received power, a preset noise baseline, and a preset receiver noise figure. The average communicable duration of the candidate satellite set is obtained by averaging the communicable duration. The standard deviation of the length and the average communicable duration is calculated to obtain the available time index of each candidate satellite. The received operation and maintenance performance index, path loss, signal-to-noise ratio and available time index of each candidate satellite are normalized to obtain a standardized index set of each candidate satellite. The standardized index set is then fused by multiple factors to obtain the channel quality score of the corresponding candidate satellite. The candidate satellites are then screened according to the channel quality score to obtain the target satellite set. The gain mapping rule obtains the satellite transmit gain and the terminal receive gain by interpolating or looking up a table at the corresponding azimuth-elevation point of the antenna pattern. When there is no accurate pattern, the main lobe / half power angle parameters given by the manufacturer are used to calculate the satellite transmit gain and the terminal receive gain. Based on the number of satellites in the target satellite set, the data to be sent is copied to obtain a data copy set. Then, based on the target satellite IDs in the target satellite set and the data copy set, tasks are created and data is encapsulated to generate a sending task list. The priority level of each transmission task in the transmission task list is determined according to the preset priority strategy and the channel quality score, and the corresponding communication duration is obtained according to the target satellite corresponding to each transmission task. The transmission time of each transmission task is allocated according to the preset timing constraints, the communication duration, and the priority level to obtain the transmission timestamp corresponding to each transmission task. The transmission tasks are sorted according to the transmission timestamp and the time order to generate a transmission sequence. The timing constraints are a set of conditions that must be met by each transmission task during the transmission time allocation stage.

2. The method according to claim 1, characterized in that, The step of copying the data to be transmitted to obtain a data replica set based on the number of satellites in the target satellite set, and generating a transmission task list based on the target satellite IDs in the target satellite set and the data replica set, includes: The number of copies of the data to be sent is determined based on the number of satellites in the target satellite set, and a data replica set is obtained by copying the data according to the number of copies and the data to be sent. According to the preset data and satellite allocation strategy, the target satellite IDs in the target satellite set and the data replicas in the data replica set are allocated and combined to generate a data set to be sent; According to the preset short message protocol, each data group in the set of data to be sent is encapsulated to generate a sending task entry and corresponding metadata. The sending task entry and corresponding metadata are then associated and stored according to the preset task list to generate a sending task list.

3. A multi-satellite cooperative short message communication device, applied to the multi-satellite cooperative short message communication method of claim 1, characterized in that, The device includes: The satellite filtering module is used to, upon receiving a target uplink signal, parse the target uplink signal to obtain terminal device information, and acquire the real-time position information, real-time velocity, satellite beam tilt angle, and orbital parameters of each satellite through a preset satellite database. It then calculates the signal coverage area of ​​each satellite based on the real-time position information, satellite beam tilt angle, and orbital parameters. Based on the signal coverage area and terminal positioning information, it filters communication satellites to obtain initial candidate satellites that can cover the terminal device. Using preset terrain simulation model data, it performs communication obstruction analysis and filtering based on the terminal positioning information and the corresponding satellite beam tilt angles of each initial candidate satellite to obtain candidate satellites whose signals are not obstructed. Finally, it calculates the signal coverage time of each candidate satellite based on the terminal positioning information, the signal coverage area, and the real-time velocity to obtain the communicable duration of each candidate satellite. The channel filtering module is used to calculate the straight-line distance, relative azimuth angle, and relative elevation angle between the terminal device and the corresponding candidate satellite based on the real-time location information and the terminal positioning information; and to obtain the satellite transmission gain and terminal reception gain based on the relative azimuth angle and the relative elevation angle using a preset gain mapping rule; to calculate the path loss of each candidate satellite based on a preset frequency band and the straight-line distance; and to calculate the theoretical received power of the terminal device receiving the corresponding candidate satellite based on the path loss, the satellite transmission gain, and the terminal reception gain; and to calculate the theoretical received power, a preset noise baseline, and a preset receiver noise level based on the theoretical received power, a preset noise baseline, and a preset receiver noise level. The signal-to-noise ratio (SNR) of the corresponding candidate satellites is calculated; the mean of the available communication duration is calculated to obtain the average available communication duration of the candidate satellite set; the standard deviation is calculated based on the available communication duration and the average available communication duration to obtain the available time index of each candidate satellite; the received operation and maintenance performance index, path loss, SNR, and available time index of each candidate satellite are normalized to obtain a standardized index set of each candidate satellite; and the standardized index set is fused by multiple factors to obtain the channel quality score of the corresponding candidate satellite; the candidate satellites are then screened based on the channel quality score to obtain the target satellite set. The task generation module is used to copy the data to be sent according to the number of satellites in the target satellite set to obtain a data copy set, and to create and encapsulate tasks according to the target satellite IDs in the target satellite set and the data copy set to generate a sending task list. The transmission sorting module is used to determine the priority level of each transmission task in the transmission task list according to a preset priority strategy and the channel quality score, and to obtain the corresponding communication duration according to the target satellite corresponding to each transmission task; to allocate transmission time for each transmission task according to preset timing constraints, the communication duration, and the priority level, and to obtain the transmission timestamp corresponding to each transmission task; and to sort the transmission tasks according to the transmission timestamp and time order to generate a transmission sequence.

4. A computer device, characterized in that, include: At least one processor; and A memory communicatively connected to the at least one processor; wherein: The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 2.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 2.

Images