TIMING AND FREQUENCY COMPENSATION IN NON-TERRESTRIAL NETWORK COMMUNICATIONS

Abstract

Various solutions for time and frequency in non-terrestrial network (NTN) communications are proposed. An apparatus implemented in a user equipment (UE) obtains a center frequency and a reference time of a non-terrestrial network. The apparatus further obtains a feeder link delay of a feeder link between a network node and a satellite, and a service link delay drift rate of a service link between the apparatus and the satellite. Then, the apparatus performs an uplink frequency pre-compensation through calculating an uplink transmit frequency according to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate.

Claims

1. A method, comprising: obtaining, by a processor of an apparatus, a center frequency and a reference time of a non-terrestrial network (NTN); obtaining, by the processor, a feeder link delay of a feeder link between a network node and a satellite; obtaining, by the processor, a service link delay drift rate of a service link between the apparatus and the satellite; and performing, by the processor, an uplink (UL) frequency pre-compensation through calculating an uplink transmit frequency according to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate.

2. The method of claim 1, wherein a reception time at the satellite is calculated as subtracting the feeder link delay from the reference time.

3. The method of claim 2, further comprising: calculating, by the processor, a Doppler frequency shift as the center frequency times the service link delay drift rate at the reception time; and calculating, by the processor, the UL transmit frequency by subtracting the Doppler frequency shift from the center frequency.

4. The method of claim 2, further comprising: measuring, by the processor, a received frequency of a DL signal; obtaining, by the processor, a service link delay; obtaining, by the processor, a Doppler frequency drift rate; calculating, by the processor, a Doppler frequency shift as the center frequency times the service link delay drift rate at the reception time; calculating, by the processor, a Doppler frequency variation as the center frequency times the Doppler frequency drift rate times twice the service link delay; and calculating, by the processor, the UL transmit frequency by subtracting twice the Doppler frequency shift from the received frequency and adding the Doppler frequency variation to the received frequency.

5. The method of claim 1, further comprising: obtaining, by the processor, a common timing advance (TA); and deriving, by the processor, the feeder link delay as half the common TA.

6. The method of claim 1, further comprising: obtaining, by the processor, a common timing advance (TA); obtaining, by the processor, a feeder link delay drift rate; and adjusting, by the processor, a sampling rate according to the reference time, the common TA, the feeder link delay drift rate, and the service link delay drift rate.

7. The method of claim 6, further comprising: performing, by the processor, a timing compensation through adjusting a baseband signal according to the common TA and the adjusted sampling rate.

8. The method of claim 6, wherein the feeder link delay drift rate is calculated by the processor based on an ephemeris of the satellite and a position of the network node or based on the common TA.

9. The method of claim 6, wherein the feeder link delay drift rate is calculated by the processor an ephemeris of the satellite and a position of the network node or based on the common TA.

10. The method of claim 6, further comprising: receiving, by the processor, a close loop timing advance (TA) from the network node; calculating, by the processor, a user equipment (UE) specific TA based on a position of the apparatus and an ephemeris of the satellite; calculating, by the processor, the common TA based on the feeder link delay, the service link delay, the feeder link delay drift rate, and the reference time; and calculating, by the processor, a transmit time for transmitting an uplink signal according to the close loop TA, the UE specific TA, and the common TA.

11. An apparatus, comprising: a transceiver configured to wirelessly communicate with a non-terrestrial network (NTN); and a processor coupled to the transceiver and configured to perform operations comprising: obtaining, via the transceiver, a center frequency and a reference time of a non-terrestrial network (NTN); obtaining, via the transceiver, a feeder link delay of a feeder link between a network node and a satellite; obtaining, via the transceiver, a service link delay drift rate of a service link between the apparatus and the satellite; and performing an uplink (UL) frequency pre-compensation through calculating an uplink transmit frequency according to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate.

12. The apparatus of claim 11, wherein a reception time at the satellite is calculated as subtracting the feeder link delay from the reference time.

13. The apparatus of claim 12, wherein the processor further performs operations comprising: calculating a Doppler frequency shift as the center frequency times the service link delay drift rate at the reception time; and calculating the UL transmit frequency by subtracting the Doppler frequency shift from the center frequency.

14. The apparatus of claim 12, wherein the processor further performs operations comprising: measuring a received frequency of a DL signal; obtaining, via the transceiver, a service link delay; obtaining a Doppler frequency drift rate; calculating a Doppler frequency shift as the center frequency times the service link delay drift rate at the reception time; calculating a Doppler frequency variation as the center frequency times the Doppler frequency drift rate times twice the service link delay; and calculating the UL transmit frequency by subtracting twice the Doppler frequency shift from the received frequency and adding the Doppler frequency variation to the received frequency.

15. The apparatus of claim 11, wherein the processor further performs operations comprising: obtaining, via the transceiver, a common timing advance (TA); and deriving the feeder link delay as half the common TA.

16. The apparatus of claim 11, wherein the processor further performs operations comprising: obtaining, via the transceiver, a common timing advance (TA); obtaining, via the transceiver, a feeder link delay drift rate; and adjusting a sampling rate according to the reference time, the common TA, the feeder link delay drift rate, and the service link delay drift rate.

17. The apparatus of claim 16, wherein the processor further performs operations comprising: performing a timing compensation through adjusting a baseband signal according to the common TA and the adjusted sampling rate.

18. The apparatus of claim 16, wherein the feeder link delay drift rate is calculated by the processor based on an ephemeris of the satellite and a position of the network node or based on the common TA.

19. The apparatus of claim 16, wherein the feeder link delay drift rate is calculated by the processor an ephemeris of the satellite and a position of the network node or based on the common TA.

20. The apparatus of claim 16, wherein the processor further performs operations comprising: receiving, via the transceiver, a close loop timing advance (TA) from the network node; calculating a user equipment (UE) specific TA based on a position of the apparatus and an ephemeris of the satellite; calculating the common TA based on the feeder link delay, the service link delay, the feeder link delay drift rate, and the reference time; and calculating a transmit time for transmitting an uplink signal according to the close loop TA, the UE specific TA, and the common TA.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.

[0014] FIG. 1 is a diagram of an example network environment in which various proposed schemes in accordance with the present disclosure may be implemented.

[0015] FIG. 2 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.

[0016] FIG. 3 is a flowchart of an example process in accordance with an implementation of the present disclosure.

[0017] FIG. 4 is a flowchart of an example process in accordance with an implementation of the present disclosure.

[0018] FIG. 5 is a flowchart of an example process in accordance with an implementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

[0019] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

Overview

[0020] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to timing compensation in NTN communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

[0021] FIG. 1 illustrates an example network environment 100 in which various proposed schemes in accordance with the present disclosure may be implemented. Network environment 100 involves UE 110, non-terrestrial (NT) network node 120 (e.g., a satellite) and terrestrial network node 130 (e.g., a gateway, base station, eNB, gNB or transmission/reception point (TRP)), which may be a part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, an NB-IoT network, an IIoT network, an NTN network or a 6G network). UE 110 may be far from terrestrial network node 130 (e.g., not within the communication range of terrestrial network node 130) and not able to communicate with terrestrial network node 130 directly. Via NTN, UE 110 may be able to transmit/receive signals to/from NT network node 120. NT network node 120 may relay/transfer signals/data from UE 110 to terrestrial network node 130. Thus, terrestrial network node 130 may be able communicate with UE 110 via NT network node 120. Since NT network node 120 is far from UE 110, propagation delay and Doppler frequency shift may be significant.

[0022] In non-terrestrial communication, satellite links (e.g., service link and feeder link) have impacts including Doppler frequency shift, feeder link delay ?.sub.f, service link delay ?.sub.s, feeder link delay drift d.sub.f and service link delay drift d.sub.s on signals transmitted by the UE.

[0023] Furthermore, UE 110 always synchronizes to the downlink (DL) and uses the DL as a reference. However, the DL itself has a delay t.sub.DL=t.sub.ABS+?.sub.s+?.sub.f. The reception time of the UL at terrestrial network node 130 has to correspond to reference time t.sub.ABS. Similarly, the frequency of the UL received at the NT network node 120 also has to match reference frequency f.sub.0. However, not compensating feeder link delay drift d.sub.f and service link delay drift d.sub.s will lead to phase distortion of the signal which degrades terrestrial network node 130 demodulation performance. Besides, the distortion will lead to demodulation SINR degradation, and the demodulation SNR degradation is small for low SNR. Given SIB performance is targeted for coverage with SNR ??5 dB, the degradation due to feeder link delay drift d.sub.f is not a problem for initial access, but for connected mode, the feeder link delay drift d.sub.f has to be known to the UE to avoid performance degradation.

[0024] In view of the above, the present disclosure proposes a number of schemes pertaining to timing and frequency compensation/synchronization in NTN communications with respect to the UE 110, NT network node 120 and terrestrial network node 130. Under various proposed schemes in accordance with the present disclosure, each of the UE 110, the NT network node 120 and the terrestrial network node 130 may be configured to perform operations pertaining to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate for uplink (UL) frequency pre-compensation in NTN communications, as described below.

[0025] UE 110 may obtain a center frequency and a reference time of NTN. Additionally, UE 110 may obtain the feeder link delay of the feeder link between the NT network node 120 and the terrestrial network node 130. Also, UE 110 may obtain the service link delay drift rate of the service link between the NT network node 120 and the UE 110. The feeder link delay may be indicated or broadcast by the terrestrial network node 130 and signalled to UE 110 by the NT network node 120 or may be derived. The service link delay drift rate may be signaled to UE 110 by the NT network node 120.

[0026] The center frequency and the reference time may be broadcast by the terrestrial network node 130 in a system information block (SIB). In an event that the SIB is an existing SIB, the center frequency and the reference time may be added to an information element (IE) definition for the existing SIB. In an event that the SIB is a new SIB, a new IE may be defined for the new SIB that includes the center frequency and the reference time.

[0027] UE 110 may perform UL frequency pre-compensation through calculating UL transmit frequency according to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate. Specifically, at time t.sub.ABS??.sub.f, UE 110 may calculate the UL transmit frequency by

[00001]$f_c=\frac{f_0}{1+d_s\left(t_{\mathrm{ABS}}-{?}_f\right)}.$

f.sub.0 denotes the center frequency, t.sub.ABS denotes the reference time, d.sub.s denotes the service link delay drift rate, and ?.sub.f denotes the feeder link delay.

[0028] Alternatively, UE 100 may calculate the UL transmit frequency by subtracting Doppler frequency shift from the center frequency. To be more specific, a reception time at the satellite is calculated as subtracting the feeder link delay from the reference time and may be expressed as t.sub.ABS??.sub.f. The Doppler frequency shift may be calculate as the center frequency times the service link delay drift rate at the reception time t.sub.ABS??.sub.f and may be expressed as f.sub.0d.sub.s(t.sub.ABS??.sub.f). Therefore, the UL transmit frequency

[00002]$f_c=\frac{f_0}{1+d_s\left(t_{\mathrm{ABS}}-{?}_f\right)}$

may approximately equal to f.sub.0-f.sub.0d.sub.s(t.sub.ABS??.sub.f).

[0029] In some implementations, UE 110 may calculate the UL transmit frequency by subtracting DL Doppler frequency shift and UL Doppler frequency shift from the received frequency of a DL signal. Specifically, UE 110 may obtain the service link delay ?.sub.s is the one way delay between UE 110 and the NT network node 120 based on the position of the NT network node 120 at time t.sub.ABS. UE 110 may obtain the service link delay drift rate d.sub.s for the DL Doppler frequency shift at the time t.sub.ABA?2?.sub.s??.sub.f, and obtain the service link delay drift rate d.sub.s for the UL Doppler frequency shift at the time t.sub.ABS??.sub.f. Thus, the UL transmit frequency f.sub.0?f.sub.0d.sub.s(t.sub.ABS??.sub.f) equals to f.sub.DL?f.sub.0d.sub.s(t.sub.ABS?2?.sub.s??.sub.f).

[0030] In some implementations, UE 110 may calculate the UL transmit frequency by subtracting twice the Doppler frequency shift from the received frequency and adding the Doppler frequency variation to the received frequency. In detail, similar to previous implementation, UE 110 may measure the received frequency of the DL signal. UE 110 may further obtain the Doppler frequency drift rate. Then, UE 110 may calculate Doppler frequency shift as the center frequency times the service link delay drift rate at the reception time t.sub.ABS??.sub.f and the Doppler frequency shift at the reception time t.sub.ABS??.sub.f may be expressed as f.sub.0d.sub.s(t.sub.ABS??.sub.f). Therefore, UE 110 may calculate the UL transmit frequency by f.sub.c?f.sub.DL?2f.sub.0d.sub.s(t.sub.ABS??.sub.f)+f.sub.0?2?.sub.s.

[0031] In this implementation, p is the Doppler frequency drift rate or derivative of d.sub.s at time t.sub.ABS??.sub.f or t.sub.ABS. The derivative may not be pretty constant during round trip time and changes very slowly, but this allow to calculate the Doppler frequency variation as f.sub.0?2?.sub.s. Since the Doppler frequency drift rate may be derivative of d.sub.s, the UL transmit frequency f.sub.DL?2f.sub.0d.sub.s(t.sub.ABS??.sub.f)+f.sub.0?2?.sub.s may be approximated as f.sub.DL?2f.sub.0d.sub.s(t.sub.ABS??.sub.f??.sub.s). Moreover, the UL transmit frequency f.sub.DL?2f.sub.0d.sub.s(t.sub.ABS??.sub.f??.sub.s) may also be expressed as

[00003]$f_{\mathrm{DL}}-2f_0{d}_s\left(t_{\mathrm{ABS}}-\frac{\mathrm{RTD}}{2}\right).$

RTD denotes the round trip delay, and may be calculated as 2?.sub.s+2?.sub.f.

[0032] According to above, if UE 110 takes center frequency f.sub.0 as a reference, then it only need to pre-compensate the Doppler frequency shift at time of satellite reception f.sub.0d.sub.s(t.sub.ABS??.sub.f). In some implementations, if UE takes the DL frequency f.sub.DL as a reference, then it needs to pre-compensate twice the Doppler frequency shift at time of satellite reception 2f.sub.0d.sub.s(t.sub.ABS??.sub.f) with an additional term f.sub.0?2?.sub.s corresponding to the Doppler drift during the round trip to the satellite 2?.sub.s.

[0033] In some implementations, if the NT network node 120 or the terrestrial network node 130 signalled a common timing advance (TA) without the feeder link delay, UE 110 may derive the feeder link delay as half the common TA at time t.sub.ABS. The feeder link delay may be expressed as

[00004]${?}_f=\frac{{\mathrm{TA}}_{\mathrm{common}}\left(t_{\mathrm{ABS}}\right)}{2}.$

[0034] Under another proposed schemes in accordance with the present disclosure pertaining to timing compensation/synchronization, each of the UE 110, the NT network node 120 and the terrestrial network node 130 may be configured to perform operations pertaining to the reference time, the common TA, the feeder link delay drift rate, and the service link delay drift rate for timing compensation in NTN communications, as described below.

[0035] UE 110 may obtain the common TA and the feeder link delay drift rate. The common TA and the feeder link delay drift rate may be broadcast by the terrestrial network node 130 in SIB. In an event that the SIB is an existing SIB, the common TA and the feeder link delay drift rate may be added to an information element (IE) definition for the existing SIB. In an event that the SIB is a new SIB, a new IE may be defined for the new SIB that includes the common TA and the feeder link delay drift rate.

[0036] UE 110 may adjust a sampling rate according to the reference time, the common TA, the feeder link delay drift rate, and the service link delay drift rate. The sampling rate adjustment can be approximated as

[00005]$\frac{t-\mathrm{TA}}{\left(1+d_s\right)\left(1+d_f\right)},$

TA is the timing advance, d.sub.s denotes the service link delay drift rate, and d.sub.f denotes the feeder link delay drift rate. The sampling rate adjustment

[00006]$\frac{t-\mathrm{TA}}{\left(1+d_s\right)\left(1+d_f\right)}$

approximately equals to

[00007]$\frac{t-\mathrm{TA}}{1+d_s+d_f)}\mathrm{or}\left(t-\mathrm{TA}\right)?\left(1-d_s-d_f\right)\mathrm{since}{d}_s.Math.d_f,$

d.sub.s.sup.2, and d.sub.f.sup.2 are very small and can be ignored.

[0037] To compensate the delay and delay drift rate on service link and feeder link, baseband signal x(t)=a(t?TA) has to include both TA and sampling rate adjustment, so UE 110 performs a timing compensation through adjusting a baseband signal according to the common TA and the adjusted sampling rate. The baseband signal adjustment may be expressed as

[00008]$x\left(t\right)=a\left(\frac{t-\mathrm{TA}}{\left(1+d_s\right)\left(1+d_f\right)}\right).$

[0038] In some implementations, the feeder link delay drift rate is calculated by the processor based on an ephemeris of the satellite and a position of the network node or based on the common TA. The service link delay drift rate is calculated by the processor based on an ephemeris of the satellite and a position of the network node or based on the common TA.

[0039] In some implementations, feeder link drift d.sub.f may not be included. For instance, the base station 130 is on the satellite 120, or part of the base station 130 is on the satellite 120. In these cases, reference point for UL time synchronization is the satellite 120. UE 110 will know about these cases if the common TA is absent or is signalled but equal to zero or a constant value.

[0040] In some implementations, If the common TA is signalled as TA.sub.common(t)=f(t)=D.sub.0+D.sub.1?t+ . . . +D.sub.n?t.sup.n, the common TA can be assumed to be twice the feeder link delay TA.sub.common(t)=f(t)=2?.sub.f(t). The common TA is based on the signaling of TA common parameters similar to the common delay drift rate (i.e., the feeder link delay drift), and the common delay drift rate is calculated as d.sub.f(t)=(D.sub.1+ . . . +nD.sub.nt.sup.n-1)/2.

[0041] TA is used to calculate the transmission start time, and the TA has several parts including a close loop TA, a UE specific TA and the common TA. To calculate the transmit time for transmitting uplink signal, UE 110 may receive the closed TA commands from the NT network node 120 or the terrestrial network node 130. UE 110 may calculate the UE specific TA based on a position of the UE 110 itself and an ephemeris of the NT network node 120. The UE specific TA may be calculated as t.sub.s(t.sub.ABS?2?.sub.s??.sub.f)+?.sub.s(t.sub.ABS??.sub.f), where ?.sub.s(t.sub.ABS) is the one way delay between UE 110 and the NT network node 120 based on the position of the NT network node 120 at time t.sub.ABS. Thus, the UE specific TA is sum of the service link delay at time (t.sub.ABS?2?.sub.s??.sub.f) and the service link delay at time (t.sub.ABS??.sub.f). Alternatively, UE specific TA may be approximated as 2?.sub.s(t.sub.ABS)?d.sub.s?2?(?.sub.s+?.sub.f), which equals to 2?.sub.s(t.sub.ABS)?d.sub.s?RTD. 2?.sub.s(t.sub.ABS)?d.sub.s?RTD may be approximated as

[00009]$2{?}_s\left(t_{\mathrm{ABS}}-\frac{\mathrm{RTD}}{2}\right).$

Hence, the UE Specific TA needs to have a correction due to the delay drift during the round trip delay (RTD), RTD=2?.sub.s+2?.sub.f=2?.sub.s+TA_common(t.sub.ABS).

[0042] UE 110 may further calculate the common TA based on the feeder link delay, the service link delay, the feeder link delay drift rate, and the reference time. Specifically, assuming that the time reference of validity of the feeder link delay/common TA in the terrestrial network node 130, common TA is the TA on the feeder link at the time t.sub.ABS?2?.sub.s?2?.sub.f and the time t.sub.ABS, and may be expressed as ?.sub.f(t.sub.ABS?2?.sub.s?2?.sub.f)+?.sub.f(t.sub.ABS). Alternatively, the common TA may be approximated as

[00010]$2{?}_f\left(t_{\mathrm{ABS}}\right)-d_{f}2\left({?}_s+{?}_f\right)=2{?}_f\left(t_{\mathrm{ABS}}\right)-d_f?\mathrm{RTD}=f\left(t_{\mathrm{ABS}}-\frac{\mathrm{RTD}}{2}\right).$

Hence, the common TA needs to have a correction due to the delay drift during the round trip delay, RTD=2?.sub.s+2?.sub.f=2?.sub.s+TA_common(t.sub.ABS).

[0043] According to above, the transmit time for transmitting uplink signal at the time t.sub.ABS is the sum of the close loop TA, the UE specific TA and the common TA.

Illustrative Implementations

[0044] FIG. 2 illustrates an example communication system 200 having an example communication apparatus 210 and an example network apparatus 220 in accordance with an implementation of the present disclosure. Each of communication apparatus 210 and network apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to center frequency, reference time, feeder link delay, and service link delay drift rate for uplink frequency pre-compensation in NTN communications, including scenarios/schemes described above as well as processes 300, 400 and 500 described below.

[0045] Communication apparatus 210 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, communication apparatus 210 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Communication apparatus 210 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, IIoT or NTN apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, communication apparatus 210 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center.

[0046] Alternatively, communication apparatus 210 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. Communication apparatus 210 may include at least some of those components shown in FIG. 2 such as a processor 212, for example. Communication apparatus 210 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device), and, thus, such component(s) of communication apparatus 210 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.

[0047] Network apparatus 220 may be a part of an electronic apparatus/station, which may be a network node such as a base station, a small cell, a router, a gateway or a satellite. For instance, network apparatus 220 may be implemented in an eNodeB in an LTE, in a gNB in a 5G, NR, 6G, IoT, NB-IoT, IIoT, or in a satellite in an NTN network. Alternatively, network apparatus 220 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 222, for example. Network apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device), and, thus, such component(s) of network apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.

[0048] In one aspect, each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term a processor is used herein to refer to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including power consumption reduction in a device (e.g., as represented by communication apparatus 210) and a network (e.g., as represented by network apparatus 220) in accordance with various implementations of the present disclosure.

[0049] In some implementations, communication apparatus 210 may also include a transceiver 216 coupled to processor 212 and capable of wirelessly transmitting and receiving data. In some implementations, communication apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein. In some implementations, network apparatus 220 may also include a transceiver 226 coupled to processor 222 and capable of wirelessly transmitting and receiving data. In some implementations, network apparatus 220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Accordingly, communication apparatus 210 and network apparatus 220 may wirelessly communicate with each other via transceiver 216 and transceiver 226, respectively.

[0050] Each of communication apparatus 210 and network apparatus 220 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. To aid better understanding, the following description of the operations, functionalities and capabilities of each of communication apparatus 210 and network apparatus 220 is provided in the context of a mobile communication environment in which communication apparatus 210 is implemented in or as a communication apparatus or a UE (e.g., UE 110) and network apparatus 220 is implemented in or as a network node or base station (e.g., NT network node 120 or terrestrial network node 130) of a communication network (e.g., network 120). It is also noteworthy that, although the example implementations described below are provided in the context of NTN communications, the same may be implemented in other types of networks.

[0051] Under a proposed scheme pertaining to center frequency, reference time, feeder link delay, and service link delay drift rate for uplink frequency pre-compensation in NTN communications in accordance with the present disclosure, with communication apparatus 210 implemented in or as UE 110 and network apparatus 220 implemented in or as NT network node 120 or terrestrial network node 130 in network environment 100.

[0052] Processor 212 of the communication apparatus 210 may obtain a center frequency and a reference time of non-terrestrial network (NTN) via transceiver 216 from a NT network node 120 (e.g., satellite). Processor 212 may further obtain a feeder link delay of a feeder link between network node 130 (e.g., base station) and a satellite 120, and obtain a service link delay drift rate of a service link between the apparatus 110 and the satellite 120. Processor 212 may perform UL frequency pre-compensation through calculating an uplink transmit frequency according to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate.

[0053] In some implementations, processor 212 may calculate a reception time at the satellite 120 by subtracting the feeder link delay from the reference time. Then, processor 212 may calculate a Doppler frequency shift as the center frequency times the service link delay drift rate times the reception time. In performing UL frequency pre-compensation, processor 212 may calculate the UL transmit frequency by subtracting the Doppler frequency shift from the center frequency.

[0054] In some implementations, processor 212 may measure a received frequency of a DL signal. Processor 212 may further obtain a service link delay and a Doppler frequency drift rate. Processor 212 may calculate a Doppler frequency shift as the center frequency times the service link delay drift rate times the reception time. Processor 212 may calculate a Doppler frequency variation as the center frequency times the Doppler frequency drift rate times twice the service link delay. In performing UL frequency pre-compensation, processor 212 may calculate the UL transmit frequency by subtracting twice the Doppler frequency shift from the received frequency and adding the Doppler frequency variation to the received frequency.

[0055] In some implementations, processor 212 may obtain the common TA via transceiver 216. Processor 212 may further derive the feeder link delay as half the common TA.

[0056] In performing the timing compensation processor 212 may involve certain operations. For instance, processor 212 may obtain the common TA and a feeder link delay drift rate via transceiver 216. Processor 212 may further adjust a sampling rate according to the reference time, the common TA, the feeder link delay drift rate, and the service link delay drift rate. Additionally, processor 212 may adjust a baseband signal according to the common TA and the adjusted sampling rate.

[0057] In some implementations, processor 212 may calculate the feeder link delay drift rate based on an ephemeris of the satellite and a position of the network node.

[0058] In some implementations, processor 212 may calculate the feeder link delay drift rate based on the common TA.

[0059] In performing UL frequency pre-compensation, processor 212 may involve certain operations. For instance, processor 212 may receive a close loop TA from the network node 130 via the transceiver 218. Processor 212 may calculate a UE specific TA based on a position of the apparatus 110 and an ephemeris of the satellite 120. Processor 212 may calculate the common TA based on the feeder link delay, the service link delay, the feeder link delay drift rate, and the reference time. Processor 212 may calculate a transmit time for transmitting an uplink signal according to the close loop TA, the UE specific TA, and the common TA.

Illustrative Processes

[0060] FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure. Process 300 may be an example implementation of schemes described above, whether partially or completely, with respect to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate for UL frequency pre-compensation with the present disclosure. Process 300 may represent an aspect of implementation of features of communication apparatus 210. Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310, 320, 330 and 340.

[0061] Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 300 may executed in the order shown in FIG. 3 or, alternatively, in a different order. Process 300 may be implemented by communication apparatus 210 or any suitable UE or machine type devices. Solely for illustrative purposes and without limitation, process 300 is described below in the context of communication apparatus 210.

[0062] Process 300 may begin at block 310. At block 310, process 300 may involve processor 212 of communication apparatus 210 obtaining, via transceiver 216, the center frequency and the reference time of non-terrestrial network. Process 300 may proceed from block 310 to block 320.

[0063] At block 320, process 300 may involve processor 212 obtaining, via transceiver 216, a feeder link delay of a feeder link between a network node. Process 300 may proceed from block 320 to block 330.

[0064] At block 330, process 300 may involve processor 212 obtaining, via transceiver 216, a service link delay drift rate of a service link between the apparatus and the satellite. Process 300 may proceed from block 330 to block 340.

[0065] At block 340, process 300 may involve processor 212 performing, via transceiver 216, an uplink frequency pre-compensation through calculating an uplink transmit frequency according to the center frequency, the reference time, the feeder link delay, and the service link delay drift rate.

[0066] In some implementations, a reception time at the satellite is calculated as subtracting the feeder link delay from the reference time.

[0067] In some implementations, process 300 may involve processor 212 calculating a Doppler frequency shift as the center frequency times the service link delay drift rate times the reception time and calculating the UL transmit frequency by subtracting the Doppler frequency shift from the center frequency.

[0068] In some implementations, in obtaining the feeder link delay, process 300 may involve processor 212 performing certain operations. For instance, process 300 may involve processor 212 obtaining a common timing advance (TA). Then, process 300 may involve processor 212 deriving the feeder link delay as half the common TA.

[0069] FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may be an example implementation of schemes described above, whether partially or completely, with respect to the DL signal, the service link delay, the Doppler frequency drift rate, the Doppler frequency shift, and the Doppler frequency variation for UL timing compensation with the present disclosure. Process 400 may represent an aspect of implementation of features of communication apparatus 210. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410, 420, 430, 440, 450, and 460.

[0070] Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 400 may executed in the order shown in FIG. 4 or, alternatively, in a different order. Process 400 may be implemented by communication apparatus 210 or any suitable UE or machine type devices. Solely for illustrative purposes and without limitation, process 400 is described below in the context of communication apparatus 210.

[0071] Process 400 may begin at block 410. At block 410, process 400 may involve processor 212 of communication apparatus 210 measuring, via transceiver 216, a received frequency of a DL signal. Process 400 may proceed from block 410 to block 420.

[0072] At block 420, process 400 may involve processor 212 obtaining a service link delay. Process 400 may proceed from block 420 to block 430. At block 430, process 400 may involve processor 212 obtaining a Doppler frequency drift rate. Process 400 may proceed from block 430 to block 440. It shall be noted that the order of block 410, 420 and block 430 may be exchanged.

[0073] At block 440, process 400 may involve processor 212 calculating a Doppler frequency shift as the center frequency times the service link delay drift rate at the reception time. Process 400 may proceed from block 440 to block 450.

[0074] At block 450, process 400 may involve processor 212 calculating a Doppler frequency variation as the center frequency times the Doppler frequency drift rate times twice the service link delay. Process 400 may proceed from block 450 to block 460.

[0075] At block 460, process 400 may involve processor 212 calculating the UL transmit frequency by subtracting twice the Doppler frequency shift from the received frequency and adding the Doppler frequency variation to the received frequency.

[0076] FIG. 5 illustrates an example process 500 in accordance with an implementation of the present disclosure. Process 500 may be an example implementation of schemes described above, whether partially or completely, with respect to the common TA, the feeder link delay drift rate, the sampling rate, and the baseband signal for UL timing compensation with the present disclosure. Process 500 may represent an aspect of implementation of features of communication apparatus 210. Process 500 may include one or more operations, actions, or functions as illustrated by one or more of blocks 510, 520, 530, and 540.

[0077] Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 500 may executed in the order shown in FIG. 5 or, alternatively, in a different order. Process 500 may be implemented by communication apparatus 210 or any suitable UE or machine type devices. Solely for illustrative purposes and without limitation, process 500 is described below in the context of communication apparatus 210.

[0078] Process 500 may begin at block 510. At block 510, process 500 may involve processor 212 of communication apparatus 210 obtaining a common TA. Process 500 may proceed from block 510 to block 520.

[0079] At block 520, process 500 may involve processor 212 obtaining a feeder link delay drift rate. Process 500 may proceed from block 520 to block 530.

[0080] At block 530, process 500 may involve processor 212 adjusting a sampling rate according to the reference time, the common TA, the feeder link delay drift rate, and the service link delay drift rate. Process 500 may proceed from block 530 to block 540.

[0081] At block 530, process 500 may involve processor 212 performing a timing compensation through adjusting a baseband signal according to the common TA and the adjusted sampling rate.

[0082] In some implementations, process 500 may involve processor 212 calculating the feeder link delay drift rate based on an ephemeris of the satellite and a position of the network node.

[0083] In some implementations, process 500 may involve processor 212 calculating the feeder link delay drift rate based on the common TA.

[0084] In some implementations, in performing timing compensation, process 500 may involve processor 212 performing certain operations. For instance, process 500 may involve processor 212 receiving a close loop TA from the network node. Additionally, process 500 may involve processor 212 calculating a UE specific TA based on a position of the apparatus and an ephemeris of the satellite. Moreover, process 500 may involve processor 212 calculating the common TA based on the feeder link delay, the service link delay, the feeder link delay drift rate, and the reference time. Furthermore, calculating a transmit time for transmitting an uplink signal according to the close loop TA, the UE specific TA, and the common TA.

Additional Notes

[0085] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively associated such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as associated with each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being operably connected, or operably coupled, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being operably couplable, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0086] Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0087] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as open terms, e.g., the term including should be interpreted as including but not limited to, the term having should be interpreted as having at least, the term includes should be interpreted as includes but is not limited to, etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases at least one and one or more to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles a or an limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases one or more or at least one and indefinite articles such as a or an, e.g., a and/or an should be interpreted to mean at least one or one or more; the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of two recitations, without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to at least one of A, B, and C, etc. is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., a system having at least one of A, B, and C would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to at least one of A, B, or C, etc. is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., a system having at least one of A, B, or C would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase A or B will be understood to include the possibilities of A or B or A and B.

[0088] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.