Week determination method, apparatus, computer storage medium, and terminal

Abstract

The example embodiment determines whether external ephemeris data is valid, determines a first GNSS cycle number by using valid ephemeris data, and ensures the reliability of the obtained first GNSS cycle number; the ephemeris data is selected from pre-stored in a receiver or directly read from outside, and in the case of quickly obtaining ephemeris data, the first GNSS cycle number is ensured to be quickly obtained; in combination of the above, the second GNSS cycle number meeting the reliability is quickly obtained, and technical support is provided for obtaining a GNSS receiver system time.

Description

Technical Field

[0001] This article relates to satellite positioning technology, and in particular to a method, apparatus, computer storage medium and terminal for determining week numbers. Background Technology

[0002] GNSS receivers, modules, and chips possess high-precision time synchronization capabilities. They can provide a precise time synchronization reference for external devices or the entire system via second pulses or timestamps. Depending on the different format protocols output by the GNSS receiver, accurate date and time information can be provided to the system or user for time synchronization. For GNSS receivers, achieving these functions requires obtaining valid GNSS week numbers and seconds within the week. Furthermore, the key factor in when a user obtains GNSS timestamp information is the calculation speed of the GNSS week number and seconds within the week. The main methods for obtaining the GNSS week number and seconds within the week in related technologies are as follows: 1. Real-Time Clock (RTC). 1. Clock: When the GNSS module's RTC module is active, the receiver can obtain the initial time information at the moment of power-on through the RTC module after power-on. The accuracy of the initial time information is related to factors such as the duration of power-off, crystal oscillator aging, and temperature changes. 2. Externally injected auxiliary time: Users can inject auxiliary approximate UTC time into the receiver in a specific format through protocol commands. This method requires GNSS software algorithm support, and the reliability of the injected auxiliary time cannot be guaranteed. 3. Navigation message calculation: Each navigation system broadcasts time information in the navigation message. Once the message frame is successfully synchronized, the week number and second information can be obtained. Under good signal conditions, the time is around 6 seconds. However, the week number broadcast period of GNSS is longer. For example, the broadcast period of the GPS system is 30 seconds. The week number (WN) information is only included in the first subframe of the message. After capturing and tracking the satellite, it is obtained by decoding the message data.

[0003] The methods described above for obtaining GNSS weeks, when using an RTC module to obtain initial time information, require the receiver to have an additional crystal oscillator or RTC chip and a backup power supply, increasing the receiver's hardware cost. Furthermore, the RTC module is highly susceptible to environmental and temperature influences, and incorrect initial time information can lead to GNSS malfunctions. Obtaining GNSS weeks through externally injected auxiliary time requires a network and dedicated services to acquire high-precision auxiliary time, and the accuracy of the injected auxiliary time cannot be guaranteed. Obtaining GNSS weeks through navigation message calculation involves the GNSS receiver stably acquiring and tracking satellite signals, using GPS L1... Taking the C / A frequency as an example, it is necessary to obtain all bits of the first subframe of the message and pass the message verification before the GNSS week number can be calculated. The calculation time of this method depends on the position of the first satellite acquisition time in the message's subframe. Under good signal conditions, the calculation time is between 6 and 30 seconds. It is also highly susceptible to the influence of signal strength and environmental obstruction. Often, weak signals or unstable tracking will cause parsing failure due to message errors, resulting in a longer time to obtain the GNSS week number. This cannot meet the time requirement of the receiver providing synchronization time information for time synchronization.

[0004] In summary, how to quickly obtain GNSS week numbers that meet reliability requirements to provide synchronization time information for time synchronization has become an unsolved problem. Summary of the Invention

[0005] This application provides a week number determination method applied to a GNSS receiver, including: For more than one global navigation satellite system, determine whether the ephemeris data of each system is valid. The ephemeris data includes: ephemeris data pre-stored in the GNSS receiver or read from an external source. When it is determined that there is valid ephemeris data for more than one global navigation satellite system, the first GNSS week number corresponding to that system is obtained by using the ephemeris data of each valid global navigation satellite system. Based on the obtained first GNSS week number, a second GNSS week number is determined for determining the system time of the GNSS receiver.

[0006] On the other hand, embodiments of this application also provide a computer storage medium storing a computer program, which, when executed by a processor, implements the above-described week number determination method.

[0007] Furthermore, embodiments of this application also provide a terminal, including: a memory and a processor, wherein the memory stores a computer program; wherein, The processor is configured to execute computer programs in memory; When the computer program is executed by the processor, it implements the week number determination method described above.

[0008] Furthermore, embodiments of this application also provide a week number determination device, comprising: a judgment unit, a processing unit, and a determination unit; wherein, The judgment unit is set to determine whether the ephemeris data of each of the more than one global navigation satellite systems is valid. The ephemeris data includes ephemeris data that is pre-stored in the GNSS receiver or read from the outside. The processing unit is configured to: when it is determined that there is valid ephemeris data for more than one global navigation satellite system, obtain the first GNSS week number corresponding to each valid global navigation satellite system through the ephemeris data for each valid global navigation satellite system; The determining unit is configured to: determine a second GNSS week number for determining the system time of the GNSS receiver based on the obtained first GNSS week number.

[0009] This exemplary embodiment determines the validity of external ephemeris data and uses valid ephemeris data to determine the first GNSS week number, ensuring the reliability of the obtained first GNSS week number. The ephemeris data is either pre-stored inside the receiver or directly read from the outside, ensuring the rapid acquisition of the first GNSS week number while rapidly obtaining ephemeris data. In summary, a second GNSS week number that meets reliability requirements is quickly obtained, providing technical support for obtaining the GNSS receiver system time.

[0010] Other features and advantages of this application will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the application. Other advantages of this application can be realized and obtained by means of the solutions described in the description and the accompanying drawings. Attached Figure Description

[0011] The accompanying drawings are used to provide an understanding of the technical solutions of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.

[0012] Figure 1 This is a flowchart of the week number determination method according to an embodiment of the present disclosure; Figure 2 This is a structural block diagram of the week number determination device according to an embodiment of the present disclosure. Detailed Implementation

[0013] This application describes several embodiments, but these descriptions are exemplary and not restrictive, and it will be apparent to those skilled in the art that many more embodiments and implementations are possible within the scope of the embodiments described herein. Although many possible combinations of features are shown in the drawings and discussed in the detailed description, many other combinations of the disclosed features are also possible. Unless specifically limited, any feature or element of any embodiment may be used in combination with, or may replace, any feature or element of any other embodiment.

[0014] This application includes and contemplates combinations of features and elements known to those skilled in the art. The embodiments, features, and elements disclosed in this application can also be combined with any conventional features or elements to form unique inventive solutions. Any feature or element of any embodiment can also be combined with features or elements from other inventive solutions to form another unique inventive solution. Therefore, it should be understood that any feature shown and / or discussed in this application can be implemented individually or in any suitable combination. Therefore, the embodiments are not limited except by the limitations imposed by the appended claims and their equivalents. Furthermore, various modifications and changes can be made within the scope of the appended claims.

[0015] Furthermore, in describing representative embodiments, the specification may have presented methods and / or processes as a specific sequence of steps. However, the method or process should not be limited to the specific order of steps described herein, to the extent that it does not depend on such a specific order. As will be understood by those skilled in the art, other sequences of steps are also possible. Therefore, the specific order of steps set forth in the specification should not be construed as a limitation of the claims. Moreover, the claims concerning the method and / or process should not be limited to the steps performed in the written order, and those skilled in the art will readily understand that these orders can be varied and still remain within the spirit and scope of the embodiments of this application.

[0016] Figure 1 This is a flowchart of a week number determination method according to an embodiment of the present disclosure, applied to a GNSS receiver, such as... Figure 1 As shown, it includes: Step 101: For one or more global navigation satellite systems, determine whether the ephemeris data of each system is valid. The ephemeris data includes: ephemeris data pre-stored in the GNSS receiver or read from the outside. Step 102: When it is determined that there is valid ephemeris data for more than one global navigation satellite system, obtain the first GNSS week number corresponding to each valid global navigation satellite system through the ephemeris data for each system. Step 103: Based on the obtained first GNSS week number, determine the second GNSS week number used to determine the system time of the GNSS receiver.

[0017] This exemplary embodiment determines the validity of external ephemeris data and uses valid ephemeris data to determine the first GNSS week number, ensuring the reliability of the obtained first GNSS week number. The ephemeris data is either pre-stored inside the receiver or directly read from the outside, ensuring the rapid acquisition of the first GNSS week number while rapidly obtaining ephemeris data. In summary, a second GNSS week number that meets reliability requirements is quickly obtained, providing technical support for obtaining the GNSS receiver system time.

[0018] Related technologies obtain GNSS week numbers for positioning from externally read or pre-stored ephemeris data, which has reliability issues. When determining the GNSS receiver system time, these technologies default to using a real-time clock, externally injected auxiliary time, and navigation message calculation to determine the GNSS week number. This exemplary embodiment aims to quickly obtain reliable GNSS week number information for determining the GNSS receiver system time by analyzing and determining the reasons why externally read or pre-stored ephemeris data affects the reliability of the GNSS week number, and performing a validity judgment on the ephemeris data. After overcoming the reliability issues through the validity judgment, the GNSS week number for determining the GNSS receiver system time is quickly obtained.

[0019] In one exemplary embodiment, the GNSS receiver system time can be used for time synchronization processing.

[0020] In one exemplary embodiment, the ephemeris data read from an external source includes data read from one or any combination of the following systems: GPS, BDS, and GAL systems.

[0021] This exemplary embodiment can read externally input ephemeris data with reference to related technologies, including receiving external system input data through a pre-configured interface.

[0022] In this exemplary embodiment, the ephemeris data pre-stored in the GNSS receiver may include: ephemeris data stored in the non-volatile memory (NVM) or FLASH of the GNSS receiver.

[0023] In one exemplary embodiment, determining whether the ephemeris data of each system is valid includes: Determine whether the ephemeris data is within its validity period based on the ephemeris reference time (Toe) and receiver time (RcvT); If the ephemeris data is not within its validity period, the ephemeris data is deemed invalid. When the ephemeris data is within its validity period, the position results are calculated based on the observations and ephemeris data, and the residuals of all available observations are calculated in reverse based on the calculated position results; the residual data of the observations are constructed from the available observations that meet the signal quality requirements, and the consistency of the residual data is checked to confirm whether the ephemeris data is valid.

[0024] This exemplary embodiment determines the validity of the ephemeris based on the reference time of the ephemeris and the receiver time obtained by frame synchronization. Then, it uses the ephemeris in combination with available observations to calculate the receiver position. By calculating the position, it back-calculates the observation residuals. Based on the consistency and average value of the observation residuals with good signal, it can further determine whether the ephemeris data is valid. Based on the determination of whether the ephemeris data is valid, it provides technical support for obtaining a reliable first GNSS week number.

[0025] Taking ephemeris broadcast via GPS L1C / A frequency as an example, its validity period is 2 hours. To determine whether the ephemeris data is within its validity period based on the ephemeris's Toe and receiver time (RcvT), the following conditions must be met: RcvT is the approximate receiver time obtained through synchronization with tracked satellite frames, typically with millisecond-level accuracy, sufficient for determining ephemeris validity. The receiver time obtained from successful initial frame synchronization can be combined with the ephemeris's Toe time to determine its validity. However, there may be cases where the externally loaded ephemeris differs from the receiver startup time by an integer number of weeks. Before the receiver parses the GNSS week number from the message, it's impossible to determine if the ephemeris differs by an integer number of weeks. In such cases, it's necessary to construct a positioning equation using the receiver-tracked observations and the loaded ephemeris. The orbital position is then calculated using the injected ephemeris. Position calculation is performed with multiple observations, and reliability is determined based on the consistency of the post-positioning observation residuals. The observation equation is constructed based on the externally loaded ephemeris and the receiver-tracked observations. In the formula, The pseudorange from receiver receiving antenna j to satellite i, in meters; Let be the geometric distance from receiver antenna j to satellite i. In particular, the satellite position is calculated from externally loaded ephemeris data. It's satellite clock bias. Here, I represents the receiver clock bias, and T represents the ionospheric delay along the satellite-to-receiver path. This represents pseudorange observation noise. Based on the above formula, the receiver position X can be calculated using least squares or the Kalman algorithm. Then, based on the calculated position X, the pseudorange residuals of all available observations can be calculated. The algorithm is as follows: Where V is the residual, and G is the state transition matrix of the least squares and Kalman solution model. Based on the formula, the pseudorange residuals of M observations can be obtained. To avoid evaluation errors introduced by unreliable quality of weak signal observations, a new residual array v is constructed by selecting observations with good signal strength. A consistency check is performed on the residuals of this group of observations, and the mean residual is less than [value missing]. The externally loaded ephemeris can then be considered valid, and a typical threshold of 5-50m is recommended. By combining the ephemeris reference time Toe and the receiver time, it is confirmed whether the loaded ephemeris is within its validity period. Then, based on the position result X calculated from the observations and ephemeris, the residuals of all available observations are back-calculated. The observation residual data constructed from observations with good signals is selected, and the validity of the externally loaded ephemeris can be confirmed through consistency detection.

[0026] In one exemplary embodiment, obtaining the first GNSS week number corresponding to each valid global navigation satellite system (GNSS system) using ephemeris data for each GNSS system may include: Obtain the GNSS week number array for all satellites in the system from the ephemeris data; The obtained GNSS week number array is subjected to consistency and gross error checks to obtain the first GNSS week number of the system.

[0027] This exemplary embodiment obtains the first GNSS week number for each system by performing consistency and gross error detection on the GNSS week number array of externally injected ephemeris data.

[0028] Assume the ephemeris data obtained from GPS contains an array of GPS week numbers for N satellites. In this exemplary embodiment, performing consistency checks and gross error removal on the GPS week number array may include: Calculate the variance: ; In the formula, To obtain the average number of GPS weeks in the week number array; A value of 0 indicates that the consistency check has been passed. If the value is not 0, then remove the discrete value with the largest distance from the average value in the week number array, and then process the remaining week numbers. Continue with consistency and gross error checks until... The calculation ends when the value is 0. At this point, for the remaining weeks... At least ensure For samples with more than one star, the threshold for the proportion of remaining weeks to the total sample size needs to be met. above, Typical values ​​can be integers greater than or equal to 3. , A typical threshold can be taken as 0.8, that is... .

[0029] In one exemplary embodiment, for the first GNSS cycle of the GPS system, according to related technologies, it is necessary to compensate for the pre-set number of thousand-cycle reversals x of the GPS system start time. This value is typically preset in the GNSS receiver firmware or configured externally. Using the method described above, the first GNSS week number for each system can be obtained: .

[0030] In one exemplary embodiment, determining a second GNSS week number for determining the GNSS receiver system time based on the obtained first GNSS week number may include: If there is only one first GNSS week number, the first GNSS week number shall be determined as the second GNSS week number; When there are two or more first GNSS week numbers, if the two or more first GNSS week numbers are determined to be consistent by using a fixed difference value determined in advance for different systems, then any one of the first GNSS week numbers is determined as the second GNSS week number.

[0031] When this exemplary embodiment obtains multiple first GNSS week numbers, it achieves reliable determination of second GNSS week numbers through inter-system consistency verification.

[0032] In this exemplary embodiment, the week numbers of the GPS, BDS, and GAL systems are each based on a specific time starting point, and the time starting points for the week numbers of each system are shown in Table 1: Table 1 This exemplary embodiment determines whether the obtained first GNSS week number is correct by checking the reasonableness of the first GNSS week number of different systems. That is, the week numbers of different systems must meet the following conditions: ; ; ; If two or more first GNSS week numbers are found to be consistent by using fixed differences between different systems, it indicates that the obtained first GNSS week numbers are accurate. If there are inconsistencies, since it is impossible to determine which first GNSS week number is incorrect, it is determined that all obtained first GNSS week numbers are incorrect.

[0033] In cases where there is no valid RTC time or external injection auxiliary time during receiver initial startup, or the injection auxiliary time is unreliable, the second GNSS week number can be quickly obtained using the above method.

[0034] In one exemplary embodiment, the week number determination method further includes: The GNSS receiver system time is determined based on the second GNSS week number and the receiver time of the GNSS receiver.

[0035] After obtaining the second GNSS week number in this exemplary embodiment, the receiver time obtained by synchronizing the signal frame can be combined to obtain the GNSS time containing the second GNSS week number and the second within the week. The GNSS time can be converted to UTC time with reference to related technologies, and reliable date and time information, such as UTC time and timestamps, can be provided to the outside world in a timely manner.

[0036] In one exemplary embodiment, the week number determination method further includes: When all system ephemeris data are determined to be invalid, the second GNSS week number is obtained by resolving the navigation message; and / or, When there are inconsistencies between two or more first GNSS week numbers, the second GNSS week number is obtained by solving the navigation message.

[0037] In this exemplary embodiment, when it is not possible to quickly obtain the GNSS week number that meets the reliability requirements, the navigation message is used to calculate the second GNSS week number in order to obtain the GNSS week number that meets the reliability requirements.

[0038] In one exemplary embodiment, the week number determination method further includes: If the GNSS receiver system time has already been obtained through the RTC module or through auxiliary time during initial startup, the GNSS receiver system time is checked and processed using the second GNSS week number as follows: The time information is accurate when the GNSS receiver system time determined based on the second GNSS week number is consistent with the GNSS receiver system time obtained through the RTC module or through auxiliary time. When the GNSS receiver system time determined based on the second GNSS week number is inconsistent with the GNSS receiver system time obtained through the RTC module or through auxiliary time, the GNSS receiver system time determined based on the second GNSS week number shall be used for time correction.

[0039] This exemplary embodiment achieves the correction of the GNSS receiver system time through the above processing, and the reliable time information can be used for time synchronization and other related applications; for example, the time synchronization function can be based on the second pulse method, and the timestamp can be synchronized through the UTC time of the NMEA protocol, the week and the second time within the week, the custom format, etc.

[0040] This disclosure also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the above-described week number determination method.

[0041] This disclosure also provides a terminal, including: a memory and a processor, wherein the memory stores a computer program; wherein, The processor is configured to execute computer programs in memory; When a computer program is executed by a processor, it implements the week number determination method described above.

[0042] Figure 2 This is a structural block diagram of the week number determination device according to an embodiment of the present disclosure, as shown below. Figure 2 As shown, there are a judgment unit, a processing unit, and a determination unit; among which, The judgment unit is set to determine whether the ephemeris data of each of the more than one global navigation satellite systems is valid. The ephemeris data includes ephemeris data that is pre-stored in the GNSS receiver or read from the outside. The processing unit is configured to: when it is determined that there is valid ephemeris data for more than one global navigation satellite system, obtain the first GNSS week number corresponding to each valid global navigation satellite system through the ephemeris data for each valid global navigation satellite system; The determining unit is configured to: determine a second GNSS week number for determining the system time of the GNSS receiver based on the obtained first GNSS week number.

[0043] This exemplary embodiment determines the validity of external ephemeris data and uses valid ephemeris data to determine the first GNSS week number, ensuring the reliability of the obtained first GNSS week number. The ephemeris data is either pre-stored inside the receiver or directly read from the outside, ensuring the rapid acquisition of the first GNSS week number while rapidly obtaining ephemeris data. In summary, a second GNSS week number that meets reliability requirements is quickly obtained, providing technical support for obtaining the GNSS receiver system time.

[0044] In one exemplary embodiment, the ephemeris data read from an external source includes data read from one or any combination of the following systems: GPS, BDS, and GAL systems.

[0045] In one exemplary embodiment, the determining unit is configured to determine whether the ephemeris data of each system is valid, including: Determine whether the ephemeris data is within its validity period based on the ephemeris reference time (Toe) and receiver time (RcvT); If the ephemeris data is not within its validity period, the ephemeris data is deemed invalid. When the ephemeris data is within its validity period, the position results are calculated based on the observations and ephemeris data, and the residuals of all available observations are calculated in reverse based on the calculated position results; the residual data of the observations are constructed from the available observations that meet the signal quality requirements, and the consistency of the residual data is checked to confirm whether the ephemeris data is valid.

[0046] In one exemplary embodiment, the determining unit is configured as follows: If there is only one first GNSS week number, the first GNSS week number shall be determined as the second GNSS week number; When there are two or more first GNSS week numbers, if the two or more first GNSS week numbers are determined to be consistent by using a fixed difference value determined in advance for different systems, then any one of the first GNSS week numbers is determined as the second GNSS week number.

[0047] In one exemplary embodiment, the determining unit is further configured as follows: The GNSS receiver system time is obtained based on the second GNSS week number and the receiver time of the GNSS receiver.

[0048] In one exemplary embodiment, the determining unit is further configured as follows: When all system ephemeris data are determined to be invalid, the second GNSS week number is obtained by resolving the navigation message; and / or, When there are inconsistencies between two or more first GNSS week numbers, the second GNSS week number is obtained by solving the navigation message.

[0049] In one exemplary embodiment, the week number determination device further includes a verification unit, configured to: If the GNSS receiver system time has already been obtained through the RTC module or through auxiliary time during initial startup, the GNSS receiver system time is checked and processed using the second GNSS week number as follows: The time information is accurate when the GNSS receiver system time determined based on the second GNSS week number is consistent with the GNSS receiver system time obtained through the RTC module or through auxiliary time. When the GNSS receiver system time determined based on the second GNSS week number is inconsistent with the GNSS receiver system time obtained through the RTC module or through auxiliary time, the GNSS receiver system time determined based on the second GNSS week number shall be used for time correction.

[0050] It will be understood by those skilled in the art that all or some of the steps, systems, or apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term "computer storage medium" includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

Claims

1. A method for determining the number of weeks, characterized in that, Applications in GNSS receivers include: For more than one global navigation satellite system, determine whether the ephemeris data of each system is valid. The ephemeris data includes: ephemeris data pre-stored in the GNSS receiver or read from an external source. When it is determined that there is valid ephemeris data for more than one global navigation satellite system, the first GNSS week number corresponding to that system is obtained by using the ephemeris data of each valid global navigation satellite system. Based on the obtained first GNSS week number, a second GNSS week number is determined for determining the system time of the GNSS receiver.

2. The method for determining the number of weeks according to claim 1, characterized in that, The ephemeris data read from external sources includes data read from one or any combination of the following systems: GPS, BDS, and GAL systems.

3. The method for determining the number of weeks according to claim 1, characterized in that, The step of determining whether the ephemeris data of each system is valid includes: The validity period of the ephemeris data is determined based on the reference time Toe and the receiver time RcvT. If the ephemeris data is not within its validity period, the ephemeris data is determined to be invalid. When the ephemeris data is within its validity period, the position results are calculated based on the observations and ephemeris data, and the residuals of all available observations are calculated back based on the calculated position results; the residual data of the observations are constructed from the available observations that meet the signal quality requirements, and a consistency check is performed on the residual data to confirm whether the ephemeris data is valid.

4. The method for determining the number of weeks according to claim 1, characterized in that, The step of determining the second GNSS week number for determining the GNSS receiver system time based on the obtained first GNSS week number includes: If there is only one first GNSS week number, the first GNSS week number is determined as the second GNSS week number; When the obtained first GNSS week number includes two or more, if it is determined by a predetermined fixed difference between different systems that the two or more first GNSS week numbers are consistent, then any one of the first GNSS week numbers is determined as the second GNSS week number.

5. The method for determining the number of weeks according to claim 1, characterized in that, After determining the second GNSS week number for determining the GNSS receiver system time based on the obtained first GNSS week number, the week number determination method further includes: The GNSS receiver system time is determined based on the second GNSS week number and the receiver time of the GNSS receiver.

6. The method for determining the number of weeks according to any one of claims 1 to 5, characterized in that, The method for determining the week number also includes: When it is determined that all the ephemeris data from all systems are invalid, the second GNSS week number is obtained by calculating the navigation message; and / or, When there are inconsistencies between two or more of the first GNSS week numbers, the second GNSS week number is obtained by solving the navigation message.

7. The method for determining the number of weeks according to any one of claims 1 to 5, characterized in that, The method for determining the week number also includes: If the GNSS receiver system time has already been obtained through the RTC module or through auxiliary time during initial startup, the GNSS receiver system time is checked and processed using the second GNSS week number as follows: When the GNSS receiver system time determined based on the second GNSS week number is consistent with the GNSS receiver system time obtained through the RTC module or through auxiliary time, the synchronization time information is determined to be accurate. When the GNSS receiver system time determined based on the second GNSS week number is inconsistent with the GNSS receiver system time obtained through the RTC module or through auxiliary time, the GNSS receiver system time determined based on the second GNSS week number shall be used for time correction.

8. A computer storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the week number determination method as described in any one of claims 1 to 7.

9. A terminal, characterized in that, include: A memory and a processor, wherein the memory stores a computer program; wherein, The processor is configured to execute computer programs in memory; When the computer program is executed by the processor, it implements the week number determination method as described in any one of claims 1 to 7.

10. A week number determining device, characterized in that, include: The system comprises a judgment unit, a processing unit, and a determination unit; among which, The judgment unit is set to determine whether the ephemeris data of each of the more than one global navigation satellite systems is valid. The ephemeris data includes ephemeris data that is pre-stored in the GNSS receiver or read from the outside. The processing unit is configured to: when it is determined that there is valid ephemeris data for more than one global navigation satellite system, obtain the first GNSS week number corresponding to each valid global navigation satellite system through the ephemeris data for each valid global navigation satellite system; The determining unit is configured to: determine a second GNSS week number for determining the system time of the GNSS receiver based on the obtained first GNSS week number.

Images