Satellite GEO-leo overlay system for efficient mobile communications

Abstract

This specification describes systems, methods and apparatus for providing a user equipment (UE) with a means of communicating via non-terrestrial network connections. In a lower quality connected state (206), the UE communicates data with a core network via a GEO satellite. The UE or core network can request a higher quality connection. In response to such a request, the GEO satellite transmits to the UE a configuration for a further network entity, such as a 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 the higher quality session completes, the UE can transition (214) back to a lower quality connected state (206) and continue to communicate data with the core network via the GEO satellite.

Description

SATELLITE GEO-LEO OVERLAY SYSTEM FOR EFFICIENT MOBILE COMMUNICATIONSBACKGROUND

[0001] User Equipment (UE) increasingly supports the ability to connect to a core network (e.g., a 5G core network) via a non-terrestrial network (NTN). Such NTNs typically include Geostationary Earth Orbit (GEO) satellites, whose orbits maintain a fixed position relative to a position on the surface of the Earth, and Low Earth Orbit (LEO) satellites, whose orbits move relative to the surface of the earth. GEO satellites orbit at an altitude of around 36,000km, while LEO satellites typically orbit at altitudes below 2000km.SUMMARY

[0002] In a first aspect, the present disclosure provides a method performed by a user equipment, the method comprising: establishing a data connection between the UE and a geostationary earth orbit, GEO, satellite; communicating a first set of signals between the UE and a network via the GEO satellite, wherein the communication of the first set of signals between the UE and a network via the GEO satellite is at a first quality value; requesting, by the UE and from the GEO satellite, a configuration for connecting to a further network entity; receiving, by the UE and from the GEO satellite, the configuration for connecting to a further network entity; 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 communicating a second set of signals between the UE and the network via the further network entity, wherein communication of the second set of signals between the UE and a 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, the present disclosure provides a method implemented by a satellite, the method comprising: maintaining a satellite in a geosynchronous orbit; establishing a data connection between a terrestrial user equipment and the satellite; communicating a first set of signals between the terrestrial user equipmentand a network via the satellite, wherein the communication of the first set of signals between the terrestrial user equipment and a network via the satellite is at a first quality value; receiving, from the network or the terrestrial user equipment, a request for a higher quality connection; in response to receiving the request, transmitting, to the terrestrial 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 the connection between the satellite and the terrestrial user equipment at least in part while the terrestrial user equipment is connected to the further network entity.

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

[0005] The systems, methods and apparatus described herein may be implemented to realise one or more of the following advantages. By connecting to an NTN network via GEO satellite by default and using a further radio access network (RAN) entity, such a LEO satellite, only when higher quality data transmission is requested, a UE can significantly reduce its power usage when connecting via an NTN.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] FIG. 1 shows an overview of a network system with a UE, a GEO satellite and one or more LEO satellites;

[0007] FIG. 2 shows a state diagram of the UE of FIG. 1 ;

[0008] FIG. 3 shows a network diagram of the network system of FIG. 1 ;

[0009] FIG. 4 shows a high-level signalling diagram for establishing a connection between a UE and a core network via a GEO satellite;

[0010] FIG. 5A shows an overview of carrier aggregation;

[0011] FIG. 5B shows an overview of dual connectivity;

[0012] FIG. 6 shows a signalling diagram for carrier aggregation (CA) with primary cell (P-Cell) from a GEO satellite and secondary cell (S-Cell) from a LEO satellite;

[0013] FIG. 7 shows a signalling diagram for dual connectivity (DC) of a LIE to GEO satellite and LEO satellite;

[0014] FIG. 8 shows a signalling diagram for providing a Secondary Cell Group (SCG) configuration to the UE via the GEO satellite, in which the GEO satellite releases its connection to the UE before the LEO satellite is attached;

[0015] FIG. 9 shows a signalling diagram for providing an SCG configuration to the UE via the GEO satellite, in which the GEO satellite releases its connection to the UE after the LEO satellite is attached;

[0016] FIG. 10 shows a high-level signalling diagram of a connection handoff from a GEO satellite to a LEO satellite;

[0017] FIG. 11 shows a flow diagram of a method performed by a UE for connecting to a core network via a GEO satellite and a LEO satellite, or other further network entity;

[0018] FIG. 12 shows a flow diagram of a method performed by a GEO for connecting a UE to a core network via the GEO satellite and a LEO satellite, or other further network entity;

[0019] FIG. 13 shows a schematic example of a computing system / apparatus for performing any of the methods, operations or processes described herein and / or for implementing any of the systems, units and / or apparatus as described herein; and

[0020] FIG. 14 shows a non-transitory media according to some implementations.DETAILED DESCRIPTION

[0021] GEO satellites typically create large beams on the ground, i.e., have a wide coverage area or “footprint”. This can lead to GEO satellites having a limited bandwidth for network signalling. The higher orbital altitude of GEO satellites also introduces additional latency to signals that are communicated to / from a core network, e.g., a 5G core network, via GEO satellites.

[0022] By contrast, LEO satellites create narrower beams and are closer to the surface of the Earth, allowing LEO satellites to transmit signals at a lower delayand / or higher bandwidth. However, because LEO satellites are fast moving (relative to the earth’s surface) and have smaller beam footprints, UEs have to re-register and update their location frequently as they move out of the beam of one LEO satellite and into the beam of another. Furthermore, in sophisticated LEO-based systems, additional measurements and reports are used to keep the frequency and doppler stable on the ground. All of this results in additional power usage and complexity, and this can contribute to a shorter battery life of the UE.

[0023] The systems, methods and apparatus described herein aim to provide a UE with a fast and energy efficient means of communicating via NTN connections. NTNs include satellites, drones, planes, balloons, High-Altitude Platform Stations (HAPS) or the like. For simplicity, the implementations described herein will all be described with reference to satellites, in particular to GEO satellites and LEO satellites, though they can be applicable to other types of NTN too.

[0024] To address these issues, a UE maintains a connection to a GEO satellite by default, i.e. , “anchoring” the connection to the GEO satellite. The UE communicates with the core network via the GEO satellite by default, for example for control signals and / or lower quality data transfer (e.g., for data signals having a low Quality of Service Flow Indicator, QFI). Because the area of the earth’s surface covered by a spot beam from a GEO satellite (referred to as the “footprint” of the satellite, or the “spot beam coverage area”) is large and stationary relative to the earth’s surface, the UE is not required to send frequent location updates; location updates are only required when the UE travels from one GEO satellite spot beam coverage area into another. This can save power at the UE.

[0025] However, when the UE or core network requests a higher quality connection for data transfer, the GEO satellite anchor initialises a data connection between the UE and the core network to a LEO satellite covering the current location of the UE. 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 communicates data with the core network via the LEO satellite using a higher quality connection. In some examples, the UE maintains the connection with the GEO satellite concurrently with the connection to the LEO satellite, routing at least some control signals over the GEO satellite connection andat least some data signals over the LEO satellite connection. After the UE completes data transfer on the higher quality connection, or if the LEO satellite connection is lost, the UE defaults back to the GEO satellite connection, i.e., the GEO satellite connection acts an 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 a LEO satellite (or other NTN) upon request, but otherwise communicates with the core network using a lower quality connection via the GEO satellite. This reduces the power consumption of the UE, while also providing the benefits of a higher quality connection when desired.

[0027] In some implementations, Signalling Radio Bearers (SRBs) are setup over either the GEO satellite connection or the LEO satellite connection, depending on the type of SRB being transmitted. For example, the SRB1 , SRB2, and SRB3 are established through the LEO satellite connection (in addition to data radio bearers, DRBs). In some examples, SRBO is setup through the GEO satellite connection. In some implementations, a further SRB (referred to herein as SRB4) is additionally setup through the GEO satellite connection. SRB4 can be used for cell activation / deactivation signals, paging and / or TA updates (e.g., even if there is a LEO satellite connection supporting SRB1). Such an SRB4 can speed up certain dedicated control channel (DCCH) messaging. In some implementations, when the UE is connected to the GEO satellite only, both SRBs and DRBs are established via the GEO satellite.

[0028] As used herein, the term “quality” when referring to a connection can refer to any one or more measures of the quality of a connection. For example, the quality of a connection can refer to one or more Quality of Service (QoS) attributes, such as a speed / throughput, a latency (such as an end-to-end latency), a network availability, a reliability, a jitter, a bandwidth and / or whether the connection is a guaranteed bit rate (GBR) connection or a non-GBR connection. In some implementations, the quality of a connection refers to one or more QoS class identifiers (QCIs), such as 5G QoS Identifiers (5QI), of QoS flows associated with the connection.

[0029] FIG. 1 shows an overview of a network system 100. The system shows a user equipment (UE) 102, a GEO satellite 104, one or more LEO satellites 106A,106B, and, in some examples, one or more terrestrial base stations 116. In some examples, the system includes other satellite types and / or alternative types of NTN (e.g., Medium Earth Orbit (MEO) satellites, heterogenous orbit satellites, drones, HAPS, balloons, aircraft etc. - not shown). The GEO satellite 104 has a fixed, wide footprint (i.e., spot beam coverage area) 110 on the surface of the earth, typically of the order of 100km. LEO satellites 106A, 106B, each have respective footprints 112A, 112B. The footprints 112A, 112B of the LEO satellites 106A, 106B pass through the footprint 110 of the GEO satellite during the orbits of the LEO satellites. A LEO satellite footprint is typically smaller than a GEO satellite footprint.

[0030] The UE 102 registers with the GEO satellite 104 and sends location updates via the GEO satellite by default. In some implementations, registration areas are set up for the GEO satellites. In such implementations, location updates by the UE, e.g., Registration Updates, are only required when the UE 102 crosses between GEO satellite footprints (i.e., when the UE leaves the footprint of one GEO satellite and enters the footprint of another). Because GEO satellite footprints are of the order 100km in diameter, registration updates for the GEO registration areas are not required regularly, reducing power consumption of the UE 102. The GEO satellite 104 acts as an anchor for the UE 102 and manages the UE’s connections to the LEO satellites 106A, 106B and / or other network entities 116 (such as terrestrial access points or other NTNs). The UE 102 transmits and receives signals 108, such as control signals and low QoS / 5QI data signals carrying text messages and text emails, for example, to and from the core network via the GEO satellite 104.

[0031] The UE 102 can request, via the GEO satellite 104, higher quality signalling for uplink data plane signalling. In some examples, if the UE 102 is idle or inactive, the request for higher quality signalling is sent from the UE 102 to the GEO satellite 104 via the physical random-access channel (PRACH) procedure. In response, the GEO satellite 104 transmits to the UE 102 a configuration for connecting to a LEO satellite 106A that is accessible to the UE 102, i.e., a LEO satellite 106A whose footprint 112A currently covers the UE 102 location. In some examples, the configuration is transmitted to the UE 102 via a paging procedure.

[0032] If the UE 102 already has an active connection to the GEO satellite 104, the request for higher quality signalling is sent, for example, via uplink control information(UCI) or a scheduling request (SR) message. In response, the GEO satellite 104 utilizes, for example, a resource grant procedure to connect the LIE 102 to the LEO satellite 106A, e.g., using downlink control information (DCI).

[0033] The core network can also request higher quality signalling on the downlink. The request for high quality signalling (either on the uplink or downlink) is triggered, for example, based on a quantity of upcoming / buffered network traffic, a QoS Flow Identifier (QFI) of data to be transferred, a request for a higher QoS and / or a request for an additional radio bearer. Alternatively or additionally, the trigger for requesting higher quality signalling is a waning GEO satellite signal strength.

[0034] The UE 102 then establishes a connection with the LEO satellite 106A using the configuration and communicates with the core network over the higher quality connection via the LEO satellite 106A.

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

[0036] In some implementations, the ephemeris data is sent from the GEO satellite 104 to the UE 102. Alternatively, to save on the amount of data transmitted, the UE 102 can maintain sets of pre-computed ephemeris data, and the GEO satellite 104 transmits to the UE 102 modifications / corrections to the pre-computed ephemeris data, if required. Orbital characteristics of the LEO constellation will determine how long the ephemeris data is valid. Corrections can be shared for some time before needing to update the entire table. In some examples, the pre-computed ephemeris data is based on pre-computed tables of ephemeris data that are known to both the core network / NTN / RAN and the UE 102. The precomputed tables are updated regularly, e.g., daily, weekly, monthly. In some implementations, the updated ephemeris tables can be downloaded to the UE 102 when available and / or broadcastby the RAN network on a downlink (DL) broadcast channel (e.g., via a terrestrial base station 116 or the GEO satellite 104).

[0037] In some implementations, version control is used to keep track of which version of ephemeris table(s) a LIE 102 has downloaded. Alternatively or additionally, the NTN or core network can poll the UE 102 to determine the ephemeris table(s) version the UE 102 has downloaded. Based on the version currently available at the UE 102, the NTN or core network determines which (if any) corrections to the ephemeris data to send to the UE 102.

[0038] During the higher quality session with the LEO satellite 106A, the UE 102, in some implementations, maintains the connection to the GEO satellite 104, for example using Carrier Aggregation (CA) or Dual Connectivity (DC), as described herein in relation to FIGs. 6 and 7. In such situations, the GEO satellite 104 connection is used and / or preferred as an anchor carrier for at least some control and paging messages. Alternatively, the GEO satellite 104 hands off the connection to the LEO satellite completely, as described herein in relation to FIGs. 8 to 10. In such examples, the connection between the GEO satellite 104 and the UE 102 is terminated until the LEO satellite 106A hands the connection back after transmission over the higher quality connection is completed or if the higher quality connection becomes unavailable.

[0039] In some implementations, connections to LEO satellites 106 and / or other satellite systems are further based on algorithms that take into account current load on each satellite subsystem, anticipated bandwidth need, and / or priority of the application for each mobile device.

[0040] In some examples, the GEO satellite 104 and / or LEO satellite 106 operate using a bent-pipe architecture or a regenerative architecture. In a bent-pipe architecture, a satellite 104, 106 receives a signal on the uplink, amplifies the signal, converts the signal to a downlink frequency and then retransmits the signal on the downlink frequency. No, or minimal, additional processing is performed by the satellite 104, 106. In a bent pipe architecture, inter-satellite signalling is performed via ground-based satellite gateways. In a regenerative architecture, a satellite 104, 106receives a signal on the uplink, then demodulates and decodes the signal. The signal is then encoded and modulated before transmission on the downlink frequency.

[0041] In some examples, the GEO satellite 104 also remains as an anchor for a terrestrial network (TN) connection, e.g., network entity 116. Because TN connections typically support higher quality of service values, the UE 102 prioritises the TN connection over the GEO satellite connection for establishing DRBs while maintaining the GEO satellite connection. In some examples, at least some SRBs are also setup over the GEO satellite connection. If the quality of the TN connection cannot be maintained, for example at the edge of a TN coverage area, the UE 102 switches to communicating data with the core network via the GEO satellite 104, e.g. DRBs and SRBs are setup over the GEO satellite connection. If a higher quality connection is requested by the UE 102 or the core network than is provided by the GEO satellite 104, the GEO satellite 104 provides a configuration for a LEO satellite 106 connection, as described herein. In this manner, a hierarchy of connections is established, with a TN connection being prioritised for data transfer with the GEO satellite used as an anchor. The GEO satellite connection is used as a lower quality connection for data transfer when the terrestrial network is unavailable, unstable, and / or cannot provide a target QoS level. The LEO satellite connection is used when a performance boost to the GEO satellite connection is required.

[0042] FIG. 2 shows an example state diagram of a UE. The state diagram shows examples of three states of the UE: an inactive state 202; a lower quality connected state 206; and a higher quality connected state 208. The state diagram indicates which subsystem (e.g., a GEO satellite or LEO satellite) the UE is attached to for data transfer in brackets for each state.

[0043] In the inactive state 202, the UE maintains a connection with the GEO satellite. The inactive state corresponds, in some examples, to an RRCJnactive, e.g. a state in which there is no, or very little, data transmission between the UE and the GEO satellite, but in which the RRC entity is not completely released and the non- access stratum (NAS) layer is maintained. In some examples, the inactive state corresponds to a connected mode discontinuous reception (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 core network requests lowerquality communication, the UE initiates 204 a lower quality session and enters a lower quality connected state 206, during which the UE communicates data with the core network via the GEO satellite. After the lower quality session is complete, the UE can transition (state 208) back to the inactive state 202.

[0044] While in the lower quality connected state 206, the UE or the core network can request a higher quality connection, for example to transmit data at a higher bandwidth and / or with a lower latency, support a higher QoS or the like. In response to such a request, the GEO satellite transmits to the UE a configuration for a LEO satellite, for example as described in relation to FIG. 1 and / or FIGs. 4 to 9. 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 LEO satellite. After the higher quality session completes, the UE can transition 214 back to a lower quality connected state 206 and continue to communicate data with the core network via the GEO satellite.Alternatively, if there is currently no further data for communication by the UE or core network, the UE can transition 216 back to the inactive state 202.

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

[0046] FIG. 3 shows a network diagram. The network 300 has a UE 302, a GEO satellite gateway (GEO-GW) 304, a LEO satellite gateway (LEO-GW) 306 (or another NTN gateway), a core network 308 (5GC) and a terrestrial gNodeB (gNB) 310. The GEO-GW 304 facilitates communication between the core network 308 and a GEO satellite, e.g., receives signals from the core network 308 and transmits them to the GEO satellite, and receives signals from the GEO satellite and transmits them to the core network 308. The LEO-GW 306 facilitates communication between the core network 308 and a LEO satellite, e.g., receives signals from the core network 308 and transmits them to the LEO satellite, and receives signals from the LEO satellite and transmits them to the core network 308.

[0047] The UE 302 maintains a wireless anchoring connection with the GEO-GW 304 for the signalling of at least some control plane signals 312. When the UE 302 isconnected to the core network 308 solely via the GEO-GW 304, all control plane signals 312 (e.g. SRBs) and data signals 314 (e.g. DRBs) are established to the LIE 302 via the GEO-GW 304. When the UE 302 is connected to the core network 308 via one or more gateways (e.g. a LEO-GW 306 and / or a terrestrial gNB 310) in addition to the GEO-GW 304, at least some control plane signals 312 are communicated with the core network 308 via the GEO-GW 304 and at least some data signals 316, 318 are communicated with the core network via the additional connection, e.g. at least some DRBs 314, 316 are setup over the additional connection. In some implementations, all control plane signals 312 are communicated with the core network 308 via the GEO-GW 304. Alternatively, a proper subset of control plane signals 312 are communicated with the core network 308 via the GEO-GW 304, and other control plane signals (not shown) are communicated with the core network 308 via the additional connection. For example, SRB0 and / or SRB4 are communicated with the core network 308 via the GEO-GW 304 and SRB1 , SRB2 and / or SRB3 communicated with the core network 308 via the LEO-GW 306 and / or terrestrial gNB 310.

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

[0049] FIG. 4 shows a high-level signalling diagram for establishing a connection between a UE 402 and a core network 408 via a GEO satellite. The UE 402 initially connects to the GEO satellite gateway 404 (GEO-GW) via a GEO satellite. In response to a request for a higher quality connection, the GEO-GW 404 directs the UE 402 to connect to a LEO gateway 406 (LEO-GW) via a LEO satellite using a configuration supplied by the GEO satellite.

[0050] Initially, the core network 408 transmits network configuration information 410 to the GEO satellite via the GEO satellite gateway 404 and transmits networkconfiguration information 412 to the LEO satellite via the LEO satellite gateway 406. The GEO-GW 404 transmits the configuration information 410 to the GEO satellite, which broadcasts 414 configuration information throughout the spot beam / cell of the GEO satellite. When in the spot beam, the UE 402 receives the broadcast 414 containing the configuration information for the UE 402 to connect to the GEO satellite. The UE 402 uses the configuration information in the cell broadcast 414 to attach 416, 418 to the core network 408 via the GEO satellite and the GEO-GW 404. Following network attachment 416, 418, the UE 402 and core network 408 communicate data signals 420, 422 via the GEO satellite and the GEO-GW 404. Both data signals and control signals are communicated between the core network 408 and UE 402 via the GEO-GW 404 and GEO satellite.

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

[0052] In some examples, the one or more of the threshold conditions for the core network 408 and / or UE 402 are based on a target connection quality for transmission of a set of signals exceeding one or more threshold connection quality values. For example, a target connection quality can include one or more of: a target QoS (for example, as indicated by the QoS Flow Indicator, QFI, of one or more packets for transmission), a target latency, a target bandwidth, a target error rate and / or the like. The one or more threshold connection quality values include, for example, a threshold bandwidth, a threshold latency, a threshold QoS and / or the like. In some examples, one or more threshold values are based on capabilities of the GEO satellite, e.g., a maximum bandwidth available to the GEO satellite, a maximum QoS that can be provided by the GEO satellite, and / or a minimum delay that can be provided by the GEO satellite. Alternatively or additionally, the higher qualityconnection request is triggered in response to a request for an additional radio bearer.

[0053] In addition to the common threshold conditions previously described, 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 a quantity of data for transmission from the core network 408 to the LIE 402 (i.e., on the downlink). An example of a threshold condition is that the quantity of data for transmission to the UE 402 is above a threshold value, e.g., one or more files for transmission to the UE 402 has a size above a threshold value.

[0054] In addition to the common threshold conditions previously described, in some examples, one or more of the threshold conditions for the UE 402 (i.e., UE-side threshold conditions) include one or more conditions based on a quantity of data for transmission to the core network 408 from the UE 402 (i.e., on the uplink). For example, a threshold condition is that the quantity of data for transmission to the core network 408 is above a threshold value, e.g., the amount of data in a buffer for transmission to the core network 408 is above a threshold value and / or one or more files for transmission to the core network 408 has a size above a threshold value.

[0055] In response to receiving a high-quality connection request 424, 426 and as part of establishing a LEO connection 424, the GEO satellite transmits configuration information for a LEO satellite connection to the UE 402. The UE 402 uses the configuration to establish a connection 424 to the LEO satellite while maintaining the connection to the GEO satellite, i.e., there is a concurrent connection between the UE 402 and both the GEO satellite and LEO satellite. Examples of establishing a connection 424 with a LEO satellite are described below in relation to FIGs. 6-10.

[0056] The UE 402 subsequently communicates data signals with the core network 408 via the LEO satellite, e.g., at least some DRBs are setup via the LEO satellite. At least some control signals are still communicated via the GEO satellite connection, e.g., at least some SRBs, such as SRB0 and / or SRB4 are setup via the GEO satellite connection. In some implementations, data signals are communicated via either the GEO satellite connection or LEO satellite connection in dependence on a QFI associated with the data signals, e.g. data signals with a QFI corresponding to ahigher QoS (i.e. above a threshold QoS) are setup over the LEO satellite connection, while data signals with a QFI corresponding to a lower QoS (i.e. below a threshold QoS) are setup over the GEO satellite connection.

[0057] The concurrent connection between the LIE 402 and the LEO satellite, and the UE 402 and the GEO satellite is, in some examples, based on a carrier aggregation (CA) protocol or a dual connectivity (DC) protocol, or both. Other methods known in the art can be used for maintaining a concurrent connection between the UE 402 and both the LEO satellite and the GEO satellite.

[0058] An example of a CA protocol is shown in FIG. 5A. Carrier aggregation (CA) is a connection mode in which a UE 502 uses multiple component carriers 550A, 550B to transmit and / or receive data traffic 552, operating over multiple frequencies at the same time. One carrier is designated as a primary cell (P-Cell), over which radio resource control (RRC) layer communications are communicated. Traffic 552 is split between carriers in the Medium Access Control (MAC) layer 554 of the protocol. In the example shown, CA uses a single base station 556, but in general multiple base stations can be used. As described herein in relation to FIG. 6, a GEO satellite / GEO-GW acts as a P-Cell for the connection between a UE 502 and a core network, with a LEO satellite / LEO-GW (or other NTN) acting as a secondary cell (S- Cell).

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

[0060] FIG. 6 shows a signalling diagram for carrier aggregation (CA) primary cell (P-Cell) from a GEO satellite 604 and secondary cell (S-Cell) from a LEO satellite 606. In response to receiving a request for a higher quality connection 624, 626(similar to 424, 426) the GEO-GW 604 starts to establish a CA connection 628 (similar to 428) with the LEO-GW 606 supporting an S-Cell. To this purpose, the GEO-GW 604 requests 630 S-Cell configuration information from the LEO-GW 606. The LEO-GW 606 responds 632 with S-Cell configuration information for the UE 602. The GEO-GW 604 then forwards 634 the S-Cell configuration information to the UE 602 via the GEO satellite. The UE 602 responds with a confirmation 636 that the S-cell configuration information has been received, which the GEO-GW 504 forwards 638 to the core network 608.

[0061] After receiving confirmation 638 that the S-cell configuration information has been received by the UE 602, the core network 608 transmits an S-Cell activation signal 640 to the GEO-GW 604, which forwards the S-Cell activation signal 642 to the UE 602 via the GEO satellite. Upon receipt of the S-Cell activation signal 642, the UE 602 establishes a connection to the LEO-GW 606 via the LEO satellite using an S- Cell Random Access Channel (RACH) 644, while maintaining the connection to the GEO-GW 604 via the GEO satellite as an anchor. The UE 602 and core network 608 then communicate data signals 646, 648 via the LEO-GW 606 and LEO satellite, i.e., DRBs are setup via the LEO satellite. At least some control signals are communicated between the core network 608 and the UE 602 over the GEO-satellite connection, e.g. at least some SRBs are setup via the GEO satellite.

[0062] FIG. 7 shows a signalling diagram for a dual connectivity (DC) of a UE to GEO satellite and a LEO satellite. In response to receiving a request for a higher quality connection 724, 726, (similar to 424, 426) the GEO-GW 704 starts to establish a DC connection 728 (similar to 428) with the LEO-GW 706 as a secondary node. To this end, the GEO-GW 706 transmits a request 750 for Secondary Cell Group (SCG) Configuration data to a LEO-GW 706 of a LEO satellite that is within the footprint of the GEO satellite associated with the 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, a LEO ephemeris function / sever (not shown) stores current LEO ephemeris tables and distribute them to the rest of the network (i.e., through the TN / NTN), e.g., on demand, whenever the ephemeris tables are updated and / or periodically. Updated LEO ephemeris tables are, for example, broadcast through thenetwork (i.e., the TN / NTN) to UEs 702. 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 updates (if any) to send to the UE 702. In some examples, the LEO ephemeris function uses this tracking data to determine whether to send a full updated ephemeris table to the UE 702 or a set of changes to the current version of the ephemeris tables that is stored on the UE 702.

[0064] The GEO-GW 704 transmits the LEO ephemeris data 754 and the received SCG Configuration / Addition information 756 (from message 730) to the UE 702 via the 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] The UE 702 uses the LEO ephemeris data 754 and SCG Configuration / Addition information 756 to establish an additional connection 746, 748 to the core network 708 via the LEO satellite and LEO-GW 704. The LEO satellite 706 then acts a SCG for the data connection. Traffic can be prioritized on each link based on a target quality, e.g., data associated with a higher target quality is routed over the LEO satellite link, and data associated with a lower target quality is routed over the GEO satellite link (concurrently). At least some control signals are routed over the GEO satellite link.

[0066] Each carrier can be independently managed to account for the timing, e.g., each base station / gateway handles its respective data stream independently. Cross carrier scheduling is used in some examples. PDCP layer or MAC layer splits can be used to account for the different latency and bandwidth capabilities of each carrier.

[0067] FIG. 8 shows a variation of the signalling diagram in FIG. 7 in which the GEO satellite releases its connection to the UE 802 between providing a configuration for the LEO connection and the LEO connection being established. The signalling follows the same procedure as described in FIG. 7 up to the broadcast of the LEO ephemeris data 854 and transmission of the cell reconfiguration data 856 from the GEO satellite (i.e., operations 824-856 correspond to operations 724-756 of FIG. 7). Following broadcast of the LEO ephemeris data 854 and transmission of cell reconfiguration data 856, the UE 802 releases 858 the connection between the GEOsatellite and the UE 802. The LIE 802 then attaches (operations 846, 848) to the core network 808 via the LEO-GW 806 and LEO satellite using the LEO ephemeris data 854 and the cell reconfiguration data 856.

[0068] FIG. 9 shows a variation of the signalling diagram in FIG. 7 in which the GEO satellite maintains its connection to the UE 902 after providing configuration data for the LEO satellite connection until the UE is attached to the LEO-GW via the LEO satellite. The GEO-GW 904 then releases 958 its connection to the UE 902. The signalling follows the same procedure as described in FIG. 7 up to the attachment 936, 938 of the UE 902 to the core network 908 via the LEO satellite and LEO-GW 906 (i.e., operations 924-948 correspond to operations 724-748 of FIG. 7). Following the attachment 946, 988 of the UE 902 to the core network 908 via the LEO satellite and LEO-GW 906, the UE 902 releases 958 the connection between the GEO satellite and the UE 902.

[0069] FIG. 10 shows a high-level signalling diagram of a connection handoff, e.g., a handover or a reconfiguration with sync, from a GEO satellite to a LEO satellite. In response to a request for a higher quality connection 1026, 1027 from the UE 1002 or a determination by the core network 1008 that a higher quality connection is desired, the core network 1008 sends a LEO handoff command 1060 to the GEO satellite via the GEO-GW 1004. The GEO satellite forwards the LEO handoff command 1062 to the UE 1002. The handoff command 1062 includes a configuration for connecting to the LEO-GW 1006 via a LEO satellite. Receipt of the handoff command 1062 by the UE 1002 triggers the UE 1002 to connect 1064 to the LEO- GW 1006 via a LEO satellite using the configuration supplied in the handoff command 1062. After establishing the connection between the UE 1002 and the LEO GW 1006, the LEO satellite sends a connection confirmation 1066 to the core network 1008. The core network 1008 and UE 1002 then communicate using a higher quality connection 1068, 1070 via the LEO satellite and the LEO-GW 1006.

[0070] FIG. 11 shows a flow diagram of an example method for communicating in a network. The method can be performed by a UE, such as the UE described in relation to FIGs. 1 and 13. In some implementation, the method corresponds at least in part to any one or more of the methods described herein with respect to FIG. 4 and FIGs. 6-10.

[0071] At operation 1116, the UE and GEO satellite establish a connection. In some implementations, operation 1116 can correspond to operations 410 to 418 of FIG. 4. The connection provides a data plane, over which data is provided to and from the UE (e.g., over which DRBs are setup), and a control plane, used for network signalling (e.g., over which SRBs are setup). The connection between the UE and the GEO satellite can be established using any method known in the art, for example, using a 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 the GEO satellite. The first set of signals can correspond to data signals 420, 422 of FIG. 4. The first set of signals includes signals that are communicated over the data plane of the connection, e.g., DRBs. The first set of signals further includes, in some examples, control signals communicated in a control plane, e.g., SRBs. Communication of the first set of signals between the UE and a network via the GEO satellite is at a first quality value.

[0073] The term “quality value” refers to a measure of the quality of a connection between the UE and the network. As an example, the quality measure includes one or more of: a bandwidth of the connection, a throughput of the connection, a latency of the connection, a QoS or QFI of the connection, or the like.

[0074] In some implementations, the first set of signals includes small files / messages with QoS or QFI achieving a threshold criterion, such as text messages or emails, and / or data signals that are do not require a low latency connection. The QoS or QFI threshold criterion could be a specific subset of QoS or QFI values that a GEO satellite can support.

[0075] At operation 1126, the UE requests, from the GEO satellite, a configuration for connecting with a further network entity. The request can correspond to signals 426 of FIG. 4 and signals 626, 726, 826, 926, 1026 of FIGs. 6-10. In some examples, the UE sends the request in response to determining that one or more threshold conditions in a set of one or more threshold conditions are satisfied. The request is, for example, communicated in the control plane of the connection between the UE and the GEO satellite, e.g., via an SRB. Alternatively or additionally, a request for a configuration for connecting with the further network entity can originate from the corenetwork, based on the network determining that one or more threshold conditions in a set of one or more network-side threshold conditions are satisfied. Examples of UE- side and network-side threshold conditions are described herein with reference to FIG. 4, in particular with reference to elements 424, 426 of FIG. 4.

[0076] The further network entity is a network entity that supports a higher quality connection to the network than the GEO satellite. The further network entity is, for example, a LEO satellite. Alternatively, the further network entity is a medium Earth orbit satellite, a satellite in a heterogenous orbital architecture, a drone, an aircraft, a balloon and / or a terrestrial base station.

[0077] At operation 1132, the UE receives, from the GEO satellite, a configuration for connecting to a further network entity. The configuration data can, for example, include the S-cell configuration 632 of FIG. 6, the LEO ephemeris data 754, 854, 954 and / or SCG Configuration 756, 856, 956 of FIGs. 7-9, and / or the handoff command 1062 of FIG. 10. The configuration data supports a wireless connection with the further entity that has a higher quality than the UE-GEO satellite connection. The configuration includes, for example, the Physical Cell ID of the LEO satellite, a carrier frequency, a reference location, and / or a distance threshold.

[0078] The configuration data additionally includes, in some examples, ephemeris data for connecting to a satellite, e.g., a LEO satellite. In some examples, the configuration data includes a full set of ephemeris data. Alternatively, the configuration data includes corrections to a set of pre-computed ephemeris data stored on the UE. The core network maintains a record of the version of the ephemeris data stored on the UE and determine which updates (if any) to send to the UE as part of the configuration data.

[0079] At operation 1146, the UE establishes a further data connection between the UE and the further network entity based on the configuration, while maintaining the connection between the UE and the GEO satellite. Operation 1146 can correspond to the attach operations 646, 746, 846, 946, 1068 of FIGs. 6-10. The data connection is a connection over which signals in the data plane are communicated, e.g., over which DRBs are setup.

[0080] The connection between the GEO satellite and the UE is used for the communication of at least some control signals in the control plane (i.e. one or more SRBs are setup via the GEO satellite), e.g., for establishing and / or tearing down connections between the UE and one or more further network entities. In some implementation, all SRBs are setup via the GEO satellite connection (e.g., SRBO- SRB3 and, if used, SRB4). Alternatively, a proper subset of SRBs (e.g., SRBO and / or SRB4) are setup over the GEO satellite connection. The concurrent connections between the GEO satellite and UE, and the LEO satellite and UE are, in some examples, maintained using carrier aggregation (CA) and / or dual connectivity (DC).

[0081] At operation 1180, the UE communicates a second set of signals with the network via the 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 additionally includes a proper subset of control signals (e.g. SRBO, SRB1 , SRB2 and / or SRB3). Communication of the second set of signals between the UE and a core network via the further network entity is at a second quality value that is higher than the first quality value, e.g., at a higher bandwidth, a higher QoS and / or a lower latency. The second set of signals comprise, 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, all data signals are setup via the further network entity when a connection to the further network entity is present, and the GEO satellite is used only for control signals. In some implementations, data signals are routed over the further network entity connection or GEO satellite connection in dependence on a QoS flow ID (QFI) associated with the data signals. 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 a hand-off from the further network entity to an additional network entity, e.g., from a first LEO satellite to a second LEO satellite. The UE receives, from the GEO satellite, an additional configuration for connecting the UE to an additional network entity. In someimplementations, the GEO satellite transmits the additional configuration in response to a determination (e.g., by the core network or UE) that the UE is moving out of the coverage area of the further network entity, due to movement of the UE and / or movement of the further network entity. Alternatively or additionally, the GEO satellite transmits the additional configuration in response to a determination (e.g., by the network or UE) that that second quality value has deteriorated to below a threshold value and / or that 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 to the GEO satellite for the additional configuration data. The request to the GEO satellite for the additional configuration data can also originate from the network.

[0084] In response to receiving the 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 set of signals are communicated between the UE and the network via the additional network entity at a third quality value that is higher than the first quality value. The third set of signals are, in some examples, be of the same type(s) as the second set of signals.

[0085] FIG. 12 shows of an example method for facilitating communication with a network by a UE. The method is performed by a GEO satellite. In some implementation, the method corresponds at least in part to any one or more of the methods described herein with respect to FIG. 4 and FIGs. 6-10.

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

[0087] At operation 1216, a UE and the GEO satellite establish a connection. In some implementations, operation 1216 can correspond to operations 410 to 418 of FIG. 4. The connection provides a data plane, over which data is provided to and from the UE (e.g. DRBs), and a control plane, used for network signalling (e.g. SRBs). The connection between the UE and the GEO satellite can be establishedusing any method known in the art, for example, using a physical random-access channel (PRACH).

[0088] At operation 1222, a core network (e.g. a 5G core network) and the UE communicate a first set of signals across the connection, i.e., via the GEO satellite. The first set of signals can correspond to data signals 420, 422 of FIG. 4. Communicating the first set of signals is described in further detail with respect to operation 1122 of FIG. 11 .

[0089] At operation 1226, the GEO satellite receives, from the UE or a core network, a request for a higher quality connection. When the request originates from the core network, the request can correspond to signals 424 of FIG. 4 and signals 624, 724, 824, 924, 1024 of FIGs. 6-10. When the request originates from a UE, the request can correspond to signals 426 of FIG. 4 and signals 626, 726, 826, 926, 1026 of FIGs. 6-10. In some examples, the UE / network sends the request in response to determining that one or more threshold conditions in a set of one or more threshold conditions are satisfied. Any of the threshold conditions described herein may be used, for example as described in relation to FIG. 10. The request is, in some examples, communicated in the control plane of the connection between the UE / network and the GEO satellite, e.g., via an SRB. Examples of requesting a higher quality connection are described herein in further detail with respect to operation 1126 of FIG. 11.

[0090] At operation 1232, the GEO satellite transmits, to the UE, a configuration for a further network entity supporting a connection with a second quality value. The second quality value is higher than the first quality value. The configuration data can, for example, include the S-cell configuration 632 of FIG. 6, the LEO ephemeris data 754, 854, 954 and / or SCG Configuration 756, 856, 956 of FIGs. 7-9, and / or the handoff command 1062 of FIG. 10. Examples of transmitting a configuration are described herein in further detail with respect to operation 1132 of FIG. 11.

[0091] At operation 1290, the GEO satellite maintains, at least in part, a connection between the satellite and the terrestrial user equipment while the terrestrial user equipment is connected to the further network entity. The connection can be maintained using call aggregation and / or dual connectivity, for example as describedherein with respect to FIGs. 6 and 7, though the skilled person will appreciate that alternative methods of maintaining multiple connections can alternatively be used. The connection between the GEO satellite and the UE is used for the communication of at least some control signals in the control plane, e.g., for establishing and / or tearing down connections between the UE and one or more further network entities.

[0092] Figure 13 illustrates a schematic example of a computing system / apparatus 1300 for performing any of the methods, operations or processes described herein and / or for implementing any of the systems, units and / or apparatus as described herein. The computing system / apparatus 1300 shown is an example of a computing device or platform. It will be appreciated by the skilled person that other types of computing devices / systems / platforms can alternatively be used to implement the methods described herein, such as a distributed computing system. The computing system / apparatus 1300 is, in some examples, a UE, a subsystem of a UE, and / or a subsystem of a satellite.

[0093] The apparatus (or system) 1300 comprises one or more processors 1302 (e.g., CPUs). The one or more processors 1302 control operation of other components of the system / apparatus 1300. The system / apparatus 1300 can be part of a computing device, computing system, distributed computing system, cloud computing platform and the like for implementing the functionality of the systems / apparatus and / or one or more methods / operations / processes as described herein. The one or more processors 1302 , for example, include a general-purpose processor. The one or more processors 1302 can be a single core device or a multiple core device. The one or more processors 1302 can include a Central Processing Unit (CPU) or a graphical processing unit (GPU). Alternatively, the one or more processors 1302 include specialized processing hardware, for instance 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 / apparatus comprises memory system or memory 1304 including a working or volatile memory 1306. The one or more processors access the volatile memory 1306 in order to process data and control the storage of data 1307 inmemory. The volatile memory 1306 can include RAM of any type, for example, Static RAM (SRAM), Dynamic RAM (DRAM), or include Flash memory, such as an SD- Card. In some embodiments, the memory 1304 and / or one or more volatile memories 1306 include a plurality of memories 1304 forming part of the distributed computing system such as the cloud computing system and / or cloud computing platform and the like.

[0095] The system / apparatus comprises a non-volatile memory 1308. The nonvolatile memory 1308 stores a set of operation or operating system instructions 1309a for controlling the operation of the processors 1302 in the form of computer readable instructions and / or software instructions 1309b in the form of computer readable instructions, which when executed on the one or more processors 1302 cause the processors to implement the methods, processes, operations and / or functionality described herein. The non-volatile memory 1308 can be a memory of any kind such as a Read Only Memory (ROM), a Flash memory, SD drive, a magnetic drive memory or magnetic disc drive memory and the like as the application demands. In some embodiments, the non-volatile memory 1308 includes a plurality of non-volatile memories 1308 forming part of the distributed computing system such as the cloud computing system and / or cloud computing platform and the like.

[0096] The one or more processors 1302 are configured to execute operating instructions 1709a and / or software instructions 1309b to cause the system / apparatus to perform any of the methods or processes described herein. The operating instructions 1309a include, for example, code (i.e. , drivers) relating to the hardware components of the system / apparatus 1300, as well as code relating to the basic operation of the system / apparatus 1300. Generally speaking, the one or more processors 1302 execute one or more instructions of the operating instructions 1309a and / or software instructions 1309b, which are stored permanently or semipermanently in the non-volatile memory 1308, using the volatile memory 1306 to store temporarily data generated during execution of said operating instructions 1309a and / or software instructions 1309b.

[0097] In some implementations, the one or more processors 1302 are connected to a network interface 1311 including a transmitter (TX) and a receiver (RX) for communicating over a network with other apparatus and systems. The one or moreprocessors 1302 are, in some examples, connected with a user interface (Ul) 1310 for user or operator input for instructing or using the computing system and / or for outputting data therefrom. The one or more processors 1302 are, in some examples, connected with a display 1312 for displaying output to a user or operator. The at least one processor 1302, with the at least one memory 1304 and the computer program code 1309a, 1309b are arranged to cause the computing system 1300 to at least perform at least the operations, methods, and / or processes, for example as disclosed in relation to the schematic diagrams, flow diagrams or operations as described with any of figures 1 to 12 and related features thereof.

[0098] FIG. 14 shows a non-transitory medium 1400 according to some implementations. The non-transitory medium 1400 includes a computer readable storage medium 1402 and / or input / output mechanism 1404 for enabling a computing system 1300 to access said computer-readable medium 1402. Although in this example the non-transitory medium is USB stick, this is by way of example only and the invention is not so limited, the skilled person would appreciate the non-transitory media 1400 could be any other type of computer readable media or medium such as, for example, a CD, a DVD, a USB stick, a blue ray disk, flash drive etc. and / or any other computer readable medium as the application demands. The non-transitory medium 1400 stores computer program code, causing an apparatus to perform one or more of the methods, operations, processors of any preceding process for example as disclosed in relation to the flow diagrams and schematic diagrams of figures 1 to 12 and related features thereof.

[0099] Implementations of the methods or processes described herein may be realized as in digital electronic circuitry, integrated circuitry, 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 e.g., magnetic discs, optical disks, memory, Programmable Logic Devices) comprising computer readable instructions that, when executed by a computer, such as that described in relation to Figure 13, cause the computer to perform one or more of the methods described herein.

[0100] Any system feature as described herein may also be provided as a method or process feature, and vice versa. As used herein, means plus function featuresmay be expressed alternatively in terms of their corresponding structure. In particular, method aspects may be applied to system aspects, and vice versa.

[0101] Furthermore, any, some and / or all features in one aspect can be applied to any, some and / or all features in any other aspect, in any appropriate combination. It should also be appreciated that particular combinations of the various features described and defined in any aspects of the disclosure can be implemented and / or supplied and / or used independently.

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

Claims

WHAT IS CLAIMED IS:1 . A method implemented by a user equipment, UE, the method comprising: establishing a data connection between the UE and a geostationary earth orbit, GEO, satellite; communicating a first set of signals between the UE and a network via the GEO satellite, wherein the communication of the first set of signals between the UE and a network via the GEO satellite is at a first quality value; requesting, by the UE and from the GEO satellite, a configuration for connecting to a further network entity; receiving, by the UE and from the GEO satellite, the configuration for connecting to a further network entity; 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 communicating a second set of signals between the UE and the network via the further network entity, wherein communication of the second set of signals between the UE and a 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: determining, by the UE, that an amount of data to be transferred to the network is above a threshold value; and wherein the requesting the configuration occurs in response to determining that the amount of data to be transferred to the network is above the threshold value, and wherein the configuration supports a wireless connection with a 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 an amount of data to be transferred to the network is above a threshold value comprises determining that an amount of data for transfer to the network in a buffer of the UE is above a threshold value.

4. The method of claim 1 , further comprising: determining, by the UE, that a target quality value for a data transmission to the network is above a threshold quality value; and wherein the requesting the configuration occurs in response to determining that the target quality value is above the threshold quality value and indicates the target quality value, and wherein the configuration supports a wireless connection with at least the target quality value.

5. The method of any preceding claim, wherein the further network entity is a low earth orbit, LEO, satellite.

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

7. The method of claim 6, wherein the method further comprises: storing pre-computed ephemeris data for the LEO satellite in a memory of the UE, and wherein receiving the configuration for connecting to the further network entity comprises receiving corrections to the pre-computed ephemeris data for the LEO satellite.

8. The method of any preceding claim, wherein the configuration comprises a physical cell ID of the further network entity.

9. The method of any preceding claim, wherein the data connection between the UE and the GEO satellite is maintained using Carrier Aggregation or Dual Connectivity.

10. The method of any preceding claim, further comprising:receiving, from the GEO satellite, an additional configuration for connecting the UE to an additional network entity; establishing an additional data connection between the UE and the additional network entity based on the additional configuration; terminating the data connection between the UE and the further network entity; and communicating a third set of signals between the UE and the network via the additional network entity, wherein communication of the third set of signals between the UE and a 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 preceding claim, wherein the establishing the data connection between the UE and the GEO satellite uses a physical random-access channel.

12. The method of any preceding claim, wherein the further network entity is a medium Earth orbit satellite, a satellite in a heterogenous orbital architecture, a drone, an aircraft, a balloon, a high-altitude platform station, and / or a terrestrial base station.

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

14. A user equipment comprising: one or more antennae; one or more processors; and a memory, the memory storing computer readable instructions that, when executed by the one or more processors, cause the user equipment to perform the method of any preceding claim.

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

16. A method implemented by a satellite, the method comprising: maintaining the satellite in a geosynchronous orbit; establishing a data connection between a terrestrial user equipment and the satellite; communicating a first set of signals between the terrestrial user equipment and a network via the satellite, wherein the communication of the first set of signals between the terrestrial user equipment and a network via the satellite is at a first quality value; receiving, from the network or the terrestrial user equipment, a request for a higher quality connection; in response to receiving the request, transmitting, to the terrestrial 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 the connection between the satellite and the terrestrial user equipment at least in part while the terrestrial 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 comprises ephemeris data for the LEO satellite.

19. The method of claim 17, wherein the configuration comprises corrections to precomputed ephemeris data for the LEO satellite stored on the terrestrial user equipment.

20. The method of claim 16, wherein the further network entity is a medium Earth orbit satellite, a satellite in a heterogenous orbital architecture, a drone, an aircraft, a balloon, a high-altitude platform station, and / or a terrestrial base station.21 . The method of any of claims 16 to 20, wherein the configuration comprises a physical cell ID of the further network entity.

22. The method of any of claims 16 to 21 , wherein the method further comprises: determining that an additional network entity would provide a connection with a higher quality value than the further network entity; and in response to determining that the additional network entity would provide connection with a higher quality value than the further network entity, transmitting, to the terrestrial user equipment, an additional configuration for the additional network entity.

23. The method of any of claims 16 to 22, wherein the establishing the data connection between a terrestrial user equipment and the satellite uses a physical random-access channel.

24. A satellite comprising: one or more processors; and a memory, the memory storing computer readable instructions that, when executed by the one or more processors, cause the satellite to perform a method according to any 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 of any of claims 16 to 23.

Images