Satellite GEO-LEO superposition system for efficient mobile communication

Abstract

This specification describes systems, methods, and apparatus for providing a user equipment (UE) with means to communicate via a non-terrestrial network connection. In a lower quality connected state (206), the UE communicates data with the core network via the GEO satellite. The UE or the core network may request a higher quality connection. In response to such a request, the GEO satellite transmits a configuration to the UE for a further network entity, such as an LEO satellite. Upon receiving the configuration, the UE transitions (210) to a higher quality session and enters a higher quality connected state (212) during which the UE communicates data signals with the core network via the further network entity. After completion of the higher quality session, the UE may transition (214) back to a lower quality connected state (206) and continue to communicate data with the core network via the GEO satellite.

Description

Background Technology

[0001] User equipment (UE) is increasingly supporting the ability to connect to core networks (e.g., 5G core networks) via non-terrestrial networks (NTNs). Such NTNs typically include geostationary orbit (GEO) satellites that maintain a fixed position relative to the Earth's surface and low Earth orbit (LEO) satellites whose orbits move relative to the Earth's surface. GEO satellites operate at altitudes of approximately 36,000 km, while LEO satellites typically operate at altitudes below 2,000 km. Summary of the Invention

[0002] In a first aspect, this disclosure provides a method performed by a user equipment (UE), the method comprising: establishing a data connection between the UE and a geostationary orbit (GEO) satellite; transmitting a first set of signals between the UE and a network via the GEO satellite, wherein the transmission of the first set of signals between the UE and the network via the GEO satellite is at a first quality value; requesting, by the UE, configuration from the GEO satellite for connection to a further network entity; receiving, by the UE, configuration for connection to the further network entity from the GEO satellite; establishing a further data connection between the UE and the further network entity based on the received configuration, while maintaining the connection between the UE and the GEO satellite; and transmitting a second set of signals between the UE and the network via the further network entity, wherein the transmission of the second set of signals between the UE and the network via the further network entity is at a second quality value, wherein the second quality value is higher than the first quality value.

[0003] In a further aspect, this disclosure provides a satellite-based method comprising: maintaining the satellite in a geosynchronous orbit; establishing a data connection between a ground user equipment and the satellite; transmitting a first set of signals between the ground user equipment and a network via the satellite, wherein the transmission of the first set of signals between the ground user equipment and the network via the satellite is at a first quality value; receiving a request from the network or the ground user equipment for a higher quality connection; in response to receiving the request, transmitting to the ground user equipment a configuration for a further network entity supporting a connection with a second quality value, wherein the second quality value is higher than the first quality value; and maintaining, at least partially, the connection between the satellite and the ground user equipment when the ground user equipment connects to the further network entity.

[0004] Further aspects of this disclosure provide systems, apparatus, and computer-readable media for implementing any of the methods described herein.

[0005] The systems, methods, and apparatus described herein enable one or more of the following advantages. By default connecting to the NTN network via GEO satellite and only using further radio access network (RAN) entities such as LEO satellites when requesting higher quality data transmission, the UE can significantly reduce its power usage when connected via NTN. Attached Figure Description

[0006] Figure 1 An overview of a network system with UE, GEO satellites and one or more LEO satellites is shown;

[0007] Figure 2 It shows Figure 1 The state diagram of the UE in the image;

[0008] Figure 3 It shows Figure 1 Network diagram of the network system in the image;

[0009] Figure 4 A high-level signaling diagram is shown for establishing a connection between the UE and the core network via GEO satellite;

[0010] Figure 5A An overview of carrier aggregation is shown;

[0011] Figure 5B An overview of the dual-connectivity is shown;

[0012] Figure 6 The signaling diagram for carrier aggregation (CA) is shown, where the primary cell (P cell) comes from a GEO satellite and the secondary cell (S cell) comes from a LEO satellite;

[0013] Figure 7 The signaling diagram for dual connectivity (DC) between the UE and GEO and LEO satellites is shown.

[0014] Figure 8 A signaling diagram is shown for providing secondary cell group (SCG) configuration to the UE via a GEO satellite, wherein the GEO satellite releases its connection with the UE before the LEO satellite is attached;

[0015] Figure 9 The signaling diagram for providing SCG configuration to the UE via a GEO satellite is shown, in which the GEO satellite releases its connection with the UE after the LEO satellite is attached;

[0016] Figure 10 The diagram shows a high-level signaling diagram of the connection handover from a GEO satellite to a LEO satellite;

[0017] Figure 11A flowchart is shown illustrating a method performed by the UE for connecting to the core network via GEO and LEO satellites or other further network entities;

[0018] Figure 12 A flowchart is shown illustrating a method performed by GEO to connect a UE to the core network via GEO satellites and LEO satellites or other further network entities;

[0019] Figure 13 Schematic examples of computing systems / apparatus for performing any of the methods, operations, or processes described herein and / or for implementing any of the systems, units, and / or apparatuses described herein are shown; and

[0020] Figure 14 The non-transitory medium is shown according to some implementation methods. Detailed Implementation

[0021] GEO satellites typically create large beams on the ground, meaning they have wide coverage areas or "footprints." This can result in GEO satellites having limited bandwidth for network signaling. The higher orbital altitude of GEO satellites also introduces additional latency to signals communicating via GEO satellites to / from core networks (e.g., 5G core networks).

[0022] In contrast, LEO satellites create narrower beams and are closer to the Earth's surface, allowing them to transmit signals with lower latency and / or higher bandwidth. However, because LEO satellites move rapidly (relative to the Earth's surface) and have smaller beam coverage areas, UEs must frequently re-register and update their positions when they move out of one LEO satellite's beam and into another. Furthermore, in complex LEO-based systems, additional measurements and reporting are used to maintain frequency and Doppler stabilization on the ground. All of this leads to additional power consumption and complexity, and can result in shorter UE battery life.

[0023] The systems, methods, and apparatus described herein are designed to provide UEs with a fast and energy-efficient means of communication via NTN connections. NTN includes satellites, drones, aircraft, balloons, high-altitude platform stations (HAPS), etc. For simplicity, the implementations described herein will be described with reference to satellites, particularly GEO and LEO satellites, although they can also be applied to other types of NTN.

[0024] To address these issues, the UE maintains a connection to GEO satellites by default; that is, it is "anchored" to a GEO satellite connection. For example, for control signals and / or lower quality data transmissions (e.g., for data signals with a low Quality of Service Stream Indicator (QFI), the UE communicates with the core network via GEO satellites by default. Because the area of ​​the Earth's surface covered by spot beams from GEO satellites (called the satellite's "coverage area" or "spot beam coverage area") is large and stationary relative to the Earth's surface, the UE does not need to send frequent location updates; location updates are only required when the UE travels from one GEO satellite spot beam coverage area to another. This saves power at the UE.

[0025] However, when the UE or core network requests a higher-quality connection for data transmission, the GEO satellite anchor initializes the data connection between the UE and the core network to an LEO satellite covering the UE's current location. The GEO satellite provides configuration data for connecting the UE to the LEO satellite. The UE uses the configuration data to establish a connection to the LEO satellite. The UE then uses the higher-quality connection via the LEO satellite to communicate data with the core network. In some examples, the UE concurrently maintains a connection to the GEO satellite with the LEO satellite, routing at least some control signals via the GEO satellite connection and at least some data signals via the LEO satellite connection. After the UE completes data transmission on the higher-quality connection, or if the LEO satellite connection is lost, the UE defaults back to the GEO satellite connection; that is, the GEO satellite connection acts as the anchor for the LEO satellite connection.

[0026] In this manner, the UE establishes a higher-quality connection (e.g., higher throughput, higher QoS, and / or lower latency) via LEO satellites (or other NTNs) upon request, but otherwise communicates with the core network using a lower-quality connection via GEO satellites. This reduces the UE's power consumption while providing the benefits of a higher-quality connection when desired.

[0027] In some implementations, the signaling radio bearer (SRB) is set up via a GEO or LEO satellite connection, depending on the type of SRB being transmitted. For example, SRB1, SRB2, and SRB3 are established via a LEO satellite connection (in addition to the data radio bearer (DRB)). In some examples, SRB0 is set up via a GEO satellite connection. In some implementations, a further SRB (referred to herein as SRB4) is set up via a GEO satellite connection. SRB4 can be used for cell activation / deactivation signals, paging, and / or TA updates (e.g., even if an LEO satellite connection supporting SRB1 is present). Such SRB4 can accelerate certain dedicated control channel (DCCH) messaging. In some implementations, when the UE is only connected to a GEO satellite, both the SRB and DRB are established via that GEO satellite.

[0028] As used herein, the term "quality" when referring to a connection can refer to any one or more metrics of the quality of the connection. For example, connection quality can refer to one or more Quality of Service (QoS) attributes, such as speed / throughput, latency (e.g., end-to-end latency), network availability, reliability, jitter, bandwidth, and / or whether the connection is a Guaranteed Bit Rate (GBR) connection or a non-GBR connection. In some implementations, connection quality refers to one or more QoS Class Identifiers (QCIs) of the QoS flows associated with the connection, such as the 5G QoS Identifier (5QI).

[0029] Figure 1 An overview of network system 100 is shown. The system shows user equipment (UE) 102, GEO satellite 104, one or more LEO satellites 106A, 106B, and in some examples, one or more ground base stations 116. In some examples, the system includes other satellite types and / or alternative types of NTNs (e.g., Medium Earth Orbit (MEO) satellites, heterogeneous orbit satellites, drones, HAPS, balloons, aircraft, etc. – not shown). GEO satellite 104 has a fixed, wide coverage area (i.e., spot beam coverage area) 110 on the Earth's surface, typically approximately 100 km. LEO satellites 106A, 106B each have corresponding coverage areas 112A, 112B. The coverage areas 112A, 112B of LEO satellites 106A, 106B cross the coverage area 110 of the GEO satellite during the LEO satellite's orbital operation. The LEO satellite coverage area is typically smaller than the GEO satellite coverage area.

[0030] UE 102 registers with GEO satellite 104 and sends location updates via GEO satellite by default. In some implementations, a registration area is set for the GEO satellite. In such implementations, location updates, such as registration updates, are only required when UE 102 crosses between GEO satellite coverage areas (i.e., when the UE leaves the coverage area of ​​one GEO satellite and enters the coverage area of ​​another). Because the diameter of the GEO satellite coverage area is approximately 100 km, periodic registration updates for the GEO registration area are not required, thus reducing the power consumption of UE 102. GEO satellite 104 acts as an anchor for UE 102 and manages the UE's connections to LEO satellites 106A, 106B and / or other network entities 116 (such as terrestrial access points or other NTNs). UE 102 transmits and receives signals 108, such as control signals and low QoS / 5QI data signals carrying text messages and text emails, via GEO satellite 104.

[0031] UE 102 may request higher quality signaling for uplink data plane signaling via GEO satellite 104. In some examples, if UE 102 is idle or inactive, a request for higher quality signaling is sent from UE 102 to GEO satellite 104 via a Physical Random Access Channel (PRACH) procedure. In response, GEO satellite 104 transmits to UE 102 a configuration for connection to LEO satellite 106A accessible to UE 102 (i.e., LEO satellite 106A currently covering the location of UE 102 in coverage area 112A). In some examples, this configuration is transmitted to UE 102 via a paging procedure.

[0032] If UE 102 already has an active connection to GEO satellite 104, it sends a request for higher quality signaling, for example, via uplink control information (UCI) or scheduling request (SR) messages. In response, GEO satellite 104 connects UE 102 to LEO satellite 106A, for example, using a resource granting procedure, such as downlink control information (DCI).

[0033] The core network may also request higher quality signaling on the downlink. For example, a request for higher quality signaling (on the uplink or downlink) may be triggered based on the amount of incoming / buffered network traffic, the QoS Flow Identifier (QFI) of the data to be transmitted, a request for higher QoS, and / or a request for additional radio bearers. Alternatively or additionally, a weakened GEO satellite signal strength may be used as a trigger for requesting higher quality signaling.

[0034] Then, UE 102 uses this configuration to establish a connection with LEO satellite 106A and communicate with the core network via LEO satellite 106A through a higher quality connection.

[0035] In some examples, this configuration includes the Physical Cell ID (PCI) of LEO satellite 106A, carrier frequency, reference position, distance threshold, and / or ephemeris data of LEO satellite 106A. The configuration data is signaled using, for example, existing Master Information Block (MIB) and System Information Block (SIB) messages, RRC reconfiguration messages, and / or measurement configuration data. Ephemeris data may be sent as a new message type or included in existing message types.

[0036] In some implementations, ephemeris data is transmitted from GEO satellite 104 to UE 102. Alternatively, to conserve data transmission, UE 102 may maintain a pre-computed ephemeris dataset, and if necessary, GEO satellite 104 may transmit modifications / corrections to the pre-computed ephemeris data to UE 102. The orbital characteristics of the LEO constellation determine how long the ephemeris data is valid. Corrections may be shared for some time before the entire table needs to be updated. In some examples, the pre-computed ephemeris data is based on a pre-computed ephemeris data table known to both the core network / NTN / RAN and UE 102. The pre-computed table is updated periodically, such as daily, weekly, or monthly. In some implementations, the updated ephemeris table may be downloaded to UE 102 when available, and / or broadcast by the RAN network on a downlink (DL) broadcast channel (e.g., via ground base station 116 or GEO satellite 104).

[0037] In some implementations, version control is used to track which version of the ephemeris has been downloaded by UE 102. Alternatively or additionally, the NTN or core network may poll UE 102 to determine the ephemeris version that UE 102 has downloaded. Based on the version currently available at UE 102, the NTN or core network determines which (if any) corrections to the ephemeris data should be sent to UE 102.

[0038] During higher quality sessions with LEO satellite 106A, UE102 maintains connectivity to GEO satellite 104 in some implementations, such as using carrier aggregation (CA) or dual connectivity (DC), as described in this paper. Figure 6 and Figure 7 As described above. In such cases, the GEO satellite 104 connection is used and / or preferably used as an anchor carrier for at least some control and paging messages. Alternatively, the GEO satellite 104 may completely transfer the connection to a LEO satellite, as described herein. Figure 8 to Figure 10As described above. In such an example, the connection between GEO satellite 104 and UE 102 is terminated until LEO satellite 106A completes transmission over a higher quality connection or if the higher quality connection becomes unavailable, and then hands the connection back.

[0039] In some implementations, connections to LEO satellite 106 and / or other satellite systems are further based on an algorithm that takes into account the current load on each satellite subsystem, the expected bandwidth requirements, and / or the priority of applications for each mobile device.

[0040] In some examples, GEO satellite 104 and / or LEO satellite 106 operate using a bend-through architecture or a regenerative architecture. In the bend-through architecture, satellites 104 and 106 receive signals on the uplink, amplify the signals, convert the signals to the downlink frequency, and then retransmit the signals at that downlink frequency. Satellites 104 and 106 perform little or no additional processing. In the bend-through architecture, inter-satellite signaling is performed via a terrestrial satellite gateway. In the regenerative architecture, satellites 104 and 106 receive signals on the uplink, then demodulate and decode the signals. The signals are then encoded and modulated before transmission at the downlink frequency.

[0041] In some examples, GEO satellite 104 also serves as an anchor for terrestrial network (TN) connections, such as network entity 116. Because TN connections typically support higher QoS values, UE 102 prioritizes TN connections over GEO satellite connections to establish DRBs while maintaining the GEO satellite connection. In some examples, at least some SRBs are also set up via the GEO satellite connection. If, for example, the quality of the TN connection cannot be maintained at the edge of a TN coverage area, UE 102 switches to communicating data with the core network via GEO satellite 104, for example, to set up DRBs and SRBs via the GEO satellite connection. If UE 102 or the core network requests a higher quality connection than that provided by GEO satellite 104, GEO satellite 104 provides a configuration for the LEO satellite 106 connection, as described herein. In this way, a hierarchy of connections is established, where TN connections are prioritized for data delivery when the GEO satellite is used as an anchor. When the terrestrial network is unavailable, unstable, and / or cannot provide the target QoS level, the GEO satellite connection is used as a lower quality connection for data delivery. Use LEO satellite connectivity when performance improvements for GEO satellite connectivity are required.

[0042] Figure 2An example state diagram of the UE is shown. This state diagram illustrates three examples of the UE's states: inactive state 202; lower quality connection state 206; and higher quality connection state 208. The state diagram indicates in brackets for each state which subsystem (e.g., GEO or LEO satellite) the UE is attached to for data transmission.

[0043] In inactive state 202, the UE maintains its connection with the GEO satellite. In some examples, the inactive state corresponds to RRC_Inactive, such as a state where there is little or no data transmission between the UE and the GEO satellite, but the RRC entity is not fully released and the Non-Access Stratum (NAS) layer is maintained. In some examples, the inactive state corresponds to Connected Mode Discontinuous Receive (CDRX) state, in which the UE periodically wakes up to monitor the Physical Downlink Control Channel (PDCCH) from the GEO satellite. When the UE or the core network requests lower quality communication, the UE initiates a lower quality session (204) and enters a lower quality connection state (206), during which the UE communicates data with the core network via the GEO satellite. After the lower quality session is completed, the UE can transition (state 208) back to inactive state 202.

[0044] When in a lower-quality connection state 206, the UE or core network may request a higher-quality connection, such as transmitting data with higher bandwidth and / or lower latency, supporting higher QoS, etc. In response to such a request, the GEO satellite transmits configuration information for the LEO satellite to the UE, such as regarding... Figure 1 and / or Figure 4 to Figure 9 As described. Upon receiving this configuration, the UE transitions 210 to a higher quality session and enters a higher quality connection state 212, during which the UE transmits data signals to the core network via the LEO satellite. After the higher quality session concludes, the UE can transition 214 back to a lower quality connection state 206 and continue transmitting data to the core network via the GEO satellite. Alternatively, if there is no further data to be transmitted by the UE or the core network at present, the UE can transition 216 back to an inactive state 202.

[0045] The UE can also transition directly from the inactive state 202 to a higher quality connection state 212, for example, when the UE is in an inactive state if the UE or the core network determines that a higher quality connection is desired.

[0046] Figure 3A network diagram is shown. Network 300 includes UE 302, GEO satellite gateway (GEO-GW) 304, LEO satellite gateway (LEO-GW) 306 (or another NTN gateway), core network 308 (5GC), and terrestrial gNodeB (gNB) 310. GEO-GW 304 facilitates communication between core network 308 and GEO satellites, for example, receiving signals from core network 308 and transmitting them to GEO satellites, and receiving signals from GEO satellites and transmitting them to core network 308. LEO-GW 306 facilitates communication between core network 308 and LEO satellites, for example, receiving signals from core network 308 and transmitting them to LEO satellites, and receiving signals from LEO satellites and transmitting them to core network 308.

[0047] UE 302 maintains a radio anchoring connection with GEO-GW 304 for signaling transmission of at least some control plane signals 312. When UE 302 is connected to the core network 308 solely via GEO-GW 304, all control plane signals 312 (e.g., SRBs) and data signals 314 (e.g., DRBs) to UE 302 are established via GEO-GW 304. When UE 302 is connected to the core network 308 via one or more gateways (e.g., LEO-GW 306 and / or terrestrial gNB 310) in addition to GEO-GW 304, at least some control plane signals 312 communicate with the core network 308 via GEO-GW 304, and at least some data signals 316, 318 communicate with the core network via additional connections, such as at least some DRBs 314, 316 configured via additional connections. In some implementations, all control plane signals 312 communicate with the core network 308 via GEO-GW 304. Alternatively, a suitable subset of control plane signals 312 communicates with the core network 308 via GEO-GW 304, and other control plane signals (not shown) communicate with the core network 308 via additional connections. For example, SRB0 and / or SRB4 communicate with the core network 308 via GEO-GW 304, and SRB1, SRB2, and / or SRB3 communicate with the core network 308 via LEO-GW 306 and / or ground gNB 310.

[0048] The GEO and LEO satellites communicate across the core network 308 via GEO-GW 304 and LEO-GW 306 and / or, in some examples, via a direct satellite-to-satellite connection (i.e., over the air). For example, when an LEO satellite enters the GEO satellite spot beam, configuration data for the LEO satellite connection is transmitted from LEO-GW 306 to GEO-GW 304 via the core network 308. Then, in response to receiving a request for a higher quality connection, GEO-GW 304 transmits the configuration data for the LEO satellite connection to the GEO satellite for transmission to UE 302.

[0049] Figure 4 A high-level signaling diagram is shown for establishing a connection between UE 402 and core network 408 via GEO satellite. UE 402 initially connects to GEO satellite gateway 404 (GEO-GW) via GEO satellite. In response to a request for a higher quality connection, GEO-GW 404 guides UE 402 to connect to LEO gateway 406 (LEO-GW) via LEO satellite using a configuration supplied by GEO satellite.

[0050] Initially, core network 408 transmits network configuration information 410 to the GEO satellite via GEO satellite gateway 404 and network configuration information 412 to the LEO satellite via LEO satellite gateway 406. GEO-GW 404 transmits configuration information 410 to the GEO satellite, which then broadcasts this configuration information 414 across the GEO satellite's spot beam / cell. When within the spot beam, UE 402 receives a broadcast 414 containing configuration information for UE 402 to connect to the GEO satellite. UE 402 uses the configuration information in the cell broadcast 414 to attach to core network 408 via GEO satellite and GEO-GW 404 via attachments 416 and 418. After network attachments 416 and 418, UE 402 and core network 408 transmit data signals 420 and 422 via GEO satellite and GEO-GW 404. Both data and control signals communicate between core network 408 and UE 402 via GEO-GW 404 and GEO satellite.

[0051] In some implementations, core network 408 determines that a higher quality connection is requested to UE 402. This determination is based on meeting one or more threshold conditions. In response to determining that a higher quality connection is requested, core network 408 transmits a high-quality connection request 424 to a GEO satellite via GEO-GW 404. Alternatively or additionally, UE 402 determines that a higher quality connection is requested to core network 408. This determination is based on one or more threshold conditions previously described. In response to determining that a higher quality connection is requested, UE 402 transmits a high-quality connection request 426 to a GEO-GW 404 satellite via a GEO satellite.

[0052] In some examples, one or more of the threshold conditions for core network 408 and / or UE 402 are based on a target connection quality for transmissions of the signal set exceeding one or more threshold connection quality values. For example, the target connection quality may include one or more of the following: target QoS (e.g., indicated by a QoS flow indicator QFI for one or more packets used for transmission), target latency, target bandwidth, target error rate, etc. One or more threshold connection quality values ​​include, for example, threshold bandwidth, threshold latency, threshold QoS, etc. In some examples, one or more thresholds are based on GEO satellite capabilities, such as the maximum bandwidth available to the GEO satellite, the maximum QoS that the GEO satellite can provide, and / or the minimum latency that the GEO satellite can provide. Alternatively or additionally, a higher quality connection request is triggered in response to a request for additional radio bearers.

[0053] In addition to the common threshold conditions described previously, in some examples, one or more of the threshold conditions for the core network 408 (i.e., network-side threshold conditions) include one or more conditions based on the amount of data used to transmit from the core network 408 to the UE 402 (i.e., on the downlink). An example of a threshold condition is that the amount of data used to transmit to the UE 402 is higher than a threshold; for example, one or more files used to transmit to the UE 402 have a size higher than a threshold.

[0054] In addition to the common threshold conditions described previously, in some examples, one or more of the threshold conditions for UE 402 (i.e., UE-side threshold conditions) include one or more conditions based on the amount of data used to transmit from UE 402 to core network 408 (i.e., on the uplink). For example, a threshold condition is that the amount of data used to transmit to core network 408 is higher than a threshold, such as the amount of data in the buffer used to transmit to core network 408 being higher than a threshold, and / or one or more files used to transmit to core network 408 having a size higher than a threshold.

[0055] In response to receiving high-quality connection requests 424 and 426, and as part of establishing a LEO connection 424, the GEO satellite transmits configuration information for the LEO satellite connection to UE 402. UE 402 uses this configuration to establish a connection to the LEO satellite 424 while maintaining a connection to the GEO satellite; that is, concurrent connections exist between UE 402 and both the GEO and LEO satellites. The following is about... Figure 6 to Figure 10 Describe an example of establishing a connection with a LEO satellite 424.

[0056] UE 402 then communicates data signals to core network 408 via LEO satellite; for example, at least some DRBs are set via LEO satellite. At least some control signals are still communicated via GEO satellite connection; for example, at least some SRBs such as SRB0 and / or SRB4 are set via GEO satellite connection. In some implementations, data signals are communicated via GEO satellite connection or LEO satellite connection, depending on the QFI associated with the data signal. For example, data signals with a QFI corresponding to a higher QoS (i.e., above the threshold QoS) are set via LEO satellite connection, while data signals with a QFI corresponding to a lower QoS (i.e., below the threshold QoS) are set via GEO satellite connection.

[0057] In some examples, concurrent connections between UE 402 and the LEO satellite, and between UE 402 and the GEO satellite, are based on carrier aggregation (CA) or dual connectivity (DC) protocols, or both. Other methods known in the art can be used to maintain concurrent connections between UE 402 and both the LEO and GEO satellites.

[0058] Figure 5A An example of the CA protocol is shown. Carrier aggregation (CA) is a connectivity mode: in this connectivity mode, UE 502 uses multiple component carriers 550A, 550B to transmit and / or receive data traffic 552, thereby operating on multiple frequencies simultaneously. One carrier is designated as the primary cell (P cell), through which Radio Resource Control (RRC) layer communications are relayed. Traffic 552 is segmented between carriers in the Media Access Control (MAC) layer 554 of the protocol. In the example shown, CA uses a single base station 556, but typically multiple base stations can be used. (See the attached document for more details.) Figure 6 The GEO satellite / GEO-GW acts as the P cell for the connection between UE 502 and the core network, while the LEO satellite / LEO-GW (or other NTN) acts as the secondary cell (S cell).

[0059] Figure 5BAn example of the DC protocol is shown. Dual connectivity is a connection mode in which UE 502 simultaneously connects to multiple base stations / cells 556A and 556B, using different carriers 550A and 55B on each base station / cell. Traffic 552 is segmented between carriers at the Packet Data Convergence Protocol (PDCP) layer 558. One cell 556A is designated as the master node (MN), while the other cell is designated as the secondary node (SN) 556B. The UE initially connects via the MN. UE 502 receives RRC signals via the MN and uses these signals to connect to the SN. Figure 7 In the example shown, the GEO satellite / GEO-GW acts as MN, while the LEO satellite / LEO-GW acts as SN.

[0060] Figure 6 The signaling diagram for carrier aggregation (CA) is shown, where the primary cell (P cell) originates from GEO satellite 604 and the secondary cell (S cell) originates from LEO satellite 606. In response to receiving requests 624, 626 (similar to 424, 426) for a higher quality connection, GEO-GW 604 initiates a CA connection 628 (similar to 428) with the LEO-GW 606 supporting the S cell. To this end, GEO-GW 604 requests 630 S cell configuration information from LEO-GW 606. LEO-GW 606 responds 632 with S cell configuration information for UE 602. GEO-GW 604 then forwards 634 the S cell configuration information to UE 602 via the GEO satellite. UE 602 responds with an acknowledgment 636 that the S cell configuration information has been received, and GEO-GW 604 forwards this acknowledgment 638 to the core network 608.

[0061] After receiving confirmation 638 from UE 602 that it has received the S-cell configuration information, the core network 608 transmits an S-cell activation signal 640 to GEO-GW 604. GEO-GW 604 then forwards this S-cell activation signal 642 to UE 602 via GEO satellite. Upon receiving the S-cell activation signal 642, UE 602 establishes a connection with LEO-GW 606 via the S-cell random access channel (RACH) 644 via LEO satellite, while maintaining the connection to GEO-GW 604 via the anchor GEO satellite. UE 602 and core network 608 then transmit data signals 646 and 648 via LEO-GW 606 and the LEO satellite, i.e., DRB setup via LEO satellite. At least some control signals are communicated between core network 608 and UE 602 via GEO satellite connection; for example, at least some SRBs are set via GEO satellite.

[0062] Figure 7The signaling diagram for dual connectivity (DC) between the UE and both GEO and LEO satellites is shown. In response to receiving requests 724, 726 (similar to 424, 426) for a higher quality connection, GEO-GW 704 initiates a DC connection 728 (similar to 428) with LEO-GW 706, which acts as a secondary node. To this end, GEO-GW 706 transmits a request 750 for secondary cell group (SCG) configuration data to the LEO satellite located within the coverage area of ​​the GEO satellite associated with GEO-GW 704. The LEO-GW 706 responds with an SCG configuration 752 for the UE 702.

[0063] The GEO-GW 704 obtains LEO ephemeris data via the core network 708. In some examples, the LEO ephemeris function / server (not shown) stores the current LEO ephemeris table and distributes it to the rest of the network (i.e., via the TN / NTN), for example, on demand, whenever the ephemeris table is updated, and / or periodically. For example, an updated LEO ephemeris table is broadcast to UE 702 via the network (i.e., the TN / NTN). The LEO ephemeris function / server tracks which version of the ephemeris table each UE 702 has stored in its memory. In some examples, the LEO ephemeris function uses this tracking data to determine which update (if any) to send to UE 702. In some examples, the LEO ephemeris function uses this tracking data to determine whether to send the complete updated ephemeris table to UE 702 or a set of changes to the current version of the ephemeris table stored on UE 702.

[0064] The GEO-GW 704 transmits LEO ephemeris data 754 and received SCG configuration / addition information 756 (from message 730) to UE 702 via a GEO satellite. In some examples, the GEO satellite broadcasts the LEO ephemeris data 754 to all UEs 702 within the spot beam of the GEO satellite.

[0065] UE 702 uses LEO ephemeris data 754 and SCG configuration / addition information 756 to establish additional connections 746 and 748 to the core network 708 via LEO satellites and LEO-GW 704. LEO satellite 706 then acts as the SCG for data connectivity. Traffic can be prioritized on each link based on target quality; for example, data associated with higher target quality is routed via LEO satellite links, and data associated with lower target quality is routed (concurrently) via GEO satellite links. At least some control signals are routed via GEO satellite links.

[0066] Each carrier can be managed independently to take timing into account; for example, each base station / gateway independently handles its corresponding data stream. Cross-carrier scheduling is used in some examples. PDCP layer or MAC layer segmentation can be used to account for the different latency and bandwidth capabilities of each carrier.

[0067] Figure 8 It shows Figure 7 A variant of the signaling diagram, where the GEO satellite releases its connection to UE 802 between providing configuration for LEO connectivity and establishing the LEO connection. Signaling follows... Figure 7 The same process described in [the original text] continues until the broadcast of LEO ephemeris data 854 from the GEO satellite and the transmission of cell reconfiguration data 856 (i.e., operations 824-856 are consistent with [the original text]). Figure 7 (Corresponding to operations 724-756). After broadcasting LEO ephemeris data 854 and transmitting cell reconfiguration data 856, UE 802 releases the connection between UE 802 and the 858 GEO satellite. Then, UE 802 uses LEO ephemeris data 854 and cell reconfiguration data 856 to connect to the core network 808 via LEO-GW 806 and LEO satellite attachment (operations 846, 848).

[0068] Figure 9 It shows Figure 7 A variation of the signaling diagram in the diagram, where the GEO satellite maintains its connection to UE 902 after providing configuration data for the LEO satellite connection, until the UE is attached to the LEO-GW via the LEO satellite. Then, the GEO-GW 904 releases its connection to UE 902. The signaling follows the same pattern as... Figure 7 The same process described in [the document] continues until UE 902 is connected to core network 908 via LEO satellite and LEO-GW 906 via attachments 936, 938 (i.e., operations 924-948 and [other connections]). Figure 7 (Corresponding to operations 724-748). After UE 902 is connected to core network 908 via LEO satellite and LEO-GW 906, and then to attachments 946 and 988, UE 902 releases the connection between UE 902 and the 958 GEO satellite.

[0069] Figure 10A high-level signaling diagram illustrating the handover of a connection from a GEO satellite to a LEO satellite, such as a handover or a reconfiguration with synchronization, is shown. In response to a request 1026, 1027 from UE 1002 for a higher quality connection, or a determination by core network 1008 of a desired higher quality connection, core network 1008 sends an LEO handover command 1060 to the GEO satellite via GEO-GW 1004. The GEO satellite forwards the LEO handover command 1062 to UE 1002. The handover command 1062 includes a configuration for connecting to LEO-GW 1006 via the LEO satellite. Upon receiving the handover command 1062, UE 1002 triggers a connection 1064 to LEO-GW 1006 via the LEO satellite using the configuration provided in the handover command 1062. After a connection is established between UE 1002 and LEO GW 1006, the LEO satellite sends a connection confirmation 1066 to core network 1008. Then, core network 1008 and UE 1002 communicate via LEO satellite and LEO-GW 1006 using higher quality connections 1068 and 1070.

[0070] Figure 11 A flowchart illustrating an example method for communication within a network is shown. This method can be derived from, for example, [the following is unclear and requires further context: "about..."] Figure 1 and Figure 13 The UE execution described in the document. In some implementations, this method is at least partially consistent with the method described in this document. Figure 4 and Figure 6 to Figure 10 Any one or more of the methods described correspond to this.

[0071] At operation 1116, the UE establishes a connection with the GEO satellite. In some implementations, operation 1116 can be connected to... Figure 4 This corresponds to operations 410 to 418. The connection provides a data plane through which data is provided to and from the UE (e.g., through which the DRB is set); and a control plane for network signaling (e.g., through which the SRB is set). The connection between the UE and the GEO satellite can be established using any method known in the art, such as the Physical Random Access Channel (PRACH) procedure.

[0072] At operation 1122, the UE communicates a first set of signals with a network such as a 5G core network via a GEO satellite. This first set of signals can be communicated with… Figure 4 The data signals 420 and 422 correspond to each other. The first signal set includes signals transmitted through the connected data plane, such as DRBs. In some examples, the first signal set further includes control signals transmitted in the control plane, such as SRBs. The transmission of the first signal set between the UE and the network via GEO satellite is at a first quality value.

[0073] The term "quality value" refers to a measure of the quality of the connection between the UE and the network. As examples, quality metrics include one or more of the following: connection bandwidth, connection throughput, connection latency, connection QoS or QFI, etc.

[0074] In some implementations, the first set of signals includes small files / messages, such as text messages or emails, that meet QoS or QFI threshold criteria, and / or data signals that do not require low-latency connections. The QoS or QFI threshold criteria can be a specific subset of QoS or QFI values ​​that can be supported by GEO satellites.

[0075] At operation 1126, the UE requests configuration from the GEO satellite for connectivity with further network entities. This request can be combined with... Figure 4 Signal 426 and Figure 6 to Figure 10 The signals 626, 726, 826, 926, and 1026 correspond to these. In some examples, the UE sends a request in response to determining that one or more threshold conditions in a set satisfy one or more threshold conditions. This request is communicated, for example, via the SRB in the control plane of the connection between the UE and the GEO satellite. Alternatively or additionally, requests for configuration of connections with further network entities may originate from the core network, based on the network determining that one or more threshold conditions in a set satisfy one or more network-side threshold conditions. (This document references...) Figure 4 Especially reference Figure 4 Elements 424 and 426 describe examples of threshold conditions on the UE side and the network side.

[0076] This further network entity is one that supports higher-quality connections to the network compared to GEO satellites. This further network entity is, for example, a LEO satellite. Alternatively, this further network entity is a medium Earth orbit satellite, a satellite in a heterogeneous orbital architecture, a drone, an aircraft, a balloon, and / or a ground station.

[0077] At operation 1132, the UE receives configuration data from the GEO satellite for connecting to further network entities. This configuration data may include, for example, […]. Figure 6 The S cell is configured with 632, Figure 7 to Figure 9 LEO ephemeris data 754, 854, 954 and / or SCG configuration 756, 856, 956 and / or Figure 10 The handover command 1062 in the document. Configuration data supports higher quality radio connectivity for UE-GEO satellite connections compared to further entities. This configuration includes, for example, the physical cell ID of the LEO satellite, carrier frequency, reference location, and / or distance threshold.

[0078] In some examples, the configuration data additionally includes ephemeris data for satellites connected to, for example, LEO satellites. In some examples, the configuration data includes a complete ephemeris dataset. Alternatively, the configuration data includes corrections to a pre-computed ephemeris dataset stored on the UE. The core network maintains a record of the versions of the ephemeris data stored on the UE and determines which updates, if any, are sent to the UE as part of the configuration data.

[0079] At operation 1146, the UE uses this configuration to establish further data connections between the UE and further network entities, while maintaining the connection between the UE and the GEO satellite. Operation 1146 can be used with... Figure 6 to Figure 10 The attachment operations 646, 746, 846, 946, and 1068 correspond to these. A data connection is a link through which signals in the data plane are transmitted; for example, a DRB is set via this connection.

[0080] The connection between the GEO satellite and the UE is used for the transmission of at least some control signals in the control plane (i.e., setting one or more SRBs via the GEO satellite), for example, for establishing and / or tearing down connections between the UE and one or more further network entities. In some implementations, all SRBs are set via the GEO satellite connection (e.g., SRB0-SRB3, and SRB4 if used). Alternatively, an appropriate subset of SRBs (e.g., SRB0 and / or SRB4) is set via the GEO satellite connection. In some examples, carrier aggregation (CA) and / or dual connectivity (DC) are used to maintain concurrent connections between the GEO satellite and the UE, and between the LEO satellite and the UE.

[0081] At operation 1180, the UE communicates a second set of signals to the network via a further network entity. The second set of signals includes data signals, i.e., signals in the data plane. In some examples, the second set of signals may additionally include an appropriate subset of control signals (e.g., SRB0, SRB1, SRB2, and / or SRB3). The communication of the second set of signals between the UE and the core network via the further network entity is at a second quality value higher than the first quality value, for example, at higher bandwidth, higher QoS, and / or lower latency. The second set of signals includes, for example, audio data (such as voice calls and / or music), video data, text data, large files, and / or chat messages. Many other examples are possible.

[0082] In some implementations, when a connection to a further network entity exists, all data signals are set via that further network entity, and the GEO satellite is used only for control signals. In some implementations, depending on the QoS Flow ID (QFI) associated with the data signal, the data signal is routed via either the further network entity connection or the GEO satellite connection. Data signals with a QFI indicating a higher QoS flow (e.g., above a threshold QoS value) are routed via the further network entity, while data signals with a QFI indicating a lower QoS flow (e.g., below a threshold QoS value) are routed via the GEO satellite connection.

[0083] In some implementations, the GEO satellite can mediate the handover from a further network entity to an additional network entity, for example, from a first LEO satellite to a second LEO satellite. The UE receives additional configuration from the GEO satellite for connecting the UE to the additional network entity. In some implementations, the GEO satellite transmits the additional configuration in response to (e.g., by the core network or the UE) determining that the UE is moving out of the coverage area of ​​the further network entity due to the movement of the UE and / or the movement of the further network entity. Alternatively or additionally, the GEO satellite transmits the additional configuration in response to (e.g., by the network or the UE) determining that a second quality value has degraded below a threshold and / or the additional entity (currently) supports a connection with a higher quality value than the further network entity. In some implementations, the UE sends a request for additional configuration data to the GEO satellite. The request for additional configuration data to the GEO satellite may also originate from the network.

[0084] In response to receiving additional configuration for connecting the UE to an additional network entity, the UE establishes an additional data connection between the UE and the additional network entity based on the additional configuration, and terminates the connection between the UE and the further network entity. A third signal set is transmitted between the UE and the network via the additional network entity at a third quality value higher than the first quality value. In some examples, the third signal set is of the same type as the second signal set.

[0085] Figure 12 An example method for facilitating communication between the UE and the network is illustrated. This method is performed by a GEO satellite. In some implementations, this method is at least partially related to the methods discussed in this paper. Figure 4 and Figure 6 to Figure 10 Any one or more of the methods described correspond to this.

[0086] At Operation 1201, the GEO satellite maintains a geosynchronous orbit. Maintaining a geosynchronous orbit keeps the GEO satellite's spot beam (approximately) fixed on the Earth's surface.

[0087] At operation 1216, the UE establishes a connection with the GEO satellite. In some implementations, operation 1216 can be connected to... Figure 4 This corresponds to operations 410 to 418. The connection provides a data plane through which data is provided to and from the UE (e.g., DRB), and a control plane for network signaling (e.g., SRB). The connection between the UE and the GEO satellite can be established using any method known in the art, such as using a Physical Random Access Channel (PRACH).

[0088] At operation 1222, the core network (e.g., a 5G core network) and the UE transmit the first signal set across this connection via GEO satellite. The first signal set can be used with... Figure 4 The data signals 420 and 422 correspond to each other. Regarding... Figure 11 Operation 1122 further describes in detail the transmission of the first set of signals.

[0089] At operation 1226, the GEO satellite receives a request for a higher quality connection from the UE or the core network. When the request originates from the core network, it can be used with... Figure 4 Signal 424 and Figure 6 to Figure 10 The signals 624, 724, 824, 924, and 1024 correspond to this. When the request originates from the UE, the request can be associated with... Figure 4 Signal 426 and Figure 6 to Figure 10 The signals 626, 726, 826, 926, and 1026 correspond to these. In some examples, the UE / network sends this request in response to determining that one or more threshold conditions in a set satisfy one or more threshold conditions. Any of the threshold conditions described herein can be used, for example, as per [reference to...]. Figure 10 As described. In some examples, the request is communicated, for instance, via the SRB in the control plane of the connection between the UE / network and the GEO satellite. Examples of requests for higher quality connections are discussed in this article. Figure 11 Operation 1126 is described in further detail.

[0090] At operation 1232, the GEO satellite transmits to the UE configuration for further network entities supporting connections with a second quality value, which is higher than the first quality value. Configuration data may include, for example, […]. Figure 6 The S cell is configured with 632, Figure 7 to Figure 9 LEO ephemeris data 754, 854, 954 and / or SCG configuration 756, 856, 956 and / or Figure 10 The handover order 1062 in the document. This article is about... Figure 11 Operation 1132 further describes an example of the transport configuration in detail.

[0091] At Operation 1290, the GEO satellite maintains at least partially the connection between the satellite and the ground user equipment while the ground user equipment connects to further network entities. Call aggregation and / or dual connectivity can be used to maintain the connection, as described herein. Figure 6 and Figure 7 As described, however, those skilled in the art will understand that alternative methods of maintaining multiple connections may be used. The connection between the GEO satellite and the UE is used for the transmission of at least some control signals in the control plane, for example, for establishing and / or terminating connections between the UE and one or more further network entities.

[0092] Figure 13 A schematic example of a computing system / equipment 1300 for performing any of the methods, operations, or processes described herein and / or for implementing any of the systems, units, and / or apparatuses described herein is shown. The computing system / equipment 1300 shown is an example of a computing device or platform. Those skilled in the art will understand that other types of computing devices / systems / platforms may alternatively be used to implement the methods described herein, such as distributed computing systems. In some examples, the computing system / equipment 1300 is a UE, a subsystem of the UE, and / or a subsystem of a satellite.

[0093] The apparatus (or system) 1300 includes one or more processors 1302 (e.g., CPUs). The one or more processors 1302 control the operation of other components of the system / apparatus 1300. The system / apparatus 1300 may be part of a computing device, computing system, distributed computing system, cloud computing platform, etc., for implementing the functionality of the system / apparatus and / or one or more methods / operations / processes as described herein. For example, the one or more processors 1302 include general-purpose processors. The one or more processors 1302 may be single-core or multi-core devices. The one or more processors 1302 may include a central processing unit (CPU) or a graphics processing unit (GPU). Alternatively, the one or more processors 1302 may include dedicated processing hardware, such as a RISC processor or programmable hardware with embedded firmware. In some examples, multiple processors are included. In some embodiments, the one or more processors 1302 are part of a distributed computing system such as a cloud computing system and / or cloud computing platform.

[0094] The system / equipment includes a memory system or memory 1304, which includes working memory or volatile memory 1306. One or more processors access the volatile memory 1306 to process data and control the storage of data 1307 in the memory. The volatile memory 1306 may include any type of RAM, such as static RAM (SRAM), dynamic RAM (DRAM), or may include flash memory, such as an SD card. In some embodiments, memory 1304 and / or one or more volatile memories 1306 comprise a plurality of memories 1304 forming part of a distributed computing system such as a cloud computing system and / or a cloud computing platform.

[0095] The system / equipment includes non-volatile memory 1308. Non-volatile memory 1308 stores computer-readable instructions in the form of an operating or operating system instruction set 1309a and / or computer-readable instructions 1309b for controlling the operation of processor 1302. When executed on one or more processors 1302, these instructions cause the processor to implement the methods, processes, operations, and / or functionalities described herein. Depending on the application requirements, non-volatile memory 1308 may be any type of memory, such as read-only memory (ROM), flash memory, SD drive, magnetic drive memory, or disk drive memory. In some embodiments, non-volatile memory 1308 includes multiple non-volatile memories 1308 forming part of a distributed computing system such as a cloud computing system and / or cloud computing platform.

[0096] One or more processors 1302 are configured to execute operation instructions 1709a and / or software instructions 1309b to cause the system / device to perform any of the methods or processes described herein. Operation instructions 1309a include, for example, code related to hardware components of the system / device 1300 (i.e., drivers), and code related to the basic operation of the system / device 1300. Generally, one or more processors 1302 execute one or more of the operation instructions 1309a and / or software instructions 1309b, which are persistently or semi-persistently stored in non-volatile memory 1308, using volatile memory 1306 to temporarily store data generated during the execution of the operation instructions 1309a and / or software instructions 1309b.

[0097] In some implementations, one or more processors 1302 are connected to a network interface 1311, which includes a transmitter (TX) and a receiver (RX) for communicating with other equipment and systems over a network. In some examples, one or more processors 1302 are connected to a user interface (UI) 1310 for user or operator input to instruct or use the computing system and / or output data therefrom. In some examples, one or more processors 1302 are connected to a display 1312 for displaying output to a user or operator. At least one processor 1302, along with at least one memory 1304 and computer program code 1309a, 1309b, are arranged to cause the computing system 1300 to perform at least at least one operation, method, and / or process, e.g., as per [reference to...]. Figure 1 to Figure 12 The schematic diagram, flowchart, or operation described in any of the above and its related features is disclosed.

[0098] Figure 14 A non-transitory medium 1400 is illustrated according to some implementations. The non-transitory medium 1400 includes a computer-readable storage medium 1402 and / or an input / output mechanism 1404 to enable a computing system 1300 to access the computer-readable medium 1402. Although in this example the non-transitory medium is a USB stick, this is merely an example, and the invention is not limited thereto. Those skilled in the art will understand that the non-transitory medium 1400 can be any other type of computer-readable medium or medium, such as a CD, DVD, USB stick, Blu-ray disc, flash drive, etc., and / or any other computer-readable medium as required by the application. The non-transitory medium 1400 stores computer program code, causing the device to perform, for example, actions related to… Figure 1 to Figure 12 The flowcharts and schematic diagrams and their associated features disclose one or more of the methods, operations, or processors of any prior process.

[0099] The methods or processes described herein can be implemented as digital electronic circuit systems, integrated circuit systems, specially designed ASICs (Application-Specific Integrated Circuits), computer hardware, firmware, software, and / or combinations thereof. These may include computer program products (such as software stored on, for example, a disk, optical disk, memory, or programmable logic device) containing computer-readable instructions that, when executed by a computer, such as regarding… Figure 13 As described herein, causing the computer to perform one or more of the methods described herein.

[0100] Any system feature described herein can also be provided as a method or process feature, and vice versa. As used herein, means plus functions can alternatively be expressed according to their corresponding structures. Specifically, methodological aspects can be applied to system aspects, and vice versa.

[0101] Furthermore, any, some, and / or all features of one aspect may be applied in any suitable combination to any, some, and / or all features of any other aspect. It should also be understood that specific combinations of the various features described and defined in any aspect of this disclosure may be independently implemented and / or supplied and / or used.

[0102] Although several embodiments have been shown and described, those skilled in the art will understand that changes may be made to these embodiments without departing from the principles of this disclosure, the scope of which is defined in the claims and their equivalents.

Claims

1. A method implemented by a user equipment (UE), the method comprising: Establish a data connection between the UE and the geostationary GEO satellite; A first set of signals is transmitted between the UE and the network via the GEO satellite, wherein the transmission of the first set of signals between the UE and the network via the GEO satellite is at a first quality value; The UE requests configuration from the GEO satellite for connection to further network entities; The UE receives the configuration for connecting to further network entities from the GEO satellite; Based on the received configuration, establish further data connections between the UE and the further network entity, while maintaining the connection between the UE and the GEO satellite; as well as A second set of signals is transmitted between the UE and the network via the further network entity, wherein the transmission of the second set of signals between the UE and the network via the further network entity is at a second quality value, wherein the second quality value is higher than the first quality value.

2. The method of claim 1, further comprising: The UE determines that the amount of data to be transmitted to the network is higher than a threshold. as well as The configuration request occurs in response to determining that the amount of data to be transmitted to the network is higher than the threshold. The aforementioned configuration supports a wireless connection with higher bandwidth than the data connection between the UE and the GEO satellite.

3. The method of claim 2, wherein determining by the UE that the amount of data to be transmitted to the network is higher than a threshold includes determining that the amount of data in the UE's buffer for transmission to the network is higher than the threshold.

4. The method of claim 1, further comprising: The UE determines that the target quality value for data transmission to the network is higher than a threshold quality value; and The configuration request occurs in response to determining that the target quality value is higher than the threshold quality value, and indicates the target quality value. The configuration described above supports wireless connectivity with at least the target quality value.

5. The method of any of the preceding claims, wherein the further network entity is a low Earth orbit (LEO) satellite.

6. The method of claim 5, wherein the configuration includes ephemeris data for the LEO satellite.

7. The method of claim 6, wherein the method further comprises: The pre-calculated ephemeris data for the LEO satellite is stored in the UE's memory, and the configuration for connecting to the further network entity includes receiving corrections to the pre-calculated ephemeris data for the LEO satellite.

8. The method of any of the preceding claims, wherein the configuration includes the physical cell ID of the further network entity.

9. The method of any of the preceding claims, wherein the data connection between the UE and the GEO satellite is maintained using carrier aggregation or dual connectivity.

10. The method according to any of the preceding claims, further comprising: Receive additional configuration from the GEO satellite for connecting the UE to additional network entities; Based on the additional configuration, establish an additional data connection between the UE and the additional network entity; Terminate the data connection between the UE and the further network entity; as well as A third set of signals is transmitted between the UE and the network via the additional network entity, wherein the transmission of the third set of signals between the UE and the network via the additional network entity is at a third quality value, wherein the third quality value is higher than the first quality value.

11. The method of any of the preceding claims, wherein the data connection between the UE and the GEO satellite is established using a physical random access channel.

12. The method of any of the preceding claims, wherein the further network entity is a medium Earth orbit satellite, a satellite in a heterogeneous orbital architecture, an unmanned aerial vehicle, an aircraft, a balloon, an upper-level platform station, and / or a ground base station.

13. The method of any of the preceding claims, wherein the first quality value and the second quality value are based on one or more of the following: bandwidth; throughput; latency; quality of service; and / or delay.

14. A user equipment, comprising: One or more antennas; One or more processors; as well as A memory that stores computer-readable instructions that, when executed by the one or more processors, cause the user equipment to perform the method as described in any of the preceding claims.

15. A computer program product comprising computer-readable instructions that, when executed by a computer, cause the computer to perform the method as claimed in any one of claims 1 to 13.

16. A method implemented by a satellite, the method comprising: Maintain the satellite in geosynchronous orbit; Establish a data connection between the ground user equipment and the satellite; A first set of signals is transmitted between the ground user equipment and the network via the satellite, wherein the transmission of the first set of signals between the ground user equipment and the network via the satellite is at a first quality value; Receive a request for a higher quality connection from the network or the terrestrial user equipment; In response to receiving the request, the configuration of further network entities for supporting connections with a second quality value is transmitted to the terrestrial user equipment, wherein the second quality value is higher than the first quality value; as well as The connection between the satellite and the ground user equipment is maintained, at least in part, when the ground user equipment is connected to the further network entity.

17. The method of claim 16, wherein the further network entity is a low Earth orbit (LEO) satellite.

18. The method of claim 17, wherein the configuration includes ephemeris data for the LEO satellite.

19. The method of claim 17, wherein the configuration includes correction of pre-calculated ephemeris data for the LEO satellite stored on the ground user equipment.

20. The method of claim 16, wherein the further network entity is a medium Earth orbit satellite, a satellite in a heterogeneous orbital architecture, a drone, an aircraft, a balloon, an upper-level platform station, and / or a ground base station.

21. The method of any one of claims 16 to 20, wherein the configuration includes the physical cell ID of the further network entity.

22. The method of any one of claims 16 to 21, wherein the method further comprises: The additional network entity will provide a connection with a higher quality value than the further network entity. as well as In response to determining that the additional network entity will provide a connection with a higher quality value than the further network entity, additional configuration for the additional network entity is transmitted to the terrestrial user equipment.

23. The method of any one of claims 16 to 22, wherein a physical random access channel is used to establish the data connection between the ground user equipment and the satellite.

24. A satellite, comprising: One or more processors; as well as A memory storing computer-readable instructions that, when executed by the one or more processors, cause the satellite to perform the method according to any one of claims 16 to 23.

25. A computer program product comprising computer-readable instructions that, when executed by a computer of a satellite, cause the satellite to perform the method as described in any one of claims 16 to 23.

Images