Method for bearer switching of cluster service, storage medium and program product

Abstract

This application provides a method, storage medium, and program product for bearer switching of trunking services. By having a first satellite actively initiate the bearer switching process, autonomously determine a candidate second satellite, and directly interact with the second satellite via inter-satellite messages to negotiate and determine a unified service switching time, the method avoids the problem of delayed transmission of switching instructions caused by satellite-to-ground communication delays without relying on the ground trunking control center to issue switching commands. The second satellite accurately starts the service bearer according to the negotiated time, ensuring consistent service switching timing and smooth process. This effectively avoids trunking service interruption or service quality degradation, and ultimately improves the efficiency of bearer switching of trunking services between satellites.

Description

Technical Field

[0001] This application relates to the field of satellite communication technology, and in particular to a method for switching the bearer of trunking services, a storage medium, and a program product. Background Technology

[0002] With the rapid development of the satellite communication industry, low-Earth orbit satellite constellations, with their advantages of low latency and wide coverage, have gradually become the core carriers for trunking communication services. However, due to factors such as orbital motion, satellites need to use flexible and efficient handover mechanisms to avoid service interruption or service quality degradation.

[0003] In related technologies, when the ground cluster control center detects that the currently carrying satellite can no longer provide services, it sends a switching command to the current satellite and the backup satellite respectively. After receiving the command, the current satellite stops carrying services, and the backup satellite starts the service reception process.

[0004] However, the delay in satellite-to-ground communication can lead to a lag in the transmission of handover instructions, resulting in low efficiency in the handover of trunking services between satellites. Summary of the Invention

[0005] The trunking service bearer handover method, storage medium, and program product provided in this application embodiment are used to improve the bearer handover efficiency of trunking services between satellites.

[0006] In a first aspect, embodiments of this application provide a method for switching the bearer of a trunking service, applied to a first satellite, the first satellite being the satellite currently carrying the first service of a first trunking, the method comprising:

[0007] A first identifier is determined, which is used to indicate whether the first satellite needs to switch the bearer of the first service;

[0008] When the first identifier indicates that the first satellite needs to switch the bearer of the first service, multiple second satellites are identified as alternative satellites that can bear the first service.

[0009] Send a first message to multiple second satellites, the first message being used to request the second satellites to carry the first service;

[0010] Receive a second message sent by the second satellite, the second message being used to instruct the second satellite to confirm that it will carry the first service at the first time;

[0011] Based on the second message, a third message is sent to the corresponding second satellite. The third message is used to instruct the first satellite to confirm that it will terminate the carrying of the first service at the first time.

[0012] When the real-time time is the same as the first time, the first service is terminated.

[0013] Secondly, embodiments of this application provide a method for switching the bearer of a cluster service, the method comprising:

[0014] Receive the first message sent by the first satellite, the first message being used to request the second satellite to carry the first service of the first cluster;

[0015] Based on the first message, a second identifier is determined, which is used to indicate whether the second satellite can or cannot carry the first service;

[0016] When the second identifier indicates that the second satellite can carry the first service, the second message is determined based on the first message. The second message is used to instruct the second satellite to confirm that it can carry the first service at the first time.

[0017] Send a second message to the first satellite;

[0018] Receive a third message sent by the first satellite. The third message is used to instruct the first satellite to confirm that the first service is terminated at the first time.

[0019] When the real-time time equals the first time, the first service is carried.

[0020] Thirdly, embodiments of this application provide a satellite, including: a memory and a processor;

[0021] The memory stores instructions that the computer executes;

[0022] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above, or to perform the second aspect and / or various possible implementations of the second aspect as described above.

[0023] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect, or to implement the second aspect and / or various possible implementations of the second aspect.

[0024] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect, or implements the second aspect and / or various possible implementations of the second aspect.

[0025] The trunking service bearer switching method, storage medium, and program product provided in this application embodiment, through the first satellite actively initiating the bearer switching process, autonomously determining the candidate second satellite, and directly exchanging inter-satellite messages with the second satellite to negotiate and determine a unified service switching time, effectively avoids the problem of delayed switching command transmission caused by satellite-to-ground communication delays without relying on the ground trunking control center to issue switching commands. The second satellite accurately starts the service bearer according to the negotiated time, ensuring consistent service switching sequence and smooth process, effectively avoiding trunking service interruption or service quality degradation, and ultimately improving the efficiency of trunking service bearer switching between satellites. Attached Figure Description

[0026] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0027] Figure 1 A schematic diagram illustrating the scenario of switching between the first and second satellites as provided in an embodiment of this application;

[0028] Figure 2 Interaction diagram of the bearer switching method for cluster services provided in the embodiments of this application Figure 1 ;

[0029] Figure 3 Interaction diagram of the bearer switching method for cluster services provided in the embodiments of this application Figure 2 ;

[0030] Figure 4 A schematic diagram of the bearer switching device for the first cluster service provided in this application embodiment;

[0031] Figure 5 A schematic diagram of the structure of the bearer switching device for the second cluster service provided in this application embodiment;

[0032] Figure 6 This is a schematic diagram of the satellite structure provided in an embodiment of this application.

[0033] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0034] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0035] To address the technical problem of delayed handover command transmission due to satellite-to-ground communication latency, resulting in low handover efficiency for inter-satellite trunking services, the following technical concept is proposed: the entire handover process is completed through direct interaction between the first and second satellites, without ground intervention. For the initiating first satellite, a proactive handover process is designed: it autonomously determines whether a handover is needed and identifies a candidate second satellite; then, it negotiates a unified handover time with the second satellite via inter-satellite messages; finally, it precisely terminates its own service bearer at the agreed time, achieving autonomy in handover initiation and timing control. For the responding second satellite, a passive response and collaborative approach is designed: upon receiving the first satellite's bearer request, it autonomously determines its bearer capacity; upon confirmation of bearer capability, it sends back a response message containing a unified handover time; upon receiving confirmation of bearer termination from the first satellite, it precisely starts service bearer operation at the agreed time, forming a closed-loop inter-satellite two-way collaboration. Direct inter-satellite interaction replaces satellite-to-ground command transmission, eliminating the impact of satellite-to-ground latency on handover. Simultaneously, the unified handover time ensures seamless service bearer integration, ultimately improving the handover efficiency for inter-satellite trunking services.

[0036] Figure 1 This is a schematic diagram illustrating the scenario of switching between the first and second satellites, as provided in an embodiment of this application. Figure 1 As shown, the scenario includes a first satellite, a second satellite, multiple cluster terminal devices, and a first control device.

[0037] against Figure 1 In the upper half, the first satellite is positioned above region B, allocating multicast beams and time-frequency resources to the first cluster located in that region to carry its voice / data trunking services. Meanwhile, the coverage area of ​​the second satellite includes region A, serving as a potential alternative carrier satellite. The trunking terminal equipment stably receives trunking services via the multicast beams of the first satellite, and the first control device interacts with the first satellite to complete group management and resource scheduling.

[0038] Due to the high-speed movement of satellites, over time, the nadir point of the first satellite gradually moves out of region B, and its coverage no longer includes that region; while the nadir point of the second satellite gradually moves above region B, expanding its coverage to include region B. Without service handover, the services of the first cluster will be interrupted due to the coverage of the first satellite moving out of the region. Therefore, a collaborative mechanism is needed to achieve seamless service takeover.

[0039] When the satellite moves to a new location ( Figure 1 In the second half, through the trunking service bearer handover method provided in this application embodiment, the second satellite formally takes over the trunking service bearer of the first trunking: the second satellite allocates new multicast beams and time-frequency resources to the trunking terminal equipment in region B, and continues to transmit services; the first satellite then stops providing trunking service resources to region B. The trunking terminal equipment receives the multicast signal from the second satellite, achieving uninterrupted service continuity.

[0040] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0041] Figure 2 Interaction diagram of the bearer switching method for cluster services provided in the embodiments of this application Figure 1 The trunking service bearer switching method provided in this application embodiment is applicable to any satellite. For example... Figure 2 As shown, the method includes:

[0042] S201. The first satellite determines the first identifier, which is used to indicate whether the first satellite needs to switch the bearer of the first service.

[0043] Among them, the first satellite refers to the satellite currently carrying the first service. As the initiator of the handover process, it is responsible for determining whether a handover is needed, initiating a handover request, and terminating the handover on time. The first identifier is a judgment identifier generated by the first satellite. Its core function is to indicate whether it needs to switch the first service it carries, which is the key basis for triggering subsequent handover processes. The first service refers to communication, data transmission, and other services generated by the first cluster, which need to be carried by satellite to realize the business interaction within the cluster and between the cluster and the outside world.

[0044] Specifically, the first satellite uses its own sensors and system monitoring module to monitor its own carrying status (such as resource occupancy, signal strength, orbital position change trend, etc.) and the first service requirement in real time, and generates a first identifier based on the detection results. This identifier is only used by the first satellite to determine whether it needs to switch the carrying of the first service—if the identifier indicates "switching is required", the subsequent S202 step is triggered; if it indicates "switching is not required", the current carrying status is maintained and the process terminates.

[0045] S202. When the first identifier indicates that the first satellite needs to switch the bearer of the first service, multiple second satellites are determined. The second satellites are alternative satellites that can bear the first service.

[0046] Among them, the second satellite refers to the satellite that can be selected as the first service bearer. As the responder in the bearer switching process, it is responsible for receiving the switching request, judging its own bearing capacity, and undertaking the service on time. The first cluster includes multiple cluster terminal devices (such as cluster communication mobile phones, vehicle terminals, etc.) and the first control device (the device used to manage terminal communication and service scheduling within the cluster), which is the main object of this service bearing.

[0047] Specifically, when the first satellite is triggered by the first identifier indicating "switching is required," it uses satellite network topology information and a pool of candidate satellite resources to select multiple second satellites capable of carrying the first service. The selection process considers factors such as the real-time resource availability of the second satellites, their coverage of the first cluster, and service compatibility to ensure that the selected second satellites are valid candidates, providing multiple options for subsequent requests to undertake services.

[0048] S203. The first satellite sends a first message to multiple second satellites. The first message is used to request the second satellites to carry the first service.

[0049] The first message refers to the handover request message sent by the first satellite to the second satellite, which is used to clearly inform the second satellite of the first service information that needs to be carried and request it to take over the service.

[0050] Specifically, the first satellite generates a first message (containing key information such as the first service type, service traffic, and required resources) for each of the identified second satellites, and sends the message to each second satellite through the inter-satellite communication link to formally initiate the bearer switching request for the first service.

[0051] S204. Based on the first message, the second satellite determines a second identifier, which is used to indicate whether the second satellite can or cannot carry the first service.

[0052] The second identifier is a judgment identifier generated by the second satellite. Its core function is to indicate whether it has the ability to carry the first service (such as resource availability, signal coverage, compatibility, etc.), which is the core basis for responding to the handover request.

[0053] Specifically, after receiving the first message sent by the first satellite, the second satellite immediately detects and evaluates its own status. The evaluation includes the current resource usage, whether it can cover the area where the first cluster is located, and the compatibility with the first service. Based on the evaluation results, a second identifier is generated to indicate whether it can "carry" or "cannot carry" the service. If the identifier indicates "cannot carry", the subsequent actions are terminated; if it indicates "can carry", the process proceeds to step S205.

[0054] S205. When the second identifier indicates that the second satellite can carry the first service, the second satellite determines the second message based on the first message. The second message is used to instruct the second satellite to confirm that it can carry the first service at the first time.

[0055] The second message refers to the confirmation response message sent by the second satellite to the first satellite, which is used to clearly inform the first satellite that it agrees to take over the service and to determine the specific service takeover time (i.e., the first time). The first time is the service switching reference time determined by the second satellite and confirmed by both parties. It is a unified time node when the first satellite ends its service and the second satellite begins its service, which is used to ensure seamless service switching.

[0056] Specifically, when the second satellite is triggered by the second identifier indicating "can carry", it determines the first time and generates a second message based on the service information in the first message and its own carrying plan. This message must clearly include two core contents: "confirmation of undertaking the first service" and "undertaking time is the first time", to ensure that the first satellite accurately obtains the handover timing information.

[0057] S206, The second satellite sends a second message to the first satellite.

[0058] Specifically, the second satellite will send the confirmed second message back to the requesting first satellite via the inter-satellite communication link, thus confirming its willingness to accept the handover and informing the first satellite of its intention to accept the handover and the specific handover time. If multiple second satellites agree to accept the handover, the first satellite will receive multiple second messages and can subsequently select a target satellite based on preset rules (such as optimal resources or best coverage).

[0059] S207. Based on the second message, the first satellite sends a third message to the corresponding second satellite. The third message is used to instruct the first satellite to confirm that it will terminate the carrying of the first service at the first time.

[0060] The third message refers to the termination of service confirmation message sent by the first satellite to the corresponding second satellite, which is used to clearly inform the corresponding second satellite that it will terminate the service service at the first time to ensure that the handover sequence is consistent.

[0061] Specifically, after the first satellite receives the second message sent by the second satellite, it confirms the switching time (first time) and the corresponding second satellite based on the message, and generates a third message. The core content of the message is "confirming the termination of the first service at the first time". The first satellite then sends the message to the corresponding second satellite to synchronize the switching sequence and avoid service disconnection or overlapping service.

[0062] S208. When the real-time time of the first satellite is the same as the first time, the first service will be terminated.

[0063] Among them, real-time time refers to the current time obtained by the first satellite in real time, which is used to compare with the first time and trigger the action of ending its carrying.

[0064] Specifically, the first satellite acquires the current time (i.e., real-time time) in real time and continuously compares the real-time time with the first time. When the two are completely consistent, it immediately executes the termination of the carrying operation, stops the signal transmission and resource allocation services for the first service, completes the termination of its own carrying task, and ensures synchronization with the timing of the receiving action of the target satellite.

[0065] S209, the second satellite carries the first service when the real-time time equals the first time.

[0066] Among them, real-time time refers to the current time obtained by the second satellite in real time, which is used to compare with the first time and trigger the start of its own actions.

[0067] Specifically, the second satellite acquires the current time (i.e., real-time time) in real time and continuously compares the real-time time with the first time. When the two are completely consistent, the bearer operation is immediately executed, and services such as signal reception, resource allocation, and data forwarding for the first service are initiated. The satellite officially takes over the first service, completes the entire bearer switching process, and ensures seamless service connection.

[0068] For the first service to be received, the second satellite payload first determines whether the service is a voice trunking service or a data trunking service based on its quality of service attributes. Then, considering the time-domain and frequency resource occupancy status within its own beam, it selects a trunking service beam suitable for the transmission of the first service. For voice trunking services in the first cluster, the second satellite payload explicitly defines the priority, guaranteed bit rate, and other core parameters of this type of service, and simultaneously sets the frequency resource requirements and time-domain attribute requirements within the selected beam. For example, it configures the number of frequency resource blocks for voice services to be 2, the time-domain semi-static scheduling period to be 20ms, and specifies the corresponding subframe and time slot resources. For data trunking services in the first cluster, the second satellite payload defines its service priority, non-guaranteed bit rate, and other parameters, and simultaneously clarifies the frequency-domain resource allocation range and time-domain scheduling attributes of this data service within the selected beam. After completing the parameter configuration, the second satellite payload broadcasts the above service parameters, beam information, and group establishment instructions to all trunking terminal devices in the paging information for the establishment of the first cluster group, formally initiating the group establishment process of the first cluster, and notifying each satellite terminal in the group to continuously monitor the beam and resource channels corresponding to the trunking service. Once the first cluster group is established, the cluster control center sends the first service data to the second satellite payload. The second satellite payload then accurately transmits the received first service data to each cluster terminal device within the first cluster via an air interface link, completing the service reception and data transmission.

[0069] The trunking service bearer handover method provided in this application embodiment involves the first satellite actively initiating the bearer handover process, autonomously determining a candidate second satellite, and directly exchanging inter-satellite messages with the second satellite to negotiate and determine a unified service handover time. This eliminates the need to rely on the ground trunking control center to issue handover commands, effectively avoiding the problem of delayed handover command transmission caused by satellite-to-ground communication delays. The second satellite accurately starts the service bearer according to the negotiated time, ensuring consistent service handover timing and smooth process. This effectively avoids trunking service interruption or service quality degradation, ultimately improving the efficiency of trunking service bearer handover between satellites.

[0070] Figure 3 Interaction diagram of the bearer switching method for cluster services provided in the embodiments of this application Figure 2 .like Figure 3 As shown, the method includes:

[0071] S301. The first satellite determines the first identifier, which indicates whether the first satellite needs to switch the bearer of the first service.

[0072] In one possible implementation, a fifth time is obtained, which is the end time of the first satellite carrying the first service; a sixth time is determined as the difference between the fifth time and the real time; if the sixth time is less than or equal to a first threshold, a first identifier is determined to indicate that the first satellite needs to switch the carrying of the first service; if the sixth time is greater than the first threshold, the first identifier is determined to indicate that the first satellite does not need to switch the carrying of the first service.

[0073] Among them, real-time time refers to the current time acquired by the first satellite in real time; fifth time refers to the end time of the first satellite's preset or planned carrying of the first service, which is the predetermined termination node of the service carrying; sixth time refers to the difference between the fifth time and the real-time time, which is used to quantify the remaining time between the current time and the predetermined end time of the service; first threshold refers to the preset time threshold for determining whether a switch needs to be triggered in advance, which is set by the system based on factors such as service stability and switch time.

[0074] Specifically, the process first acquires the real-time fourth time and the preset fifth time. Then, it calculates the sixth time (the difference between the fifth time and the real-time time). The sixth time is then compared to a first threshold. If the sixth time is less than or equal to the first threshold, it indicates that the scheduled end time of the service is too close, requiring an early switch to ensure service continuity; in this case, the first flag indicates "switching is required." If the sixth time is greater than the first threshold, it indicates that the remaining time is sufficient, and immediate switching is unnecessary; in this case, the first flag indicates "switching is not required." This implementation method provides a precise basis for generating the first flag through quantitative judgment in the time dimension.

[0075] S302. When the first identifier is used to indicate that the first satellite needs to switch the bearer of the first service, multiple second satellites are determined. The second satellites are alternative satellites that can bear the first service.

[0076] S303. The first satellite sends a first message to multiple second satellites. The first message is used to request the second satellites to carry the first service.

[0077] In one possible implementation, the first message includes at least one of the following: a first satellite identifier of a first satellite; a second satellite identifier of a second satellite; a first group identifier of a first cluster; first group service configuration information corresponding to the first group identifier, wherein the first group service configuration information includes at least one of the following: first group service priority information, bearer definition information of signaling radio bearer, bearer definition information of data radio bearer, and quality of service information of the first service; and a sixth time.

[0078] Specifically, the first satellite identifier is a unique code within the satellite network (such as a satellite ID), used by the second satellite to quickly identify the initiator of the switchover request, avoiding confusion of request sources in multi-satellite scenarios. It also associates with the historical carrying records of the first satellite to assist in determining service continuity requirements. The second satellite identifier is a unique code corresponding to each candidate second satellite, enabling precise targeted delivery of the first message. The first group identifier is a globally unique identifier for the first cluster (such as a cluster number).

[0079] The first group of service configuration information serves as the core parameter set, with each sub-item serving a specific purpose: service priority information (e.g., voice service has higher priority than data service), used by the second satellite to determine the scheduling order when multiple services are concurrent, ensuring uninterrupted high-priority services; bearer definition information for signaling radio bearers, specifying the link type, encryption method, and resource allocation quota for controlling signaling transmission, ensuring stable signaling interaction during handover; bearer definition information for data radio bearers, specifying the link bandwidth, modulation and coding scheme, and retransmission mechanism for service data transmission, adapting to the needs of cluster services at different rates; and service quality information, including quantitative indicators such as end-to-end latency, throughput, and packet loss rate (e.g., voice service latency ≤ 50ms, packet loss rate < 1%), which the second satellite must determine based on its own capabilities to ensure it meets these indicators, avoiding substandard service quality after takeover.

[0080] The sixth time is the remaining carrying time of the first satellite (the fifth time - the real-time time). The second satellite can plan its own preparation process (such as resource reservation and parameter calibration) based on this time. If the sixth time is too short (such as less than the handover preparation time), feedback can be given in advance to adjust the takeover sequence and ensure that the handover action proceeds in an orderly manner.

[0081] S304. The second satellite determines a second identifier based on the first message. The second identifier is used to indicate whether the second satellite can or cannot carry the first service.

[0082] S305. When the second identifier indicates that the second satellite can carry the first service, the second satellite determines the second message based on the first message. The second message is used to instruct the second satellite to confirm that it can carry the first service at the first time.

[0083] In one possible implementation, the system includes: a first satellite identifier for a first satellite; a second satellite identifier for a second satellite; time difference information between the first and second satellites; a first group identifier for a first cluster; a first service beam identifier for the first cluster; a first service time pattern corresponding to the first service beam identifier, the first service time pattern including at least one of a first beam service period, a first subframe start time, and a first subframe duration; a first time; a first activation frame number corresponding to the first time; a first frequency point corresponding to the first service beam identifier; first frequency domain configuration information for the first service; first time domain configuration information for the first service; and a first cell identifier corresponding to the first service beam identifier.

[0084] Specifically, the first / second satellite identifier reuses the identity code from the first message. This serves two purposes: first, the first satellite verifies the identity of the feedback provider, eliminating invalid interference messages; second, it establishes a handover association file between the two satellites, facilitating subsequent fault tracing. The time difference information is the local clock deviation between the first and second satellites (calculated through satellite timing system calibration, with microsecond-level accuracy). The second satellite incorporates this deviation value into the message, allowing the first satellite to adjust its local clock accordingly. This ensures complete consistency in the perception of the "first time" between both satellites, preventing service interruptions caused by timing discrepancies.

[0085] The first group identifier is associated with the target cluster, and the first service beam identifier corresponds to the specific beam code of the area covered by the second satellite in the first cluster area (in the case of satellite multi-beam scenario, different beams correspond to different ground coverage areas). The combination of the two can accurately locate the service object and coverage area, ensure that the second satellite activates the corresponding beam resources, and avoid resource waste caused by beam misactivation.

[0086] The first service time pattern is the working timing plan for the beam corresponding to the second satellite. The beam service period refers to the time interval between beams repeatedly covering the target area (e.g., 100ms / cycle), the subframe start time refers to the specific subframe number in which the beam starts transmitting signals in each cycle (e.g., the 5th subframe), and the subframe duration refers to the number of subframes that the beam works in a single operation (e.g., 8 subframes).

[0087] The first time is the unified switching reference time (e.g., time 12:00:00.000), and the first active frame number is the system frame number corresponding to that time point (e.g., frame number 10086). Frame-level precision can achieve millisecond-level synchronization of switching actions, avoiding the loss of business data caused by cross-frame switching.

[0088] The first frequency point is the center frequency of service transmission (such as a specific frequency point in the X band). The frequency domain configuration information includes the subcarrier spacing (such as 15kHz) and the resource block allocation range (such as resource blocks 10-20). The time domain configuration information includes the time slot ratio (such as uplink-downlink time slot ratio of 3:1) and the symbol number allocation (such as 14 symbols per time slot). The three clearly define the resource boundaries of service transmission and ensure that the transmission parameters of the first satellite, the second satellite and the trunk terminal are consistent.

[0089] The first cell identifier is the virtual cell number under the beam corresponding to the second satellite (in satellite communication, a single beam corresponds to one virtual cell).

[0090] S306, The second satellite sends a second message to the first satellite.

[0091] S307. Based on the second message, the first satellite sends a third message to the corresponding second satellite. The third message is used to instruct the first satellite to confirm that it will terminate the carrying of the first service at the first time.

[0092] S308. Based on the second message, the first satellite identifies the corresponding second satellite as the target satellite and sends a fourth message to the first control device of the first cluster. The fourth message is used to request that the first service be switched to the target satellite at the first time.

[0093] Among them, the target satellite refers to the final recipient selected by the first satellite from multiple second satellites that agree to take over the service; the fourth message refers to the handover request message sent by the first satellite to the first control device, the core function of which is to request the control device to switch the service to the target satellite synchronously at the first time.

[0094] Specifically, based on the second message confirming the takeover capacity and timing of each second satellite, the optimal second satellite is selected as the target satellite; then a fourth message is generated, specifying the handover time (first time) and target satellite information, and sent to the first control device to realize the synchronization of the handover request to the cluster control layer, ensuring the overall coordinated handover of the cluster.

[0095] S309. The first satellite receives the fifth message sent by the first control device. The fifth message is used to instruct the first control device to confirm that the first service will be switched to the target satellite at the first time.

[0096] The fifth message refers to the confirmation message sent by the first control device to the first satellite, which indicates that the control device has confirmed the handover arrangement and agrees to switch the service to the target satellite as soon as possible.

[0097] Specifically, the system receives the fifth message sent by the first control device, confirms that the control layer has synchronized the handover plan, completes the two-way confirmation of the handover request, provides the triggering conditions for subsequent notification of handover matters to the terminal devices, and ensures the coordination and consistency of the cluster control device, satellite, and terminal.

[0098] S310. Based on the fifth message, the first satellite sends a sixth message to each cluster terminal device of the first cluster. The sixth message is used to notify the cluster terminal devices that they have established a communication connection with the target satellite at the first time.

[0099] The sixth message refers to the handover notification message sent by the first satellite to each terminal device in the first cluster. Its core function is to inform the terminal devices of the handover time and the target satellite, so that they can prepare for communication connection in advance.

[0100] Specifically, after the control layer confirms the handover based on the fifth message, a sixth message is generated, specifying the first time and the target satellite identifier, and sent to each terminal device in the first cluster; this ensures that each terminal device is aware of the handover arrangements in a timely manner, completes the adaptation of communication parameters with the target satellite in advance, and avoids disconnection during the handover.

[0101] Optionally, if some cluster terminal devices do not receive the sixth message and cannot obtain the new cluster service information (including beam information, frequency / time domain resource configuration, service access parameters, etc.) corresponding to the target satellite (i.e., the second satellite), these cluster terminal devices will proactively initiate a group service joining message. The group service joining message carries key information such as its own terminal identifier and the first group identifier of the first cluster, and is sent to the cluster service service center. After receiving the group service joining message, the cluster service service center, based on the synchronized first service handover plan (including target satellite information and service configuration parameters), sends cluster service information to these cluster terminal devices through a pre-established dedicated bearer. The cluster service information fully includes the cluster service bearer parameters, monitoring channel information, and access timing requirements of the target satellite (second satellite). Based on the received new cluster service information, the cluster terminal devices quickly complete parameter configuration and accurately monitor the cluster services of the target satellite (second satellite) payload in space, ensuring timely access to the new service link, guaranteeing the continuity of their own cluster services, and avoiding service interruption due to the lack of a sixth message.

[0102] S311. The second satellite receives the seventh message sent by the first control device of the first cluster. The seventh message is used to request the establishment of a bearer with the second satellite for the first service.

[0103] Specifically, the seventh message refers to the bearer establishment request message sent by the first control device to the second satellite. Its core function is to request the second satellite to establish a communication link and resource bearer for carrying the first service. Receiving the seventh message sent by the first control device clarifies the bearer establishment request initiated by the control layer, provides triggering conditions for subsequent bearer resource configuration, and realizes bearer coordination between the trunking control device and the second satellite.

[0104] S312. Based on the seventh message, the second satellite establishes a bearer with the first control device for the first service and sends an eighth message to the first control device. The eighth message is used to instruct the second satellite to confirm the establishment of the bearer with the first control device for the first service.

[0105] Specifically, the eighth message refers to the bearer establishment confirmation message fed back by the second satellite to the first control device, indicating that the bearer has been successfully established and can be used to accept services at any time. Based on the service configuration requirements in the seventh message, the corresponding resources are configured, and the service bearer (including signaling bearer and data bearer) between the second satellite and the first control device is established. After the bearer is established, the eighth message is generated and sent to the first control device to complete the two-way confirmation of the bearer establishment, laying a solid foundation for accepting services as soon as possible.

[0106] S313. When the real-time time of the first satellite is the same as the first time, the first service will be terminated.

[0107] S314. When the real-time time of the second satellite equals that of the first satellite, it carries the first service.

[0108] Through the interaction process between the first satellite, the first control device, and the trunking terminal devices, full coordination between the satellite-side handover plan and the trunking side was achieved: First, the handover confirmation with the trunking control device was completed through the fourth and fifth messages to ensure that the trunking management layer synchronized the handover sequence and target satellite information. Then, the sixth message notified each terminal device in advance, allowing the terminals to reserve time to complete preparations such as communication parameter adaptation and link pre-synchronization with the target satellite. This effectively avoided the response lag of the trunking control device and terminals at the moment of handover, filled the gap in the connection between inter-satellite handover and internal trunking coordination, significantly improved the smoothness of trunking service handover, ensured that voice, data and other trunking services were uninterrupted and uninterrupted during the handover process, and enhanced the stability of overall service transmission.

[0109] By introducing real-time, fifth time, sixth time, and first threshold, the judgment of "whether a switchover is needed" is transformed into a quantifiable time difference comparison, replacing subjective or experience-based judgment. It can dynamically decide the timing of the switchover based on the remaining carrying capacity of the first satellite: when the remaining carrying capacity is insufficient, the switchover process is triggered in advance, reserving sufficient time for subsequent actions such as alternative satellite evaluation, carrying capacity establishment, and cluster coordination; when the remaining carrying capacity is sufficient, the current carrying capacity is maintained, avoiding unnecessary switchover operations that would waste resources. This ensures that services are smoothly switched over before the satellite's predetermined carrying capacity ends, improves satellite resource utilization, enhances the scientific nature and flexibility of the switchover decision-making, and adapts to application scenarios with different service durations and different satellite orbital characteristics.

[0110] By clearly defining the core components of the first message, the handover request information was transmitted accurately and efficiently: Identification information (satellite identifier, group identifier) ​​ensures that the second satellite can quickly locate the requesting subject and target service, avoiding information confusion in multi-satellite and multi-cluster scenarios; Service configuration information (priority, bearer definition) provides the second satellite with the core parameter basis for undertaking the service, enabling it to quickly assess whether its own resources match the service requirements without initiating additional parameter query requests; The sixth time allows the second satellite to accurately grasp the remaining bearer time of the first satellite, rationally plan its own preparation process, reduce assessment errors or handover timing conflicts caused by incomplete information, and significantly improve the efficiency and accuracy of the second satellite's assessment, laying the foundation for the smooth progress of the subsequent handover process.

[0111] By establishing a bearer connection between the second satellite and the first control device, the service bearer link was pre-established. After receiving the seventh message, the second satellite could complete the bearer configuration (including signaling and data bearers) with the trunking control device before the handover reference time (first time), and confirm the completion of bearer establishment via the eighth message. This avoided link delays or service interruptions caused by restarting bearer establishment at the moment of handover. Simultaneously, this process enabled bearer coordination between the second satellite and the trunking control device, ensuring that the second satellite had the necessary link conditions to undertake services at the time of handover. The trunking control device could also simultaneously complete the switching of service data forwarding paths, further guaranteeing seamless connection of trunking services from the first satellite to the second satellite and improving the real-time performance and reliability of service transmission during the handover process.

[0112] By refining the components of the second message, the solution achieves full-dimensional transmission and multi-dimensional collaboration of handover information: time difference information ensures accurate clock calibration between the first and second satellites, avoiding handover asynchrony caused by timing deviations; beam, frequency domain, time domain, and cell identifier information enable the first satellite, trunking control equipment, and terminals to accurately adapt to the service resource configuration of the second satellite, completing beam alignment, frequency adjustment, and cell search in advance; activation frame number and service time pattern achieve fine-grained timing synchronization at the frame and subframe levels, adapting to the service requirements of multi-beam and high-dynamic satellite scenarios. Overall, this solution solves the problems of mismatched handover parameters and timing asynchrony in complex satellite communication scenarios by enriching the information dimensions of the second message, improving the adaptability and accuracy of the handover process, and ensuring stable handover of trunking services in high-dynamic and multi-resource configuration scenarios.

[0113] Figure 4 This is a schematic diagram of the structure of the bearer switching device for the first cluster service provided in an embodiment of this application. Figure 4 As shown, the bearer switching device 40 for the first cluster service includes a processing module 401, a communication module 402, and a switching module 403.

[0114] Processing module 401 is used to determine a first identifier, which is used to indicate whether the first satellite needs to switch the bearer of the first service;

[0115] The processing module 401 is further configured to determine multiple second satellites when the first identifier is used to indicate that the first satellite needs to switch the bearer of the first service, wherein the second satellites are used to indicate alternative satellites that can bear the first service;

[0116] Communication module 402 is used to send a first message to multiple second satellites, the first message being used to request the second satellites to carry a first service;

[0117] The communication module 402 is also used to receive a second message sent by the second satellite, the second message being used to instruct the second satellite to confirm that it will carry the first service at the first time.

[0118] The communication module 402 is also used to send a third message to the corresponding second satellite based on the second message. The third message is used to instruct the first satellite to confirm that it will terminate the carrying of the first service at the first time.

[0119] The switching module 403 is used to terminate the carrying of the first service when the real-time time is the same as the first time.

[0120] In one possible implementation, the communication module 402 is further configured to:

[0121] Based on the second message, the corresponding second satellite is identified as the target satellite, and a fourth message is sent to the first control device of the first cluster. The fourth message is used to request that the first service be switched to the target satellite at the first time.

[0122] Receive a fifth message sent by the first control device. The fifth message is used to instruct the first control device to confirm that the first service is switched to the target satellite at the first time.

[0123] Based on the fifth message, a sixth message is sent to each cluster terminal device in the first cluster. The sixth message is used to notify the cluster terminal devices that they have established a communication connection with the target satellite at the first moment.

[0124] In one possible implementation, the processing module 401 is specifically used for:

[0125] Obtain the fifth time, which is the end time of the first service carried by the first satellite;

[0126] The sixth time is determined to be the difference between the fifth time and the real-time time;

[0127] If the sixth time is less than or equal to the first threshold, then the first identifier is determined to indicate that the first satellite needs to switch the bearer of the first service;

[0128] If the sixth time exceeds the first threshold, then the first identifier is determined to indicate that the first satellite does not need to switch the bearer of the first service.

[0129] In one possible implementation, the first message includes at least one of the following:

[0130] The first satellite identifier of the first satellite;

[0131] The second satellite's second satellite identifier;

[0132] The first group identifier of the first cluster;

[0133] The first group identifier corresponds to the first group service configuration information, which includes at least one of the following: first group service priority information, signaling radio bearer bearer definition information, data radio bearer bearer definition information, and service quality information of the first service.

[0134] The sixth time.

[0135] Figure 5 This is a schematic diagram of the structure of the bearer switching device for the second cluster service provided in an embodiment of this application. Figure 5 As shown, the bearer switching device 50 for the second cluster service includes an acquisition module 501, a determination module 502, and a bearer module 503.

[0136] The acquisition module 501 is used to receive a first message sent by the first satellite, the first message being used to request the second satellite to carry the first service of the first cluster;

[0137] The determining module 502 is used to determine a second identifier based on the first message. The second identifier is used to indicate whether the second satellite can or cannot carry the first service.

[0138] The determining module 502 is further configured to determine a second message based on the first message when the second identifier indicates that the second satellite can carry the first service. The second message is used to instruct the second satellite to confirm that it can carry the first service at the first time.

[0139] The acquisition module 501 is also used to send a second message to the first satellite;

[0140] The acquisition module 501 is also used to receive a third message sent by the first satellite, the third message being used to instruct the first satellite to confirm that it will terminate the carrying of the first service at the first time.

[0141] The bearer module 503 is used to obtain the real-time third time. When the third time is equal to the first time, it carries the first service.

[0142] In one possible implementation, the acquisition module 501 is further configured to:

[0143] Receive the seventh message sent by the first control device of the first cluster. The seventh message is used to request the establishment of a bearer for the first service with the second satellite.

[0144] Based on the seventh message, a bearer for the first service is established with the first control device, and an eighth message is sent to the first control device. The eighth message is used to instruct the second satellite to confirm the establishment of the bearer for the first service with the first control device.

[0145] In one possible implementation, the second message includes at least one of the following:

[0146] The first satellite identifier of the first satellite;

[0147] The second satellite's second satellite identifier;

[0148] Time difference information between the first and second satellites;

[0149] The first group identifier of the first cluster;

[0150] The first service beam identifier of the first cluster;

[0151] The first service time pattern corresponding to the first service beam identifier includes at least one of the first beam service period, the first subframe start time, and the first subframe duration.

[0152] First time;

[0153] The first active frame number corresponding to the first moment;

[0154] The first frequency point corresponding to the first service beam identifier;

[0155] First frequency domain configuration information for the first service;

[0156] First time-domain configuration information for the first service;

[0157] The first service beam identifier corresponds to the first cell identifier.

[0158] The bearer switching device for the first cluster service or the bearer switching device for the second cluster provided in this embodiment can execute the bearer switching method for the cluster service provided in the above method embodiment. Their implementation principle and technical effect are similar, and will not be described in detail here.

[0159] Figure 6 This is a schematic diagram of the satellite structure provided in an embodiment of this application. Figure 6 As shown, the satellite 60 provided in this embodiment includes at least one processor 601 and a memory 602. Optionally, the satellite 60 also includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus.

[0160] In a specific implementation, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to perform the above-described method.

[0161] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0162] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0163] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0164] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0165] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0166] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0167] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0168] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0169] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0170] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0171] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0172] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0173] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0174] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for switching bearers of cluster services, characterized in that, Applied to a first satellite, which is currently carrying the first service of the first cluster, the method includes: A first identifier is determined, which is used to indicate whether the first satellite needs to switch the bearer of the first service; When the first identifier indicates that the first satellite needs to switch the bearer of the first service, multiple second satellites are identified, and the second satellites are candidate satellites that can bear the first service. Send a first message to multiple second satellites, the first message being used to request the second satellites to carry the first service; Receive a second message sent by the second satellite, the second message being used to instruct the second satellite to confirm that it will carry the first service at a first time; Based on the second message, a third message is sent to the corresponding second satellite, the third message being used to instruct the first satellite to confirm that it will terminate the carrying of the first service at the first time. When the real-time time is the same as the first time, the first service is terminated.

2. The method according to claim 1, characterized in that, Before terminating the first service when the real-time time is the same as the first time, the method further includes: Based on the second message, the corresponding second satellite is identified as the target satellite, and a fourth message is sent to the first control device of the first cluster. The fourth message is used to request that the first service be switched to the target satellite at the first time. The system receives a fifth message sent by the first control device, the fifth message being used to instruct the first control device to confirm that the first service is switched to the target satellite at the first time. Based on the fifth message, a sixth message is sent to each cluster terminal device of the first cluster. The sixth message is used to notify the cluster terminal devices that they have established a communication connection with the target satellite at the first time.

3. The method according to any one of claims 1 or 2, characterized in that, Determining the first identifier includes: Obtain the fifth time, which is the end time of the first satellite carrying the first service; The sixth time is determined to be the difference between the fifth time and the real-time time; If the sixth time is less than or equal to the first threshold, then the first identifier is determined to indicate that the first satellite needs to switch the bearer of the first service; If the sixth time is greater than the first threshold, then the first identifier is determined to indicate that the first satellite does not need to switch the bearer of the first service.

4. The method according to claim 3, characterized in that, The first message includes at least one of the following: The first satellite identifier of the first satellite; The second satellite's second satellite identifier; The first group identifier of the first cluster; The first group identifier corresponds to the first group service configuration information, which includes at least one of the following: first group service priority information, signaling radio bearer bearer definition information, data radio bearer bearer definition information, and service quality information of the first service. The sixth time.

5. A method for switching bearers of cluster services, characterized in that, Applied to a second satellite, the method includes: Receive a first message sent by the first satellite, the first message being used to request the second satellite to carry the first service of the first cluster; Based on the first message, a second identifier is determined, which is used to indicate whether the second satellite can or cannot carry the first service; When the second identifier indicates that the second satellite can carry the first service, a second message is determined based on the first message. The second message is used to instruct the second satellite to confirm that it can carry the first service at the first time. Send a second message to the first satellite; Receive a third message sent by the first satellite, the third message being used to instruct the first satellite to confirm that it will terminate carrying the first service at the first time; When the real-time time equals the first time, the first service is carried out.

6. The method according to claim 5, characterized in that, Before carrying the first service when the real-time time equals the first time, the process further includes: The system receives a seventh message sent by the first control device of the first cluster, the seventh message being used to request the establishment of a bearer with the second satellite for the first service; Based on the seventh message, a bearer for the first service is established with the first control device, and an eighth message is sent to the first control device, the eighth message being used to instruct the second satellite to confirm the establishment of the bearer for the first service with the first control device.

7. The method according to any one of claims 5 or 6, characterized in that, The second message includes at least one of the following: The first satellite identifier of the first satellite; The second satellite's second satellite identifier; Time difference information between the first satellite and the second satellite; The first group identifier of the first cluster; The first service beam identifier of the first cluster; The first service time pattern corresponding to the first service beam identifier includes at least one of the first beam service period, the first subframe start time, and the first subframe duration. The first time; The first activation frame number corresponding to the first time; The first frequency point corresponding to the first service beam identifier; The first frequency domain configuration information of the first service; The first time-domain configuration information of the first service; The first cell identifier corresponding to the first service beam identifier.

8. A satellite, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-4, or the method as described in any one of claims 5-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-4, or to implement the method as described in any one of claims 5-7.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-4, or implements the method of any one of claims 5-7.

Images