Method and system for handling satellite transport optimization for reliable mobility

The method optimizes satellite network transport by dynamically adjusting TCP/UDP rates and buffer sizes based on real-time metrics, addressing throughput and latency issues in satellite networks.

WO2026235478A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096627
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-06
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Satellite networks experience interruptions, high round trip time (RTT), bandwidth constraints, and inefficient buffer management due to static TCP/UDP buffer sizes, leading to suboptimal throughput and data transfer delays, especially during satellite handovers.

Method used

A method and system for dynamically adjusting TCP/UDP rates, tuning TX/RX buffer sizes, and proactively modifying transport-layer control parameters based on real-time satellite metrics to optimize bandwidth-delay product and prevent buffer bloat, while minimizing data stalls during handovers.

Benefits of technology

Enhances throughput and stability in satellite networks by adapting to varying link conditions, reducing latency, and ensuring seamless data transmission without requiring satellite infrastructure changes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096627_12112026_PF_FP_ABST
    Figure KR2026096627_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method for controlling transport-layer communication in a satellite network performed by a UE is provided. The method includes determining that an active data session of the UE is ongoing over a satellite link. Further, the method includes monitoring at least one transport and network layer metrics during transmission of the active data session. Further, the method includes identifying a satellite link condition associated with the active data session based on the monitored transport and network layer metrics. Further, the method includes detecting a satellite handover event based on a variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change. Further, the method includes modifying at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event in response to the detecting of the satellite handover event.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND SYSTEM FOR HANDLING SATELLITE TRANSPORT OPTIMIZATION FOR RELIABLE MOBILITY

[0001] The disclosure relates to a satellite communication system and method, and more particularly to a method and system for handling a satellite transport optimization for a reliable mobility in a satellite network.

[0002] Currently, a satellite network involves small data transfers. Switching between satellites in the satellite network causes interruptions of up to 2 to 4 minutes (for example). Further, high round trip time (RTT) and bandwidth constraints results in slow data completion times.

[0003] Further, a transmission control protocol (TCP) congestion control misinterprets long delays as network congestion reducing send rates unnecessarily. Also, high RTT variations and packet reordering trigger unnecessary retransmissions waste bandwidth. Further, a satellite handover interrupts cause long pauses in data flow, and TCP's recovery mechanisms are too slow when there is not enough data transfer happening. Further, large RTTs lead to slow congestion window growth, so as to limit the amount of in-flight data. Further, high device buffers cause excessive queuing delays, increasing RTT. So, Buffers need dynamic tuning for optimal performance.

[0004] With the integration of non-terrestrial networks (NTN) such as geostationary earth orbit (GEO), low earth orbit (LEO), direct-to-cell (D2C), and 3rdgeneration partnership project (3GPP) standard NTN, mobile devices increasingly communicate over satellite links with vastly different latency and bandwidth characteristics. Following are core problem and key issues:

[0005] Core Problem: Static TCP / user datagram protocol (UDP) buffer sizes are sub-optimal for satellite communications.

[0006] Following are Key Issues:

[0007] a) Misaligned buffer sizes cause underutilization of bandwidth or excessive memory usage.

[0008] b) TCP throughput suffers in GEO if buffers are not tuned properly, due to high RTT.

[0009] c) UDP packet loss increases in D2C if buffers are too large for low-bandwidth links.

[0010] d) One-size-fits-all approach fails across different satellite types and changing link conditions.

[0011] FIG. 1 depicts I / O graphs for data transfer over satellites according to related art. During test conditions (e.g., DL test, satellite network, 20MB file download, and 5 iterations). The data transfer (both speedtest and http DL) did not happen continuously. Stall is seen even during periods when satellite handover is not happening.

[0012] FIG. 2 depicts a graph illustrating satellite handover durations and http behavior, according to prior art. During speedtest, for 5iterations, handovers are seen with Gap times 2secs, 13secs, 17secs, 35secs, 6secs, 9secs, 6secs, 10secs, 2secs, 10secs. In another trial, gap time of 12sec, 3sec, 16sec, 5sec, 50sec are observed. Single trial of 10MB http DL took very long time. Tester had to download multiple times as DL is not able to complete in one shot.

[0013] FIG. 3 depicts a graph illustrating satellite behavior for high RTT server according to related art. DATA transfer did not happen continuously. Stall is seen even during periods when satellite handover is not happening. http download transfer is breaking continuously due to high RTT.

[0014] FIG. 4 is a screen shot depicting an ICMP error stats according to related art. TTL Expired Count = 118 and Destination Unreachable Count = 91 were observed in a single test. Number of hops is reaching to 0 even though maximum TTL of 255 is set. TTL is a field in the IP header that acts as a "hop limit" for packets to prevent them from looping infinitely in a network.

[0015] The data shows 118 TTL Expired counts. This is highly unusual for terrestrial networks but common in satellite scenarios because:

[0016] a) Long-Path Routing: Satellite links often involve complex ground-station-to-satellite-to-gateway paths that standard terrestrial protocols don't expect.

[0017] b) Handover Looping: During a satellite transition (handover), a packet might get caught in a routing loop between the old and new satellite beams, rapidly exhausting its TTL.

[0018] c) The "Destination Unreachable" Link: Once TTL hits 0, the UE (smartphone) received the 91 Destination Unreachable errors, causing the app to think the server is dead when it's actually just a routing delay.

[0019] Impact on User Experience

[0020] a)Session Death: For the user, a TTL expiry means a "Data Stall." Even if the signal is "Full," the packet never reaches the server.

[0021] In standard terrestrial networks (TN), Android kernel parameters are often tuned for high-bandwidth fiber or 5G links.

[0022] a) Terrestrial Configuration (Static): Most modern smartphones use a static rmem_max and wmem_max of 16MB.

[0023] b)The Streaming Example: A high-definition video stream typically requires a consistent data rate of 5-15 Mbps.

[0024] c) The Bandwidth-Delay Product (BDP): The ideal buffer size is calculated as BDP = Bandwidth*RTT.

[0025] In 5G, with an RTT of 20ms, a 16MB buffer is massive and easily handles the flow. In GEO satellites, where RTT jumps to 600ms+, that same 16MB buffer may actually be too small to maintain high-speed throughput over such a long "pipe," causing data gaps.

[0026] Further, below are the key problem metrics (based on the existing methods):

[0027] a) Video Streaming Example: A standard HD stream (2 to 5 Mbps) on a D2C link with a static 16MB buffer creates a 64-second queue ((16*8) / 2 = 64s). This results in unplayable latency and app timeouts.

[0028] b) Bufferbloat in NTN: Keeping large buffers for low-bandwidth satellite links (1-10 Mbps) leads to increased RTT and significant throughput drops as the "pipe" becomes clogged with stale data.

[0029] c) Static Limitation: Modern devices lock rmem_max and wmem_max at 16MB, which is up to 300x larger than necessary for a typical LEO / D2C link, yet may be too small to saturate high-capacity GEO pipes without specialized tuning.

[0030] FIG. 5 is a flow chart illustrating a method for controlling transport-layer communication in a satellite network according to related art.

[0031] At S502, the method includes determining whether the network is a satellite network. If the network is not the satellite network, the method stops. If the network is the satellite network then, the current process does not have an adaptive behaviour for controlling the transport-layer communication in the satellite network at S504. Hence, at S506, the method results in poor application experience.

[0032] Thus, it is desired to address the above mentioned disadvantages or other shortcomings or at least provide a useful alternative.

[0033] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide an electronic device for changing a transmitting antenna and an operation method thereof.

[0034] Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments.

[0035] The disclosure provides a method and system for handling a satellite transport optimization for a reliable mobility in a satellite network.

[0036] An embodiment of the disclosure is to dynamically adjust TCP / UDP rates in real-time based on live satellite metrics (RTT and jitter). It prevents unnecessary congestion window shrinking to maintain stable throughput during variable link conditions.

[0037] An embodiment of the disclosure is to automatically tune TX / RX buffer sizes based on the specific non-terrestrial network type (e.g., GEO, LEO, D2C or the like). This optimizes throughput for high Bandwidth-Delay Products while preventing buffer bloat on low-bandwidth links.

[0038] An embodiment of the disclosure is to detect impending satellite transitions to proactively modify retransmission timers (RTO) and congestion window scaling. This minimizes data stalls and ensures session continuity during handovers.

[0039] An embodiment of the disclosure is to utilize physical-layer (PHY) signals from the modem to trigger transport-layer adjustments for satellite networks. It uses hardware-level data to adapt protocol behaviour before link degradation impacts the application

[0040] An embodiment of the disclosure is to disclose a non-intrusively monitoring and modifying transport-layer parameters using eBPF techniques within the smartphone kernel. This enables real-time optimization without requiring changes to satellite infrastructure or the core OS.

[0041] An embodiment of the disclosure is to identify and prioritize latency-sensitive packets (e.g., VoIP, streaming) over bulk data. It uses network-aware scheduling policies to improve perceived user experience under satellite constraints.

[0042] An embodiment of the disclosure is to leverage redundancy coding and selective retransmissions to minimize data loss. This mechanism recovers lost segments without full retransmission, reducing the impact of high packet loss rates.

[0043] An embodiment of the disclosure provides a method for controlling transport-layer communication in a satellite network performed by a UE. The method includes determining that an active data session of the UE is ongoing over a satellite link. Further, the method includes monitoring at least one transport and network layer metrics during transmission of the active data session. Further, the method includes identifying a satellite link condition associated with the active data session based on the monitored transport and network layer metrics. Further, the method includes detecting a satellite handover event based on a variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change. Further, the method includes modifying at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event in response to the detecting of the satellite handover event.

[0044] An embodiment of the disclosure provides a UE including a transport-layer communication controlling controller coupled with a processor and a memory. The transport-layer communication controlling controller is configured to determine that an active data session of the UE is ongoing over a satellite link. Further, the transport-layer communication controlling controller is configured to monitor at least one transport and network layer metrics comprising at least one RTT during transmission of the active data session. Further, the transport-layer communication controlling controller is configured to identify a satellite link condition associated with the active data session based on the monitored transport and network layer metrics. Further, the transport-layer communication controlling controller is configured to detect a satellite handover event based on a variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change. Further, the transport-layer communication controlling controller is configured to proactively modify at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event in response to the detecting of the satellite handover event.

[0045] In an embodiment, the method includes computing a bandwidth-delay product (BDP) based on measured bandwidth and the round-trip time, and adjusting at least one transmit or receive buffer size according to the computed BDP.

[0046] In an embodiment, the UE automatically tunes transmitting (TX) buffer sizes and receiving (RX) buffer sizes based on a detected NTN type to optimize the Bandwidth-Delay Product (BDP) and prevent bufferbloat.

[0047] In an embodiment, the method comprises dynamically managing Transmission Control Protocol (TCP) congestion control, User Datagram Protocol (UDP) sending rate control, buffer tuning, and packet scheduling, based on real-time satellite link condition, upon proactively modifying at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event.

[0048] In an embodiment, the at least one transport-layer control parameter comprises at least one of: a congestion window parameter and a retransmission timeout parameter.

[0049] In an embodiment, the satellite link condition is identified when the round-trip time exceeds a specified latency threshold characteristic of a non-terrestrial network.

[0050] In an embodiment, proactively modifying the at least one transport-layer control parameter comprises temporarily preventing reduction of a congestion window during the satellite handover event.

[0051] In an embodiment, proactively modifying the at least one transport-layer control parameter comprises implementing delay-based congestion control for a long-latency satellite link during the satellite handover event.

[0052] In an embodiment, proactively modifying the at least one transport-layer control parameter comprises increasing a retransmission timeout value in response to the detected satellite handover event.

[0053] In an embodiment, the at least one transport and network layer metrics comprising at least one of: round-trip time (RTT), jitter, packet reordering, and packet retransmissions.

[0054] In an embodiment, the at least one transport and network layer is modified by a use of an Extended Berkeley Packet Filter (eBPF) technique to modify a kernel-level networking parameter in real-time without modifying a core operating system, wherein the kernel-level networking parameter comprises a Time to Live (TTL) and packet prioritization.

[0055] In an embodiment, after monitoring the at least one transport and network layer metrics, where proactively modifying the at least one transport-layer control parameter of the active data session includes performing an extended Berkeley Packet Filter (eBPF) driven tuning of a kernel parameter upon identifying a non-terrestrial networks (NTN) profile and determining an application type, and applying a redundancy technique and selective recovery.

[0056] In an embodiment, the at least one transport and network layer metrics is monitored by utilizing a Physical Layer (PHY) signal from a modem to trigger transport and internet protocol (IP) layer adjustments, so as to allow the UE to anticipate link degradation before transport-layer packet loss occurs, wherein the PHY signal comprises at least one of: a Signal-to-Interference-Noise Ratio (SINR), a Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Block Error Rate (BLER).

[0057] In an embodiment, the at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event is proactively modified in response to the detecting of the satellite handover event.

[0058] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0059] The above and other aspects, features, and advantages certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0060] FIG. 1 depicts I / O graphs for data transfer over satellites according to related art.

[0061] FIG. 2 depicts a graph illustrating satellite handover durations and http behavior according to related art.

[0062] FIG. 3 depicts a graph illustrating satellite behavior for high RTT server according to related art.

[0063] FIG. 4 is a screen shot depicting an ICMP error stats according to related art.

[0064] FIG. 5 is a flow chart illustrating a method for controlling transport-layer communication in a satellite network according to related art.

[0065] FIG. 6 illustrates an overview of a UE for controlling transport-layer communication in a satellite network, according to the embodiment of the disclosure.

[0066] FIG. 7 illustrates an example UE framework for handling the satellite transport optimization for the reliable mobility in the satellite network, according to embodiments of the disclosure.

[0067] FIG. 8 illustrates a protocol stack flow while controlling the transport-layer communication in the satellite network, according to embodiments of the disclosure.

[0068] FIG. 9 is a flow chart illustrating a method for controlling transport-layer communication in the satellite network performed by the UE, according to embodiments of the disclosure.

[0069] FIG. 10 is an example flow chart illustrating a method for controlling transport-layer communication in the satellite network performed by the UE, according to embodiments of the disclosure.

[0070] FIG. 11 is example scenario in which results for Whatsapp (video calling) is depicted, according to the embodiment of the disclosure.

[0071] FIG. 12 is example scenario in which results for chrome (browsing) is depicted, according to the embodiment of the disclosure.

[0072] FIG. 13 is example scenario in which results for Facebook (social media) is depicted, according to the embodiment of the disclosure.

[0073] FIG. 14 is example scenario in which results for Instagram is depicted, according to the embodiment of the disclosure.

[0074] FIG. 15 is example scenario in which results for X is depicted, according to the embodiment of the disclosure.

[0075] FIG. 16 is example scenario in which results for Netflix [video] is depicted, according to the embodiment of the disclosure.

[0076] FIG. 17 is example scenario in which results for speedtest is depicted, according to the embodiment of the disclosure.

[0077] FIG. 18 is example scenario in which results for http downloads are depicted, according to the embodiment of the disclosure.

[0078] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures

[0079] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0080] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0081] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the disclosure using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0082] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0083] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the disclosure so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the disclosure so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0084] The accompanying drawings are used to help easily understand various technical features and it should be understood that the disclosure are not limited by the accompanying drawings. As such, the disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0085] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0086] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0087] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0088] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0089] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded individually or collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0090] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks (or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0091] As used in embodiments of the disclosure, a "~unit / module" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word "~unit / module" does not always have a meaning limited to software or hardware. The "~unit / module" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "~unit / module" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the "~unit / module" may be either combined into a smaller number of components and a "~unit / module," or divided into additional components and a "~unit / module." Moreover, the components and "~units / module" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "~unit / module" may include one or more processors.

[0092] The entirety of the one or more computer programs may be stored in a single memory device, or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0093] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0094] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0095] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0096] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0097] Hereinafter, the determination of priority between A and B in the disclosure may refer to various actions such as selecting the one having a higher priority based on a specified priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0098] Hereinafter, "A or B" as described in the disclosure may be understood as "A and / or B," which may include A, or B, or both A and B. In addition, "at least one of A, B, and C" as described in the disclosure may be understood to include A, or B, or C, or any combination of A, B, and C. In addition, "at least one of A, B, or C" as described in the disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0099] Furthermore, "A / B" as described in the disclosure may be understood as "A and / or B," which may include A, or B, or both A and B. Furthermore, "A, B" as described in the disclosure may be understood as "A and / or B," which may include A, or B, or both A and B. Furthermore, "A and B" as described in the disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0100] Furthermore, "if condition A and condition B are satisfied," as described in the disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0101] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0102] Furthermore, the terms "first ~", "second ~", etc., as described in the disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0103] Furthermore, even if "first ~" and "second ~" are described in the disclosure, it may be understood that element(s) referred to by "first ~" and "second ~" may be the same or different. For example, in case of element(s) being information, first information and second information may both be the same information, and, in some cases, are separate and different information.

[0104] In addition, the terms "if ~" and "in case that ~" as used in the disclosure or claims may be interpreted to include the meanings of "when (or upon) ~," "in response to ~," "based on ~," or "according to ~," and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the disclosure. If a method step (e.g., transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as "in case that ~" or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state "~" (e.g., a bit length is above X), and then perform the method step in response to said determination.

[0105] In addition, the term "not perform" as used in the disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0106] In addition, "transmitting a message including A and B" as described in the disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0107] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0108] In the specific embodiments of the disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0109] The drawings or flowcharts described below illustrate example methods that may be implemented according to the principles of the disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0110] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0111] The methods and apparatuses proposed in the embodiments of the disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0112] The methods and apparatuses proposed in the embodiments of the disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the disclosure may be modified and applied without significantly departing from the scope of the disclosure, as would be understood by those skilled in the art.

[0113] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0114] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from ETSI, where appropriate.

[0115] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0116] Furthermore, the base station of the disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0117] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an internet of things (IoT) device, or any other device / system capable of performing communication functions.

[0118] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0119] Furthermore, hereinafter, 5thgeneration (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the disclosure

[0120] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0121] Hereinafter, in the context of the disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0122] In addition, layer 1 (L1) signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0123] For example, the physical layer signaling (e.g., L1 signaling) may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0124] Hereinafter, the expression that information is configured by the BS, as used in the disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0125] Hereinafter, the operational principle of the disclosure will be described in detail with reference to the accompanying drawings.

[0126] Satellite networks introduce significant challenges for TCP / UDP-based communications due to high latency, frequent handover stalls, low throughput, and packet reordering. Traditional transport protocols, optimized for terrestrial networks, struggle to adapt to the dynamic nature of satellite links, leading to inefficient congestion control, excessive buffering (buffer bloat), and suboptimal data transfer rates. The proposed method introduces a UE based transport optimization framework (e.g., smartphone-based transport optimization framework or the like) that dynamically adjusts TCP / UDP behaviours for satellite environments. The proposed method includes adaptive congestion control, which modifies window sizes and retransmission strategies based on real-time network conditions, and dynamic buffer management to prevent excessive queuing delays. Additionally, handover-aware transport optimization minimizes stalls during satellite transitions, while latency-aware packet scheduling ensures efficient data transmission. An enhanced packet recovery mechanism further improves reliability in satellite-induced packet loss scenarios. By integrating these optimizations at the UE (smartphone) level, the proposed method significantly reduces latency, improves throughput, and ensures stable connectivity without requiring satellite-side modifications, making it an efficient and scalable solution for next-generation satellite communications.

[0127] The proposed method reduces lags, freezes, and call drops on satellite connections. The proposed method prevents stuck downloads and ensures smoother progress in weak coverage. The proposed method improves page load times, minimizes latency spikes and reordering for seamless real-time communication.

[0128] The proposed method introduces a UE-side adaptive transport optimization engine that dynamically adjusts congestion control, buffer sizes, and packet scheduling based on real-time satellite link metrics like RTT, loss, and handovers. It ensures stable connectivity, seamless transitions between satellites, and efficient data flow without requiring satellite infrastructure changes. The approach significantly enhances app and service reliability over satellite networks. The proposed method provides a satellite-aware, on-device transport control system that proactively manages TCP / UDP behaviour in response to live satellite link conditions. It includes handover-aware optimizations, dynamic buffer tuning, latency-sensitive packet handling, and enhanced recovery mechanisms. The proposed method enhances end-to-end reliability and efficiency of data transport in satellite networks by making the transport layer satellite-aware without requiring changes to satellite infrastructure. The proposed method addresses challenges like long RTT, frequent stalls, and packet reordering.

[0129] The proposed method improves application performance and user experience even in remote and underserved areas, increasing adoption and enabling premium satellite-backed connectivity offerings for the smartphones.

[0130] Accordingly, the embodiments herein provide a method and system for handling a satellite transport optimization for a reliable mobility. The proposed system and method may be used to dynamically adjusts TCP / UDP rates based on real-time satellite network conditions, mitigating high RTT variations and packet reordering. The proposed system and method may be used to automatically tune TX / RX buffer sizes to prevent bufferbloat and optimize throughput under varying satellite link conditions and based on type of NTN such as GEO, LEO, D2C, Standard NTN etc., The proposed system and method may be used to detect satellite transitions and proactively adjusts retransmission timers and congestion window scaling to reduce stalls during handovers. The proposed system and method may be used to prioritize critical data packets based on network latency estimates, ensuring efficient utilization of satellite bandwidth.

[0131] The embodiments herein achieve a method and system for handling a satellite transport optimization for a reliable mobility. Below are various satellite Types in NTN (for example).

[0132] a) Geostationary orbit (GEO) satellites

[0133] a. Altitude: Approximately 35,786 km above Earth's equator.

[0134] b. Characteristics: Orbit synchronously with Earth's rotation, appearing stationary over a fixed point.

[0135] c. Advantages: Provide continuous coverage over large areas with a single satellite.

[0136] d. Use Cases: Traditional satellite TV, weather monitoring, and some communication services.

[0137] e. Latency: Higher latency (~600 ms) due to distance, which can affect real-time applications.

[0138] b)Low earth orbit (LEO) Satellites

[0139] a. Altitude: Typically between 500 km and 2,000 km.

[0140] b. Characteristics: Move quickly across the sky, requiring constellations for continuous coverage.

[0141] c. Advantages: Lower latency (~20-40 ms), making them suitable for real-time communications.

[0142] d. Use Cases: Broadband internet services (e.g., Starlink), Earth observation, and emerging direct-to-device communications.

[0143] c) Direct-to-cell (D2C) satellites

[0144] a. Definition: Satellites that enable direct communication with standard mobile devices without the need for ground-based infrastructure.

[0145] b. Characteristics: Often utilize LEO constellations to provide coverage.

[0146] c. Advantages: Expand connectivity to remote or underserved areas, useful for emergency services and IoT applications.

[0147] d. Use Cases: Text messaging, emergency alerts, and basic data services directly to smartphones.

[0148] The proposed method relates to satellite communication optimizations, specifically improving TCP and UDP transport performance in high-latency, low-bandwidth satellite networks. It focuses on reducing transmission stalls, optimizing congestion control, and dynamically tuning buffers to enhance end-to-end data efficiency.

[0149] The proposed method optimizes TCP / UDP transport in satellite networks by minimizing handover stalls, implementing adaptive congestion control to handle high RTT and packet reordering, dynamically tuning TX / RX buffers to prevent buffer bloat, and modifying transport protocols to enhance data transfer efficiency under satellite constraints.

[0150] The proposed method has the following technical advantages:

[0151] a) Adaptive congestion control for satellites: Dynamically modifies congestion window and retransmission policies based on real-time satellite link conditions.

[0152] b) Dynamic buffer management: Automatically tunes TX / RX buffers to prevent bufferbloat and maintain optimal throughput in fluctuating satellite environments.

[0153] c) Handover-aware transport optimization: Proactively adjusts TCP parameters to minimize stalls and packet loss during satellite transitions.

[0154] d) Latency-aware packet scheduling: Prioritizes packets based on real-time network conditions to optimize performance.

[0155] e) Enhanced packet recovery mechanism: Uses selective retransmissions and redundancy strategies tailored for satellite-induced packet loss.

[0156] f) Adaptive congestion control mechanism: A method that dynamically adjusts TCP / UDP transmission rates based on real-time satellite link metrics such as RTT, jitter, and packet loss

[0157] g) Satellite-type-aware congestion adaptation: A system that modifies congestion control behaviour based on the type of satellite (e.g., LEO, GEO, D2C, NTN), accounting for their unique delay and bandwidth characteristics.

[0158] h) Dual-path congestion feedback fusion: A mechanism that integrates feedback from satellite and terrestrial fallback paths to optimize transport behavior and avoid overcompensation.

[0159] i) Dynamic buffer management system: A mechanism that tunes TX and RX socket buffer sizes (tcp_rmem, tcp_wmem, rmem_max, etc.) dynamically based on satellite link performance.

[0160] j) Buffer tuning based on satellite handover events: A method for shrinking or expanding buffers upon detection of a handover event to avoid overflows or starvation during topology shifts.

[0161] k) Transport-layer buffer optimization using ML: A system that leverages ML models trained on satellite traffic patterns to predict optimal buffer settings.

[0162] l) Handover-aware transport optimization: A method that proactively modifies congestion window, retransmission timeout (RTO), and duplicate ACK thresholds during satellite-to-satellite handover events.

[0163] m) Latency-aware packet scheduling algorithm: A scheduler that reorders or prioritizes packets based on network latency predictions to maintain throughput while minimizing perceived delay.

[0164] n) RTT-aware RTO tuning mechanism: A method that adjusts RTO values dynamically based on moving average RTTs specifically tailored for satellite latency behaviour.

[0165] o) Enhanced packet recovery mechanism: A transport-layer recovery strategy that uses redundancy or forward error correction selectively based on link health estimation.

[0166] p) Selective acknowledgment optimization for satellite links: A modified SACK strategy to handle long RTTs and packet reorderings in satellite environments.

[0167] q) Early loss detection in High-BDP paths: A method that identifies losses using heuristics adapted for large bandwidth-delay product paths common in satellite links.

[0168] r) Architecture & system-level enhancements (satellite-aware transport stack): A mobile-side or UE-side stack enhancement that includes modules for satellite link classification, latency estimation, and buffer control.

[0169] s) Transport parameter profile switching: A system that switches between specified profiles (e.g., for LEO, GEO, and terrestrial) for TCP / UDP parameters without rebooting or resetting the network stack.

[0170] t) Kernel parameter manager for satellite links: An on-device daemon or APK that modifies / proc / sys / net / ipv4 / parameters dynamically based on real-time satellite link feedback.

[0171] u) Machine learning-based transport parameter Prediction: A method using ML to predict optimal values for congestion control, retransmission timeout, and buffer size based on historical satellite link performance.

[0172] v) Adaptive transport strategy selection: A mechanism that dynamically selects among multiple transport strategies (e.g., BBR, Cubic / BIC, PRAGUE) depending on satellite network conditions.

[0173] w) Reinforcement learning for transport resilience: A system that uses reinforcement learning to maximize throughput and minimize retransmissions over time in dynamic satellite environments.

[0174] The proposed system and method may be used to leverages redundancy and selective retransmissions to minimize data loss and improve reliability in satellite communication. The proposed method reduces satellite handover delays. The proposed method minimizes packet loss and reordering. The proposed method dynamically adjusts buffer sizes. The proposed method prevents bufferbloat in satellite links. The proposed method optimizes TCP / UDP congestion control. The proposed method enhances data transfer efficiency. The proposed method improves throughput in high-latency networks. The proposed method ensures seamless satellite communication.

[0175] In an embodiment, the proposed system and method may be used to leverage redundancy and selective retransmissions to minimize data loss and improve reliability in satellite communication. the proposed system and method may be used to reduce page load failures, video buffering, and app timeouts on smartphones connected to satellite networks, ensuring smooth connectivity even in remote areas where traditional mobile networks fail.

[0176] Referring now to the drawings, and more particularly to FIGS. 6 to FIG. 18, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0177] FIG. 6 illustrates an overview of a UE (or terminal) 600 for controlling transport-layer communication in the satellite network, according to the embodiment of the disclosure.

[0178] Referring to FIG. 6, the UE (or terminal) 600 is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an internet of things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0179] The UE 600 may be, for example, but not limited to a smart phone, a gaming device, a smart watch, a laptop, a desktop computer, a notebook, a smart TV, a tablet, an immersive device, a virtual reality (VR) device, an augmented reality (AR) device, a mixed reality (MR) device, a head-mounted display (HMD), a visual see-through (VST) device, a smart ring, a smart band, a foldable phone, or the like.

[0180] The UE 600 may include at least one processor (hereinafter, referred to as simply "processor") 602, at least one transceiver (hereinafter, referred to as simply "transceiver") 604, at least one memory (hereinafter, referred to as simply "memory") 606, a transport-layer communication controlling controller 608 and a data driven controller 610. According to at least one or a combination of methods corresponding to the embodiments described in the disclosure, the processor 602, the transceiver 604, the memory 606, the transport-layer communication controlling controller 608, and the data driven controller 610 of the UE 600 may operate. However, components of the UE 600 are not limited to the example components illustrated in FIG. 6 and FIG. 7. In an embodiment, the UE 600 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, any combination of the processor 602, the transceiver 604, the memory 606, the transport-layer communication controlling controller 608, and the data driven controller 610 may be integrated in the form of one component. In an embodiment, the processor 602 may include the transport-layer communication controlling controller 608 and the data driven controller 610.

[0181] The transport-layer communication controlling controller 608 determines that an active data session of the UE 600 is ongoing over a satellite link. Further, the transport-layer communication controlling controller 608 monitors at least one transport and network layer metrics including at least one RTT during transmission of the active data session. The at least one transport and network layer metrics includes at least one of: round-trip time (RTT), jitter, packet reordering, and packet retransmissions. In an embodiment, the at least one transport and network layer metrics is monitored by utilizing a physical layer (PHY) signal from a modem to trigger transport and internet protocol (IP) layer adjustments, so as to allow the UE 600 to anticipate link degradation before transport-layer packet loss occurs, where the PHY signal includes at least one of: a SINR, a RSRP, a RSRQ, and BLER. The at least one transport and network layer is modified by a use of an extended berkeley packet filter (eBPF) technique to modify a kernel-level networking parameter in real-time without modifying a core operating system, where the kernel-level networking parameter comprises a time to live (TTL) and packet prioritization.

[0182] Further, the transport-layer communication controlling controller 608 identifies a satellite link condition associated with the active data session based on the monitored transport and network layer metrics. In an embodiment, the satellite link condition is identified when the round-trip time exceeds a specified latency threshold characteristic of a non-terrestrial network. Further, the transport-layer communication controlling controller 608 detects a satellite handover event based on a variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change.

[0183] Further, the transport-layer communication controlling controller 608 proactively modifies at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event in response to the detecting of the satellite handover event. The at least one transport-layer control parameter may be, for example, but not limited to a congestion window parameter and a retransmission timeout parameter. In an embodiment, proactively modify the at least one transport-layer control parameter includes temporarily prevent reduction of a congestion window during the satellite handover event. In another embodiment, proactively modify the at least one transport-layer control parameter includes implement delay-based congestion control for a long-latency satellite link during the satellite handover event. In another embodiment,proactively modify the at least one transport-layer control parameter includes increasing a retransmission timeout value in response to the detected satellite handover event.

[0184] After monitoring the at least one transport and network layer metrics, where proactively modifying the at least one transport-layer control parameter of the active data session includes performing an extended berkeley packet filter (eBPF) driven tuning of a kernel parameter upon identifying a non-terrestrial networks (NTN) profile and determining an application type, and applying a redundancy technique and selective recovery.

[0185] Further, the transport-layer communication controlling controller 608 computes a bandwidth-delay product (BDP) based on measured bandwidth and the round-trip time, and adjusts the transmit or receive buffer size according to the computed BDP. Further, the transport-layer communication controlling controller 608 automatically tunes transmitting (TX) buffer sizes and receives (RX) buffer sizes based on a detected NTN type to optimize the bandwidth-delay product (BDP) and prevent bufferbloat.

[0186] Further, the transport-layer communication controlling controller 608 dynamically manages TCP congestion control, UDP sending rate control, buffer tuning, and packet scheduling, based on real-time satellite link condition, upon proactively modifying at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event.

[0187] The transceiver 604 may be a communication circuit or communication circuitry that enables the UE 600 to perform wireless communication with a node or an entity of the network. For example, the transceiver 604 may enable the UE 600 to transmit or receive a signal to or from a BS or satellite through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 604 may support at least one of various cellular communication technologies including 3rd generation (3G), 4thgeneration (4G), long term evolution (LTE), 5th generation (5G) NR, 6thgeneration (6G), satellite and various cellular wireless communication technologies supported by the transceiver 604 may include all subsequent generations of evolved wireless communications.

[0188] According to an embodiment, the transceiver 604 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 604 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 604 may output a signal received through a wireless channel to the processor 602 and may transmit, through a wireless channel, a signal output from the processor 602.

[0189] According to an embodiment, the UE 600 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 600 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 600 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 600 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0190] The processor 602 may control general operations of the UE 600 according to embodiments of the disclosure. The processor 602 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 602 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 606, individually, collectively or in any combination thereof. Further, the processor 602 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0191] The processor 602 may be electrically, operatively, and / or communicatively coupled to the transceiver 604 to control the transceiver 604. The processor 602 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 602 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 602 may be included in one chip and the other part of the processor 602 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 604 or the memory 606.

[0192] The processor 602 may perform or control or cause an operation of the UE 600 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 602 may control operations of the UE 600 for processing a downlink signal received from the BS or satellite or generating and transmitting an uplink signal to the BS or satellite. To this end, the processor 602 may execute a computer program, codes, or instructions stored in the memory 606, so as to control other components of the UE 600 to enable execution of various operations.

[0193] The memory 606 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 606 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0194] The memory 606 may be electrically, operatively, and / or communicatively coupled to the processor 602 and may be accessed by the processor 602. The memory 606 may store a computer program, codes, or instructions executable by the processor 602. According to an embodiment, a computer program, codes, or instructions executable by the processor 602 may be either stored in a single memory device or separated and stored in a distributed manner in two or more memory devices. By executing the instructions stored in the memory 606, the processor 602 may perform various functions according to an embodiment of the disclosure.

[0195] According to an embodiment of the disclosure, operations of the UE 600 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 606 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0196] The proposed method may be used to enhance the performance of applications in satellite environment. Consider the use case, for video calling (e.g., WhatsApp, Google Meet or the like), in the existing method, high RTT and packet reordering cause video / audio to freeze or distort. Satellite handovers (e.g., LEO transitions) lead to 30-120 sec stalls or call drops. Based on the proposed method, handover-aware transport quickly adapts TCP / UDP retransmissions and congestion window to maintain continuity. latency-aware packet scheduling prioritizes media frames to prevent lag and freezing.

[0197] Consider another use cases, for file downloads (e.g., Browser, drive, email attachments or the like), in the existing method, TCP stalls frequently due to static buffers and high bandwidth delay product (BDP) mismatch. Poor congestion control causes slow download speeds, frequent timeouts. Based on the proposed method, dynamic buffer management tunes TCP window / buffer sizes to match satellite BDP. Adaptive congestion control improves throughput even under high delay and jitter.

[0198] For social media scrolling (e.g., Instagram, Twitter or the like), in the existing method, page loads freeze midway due to TCP retransmission issues and small images and videos fail to load under poor satellite signal conditions. The proposed method provides selective retransmission and packet recovery fix out-of-order and dropped segments. The adaptive queuing ensures smooth, progressive content loading.

[0199] For streaming (e.g., Netflix, Prime video etc.,), in the existing method, streaming progress stalls randomly due to network handover delays. High packet loss leads to retries, draining battery and wasting bandwidth. Based on the proposed method, theproactive handover handling ensures steady TCP session across satellite transitions. Efficient packet recovery prevents re-downloads, saving time and data.

[0200] The proposed method has the following advantages:

[0201] a) Predictive tuning: Using signals from the telephony module (e.g., isNonTerrestrialNetwork), the proposed method identifies the imminent handover before the current link breaks.

[0202] b) Session "Freezing" vs. "Dropping": the proposed method proactively adjusts the RTO and scales the congestion window (CWND) to keep the session alive in a "waiting" state rather than letting it time out.

[0203] c) Instant resumption: The moment the new beam is connected, the proposed method injects the new satellite profile into the kernel via eBPF, allowing the video call to resume instantly without the typical "reconnecting" delay.

[0204] FIG. 7 illustrates an example UE framework for handling the satellite transport optimization for the reliable mobility in the satellite network, according to embodiments of the disclosure.

[0205] Referring to FIG. 7, the proposed method and system is implemented inside the smartphone (UE), optimizing TCP / UDP transport for satellite communication. It consists of multiple modules that interact with the kernel and modem to enhance data transfer efficiency in satellite network. The UE 600 includes various modules such as satellite-aware transport controller (SATC) 612, latency-aware packet scheduler (LAPS) 614, dynamic buffer management system (DBMS) 616, handover prediction & adaptation (HPA) 618, and smart packet recovery engine (SPRE) 620.

[0206] The SATC 612 manages congestion control, buffer tuning, and retransmissions dynamically. The DBMS 616 adjusts TX / RX buffers in real time to prevent bufferbloat. The HPA 618 detects satellite handover events and modifies TCP parameters proactively. The LAPS 614 prioritizes packets based on latency sensitivity and network conditions. The SPRE 620 enhances reliability using selective retransmissions and redundancy techniques.

[0207] The SATC 612, the DBMS 616, the HPA 618, the LAPS 614, and the SPRE modules 620 operates at frameworks. The module 612-620 receive the events from the CP (via SIPC), Kernel(via netd, eBPF programs) and tunes kernel TCP / IP parameters via netd.

[0208] The SATC 612 monitors RTT variations, packet loss, and throughput in real time. The SATC 612 dynamically adjusts congestion window (CWND) and retransmission timers based on satellite link characteristics via netd.

[0209] The SATC 612 detects high RTT and satellite-induced jitter. Further, the SATC 612 prevents unnecessary congestion window shrinking, so as to allow the stable throughput. Further, the SATC 612 implements delay-based congestion control for long-latency satellite links. Further, the SATC 612 reduces retransmissions caused by packet reordering due to satellite routing changes.

[0210] The DBMS 616 continuously tunes TX / RX buffer sizes based on real-time network conditions and based on satellite network type such as GEO, LEO, D2C and Standard NTN. The DBMS 616 prevents bufferbloat, so as to reduce the excessive queuing delays. The DBMS 616 ensures efficient utilization of satellite bandwidth while maintaining optimal data flow.

[0211] The HPA 618 detects satellite handover events before connection loss. The HPA 618 proactively adjusts TCP retransmission timeout (RTO) and congestion window (CWND). The HPA 618 ensures seamless data transfer during satellite transitions.

[0212] The LAPS 614 identifies latency-sensitive verus bulk data packets. The LAPS 614 prioritizes important traffic (e.g., VoIP, streaming) to reduce perceived latency. Further, the LAPS 614 uses network-aware scheduling policies to improve end-user experience.

[0213] The SPRE 620 implements selective retransmission to avoid unnecessary duplicate packets. Further, the SPRE 620 uses redundancy coding techniques to recover lost packets without full retransmission. Further, the SPRE 620 reduces the impact of high packet loss rates in satellite networks.

[0214] In an example for NTN signalling and profile detection, the UE 600 registers a listener for onDataNetworkConnected through the telephony manager. Upon a connection event, the engine queries the isNonTerrestrialNetwork() API. If true, the engine pulls specific frequency bands (e.g., n255 / n256) or Operator IDs (PLMN) to differentiate between GEO, LEO, or D2C. This "Satellite Profile" is then pushed via SIPC / Netlink to the KS (Kernel Space) to update eBPF maps.

[0215] In an example for NTN signalling architecture, the UE 600 utilizes the Android TelephonyCallback interface to monitor state changes. Because isNonTerrestrialNetwork() is a getter and not a push notification, the UE 600 hooks into onDataNetworkConnected to ensure zero-day optimization. Modem (CP) broadcasts link status via the radio interface layer (RIL). The telephony module: Updates the ServiceState. The engine polls the state, identifies the orbit (GEO / LEO), and triggers the SATC / DBMS modules

[0216] The proposed method reduces satellite handover delays. The proposed method minimizes packet loss and reordering. The proposed method dynamically adjusts buffer sizes. The proposed method prevents bufferbloat in satellite links. The proposed method optimizes TCP / UDP congestion control. The proposed method enhances data transfer efficiency. The proposed method improves throughput in high-latency networks. The proposed method ensures seamless satellite communication.

[0217] FIG. 8 depicts an example protocol stack flow while controlling transport-layer communication in the satellite network performed by the UE, according to the embodiment of the disclosure.

[0218] Referring to FIG. 8, the architectural overview is shown. The proposed system is a cross-layer optimization framework integrated directly into the linux networking stack of the UE (600). Unlike traditional terrestrial networking, which operates on static parameters, the proposed method acts as an intelligent orchestration layer between the application layer and the non-terrestrial network (NTN). By utilizing  extended berkeley packet filter (eBPF) hooks, the proposed method may be used to perform the real-time kernel-level parameter modifications without requiring changes to the core Android / Linux OS. This allows the engine to intercept data streams from applications (e.g., WhatsApp, Netflix or the like) and dynamically reconfigure the transport (TCP / UDP) and IP layers to match the unique physical constraints of satellite links, such as extreme RTT and frequent LEO handovers.

[0219] FIG. 9 is a flow chart illustrating a method for controlling transport-layer communication in the satellite network performed by the UE according to the embodiment of the disclosure. The operations (S902-S910) are handled by the transport-layer communication controlling controller (610).

[0220] Referring to FIG. 9, at S902, the method includes determining that the active data session of the UE 600 is ongoing over the satellite link. At S904, the method includes monitoring the at least one transport and network layer metrics during transmission of the active data session. At S906, the method includes identifying the satellite link condition associated with the active data session based on the monitored transport and network layer metrics.

[0221] At S908, the method includes detecting the satellite handover event based on the variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change. At S910, the method includes modifying at least one transport-layer control parameter of the active data session prior to completion of the satellite handover event in response to the detecting of the satellite handover event.

[0222] FIG. 10 is an example flow chart illustrating a method for controlling transport-layer communication in the satellite network performed by the UE according to the embodiment of the disclosure. The operations (S1002-S1024) are handled by the transport-layer communication controlling controller (610).

[0223] Referring to FIG. 10, at S1002, the method includes determines whether the network is the satellite network. If the network is the satellite network then, at S1004, the method includes receiving the real time metrics (e.g., RTT, reordering, retransmissions, Jitter etc.,) from the modem. At S1006, the method includes monitoring the real time metrics. At S1008, the method includes identifying the NTN profile such as GEO / LEO / D2C. At S1010, the method includes checking the application type (e.g., video streaming, browsing, video calling, download etc.). At S1012, the eBPF driven tuns of the kernel parameters. At S1014, the method includes applying the redundancy coding and selective recovery.

[0224] At S1016, the method includes determining whether the handover is detected. If the handover is detected then, at S1018, the method includes pro-actively adjusting the RTO and scaling the CWND. At S1020, the method includes providing the enhanced performance and stability. At S1022, the method includes determining whether the connection is terminated. If the connection is terminated then, the method stops the operation. If the connection is not terminated then, at S1024, the method includes identifying the NTN profile such as GEO / LEO / D2C.

[0225] The proposed method may be used to reduce the satellite handover delays. The proposed method may be used to minimize the packet loss and reordering. The proposed method may be used to dynamically adjust buffer sizes. The proposed method may be used to prevent bufferbloat in satellite links. The proposed method may be used to optimize the TCP / UDP congestion control. The proposed method may be used to enhance the data transfer efficiency. The proposed method may be used to improve the throughput in high-latency networks. The proposed method may be used to ensure the seamless satellite communication. By adjusting the retransmission timeout (RTO) and congestion window (CWND) before the switch (handover), the proposed method ensures the data session "pauses and resumes" instantly rather than "crashing and reconnecting." The physical handover timing is unchanged, but the protocol-level stall is virtually eliminated.

[0226] FIG. 11 is example scenario in which results for Whatsapp (video calling) is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as noticeable improvement in call stability, reduced lag and buffering during live conversations, and lower retransmissions and fewer out-of-order packets etc., observed.

[0227] FIG. 12 is example scenario in which results for chrome (browsing) is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as web pages loaded more consistently without visible stalls, lower duplicate ACKs and retransmissions helped reducing perceived delays, and quicker page rendering that is noticed under variable network conditions.

[0228] FIG. 13 is example scenario in which results for Facebook (social media) is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as feeds loaded smoothly with minimal visible delays, lower retransmissions, packet losses and better congestion handling observed, and scrolling and media playback that was more responsive.

[0229] FIG. 14 is example scenario in which results for Instagram is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as stories and reels loaded with reduced buffering, image-heavy content shown faster loading due to fewer lost segments, and noticeable improvement in responsiveness while browsing.

[0230] FIG. 15 is example scenario in which results for X is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as tweets and media loaded quickly even on poor links, reduced packet reordering helped stabilize feed updates, and delays while uploading media are minimized.

[0231] FIG. 16 is example scenario in which results for Netflix [video] is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as video playback was smoother with fewer resolution drops, initial buffering is reduced, and rebuffering events were minimal, and Kernel param tuning ensured better bandwidth utilization.

[0232] FIG. 17 is example scenario in which results for speedtest is depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as speed test results are more stable, less fluctuation in throughput and better uplink / downlink consistency, and improved TCP efficiency due to fewer duplicate ACKs.

[0233] FIG. 18 is example scenario in which results for http downloads are depicted, according to the embodiment of the disclosure. The proposed method provides various advantages such as file downloads complete faster with fewer stalls, fewer fast retransmits and lower packet loss enhance reliability, and overall improvement in download stability and speed.

[0234] In overall, slight improvement in TTL expired count is noticed with the proposed method count being 118 versus without proposed method 145. Newly tuned buffer is fully utilized as shown in window graph. 1.25MB receive window is reached.

[0235] Based on experimental results, the proposed method may quantify the improvement with high confidence:

[0236] a) Stall duration: The 30-120 second "stall" is reduced to the bare minimum physical switching time of the modem (often <2-5 seconds).

[0237] b) Data reliability: Retransmissions in apps like WhatsApp dropped from 1,312 to just 12 in trials.

[0238] c) Call continuity: While the video might momentarily "freeze" or drop to a lower resolution, the audio call remains intact, and the video recovers seamlessly once the handover completes.

[0239] The proposed method ensures a smooth experience by prioritizing the latency-aware packet scheduler (LAPS) module:

[0240] a) Traffic prioritization: It identifies VoIP / video packets and prioritizes them over background data.

[0241] b) Throughput stability: By tuning kernel buffers (e.g., tcp_rmem), the proposed method ensures that even a 1-2 Mbps satellite link is fully utilized to maintain the bare minimum bitrate required for a compressed video stream.

[0242] In other words, based on the proposed methods, please find below results in the view of various applications:

[0243] Results (Whatsapp)

[0244]

[0245] Results(chrome)

[0246]

[0247] Results(facebook)

[0248]

[0249] Results(instagram)

[0250]

[0251] Results(netflix)

[0252]

[0253] Results(x)

[0254]

[0255] Results(Youtube)

[0256]

[0257] The various actions in method may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in figures may be omitted.

[0258] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in figures can be at least one of a hardware device, or a combination of hardware device and software module.

[0259] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0260] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform a method of the disclosure.

[0261] Any such software may be stored in the form of volatile or non-volatile storage, such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory, such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium, such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments provide a program comprising code for implementing apparatus or a method of any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0262] While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1.A method for controlling transport-layer communication in a satellite network performed by a user equipment (UE), comprising:identifying (S902) that an active data session of the UE is ongoing over a satellite link;monitoring (S904) at least one transport and network layer metrics comprising at least one round-trip time (RTT) during transmission of the active data session;identifying (S906) a satellite link condition associated with the active data session based on the monitored transport and network layer metrics;detecting (S908) a satellite handover event based on a variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change; andmodifying (S910) at least one transport-layer control parameter of the active data session in response to the detecting of the satellite handover event.2.The method of claim 1, further comprising:identifying a bandwidth-delay product (BDP) based on a bandwidth and the RTT; andadjusting at least one of transmitting (TX) buffer sizes or receiving (RX) buffer sizes based on the BDP.3.The method of claim 2, wherein transmitting (TX) buffer sizes and receiving (RX) buffer sizes are tuned based on a non-terrestrial network ( NTN) type to optimize the BDP and a prevent bufferbloat.4.The method of claim 1, further comprising:managing transmission control protocol (TCP) congestion control, user datagram protocol (UDP) sending rate control, buffer tuning, and packet scheduling, based on real-time satellite link condition, upon modifying the at least one transport-layer control parameter of the active data session prior to the completion of the satellite handover event.5.The method of claim 1, wherein the at least one transport-layer control parameter comprises at least one of: a congestion window parameter or a retransmission timeout parameter.6.The method of claim 1, wherein the RTT exceeds a latency threshold characteristic of a non-terrestrial network (NTN).7.The method of claim 1, wherein the modifying the at least one transport-layer control parameter comprises temporarily preventing reduction of a congestion window during the satellite handover event.8.The method of claim 1, wherein the modifying the at least one transport-layer control parameter comprises implementing delay-based congestion control for a long-latency satellite link during the satellite handover event.9.The method of claim 1, wherein the modifying the at least one transport-layer control parameter comprises increasing a retransmission timeout value in response to the detected satellite handover event.10.The method of claim 1, wherein the at least one transport and network layer metrics further comprises at least one of: a jitter, a packet reordering, or packet retransmissions.11.The method of claim 1, wherein the at least one transport and network layer is modified by a use of an extended berkeley packet filter (eBPF) technique to modify a kernel-level networking parameter in real-time, andwherein the kernel-level networking parameter comprises a time to live (TTL) and a packet prioritization.12.The method of claim 1, wherein the modifying the at least one transport-layer control parameter of the active data session comprises:performing an extended berkeley packet filter (eBPF) driven tuning of a kernel parameter upon identifying a non-terrestrial networks (NTN) profile and determining an application type; andapplying a redundancy technique and a selective recovery.13.The method of claim 1, wherein the at least one transport and network layer metrics is monitored by:utilizing a physical layer (PHY) signal from a modem to trigger transport and internet protocol (IP) layer adjustments, so as to allow the UE to anticipate link degradation before transport-layer packet loss occurs, wherein the PHY signal comprises at least one of: a signal-to-interference-noise ratio (SINR), a reference signal received power (RSRP), reference signal received quality (RSRQ), and block error rate (BLER).14.The method of claim 1, wherein the at least one transport-layer control parameter of the active data session is modified prior to completion of the satellite handover event.15.A UE (600), comprising:memory (606) storing instructions; andat least one processor (602) communicatively coupled to the memory,wherein the instructions that, when executed by the at least one processor individually or collectively, cause the UE (600) to:identify that an active data session of the UE (600) is ongoing over a satellite link;monitor at least one transport and network layer metrics comprising at least one round-trip time (RTT) during transmission of the active data session;identify a satellite link condition associated with the active data session based on the monitored transport and network layer metrics;detect a satellite handover event based on a variation in the monitored transport and network layer metrics indicative of satellite beam transition or satellite routing change; andmodify at least one transport-layer control parameter of the active data session in response to the detecting of the satellite handover event.