Ground time virtually referenced positioning and timing system

Abstract

A platform with a signal generation unit and a transmitting unit. The signal generation unit is adapted to generate a spreading code sequence. The spreading code sequence has a reference chip with a rising edge and a falling edge. The signal generation unit is adapted to adjust the spreading code sequence to ensure that the rising edge or the falling edge of the reference chip arrives at a Virtual Timing Reference Station, VTRS, on a predetermined time (t.sub.ref,VTRS). The transmitting unit is adapted to engage with the signal generation unit and adapted to transmit the spreading code sequence. Further, a user device for receiving the transmitted spreading code sequence.

Claims

1. A platform comprising: a signal generation unit configured to generate a spreading code sequence, wherein the spreading code sequence has a reference chip with a rising edge and a falling edge, and wherein the signal generation unit is further configured to adjust the spreading code sequence to ensure that the rising edge or the falling edge of the reference chip arrives at a Virtual Timing Reference Station, VTRS, on a predetermined time (tref,VTRS); and a transmitting unit configured to engage with the signal generation unit and configured to transmit the spreading code sequence.

2. The platform according to claim 1, wherein the VTRS forms a center of a cell, and wherein the spreading code sequence is adjusted such that the reference chip of the spreading code sequence corresponds to the VTRS.

3. The platform according to claim 1, wherein the VTRS is a virtual point on earth or in space.

4. The platform according to claim 1, wherein the signal generation unit is configured to adjust the spreading code sequence to ensure that the rising edge or the falling edge of the reference chip arrives at other Virtual Timing Reference Stations, VTRSs, at different predetermined times.

5. The platform according to claim 4, wherein a length of the spreading code sequence is based on a shortest distance between VTRSs of a set of VTRSs comprising the VTRS and the other VTRSs.

6. The platform according to claim 1, wherein the signal generation unit is configured to compensate for the clock offset between a satellite local time and a system time of a corresponding Global Navigation Satellite System, GNSS.

7. The platform according to claim 1, wherein the signal generation unit is configured to compensate for the tropospheric and ionospheric delay at the VTRS on the predetermined time (tref,VTRS).

8. The platform according to claim 1, wherein the transmitted spreading code sequence comprises a spreading code counter which comprises a number of spreading codes starting from a first spreading code which comprises the reference chip.

9. The platform according to claim 1, wherein the signal generation unit is configured to compensate Doppler at the VTRS.

10. The platform according to claim 1, wherein the VTRS is not a fixed point on earth, but a moving point.

11. The platform according to claim 1, wherein the platform is a space-based station.

12. The platform according to claim 1, wherein the platform is a near earth platform.

13. The platform according to claim 1, wherein the platform is a static terrestrial platform which is configured for terrestrial mobile network infrastructures.

14. A user device configured to receive the spreading code sequence from the platform according to claim 1 and further configured to perform acquisition based on the spreading code sequence, wherein the VTRS is a priori known by the user device.

15. The user device according to claim 14, wherein the VTRS forms a trajectory which is known to the user device, wherein an exact position on the trajectory is known, which corresponds to an arrival of the reference chip of the spreading code sequence.

16. The platform according to claim 11, wherein the space-based station comprises a Navigation Satellite at a Medium Earth Orbit, MEO, a Low Earth Orbit, LEO, or a GEO stationary satellite, GEO.

17. The platform according to claim 12, wherein the near earth platform comprises a High-Altitude Platform, HAPS, a stratospheric Balloon, or a Drone.

18. The platform according to claim 13, wherein the static terrestrial platform comprises a Base Transceiver Stations, BTS, a terrestrial Navigation Beacon, a Pseudo-satellite, or Pseudolite.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) In the following, the preferred embodiments of the present disclosure are described with reference to the accompanying drawings; the same components are always provided with the same reference symbols.

(2) In the description of the present disclosure, detailed explanations of known connected functions or constructions are omitted, insofar as they are unnecessarily distracting from the present disclosure; such functions and constructions are, however, understandable to the skilled person in the technical field of the present disclosure. The accompanying drawings are illustrative of the present disclosure and are not to be construed as a limitation. The technical idea of the present disclosure is to be construed as comprising, in addition to the accompanying drawings, all such modifications, variations and variants.

(3) Other objects, features, advantages and applications become apparent from the following description of non-limiting embodiments regarding the accompanying drawings. In the drawings, all described and/or illustrated features, alone or in any combination form the subject matter disclosed therein, irrespective of their grouping in the claims or their relations/references. The dimensions and proportions of components or parts shown in the figures are not necessarily to scale; these dimensions and proportions may differ from illustrations in the figures and implemented embodiments.

(4) FIG. 1 schematically illustrates a typical GNSS signal generation chain implemented on-board a navigation satellite;

(5) FIG. 2 schematically illustrates the generation of a simple navigation signal structure;

(6) FIG. 3 schematically illustrates another evolution of the first navigation signal structure;

(7) FIG. 4 schematically illustrates a further evolution of the first and second navigation signal structure;

(8) FIG. 5 schematically illustrates the positions of one navigation satellite at different epochs;

(9) FIG. 6 schematically illustrates propagation of different chips with respect to satellite antenna phase center;

(10) FIG. 7 schematically illustrates propagation of different chips in all directions with respect to satellite antenna phase center;

(11) FIG. 8 schematically illustrates propagation of different chips in all directions with respect to satellite antenna phase center;

(12) FIG. 9 schematically illustrates a delayed transmission of the navigation signal component;

(13) FIG. 10 schematically illustrates the principle of code compensation;

(14) FIG. 11 schematically illustrates code compensation and an introduction of a Virtual Time Reference Station (cell);

(15) FIG. 12 schematically illustrates Line of Sight between the VTRS and the satellite as tangent to the earth surface;

(16) FIG. 13 schematically illustrates Line of Sight between the VTRS and the satellite as orthogonal to the earth surface;

(17) FIG. 14 schematically illustrates parameters to be used in order to quantitatively determine the difference in reception time between a User Device A located exactly at VTRS and a User Device B located a distance 1 from the VTRS;

(18) FIG. 15 schematically illustrates difference in reception time over satellite altitudes for different distances between the User Device B and the VTRS;

(19) FIG. 16 schematically illustrates Line of Sight between the VTRS and the satellite as inclined to the earth surface;

(20) FIG. 17 schematically illustrates parameters to be used in order to quantitatively determine the difference in reception time between a User Device A located exactly at VTRS and a User Device B located a distance 1 from the VTRS for a satellite being inclined with respect to the earth surface;

(21) FIG. 18 schematically illustrates synchronization error as function of the elevation angle, considering the distance between the User Device and the VTRS;

(22) FIG. 19 schematically illustrates probability to see at least one satellite above a specific elevation over user latitude, and probability to see at least two satellites above a specific elevation over user latitude;

(23) FIG. 20 schematically illustrates a sectorization of the earth;

(24) FIG. 21 schematically illustrates a sectorization of the earth with a smaller cell radius;

(25) FIG. 22 schematically illustrates geometrical positions of a satellite transmitting a positioning signal and a user equipment;

(26) FIG. 23 schematically illustrates time propagation between satellite and a VTRS;

(27) FIG. 24 schematically illustrates passive acquisition modules forming a dense mesh over the earth surface;

(28) FIG. 25 schematically illustrates a duration of Spreading Code sequence equal (left part) and smaller (right part) than an inter-cell distance;

(29) FIG. 26 schematically illustrates three situations for a maximal spreading code sequence length (left), an optimal spreading code sequence length (middle) and a non-sufficient spreading code sequence length (right);

(30) FIG. 27 schematically illustrates a first implementation of a code sequence counter;

(31) FIG. 28 schematically illustrates a second implementation of a code sequence counter;

(32) FIG. 29 schematically illustrates geographical variations of the actual received Doppler (minimal elevation angle of 5°);

(33) FIG. 30 schematically illustrates geographical variations of the actual received Doppler (minimal elevation angle of 40°);

(34) FIG. 31 schematically illustrates Doppler variations within each cell;

(35) FIG. 32 schematically illustrates a maximal Doppler variation after compensation;

(36) FIG. 33 schematically illustrates a moving VTRS with a reference trajectory known by the user device;

(37) FIG. 34 schematically illustrates a balloon as platform for implementing compensation techniques;

(38) FIG. 35 schematically illustrates a High Altitude Platform Station as platform for implementing compensation techniques;

(39) FIG. 36 schematically illustrates a terrestrial station as platform for implementing compensation techniques; and

(40) FIG. 37 schematically illustrates an application of the code compensation when applied to HAPS.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

(41) The figures are partially schematic, said essential properties and effects are clearly shown enlarged or scaled down in part to clarify the functions, active principles, embodiments and technical characteristics. Every operation, every principle, every technical aspect and every feature that/which is disclosed in the figures or in the text is/can be combined with all claims, each feature in the text and the other figures, other modes of operation, principles, technical refinements and features that are included in this disclosure, or result from it, so that all possible combinations are assigned to the devices and methods described. They also include combinations of all individual comments in the text, that is, in each section of the description, in the claims and combinations between different variations in the text, in the claims and in the figures, and can be made to subject-matter of further claims. The claims do not limit the disclosure and therefore the possible combinations of all identified characteristics among themselves. All features disclosed are explicitly also individually and in combination with all other features disclosed herein.

(42) Accordingly, while further examples are capable of various modifications and alternative forms, some particular examples thereof are shown in the figures and will subsequently be described in detail. However, this detailed description does not limit further examples to the particular forms described. Further examples may cover all modifications, equivalents, and alternatives falling within the scope of the disclosure. Like numbers refer to like or similar elements throughout the description of the figures, which may be implemented identically or in modified form when compared to one another while providing for the same or a similar functionality.

(43) It is understood that when an element is referred to as being “connected” or “coupled” to another element, the elements may be directly connected or coupled or via one or more intervening elements. If two elements A and B are combined using an “or”, this is to be understood to disclose all possible combinations, i.e. only A, only B as well as A and B. An alternative wording for the same combinations is “at least one of A and B”. The same applies for combinations of more than 2 elements.

(44) The terminology used herein for the purpose of describing particular examples is not intended to be limiting for further examples. Whenever a singular form such as “a,” “an” and “the” is used and using only a single element is neither explicitly or implicitly defined as being mandatory, further examples may also use plural elements to implement the same functionality. Likewise, when a functionality is subsequently described as being implemented using multiple elements, further examples may implement the same functionality using a single element or processing entity. It is further understood that the terms “comprises,” “comprising,” “includes” and/or “including,” when used, specify the presence of the stated features, integers, steps, operations, processes, acts, elements and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, processes, acts, elements, components and/or any group thereof.

(45) Unless otherwise defined, all terms (including technical and scientific terms) are used herein in their ordinary meaning of the art to which the examples belong.

(46) The platform, the compensation technique(s), the system and the user device will now be described with respect to the embodiments.

(47) In the following, without being restricted thereto, specific details are set forth to provide a thorough understanding of the present disclosure. However, it is clear to the skilled person that the present disclosure may be used in other embodiments, which may differ from the details set out below.

(48) The present disclosure may often refer to Global Navigation Satellite System (GNSS) whose Space Segment comprises Medium Earth Orbit (MEO) satellites, and may in particular use illustrations based on MEO satellites. This is to ease the comprehension of the underlying concept. However, the present disclosure is not restricted to this type of MEO platform, but can also be applied to other types of space-based platforms, such as Low Earth Orbit (LEO) or Geostationary Earth Orbit (GEO) satellites or any alternative near-earth platforms such as High Altitude Platform Stations (HAPS), a Balloon or Drones. The present disclosure can even be proposed for terrestrial “static” platforms such as Base Transceiver Stations (BTS) used in general for terrestrial mobile network infrastructures, or such as terrestrial Navigation Beacons, also called Pseudo-satellites or Pseudolites.

(49) FIG. 1 schematically illustrates a typical GNSS signal generation chain implemented on-board a navigation satellite. The GNSS signal generation chain of FIG. 1 comprises an on-board Frequency and Time Generation Unit (FTGU), encompassing one or more highly stable clocks (typically Atomic clocks) and responsible to provide to the other elements of the chain (also called payload units) a very stable timing or frequency source.

(50) The GNSS signal generation chain of FIG. 1 further comprises an on-board Navigation Signal Generation Unit (NSGU), responsible to generate the navigation signal transmitted by the satellite. The signal generation unit from the description above may be referred herein as the NSGU. The satellite can transmit one or more navigation signals simultaneously. Thus, the NSGU is capable of generating those navigation signals, also called signal components. For example, the satellites of the GPS system generates and transmits the GPS-C/A, L1C signals in the frequency band [1559-1591 MHz] with a reference carrier frequency of f.sub.carrier=1575.742 MHz, while the Galileo system generates and transmits the E1-B and -C components in the same frequency band. In the following the NSGU is especially responsible to generate the corresponding signal components at Baseband, to up-convert them to the RF frequency (e.g. 1575.742 MHz), and to multiplex them. The physical implementation of the aforementioned functionalities (BB generation, Up-Conversion and multiplexing) is specific to each navigation system/satellite and can be performed in independent or combined units, and the analogue to digital interface (with a Digital-to-Analogue Converter, DAC) can also take place at different places of the signal generation chain. Nevertheless, the aforementioned functionalities can all be encountered in a generic Navigation Signal Generation Unit.

(51) The GNSS signal generation chain of FIG. 1 further comprises a navigation antenna responsible to radiate the generated navigation signal components towards the earth. The antenna phase center may be the geometrical reference point for the navigation signal transmission. The transmitting unit from the description above may be part of the NSGU and the navigation antenna or may be the navigation antenna.

(52) The generic signal generation chain for a GNSS satellite can be employed on-board LEO, HAPS, or Drones. The main difference may be the dimension of the antenna, and possibly the range for the transmit power of the corresponding navigation signals. This generic signal generation chain can also be used in Base Transceiver Stations (BTS) or in pseudolites.

(53) In GNSS, the structure of each Navigation Signal Component, at baseband, comprises a spreading sequence, composed of N elementary binary symbols also called chips. Each spreading sequence can, but does not have to be modulated with symbols. In absence of symbol modulation, i.e. when the spreading sequence is not modulated, the corresponding symbol-less signal component is called Pilot component. The symbols can but do not have to be mapped into binary data, by applying a so-called coding technique such as convolutive coding or LDPC (which are the most encountered types of coding in navigation signals). Coding techniques are especially suited to improve coding performances. The spreading sequence can itself be composed of a first layer of spreading code, called primary code, or alternatively it can be obtained by combining a primary code layer and a second layer of secondary codes, where each primary code sequence is modulated with one chip of the secondary code sequence. Further, the pulse waveform of each chip of the primary sequence can take the form of a simple Binary Phase Shift Keying (BPSK) waveform, or a more complex waveform such as a Binary-offset-Carrier (BOC), or another type of waveform not explicitly described.

(54) The former description provides main characteristics and constituents of the most encountered navigation signals. In FIGS. 2 to 4, three typical signal structures of navigation signals are shown.

(55) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 1 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described below (e.g. FIGS. 2-37).

(56) FIG. 2 schematically illustrates the generation of a simple navigation signal structure, composed of a binary sequence comprising N chips, and which is modulated with a symbol. The chip rate f.sub.c equals N×f.sub.0, where f.sub.0 equals 1,023 MCps, and the symbol rate equals f.sub.s=f.sub.c/N. The chip duration T.sub.c is equal to the inverse of the chip rate T.sub.c=1/f.sub.c. FIG. 2 represents N.sub.s different symbol epochs. The coding process used to generate symbol on the basis of binary data with data rate f.sub.d is also represented in FIG. 2. The Coding Rate (CR) represents the ratio between the data and symbol rate (the Coding Rate is for example ½ for the typical convolutive coding rate applied by GPS or Galileo data signal components). In absence of coding, one binary data is represented by one binary symbol directly. In absence of symbol modulation, the navigation signal structure at baseband is just the repetition of primary codes, concatenated one after the other, yielding a Pilot or data-less component. The functional blocks for the Primary Code Generation, and the Symbol Data generation are both fed with the clock signal generated by the FTGU.

(57) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 2 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIG. 1) or below (e.g. FIGS. 3-37).

(58) FIG. 3 schematically illustrates (a second navigation signal structure) another evolution of the first navigation signal structure, since it includes the aforementioned two layers of the spreading sequence. The primary code comprising N chips is modulated with symbols of the secondary sequence comprising N.sub.sc secondary codes. In that case, the data rate f.sub.d equals the chip rate (of the primary sequence) divided by (N×N.sub.sc) and multiplied with the Coding Rate, CR. [000100] More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 3 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-2) or below (e.g. FIGS. 4-37).

(59) FIG. 4 schematically illustrates a further evolution of the first and second navigation signal structure, since it includes the application of a pulse waveform for the chip of the binary sequence (i.e. primary sequence). For illustration, a BOC(1,1) pulse waveform is applied. In that case each binary chip of duration T.sub.c is replaced by two plateaus of duration T.sub.c/2 each, one with amplitude of +1 and a second one with amplitude −1 (this is also represented on the bottom of FIG. 3).

(60) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 4 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-3) or below (e.g. FIGS. 5-37).

(61) The generation and transmission of the GNSS signals is typically performed continuously over the time and path of the GNSS satellite, meaning that the stream of navigation signals as “concatenation of spreading sequences modulated with symbol” is leaving continuously the phase center of the navigation antenna. This is illustrated in FIG. 5 which depicts at different epochs t.sub.1, t.sub.2 and t.sub.3 the positions of one navigation satellite for a displacement direction from right to left, as well as the propagation of two specific chips, with index 1 and K, of a spreading sequence of one navigation signal component. For this illustrative example, K represents the last chip of the spreading sequence comprising 1023 chips with duration T.sub.c=1 μs. K can also be any of the chips of spreading sequence. The chip of index 1, highlighted with a black colored cell, represents the first chip of the spreading sequence of the corresponding navigation signal component, which is used later as “reference chip”. The K.sup.th=1023.sup.th chip is highlighted with a grey colored cell. In FIG. 5, the direction of the signal propagation from the satellite (at each epoch) towards the earth center is also indicated. When the epochs t.sub.1, t.sub.2 and t.sub.3 are close (differences expressed in seconds), then the corresponding directions of signal propagation may be almost collinear. However, due to the small radius of the circular orbit relative to the earth radius (in this exemplary illustration), the corresponding direction are however not “parallel”. This is only a consequence of the dimensions used for this exemplary illustration. Furthermore, the position of the first chip is illustrated in FIG. 5, for the epochs t.sub.1, t.sub.2 and t.sub.3. It means that the actual satellite position when the K.sup.th chip is transmitted may have changed with respect to the satellite position when the first chip was transmitted 1023 chips (or equivalently 1 ms) earlier with a distance depending on the along-track velocity of the satellite. For example, a GPS satellite with a Semi-Major Axis (SMA) of 26400 km, the along-track velocity is given by:

(62) $v=\sqrt{\frac{\mathrm{GM}}{\mathrm{SMA}}}=\sqrt{\frac{3.986E14}{29600E3}}=3.7\mathrm{km}\text{/}s$

(63) Assuming a chip rate of f.sub.c=1 MCps, or equivalently a chip duration of T.sub.c=1 μs, the satellite may have moved by 3.9 mm during the transmission of one chip. For 1023 chips (which corresponds to transmission between the 1.sup.st and 1023.sup.th chip), or 1 ms, the aforementioned distance becomes 3.9 m. Similarly for a LEO satellite at an altitude of 800 km (SMA of 7180 km), the LEO satellite may have moved by 7.45 mm during the transmission of one chip, and 7.45 m during transmission of a spreading sequence of 1023 chips. For sake of simplification, the satellite is assumed at the same position when transmitting the K.sup.th=1023.sup.th chip. Furthermore, the Sagnac effects due to the earth rotation are not accounted for this simplification.

(64) Further, during epoch t.sub.1 and t.sub.2 two additional chips (K+1 and K+2) may have been sent from the satellite. Similarly, between t.sub.2 and t.sub.3, two additional chips (K+3 and K+4) may have been sent from the satellite. The exact number of additional chips transmitted between epochs depends thus on the satellite orbit (velocity, altitude) and on the interval duration between epochs (t.sub.1 and t.sub.2) or (t.sub.2 and t.sub.3), which are expressed in seconds in this assumption.

(65) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 5 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-4) or below (e.g. FIGS. 6-37).

(66) FIG. 6 schematically illustrates propagation of different chips with respect to satellite antenna phase center. This further representation is a close-in of FIG. 5. In addition to FIG. 5, the intersection between the line joining the Satellite and the Earth Centre and the earth surface itself at each epoch is also represented, together with circles around this intersection point. For this example the rising edge of the chip 1 arrives at the intersection between the line joining the Satellite and the Earth Centre and the earth surface at the first epoch, which is denoted “Location A”, for epoch t.sub.1.

(67) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 6 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-5) or below (e.g. FIGS. 7-37).

(68) FIG. 7 and FIG. 8 (Close-In) schematically illustrate in complement to FIG. 5 and FIG. 6 the propagation of the different chips in all directions with respect to satellite antenna phase center. Such propagations are symbolized with arcs in dashed lines since the propagation in the medium is considered isotropic. Those arcs are centered at the antenna phase center, with a radius equal to the distance between the antenna phase center and the rising edge of the chip at the given epoch. One specific direction of interest is the direction between the phase center of the antenna and the Location A. For the assumed geometry, the number of chips that have passed the “Location A” at epoch t.sub.2 or at epoch t.sub.3 depend on geometrical parameters such as the satellite orbit (e.g. altitude), the chip rate, but also the distance between location A and the satellite at those specific epochs t.sub.2 or t.sub.3. This is due to the reception of the first chip of the spreading sequence at epoch t.sub.1. In FIG. 8, 11 chips may have been passed at epoch t.sub.2 at location A, since the reception of the first chip at epoch t.sub.1.

(69) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiments shown in FIGS. 7 and 8 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-6) or below (e.g. FIGS. 9-37).

(70) In one or more aspects, the transmission of the navigation signal component and especially the underlying chip stream may be disciplined in such a way that the latter arrives at a specific location and at a specific time epoch. This is illustrated in FIG. 9. FIG. 9 schematically illustrates a delayed transmission of the navigation signal component. The transmission of the navigation signal component may be “delayed” in such a way that the rising edge of the first chip of the navigation signal component arrives at the “Location A” at a given reference time. In order to achieve this, a so-called “code compensation” may be applied to the navigation signal generation unit before epoch t.sub.2. The corresponding “code compensation” is also represented in FIG. 9. The code compensation may be understood as the distance between the “chip K” of the un-compensated spreading sequence (grey cell) projected onto the direction between satellite position and Location A at the reference epoch, and “chip K” of the compensated spreading sequence. The corresponding code compensation has the same value as the number of chips that have passed the “Location A” at epoch t.sub.2, since reception of the first chip at epoch t.sub.1, also represented in FIG. 8. A similar code compensation may also be represented at the “Location A” at epoch t.sub.3 (instead of t.sub.2), as shown in FIG. 9 in order to guarantee that the rising edge of the first chip of the navigation signal component arrives.

(71) FIG. 9 represents the compensation that shall be applied to ensure reception of the rising edge of the chip 1 at epoch t.sub.1, t.sub.2 or t.sub.3.

(72) For epoch t.sub.1 it is not necessary to apply the corresponding code compensation, since the rising edge of the first chip already arrives at Location A. For epoch t.sub.2 and t.sub.3, it is necessary to apply the corresponding code compensation, to ensure that the rising edge of the first chip arrives at Location A.

(73) In the former description, the rising edge of the first chip is selected for the code compensation. Alternatively, it is possible to consider the falling edge of the first chip. Furthermore, the first chip of the spreading sequence is used to derive the code compensation applied on-board the satellite. Another chip of the spreading sequence could be used in place as “reference chip” as long as its definition is un-ambiguous within the spreading sequence. This is especially true for spreading sequences which are not periodic (case of cyphered spreading sequences).

(74) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 9 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-8) or below (e.g. FIGS. 10-37).

(75) FIG. 10 schematically illustrates the principle of code compensation (at a wider scale). The concept of code compensation is to ensure synchronization at reception for a specific earth position. The exact location on the earth for which the rising edge of the “reference chip” is received at a given epoch may be called Virtual Time Reference Station (VTRS). No “physical” reference station (i.e. receiver, facility, . . . ) needs to be located at the position of the VTRS. Furthermore, the epoch at which the rising edge of the “reference chip” is received at VTRS, may be called Reference Epoch, t.sub.ref,VTRS. The corresponding appellations are introduced in FIG. 11.

(76) In both navigation signal acquisition and tracking modes, the receiver usually computes the correlation between the received signal and a replica of it. The replica is generated with the same spreading sequence and it is offset with a so-called Code Delay estimate, τ.sub.est which estimates the actual Code Delay, τ.sub.act and multiplied with an exponential composed of the estimate Carrier Frequency, f.sub.carrier,est, which estimates the actual (or apparent) f.sub.carrier,act and Carrier Phase Estimate φ.sub.est:

(77) $r_{\mathrm{rep}}\left(t\right)=\stackrel{\_}{c}\left(t-{\tau }_{\mathrm{est}}\right)\times e^{j\left(2\pi f_{\mathrm{carrier},\mathrm{est}}\left(t-{\tau }_{\mathrm{est}}\right)+{\phi }_{\mathrm{est}}\right)}$$\stackrel{\_}{c}\left(t\right)=\underset{i=1}{\overset{N_c}{.Math.}}\left(c_i\times p_c\left(t-i\times T_c\right)\times {\Pi }_{T_c}\left(t-i\times T_c\right)\right)$${\Pi }_{T_c}\left(u\right)\{\begin{array}{cc}1& \mathrm{for}0\le u\le T_c\\ 0& \mathrm{else}\end{array}$

(78) In the former expressions, c represents the spreading code composed of N.sub.c chips. Each chip value is equal to c.sub.i and is modulated with a pulse waveform p.sub.c (for example, BPSK or BOC). Furthermore, the function Π.sub.T is the so-called “temporal door” which is 1 within the interval [0,T] and 0 outside.

(79) The following distinctions apply between the acquisition and tracking processing steps. In acquisition, the user device aims at providing coarse estimation of both code delay (with the code delay estimate τ.sub.est) and carrier frequency (with the carrier frequency estimate f.sub.carrier,est) which are un-known if not existent a-priori. Without an accurate estimate of the actual carrier frequency f.sub.carrier,act, the carrier phase, φ.sub.est is not estimated. The receiver (for example the user device) knows the reference carrier frequency, f.sub.carrier at transmission (e.g. 1575.742 MHz), but neither the additional Doppler (typically ranging between [−5 KHz and 5 KHz]) due to the dynamic (velocity) between satellite and user device, nor the actual frequency error offset (typically ranging between [−1 KHz and 1 KHz]), due the local clock stability. Therefore, the f.sub.carrier,est can also be expressed as [f.sub.carrier+f.sub.Doppler,est], where f.sub.Doppler,est encompasses both Doppler and local clock frequency estimates. In acquisition mode, the accuracy for the code delay estimation error, (i.e. root mean square (r.m.s.) of τ.sub.est) is typically a fraction of a chip: code delay hypotheses spaced every half chip (T.sub.c/2) or quarter of chip (T.sub.c/4) are typically tested. Similarly, the accuracy for the apparent Doppler estimation error (i.e. r.m.s. of f.sub.carrier,est) is expressed in tenth of Hertz: Doppler hypotheses are typically spaced with 10 to 50 Hz. Beside the accuracy of code and Doppler hypothesis, it may also be necessary to introduce different acquisition modes. In the so-called cold acquisition mode, the user device has no a priori knowledge on its position and its local time. It means that the user device has to test all possible Doppler offset but also code offsets corresponding to the spreading code sequence. Assuming a spreading code sequence of 1023 as for the GPS C/A signal components (resp. 4096 chip as for the Galileo E1-B or E1-C signal components), then 1023×2 (resp. 4096×2) for half chip spaced code hypotheses may be tested. In warm or hot acquisition modes, the receiver has a better knowledge on its position and time, together with the position of the transmitting navigation satellites, provided in so-called Almanacs. Only a limited number of Code and Doppler hypotheses may be tested.

(80) In tracking, the user device has already gained a very good estimation, f.sub.carrier,est, of the actual carrier frequency f.sub.carrier,act, (i.e. including Doppler effects) for example with a Frequency Lock Loop (FLL) and of the code Delay, τ.sub.est, for example with a Delay Lock Loop (DLL). In comparison to the acquisition, the accuracy for code delay estimation error is expressed in meters or equivalently T.sub.c/100 as order of magnitude. Similarly, the Doppler estimation error is expressed in Hz. In tracking mode, it is possible and necessary to estimate the carrier phase φ.sub.est (contrarily to the acquisition phase), for example with a Phase Lock Loop (PLL) or a Costas Loop. The carrier phase estimate is used to determine the symbol or data modulated onto the spreading sequences, or for very precise positioning where the phase estimate is used in combination to the code estimate in order to provide a very precise position of the user device (precision of a few decimeters).

(81) For both, acquisition and tracking phases, the user device may compute a correlation between the received signal, and a replica generated with the estimate for code delay, carrier frequency and carrier phase (applicable for tracking):

(82) $R\left(\mathrm{\Delta \tau },\Delta f_{\mathrm{carrier},}{\mathrm{\Delta \phi }}_{\mathrm{carrier}}\right)=\frac{1}{T_{\mathrm{int}}}{\int }_0^{T_{\mathrm{int}}}{r}_{\mathrm{rx}}\left(t\right)\times r_{\mathrm{rep}}\left(t\right)\mathrm{dt}\left(\mathrm{\Delta \tau },\Delta f_{\mathrm{carrier},}{\mathrm{\Delta \phi }}_{\mathrm{carrier}}\right)=\frac{1}{T_{\mathrm{int}}}{\int }_0^{T_{\mathrm{int}}}\begin{array}{c}\left(\stackrel{\_}{c}\left(t-{\tau }_{\mathrm{est}}\right)\times e^{j\left(2\pi f_{\mathrm{carrier},\mathrm{est}}\left(t-{\tau }_{\mathrm{est}}\right)+{\phi }_{\mathrm{est}}\right)}\right)\times \\ \left(\stackrel{\_}{c}\left(t-{\tau }_{\mathrm{act}}\right)\times e^{j\left(2\pi f_{\mathrm{carrier},\mathrm{act}}\left(t-{\tau }_{\mathrm{act}}\right)+{\phi }_{\mathrm{act}}\right)}\right)\mathrm{dt}\end{array}$$\mathrm{\Delta \tau }={\tau }_{\mathrm{act}}-{\tau }_{\mathrm{est}},\Delta f_{\mathrm{carrier}}=f_{\mathrm{carrier},\mathrm{act}}-f_{\mathrm{carrier},\mathrm{est}}\mathrm{and}{\mathrm{\Delta \phi }}_{\mathrm{carrier}}={\phi }_{\mathrm{act}}-{\phi }_{\mathrm{est}}$

(83) In the equations above:

(84) r.sub.rx(t) represents the received navigation signal reduced here, for simplification, to a single navigation signal component;

(85) r.sub.rep(t) represents the replica generated at user device;

(86) T.sub.int represents the coherent integration time, usually taken equal to the spreading code period (or a fraction of the spreading code period), or the symbol duration (applicable for data modulated GNSS signals); and

(87) Δτ, Δf.sub.carrier and Δφ respectively represent the estimation errors for the code, actual carrier frequency and carrier phase, as difference between the estimated code delay (τ.sub.est) and the actual code delay (τ.sub.act), the estimated carrier frequency (f.sub.carrier,est) and the actual carrier frequency (f.sub.carrier,act) and the estimated carrier phase (φ.sub.est) and actual carrier phase (φ.sub.act).

(88) The “granularity” for the code, carrier frequency and carrier phase estimate may depend on the acquisition or tracking phase as explained above.

(89) In acquisition phase, the receiver may compute the square of the absolute correlation function (suppressing in that way the dependency with respect to carrier phase) evaluated for each pair of code and Doppler hypotheses, yielding to an elementary power detector. In order to improve the detection performance different elementary power detectors can be added non-coherently, all calculated for the same Code and Doppler hypothesis, yielding to an aggregate power detector.

(90) In tracking phase, the receiver may compute the correlation function for different code offsets surrounding the estimated one, τ.sub.est. For code offsets lower than the estimated one (τ.sub.est), for example τ.sub.est-T.sub.c/2, and/or τ.sub.est-T.sub.c/4, and/or τ.sub.est-T.sub.c/U (with U integer), . . . the corresponding correlation function is called “Early Correlation function”, also called “Early Correlation channel”. For code offsets higher than the estimated one (τ.sub.est), for example τ.sub.est+T.sub.c/2, and/or τ.sub.est+T.sub.c/4, and/or τ.sub.est+T.sub.c/U (with U integer), . . . the corresponding correlation function is called “Late Correlation function”, also called “Late Correlation Channel”. The receiver may then combine the corresponding Early and Late correlation functions in order to generate a so-called discriminator output which may serve for estimating the code delay τ.sub.est, for example within a Code Delay Lock Loop (DLL). The so-called “Prompt Correlation channel” calculated with the code delay estimate τ.sub.est, is used to retrieve the sign of the symbol modulated onto the navigation signal component, which is later used to derive the data information with demodulation techniques. As explained earlier the “Prompt Correlation Channel” can also serve for estimating the carrier phase, φ.sub.est, for example by applying the atan operator to the ratio of the imaginary and real parts of the prompt correlation channel: φ.sub.est=atan(Imag(R.sub.Prompt)/Real(R.sub.Prompt)), which corresponds to the Carrier Phase estimator applied by Costas Loop (other algorithms not disclosed in this document can be used to retrieve the carrier phase).

(91) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiments shown in FIGS. 10 and 11 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-9) or below (e.g. FIGS. 12-37).

(92) FIG. 12, FIG. 13 and FIG. 16 schematically illustrate user devices in the vicinity of a VTRS. In FIG. 12 the Line of Sight (LoS) between the VTRS and the satellite is tangent to the earth surface. In FIG. 13 the LoS is perfectly orthogonal with respect to the earth surface. In FIG. 16, the LoS is inclined with respect to the earth surface. Furthermore, on each figure the wavefronts corresponding to the rising edge of the chips are represented by arcs.

(93) In FIG. 12, different user devices are represented in the vicinity of the VTRS. First, a “user device A” is assumed located exactly at VTRS. The corresponding user device may compute a correlation with a replica r.sub.rep(t) generated with the “un-shifted” spreading sequence c, when τ.sub.est=0. This may be understood such that the chip stream starts with the first chip 1 of the spreading sequence. Furthermore, this replica keeps unchanged, while the received signal enters the correlation engine continuously, which enables to test the different code hypotheses at a sample rate. This type of acquisition technique is also called “passive acquisition”, since the user device “waits” that the received signal becomes synchronized to the un-shifted spreading sequence, prepared in the acquisition module. When the correlation function generated in that way, reaches a peak, it means that the rising edge of the spreading sequence of the received signal r.sub.rx(t) exactly arrives at the VTRS, i.e. the User Device, and at the t.sub.ref,VTRS epoch. It means that the system time has been provided or “transferred” to the User Device, which can deduce the system time based on this event. A strong limitation to this “ideal” case is that the User Device usually ignores its exact position and especially in a cold acquisition.

(94) The present disclosure is not limited to the case of a passive acquisition technique, but can also serve for active acquisition techniques. In a typical active acquisition technique, the user device does not keep the replica unchanged, but generates a different replica, according to the code and Doppler hypotheses to be tested, and correlates this newly generated replica with a completely new batch of received signal samples. The consequence is a lower rate for testing Code and Doppler hypotheses, but a lower complexity, when compared to the passive acquisition technique. When applying an active acquisition, it is possible to acquire a segment of the navigation signal transmitted with compensation, rather than the start of the corresponding navigation signal for passive acquisition. Considering that this segment of navigation signal can be related to its beginning, using a time-tag solution, such as a spreading code counter, or considering a very long spreading sequence, then it is also possible to synchronize the user device to the System Time, via this alternative time transfer approach.

(95) Further, a “user device B” is located at “one chip distance” (for example 300 m if one considers the chip duration T.sub.c equal to 1 μs for the GPS C/A signal), and that the LoS is tangent to the earth surface (FIG. 12). If the “User Device B” is located 300 m from the VTRS and between the VTRS and satellite, the difference of reception time between the “User Device B” and the VTRS corresponds to the distance between VTRS and “User Device B”, which may be expressed as algebraic value in seconds. It means that the correlation peak calculated with the un-shifted spreading sequence, may be observed at [t.sub.ref,VTRS-T.sub.c], on an “absolute” time scale. If the User Device B is located “one chip distance” away from the VTRS and in the opposite side with respect to satellite, the correlation peak may be observed at [t.sub.ref,VTRS+T.sub.c] on an “absolute” time scale. This can be repeated for different positions of the user device as shown in FIG. 12. Hence, this figure also shows that the wavefront corresponding to the rising edge of the reference chip defines a so-called “Reference Iso-chrone” representing the t.sub.ref,VTRS. Any wavefront seen with 1 chip in advance or delay from the “Reference Iso-chrone” may correspond to 1 μs in advance or delay with respect to t.sub.ref,VTRS, referred to the VTRS.

(96) In FIG. 13, the satellite is located exactly at Zenith of VTRS. In FIG. 13 the “User Device A” located exactly at VTRS and “User Device B” located at the same position with respect to “User Device A” (i.e. VTRS) may be the same as in FIG. 12 before. The “User Device A” and “User Device B” also each prepare a replica r.sub.rep(t) generated with the “un-shifted” spreading sequence c (here considering a passive acquisition strategy). The main difference with respect to FIG. 12 is that, due to the very high inclination of Line of Sight between VTRS and satellite, the difference in reception time of the wavefront corresponding to the reference chip at VTRS (i.e. User Device A) and “User Device B” may be much smaller than in the case of FIG. 12. This difference of reception time can be measured as the difference of time (on the absolute time scale) when the correlation function reaches a peak at User Device A and when the correlation function reaches a peak at User Device B. The corresponding difference in reception time is a function of the satellite altitude: the higher the satellite altitude located at zenith of user device, the smaller the difference of reception time.

(97) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiments shown in FIGS. 12 and 13 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-11) or below (e.g. FIGS. 14-37).

(98) FIG. 14 schematically illustrates parameters to be used in order to quantitatively determine the difference in reception time between a User Device A located exactly at VTRS and a User Device B located a distance 1 from the VTRS, in the specific case when the satellite is at Zenith of VTRS. In particular, L represents the distance between the satellite and the center of the earth, which is modelled as a perfect sphere of Radius R. The distance between the satellite and the User Device A, located at VTRS, and at Nadir of Satellite is P. The distance between the VTRS and the User Device B is denoted 1. Q and S represent the distance between the satellite and the User Device B, when it is located either on the left (S) or right (Q) side of the VTRS in the plane defined by the satellite, the earth center and user device B. Due to the symmetrical configuration, applicable when the satellite is at Zenith of the VTRS, Q=S.

(99) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 14 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-13) or below (e.g. FIGS. 15-37).

(100) FIG. 15 schematically illustrates difference in reception time over satellite altitudes for different distances between the User Device B and the VTRS. Based on the models described in FIG. 14, FIG. 15 shows that for typical satellite altitudes corresponding to GNSS system (between 20E3km and 25E3km), the difference in reception time is below 8 μs for a distance 1 smaller or equal to 150 km. This difference in reception time corresponds to the maximal error for the time transfer (synchronization to the system time). It increases to 25 μs for 300 km and reaches 300 μs for 1000 km. The difference of reception time shows the same order of magnitude for GEO satellites but is still slightly smaller due to the higher distance between satellite and VTRS, for example the user device A. It is worthwhile mentioning that for the specific case of GEO satellites, users at Nadir of the GEO satellites belong to the equatorial plane. On the opposite, for LEO satellites the difference in reception time increases as a direct consequence of the lower distance between the LEO satellite and the VTRS, for example the user device A. In that case, the main assumption of “earth surface flatness” applies for a smaller distance, 1, between user device B and VTRS, for example user device A. For other platforms, closer to the earth, such as HAPS, stratospheric Balloons or Drones, the distance 1 satisfying the “earth surface flatness” condition becomes even smaller. Nevertheless, the proposed scheme can still be applied for a service provided within a smaller surface area just below each HAPS, Balloon or Drone platform.

(101) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 15 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-14) or below (e.g. FIGS. 16-37).

(102) FIG. 16 describes the situation when the line of sight to the satellite is inclined with respect to the earth surface. The “User Device A”, located exactly at VTRS and the “User Device B” located at the same position with respect to “User Device A” (i.e. VTRS) as in the figures above. Similarly to FIG. 14, the parameters used to determine quantitatively the difference in reception between the User Device A located exactly at VTRS and the User Device B located at a distance 1 from the VTRS are represented in FIG. 17. Especially important is the distance identified with (S-Q), and resp. (S-P), which corresponds to the time transfer error for the specific geometrical configuration according to the relative position of the User Device B with respect to the VTRS. Based on these parameters, FIG. 18 schematically illustrates the synchronization error as function of the elevation angle, considering the distance between the User Device and the VTRS. Here, following distances are considered: 300 m, 3 km, 30 km, 150 km, 192.96 km, 380.65 km and 1500 km. For the quantitative assessments the orbital parameters of a typical GNSS system in a Medium Earth Orbit (MEO) orbit are considered. The black curve in FIG. 18 corresponds to the situation when the user device is located between the VTRS and the satellite (case “S-P”), while the grey curves correspond to the situation when the VTRS is located between the User Device and the Satellite (case “Q-P”). In the legends the maximal synchronization error is also indicated, when the satellite is at zenith of VTRS (90° elevation from VTRS), or when it is tangent to the earth (0° elevation from VTRS), and finally when it shows a 50° elevation from VTRS. When the satellite elevation from VTRS is 0°, the synchronization error exactly corresponds to the distance 1 between the user device and the VTRS, which corresponds to the case in FIG. 12. The synchronization error is minimal when the satellite is at zenith of VTRS, which corresponds to the case in FIG. 13. The distance 1 equal to 192.96 km (resp. 380.65 km) represents a working point, since it corresponds to a synchronization error of ±0.5 ms (resp. ±1 ms).

(103) The special case of an elevation of 50° with respect to the VTRS has been selected because it is shown that for a typical GNSS constellation, that any user and therefore the VTRS sees a satellite with 100% probability with an elevation smaller or equal to 50°, except for users located at latitudes lower than 25° for which the aforementioned probability decreases from 90% downwards, and users above 80° for which the aforementioned probability decreases also from 90% downwards. The probability to see two satellites above a specific elevation is also presented in FIG. 19. Here the probability to see two satellites becomes much smaller.

(104) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIGS. 16, 17, 18 and 19 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-15) or below (e.g. FIGS. 20-37).

(105) FIG. 20 represents a sectorization of the earth with cells having a radius of 380.65 km, and a distance between cell centers of 2×380.65 km=761.3 km. Each VTRS is at the center of a “cell” with radius 380.65 km. This value is selected with respect to aforementioned calculations which show that any user away from the VTRS is able to recover the system time with an error of ±0.5 ms. It can be shown that P=1431 such cells exist. P represents the number of cells which cover the earth surface. Furthermore, FIG. 20 shows the footprints of each of the Q=24 GNSS satellites, when considering an elevation masking angle of 50°. Further, Q represents the number of satellites of the GNSS. The main orbital characteristics of the GNSS satellites are a Semi-Major Axis of 26400 km, and an inclination of 55 degrees. Here different grey colors are used to represent each of the 24 footprints. For example, 80 VTRS, and therefore cells can be defined, as part of the visibility footprint of the satellite with a minimal elevation of 50°.

(106) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 20 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-19) or below (e.g. FIGS. 21-37).

(107) FIG. 21 represents a similar representation but for a cell radius of 192.96 km (instead of 380.65 km). Here, each user belonging to this cell shall have a maximal synchronization error of ±1 ms. In that case, the number of cells increases to P=5408 cells, and on average 615 cells belong to a visibility footprint with 50 degrees in elevation.

(108) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 21 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-20) or below (e.g. FIGS. 22-37).

(109) FIG. 22 schematically illustrates geometrical positions of a satellite transmitting a positioning signal and a user equipment (herein also called user device), and different contributions to the pseudo-ranges for an exemplary LOS. Herein, reference is made to [“Understanding GPS Principles and Application”, Kaplan Artech House Publish, ISBN 0-89006-793-7], wherein similar notations are applied. This concerns especially the following parameters and variables applied in FIG. 22, and explained as follows:

(110) R.sub.r.sup.s represents a true (“Physical”) distance between a satellite and a user equipment;

(111) t.sub.s represents a time of transmission expressed in the System Time scale;

(112) t.sub.r represents a time of reception expressed in the System Time scale;

(113) τ.sub.s represents a clock offset between the satellite Local Time and the System Time scale and evaluated at time of transmission. Per convention the clock offset is positive when the clock is delayed with respect to time scale;

(114) τ.sub.r represents a clock offset between the receiver local time and the System Time scale and evaluated at time of reception;

(115) τ.sub.l.sup.s represents a contribution of a Ionosphere onto a propagation delay;

(116) τ.sub.T.sup.s represents a contribution of a Troposphere onto the propagation delay;

(117) τ.sub.MP.sup.s represents a contribution of a local Multipath onto the propagation delay estimation;

(118) τ.sub.RFI.sup.s represents a contribution of a local Radio Frequency Interference (RFI) onto the propagation delay estimation;

(119) τ.sub.N0.sup.s represents a contribution of thermal noise onto the propagation delay estimation;

(120) [x.sub.r y.sub.r z.sub.r].sup.T represents a coordinate vector of the user equipment to be estimated;

(121) [x.sub.s y.sub.s z.sub.s].sup.T represents a coordinate vector of a true satellite position; and

(122) [{circumflex over (x)}.sub.s ŷ.sub.s {circumflex over (z)}.sub.z].sup.T represents a coordinate vector of the predicted satellite position, which is usually computed (estimated) based on models computed in the central processing facility of a navigation system and encoded onto the navigation signal.

(123) Alternatively the predicted satellite position can also be computed based on models provided by another navigation service operator and made available to the user equipment via another mean, such as the internet. Alternatively, the predicted satellite position can also be generated by the user equipment itself, based on an orbit propagator.

(124) Assuming an “ideal” satellite and receiver/user equipment clock (free of drift), the distance between satellite and user equipment is given by the following equation, where c.sub.0 represents the speed of light:
R.sub.r.sup.s=c.sub.0.Math.(t.sub.r−t.sub.s)  (eq. 1)

(125) Due to the clock offsets at satellite and user equipment, the pseudo-range (PR) expression, without any additional perturbing contributions, can be derived by the former equation as:
PR.sub.r.sup.s=c.sub.0.Math.((t.sub.r+τ.sub.r)−(t.sub.s+τ.sub.s))=R.sub.r.sup.s+c.sub.0.Math.(τ.sub.r−τ.sub.s)  (eq. 2)

(126) The true satellite to user equipment distance can also be expressed as
R.sub.r.sup.s=√{square root over ((x.sub.s−x.sub.r).sup.2+(y.sub.s−y.sub.r).sup.2(z.sub.s−z.sub.r).sup.2)}  (eq. 3)

(127) (eq. 2) can be rewritten as follows, when accounting now for all other contributions to the pseudo-range measurement:
PR.sub.r.sup.s=√{square root over ((x.sub.s−x.sub.r).sup.2+(y.sub.s−y.sub.r).sup.2+(z.sub.s−z.sub.r).sup.2)}+c.sub.0.Math.(τ.sub.r−τ.sub.s)+Σ.sub.l.sup.s+τ.sub.T.sup.s+τ.sub.RFI.sup.s+τ.sub.MP.sup.s+τ.sub.N0.sup.s  (eq. 4)

(128) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 22 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-21) or below (e.g. FIGS. 23-37).

(129) FIG. 23 schematically illustrates time propagation between satellite and a VTRS. The Reference Station is virtual and similar pseudo-range measurement parameters can be expressed:

(130) both contributions for the multipath (τ.sub.MP,vtrs.sup.s) and thermal noise (τ.sub.N0,vtrs.sup.s) τ.sub.r at VTRS are not applicable here; and

(131) the time offset τ.sub.vtrs at VTRS is assumed zero, which means that the VTRS is exactly synchronized to the system time at reception of the ranging signal since the VTRS reflects (without drift) the system time.

(132) For the contributions for the Ionosphere (τ.sub.I,vtrs.sup.s) and troposphere (τ.sub.T,vtrs.sup.s) onto the delay two options are provided.

(133) The first option considers that both contributions are not part of the code compensation at VTRS. In that case, the user device experiences an “absolute” error accounting for both effects when synchronizing with the ranging signals transmitted by the satellite, and comprising the code compensation. Nevertheless, the application of estimation models for both Iono-sphere (e.g. Necquick Model) and Tropo-sphere (with the Zenithal Hydrostatic and Zenith Wet Delays) effects at user side enables reduction of corresponding contributions.

(134) The second option considers that both contributions are part of the code compensation at VTRS. It means that a User Device A, located at VTRS itself has not to account (i.e. correct) for both ionospheric and tropospheric delays, since already accounted in the compensation. For a User Device B not located exactly at VTRS, the synchronization error equals the sum of the difference between the actual ionosphere/tropospheric delays at User Device B and ionosphere/tropospheric delays at VTRS. The further the User Device B is away from the VTRS, the larger these effects.

(135) Based on these assumptions, the expression for the Pseudo-Range at VTRS becomes the following:

(136) Option 1, if the Tropospheric and Ionospheric delays (at VTRS) are not compensated at VTRS:
PR.sub.vtrs.sup.s=√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)}+c.sub.0.Math.(−τ.sub.s)+τ.sub.I,vtrs.sup.s+τ.sub.T,vtrs.sup.s  (eq. 5)

(137) Option 2, if the Tropospheric and Ionospheric delays (at VTRS) are compensated at VTRS:
PR.sub.vtrs.sup.s=√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)}+c.sub.0.Math.(−τ.sub.s)  (eq. 6)

(138) Based on these introductive works, the method used to derive the code compensation can be presented. Assuming no Ionospheric and Tropospheric contribution, then the first chip of the spreading sequence has to leave at time
t.sub.global.sup.s=t.sub.vtrs.sup.r,ref−((√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)})/c.sub.0)

(139) the satellite antenna phase center in order for this first chip to reach the VTRS at a reception reference time t.sub.vtrs.sup.r,ref. Here t.sub.global.sup.s is expressed in the System Time reference. Due to the clock offset τ.sub.s between the Satellite local time (i.e. clock) and the System Time reference, the first chip of the spreading sequence has to leave at time t.sup.s.sub.local, with
t.sub.local.sup.s=t.sub.vtrs.sup.r,ref−((√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)})/c.sub.0+(−τ.sub.s))

(140) where t.sub.local.sup.s is expressed in the Local System Time reference. Similarly, when considering the Ionospheric and Tropospheric contributions, then the first chip of the spreading sequence has to leave at time
t.sub.global.sup.s=t.sub.vtrs.sup.r,ref−((√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)})/c.sub.0+τ.sub.l,vtrs.sup.s+τ.sub.T,vtrs.sup.s)

(141) when expressed in the System Time reference, and at time
t.sub.local.sup.s=t.sub.vtrs.sup.r,ref−((√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)})/c.sub.0+(−τ.sub.s)+τ.sub.l,vtrs.sup.s+τ.sub.T,vtrs.sup.s)

(142) when expressed in the Local System Time reference. The clock offset τ.sub.s can either be accessed by the satellite directly from the user navigation message which is available at satellite for later broadcasting, or be provided to the satellite with a dedicated communication link.

(143) The code compensation τ.sub.comp then corresponds to the delay between the epoch of transmission (t.sup.s.sub.global or t.sup.s.sub.local) and the reference time at VTRS at t.sub.vtrs,ref. The code compensation serves to trigger the transmission of the spreading sequence, such that when the first chip of the spreading sequence leaves the antenna phase center at t.sup.s.sub.global (if expressed in the GNSS system time), or at t.sup.s.sub.local (if expressed in the satellite local time), then the first chip of the spreading sequence reaches the VTRS at t.sub.vtrs,ref. This later case shall correspond to the more realistic implementation since the satellite will use its local time to trigger the transmission of the spreading sequence. Hence, the code compensation consists then to apply a physical delay τ.sub.comp to the actual satellite clock offset, τ.sub.s. Based on equations (eq. 5) and (eq. 6), the corresponding code compensation is then equal to eq. 7, when the Iono- and Tropospheric Delays are compensated and eq. 8, when Iono- and Tropospheric Delays are not compensated.
τ.sub.comp=(√{square root over (x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)})/c.sub.0+(−τ.sub.s)+τ.sub.I,vtrs.sup.s+τ.sub.T,vtrs.sup.s  (eq. 7)

(144) In the following, the measured pseudo-range is derived for a user device which tracks navigation signal generated with code compensation. The general expression for the code pseudorange at user level, (eq. 4), once the code compensation is applied, becomes:
PR.sub.r.sup.s=√{square root over ((x.sub.s−x.sub.r).sup.2+(y.sub.s−y.sub.r).sup.2+(z.sub.s−z.sub.r).sup.2)}+c.sub.0.Math.(τ.sub.r−τ.sub.s−τ.sub.comp)+τ.sub.1.sup.s+τ.sub.T.sup.s+τ.sub.RF1.sup.s+τ.sub.MP.sup.s+τ.sub.N0.sup.s  (eq. 9)

(145) When applying the Code compensation not encompassing the tropospheric and ionospheric delay (see eq. 8), the former equation becomes following:
PR.sub.r.sup.s=√{square root over ((x.sub.s−x.sub.r).sup.2+(y.sub.s−y.sub.r).sup.2+(z.sub.s−z.sub.r).sup.2)}−√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)}+ . . . c.sub.0.Math.τ.sub.r+τ.sub.1.sup.s+τ.sub.T.sup.s+τ.sub.RF1.sup.s+τ.sub.MP.sup.s+τ.sub.N0.sup.s  (eq. 10)

(146) When applying the Code compensation encompassing the tropospheric and ionospheric delay (see eq. 7), the former equation becomes following:

(147) $\begin{array}{cc}{\mathrm{PR}}_r^s=\sqrt{{\left(x_s-x_r\right)}^2+{\left(y_s-y_r\right)}^2+{\left(z_s-z_r\right)}^2}-\sqrt{{\left(x_s-x_{\mathrm{vtrs}}\right)}^2+{\left(y_s-y_{\mathrm{vtrs}}\right)}^2+{\left(z_s-z_{\mathrm{vtrs}}\right)}^2}+\mathrm{.Math.}{c}_0.Math.{\tau }_r+\left({\tau }_l^s-{\tau }_{l,\mathrm{vtrs}}^s\right)+\left({\tau }_T^s-{\tau }_{T,\mathrm{vtrs}}^s\right)+{\tau }_{\mathrm{RFI}}^s+{\tau }_{\mathrm{MP}}^s+{\tau }_{N0}^s& \left(\mathrm{eq}.11\right)\end{array}$

(148) From (eq. 10) and (eq. 11) it can be observed that the code compensation enables to avoid providing to the user the satellite clock offset, τ.sub.s, since it disappears with the code compensation. Furthermore, neglecting local and atmospheric contributions to the user pseudorange then the former expressions reduces to
PR.sub.r.sup.s≈√{square root over ((x.sub.s−x.sub.r).sup.2+(y.sub.s−y.sub.r).sup.2)}+(z.sub.s−z.sub.r).sup.2×−√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)}  (eq. 12)

(149) This expression corresponds to the Time Difference Of Arrival (TDOA) between the VTRS and the user device, when transmitted by the satellite.

(150) Another option regarding the calculation of the code compensation consists to not compensate neither for the satellite clock offset, τ.sub.s, nor for the tropospheric and ionospheric delays, and only to account for the propagation time between satellite and the VTRS as described hereafter.
τ.sub.comp=(√{square root over ((x.sub.s−x.sub.vtrs).sup.2+(y.sub.s−y.sub.vtrs).sup.2+(z.sub.s−z.sub.vtrs).sup.2)})/c.sub.0  (eq. 12)

(151) In that case the expression of the measured pseudo-range for a user device becomes:

(152) $\begin{array}{cc}{\mathrm{PR}}_r^s=\sqrt{{\left(x_s-x_r\right)}^2+{\left(y_s-y_r\right)}^2+{\left(z_s-z_r\right)}^2}-\sqrt{{\left(x_s-x_{\mathrm{vtrs}}\right)}^2+{\left(y_s-y_{\mathrm{vtrs}}\right)}^2+{\left(z_s-z_{\mathrm{vtrs}}\right)}^2}\mathrm{.Math.}+c_0.Math.\left({\tau }_r-{\tau }_s\right)+{\tau }_I^s+{\tau }_T^s+{\tau }_{\mathrm{RFI}}^s+{\tau }_{\mathrm{MP}}^s+{\tau }_{N0}^s& \left(\mathrm{eq}.13\right)\end{array}$

(153) In one or more aspect, the code acquisition search may be reduced by considering that the cell repartition covers uniformly the earth surface, as shown in the illustrative FIGS. 20 and 21, and that a specific spreading sequence is allotted for each pair of cell-satellite. It means that when the satellite with identifier Sat-ID-q transmits a navigation signal component to a Cell with identifier Cell-ID-p, the corresponding signal is modulated with a specific spreading sequence PRN.sub.Sat-ID-q, Cell-ID-p. This spreading sequence, PRN.sub.Sat-ID-q, Cell-ID-p1, is different to the spreading sequence PRN.sub.Sat-ID-q, Cell-ID-p2 used to modulate the navigation signal component transmitted by the Satellite with identifier Sat-ID-q towards the cell with identifier Cell-ID-p2. The spreading sequence, PRN.sub.Sat-ID-q1, Cell-ID-p, can but does not have to be different to the spreading sequence PRN.sub.Sat-ID-q2, Cell-ID-p used to modulate the navigation signal component transmitted by the Satellite with identifier Sat-ID-q2 towards the cell with identifier Cell-ID-p. Hence, a Look-Up table for the Spreading Code allocation exists between the P cells and the Q satellites. It is recalled that for conventional satellite navigation system, a single spreading sequence is allotted per satellite for each navigation signal component. One candidate implementation for the acquisition of the signal transmitted by satellite with Sat-ID-q is an acquisition bank made of P individual passive acquisition modules having each a replica based on an un-shifted spreading sequence PRN.sub.Sat-ID-q, Cell-ID-p corresponding to the p.sup.th cell and q.sup.th satellite. A similar architecture can be a bank of active acquisition modules, each testing a different set of Code and Doppler hypotheses, corresponding to each of the PRN.sub.Sat-ID-q, Cell-ID-p.

(154) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 23 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-22) or below (e.g. FIGS. 24-37).

(155) If the user device has an a priori regarding its rough position on the earth surface, that is to say the candidate cells where the user device can potentially be part of, only a sub-set of acquisition modules corresponding to the cells which belongs to this a-priori is then necessary. A high-level description of the corresponding acquisition bank, comprising 13 individual passive acquisition modules, corresponding to 13 cells forming a dense mesh over the earth surface is illustrated in FIG. 24. At reception of the navigation signal component transmitted by satellite Sat-ID-q, only one module out of the Q experiences a correlation peak. The user device in FIG. 24 belongs to the cell with Cell-ID-10, and the output of the passive acquisition module 10 experiences a peak. The allocation of the spreading codes to cells enables to reduce the overall time uncertainty since a peak observed at the output of one of the passive acquisition modules provides already an information on the user device position within the corresponding cell. This feature enables to dimension the length of the spreading code sequence, as explained hereafter.

(156) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 24 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-23) or below (e.g. FIGS. 25-37).

(157) In FIG. 12, the difference in reception time of the wave-front corresponding to the reference chip at VTRS (i.e. User Device A) and “User Device B” for a satellite is tangent to the earth surface (exactly) corresponds to the distance (once expressed in unit of time) between the VTRS and the User Device B. As a matter of fact, the spreading sequence defines a circular area with center at cell center and radius equals to the spreading code period (once expressed in meters). In the following, this area is called the Code Acquisition Search Area to Cell-ID-q. In cold acquisition, i.e. when the User Device has no a priori about its position, the maximal time uncertainty to be scrutinized is therefore equal to the spreading code sequence length. Indeed, it is considered that a time transfer can be achieved with the center of the neighbored areas, possibly with another reference time for the corresponding t.sub.Ref,VTRS* (where VTRS* represents the VTRS at the center of the neighbored cell). The maximal time uncertainty and the underlying spreading sequence duration, thus depend on the distance between two neighbored cells, which is also called inter-cell distance, but also on the ability of the Code Acquisition Search Areas to fully “cover” the earth surface. At maximum, the duration of the Spreading Code sequence equals the inter-cell distance (once expressed in time unit). This is represented on the left part in FIG. 25, when a maximal overlap applies between the acquisition search areas associated to neighbored cells. For example, assuming an inter-cell distance of 380.65 km (as per FIG. 20) and a chip rate of R.sub.c=1 MCps, i.e. T.sub.c=1 μs or 300 m, then the length for the underlying spreading sequence shall be 1268 chips. On the right part in FIG. 25, the spreading code length once expressed in meters is smaller than the inter-cell distance. For the same chip rate, this corresponds for example to a spreading code length of 1023 chips. This yields to a smaller overlap between the acquisition search areas associated to both neighbored cells. It means that the code length may not be sufficient.

(158) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 25 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-24) or below (e.g. FIGS. 26-37).

(159) At the end, minimal and optimal spreading code length may need to ensure that the overlap of the acquisition search areas, associated to all cells, covers the whole earth surface. This may then correspond to the optimal code length. This is illustrated in the middle part in FIG. 26. FIG. 26 shows on the left part the situation corresponding to the maximal spreading code sequence length, on the middle part the situation corresponding to the optimal spreading code sequence length and on the right part the situation where the spreading code sequence length is not sufficient. In the latter case, it can be observed that the user device is not part of any acquisition search areas, meaning that its acquisition performance is strongly degraded.

(160) Once the spreading code length has been optimally dimensioned, based on the inter-cell distance, it is then necessary to facilitate the user device to identify the number of spreading sequences that have passed through the user device since the first spreading sequence, and the one which has been used to successfully acquire and track the navigation signal stream. Indeed, from the acquisition process, the user device may synchronize its locally generated and shifted replica with the received signal, and especially with a portion of the received signal comprising a spreading sequence which is distant of “r” spreading sequences to the first transmitted spreading sequence and whose first chip arrives at t.sub.ref,VTRS at the VTRS. Then the user device will track with the DLL the navigation signal, once synchronized to it. Hence an ambiguity, related to the actual occurrence of the spreading sequence, currently processed by the user device, since the first spreading sequence may need to be solved in order to deduce r, and thus to enable the user device to synchronize to the system time.

(161) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 26 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-25) or below (e.g. FIGS. 27-37).

(162) In one or more aspects, the navigation signal may include an information for the code sequence counter for the first spreading sequence and which enables to deduce r. First and second implementations may be used for this purpose.

(163) In FIG. 27, the first implementation modulates a code sequence counter onto the spreading sequence, as part of the navigation data. In the same figure, the actual occurrence of the spreading sequence for which the user device is synchronized (i.e. a clear peak of the correlation function is observed) is equal to r=5, for illustration purposes. It means that since the first chip of the first spreading sequence arrived to the VTRS (i.e. cell center), 5 spreading sequences occurred.

(164) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 27 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-26) or below (e.g. FIGS. 28-37).

(165) In FIG. 28, the second implementation applies a shift to the spreading sequence for each new spreading sequence epoch (r), where the shift depends on the spreading sequence occurrence, r, since the first spreading sequence. The spreading sequence counter may also be called Code Shift Keying. After synchronization on the 5th occurrence of the spreading sequence (value again used for illustration purpose) the user device is able to derive from the different shifts applying between different consecutive spreading sequences, the value for the actual occurrence of the spreading sequence.

(166) In one or more aspects, the Doppler acquisition search may be reduced by controlling the offset between actual carrier frequency, f.sub.carrier,RF of the transmitted signal and the reference carrier frequency f.sub.carrier (e.g. 1575.45 MHz as for the GPS L1 C/A signal component), in such a way that the actual Doppler observed at VTRS is zero.

(167) The following equation provides the general expression for the Doppler experienced at a terrestrial users when receiving a signal, transmitted by a satellite.

(168) $\begin{array}{cc}\Delta f_{\mathrm{Dopp}}\left(\mathrm{user}\right)=-\left(\frac{{\left(\stackrel{.Math.}{P_r}-\stackrel{.Math.}{P_s}\right)}^T\left(\stackrel{.Math.}{V_r}-\stackrel{.Math.}{V_s}\right)}{.Math.\left(\stackrel{.Math.}{P_r}-\stackrel{.Math.}{P_s}\right).Math.c_0}\right)f_{\mathrm{carr}}& \left(\mathrm{eq}.14\right)\end{array}$

(169) Where

(170) f.sub.carr designates the carrier frequency transmitted by the satellite

(171) Δf.sub.Dopp designates the Doppler offset as difference between the received frequency f.sub.carr and the transmitted carrier frequency f.sub.carr

(172) {right arrow over (P.sub.r)} (resp. {right arrow over (P.sub.e)}) designate the position vector of the receiver (transmitter respectively)

(173) {right arrow over (V.sub.r)} (resp. {right arrow over (V.sub.e)}) designate the velocity vector of the receiver (transmitter respectively)

(174) Applying the former expression to the VTRS enables to deduce the Doppler offset experienced at VTRS. The application of the Doppler compensation means that the actual transmitted frequency shall be corrected with Δf.sub.carr,comp by subtracting with Δf.sub.Dopp(VTRS), as computed with the position and velocity of the VTRS.

(175) It is worth highlighting that the Doppler compensation is performed for a VTRS, where no physical device has to be present, which is one particularity of the proposed concept.

(176) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 28 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-27) or below (e.g. FIGS. 29-37).

(177) FIG. 29 schematically illustrates geographical variations of the actual received Doppler, as difference between the actual received carrier frequency and the reference carrier frequency, when the frequency of the RF signal transmitted at the satellite equals the reference carrier frequency (for example 1575.45 MHz). The determination of the actual received Doppler does not account neither the user dynamic, nor the stability of the user equipment clocks. The geographical variations of the actual received Doppler are represented within the visibility footprint, based on a minimal elevation angle of 5°, for the GNSS satellite 1. In FIG. 29, two representations are shown, a first representation based on isolines of Doppler which enables to see the cell centers, and a second representation which shows filled areas where the actual Doppler belongs to the ranges defined by the aforementioned isolines. For a cell radius of 380.6 km and a minimal elevation angle of 5°, 481 cells are included within the corresponding visibility footprint. Further, within a satellite visibility footprint, the Doppler spans between ˜−4001 Hz and +4001 Hz, yielding an overall variation of 8002 Hz. The consequence of this large range of Doppler due to the dynamic of the satellite-to-user link is that the user may have to test a large number of Doppler hypotheses. Assuming for example a spacing between two consecutive Doppler hypotheses, also called Doppler bin width, of 50 Hz, may then yield to test 160 Doppler hypotheses.

(178) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 29 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-28) or below (e.g. FIGS. 30-37).

(179) FIG. 30 schematically illustrates a similar representation as FIG. 29, when considering a visibility footprint based on a minimal elevation angle of 40°, still for the GNSS satellite 1. For a cell radius of 380.6 km and a minimal elevation angle of 40°, it can be seen that 161 cells are included within the corresponding visibility footprint.

(180) In order to reduce the corresponding number of Doppler hypotheses, the carrier frequency of the RF signal transmitted at the satellite may be offset by a value, Δf.sub.carr,comp such that the actual received carrier frequency at the cell center, which represents a VTRS according to the afore description, is null. It means that when the satellite is transmitted to each cell, the aforementioned carrier frequency offset at satellite level may depend on the actual velocity of the satellite, and the position of the VTRS (i.e. cell center), and may therefore vary from cell center to cell center.

(181) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 30 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-29) or below (e.g. FIGS. 31-37).

(182) FIG. 31 schematically illustrates Doppler variations within each of the aforementioned 161 cells, when applying the Doppler compensation. In order to better show the reduction of the corresponding Doppler excursion within each cell, two close-ins provided for one cell located in the lower part of the visibility footprint, and for another cell in the middle part of the visibility footprint. For the first cell, the Doppler variations reduce from 6840 Hz (without Doppler compensation) down to 368.5 Hz (factor ˜19), while for the second cell, the Doppler variations reduce from 3840 Hz (without Doppler compensation) down to 565.5 Hz (factor ˜12). It also means that for the first cell, a user located within the corresponding cell may have to test at maximum 8 Doppler bins, while for the second cell, a user located within the corresponding cell may have to test at maximum 12 Doppler bins for a Doppler bin width of 50 Hz.

(183) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 31 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-30) or below (e.g. FIGS. 32-37).

(184) FIG. 32 schematically illustrates a maximal Doppler variation when applying Doppler compensation for each of the 161 cells. The values of 368.5 Hz and 565.5 Hz can be effectively retrieved from the figure as well. It can be verified that the Doppler span ranges between 300 Hz (i.e. 6 Doppler hypotheses) and 562.5 (i.e. 12 Doppler hypotheses).

(185) First and second implementations may be used for a corresponding Doppler compensation. The first implementation may offset the frequency generated by the Frequency and Time Generation Unit (FTGU), f.sub.ftgu,act with an offset Δf.sub.ftgu such that f.sub.ftgu,act=f.sub.ftgu+Δf.sub.ftgu, where the corresponding offset is proportional to the offset Δf.sub.carr,comp applied to the transmitted RF carrier. The corresponding offset may account for the different steps of up-conversion between the nominal frequency f.sub.ftgu of the FTGU and the reference carrier f.sub.carr. The second implementation may apply an offset to the signal generated within the Navigation Signal Generation Unit (NSGU). The NSGU is then fed with the unmodified nominal frequency f.sub.ftgu,act=f.sub.ftgu, and may apply an offset Δf.sub.nsgu to the frequency of the output signal, either in the analogue or in the digital domain (depending on the actual configuration of the NSGU), which yield to the actual carrier frequency of the NSGU output: f.sub.nsgu,act=f.sub.nsgu+Δf.sub.nsgu, where the corresponding offset Δf.sub.nsgu is proportional to the offset Δf.sub.carr,comp applied to the transmitted RF carrier.

(186) Further, the Doppler compensation can be applied continuously over time at navigation signal generation chain.

(187) Further, the user device may know (in advance) the exact position of the VTRS as well as the reference time t.sub.ref,VTRS. When considering (a network of) cells, an ensemble of pairs comprising each the exact position of the VTRS (or equivalently the cell center) and reference times, t.sub.ref,VTRS at each cell center may be made available to the user device. Here a Look-Up table of VTRS positions and reference time can then be generated. Such information can for example be provided in the user navigation message, transmitted earlier to the user device, which enables to update the corresponding look-up table. The corresponding information can also be made available via a so-called third channel, or communication channel that is available at user device, for example using the terrestrial communication networks. The corresponding information can also be “hardcoded” in the user device, letting less possibly to modify the corresponding Look-up table. It is further outlined that different reference times for each VTRS can be applied, in order to ensure time transfer and ease acquisition, over time.

(188) Further, the VTRS can be a “static VTRS” or a “moving VTRS” for which the trajectory can be known in advance by the user device, as well as the reference time, t.sub.ref,vtrs when the raising edge of the first chip arrives at the moving VTRS according to the known trajectory. This situation is illustrated in FIG. 33.

(189) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiments shown in FIGS. 32 and 33 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-31) or below (e.g. FIGS. 34-37).

(190) FIG. 34, FIG. 35 and FIG. 36 show alternative platforms that could be used to host the signal generation chain implementing the code compensation according to the present disclosure. FIG. 34 illustrates the case of a (stratospheric) balloon. FIG. 35 illustrates the case of a High-Altitude Platform Station (HAPS). FIG. 36 illustrates the case of a terrestrial station, here a Base Transceiver Station, but the case of a Pseudolite can also be considered in place.

(191) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiments shown in FIGS. 34, 35 and 36 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-33) or below (e.g. FIG. 37).

(192) FIG. 37 schematically illustrates an application of the code compensation when applied to HAPS. In this example three HAPS are represented, as well as three VTRS, whose distance is consistent with the assessments related to the necessary spreading code length to ensure a faster acquisition. With respect to satellites, the advantage of HAPS is their lower dynamic, together with the lower investment need for their development, deployment and operation. Furthermore, another advantage of HAPS is the possibility to put them onto operation over (populated) regions where demanded. In that way “wasting” HAPS platform over regions without this demand is avoided. The precise HAPS position is needed in order to ensure accurate code and Doppler compensation. One approach to solve this issue can consists in implementing a multi-GNSS receiver on-board the HAPS platform which will provide exact position as well as time with respect to GNSS time scale referential. Based on this information, it is possible to generate the code and Doppler compensation in order to ensure synchronization at the VTRS. The principle for the generation of the Code and Doppler compensation is then similar to the one presented in FIG. 9.

(193) More details and aspects are mentioned in connection with the embodiments described above or below. The embodiment shown in FIG. 37 may comprise one or more optional additional features corresponding to one or more aspects mentioned in connection with the proposed concept or one or more embodiments described above (e.g. FIGS. 1-36) or below.

(194) In one or more embodiments, code compensation may be performed ensuring that the rising or falling edge of a reference chip arrives at a time t.sub.ref,VTRS at a so-called Virtual Timing Reference Station (VTRS).

(195) In one or more embodiments, (a network of) cells may be provided whose centers are VTRS.

(196) In one or more embodiments, code compensation determination may account for the clock offset of navigation signal source with respect to system time, the position of the navigation signal generation as well as the position of the VTRS and the reference time t.sub.ref,VTRS. The code compensation determination can but does not have to account for the ionospheric and tropospheric delay experienced at VTRS and at t.sub.ref,VTRS.

(197) In one or more embodiments, code length may be derived based on the inter-cell distance.

(198) In one or more embodiments, the navigation signal may comprise a Spreading Code counter which counts the number of spreading codes since the first spreading code comprising the reference chip.

(199) In one or more embodiments, Doppler compensation may ensure that the actual Doppler is zero at the VTRS. The Doppler compensation may account for the exact VTRS position, the satellite orbit, and the reference carrier frequency.

(200) In one or more embodiments, the exact position of the VTRS and the reference time t.sub.ref,vtrs may be made available to the user device or are hard coded.

(201) In one or more embodiments, the VTRS can follow a trajectory which is known from user device, and the exact position when the reference chip arrives at the reference trajectory at a reference time t.sub.ref,VTRS is also known by the user device.

(202) In one or more embodiments, the platforms hosting the navigation signal generation implementing the code and Doppler compensation as well as the corresponding signal features can be a space-based station such as a Navigation Satellite at a Medium Earth Orbit (MEO), a Low Earth Obit (LEO) or a GEO stationary satellites (GEO). The platforms can also be a near earth platform such as a High Altitude Platform (HAPS), a (stratospheric) Balloons or a Drone. The platforms can also be a static terrestrial platform, such as Base Transceiver Stations (BTS) used in general for terrestrial mobile network infrastructures, or such as terrestrial Navigation Beacons, also called Pseudo-satellites or Pseudolites.

(203) The aspects and features mentioned and described together with one or more of the previously detailed examples and figures, may as well be combined with one or more of the other examples in order to replace a like feature of the other example or in order to additionally introduce the feature to the other example.

(204) Examples may further be or relate to a computer program having a program code for performing one or more of the above methods, when the computer program is executed on a computer or processor. Steps, operations or processes of various above-described methods may be performed by programmed computers or processors. Examples may also cover program storage devices such as digital data storage media, which are machine, processor or computer readable and encode machine-executable, processor-executable or computer-executable programs of instructions. The instructions perform or cause performing some or all of the acts of the above-described methods. The program storage devices may comprise or be, for instance, digital memories, magnetic storage media such as magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. Further examples may also cover computers, processors or control units programmed to perform the acts of the above-described methods or (field) programmable logic arrays ((F)PLAs) or (field) programmable gate arrays ((F)PGAs), programmed to perform the acts of the above-described methods.

(205) The description and drawings merely illustrate the principles of the disclosure. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the disclosure and the concepts contributed by the inventor(s) to furthering the art. All statements herein reciting principles, aspects, and examples of the disclosure, as well as specific examples thereof, are intended to encompass equivalents thereof.

(206) A block diagram may, for instance, illustrate a high-level circuit diagram implementing the principles of the disclosure. Similarly, a flow chart, a flow diagram, a state transition diagram, a pseudo code, and the like may represent various processes, operations or steps, which may, for instance, be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown. Methods disclosed in the specification or in the claims may be implemented by a device having means for performing each of the respective acts of these methods.

(207) It is to be understood that the disclosure of multiple acts, processes, operations, steps or functions disclosed in the specification or claims may not be construed as to be within the specific order, unless explicitly or implicitly stated otherwise, for instance for technical reasons. Therefore, the disclosure of multiple acts or functions will not limit these to a particular order unless such acts or functions are not interchangeable for technical reasons. Furthermore, in some examples a single act, function, process, operation or step may include or may be broken into multiple sub-acts, -functions, -processes, -operations or -steps, respectively. Such sub acts may be included and part of the disclosure of this single act unless explicitly excluded.

(208) Furthermore, the following claims are hereby incorporated into the detailed description, where each claim may stand on its own as a separate example. While each claim may stand on its own as a separate example, it is to be noted that—although a dependent claim may refer in the claims to a specific combination with one or more other claims—other examples may also include a combination of the dependent claim with the subject matter of each other dependent or independent claim. Such combinations are explicitly proposed herein unless it is stated that a specific combination is not intended. Furthermore, it is intended to include also features of a claim to any other independent claim even if this claim is not directly made dependent to the independent claim.

(209) The present disclosure is not limited in any way to the embodiments described above. On the contrary, there are many possibilities for modifications thereof, which are apparent to an average skilled person without departing from the underlying idea of the present disclosure as defined in the appended claims.

(210) While at least one exemplary embodiment of the present invention(s) is disclosed herein, it should be understood that modifications, substitutions and alternatives may be apparent to one of ordinary skill in the art and can be made without departing from the scope of this disclosure. This disclosure is intended to cover any adaptations or variations of the exemplary embodiment(s). In addition, in this disclosure, the terms “comprise” or “comprising” do not exclude other elements or steps, the terms “a” or “one” do not exclude a plural number, and the term “or” means either or both. Furthermore, characteristics or steps which have been described may also be used in combination with other characteristics or steps and in any order unless the disclosure or context suggests otherwise. This disclosure hereby incorporates by reference the complete disclosure of any patent or application from which it claims benefit or priority.