Time calibration method, vehicle-mounted wireless communication box system and motor vehicle

Abstract

The invention provides a time calibration method of a vehicle-mounted wireless communication box (TBOX) system, a vehicle-mounted wireless communication box and a motor vehicle. The method comprises the following steps: calibrating the TBOX time of the vehicle-mounted TBOX system based on a first type of time with the highest priority, which can be obtained currently, in multiple types of time with priority ranking; and restricting the use of other types of times having a lower priority than the priority of the first type of time for calibrating the TBOX time, the plurality of types of times include a global navigation satellite system (GNSS) time obtained from a global navigation satellite system (GNSS) module, a TSP time obtained from a telecommunications service platform (TSP), a network time protocol (NTP) time obtained from a timing server based on the NTP, and a real-time clock (RTC) time obtained from a RTC module, priority ranked from high to low.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle networking technology, and in particular to a time calibration method for a vehicle-mounted wireless communication box (TBOX) system, a vehicle-mounted wireless communication box system, and a motor vehicle. Background Art

[0002] With the development of science and technology, automobile control has become more intelligent, for example, remote locking, scheduled charging, scheduled air conditioning, etc. Such control functions are mainly realized by the vehicle-mounted wireless communication box (Telematics BOX, TBOX). TBOX is a device used for vehicle monitoring and management, which is equipped with an operating system (Android system or Linux system, etc.) and is generally installed in various vehicles. It integrates multiple functions such as positioning, communication and driving records, and can play a role in scheduling and monitoring vehicles, and has a wide range of applications.

[0003] The vehicle components rely on a unified clock source to more accurately record and control the status, actions, internal processing time points, etc. of each component. Accurate time helps to calibrate the occurrence of events. If the time at the TBOX (called TBOX time) is wrong, many programs in the TBOX will be abnormal and fail to execute successfully. The TBOX time can include the system time of its operating system and the hardware time of the control unit (such as MCU). For example, taking the Linux operating system as an example, the hardware time is the time in the BIOS on the motherboard, which is powered by the motherboard battery to maintain operation. When the system is turned on, this hardware time must be read and the initial system time is set based on it.

[0004] Therefore, the accuracy of TBOX time is particularly critical for vehicle control, so a solution for time calibration of TBOX time is needed. Summary of the invention

[0005] According to one aspect of the present application, a time calibration method for a vehicle-mounted wireless communication box (TBOX) system is provided, the method comprising: calibrating the TBOX time of the vehicle-mounted TBOX system based on a first type of time with the highest priority that is currently available among multiple types of time with priority sorting; and limiting the use of other types of time with a lower priority than the first type of time for calibrating the TBOX time, wherein the multiple types of time include GNSS time obtained from a global navigation satellite system (GNSS) module, sorted from high to low priority, TSP time obtained from a telecommunications service platform (TSP), NTP time obtained from a time calibration server based on the Network Time Protocol (NTP), and RTC time obtained from a real-time clock (RTC) module.

[0006] According to an embodiment of the present application, the TBOX time of the on-board TBOX system is calibrated based on the first type of time with the highest priority that is currently available among the multiple types of time, including: when the TBOX time is not calibrated based on the GNSS time, a timing request is sent to the remote communication service platform TSP via the communication link between the on-board TBOX system and the remote communication service platform TSP to request to obtain the TSP service time as the TSP time from the remote communication service platform TSP; and when a timing response including the TSP time is obtained from the remote communication service platform TSP via the communication link, the system time included in the TBOX time is calibrated based on the TSP time as the first type of time, and the TSP time is set in the RTC clock module.

[0007] According to an embodiment of the present application, limiting the use of other types of time having a lower priority than the first type of time for calibrating the TBOX time includes: determining the TSP timing status in response to determining that the TBOX time is to be calibrated using the TSP time, so that the TBOX time is not calibrated based on other types of time except GNSS time.

[0008] According to an embodiment of the present application, the TBOX time of the on-board TBOX system is calibrated based on the first type of time with the highest priority that is currently available among the multiple types of time, including: when the GNSS time is acquired, the system time included in the TBOX time is calibrated based on the GNSS time as the first type of time, and the GNSS time is set in the RTC module.

[0009] According to an embodiment of the present application, limiting the use of other types of time having a lower priority than the first type of time for calibrating the TBOX time includes: determining the GNSS timing status in response to determining that the TBOX time is to be calibrated using the GNSS time, so that the TBOX time is not calibrated based on other types of time.

[0010] According to an embodiment of the present application, the TBOX time of the on-board TBOX system is calibrated based on the first type of time with the highest priority that is currently available among the multiple types of time, including: without calibrating the TBOX time based on the GNSS time and the TSP time, interacting with the time calibration server via the second communication link between the on-board TBOX system and the time calibration server to obtain the NTP time; and calibrating the system time included in the TBOX time based on the NTP time as the first type of time, and setting the NTP time in the RTC module.

[0011] According to an embodiment of the present application, limiting the use of other types of time having a lower priority than the first type of time for calibrating the TBOX time includes: determining the NTP timing status in response to determining that the TBOX time is to be calibrated using the NTP time, so that the RTC time is not used to calibrate the TBOX time.

[0012] According to an embodiment of the present application, the TBOX time of the on-board TBOX system is calibrated based on the first type of time with the highest priority that is currently available among the multiple times, including: when the TBOX time is not calibrated based on the GNSS time, the TSP time, and the NTP time, obtaining the RTC time from the RTC time module, and determining whether the RTC time meets the preset requirements; and when the RTC time meets the preset requirements, using the RTC time to calibrate the TBOX time.

[0013] According to another aspect of the present application, a vehicle-mounted wireless communication box (TBOX) system is also provided, including: a global navigation satellite system (GNSS) module for determining GNSS time; a networking module for obtaining TSP time from a telecommunications service platform (TSP), and obtaining NTP time from a time calibration server based on the Network Time Protocol (NTP), and a control unit for obtaining the GNSS time from the GNSS module, obtaining the NTP time from the networking module, and obtaining the RTC time of the RTC module, and is configured to: calibrate the TBOX time of the vehicle-mounted TBOX system based on the first type of time with the highest priority currently available; and limit the use of other types of time with a lower priority than the first type of time for calibrating the TBOX time, wherein the first type of time is selected from the GNSS time, the TSP time, the NTP time and the RTC time sorted from high to low priority.

[0014] According to another aspect of the present application, a motor vehicle is provided, comprising the above-mentioned vehicle-mounted wireless communication box (TBOX) system.

[0015] By adding a time calibration method based on TSP time to improve the time calibration solution selection, and by giving priorities to a variety of different time calibration solutions, they are combined to improve the calibration effect of the system time. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments of the present application or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings of the embodiments of the present application.

[0017] Figure 1 The figure shows a structural block diagram of a TBOX according to an embodiment of the present application.

[0018] Figure 2 A schematic flow chart of a method for calibrating the system time of a vehicle-mounted TBOX system according to an embodiment of the present application is shown.

[0019] Figure 3 Shown is a reference Figure 2 A schematic process diagram of the described method.

[0020] Figure 4 A block diagram of a motor vehicle is shown. DETAILED DESCRIPTION

[0021] The technical solutions in the embodiments of the present disclosure will be described clearly and completely below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only embodiments of a part of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0022] Generally, the intelligent control function of a car can be realized by relying on a vehicle-mounted wireless communication box (Telematics BOX, TBOX), and the execution of the corresponding control function usually needs to be calibrated based on the system time of the operating system mounted thereon. The calibration process may include, for example, comparing the obtained time for calibration (such as the GNSS time, TSP time or NTP time described later) with the current system time. When the difference between the two exceeds a threshold value (for example, 0), the obtained time for calibration is used as the calibrated system time, or the obtained time for calibration is directly used as the calibrated system time. At this time, the calibrated system time with higher accuracy can also be set to the local RTC module, so it can be collectively referred to as calibrating the TBOX time.

[0023] In some embodiments of the present application, for TBOX, the time calibration method may include three methods: a method based on a global navigation satellite system (GNSS) (e.g., a global positioning system (GPS)), a method based on a network time protocol (NTP) to obtain time from a time calibration server (hereinafter referred to as a method based on NTP), and a method based on the local RTC time of TBOX (hereinafter referred to as a method based on RTC), and the obtained time is respectively referred to as GNSS time, NTP time, and RTC time. These three time calibration methods can have priorities based on the accuracy of the time that can be provided, for example, they are sorted from high to low in terms of priority: a method based on GNSS, a method based on NTP, and a method based on RTC, and the corresponding GNSS time, NTP time, and RTC time also have decreasing priorities. That is, only when a method with a higher priority cannot be used for TBOX time calibration, a method with a lower priority is used for TBOX time calibration.

[0024] Specifically, Figure 1 FIG. 4 shows a structural block diagram of a TBOX system according to an embodiment of the present application. Figure 1 As shown, the TBOX100 system may include a global navigation satellite system (GNSS) module 10, a networking module 20, a real-time clock (RTC) module 30, and a control unit 40. The RTC module 30 may include an RTC clock chip and its associated circuits and software configurations, and may be included in the control unit 40 or expanded outside thereof.

[0025] Optionally, a Global Navigation Satellite System (GNSS) module 10 may be used to determine GNSS time.

[0026] The networking module 20 may be used to obtain NTP time from a time calibration server based on the Network Time Protocol (NTP).

[0027] The control unit 40 is used to obtain the GNSS time from the GNSS module 10, obtain the NTP time from the networking module 20, and obtain the RTC time of the RTC module, and is configured to: calibrate the TBOX time of the on-board TBOX system based on the first type time with the highest priority that can be currently obtained; and limit the use of other types of time with a lower priority than the first type of time for calibrating the TBOX time, wherein the first type of time is selected from the GNSS time, the NTP time and the RTC time sorted from high to low priority.

[0028] The control unit 40 can be connected to the GNSS module to obtain the GNSS time, the networking module 20 can be wirelessly connected to a remote time calibration server to obtain the NTP time, and the control unit can be connected to the RTC module (e.g., the RTC clock chip and its associated circuits and software configuration) via a bus to obtain the RTC time. Optionally, the RTC module can generate time information according to the oscillation frequency and transmit the time information to the core part of the control unit so that the control unit obtains the current RTC time according to the received time information.

[0029] Optionally, the networking module 20 may include a network access device (NAD), and the networking module 20 may exchange information with the control unit. For example, when the TBOX system is just powered on, the network access device (NAD) may request the RTC time from the control unit, and the control unit may return a response including the RTC time to the network access device. In addition, in some embodiments, certain functions of the networking module may also be integrated into the control unit or regarded as part of the control unit. For example, the control unit may also directly obtain the NTP time from a remote time synchronization server based on the Network Time Protocol (NTP).

[0030] Usually, when the power is just turned on or when the GNSS time or NTP time cannot be obtained, the control unit can set the system time of the operating system installed therein according to the RTC time. In addition, the network access device NAD is also equipped with an operating system accordingly, so the network access device can also set the system time of the operating system installed therein according to the RTC time obtained from the control unit. When setting the system time based on the RTC time, you can first determine whether the current system time is correct (for example, if the system time is less than 2019-01-01 08:00:00, it is considered that the system time is wrong) to determine whether to use the RTC time as the system time. For example, when it is determined that the system time is incorrect, the system time is set based on the RTC time.

[0031] The following introduces the processes of the GSP-based method, the NTP-based method, and the RTC-based method.

[0032] In the GNSS-based method, the control unit of TBOX can obtain GNSS time from the GNSS module, and use the obtained GNSS time to calibrate the system time of TBOX. For example, when the GNSS module can obtain the position (the longitude and latitude are valid) and the time has not been reset (that is, the obtained time is the current time), at this time, since the priority of GNSS time is higher than NTP time and RTC time, the control unit of TBOX no longer performs time calibration based on NTP time and RTC time (for example, compare GNSS time with the current system time, and when the difference between the two is greater than a threshold, determine GNSS time as system time), that is, it can limit the use of other types of time (that is, NTP time and RTC time with lower priority), for example, when the TBOX operating system is Linux, it can be restricted by acquiring a mutex lock. After the GNSS time is set as the system time and synchronized to the control unit, the restriction on obtaining other types of time can be cancelled, such as releasing the mutex lock. However, in this solution, when the GNSS signal is not good, it may result in the inability to obtain GNSS time for system time calibration.

[0033] In the NTP-based method, the networking module of TBOX can interact with a remote server to calibrate the system time. For example, when the networking module realizes the connection with the remote server (for example, a public / private network connection), and the TBOX time has not been calibrated by the GNSS time and the system time has not been initialized, the NTP time can be obtained based on the connection to calibrate the system time, and the use of other types of time (i.e., RTC time with a lower priority) can be restricted. For example, when the TBOX operating system is Linux, the restriction can be made by acquiring a mutex lock, and TBOX, as an NTP client, interacts with a remote time server as an NTP server via the networking module using ntpdate0.cn.pool.ntp.org and / etc / init.d / ntpd restart to implement the time calibration operation, thereby achieving system time calibration. Optionally, the server synchronizes the NTP time to the control unit of TBOX via the networking module using a heartbeat packet. After the predetermined time period ends, the control unit cancels the restriction on obtaining other types of time, for example, releasing the mutex lock after 30 seconds.

[0034] However, the NTP-based method is based on network connection, so data network congestion may cause delays in the obtained time, and may also be affected by the target server, so the obtained time may be greatly deviated and without any constraints.

[0035] In the RTC time-based method, the local RTC time is used as the system time only when it is determined that the system time is wrong (for example, less than 2019-01-01 08:00:00) and the GNSS time and NTP time cannot be obtained. The accuracy of the local RTC time is related to the external working environment and may cause large errors.

[0036] It can be seen that the above-mentioned methods all have corresponding defects, which may cause the calibrated system time to be inaccurate when calibrating the system time. Therefore, the embodiments of the present application further provide a solution to improve the above-mentioned solution, for example, by adding a new time calibration method to improve the time calibration solution selection, and optionally giving it priority relative to the above-mentioned three methods, so as to combine them to improve the calibration effect of the system time.

[0037] In practical applications, TBOX can usually exchange information with a telematics service platform (TSP) through its networking module, for example, based on wireless communication technology (e.g., cellular base station wireless technology), and TSP generally has more accurate time. Therefore, it can be considered that TBOX can obtain time (called TSP time) from TSP during the interaction.

[0038] in this case, Figure 1 The control unit or networking module shown may also obtain the Telematics Service Platform (TSP) time from the TSP.

[0039] For example, after TBOX establishes a communication link with TSP, the control unit of TBOX can send a TSP timing request on the communication link via the networking module, and obtain a response including time information from TSP. For example, as an example, the timing request sent by TBOX to TSP can include an inquiry type askType (0: Beijing time, 1: UTC time), and the response can include a response code responseCode (0: normal) and TSP service time tspServiceTime (YYMMddHHmmss) accurate to seconds. In this way, the control unit of TBOX can obtain the TSP time and use it for system time calibration.

[0040] Therefore, according to some aspects of the present application, a method for calibrating the TBOX time of the vehicle-mounted TBOX system according to some embodiments of the present application is provided.

[0041] Figure 2A flow chart of a method for calibrating the system time of a vehicle-mounted TBOX system according to some embodiments of the present application is shown. For example, as described above, the vehicle-mounted TBOX system has the ability to obtain multiple types of time, and the multiple types of time have priorities, for example, including GNSS time obtained from a global navigation satellite system (GNSS) module, TSP time obtained from a telematic service platform (TSP), NTP time obtained from a time calibration server based on a network time protocol (NTP), and RTC time obtained from a real-time clock (RTC) module, which are sorted from high to low priority.

[0042] like Figure 2 As shown, in step S210, the TBOX time (eg, including system time and hardware time) of the vehicle-mounted TBOX system is calibrated based on the first type of time with the highest priority that is currently available among the multiple types of time with priority sorting.

[0043] As mentioned above, due to the current GNSS signal status or network connection status, etc., the time currently available for system time calibration may not be GNSS time, for example, it may be TSP time, NTP time and / or RTC time. Therefore, the first type of time here may be one of GNSS time, TSP time, NTP time or RTC time.

[0044] Optionally, the cycle of the time calibration process operation (time calibration cycle) can be the same as the operation cycle of the TBOX, or it can be another preset cycle that is different from the operation cycle of the TBOX. For example, one TBOX operation cycle can perform multiple time calibrations, or multiple TBOX operation cycles can perform one time calibration.

[0045] In step S220, the use of other types of time having a lower priority than the first type of time for calibrating the TBOX time is restricted.

[0046] That is, when a time with a higher priority is acquired and can be used to calibrate the system time, it is not necessary to acquire or use other types of acquired time to calibrate the TBOX time.

[0047] More specifically, the method is further introduced below based on that the first type of time is GNSS time, TSP time, NTP time or RTC time.

[0048] For example, when the first type of time is GNSS time, when the GNSS time is obtained (for example, the GNSS module determines the 3D positioning state and the GNSS time, so that the control unit obtains the GNSS time), the system time included in the TBOX time is calibrated based on the GNSS time as the first type of time, and the GNSS time can be set to the RTC clock module of the vehicle-mounted TBOX system. Of course, it is also possible to calibrate the TBOX time based on the currently obtained GNSS time when the TBOX time calibration has not been performed based on the GNSS time before during this TBOX operation cycle. Optionally, the GNSS time can be stored in a corresponding location as an updated system time, for example, in the file directory / persist / misc.conf of the operating system.

[0049] Then, for the process of limiting other types of time for calibration, in response to determining that the system time is calibrated using the GNSS time, the GNSS timing status is determined (for example, set to a valid status, such as a status mark of 1), so that the TBOX time is not calibrated based on other types of time.

[0050] For example, the control unit may synchronize the GNSS timing status to the networking module, so that the networking module may not interact with the telematics service platform (TSP) and the timing server, or the networking module does not interact with the control unit, so that the control unit does not obtain other types of time for calibrating the system time. Optionally, the synchronization is performed once per TBOX operation cycle.

[0051] For another example, when the first type of time is TSP time, when the TBOX time is not calibrated based on the GNSS time, a timing request is sent to the remote communication service platform TSP via the communication link between the on-board TBOX system and the remote communication service platform TSP, so as to request to obtain the TSP service time as the TSP time from the remote communication service platform TSP; then, when a timing response including the TSP time is obtained from the remote communication service platform TSP via the communication link, the system time included in the TBOX time is calibrated based on the TSP time as the first type of time, and the TSP time is set in the RTC clock module.

[0052] For example, as described above, after TBOX establishes a communication link with TSP, the control unit of TBOX can send a TSP timing request (e.g., TSP timing request of 3021) on the communication link via the networking module, and obtain a response including time information from TSP. For example, as an example, the timing request sent by TBOX to TSP may include an inquiry type askType (0: Beijing time, 1: UTC time), and the response may include a response code responseCode (0: normal) and TSP service time tspServiceTime (YYMMddHHmmss) accurate to seconds. In this way, the control unit of TBOX can obtain the TSP time and use it for system time calibration.

[0053] Then, for the process of limiting other types of time for calibration, the TSP timing status can be determined (for example, set to a valid status, such as a status mark of 1) in response to determining that the system time is calibrated using the TSP time, so that the TBOX time is not calibrated based on other types of time except GNSS time.

[0054] For example, the control unit may synchronize the TSP time state to the networking module, so that the networking module may not interact with the time server, or the networking module does not interact with the control unit, so that the control unit does not obtain other types of time for calibrating the system time. Optionally, the synchronization is performed once per TBOX operation cycle.

[0055] For another example, when the first type of time is NTP time, in the case where the system time is not calibrated based on the GNSS time and the TSP time, the vehicle-mounted TBOX system interacts with the time calibration server via the second communication link between the vehicle-mounted TBOX system and the time calibration server to obtain the NTP time; and the system time included in the TBOX time is calibrated based on the NTP time as the first type of time, and the NTP time is set in the RTC clock module. For example, after the SIM card of the TBOX is successfully stationed (i.e., a communication link is established), the system time is delayed for 8 seconds. If the system time has not been calibrated based on the GNSS time and the TSP time, the system time is calibrated based on the acquired NTP time.

[0056] Then, for the process of limiting other types of time for calibration, the NTP time calibration state can be determined in response to determining that the system time is calibrated using the NTP time (e.g., set to a valid state, such as a state mark of 1), so that the RTC time is not used to calibrate the system time. Optionally, the TBOX is synchronized once per operation cycle.

[0057] Optionally, in some embodiments, a self-developed dedicated NTP server and client and a self-built NTP server platform can be used to replace the existing shared time calibration server and its platform, thereby avoiding interference from uncertain factors on public servers and network connections, thereby obtaining more accurate NTP time, making the NTP-based time calibration solution more accurate and more reliable.

[0058] For another example, when the first type of time is RTC time (i.e., the hardware time of the control unit), without calibrating the system time based on the GNSS time, the TSP time, and the NTP time, the RTC time is obtained from the RTC time module, and it is determined whether the RTC time meets the preset requirements; and when the RTC time meets the preset requirements, the RTC time is used to calibrate the system time.

[0059] For example, in the case where the system time is not calibrated based on the GNSS time, the TSP time, and the NTP time, the RTC time calibration state can be set to valid, and it is determined whether there is system time, whether the RTC time is within a suitable time range (for example, greater than 8:00 a.m. on January 21, 2022), and whether it is greater than the current system time (i.e., the software time of the operating system). If there is no system time, or if there is system time and the RTC time is within a suitable time range and the difference with the current system time (for example, the time stored in / persist / misc.conf) is greater than a threshold, the RTC time is used to calibrate the system time.

[0060] Calibration based on RTC time usually occurs when TBOX is just powered on or awakened from sleep mode, because there is usually no GNSS time, TSP time or NTP time at this time. For example, when TBOX is just powered on, the network access device NAD in the networking module can send a request for RTC time to the control unit, and the control unit can return a response including RTC time (and optionally indicate that its system time needs to be updated / set based on RTC time). At this time, the control unit uses RTC time to set the initial system time (if possible, it will be calibrated based on the subsequently acquired GNSS time, TSP time or NTP time), and the network access device NAD can also use RTC time as its system time for various interactions. In addition, when TBOX wakes up from sleep mode, the network access device NAD in the networking module, for example, may send a request for RTC time to the control unit, and the control unit may return a response including the RTC time (and optionally does not indicate the need to update / set the system time based on the RTC time), but the control unit and / or the networking module does not necessarily use the RTC time to set the initial system time. The RTC time will be used as the system time only when and only when the RTC time meets the preset requirements. At the same time, the network access device NAD will use the RTC time as the system time for various interactions.

[0061] In addition, for system time calibration at the network access module NAD, an RTC module can be set at the NAD, so that the system time at the NAD can be set based on the RTC time of the RTC module without obtaining the RTC time from the control unit, which can make the system time at the NAD more accurate and more stable.

[0062] Optional, Figure 2 The time calibration method shown may also include the following steps: using a dedicated thread to monitor the change of the system time, and in response to determining that the change of the system time is deviated, triggering to obtain the GNSS time from the GNSS module or to obtain the TSP time from the TSP. In addition, in the case where the GNSS time and the TSP time cannot be obtained, triggering to obtain the NTP time or the RTC time.

[0063] Figure 3 Shown is a reference Figure 2 A schematic process diagram of the described method. Figure 3 The GNSS time synchronization uses GPS time synchronization as an example, but it is not limited to it.

[0064] First, TBOX is powered on and started. As mentioned above, the initial system time can be set according to the RTC time. Then, it is determined whether the GNSS time can be obtained at this time (for example, polling every 5 seconds). If the GNSS time is currently obtained and the time calibration based on the GNSS time has not been performed in the current time calibration cycle, it is optional to further determine whether the GNSS time meets the requirements (for example, if it is greater than 8:00 am on January 21, 2022, it means that the GNSS time is not wrong), and then the TBOX time is calibrated based on the (compliant) GNSS time, for example, the GNSS time is synchronized to the system time, and synchronized to the control unit so that it no longer uses its RTC time (hardware time). Since GNSS time has the highest priority, if the time calibration is performed based on the GNSS time in this time calibration cycle, the current time calibration process can be completed.

[0065] If the GNSS time is not currently acquired or the time calibration has been performed based on the GNSS time in the current time calibration cycle, the "No" step can be performed to reach the TSP time calibration part. If in response to determining before logging into the TSP that the time calibration has not been performed based on the GNSS time and the TSP time in the current calibration cycle, and the TSP time is acquired after logging into the TSP, it is optional to further determine whether the TSP time meets the requirements (for example, if it is greater than 8:00 am on January 21, 2022, it means that the TSP time is not wrong), and then perform time calibration based on the (compliant) TSP time, for example, synchronize the TSP time to the system time, and synchronize it to the control unit so that it no longer uses its RTC time (hardware time). Thereafter, if the GNSS time is acquired based on polling, the GNSS time can be reused for time calibration, thereby replacing the current time obtained based on the TSP time calibration.

[0066] In the TSP time calibration part, if the GNSS time and TSP time are not currently acquired or the time calibration has been performed based on the TSP time or GNSS time during the current time calibration cycle, the "No" step can be performed to reach the NTP time calibration part. For example, in the NTP time calibration part, in response to connecting to the time calibration server (connecting to the public / private APN), it is determined whether the TSP has been logged in. If so, a predetermined time is waited to further determine whether a higher priority TSP time can be acquired, and further determine whether a time calibration has been performed based on the GNSS time, TSP time, and NTP time; if the TSP has not been logged in, it is directly determined whether the time calibration has been performed based on the GNSS time, TSP time, and NTP time. If time calibration has not been performed based on GNSS time, TSP time, and NTP time during the current time calibration cycle, it is optional to further determine whether the NTP time meets the requirements (for example, if it is greater than 8:00 a.m. on January 21, 2022, it means that the NTP time is not wrong), and then calibrate based on the (compliant) NTP time, for example, synchronize the NTP time to the system time, and synchronize it to the control unit so that it no longer uses its RTC time (hardware time). Thereafter, if GNSS time or TSP time calibration is obtained based on polling, the GNSS time or TSP time can be reused for time calibration, thereby replacing the current time obtained based on NTP time calibration.

[0067] In the NTP time calibration part, if the GNSS time, TSP time and NTP time are not obtained (for example, when just powered on or woken up) or the time calibration has been performed based on the GNSS time, TSP time and NTP time, the "No" step can be performed to reach the RTC time calibration part. For example, the RTC time calibration state can be set to valid, and the RTC time can be obtained from the RTC module. If the RTC time cannot be obtained (that is, the time calibration cannot be performed based on the RTC time at this time), wait for the next polling opportunity to re-execute the process. If the RTC time can be obtained and the time calibration has not been performed based on the GNSS time, TSP time, NTP time and RTC time, if the RTC time calibration state is valid at this time and the RTC time meets the preset requirements, the RTC time can be used for time calibration, that is, the RTC time is used as the system time and the control unit uses the RTC time. On the contrary, if the RTC time calibration state is invalid (for example, the RTC time calibration cannot be used according to the requirements of certain application scenarios), or the RTC time does not meet the preset requirements, the RTC time is not used for time calibration.

[0068] In addition, in the RTC time calibration part, if the RTC time cannot be obtained or the time calibration has been performed based on the GNSS time, TSP time, NTP time or RTC time, the GNSS time calibration part can be returned to poll to repeat the above steps. Assuming that the time calibration has been performed based on the NTP time, if the GNSS time is not obtained based on the next polling, the TSP time calibration part is performed, and if the TSP time is obtained at this time, and the time calibration has not been performed based on the TSP time and the GSP time, the time calibration can be performed based on the obtained TSP time to replace the previous system time based on the NTP time. Through polling, it can be determined at a predetermined time interval whether a time with a higher priority can be used for time calibration.

[0069] Therefore, in the embodiment of the present application, a time calibration method based on TSP time is added to improve the selection of time calibration schemes, and a plurality of different time calibration schemes are given priorities, so as to improve the calibration effect of the system time. In addition, for the time calibration scheme based on NTP time, by independently developing the NTP server and client and building the NTP server platform, the existing shared time calibration server and its platform are replaced, so that the time calibration scheme based on NTP is more accurate and more reliable. In addition, an RTC time module is set for the network access device NAD, so that the network access device NAD can directly obtain the RTC time without requesting the RTC time from the control unit, which can improve the accuracy of the system time of the network access device NAD and make it more stable. In addition, a dedicated thread can be set to monitor the change of time. If a deviation occurs, GNSS or TSP timing is triggered to make GNSS and TSP timing more adaptive.

[0070] According to another aspect of the present application, a motor vehicle is also provided, such as Figure 4 The motor vehicle may include Figure 1 The described vehicle-mounted wireless communication box (Telematics BOX, TBOX) is used to realize intelligent control functions of the car, such as remote locking of the car, scheduled charging, scheduled air conditioning, etc.

[0071] As an example, the control unit of the present application may include an integrated circuit chip having a signal processing capability. The above-mentioned control unit may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, for implementing or executing the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The control unit may also include a memory or be combined with a memory, and the memory may include a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and may also store a computer executable program, which, when executed, enables the control unit to implement various operations as described above. A computer executable program may also be stored in the internal memory, which, when executed, enables the control unit to implement various operations as described above.

[0072] The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. It should be noted that the memory of the methods described herein is intended to include, but is not limited to, these and any other suitable categories of memory.

[0073] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the methods and devices according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment, or a part of a code, and the module, program segment, or a part of the code contains at least one executable instruction for realizing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, or the various modules mentioned, can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0074] The embodiments of the present application described in detail above are merely illustrative and not restrictive. It should be understood by those skilled in the art that various modifications and combinations may be made to these embodiments or their features without departing from the principles and spirit of the present application, and such modifications should fall within the scope of the present application.

Claims

1. A time calibration method for a vehicle-mounted wireless communication box (TBOX) system, comprising: calibrating the TBOX time of the vehicle-mounted TBOX system based on a first type of time with the highest priority that is currently available among the plurality of types of time with priority sorting; as well as restricting the use of other types of time having a lower priority than the first type of time for calibrating the TBOX time, Among them, the multiple types of time include GNSS time obtained from the Global Navigation Satellite System (GNSS) module, TSP time obtained from the Telecommunications Service Platform (TSP), NTP time obtained from the time calibration server based on the Network Time Protocol (NTP), and RTC time obtained from the Real-Time Clock (RTC) module, sorted from high to low priority.

2. The method according to claim 1, wherein: Based on the first type of time with the highest priority that is currently available among the multiple types of time, calibrating the TBOX time of the vehicle-mounted TBOX system includes: In the case where the TBOX time is not calibrated based on the GNSS time, sending a timing request to the telematics service platform TSP via a communication link between the on-board TBOX system and the telematics service platform TSP, so as to request to obtain the TSP service time as the TSP time from the telematics service platform TSP; and When a timing response including the TSP time is obtained from a remote communication service platform TSP via the communication link, the system time included in the TBOX time is calibrated based on the TSP time as the first type of time, and the TSP time is set in the RTC clock module.

3. The method according to claim 2, wherein: Restricting the use of other types of time having a lower priority than the first type of time for calibration of TBOX time includes: In response to determining that the TBOX time is to be calibrated using the TSP time, a TSP timing status is determined such that the TBOX time is not calibrated based on other types of time except for the GNSS time.

4. The method according to claim 1, wherein: Based on the first type of time with the highest priority that is currently available among the multiple types of time, calibrating the TBOX time of the vehicle-mounted TBOX system includes: In the case where the GNSS time is acquired, the system time included in the TBOX time is calibrated based on the GNSS time as the first type of time, and the GNSS time is set in the RTC module.

5. The method according to claim 4, wherein: Restricting the use of other types of time having a lower priority than the first type of time for calibration of TBOX time includes: In response to determining that the TBOX time is to be calibrated using the GNSS time, a GNSS timing status is determined such that the TBOX time is not calibrated based on other types of time.

6. The method according to claim 1, wherein: Based on the first type of time with the highest priority that is currently available among the multiple types of time, calibrating the TBOX time of the vehicle-mounted TBOX system includes: In the case where the TBOX time is not calibrated based on the GNSS time and the TSP time, interacting with a time calibration server via a second communication link between the onboard TBOX system and the time calibration server to obtain the NTP time; and The system time included in the TBOX time is calibrated based on the NTP time as the first type time, and the NTP time is set in the RTC module.

7. The method according to claim 6, wherein: Restricting the use of other types of time having a lower priority than the first type of time for calibration of TBOX time includes: In response to determining that the TBOX time is to be calibrated using the NTP time, an NTP time calibration state is determined such that the RTC time is not used to calibrate the TBOX time.

8. The method according to claim 1, calibrating the TBOX time of the vehicle-mounted TBOX system based on the first type of time with the highest priority that is currently available among the multiple times, comprises: In the case where the TBOX time is not calibrated based on the GNSS time, the TSP time and the NTP time, acquiring the RTC time from the RTC time module, and determining whether the RTC time meets the preset requirement; as well as When the RTC time meets the preset requirements, the RTC time is used to calibrate the TBOX time.

9. A vehicle-mounted wireless communication box (TBOX) system, comprising: A Global Navigation Satellite System (GNSS) module for determining GNSS time; A networking module, used to obtain TSP time from a telecommunications service platform (TSP), and obtain NTP time from a time calibration server based on the Network Time Protocol (NTP), and A control unit is used to obtain the GNSS time from the GNSS module, obtain the NTP time from the networking module, and obtain the RTC time of the RTC module, and is configured to: Calibrate the TBOX time of the vehicle-mounted TBOX system based on the first type time with the highest priority that can be currently obtained; as well as restricting the use of other types of time having a lower priority than the first type of time for calibrating the TBOX time, The first type of time is selected from the GNSS time, the TSP time, the NTP time and the RTC time which are sorted in descending order of priority.

10. A motor vehicle comprising the on-board wireless communication box (TBOX) system according to claim 9.

Images