ELECTRONIC DEVICE, INFRASTRUCTURE EQUIPMENT AND METHOD

Abstract

An electronic device (UE) comprising circuitry configured to compensate feeder link influence on the common TA (T.sub.com) in a transparent payload non-terrestrial network (NTN) configuration with a non-terrestrial network component (NT-RN) and an infrastructure equipment (gNB) tethered by the non-terrestrial network component (NT-RN).

Claims

1. An electronic device comprising circuitry configured to compensate feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and an infrastructure equipment tethered by the non-terrestrial network component.

2. The electronic device of claim 1 in which the circuitry is configured to absorb changes in a feeder link propagation time as part of a UE-specific differential TA.

3. The electronic device of claim 1 in which the circuitry is configured to repeatedly adjust a UE-specific differential TA to take account of a changing distance between the non-terrestrial network component and the infrastructure equipment.

4. The electronic device of claim 1, in which the circuitry is configured to receive information on the ephemeris of the non-terrestrial network component and a location of the infrastructure equipment, and to repeatedly calculate a distance between the non-terrestrial network component and the infrastructure equipment based on this information.

5. The electronic device of claim 1, in which the circuitry is configured to receive information on the ephemeris of the non-terrestrial network component and an initial distance between the infrastructure equipment and the non-terrestrial network component, and to repeatedly calculate a distance between the non-terrestrial network component and the infrastructure equipment based on this information.

6. The electronic device of claim 1, in which the circuitry is configured to receive information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component once the electronic device enters RRC connected mode and/or shortly after feeder link switching occurs.

7. The electronic device of claim 1, in which the circuitry is configured to receive information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component in encrypted form.

8. The electronic device of claim 1, in which the circuitry is configured to repeatedly receive a current TA adjustment and to adjust a common TA according to this TA adjustment.

9. The electronic device of claim 1, in which the circuitry is configured to repeatedly determine a current TA adjustment according to a TA drift figure and its direction and to adjust a common TA according to this TA adjustment.

10. The electronic device of claim 1, in which the TA drift figure and its direction includes both the drift due to the satellite movement in its orbit and also its changing displacement from the tethered infrastructure equipment.

11. The electronic device of claim 1, in which the circuitry is configured to receive the TA drift figure and its direction as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by regular MAC messages.

12. (canceled)

13. An infrastructure equipment comprising circuitry configured to provide information to a user equipment for compensating feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and a base station tethered by the non-terrestrial network component.

14. The infrastructure equipment of claim 13 in which the circuitry is configured to send to the user equipment information on the ephemeris of the non-terrestrial network

15. The infrastructure equipment of claim 13 in which the circuitry is configured to send to the user equipment information on the location of the infrastructure equipment tethered by the non-terrestrial network component.

16. The infrastructure equipment of claim 13 in which the circuitry is configured to send to the user equipment information on an initial distance between the infrastructure equipment and the non-terrestrial network component.

17. The infrastructure equipment of claim 13 in which the circuitry is configured to send to the user equipment information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component once the electronic device enters RRC connected mode and/or shortly after feeder link switching occurs.

18. The infrastructure equipment of claim 13 in which the circuitry is configured to send to the user equipment information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component in encrypted form.

19. The infrastructure equipment of claim 13 in which the circuitry is configured to repeatedly send to the user equipment a current TA adjustment.

20. The infrastructure equipment of claim 13 in which the circuitry is configured to send to the user equipment a TA drift figure, or a TA drift figure and its direction.

21. (canceled)

22. A method comprising compensating feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and an infrastructure equipment tethered by the non-terrestrial network

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Embodiments are explained by way of example with respect to the accompanying drawings, in which:

[0012] FIG. 1 shows a Non-Terrestrial Network (NTN) in which a space/aerial vehicle relays an NR signal between a gNB and a UE in a transparent manner;

[0013] FIG. 2 schematically illustrates an embodiment of uplink (UL) time synchronization in a transparent payload NTN scenario;

[0014] FIG. 3a shows a first embodiment of a process compensating a changing common TA at the UE in a transparent payload NTN;

[0015] FIG. 3b shows a variant of the first embodiment where the UE determined the common TA;

[0016] FIG. 4a shows a second embodiment of a process compensating a changing common TA in a transparent payload NTN;

[0017] FIG. 4b shows a variant of the second embodiment where the UE determined the common TA;

[0018] FIG. 5 shows a third embodiment of a process compensating a changing common TA in a transparent payload NTN;

[0019] FIG. 6 shows a fourth embodiment of a process compensating a changing common TA in a transparent payload NTN;

[0020] FIG. 7 shows an example of determining a TA adjustment based on a drift figure and direction sent from the network to the UE;

[0021] FIG. 8 shows an example of representing ephemeris data;

[0022] FIG. 9 shows a schematic block diagram of a communications path between an UE and an gNB; and

[0023] FIG. 10 shows an embodiment of a controller for a UE, a gNB, a relay node or a non-terrestrial network component.

DETAILED DESCRIPTION OF EMBODIMENTS

[0024] Before a detailed description of the embodiments under reference of FIG. 1, some general explanations are made.

[0025] The embodiments described below disclose an electronic device comprising circuitry configured to compensate feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and an infrastructure equipment tethered by the non-terrestrial network component.

[0026] The electronic device may be a User Equipment. A User Equipment (UE) may be any device that is related to an end-user or to a terminal to communicate in e.g. a Universal Mobile Telecommunications System (UMTS) and 3GPP Long Term Evolution (LTE, or aLTE) system. The UE may support the New Radio Access Technology Systems in addition to the legacy system such as LTE, and other advancements. The User Equipment (UE) may also be a machine type communication (MTC) terminal. The UE may also have a relay function in which it forwards transmissions from other tethered UEs towards the network.

[0027] Circuitry of the electronic device may include at least one of: a processor, a microprocessor, a dedicated circuit, a memory, a storage, a radio interface, a wireless interface, a network interface, or the like, e.g. typical electronic components which are included in a User Equipment, such as a mobile phone.

[0028] The User Equipment (UE) may also be an aerial UE. An aerial UE may for example be a UE that is provided in, on or at an aerial vehicle. An aerial device may for example be an Unmanned Aerial Vehicles (UAV) (a “Drone”), or aircrafts that operate with various degrees of autonomy, e.g. under remote control by a human operator or autonomously by an onboard micro controller. An aerial UE may be a mobile communications device that is configured to communicate data via the transmission and reception of signals representing data using a wireless access interface. In the context of this application, the term aerial UE is also used for an electronic device that is autonomously or semi-autonomously operating in an aerial device, without the operator (or “user”) of the device being required to be located at or close to the device. The term User Equipment (UE) thus also relates to equipment where the user is located remote to the equipment.

[0029] The circuitry of the electronic device may be configured to absorb changes in a feeder link propagation time as part of a UE-specific differential TA.

[0030] The circuitry of the electronic device may be configured to repeatedly adjust a UE-specific differential TA to take account of a changing distance between the non-terrestrial network component and the infrastructure equipment.

[0031] The circuitry of the electronic device may be configured to receive information on the ephemeris of the non-terrestrial network component and a location of the infrastructure equipment, and to repeatedly calculate a distance between the non-terrestrial network component and the infrastructure equipment based on this information.

[0032] The circuitry of the electronic device may be configured to receive information on the ephemeris of the non-terrestrial network component and an initial distance between the infrastructure equipment and the non-terrestrial network component, and to repeatedly calculate a distance between the nonterrestrial network component and the infrastructure equipment based on this information.

[0033] The circuitry of the electronic device may be configured to receive information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component once the electronic device enters RRC connected mode and/or shortly after feeder link switching occurs.

[0034] The circuitry of the electronic device may be configured to receive information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component in encrypted form.

[0035] The circuitry of the electronic device may be configured to repeatedly receive a current TA adjustment and to adjust a common TA according to this TA adjustment.

[0036] The circuitry of the electronic device may be configured to repeatedly determine a current TA adjustment according to a TA drift figure and its direction and to adjust a common TA according to this TA adjustment.

[0037] The TA drift figure and its direction may include both the drift due to the satellite movement in its orbit and also its changing displacement from the tethered infrastructure equipment.

[0038] The circuitry of the electronic device may be configured to receive the TA drift figure and its direction as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by regular MAC messages.

[0039] The embodiments further disclose a system comprising an electronic device as defined in claim 1, an infrastructure equipment located on the ground, and a non-terrestrial network component configured to relay uplink and downlink traffic between the user equipment and the infrastructure equipment.

[0040] The embodiments further disclose an infrastructure equipment comprising circuitry configured to provide information to a user equipment for compensating feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and a base station tethered by the non-terrestrial network component.

[0041] The infrastructure equipment may also be referred to as a base station, a network element such as an entity of a core network, an enhanced Node B or a coordinating entity for example, and may provide a wireless access interface to one or more communications devices within a coverage area or cell. The infrastructure equipment may for example be any entity of a telecommunications system, e.g. an entity of a New Radio Access Technology Systems, e.g. next Generation' Node B.

[0042] Circuitry of an infrastructure equipment may include at least one of: a processor, a microprocessor, a dedicated circuit, a memory, a storage, a radio interface, a wireless interface, a network interface, or the like, e.g. typical electronic components which are included in a base station, such as an gNB.

[0043] The circuitry of the infrastructure equipment may be configured to send to the user equipment information on the ephemeris of the non-terrestrial network component.

[0044] The circuitry of the infrastructure equipment may be configured to send to the user equipment information on the location of the infrastructure equipment tethered by the non-terrestrial network component.

[0045] The circuitry of the infrastructure equipment may be configured to send to the user equipment information on an initial distance between the infrastructure equipment and the non-terrestrial network component.

[0046] The circuitry of the infrastructure equipment may be configured to send to the user equipment information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component once the electronic device enters RRC connected mode and/or shortly after feeder link switching occurs.

[0047] The circuitry of the infrastructure equipment may be configured to send to the user equipment information on the location of the infrastructure equipment or information on the distance of the infrastructure equipment from the non-terrestrial network component in encrypted form.

[0048] The circuitry of the infrastructure equipment may be configured to repeatedly send to the user equipment a current TA adjustment.

[0049] The circuitry of the infrastructure equipment may be configured to send to the user equipment a TA drift figure and its direction.

[0050] The circuitry of the infrastructure equipment may be configured to send the TA drift figure and its direction (ΔT.sub.com/Δt) as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by regular MAC messages.

[0051] The embodiments also disclose a method comprising compensating feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and an infrastructure equipment tethered by the non-terrestrial network component. The method may be a computer-implemented method.

[0052] The embodiments also disclose a computer program comprising instructions, which when executed by a processor, instruct the processor to compensate feeder link influence on the common TA in a transparent payload non-terrestrial network configuration with a non-terrestrial network component and an infrastructure equipment tethered by the non-terrestrial network component. The embodiments also disclose a computer-readable medium storing this computer program.

[0053] The embodiments are now described in more detail with reference to the accompanying drawings.

[0054] As stated in the introductory part of this application, Non-Terrestrial Network (NTN) components in the 5G system rely on space/airborne vehicles (such as satellites) to provide 5G service in unserved or underserved areas that cannot be (sufficiently) covered by terrestrial 5G network. The purpose of a space/airborne network component is to provide the 5G service enablers to user equipment (UE) such as handheld devices.

[0055] For such space/airborne networks, it is considered a configuration where base station functions (next Generation Node B, short gNB) are on board the space/airborne vehicle. This scenario is called “regenerative payload NTN”. There are other scenarios, where the space/airborne vehicle only relays an NR signal between a gNB and a UE in a transparent manner. In this latter scenario, which (also called “transparent payload”, or “bent pipe payload”), there are no base station functions on board the space/airborne vehicle.

[0056] In general, the term “feeder link” refers to the radio link between the space/airborne platform and the gateways that connect the satellite or aerial access network to the core network, and the term “service link” refers to the radio link between the user equipment (UE) and the space/airborne platform. In addition to the service link to the space/airborne platform, the UE may also support a radio link with a terrestrial based RAN.

[0057] FIG. 1 shows a Non-Terrestrial Network (NTN) in which a space/aerial vehicle relays an NR signal between a gNB and a UE in a transparent manner. A non-terrestrial network device NT-RN (e.g. space/aerial vehicle such as a satellite) includes functionality to relay, via a Un interface, an NR signal between a UE and a terrestrial next Generation Node B gNB. The gNB communicates with NG Core components NGC, in particular a core data network. Here, the gNB comprises the functionality of an NTN Gateway which acts as router interfacing the NGC. Via the non-terrestrial network device NT-RN, the gNB provides NR user plane and control plane protocol terminations towards the UE, and connects via the NG interface to the NG Core (NGC).

[0058] Here, the Un interface refers to the radio interface between the UE and the gNB via the non-terrestrial network device NT-RN. Still further, NGc refers to the control plane interface between the gNB and the NGC and NGu refers to the user plane interface between the gNB and the NGC.

Transparent Mode NTN Configuration

[0059] In a transparent mode NTN configuration such as described in FIG. 1, the space/airborne network component (e.g. satellite) is transparent to the UE and the one way propagation delay from the UE to the gNB incorporates the feeder link which connects the satellite to the terrestrial gNB. As the length of this feeder link changes due to satellite orbital movement and occasional feeder link switching, this needs to be reflected in the timing adjustments between the UE and the gNB.

[0060] FIG. 2 schematically illustrates an embodiment of uplink (UL) time synchronization in a transparent payload NTN scenario. A terrestrial gNB provides NR user plane and control plane protocol terminations towards user equipments UE1, UE2, . . . , UEx via a non-terrestrial (space/airborne) network component (e.g. a satellite) NT-RN. The non-terrestrial network component NT-RN acts as non-terrestrial relay node NT-RN and relays the uplink and downlink signals from and to gNB for user equipments UEs UE1, UE2, . . . , UEx within its service area 20 (footprint of the spot beam of the space/airborne network component NT-RN). To this end, the space/airborne network component NT-RN connects via the NG interface to the gNB.

[0061] The network NGC which knows the ephemeris of the non-terrestrial network component (satellite) NT-RN and the location of the gNB calculates a common timing adjustment (TA) that all UEs within the given service area 20 can use to advance their UL transmissions so that at the gNB, there can be alignment of all UL received and DL transmit frames.

[0062] A common timing adjustment (common TA) T.sub.com is defined as the delay between the gNB and a reference point RP defined in the beam footprint 20:

T.sub.com=2*(D.sub.01+D.sub.02)/c

[0063] where D.sub.01 is the distance between the reference point RP and the space/airborne relay node NT-RN, D.sub.02 is the distance between the space/airborne network relay node NT-RN and the gNB, and c is the speed of light. This common TA T.sub.com may be seen as the average delay between the gNB and all locations of UEs within the footprint 20 of the spot beam.

[0064] The reference point RP may for example be taken as the center of the beam footprint 20 on the earth surface. In particular, the common TA reference point may for example be defined as the earth-based center of the beam footprint when the satellite is at zenith. This can be calculated by the network as it knows the ephemeris of the satellite and in general the beam footprint. If the reference point is on earth, then any UEs that happens to be airborne (e.g. the UE of a passenger on a plane) will be in general closer to the space/airborne network component than the common TA reference point. For such UEs, their UE specific differential TA will be negative. In order to ensure that differential TAs for all UEs, including airborne UEs, is always positive, the reference point RP may be defined at an aerial location above the beam center on earth. The height of such a location may for example be the predetermined maximum height at which it is known a UE can potentially rise to, e.g. the highest height aircraft can fly to (for example 15000 km above sea level).

[0065] There are several ways to determine the common TA T.sub.com. For example, the network may calculate the common TA and broadcast it within the beam for example, in system information. Alternatively, in connected mode, the network may send the UE the common TA via a MAC signaling like e.g. MAC CE message. Still further, knowing the common TA reference point of its beam and the current position of the satellite (through knowledge of the ephemeris), the UE can itself calculate the common TA. If the UE has to calculate the common TA, then the location of the common TA reference point may be broadcast to the UE (respectively all UEs in the beam footprint) for example through system information so that the UE knows the reference point for computing the common TA. The ephemeris data may be provided to the UEs according to the principles set out in section 7.3.6.2 of 3GPP TR 38.821 V16.0.0 which are summarized below with regard to FIG. 8 and the corresponding description.

[0066] Each UE is supposed to derive a UE-specific differential delay adjustment T.sub.UEx (for the x-th UE) which is related to the propagation time between the x-th UE and the reference point for the common TA:

T.sub.UEx=2*(D.sub.1x−D.sub.01)/c

[0067] where D.sub.01 is the distance between the reference point RP and the gNB, D.sub.1x is the distance between gNB and the x-th UE, and c is the speed of light. As the beam footprint sizes of NTN components are bigger than normal terrestrial cells, it is expected that even this UE specific differential TA will be larger than the typical TAs in a terrestrial network wherein cell sizes are a lot smaller. A positioning capable UE, knowing its position and the reference point RP for the common TA can calculate its differential delay T.sub.UEx as the propagation time to the common TA reference point. Alternatively, the network, knowing the UEs position (e.g. reported by a positioning-capable UE), can also calculate the UE's propagation time to the common TA reference point RP which the network also knows for any of its current beams. Then the network can send this propagation time to the UE in connected mode. Still alternatively, the UE can RACH and then receive its differential TA from the RAR. For this RACH, the UE must advance the transmission time of its RACH transmissions by the common TA. So the UE needs to know the value for the common TA before it can derive its differential TA via RACH.

[0068] From the UE-specific differential delay T.sub.UEx and the common timing adjustment T.sub.com a full TA T.sub.full is obtained for each UE:

T.sub.full=T.sub.com+T.sub.UEx

[0069] This full TA T.sub.full can then be used by the UE to maintain the UL timing advance and synchronization in the NTN cell.

Changing Common TA in a Transparent Payload NTN

[0070] In a regenerative payload NTN, the gNB (or its distributed unit gNB-DU) is on the satellite and so, the common TA is essentially the height of the satellite above the reference point. This depends mostly on the orbital height of the satellite and so for a given beam or satellite, this height is to a large extent fixed the implication of which is that the common TA does not significantly change with time. In a transparent payload NTN as shown in FIG. 1, however, the gNB is located on the ground and the common TA depends on both the satellite height and the propagation delay between the satellite and the terrestrial gNB. As the satellite describes its orbit, this second component changes and so the common TA also changes. The embodiments described below in more detail address this aspect of how to treat a changing common TA in a transparent payload NTN that changes because of: (a) the changing distance due to the orbiting of the satellite between the gNB and the satellite or, (b) a feeder link switch. When a feeder link switch occurs, the network switches its connection to the UE from the current serving gateway to another target gateway. The distance between the target gateway and the satellite is likely to be different from that between the original serving gateway and the satellite.

[0071] FIG. 3a shows a first embodiment of a process compensating a changing common TA at the UE in a transparent payload NTN. At 31, a UE receives from the network a common TA, information on the ephemeris of a satellite, and the location of the serving gNB tethered by the satellite. At 32, the UE determines the UE-specific differential TA. This may happen according to any one of the methods described above (depending on the chosen method of determining the UE-specific differential TA, the network may provide additional information such as the position of the reference point RP, UE-specific propagation time, etc not displayed in FIG. 3a). Knowing the ephemeris of the satellite and hence its orbital speed, at 33, the UE calculates the position of the satellite based on the information on the ephemeris of the satellite. This calculation of the position of the satellite based on the information on the ephemeris of the satellite may be performed according to the principles set out in Annex A of 3GPP TR 38.821 V16.0.0 which is herewith incorporated by reference. At 34, the UE calculates the distance between the satellite and its tethered gNB based on the location of the satellite and the location of the gNB. Based on this distance between the satellite and its tethered gNB, the UE, at 35, adjusts its UE-specific differential TA (for example in each UL transmission) to take account of any changes in the distance between the satellite and its tethered gNB. At 36, the UE determines the full TA based on the (constant) common TA obtained from the network, and based on the adjusted UE-specific differential TA. The UE then uses this full TA for maintenance of UL timing advance and synchronization in NTN cell. As indicated by the arrow in FIG. 3a, steps 33, 34, 35, and 36 are performed repeatedly while the UE is within the spot beam of the satellite and thus in the service area of the gNB tethered by the satellite.

[0072] In this embodiment, the common TA stays constant whilst the changes in the feeder link propagation time are absorbed as part of the UE-specific differential TA. The location of the serving gNB can be provided to the UEs once they enter RRC connected mode and/or shortly after feeder link switching occurs. The location of the serving gNB can for example be provided to the UEs in a MAC signaling e.g. MAC control element (MAC CE). In RRC connected mode, the gNB location information can be encrypted and this information is transferred either in encrypted user plane packet or protected RRC signaling. The ephemeris data may be provided to the UEs according to the principles set out in section 7.3.6.2 of 3GPP TR 38.821 V16.0.0 which are summarized below with regard to FIG. 8 and the corresponding description.

[0073] In the embodiment of FIG. 3a, the UE receives, at 31, a common TA from the network. FIG. 3b shows a variant of this first embodiment. In this variant, the UE does not receive the common TA from the network. Instead, the UE, at 31a receives from the network information on the ephemeris of the satellite and the location of the gNB. At 31b, the UE determines a common TA based on the information on the ephemeris of the satellite and the location of the gNB, and then follows the same steps 33 to 36 as in the embodiment of FIG. 3a.

[0074] FIG. 4a shows a second embodiment of a process of compensating a changing common TA in a transparent payload NTN. At 41, a UE receives from the network a common TA, information on the ephemeris of a satellite, and the initial distance between the satellite and the serving gNB tethered by the satellite. At 42, the UE determines the UE-specific differential TA. Knowing the ephemeris of the satellite and hence its orbital speed, at 43, the UE calculates the distance between the satellite and the gNB based on the initial distance between the satellite, and based on the information on the ephemeris of the satellite. Based on this distance between the satellite and its tethered gNB, the UE, at 44, adjust its UE-specific differential TA (for example in each UL transmission) to take account of any changes in the distance between the satellite and its tethered gNB. At 45, the UE determines its full TA based on the (constant) common TA obtained by from the network, and based on the adjusted UE-specific differential TA. The UE then uses this full TA for maintenance of UL timing advance and synchronization in NTN cell. As indicated by the arrow in FIG. 4a, steps 43, 44, and 45 are performed repeatedly while the UE is within the spot beam of the satellite and thus in the service area of the gNB tethered by the satellite.

[0075] Like in the embodiment of FIG. 3a, also in this embodiment of FIG. 4a, the common TA stays constant whilst the changes in the feeder link propagation time are absorbed as part of the UE-specific differential TA. The distance of the serving gNB can be provided to the UEs once they enter RRC connected mode and shortly after feeder link switching occurs. The location of the serving gNB can for example be provided to the UEs in a MAC control element (MAC CE). In RRC connected mode, the gNB distance information can be encrypted.

[0076] In the embodiment of FIG. 4a, the UE receives, at 41, a common TA from the network. FIG. 4b shows a variant of this second embodiment. In this variant, the UE does not receive the common TA from the network. Instead, the UE, at 41a receives from the network information on the ephemeris of the satellite and the distance of the gNB. At 41b, the UE determines a common TA based on the information on the ephemeris of the satellite and the location of the gNB, and then follows the same steps 43 to 45 as in the embodiment of FIG. 4a.

[0077] FIG. 5 shows a third embodiment of a process compensating a changing common TA in a transparent payload NTN. At 51, a UE receives from the network a common TA. At 52, the UE determines the UE-specific differential TA. At 53, a UE in connected mode regularly receives common TA adjustment messages. Such a message will carry the common TA adjustment calculated by the network that arises either from just normal orbital movement of the satellite or from feeder link switching. Since this signaling is UE-specific and there are likely many UEs within the large footprint of a particular spot beam, it consumes a lot of resources. At 54, the UE adjusts the common TA based on the common TA adjustment received from the network. At 55, the UE determines its full TA based on the adjusted common TA and based on the UE-specific differential TA. The UE then uses this full TA for maintenance of UL timing advance and synchronization in NTN cell. As indicated by the arrow in FIG. 5, steps 53, 54 and 55 are performed repeatedly while the UE is within the spot beam of the satellite and thus in the service area of the gNB tethered by the satellite.

[0078] An adjusted common TA T.sub.com,adjusted may for example be determined according to

T.sub.com,adjusted=T.sub.com+T.sub.adjust

[0079] based on a constant common TA T.sub.com initially received from the network and based on a respective current TA adjustment T.sub.adjust repeatedly received from the network.

[0080] FIG. 6 shows a fourth embodiment of a process compensating a changing common TA in a transparent payload NTN. At 61, a UE receives from the network a common TA, a TA drift figure and its direction. The drift figure and the direction of the drift are derived by the network from the satellite ephemeris information. The TA drift includes both the drift due to the satellite movement in its orbit and also its changing displacement from its serving gNB as calculated by the network. The network may for example send the TA drift figure and its direction to the UE as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by regular MAC messages. At 62, the UE determines the UE-specific differential TA. At 63, the UE determines a current TA adjustment from the drift figure and direction obtained from the network. At 64, the UE adjusts the common TA according to the current TA adjustment obtained from the drift figure and direction. At 65, the UE determines its full TA based on the adjusted common TA and based on the UE-specific differential TA. The UE then uses this full TA for maintenance of UL timing advance and synchronization in NTN cell. As indicated by the arrow in FIG. 6, steps 63, 64, and 65 are performed repeatedly while the UE is within the spot beam of the satellite and thus in the service area of the gNB tethered by the satellite.

[0081] This embodiment works for all types of satellite orbits including elliptical orbits and allows the UEs to have three components in its TA adjustment: common TA, TA drift and UE-specific differential TA. The signaling is UE-specific with regard to the drift figure and direction, but the drift figure and direction may be provided to the UEs less frequent than in the embodiment of FIG. 5. The signaling thus consumes less resources than the signaling in the embodiment of FIG. 5.

[0082] In the embodiment of FIG. 6, the UE receives from the network a TA drift figure and its direction In an alternative embodiment, the UE will receive from the network only a TA drift figure and the UE determines the direction of the drift from the ephemeris.

[0083] FIG. 7 shows an example of determining a TA adjustment based on a drift figure and direction sent from the network to the UE (or drift direction determined by the UE from the ephemeris) as described at process step 62 in the fourth embodiment above. In the example, a drift figure and direction ΔT.sub.com/Δt=+2 μs/10 ms=+0.0002, for example, is sent from the network to a UE. The drift FIG. 0.0002 indicates the amount of TA drift, whereas the plus sign indicates the direction of the TA drift (here: TA drift is increasing in time). The graph shows the time in milliseconds (ms) on the ordinate and the common TA in microseconds (μs) on the abscissa. The solid line shows the common TA T.sub.com,adjusted as computed by the UE from the drift figure and direction obtained from the network. This adjusted common TA T.sub.com,adjusted may for example be determined according to

T.sub.com,adjusted=T.sub.com+(ΔT.sub.com/Δt)*t

[0084] based on the time t, drift figure and direction ΔT.sub.com/Δt and a predefined fixed common TA T.sub.com received from the network.

[0085] The embodiments described above all address the issue of feeder link influence on the common TA and thus allow for a maintenance of UL timing advance and synchronization in NTN cells.

Ephemeris Data for NTN

[0086] Ephemeris Data for NTN is treated in section 7.3.6 of 3GPP TR 38.821 V16.0.0 in more detail which is herewith incorporated by reference. Ephemeris data may contain the information about the orbital trajectories of artificial satellites as described for example in Annex A of 3GPP TR 38.821 V16.0.0. There are different possible representations of ephemeris data.

[0087] FIG. 8 shows one possibility to represent ephemeris data. According to this example orbital parameters are used, e.g. semi-major axis α, eccentricity e, inclination i.sub.0, right ascension Ω.sub.0 of the ascending node, argument ωof periapsis, mean anomaly M.sub.0 at a reference point in time, and the epoch t.sub.06. The first five parameters can determine an orbital plane, and the other two parameters are used to determine exact satellite location at a time. A description table for the orbital parameters and the corresponding illustrations are as below:

TABLE-US-00001 Orbital √{square root over (a)} Square root of semi major axis (semi-major axis) plane e Eccentricity (eccentricity) parameters i.sub.0 Inclination angle at reference time (inclination) Ω.sub.0 Longitude of ascending node of orbit plane (right ascension of the ascending node) ω Argument of perigee (argument of periapsis) Satellite M.sub.0 Mean anomaly at reference time (true anomaly and a level reference point in time) parameters t.sub.06 Ephemeris reference time (the epoch)

[0088] The embodiments are, however, not restricted to this representation of ephemeris data. Another possible option is to provide the location of the satellite in coordinates (x, y, z), e.g. ECEF coordinates. Additionally, a velocity vector (vx, vy, vz) and again a reference point in time may also be provided.

[0089] The ephemeris data may be provided to the UEs according to the principles set out in section 7.3.6.2 of 3GPP TR 38.821 V16.0.0. A possibility of provisioning the ephemeris data or parts of the ephemeris data from the network to the UE may be via a memory card such as a uSIM. However, there is no need for a UE to store orbital parameters for all the satellites. If the orbital parameters per satellite are pre-provisioned, UE only needs to store the ephemeris data for the satellites that may serve UE. Another possible solution is to broadcast the orbital parameters of the serving satellite and several neighbouring satellites which will be sufficient for initial access and mobility handling at UE side.

[0090] Means for updating ephemeris data stored in a UE may be foreseen such as set out in section 7.3.6.3 of 3GPP TR 38.821 V16.0.0 which is herewith incorporated by reference.

[0091] Given a specific point in time, it is straightforward to calculate the satellite location according to the principles set out in Annex A of 3GPP TR 38.821 V16.0.0 which is herewith incorporated by reference.

Implementation

[0092] FIG. 9 shows a schematic block diagram of a communications path between a UE 800, a non-terrestrial (space/airborne) relay node NT-RN 820 (e.g. satellite), and a gNB 830. As shown in FIG. 9 the UE includes a transmitter 801, a receiver 802, and a controller 803 to control the transmission of signals to and the reception of signals from the gNB. The Uplink signals are represented by an arrow 860. Downlink signals are shown by an arrow 850. The space/airborne relay node RT-RN 820 includes a transmitter 821 a receiver 822 and a controller 823 which may include functionality for relaying downlink and uplink signals between the UE 800 and the gNB 820 in accordance with a wireless access interface. The gNB 830 includes a transmitter 831 a receiver 832 and a controller 833 which may include a scheduler for scheduling the transmission and reception of signals on the downlink and the uplink in accordance with a wireless access interface.

[0093] FIG. 10 describes an embodiment of a controller 900. This controller 900 can be implemented such that it can basically function as any type of apparatus or entity, base station, relay node, transmission and reception point, or user equipment as described herein. Controller 900 can thus act as controllers 803, 823, or controller 833 of FIG. 9. The controller 900 has components 931 to 940, which can form a circuitry, such as any one of the circuitries of the entities, base stations, and user equipment, as described herein.

[0094] Embodiments which use software, firmware, programs or the like for performing the methods as described herein can be installed on controller 900, which is then configured to be suitable for the concrete embodiment.

[0095] The controller 900 has a CPU 931 (Central Processing Unit), which can execute various types of procedures and methods as described herein, for example, in accordance with programs stored in a read-only memory (ROM) 932, stored in a storage 937 and loaded into a random access memory (RAM) 933, stored on a medium 940, which can be inserted in a respective drive 939, etc.

[0096] The CPU 931, the ROM 932 and the RAM 933 are connected with a bus 941, which in turn is connected to an input/output interface 934. The number of CPUs, memories and storages is only exemplary, and the skilled person will appreciate that the controller 900 can be adapted and configured accordingly for meeting specific requirements which arise when it functions as a base station, and user equipment.

[0097] At the input/output interface 934, several components are connected: an input 935, an output 936, the storage 937, a communication interface 938 and the drive 939, into which a medium 940 (compact disc, digital video disc, compact flash memory, or the like) can be inserted.

[0098] The input 935 can be a pointer device (mouse, graphic table, or the like), a keyboard, a microphone, a camera, a touchscreen, etc. The output 936 can have a display (liquid crystal display, cathode ray tube display, light emittance diode display, etc.), loudspeakers, etc. The storage 937 can have a hard disk, a solid state drive and the like.

[0099] The communication interface 938 can be adapted to communicate, for example, via a local area network (LAN), wireless local area network (WLAN), mobile telecommunications system (GSM, UMTS, LTE, etc.), Bluetooth, infrared, etc. When the controller 900 functions as a base station, the communication interface 938 can further have a respective air interface (providing e.g. E-UTRA protocols OFDMA (downlink) and SC-FDMA (uplink)) and network interfaces (implementing for example protocols such as S1-AP, GTP-U, S1-MME, X2-AP, or the like). Moreover, the controller 900 may have one or more antennas and/or an antenna array. The present disclosure is not limited to any particularities of such protocols.

[0100] It should be recognized that the embodiments describe methods with an exemplary ordering of method steps. The specific ordering of method steps is however given for illustrative purposes only and should not be construed as binding. For example the ordering of the process steps 31b and 32 in FIG. 3b may be changed. Other changes of the ordering of method steps may be apparent to the skilled person.

[0101] It should also be noted that the division of the control or circuitry of FIG. 10 into units 931 to 940 is only made for illustration purposes and that the present disclosure is not limited to any specific division of functions in specific units. For instance, at least parts of the circuitry could be implemented by a respective programmed processor, field programmable gate array (FPGA), dedicated circuits, and the like.

[0102] All units and entities described in this specification and claimed in the appended claims can, if not stated otherwise, be implemented as integrated circuit logic, for example on a chip, and functionality provided by such units and entities can, if not stated otherwise, be implemented by software.

[0103] In so far as the embodiments of the disclosure described above are implemented, at least in part, using software-controlled data processing apparatus, it will be appreciated that a computer program providing such software control and a transmission, storage or other medium by which such a computer program is provided are envisaged as aspects of the present disclosure.

[0104] Note that the present technology can also be configured as described below: [0105] (1) An electronic device (UE) comprising circuitry configured to compensate feeder link influence on the common TA (T.sub.com) in a transparent payload non-terrestrial network (NTN) configuration with a non-terrestrial network component (NT-RN) and an infrastructure equipment (gNB) tethered by the non-terrestrial network component (NT-RN). [0106] (2) The electronic device (UE) of (1) in which the circuitry is configured to absorb changes in a feeder link propagation time as part of a UE-specific differential TA (T.sub.UEx). [0107] (3) The electronic device (UE) of (1) or (2) in which the circuitry is configured to repeatedly adjust (35, 44) a UE-specific differential TA (T.sub.UEx) to take account of a changing distance between the non-terrestrial network component (NT-RN) and the infrastructure equipment (gNB). [0108] (4) The electronic device (UE) of any one of (1) to (3), in which the circuitry is configured to receive (31) information on the ephemeris of the non-terrestrial network component (NT-RN) and a location of the infrastructure equipment (gNB), and to repeatedly calculate (33, 34) a distance between the non-terrestrial network component (NT-RN) and the infrastructure equipment (gNB) based on this information. [0109] (5) The electronic device (UE) of any one of (1) to (4), in which the circuitry is configured to receive (41) information on the ephemeris of the non-terrestrial network component (NT-RN) and an initial distance between the infrastructure equipment (gNB) and the non-terrestrial network component (NT-RN), and to repeatedly calculate (43) a distance between the non-terrestrial network component (NT-RN) and the infrastructure equipment (gNB) based on this information. [0110] (6) The electronic device (UE) of any one of (1) to (5), in which the circuitry is configured to receive (31) information on the location of the infrastructure equipment (gNB) or information on the distance of the infrastructure equipment (gNB) from the non-terrestrial network component (NT-RN) once the electronic device (UE) enters RRC connected mode and/or shortly after feeder link switching occurs. [0111] (7) The electronic device (UE) of any one of (1) to (6), in which the circuitry is configured to receive (31) information on the location of the infrastructure equipment (gNB) or information on the distance of the infrastructure equipment (gNB) from the non-terrestrial network component (NT-RN) in encrypted form. [0112] (8) The electronic device (UE) of any one of (1) to (7), in which the circuitry is configured to repeatedly receive (53) a current TA adjustment (T.sub.adjust) and to adjust (54) a common TA (T.sub.com) according to this TA adjustment (T.sub.adjust). [0113] (9) The electronic device (UE) of any one of (1) to (8), in which the circuitry is configured to repeatedly determine (63) a current TA adjustment ((ΔT.sub.com/Δt)*t) according to a TA drift figure and its direction (ΔT.sub.com/Δt) and to adjust (64) a common TA (T.sub.com) according to this TA adjustment (T.sub.adjust). [0114] (10) The electronic device (UE) of (9), in which the TA drift figure and its direction (AT./At) includes both the drift due to the satellite movement in its orbit and also its changing displacement from the tethered infrastructure equipment (gNB). [0115] (11) The electronic device (UE) of (9) or (10), in which the circuitry is configured to receive the TA drift figure and its direction (ΔT.sub.com/Δt) as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by regular MAC messages. [0116] (12) A system comprising an electronic device (UE) as defined in any one of (1) to 12, an infrastructure equipment (gNB) located on the ground, and a non-terrestrial network component (NT-RN) configured to relay uplink and downlink traffic between the user equipment (UE) and the infrastructure equipment (gNB). [0117] (13) An infrastructure equipment (gNB; NTC) comprising circuitry configured to provide information to a user equipment (UE) for compensating feeder link influence on the common TA (T.sub.com) in a transparent payload non-terrestrial network (NTN) configuration with a non-terrestrial network component (NT-RN) and a base station (gNB) tethered by the non-terrestrial network component (NT-RN). [0118] (14) The infrastructure equipment (gNB; NTC) of (13) in which the circuitry is configured to send to the user equipment (UE) information on the ephemeris of the non-terrestrial network component (NT-RN). [0119] (15) The infrastructure equipment (gNB; NTC) of (13) or (14) in which the circuitry is configured to send to the user equipment (UE) information on the location of the infrastructure equipment (gNB) tethered by the non-terrestrial network component (NT-RN). [0120] (16) The infrastructure equipment (gNB; NTC) of any one of (13) to (15) in which the circuitry is configured to send to the user equipment (UE) information on an initial distance between the infrastructure equipment (gNB) and the non-terrestrial network component (NT-RN). [0121] (17) The infrastructure equipment (gNB; NTC) of any one of (13) to (16) in which the circuitry is configured to send to the user equipment (UE) information on the location of the infrastructure equipment (gNB) or information on the distance of the infrastructure equipment (gNB) from the non-terrestrial network component (NT-RN) once the electronic device (UE) enters RRC connected mode and/or shortly after feeder link switching occurs. [0122] (18) The infrastructure equipment (gNB; NTC) of any one of (13) to (17) in which the circuitry is configured to send to the user equipment (UE) information on the location of the infrastructure equipment (gNB) or information on the distance of the infrastructure equipment (gNB) from the non-terrestrial network component (NT-RN) in encrypted form. [0123] (19) The infrastructure equipment (gNB; NTC) of any one of (13) to (18) in which the circuitry is configured to repeatedly send to the user equipment (UE) a current TA adjustment (T.sub.adjust). [0124] (20) The infrastructure equipment (gNB; NTC) of any one of (13) to (19) in which the circuitry is configured to send to the user equipment (UE) a TA drift figure, or a TA drift figure and its direction (ΔT.sub.com/Δt). [0125] (21) The infrastructure equipment (gNB; NTC) of (20) in which the circuitry is configured to send the TA drift figure and its direction (ΔT.sub.com/Δt) as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by regular MAC messages. [0126] (22) A method comprising compensating feeder link influence on the common TA (T.sub.com) in a transparent payload non-terrestrial network (NTN) configuration with a non-terrestrial network component (NT-RN) and an infrastructure equipment (gNB) tethered by the non-terrestrial network component (NT-RN).