Method and apparatus for synchronizing GNSS time scale with coordinated universal time

Abstract

The application provides a GNSS time scale and coordinated universal time synchronization method and device, and belongs to the technical field of radio communication. In the method, when GNSS data is received, current time is calculated, a sub-time unit base and a remainder are determined; the current sub-time unit base and the parity code of the current sub-time unit are determined; the time to the next accurate 0.2-second sub-time unit is calculated and a countdown timer to the next time unit is set; it is determined whether the calculation time is sufficient; if the calculation time is sufficient, the position of the next 0.2-second sub-time unit is calculated and saved, the parity code of the next sub-time unit is determined, and the position loading flag is cleared; the method utilizes the time scale pulse, position, speed and time data from the GNSS to synchronize the time scale pulse and the UTC time, reduces the deviation of the position data in the air position message or the ground position message from the real-time position, and ensures the correctness of the position data transmitted by the ADS-B transmitter.

Description

Technical Field

[0001] This invention belongs to the field of radio communication technology, and particularly relates to a method and apparatus for synchronizing GNSS time markers with Coordinated Universal Time. Background Technology

[0002] Aviation surveillance is one of the core means of ensuring air traffic safety. With the increasing demands of air traffic users for surveillance performance, traditional land-based surveillance systems can no longer meet the requirements. New air-ground collaborative surveillance systems, such as Automatic Dependence Surveillance-Broadcasting (ADS-B), have become an important development direction to meet these new demands. ADS-B is an air traffic control surveillance technology based on the Global Navigation Satellite System (GNSS) and utilizing ground-to-air and air-to-air data link communication to complete traffic surveillance and information transmission. ADS-B technology features low cost, high accuracy, strong surveillance capabilities, and high flexibility, making it suitable for air traffic services in high-density flight areas and effectively solving the various drawbacks of traditional surveillance methods. ADS-B technology combines advanced technologies such as satellite navigation, communication technology, airborne equipment, and ground equipment to provide a safer and more efficient means of air traffic surveillance. It can effectively improve the situational awareness of controllers and pilots, expand the surveillance coverage, and improve air traffic safety, airspace capacity, and operational efficiency.

[0003] From the time GNSS generates position data to the time the ADS-B transmitter receives the position data, completes the encoding, and transmits it, a certain amount of time has passed. By the time the ADS-B transmitter transmits its airborne or ground position message, its position has already changed due to its own movement. To ensure the accuracy of the position data transmitted by the ADS-B transmitter despite time differences and aircraft movement, a method for synchronizing the GNSS timescale with Coordinated Universal Time (UTC) for the ADS-B transmitter is needed. Summary of the Invention

[0004] To ensure the accuracy of position data transmitted by ADS-B transmitters despite time differences and aircraft motion, this invention provides a method and apparatus for synchronizing GNSS time stamps with Coordinated Universal Time (UTC) for ADS-B transmitters. This method uses data such as time stamp pulses, time, longitude, latitude, east / west velocity, and south / north velocity from GNSS to establish synchronization with UTC time. The technical solution is as follows:

[0005] Firstly, a method for synchronizing GNSS time stamps with Coordinated Universal Time (UTC) is provided, which uses time stamp pulses, position, velocity, and time data from GNSS to synchronize the time stamp pulses with UTC time.

[0006] The method includes:

[0007] Begin by waiting for the leading edge of the GNSS timescale;

[0008] When GNSS data is received, the current time is calculated. The current time refers to the time when the synchronization process is completed. GNSS data includes longitude, latitude, north-south velocity, east-west velocity, Label_150UTC, and Label_140UTC precise time.

[0009] Determine the base and remainder of the sub-time unit;

[0010] Determine the cardinality and parity code of the current sub-time unit;

[0011] Calculate the time to the next precise 0.2-second sub-time unit and set the countdown timer for the next time unit;

[0012] Determine if there is sufficient time for calculation;

[0013] If there is sufficient time for computation, calculate and save the position of the next 0.2-second sub-time unit, determine the parity code of the next sub-time unit, and clear the position loading flag to zero.

[0014] Furthermore, the method also includes:

[0015] If the calculation time is insufficient, determine the parity code of the next sub-time unit and set the position loading flag. If the countdown timer expires, determine whether the position loading flag is set.

[0016] If the position loading flag is set, calculate the position at the next 0.2-second sub-time unit + 0.2 seconds and save the position for loading.

[0017] Furthermore, the method also includes:

[0018] If the location loading flag is not set, the new location is extrapolated, the new location data is CPR encoded, and the new location data is loaded into the BDS cache; the extrapolation process continues in every 0.2-second sub-time unit until the next resynchronization.

[0019] Furthermore, the method also includes:

[0020] If the countdown timer has not expired, continue waiting.

[0021] Secondly, a GNSS time stamp and Coordinated Universal Time (UTC) synchronization device is provided, which uses time stamp pulses, position, velocity and time data from GNSS to synchronize the time stamp pulses with Coordinated Universal Time (UTC).

[0022] The device includes:

[0023] The calculation module is used for:

[0024] Begin by waiting for the leading edge of the GNSS timescale;

[0025] When GNSS data is received, the current time is calculated. The current time refers to the time when the synchronization process is completed. GNSS data includes longitude, latitude, north-south velocity, east-west velocity, Label_150UTC, and Label_140UTC precise time.

[0026] Determine the base and remainder of the sub-time unit;

[0027] Determine the cardinality and parity code of the current sub-time unit;

[0028] Calculate the time to the next precise 0.2-second sub-time unit and set the countdown timer for the next time unit;

[0029] Determine if there is sufficient time for calculation;

[0030] If there is sufficient time for computation, calculate and save the position of the next 0.2-second sub-time unit, determine the parity code of the next sub-time unit, and clear the position loading flag to zero.

[0031] Furthermore, the device also includes:

[0032] The determination module is used for:

[0033] If the calculation time is insufficient, determine the parity code of the next sub-time unit and set the position loading flag. If the countdown timer expires, determine whether the position loading flag is set.

[0034] If the position loading flag is set, calculate the position at the next 0.2-second sub-time unit + 0.2 seconds and save the position for loading.

[0035] Furthermore, the device also includes:

[0036] The processing module is used to extrapolate a new location if the location loading flag is not set, perform CPR encoding on the new location data, and load the new location data into the BDS cache; the extrapolation process continues in every 0.2-second sub-time unit until the next resynchronization.

[0037] Thirdly, a GNSS timescale and Coordinated Universal Time (UTC) synchronization device is provided, comprising a processor and a memory, wherein the processor is configured to execute instructions stored in the memory, and the processor implements a GNSS timescale and UTC synchronization method as described in any of the first aspects by executing the instructions.

[0038] Fourthly, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a processing component of a computer, cause the processing component to perform a GNSS timescale and Coordinated Universal Time synchronization method as described in any of the first aspects.

[0039] Fifthly, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to execute a GNSS timescale and Coordinated Universal Time synchronization method as described in any of the first aspects.

[0040] The beneficial effects of this invention are at least as follows:

[0041] This invention achieves synchronization between GNSS data and UTC time, resulting in minimal deviation between the position data in the transmitted message and the actual data. When other machines receive the air or ground position messages transmitted by this machine, the positioning longitude is high and the position delay is small. Attached Figure Description

[0042] Figure 1 A schematic diagram of precise 0.2UTC sub-time unit encoding with sub-time unit base and sub-time unit base + 1 provided for embodiments of the present invention;

[0043] Figure 2 A flowchart of time-UTC synchronization provided for embodiments of the present invention. Detailed Implementation

[0044] The present invention will now be described in further detail with reference to specific embodiments and accompanying drawings.

[0045] The 53rd bit of an air or ground location message is the Time subfield. When this subfield is set to "1", it indicates that the location data in the location message is time-synchronized to a precise 0.2-second UTC time unit (each UTC time unit is 1 second).

[0046] like Figure 1 As shown, each UTC time unit is divided into five precise 0.2-second sub-time units. The transmitted location message requires Compressed Position Reporting (CPR) encoding of the local machine's longitude and latitude. CPR encoding has two methods: even encoding and odd encoding. The CPR encoding in each 0.2 UTC time unit switches between even and odd encoding.

[0047] For each 0.2 UTC time unit, the distribution of even and odd codes begins with an even time unit.

[0048] The leading edge of the GNSS time-scale pulse is within ±5 milliseconds of the start of the second time unit.

[0049] Position, velocity, and time (PVT) data should be acquired from GNSS no later than 200 ms after the leading edge of the time-stamped pulse. Most GNSS systems provide PVT data within 200 ms of the time-stamped pulse.

[0050] However, the time-stamped pulse and the UTC time unit are not tightly coupled.

[0051] GNSS outputs time data via label_150 and label_140. The leading edge of the time stamp pulse is not synchronized with the start of the integer time unit (integer seconds). The relationship between the time stamp pulse and UTC time will be completely different each time the GNSS is powered on.

[0052] Therefore, the GNSS time stamp pulse and its UTC time cannot be used as the starting point for the actual time unit. This necessitates a method to synchronize the time stamp and its UTC time so that the precise 0.2UTC sub-time unit required by ADS-B can be established based on the time provided by the UTC time of the time stamp's leading edge.

[0053] Please see Figure 2 , Figure 2 The number in each process represents the flow procedure number, denoted as process n. This invention provides a method for synchronizing GNSS time scales with Coordinated Universal Time for an ADS-B transmitter, comprising the following steps:

[0054] Step 1: Begin by waiting for the leading edge of the GNSS timescale. For example... Figure 2 The process flow is shown in steps 1 to 3.

[0055] When the leading edge of the time scale is detected, the timer... tag_edge Start timing and count the time elapsed since the leading edge of the time mark. The timer is an incrementing counter with a minimum resolution of 1 ms. If higher accuracy is desired, increments of 100 µs can be used, and the maximum counter range is 1 second.

[0056] Step 2: Wait for GNSS data. For example... Figure 2 As shown in process 4.

[0057] Wait for GNSS data received from the GNSS receiver, including longitude, latitude, north-south velocity, east-west velocity, Label_150UTC, and Label_140UTC precise time, as a minimum requirement to perform the synchronization process. Ensure that all this data has been stored for subsequent synchronization processes.

[0058] Step 3: Calculate the current time. For example... Figure 2 As shown in process 5.

[0059] The current time refers to the time when the synchronization process completed its calculations. Specifically, the current time is calculated using Formula 1:

[0060] Formula 1: time current =time in_label_140 +timer tag_edge +time est_comp ,

[0061] Among them, time current This refers to the time it takes for the synchronization process to complete.

[0062] time in_label_140 This refers to the decimal seconds in Label140;

[0063] timer tag_edge The fractional seconds following the start of the time stamp pulse;

[0064] time est_comp This refers to the estimated synchronization time required to complete the synchronization process.

[0065] Step 4: Determine the base and remainder of the sub-time unit. For example... Figure 2 As shown in process 6.

[0066] Sub-epoch base The sub-epoch is used to establish the current time period and is a number between 0 and 4. base Calculated using Formula 2:

[0067] Formula 2: Sub-epoch base =floor(time) current )

[0068] Sub-epoch base Then to time current The remaining time, or how far away the next time unit is from the current time. This parameter is expressed as time. mod_0.2 This means that it can be calculated using Formula 3:

[0069] Formula 3: time mod_0.2 =mod(time) current ,0.2)

[0070] Step 5: Determine the cardinality of the current sub-time unit. For example... Figure 2 The process flow is shown in 7-8.

[0071] The least significant bit (LSB) of the "seconds" data provided in label_150 determines whether the time is in an even or odd time unit.

[0072] like Figure 1 As shown, if the time is in an even-time unit, then the Sub-epochbase The time interval is either even or odd, and for even time units, it is arranged in an even / odd distribution; if the time is in an odd time unit, then the sub-epoch... base One more sub-epoch needs to be added. base +1 represents either odd or even, and for odd time units, the distribution is arranged in odd / even order.

[0073] Step 6: Determine the parity code for the current sub-time unit. For example... Figure 2 The process flow is shown in 9 to 11.

[0074] If Sub-epoch base If the least significant bit (LSB) is 0, then Current sub-epoch Set to "Even", otherwise Current sub-epoch Set it to "Odd".

[0075] Step 7: Calculate the time until the next precise 0.2-second sub-time unit. For example... Figure 2 As shown in process 12.

[0076] Time to_next_sub-epoch The remaining time until the start of the next precise 0.2-second sub-time unit is defined as follows:

[0077] Formula 4: Time to_next_sub-epoch =0.2-time mod_0.2

[0078] Then, for convenience, the available time (TOA) of the next 0.2-second sub-time unit is set to the same as Time. to_next_sub-epoch They are equal, as defined in Formula 5:

[0079] Formula 5: TOA=Time to_next_sub-epoch

[0080] Step 8: Set the countdown timer for the next time unit. For example... Figure 2 As shown in process 14.

[0081] Start a countdown timer with an initial value of TOA.

[0082] Step 9: Determine if there is sufficient computation time. For example... Figure 2 As shown in process 15.

[0083] Determine if there is sufficient time to compensate for the current position before the start of the next precise 0.2-second sub-time unit. Figure 2 The 5ms in process 15 is an arbitrary setting, and this value should be based on the actual time required to complete the position compensation calculation.

[0084] If there is sufficient time available:

[0085] If sufficient time is available, position compensation is performed at the beginning of the next precise 0.2-second sub-time unit. Once the next 0.2-second sub-time unit is reached, the updated position is pushed forward outward to the next precise 0.2-second sub-time unit to provide the updated position. The updated position is CPR-encoded and loaded into the appropriate registers for random firing when needed.

[0086] The key here is to only compensate for the accuracy of the position of the next 0.2-second sub-time unit. Further compensation is handled in the extrapolation process. Note: Compensation is completed before the countdown timer expires.

[0087] If there is insufficient time available:

[0088] If there is insufficient time available for position compensation at the start of the next precise 0.2-second sub-time unit, the position must be compensated after the countdown timer expires. In this case, the position will be directly compensated to the next precise 0.2-second time unit after the countdown timer expires. The compensated position is saved, CPR encoded, and loaded into the appropriate register for random firing when needed. Therefore, in this case, the compensated position does not undergo an extrapolation process because it has already been extrapolated forward.

[0089] Step 10: If there is sufficient time for calculation, calculate the position of the next 0.2-second sub-time unit. For example... Figure 2 The process is shown in step 20.

[0090] The compensation time is calculated using formula 6:

[0091] Formula 6: time compensate =TOA-time in_label_140

[0092] The next latitude position, or more precisely defined as the latitude position at the start of the next precise 0.2-second time unit, is calculated using Formula 7:

[0093] Formula 7:Lat next =Lat 110_120 +N / S_vel 166 *time compensate

[0094] Among them, Lat next This refers to the latitude position at the start of the next precise 0.2-second time unit;

[0095] Lat 110_120 Refers to the latitude in Label110 and Label120;

[0096] N / S_vel 166Refers to the north-south velocity in Label166;

[0097] time compensate This refers to the compensation period.

[0098] The next longitude position, or more precisely defined as the longitude position at the start of the next precise 0.2-second time unit, is calculated using Formula 8:

[0099] Formula 8: Lon next =Lon 111_121 +E / W_vel 174 *time compensate

[0100] Among them, Lor next This refers to the longitude position at the start of the next precise 0.2-second time unit;

[0101] Lon 110_120 Refers to the longitude in Label111 and Label121;

[0102] E / W_vel 174 Refers to the east-west velocity in Label174;

[0103] time compensate This refers to the compensation period.

[0104] Step 11: (If sufficient computation time is available), save the position calculated in Step 10 for extrapolation. For example... Figure 2 The process is shown in step 21.

[0105] Save Lat next and Lon next This is so that it can be used in the next extrapolation process, which will begin after the next precise 0.2-second time unit.

[0106] Step 12: (If sufficient computation time is available), determine the parity code for the next sub-time unit. For example... Figure 2 The process flow is shown in 22-24.

[0107] An even / odd encoding format is established and used by the extrapolation process that begins after the next precise 0.2-second time unit.

[0108] If the current sub-time unit is odd, then the next sub-time unit will be even;

[0109] If the current sub-time unit is even, then the next sub-time unit will be odd.

[0110] Step 13: (If sufficient computation time is available), clear the position loading flag. For example... Figure 2 The process flow is shown in step 25.

[0111] Step 14: If computation time is insufficient, determine the parity code for the next sub-time unit. For example... Figure 2 The process flow is shown in 16-18.

[0112] If the current sub-time unit is odd, then the next sub-time unit will be odd;

[0113] If the current sub-time unit is even, then the next sub-time unit will be even.

[0114] Step 15: (If computation time is insufficient), set the position loading flag. For example... Figure 2 The process is shown in step 19.

[0115] Step 16: Determine if the countdown timer has expired. For example... Figure 2 The process flow is shown in step 26.

[0116] Step 17: If the countdown timer has not expired, continue waiting.

[0117] Step 18: If the countdown timer expires, check if the position loading flag is set. For example... Figure 2 The process is shown in step 27.

[0118] Step 19: If the position loading flag is set, calculate the position at the next 0.2-second sub-time unit + 0.2 seconds. For example... Figure 2 The process flow is shown in step 28.

[0119] If the position loading flag is set, the position data must be extrapolated to the next precise 0.2-second sub-time unit plus an additional 200ms. The compensation time is first calculated using Formula 9:

[0120] Formula 9: time compensate =0.2+TOA-time in_label_140

[0121] Step 20: (If the location loading flag is set), save the location to be loaded. For example... Figure 2 As shown in process 29.

[0122] Step 21: If the position loading flag is not set, extrapolate the new position. For example... Figure 2 The process flow is shown in step 30.

[0123] Step 22: (If the location loading flag is not set), the new location data is CPR encoded. For example... Figure 2 The process is shown in step 31.

[0124] Step 23: (If the location loading flag is not set), load the new location data into the BDS cache. For example... Figure 2 The process flow is shown in step 32.

[0125] Step 24: (If the position loading flag is not set), continue the extrapolation process every 0.2-second sub-time unit until the next resynchronization. For example... Figure 2 The process flow is shown in step 33.

[0126] Based on the time given in GNSS, synchronization can be completed at almost any time within a time unit.

[0127] Once synchronization is established, more frequent resynchronization is not needed; generally, synchronization occurs every 10 seconds. In a worse-case scenario, synchronization occurs every 2 seconds.

[0128] ADS-B transmitters using this method achieve synchronization between GNSS data and UTC time, resulting in minimal deviation between the position data in the transmitted messages and the actual data. When other machines receive the air or ground position messages transmitted by this machine, the positioning longitude is high and the position delay is small.

[0129] The method described in this invention utilizes received time stamp pulses, position, velocity, and time data from GNSS to synchronize the time stamp pulses with UTC time, reducing the deviation between the position data in airborne or ground position messages and the real-time position. This method can be applied to a traffic monitoring system and can be implemented using an FPGA+PowerPC architecture, with good results.

[0130] This invention also provides a GNSS timescale and Coordinated Universal Time (UTC) synchronization device, which uses timescale pulses, position, velocity and time data from GNSS to synchronize the timescale pulses with Coordinated Universal Time (UTC).

[0131] Further, the device includes:

[0132] The calculation module is used for:

[0133] Begin by waiting for the leading edge of the GNSS timescale;

[0134] When GNSS data is received, the current time is calculated. The current time refers to the time when the synchronization process is completed. GNSS data includes longitude, latitude, north-south velocity, east-west velocity, Label_150UTC, and Label_140UTC precise time.

[0135] Determine the base and remainder of the sub-time unit;

[0136] Determine the cardinality and parity code of the current sub-time unit;

[0137] Calculate the time to the next precise 0.2-second sub-time unit and set the countdown timer for the next time unit;

[0138] Determine if there is sufficient time for calculation;

[0139] If there is sufficient time for computation, calculate and save the position of the next 0.2-second sub-time unit, determine the parity code of the next sub-time unit, and clear the position loading flag to zero.

[0140] Furthermore, the device also includes:

[0141] The determination module is used for:

[0142] If the calculation time is insufficient, determine the parity code of the next sub-time unit and set the position loading flag. If the countdown timer expires, determine whether the position loading flag is set.

[0143] If the position loading flag is set, calculate the position at the next 0.2-second sub-time unit + 0.2 seconds and save the position for loading.

[0144] Furthermore, the device also includes:

[0145] The processing module is used to extrapolate a new location if the location loading flag is not set, perform CPR encoding on the new location data, and load the new location data into the BDS cache; the extrapolation process continues in every 0.2-second sub-time unit until the next resynchronization.

[0146] The specific execution process of each module in the embodiment of the device of the present invention can be referred to the specific process of the relevant steps of the above method, and will not be repeated here.

[0147] An embodiment of the present invention also provides a GNSS timescale and Coordinated Universal Time synchronization device, comprising: a processor and a memory, wherein the processor is configured to execute instructions stored in the memory, and the processor implements the GNSS timescale and Coordinated Universal Time synchronization method of the present invention by executing the instructions.

[0148] Another embodiment of the present invention provides a computer-readable storage medium storing instructions that, when executed on a computer's processing component, cause the processing component to perform the GNSS timescale and Coordinated Universal Time synchronization method described in the present invention.

[0149] In another embodiment of the present invention, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to execute the GNSS timescale and Coordinated Universal Time synchronization method described in the present invention.

[0150] The above description merely illustrates embodiments of the present invention and is quite specific and detailed; however, it should not be construed as limiting the scope of the patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the scope of protection of the present invention. Furthermore, any parts of the present invention not described in detail are conventional techniques.

Claims

1. A method for synchronizing GNSS time scales with Coordinated Universal Time, characterized in that, Synchronization of the time stamp pulse with Coordinated Universal Time (UTC) is performed using time stamp pulse, position, velocity, and time data from GNSS. The method includes: Begin by waiting for the leading edge of the GNSS timescale; When GNSS data is received, the current time is calculated. The current time refers to the time when the synchronization process is completed. GNSS data includes longitude, latitude, north-south velocity, east-west velocity, Label_150 UTC, and Label_140 UTC precise time. Determine the base and remainder of the sub-time unit; Determine the cardinality and parity code of the current sub-time unit; Calculate the time to the next precise 0.2-second sub-time unit and set the countdown timer for the next time unit; Determine if there is sufficient time for calculation; If there is sufficient time for computation, calculate and save the position of the next 0.2-second sub-time unit, determine the parity code of the next sub-time unit, and clear the position loading flag to zero.

2. The method according to claim 1, characterized in that, The method further includes: If the calculation time is insufficient, determine the parity code of the next sub-time unit and set the position loading flag. If the countdown timer expires, determine whether the position loading flag is set. If the position loading flag is set, calculate the position at the next 0.2-second sub-time unit + 0.2 seconds and save the position for loading.

3. The method according to claim 2, characterized in that, The method further includes: If the location loading flag is not set, the new location is extrapolated, the new location data is CPR encoded, and the new location data is loaded into the BDS cache; the extrapolation process continues in every 0.2-second sub-time unit until the next resynchronization.

4. The method according to claim 2, characterized in that, The method further includes: If the countdown timer has not expired, continue waiting.

5. A GNSS time scale and Coordinated Universal Time synchronization device, characterized in that, Synchronization of the time stamp pulse with Coordinated Universal Time (UTC) is performed using time stamp pulse, position, velocity, and time data from GNSS. The device includes: The calculation module is used for: Begin by waiting for the leading edge of the GNSS timescale; When GNSS data is received, the current time is calculated. The current time refers to the time when the synchronization process is completed. GNSS data includes longitude, latitude, north-south velocity, east-west velocity, Label_150 UTC, and Label_140 UTC precise time. Determine the base and remainder of the sub-time unit; Determine the cardinality and parity code of the current sub-time unit; Calculate the time to the next precise 0.2-second sub-time unit and set the countdown timer for the next time unit; Determine if there is sufficient time for calculation; If there is sufficient time for computation, calculate and save the position of the next 0.2-second sub-time unit, determine the parity code of the next sub-time unit, and clear the position loading flag to zero.

6. The apparatus according to claim 5, characterized in that, The device further includes: The determination module is used for: If the calculation time is insufficient, determine the parity code of the next sub-time unit and set the position loading flag. If the countdown timer expires, determine whether the position loading flag is set. If the position loading flag is set, calculate the position at the next 0.2-second sub-time unit + 0.2 seconds and save the position for loading.

7. The apparatus according to claim 6, characterized in that, The device further includes: The processing module is used to extrapolate a new location if the location loading flag is not set, perform CPR encoding on the new location data, and load the new location data into the BDS cache; the extrapolation process continues in every 0.2-second sub-time unit until the next resynchronization.

8. A GNSS time scale and Coordinated Universal Time synchronization device, characterized in that, include: A processor and a memory, the processor being configured to execute instructions stored in the memory, the processor implementing the method of any one of claims 1 to 4 by executing the instructions.

Images