Vehicle time zone calibration methods, systems and vehicles
By combining local and cloud-based rule bases in the vehicle time zone calibration system and using photovoltaic panel voltage data to predict time zone offset, the accuracy and reliability issues of time zone calibration under different operating conditions are solved, improving the intelligent experience and operational efficiency of the vehicle system.
Patent Information
- Application Number
- CN202611474434.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-21
- Publication Date
- 2026-11-10
AI Technical Summary
Existing vehicle time zone calibration solutions cannot adapt to different operating conditions, especially in environments with weak or no GPS signals, which causes the time zone synchronization calibration link to fail, requiring manual adjustment of the time zone and resulting in a poor intelligent experience.
A time zone calibration method adapted to different working conditions is adopted. It combines local rule bases and cloud rule bases to determine target calibration rules through vehicle information, including calibration rules for working conditions with positioning network, without positioning network, and without positioning offline. It uses photovoltaic panel voltage data to predict time zone offset in the scenario without positioning offline, and performs calibration in combination with the vehicle-mounted land and ocean grid database.
Ensuring the accuracy and reliability of time zone calibration under various operating conditions improves the operating efficiency of the vehicle system, avoids time zone errors and abnormal time display, reduces the tediousness of manual adjustment, and adapts to the needs of cross-regional driving.
Smart Images

Figure CN123074628A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of vehicle technology, and more specifically to vehicle time zone calibration methods, systems, and vehicles. Background Technology
[0002] With the globalization of the automotive industry and the large-scale export of new energy vehicles, it is becoming increasingly common for vehicles to be sold to different countries and used across time zones and latitudes. Because different countries or regions use significantly different time zone offsets and daylight saving time switching rules, and some countries or regions adjust their time zone policies periodically, vehicles exported overseas need to complete timely and accurate time zone synchronization calibration at critical times such as power-on and cross-regional driving. This is to avoid systemic risks such as incorrect timestamps for driving events, failure of remote dispatch and diagnostic logic, and inaccurate vehicle log traceability.
[0003] Existing vehicle time zone calibration solutions typically rely on the vehicle's GPS signal and vehicle-to-cloud communication network. Under normal operating conditions with normal GPS positioning and uninterrupted network connectivity, the system matches the corresponding time zone using GPS latitude and longitude, and combines this with time zone rules issued by the cloud server to complete the vehicle's time calibration. However, vehicles operating overseas face complex and diverse real-world environments. They may enter environments with weak or no GPS signals, such as underground parking garages, tunnels, high-rise buildings, canyons, or areas with satellite signal interference. They may also enter remote areas, cross-border blind spots, or underground parking lots, where network signals are weak or completely disconnected. In these situations, conventional calibration solutions relying solely on GPS and the network will be unable to obtain accurate vehicle location and reliable time zone rules, leading to the failure of the vehicle's time zone synchronization calibration link and a systematic deviation in vehicle time. In such cases, users must manually connect to a mobile hotspot and manually adjust the time zone, which is cumbersome and results in a poor user experience. Summary of the Invention
[0004] In view of the shortcomings of the prior art, the purpose of this application is to provide a vehicle time zone calibration method, system and vehicle, which aims to solve the problem that the existing time zone calibration scheme cannot be adapted to different operating conditions of the vehicle and can only be adjusted manually.
[0005] In a first aspect, embodiments of this application provide a vehicle time zone calibration method, the vehicle time zone calibration method comprising: when the vehicle is powered on, determining a time zone calibration condition based on collected vehicle information, wherein the time zone calibration condition includes a location-connected network condition, a location-unconnected network condition, and a location-unconnected offline condition; obtaining time zone calibration information corresponding to the vehicle information from a local rule base or a cloud rule base according to the time zone calibration condition, and determining a target calibration rule according to the time zone calibration information; and performing vehicle time zone synchronization calibration processing according to the target calibration rule.
[0006] Compared to traditional calibration schemes that rely solely on network positioning to obtain time zone information, this method can match and adapt calibration rules to different hardware and software operating states of the vehicle, covering the needs of vehicle use in all scenarios. It can obtain real-time updated high-precision time zone information from cloud data when the positioning and network signal is good, ensuring the accuracy of time zone calibration when traveling across regions. It can also complete time zone calibration based on a pre-stored local rule library when there is no positioning signal or the vehicle is offline and disconnected from the network, avoiding the problem of time zone confusion and abnormal time display due to signal loss. It solves the problem that existing time zone calibration schemes cannot adapt to different vehicle operating conditions and can only be adjusted manually. While ensuring the reliability and accuracy of time zone calibration, it improves the overall efficiency of vehicle system operation.
[0007] In one possible embodiment, based on the time zone calibration condition, time zone calibration information corresponding to the vehicle information is obtained from a local rule base or a cloud rule base, and a target calibration rule is determined based on the time zone calibration information. This includes: when the time zone calibration condition is a location-connected condition, obtaining first time zone calibration information corresponding to the vehicle information from the cloud rule base based on the vehicle location parameters in the vehicle information, and determining a target calibration rule based on the matching result between the location parsing result and the first time zone calibration information; when the time zone calibration condition is a location-free condition, using the first time zone calibration information obtained from the cloud rule base based on the vehicle location parameters in the vehicle information as the target calibration rule; when the time zone calibration condition is a location-free offline condition, determining a target calibration rule based on second time zone calibration information obtained from the local rule base based on the vehicle location parameters and photovoltaic panel voltage data in the vehicle information, wherein the time zone calibration information is either the first time zone calibration information or the second time zone calibration information.
[0008] This scenario-specific rule retrieval scheme significantly improves the adaptability and accuracy of time zone calibration. In scenarios with location and network connectivity, relying on the dynamic update capability of the cloud-based rule library and combining it with dual verification of location data, it can reduce time zone matching errors caused by cross-regional sales and long-distance travel across time zones. In scenarios without location and network connectivity, leveraging the full coverage capability of the cloud-based rule library, time zone matching can be completed without location data. In offline scenarios without location connectivity, the target calibration rule is determined by combining locally pre-stored rules and photovoltaic panel voltage data, enabling calibration to be completed in extreme scenarios where the vehicle is completely offline and has no location signal, thus improving the calibration success rate in offline scenarios. At the same time, local rule retrieval does not rely on network transmission, shortening the calibration time in this scenario and effectively ensuring the availability of the central control time system when the vehicle is offline.
[0009] In one embodiment, determining a target calibration rule based on the matching result between the positioning analysis result and the first time zone calibration information includes: if the positioning analysis result and the first time zone calibration information are successfully matched, using the positioning analysis result as the target calibration rule, wherein a successful match indicates that the time zone identifier in the positioning analysis result is the same as the time zone identifier in the first time zone calibration information, and the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is less than a preset time difference; if the positioning analysis result and the first time zone calibration information are not matched, using the first time zone calibration information as the target calibration rule, wherein a failed match indicates that the time zone identifier in the positioning analysis result is different from the time zone identifier in the first time zone calibration information, and / or the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is greater than or equal to a preset time difference.
[0010] This matching and determination mechanism performs dual verification from two core dimensions: time zone identifier and time offset. It can filter out time zone information deviations caused by satellite signal drift and base station positioning errors during the positioning and analysis process.
[0011] In some embodiments, determining a target calibration rule based on second time zone calibration information obtained from the local rule base based on vehicle location parameters and photovoltaic panel voltage data in the vehicle information includes: if the photovoltaic panel voltage data is not present in the vehicle information, using third time zone calibration information obtained from the local rule base based on the vehicle location parameters as the target calibration rule; if the photovoltaic panel voltage data is present in the vehicle information, determining a predicted time zone offset based on the photovoltaic panel voltage data, and using fourth time zone calibration information obtained from the local rule base based on the vehicle location parameters and the predicted time zone offset as the target calibration rule, wherein the second time zone calibration information is either the third time zone calibration information or the fourth time zone calibration information.
[0012] When a vehicle can only provide its location parameters, time zone calibration can be quickly completed using a locally stored rule base, avoiding calibration lag caused by network request delays. When photovoltaic panel voltage data is available, the actual time zone can be deduced by observing the changes in photovoltaic panel output voltage with solar radiation intensity. Combined with the vehicle location parameters, time zone offset errors can be corrected. Compared to calibration methods that rely solely on vehicle location, this method can improve the accuracy of time zone calibration when traveling across regions. Furthermore, it does not require access to cloud computing resources and can still output accurate calibration results stably in offline scenarios such as underground parking garages and remote areas without signal. This solves the technical problems of offline failure and delayed response in traditional cloud-based clock calibration solutions.
[0013] In an exemplary embodiment, determining the predicted time zone offset based on the photovoltaic panel voltage data includes: determining the median sunrise time and median daytime duration within a preset duration based on the voltage time series curve corresponding to a preset duration in the photovoltaic panel voltage data; determining the predicted longitude based on the median sunrise time and the predicted latitude based on the median daytime duration; determining the data validity of the predicted longitude and the predicted latitude based on the matching result between the predicted longitude, the predicted latitude and the vehicle-mounted land and ocean grid database; and determining the predicted time zone offset based on the ratio of the predicted longitude to a preset time zone coefficient if the data validity of the predicted longitude and the predicted latitude is valid.
[0014] It can predict the time zone shift of a vehicle's location solely based on voltage data collected by the vehicle's solar panels, independent of satellite and cellular network positioning signals. Even in extreme scenarios without external positioning signal coverage, it can still stably output valid time zone shift results, solving the problems of traditional positioning relying on external signals and being unable to synchronize local time after signal failure. At the same time, relying on the validity verification of longitude and latitude, it can filter out abnormal longitude and latitude results that do not match the land and sea attributes, improving the accuracy of predicted time zone shift and meeting the accuracy requirements of core functions such as vehicle instrument time synchronization and vehicle navigation route time planning. Moreover, the entire prediction process only requires calculation of the regular voltage data collected by the solar panels, without the need for additional vehicle hardware configuration, and will not occupy additional vehicle computing resources. It can be adapted to most civilian vehicles equipped with solar power systems, with low technology implementation costs and strong compatibility.
[0015] In an exemplary embodiment, after determining the data validity of the predicted longitude and the predicted latitude based on the matching result between the predicted longitude, the predicted latitude and the vehicle-mounted land and ocean grid database, the method further includes: if the data validity of the predicted longitude and the predicted latitude is invalid, and / or the median value of the daytime duration is less than the daytime duration threshold, extending the preset duration by a preset time step, and re-executing the step of determining the median value of sunrise time and the median value of daytime duration within the preset duration based on the voltage time series curve corresponding to the preset duration in the photovoltaic panel voltage data; if the number of times the preset duration is extended reaches a preset number, and the data validity of the re-obtained predicted longitude and predicted latitude is invalid, and / or the median value of the daytime duration is less than the daytime duration threshold, using the third time zone calibration information obtained from the local rule base based on the vehicle location parameters as the target calibration rule.
[0016] By recalculating latitude and longitude through a step-by-step extension of the preset time, the processing logic can fully explore the geographic time-domain characteristics contained in the photovoltaic panel voltage time-series curve. Combined with the validity verification mechanism of the vehicle-mounted land and ocean grid database, it can filter out prediction errors caused by noise interference and meet the operational requirements of basic functions such as central control clock and trip recording in scenarios where the vehicle has no positioning signal.
[0017] In an exemplary embodiment, after performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: periodically calculating the calibration time difference between the vehicle hardware time and the local reference time determined based on the target calibration rule according to a first preset cycle, and detecting the parameter matching result between the currently effective time zone parameter and the target time zone parameter in the target calibration rule; if the calibration time difference is greater than the preset time difference, adjusting the timing rate of the vehicle hardware time according to historical offset records; if the number of times the parameter matching result indicates a matching failure reaches a threshold, triggering a recalibration task and uploading the abnormal calibration log to the cloud server.
[0018] It can effectively offset the timing rate deviation caused by temperature drift and aging of vehicle hardware crystal oscillators. At the same time, it can promptly detect occasional failures of time zone parameters due to storage abnormalities and signal interference. Relying on the cloud-based abnormal log aggregation and analysis capabilities, it can also provide data support for the reliability optimization of timing modules for batch vehicles.
[0019] In an exemplary embodiment, after performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: when the vehicle is in a powered-off state and the vehicle information meets the data download conditions, downloading an incremental update package of the update rules from the cloud rule base from the cloud server; if the incremental update package successfully passes the hash verification, saving the incremental update package to a secure storage area; and when the vehicle is detected to be powered on, loading and merging the incremental update package in the secure storage area into the local rule base.
[0020] This incremental update mechanism compresses the download size of the complete rule base, significantly reducing the traffic consumption and download time of the vehicle communication module. The background pre-download during the standby phase and merging upon power-on processing logic avoids the computational power occupation during the vehicle's power-on operation phase, ensuring that the vehicle controller's computing power is always prioritized for core tasks such as driving control and safety monitoring. It also avoids the risk of the original local rule base being corrupted or invalidated due to update package verification failure or download interruption during the update process. At the same time, the hash verification process can accurately identify data packet corruption or tampering caused by network fluctuations and transmission interference during the download process, ensuring the consistency between the local rule base and the cloud rule base after the update. This ensures that various vehicle rules, such as vehicle time zone calibration rules and communication rules, are always up-to-date, preventing issues such as excessive time zone synchronization errors and abnormal cross-regional driving functions caused by rule version lag. The impact of rule updates on the normal use of the vehicle is reduced to an almost imperceptible level.
[0021] In an exemplary embodiment, after performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: periodically uploading the rule base hash value and version information of the local rule base to a cloud server according to a second preset cycle, wherein the cloud server performs a repair judgment on the local rule base based on the rule base hash value and version information; upon receiving a repair instruction from the cloud server, downloading the repair data package corresponding to the repair instruction from the cloud server; and performing repair processing on the local rule base according to the repair data package.
[0022] By matching and verifying hash values with version information, it is possible to identify problems such as missing, corrupted, or misaligned rules in the local rule base caused by storage anomalies or incomplete incremental updates. Compared to redistributing the entire rule base, this reduces the amount of data that needs to be transmitted, significantly shortens the repair processing time, and avoids unnecessary waste of vehicle network traffic. In conjunction with the cloud-based proactive identification and triggering mechanism, it can automatically complete the self-healing of the local rule base without interfering with the normal operation of the vehicle. This ensures that the rule base on which the vehicle's time zone synchronization calibration depends remains intact and usable, effectively improving the robustness and long-term operational stability of the vehicle's time zone synchronization system and reducing after-sales maintenance costs for problems such as time zone synchronization deviations and functional failures caused by rule base failures.
[0023] Secondly, embodiments of this application provide a vehicle, including a body and a vehicle controller, the vehicle controller being used to implement the vehicle time zone calibration method as described in any of the preceding claims.
[0024] Thirdly, embodiments of this application provide a vehicle time zone calibration system, which includes a cloud server and at least one vehicle as described above.
[0025] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the vehicle time zone calibration method as described in any of the preceding claims.
[0026] Fifthly, embodiments of this application provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the vehicle time zone calibration method described in any of the preceding claims. Attached Figure Description
[0027] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application will be described below.
[0028] Figure 1 This is a schematic diagram of the vehicle time zone calibration system disclosed in an embodiment of this application; Figure 2 This is a flowchart illustrating the vehicle time zone calibration method disclosed in an embodiment of this application; Figure 3 This is a schematic diagram of the overall process of the vehicle time zone calibration method disclosed in the embodiments of this application; Figure 4 This is a schematic diagram illustrating the data acquisition frequency adjustment process disclosed in an embodiment of this application; Figure 5 This is a schematic diagram of the closed-loop verification process disclosed in the embodiments of this application; Figure 6 This is a schematic diagram of the process for remote repair of local anomalies disclosed in an embodiment of this application; Explanation of reference numerals in the attached figures: 1-Vehicle; 2-Cloud server. Detailed Implementation
[0029] The terms "first," "second," etc., are used for descriptive purposes only and have no sequential or technical meaning, nor should they be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Directional terms used in this application, such as "upper," "lower," "front," "rear," "left," "right," "inner," and "outer," are merely for reference to the orientation shown in the accompanying drawings. The use of directional terms is for better and clearer explanation and understanding of this application, and does not indicate the orientation of the system or component in a practical application scenario.
[0030] In the embodiments of this application, "or" is merely a way of describing the relationship between related objects, indicating that three relationships can exist. For example, A or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0031] The embodiments of this application are described below with reference to the accompanying drawings.
[0032] Please see Figure 1 , Figure 1 This is a schematic diagram of the vehicle time zone calibration system disclosed in this application. The vehicle time zone calibration system includes a cloud server 2 and at least one vehicle 1. Each vehicle 1 establishes a communication connection with the cloud server 2 through a network. The cloud server 2 stores a cloud rule base, which includes time zone calibration information corresponding to multiple countries around the world. Each vehicle 1 stores a local rule base, which is a lightweight hash table pre-installed with the vehicle at the factory, with a capacity controlled within 5MB. The time zone calibration information in the local rule base is constructed with the ISO 3166-1 three-digit country code as the hash key to build the main index. The time zone calibration information includes a time zone identifier (corresponding to the time zone of the country code in the index), the UTC standard time zone offset (accurate to the minute), the daylight saving time activation flag, the daylight saving time switching rules (start month / week / day of the week / time of day, end month / week / day of the week / time of day), the range of years in which the rules take effect, the latitude and longitude constraints of the regional time zone boundary, the Northern and Southern Hemisphere identifier fields (used to distinguish the different logic of the opposite activation months of daylight saving time in the Northern and Southern Hemispheres), and the half-time zone identifier field.
[0033] Please see Figure 2 , Figure 2 This is a flowchart illustrating the vehicle time zone calibration method disclosed in this application. This embodiment uses the vehicle controller as an example to illustrate the method. It is understood that in other embodiments, the method can also be executed by other in-vehicle terminals with data processing capabilities, and this application does not impose specific limitations on this.
[0034] The vehicle time zone calibration method includes: When vehicle 1 is powered on, the time zone calibration condition is determined based on the collected vehicle information. The time zone calibration condition includes a positioning network condition, a positioning network-free condition, and a positioning offline condition. Based on the time zone calibration conditions, obtain the time zone calibration information corresponding to the vehicle information from the local rule base or the cloud rule base, and determine the target calibration rule based on the time zone calibration information; Perform vehicle time zone synchronization calibration according to the target calibration rules.
[0035] The vehicle information includes, but is not limited to: satellite positioning data from the satellite positioning module of vehicle 1, vehicle-to-cloud communication link status data, vehicle location parameters, photovoltaic panel mounting flag, and photovoltaic panel voltage data. The satellite positioning data includes GNSS (Global Navigation Satellite System) signal strength, latitude and longitude coordinates, and valid positioning flags. The vehicle-to-cloud communication link status data includes the communication connection status with cloud server 2 and network connectivity records within a preset time period. The vehicle location parameters reflect the location information of the country or region where vehicle 1 is sold. The photovoltaic panel mounting flag indicates whether vehicle 1 is equipped with a photovoltaic panel. Photovoltaic panel voltage data will only exist in the vehicle information if vehicle 1 is equipped with a photovoltaic panel. The photovoltaic panel voltage data includes a photovoltaic panel voltage time series curve formed by continuously collected photovoltaic panel output voltages.
[0036] It is understandable that during the power-on process of vehicle 1, the vehicle controller can identify the vehicle hardware status according to the vehicle type configuration parameters, and execute the preset fault-tolerant processing logic in the event of abnormal hardware status, such as skipping satellite positioning data collection when the satellite positioning module is detected to be missing, and only collecting vehicle-to-cloud communication link status data and vehicle location parameters; the specific implementation of the above fault-tolerant processing logic can be customized according to actual application requirements, and this application does not impose specific restrictions on it.
[0037] After collecting the vehicle information, the vehicle controller performs a fusion judgment on the vehicle information according to the preset operating condition classification rules to determine the current time zone calibration operating condition of vehicle 1.
[0038] The time zone calibration conditions are categorized based on whether vehicle 1 currently possesses valid satellite positioning data and whether a communication link has been established with cloud server 2, including: With location-based networking: The vehicle information includes valid satellite positioning data, and the vehicle-to-cloud communication link status indicates that the current communication link with the cloud server 2 is in a connected state; No location-based network connection: The vehicle information does not contain valid satellite positioning data, but the vehicle-to-cloud communication link status indicates that the current communication link with the cloud server 2 is in a connected state; Offline operation without positioning: The vehicle information does not contain valid satellite positioning data, and the vehicle-to-cloud communication link status indicates that the current communication link with the cloud server 2 is disconnected.
[0039] The aforementioned operating condition classification rules provide a unified basis for subsequent rule base retrieval and target calibration rule matching, enabling the vehicle controller to select the most suitable calibration data source and matching strategy based on operating condition differences. This avoids calibration failures caused by improper data source selection under abnormal operating conditions. Furthermore, the data collection frequency for subsequent vehicle information can be determined based on time zone calibration conditions, referring to… Figure 4 Under normal operating conditions (i.e., with GPS signal and network connectivity), a low-frequency acquisition strategy (e.g., acquiring data every 300 seconds) is used to collect multi-source vehicle data, reducing onboard computing power consumption and bus load. When GPS hardware is missing, network is disconnected, or time zone offset is detected (i.e., without network connectivity or without location services), a high-frequency acquisition strategy is automatically switched (e.g., acquiring data every 60 seconds) to ensure data integrity and validity in abnormal scenarios. (Refer to...) Figure 3 and Figure 4 All collected multi-source vehicle data is stored locally on the vehicle controller and simultaneously uploaded to the cloud for archiving when there is a network connection. The multi-source vehicle data is deduplicated, corrected, and invalid data is removed. The data format and statistical standards of various parameters are unified. Key and effective information such as vehicle hardware configuration features, network status, time zone offset anomaly status, and location matching status are extracted to form vehicle information, which is used for subsequent scene recognition and calibration strategy matching.
[0040] After determining the time zone calibration condition, the vehicle controller obtains the time zone calibration information corresponding to the vehicle information from the local rule base or the cloud rule base, and determines the target calibration rule based on the time zone calibration information obtained from the local rule base and / or the cloud rule base.
[0041] The cloud-based rule base exists as a complete time zone rule database pre-installed on the cloud server, storing time zone calibration information for multiple countries and regions worldwide. It is continuously maintained and updated in the background to keep pace with changes in global time zone policies and daylight saving time activation / cancellation rules. The time zone calibration information in the cloud-based rule base includes, but is not limited to: time zone identifiers, UTC standard time zone offsets, and daylight saving time switching rules.
[0042] It should be noted that the local rule base and the cloud rule base adopt a dual-base collaborative architecture with static fallback and dynamic updates: the local rule base is used to provide basic time zone calibration capabilities when vehicle 1 is in an abnormal offline condition without network, ensuring that the vehicle can obtain time zone calibration information corresponding to the vehicle's location at any time; the cloud rule base is used to provide the latest time zone calibration capabilities, including dynamic information such as daylight saving time switching and national time zone changes, when vehicle 1 is in a network condition; through the collaboration of the two bases, the timeliness of time zone calibration rules can be taken into account while ensuring the offline availability of vehicle 1, avoiding calibration failure caused by the limitations of a single rule source.
[0043] In one embodiment, based on the time zone calibration conditions, time zone calibration information corresponding to the vehicle information is obtained from a local rule base or a cloud rule base, and a target calibration rule is determined based on the time zone calibration information, including: When the time zone calibration condition is a location network condition, the first time zone calibration information corresponding to the vehicle information is obtained from the cloud rule base according to the vehicle location parameter in the vehicle information, and the target calibration rule is determined according to the matching result between the location parsing result and the first time zone calibration information. When the time zone calibration condition is a non-location network condition, the first time zone calibration information obtained from the cloud rule base based on the vehicle location parameters in the vehicle information will be used as the target calibration rule. When the time zone calibration condition is a non-location offline condition, the target calibration rule is determined based on the second time zone calibration information obtained from the local rule base based on the vehicle location parameters and photovoltaic panel voltage data in the vehicle information, wherein the time zone calibration information is either the first time zone calibration information or the second time zone calibration information.
[0044] Specifically, when the time zone calibration condition is a location-connected condition, the vehicle controller initiates a time zone calibration information query request carrying the vehicle's location parameters to the cloud server 2. After receiving the query request, the cloud server 2 retrieves the corresponding cloud time zone calibration information (i.e., the first time zone calibration information) from the cloud rule base according to the vehicle's location parameters and sends it to the vehicle 1. The vehicle 1 parses the satellite positioning data to obtain the positioning parsing result, which includes at least the positioning time zone identifier and time offset. Then, the positioning parsing result is matched and verified with the first time zone calibration information from the cloud rule base to determine the final target calibration rule.
[0045] In situations without a location-based network connection, the vehicle lacks effective satellite positioning data, making it impossible to obtain the time zone identifier and time offset required for time zone calibration through location parsing. In this case, the vehicle controller relies on the full coverage capability of the cloud-based rule base. It only needs to query the corresponding cloud-based time zone calibration information (i.e., the first time zone calibration information) from the cloud-based rule base based on the vehicle's location parameters, and directly uses the query result as the target calibration rule. There is no need to perform a matching judgment between the location parsing result and the cloud-based time zone calibration information. This processing logic retains the dynamic update capability of the cloud-based rule base while avoiding matching anomalies caused by missing location data, thus improving the success rate of time zone calibration in situations without a location-based network connection.
[0046] When the time zone calibration is performed in an offline, location-free condition, since vehicle 1 has neither valid satellite positioning data nor a communication link with cloud server 2, the vehicle controller determines the target calibration rule based on the second time zone calibration information obtained from the local rule base according to the vehicle location parameters and photovoltaic panel voltage data in the vehicle information. This enables calibration to be completed in extreme scenarios where vehicle 1 is completely offline and has no positioning signal, improving the calibration success rate in offline scenarios. At the same time, local rule calls do not rely on network transmission, shortening the calibration time in this condition and effectively ensuring the availability of the central control time system when vehicle 1 is offline.
[0047] In one embodiment, determining the target calibration rule based on the matching result between the positioning resolution result and the first time zone calibration information includes: If the positioning analysis result matches the first time zone calibration information successfully, the positioning analysis result is used as the target calibration rule. A successful match indicates that the time zone identifier in the positioning analysis result is the same as the time zone identifier in the first time zone calibration information, and the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is less than a preset time difference. If the positioning analysis result fails to match the first time zone calibration information, the first time zone calibration information is used as the target calibration rule. The failure to match indicates that the time zone identifier in the positioning analysis result is different from the time zone identifier in the first time zone calibration information, and / or the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is greater than or equal to a preset time difference.
[0048] Specifically, if the positioning analysis result matches the first time zone calibration information from the cloud rule base, that is, the time zone identifier in the positioning analysis result is the same as the time zone identifier in the first time zone calibration information, and the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is less than a preset time difference, then the positioning analysis result is used as the target calibration rule.
[0049] If the positioning analysis result fails to match the first time zone calibration information, that is, the time zone identifier in the positioning analysis result is different from the time zone identifier in the first time zone calibration information, and / or the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is greater than or equal to the preset time difference, then the first time zone calibration information will be used as the target calibration rule.
[0050] This matching and judgment mechanism performs dual verification from two core dimensions: time zone identifier and time offset. It can filter out time zone information deviations caused by satellite signal drift and base station positioning errors during the positioning and parsing process. It ensures that high-precision positioning results are given priority when the positioning data is reliable, and cloud-based rule data is used when the positioning data is interfered with, thereby improving the robustness of target calibration rules under positioning network conditions.
[0051] In one embodiment, a target calibration rule is determined based on second time zone calibration information obtained from the local rule base based on vehicle location parameters and photovoltaic panel voltage data in the vehicle information, including: If the photovoltaic panel voltage data is not found in the vehicle information, the third time zone calibration information obtained from the local rule base based on the vehicle location parameters will be used as the target calibration rule. If the photovoltaic panel voltage data exists in the vehicle information, the predicted time zone offset is determined based on the photovoltaic panel voltage data, and the fourth time zone calibration information obtained from the local rule base based on the vehicle location parameters and the predicted time zone offset is used as the target calibration rule, wherein the second time zone calibration information is the third time zone calibration information or the fourth time zone calibration information.
[0052] Specifically, the vehicle controller performs shunt processing based on whether photovoltaic panel voltage data is present in the vehicle information: If the photovoltaic panel voltage data is not found in the vehicle information (i.e., the photovoltaic panel mounting flag indicates that no photovoltaic panel is mounted), the vehicle controller will use the third time zone calibration information obtained from the local rule base based on the vehicle location parameter (i.e., the sales country code of vehicle 1) as the target calibration rule. Specifically, the vehicle location parameter is used as the hash key, and the storage slot in the local rule base is directly located through a preset hash function to obtain the time zone calibration information corresponding to the vehicle location parameter. This retrieval process is an O(1) constant level hit retrieval, with no traversal loop operation throughout. It can complete a single time zone rule lock within a time threshold (e.g., 50ms) under low computing power conditions of automotive-grade microcontroller units (MCUs), ensuring the efficiency and delay determinism of time zone calibration under offline conditions without positioning. Since the local rule base is pre-installed in the form of a lightweight hash table with the vehicle, its retrieval efficiency is independent of the size of the local rule base and depends only on the mapping speed of the hash function. Therefore, even if the local rule base is expanded to a larger capacity in the future, the retrieval latency can still be stably controlled within the time threshold, meeting the real-time constraints of automotive-grade embedded systems.
[0053] If photovoltaic panel voltage data exists in the vehicle information, the vehicle controller determines the predicted time zone offset based on the photovoltaic panel voltage data and uses the fourth time zone calibration information obtained from the local rule base based on the vehicle location parameters and the predicted time zone offset as the target calibration rule. By using the photovoltaic panel voltage data of the onboard photovoltaic panel to infer the predicted time zone offset, autonomous time zone locking can be achieved in offline conditions without relying on external positioning methods and without increasing the cost of onboard hardware. This provides a third independent method for vehicle time zone synchronization calibration, alongside GPS positioning and network positioning. The joint retrieval of the predicted time zone offset and vehicle location parameters can further narrow down the candidate rule range and improve the accuracy of retrieving the target calibration rule from the local rule base.
[0054] In one embodiment, determining the predicted time zone offset based on the photovoltaic panel voltage data includes: Based on the voltage time-series curve corresponding to the preset duration in the photovoltaic panel voltage data, determine the median value of sunrise time and the median value of daytime duration within the preset duration; The predicted longitude is determined based on the median value of the sunrise time, and the predicted latitude is determined based on the median value of the daytime duration. The validity of the predicted longitude and the predicted latitude is determined based on the matching results between the predicted longitude, the predicted latitude and the vehicle-mounted land and ocean grid database. If the data for the predicted longitude and the predicted latitude are valid, the predicted time zone offset is determined based on the ratio of the predicted longitude to the preset time zone coefficient.
[0055] Specifically, based on the voltage time series curve corresponding to a preset duration (e.g., the last 7 days) in the photovoltaic panel voltage data, a moving average filter is applied to the voltage time series curve corresponding to the preset duration (the moving window width is 5), and then normalized to the [0,1] interval. The filtered voltage is compared with the voltage threshold TH (e.g., 0.1), and the moment when the voltage rises from below TH to above TH is recorded as the sunrise time. The moment when the voltage drops from above TH to below TH is recorded as the sunset time. Daily daytime length ΔT = - A total of 7 sets of sunrise forecast data were obtained over 7 days. ,ΔT).
[0056] The median sunrise time within the preset time period is determined based on the daily sunrise forecast data for each day within the preset time period. and median daytime length Among them, the median sunrise time is used to eliminate noise in the daily data and reflect the statistical characteristics of sunrise time within the preset duration; the median daytime duration is used to reflect the statistical characteristics of daytime duration within the preset duration.
[0057] Determining the predicted longitude based on the median sunrise time includes: using the Standard Solar Position Algorithm (SPA), with the current date and 0° longitude as input, to calculate the theoretical sunrise time of the Prime Meridian. The formula for predicting longitude is Lon= ×15°, During this calculation process, RTC (Real) The fixed deviation of the real-time clock (Time Clock) is canceled out in the differential operation.
[0058] The predicted latitude is determined based on the median daylight duration, and the formula for calculating sunshine duration is as follows: The median daytime length was used as... , The solar declination angle, i.e., the latitude of the subsolar point, is used to deduce the predicted latitude based on the above formula. .
[0059] Based on the matching results between the predicted longitude, the predicted latitude, and the vehicle-mounted land and ocean grid database, the validity of the predicted longitude and the predicted latitude is determined. Specifically, if the predicted longitude and latitude fall within the land area corresponding to the vehicle-mounted land and ocean grid database, and the difference between the predicted longitude / latitude and the longitude / latitude range corresponding to the vehicle's location parameters is less than a preset difference, then the validity of the predicted longitude and the predicted latitude is determined to be valid. If the predicted longitude and latitude fall within the ocean area, and / or the difference between the predicted longitude / latitude and the longitude / latitude range corresponding to the vehicle's location parameters is greater than or equal to a preset difference, then the validity of the predicted longitude and the predicted latitude is determined to be invalid.
[0060] If the data for the predicted longitude and the predicted latitude are valid, the predicted time zone offset is determined by rounding up the ratio of the predicted longitude Lon to the preset time zone coefficient (e.g., 15), i.e., the predicted time zone offset is offset=round(Lon / 15).
[0061] It should be noted that the photovoltaic panel voltage data comes from the solar photovoltaic panel installed on vehicle 1 and its supporting voltage detection circuit; the daily variation curve of the output voltage of the photovoltaic panel of vehicle 1 naturally carries sunrise / sunset / noon time information; combined with the sales country code (i.e. vehicle location parameter) fixed at the factory of vehicle 1, the ambiguity of the Northern and Southern Hemispheres can be eliminated (the months of daylight saving time activation are opposite in the Northern and Southern Hemispheres, and the relationship between day length and latitude is opposite in the Northern and Southern Hemispheres), so that the predicted longitude of the current time zone of vehicle 1 can be deduced without relying on GPS, network, manual input by the user, or additional sensors. Then, based on the predicted longitude, the predicted time zone offset of the current time zone of vehicle 1 can be calculated. The predicted time zone offset and the factory country code are used to construct a hash key, and an O(1) hash search is performed in the local static rule base. The corresponding time zone offset and daylight saving time rule are used as the final target calibration rule.
[0062] In one embodiment, after determining the data validity of the predicted longitude and the predicted latitude based on the matching result between the predicted longitude, the predicted latitude and the vehicle-mounted land-ocean grid database, the method further includes: If the data validity of the predicted longitude and the predicted latitude is invalid, and / or the median value of the daytime duration is less than the daytime duration threshold, the preset duration is extended according to a preset time step (e.g., 7 days), and the step of determining the median value of sunrise time and the median value of daytime duration within the preset duration based on the voltage time series curve corresponding to the preset duration in the photovoltaic panel voltage data is re-executed. If the preset duration is extended a preset number of times (e.g., 3 times), and the validity of the re-obtained predicted longitude and predicted latitude data is invalid, and / or the median value of the daytime duration is less than the daytime duration threshold, the third time zone calibration information obtained from the local rule base based on the vehicle location parameters will be used as the target calibration rule.
[0063] Specifically, if the photovoltaic panel voltage data for 7 consecutive days cannot be used to estimate effective longitude and latitude, and / or the median daytime duration is always less than the daytime duration threshold (e.g., 12 hours), the observation period will be extended to 14 days. If effective longitude and latitude cannot be estimated after 14 days, and / or the median daytime duration is still less than the daytime duration threshold, the solar energy solution will be abandoned, and the corresponding third time zone calibration information will be retrieved from the local rule base based solely on the vehicle's location parameters as the target calibration rule.
[0064] The processing logic of recalculating the predicted latitude and longitude by extending the preset time step by step can fully explore the geographic time-domain characteristics contained in the photovoltaic panel voltage time series curve when the initial photovoltaic panel voltage data sample is insufficient or the noise interference is large. Combined with the validity verification mechanism of the vehicle-mounted land and ocean grid database, it can filter the prediction errors caused by noise interference. Even if the predicted latitude and longitude still fall within the ocean area after multiple retries, the time zone calibration can be completed by downgrading to the local rule base data corresponding to the vehicle's location parameters, ensuring the robustness of the time zone calibration link under offline conditions without positioning.
[0065] For example, taking a vehicle exported to a certain country (country code 682, latitude 16-32°N) as an example, if the vehicle is operating in Riyadh (approximately 47°E) on June 21st (summer solstice), where there is no network or GPS, the voltage curve of the onboard photovoltaic panel shows a sunrise UTC time of approximately 03:07, with a daytime length of approximately 13.5 hours. The theoretical sunrise time on the Prime Meridian summer solstice is approximately 03:47, Lon≈-10°, which differs significantly from the actual longitude of the capital city of 47°. This indicates that the RTC bias is not completely offset or there is weather interference, and the observation period is automatically extended to 14 days. If convergence is still not achieved after 14 days, the system is downgraded to directly retrieve the time zone (UTC+3) using the factory-issued country code 682 to complete the calibration. If the weather is clear, after taking the median value of 7 days of observation, it can converge to Lon≈45°-50°, offset=+3. The composite hash hits a certain country (UTC+3, no daylight saving time), and the controller automatically updates the local rule base to UTC+3 parameters and synchronizes the time of the entire vehicle.
[0066] In one embodiment, after determining the target calibration rule, the vehicle controller performs vehicle time zone synchronization calibration according to the target calibration rule. Specifically, the vehicle time zone synchronization calibration process includes: the vehicle controller first converts the UTC (Coordinated Universal Time, also known as World Unified Time or Zulu Time) time corresponding to the vehicle hardware time into the base local time according to the UTC standard time zone offset (accurate to the minute) in the target calibration rule; then, it determines whether daylight saving time is enabled in the region according to the daylight saving time activation flag; if enabled, it determines whether the current time is within the daylight saving time effective period by combining the start month / week / day / time, end month / week / day / time, and rule effective year range in the daylight saving time switching rule; and adds the offset corresponding to the daylight saving time switching rule to the base local time. At the same time, it distinguishes the opposite logic of the month of daylight saving time activation in the northern and southern hemispheres according to the northern and southern hemisphere identification fields, retains the minute-level offset corresponding to the half time zone or non-hour time zone according to the half time zone identification field, and determines the local time according to the regional time. The latitude and longitude constraints of the area boundary are used to perform boundary verification on the positioning analysis results or predicted latitude and longitude to confirm the time zone parameters corresponding to the current location of vehicle 1, and finally obtain the local reference time. The local reference time is then sent to the central control screen, instrument panel and various electronic control units (ECUs), such as multimedia ECU, body control ECU, powertrain ECU, remote information processing terminal TBOX, etc., and the synchronization result flag bit returned by each ECU is received. If all ECUs are successfully synchronized, the vehicle time zone synchronization calibration process is considered complete. If there is an abnormal situation where ECU synchronization fails, the identifier of the abnormal ECU and the reason for the failure are recorded, and a recalibration task is triggered.
[0067] Based on the different vehicle communication conditions mentioned above, the first time zone calibration information or the second time zone calibration information (i.e., the third time zone calibration information or the fourth time zone calibration information) is selected as the target calibration rule. The first time zone calibration information, the third time zone calibration information, and the fourth time zone calibration information also include parameters such as time zone identifier, UTC standard time zone offset (accurate to the minute), daylight saving time activation flag, daylight saving time switching rules (start month / week / day of the week / time of day, end month / week / day of the week / time of day), rule effective year range, regional time zone boundary latitude and longitude constraints, Northern and Southern Hemisphere identifier fields (used to distinguish the different logic of opposite months of daylight saving time activation in the Northern and Southern Hemispheres), and half time zone identifier fields. However, due to the different sources and acquisition methods of the first time zone calibration information and the third and fourth time zone calibration information, the parameter values of the same parameter in the first time zone calibration information, the third time zone calibration information, and the fourth time zone calibration information may be different. Therefore, performing vehicle time zone synchronization calibration according to the corresponding target calibration rules under different vehicle communication conditions means performing vehicle time zone synchronization calibration using the first time zone calibration information, the third time zone calibration information, or the fourth time zone calibration information, following the above-mentioned vehicle time zone synchronization calibration process.
[0068] In one embodiment, after the vehicle time zone synchronization calibration process is completed, the vehicle controller periodically calculates the vehicle hardware time according to a first preset cycle, the calibration time difference between the vehicle hardware time and the local reference time determined based on the target calibration rule, and detects the parameter matching result between the currently effective time zone parameter and the target time zone parameter in the target calibration rule; If the calibration time difference is greater than the preset time difference, the timing rate of the vehicle hardware time is adjusted according to the historical offset record; If the number of times the parameter matching result fails to match reaches a threshold, a recalibration task is triggered, and the abnormal calibration log is uploaded to the cloud server 2.
[0069] Specifically, refer to Figure 5 The vehicle controller periodically performs hardware time self-calibration according to a first preset cycle (e.g., 10 seconds) to compensate for timing rate deviations caused by temperature drift and aging of the vehicle hardware crystal oscillator. The hardware time self-calibration operation includes: periodically calculating the calibration time difference between the vehicle hardware time (RTC time) and the local reference time determined based on the target calibration rule according to the first preset cycle; detecting the parameter matching result between the currently effective time zone parameter and the target time zone parameter in the target calibration rule; the time zone parameter includes the time zone identifier and time zone offset; if the calibration time difference is greater than a preset time difference (e.g., 5 seconds), calculating the crystal oscillator drift rate based on historical offset records, and gradually compensating the RTC timing rate through a PID control algorithm to smoothly converge the time to the standard value and avoid abrupt changes, for example, by fine-tuning the timing frequency compensation coefficient of the MCU's internal crystal oscillator to control the long-term timekeeping error of the vehicle within the hundreds of milliseconds; if the parameter matching result is a mismatch... If the number of failures reaches a threshold (e.g., 3 times), a recalibration task is triggered, and abnormal calibration logs are uploaded to cloud server 2. Cloud server 2 then uses aggregated analysis of the abnormal logs to identify potential problems in a batch of vehicles. If the parameter matching result is a failure, it means that the time zone identifier in the currently effective time zone parameter is inconsistent with the time zone identifier in the target time zone parameter, and / or, the difference between the time zone offset in the currently effective time zone parameter and the time zone offset in the target time zone parameter is greater than a preset difference. Conversely, if the parameter matching result is a success, it means that the time zone identifier in the currently effective time zone parameter is consistent with the time zone identifier in the target time zone parameter, and the difference between the time zone offset in the currently effective time zone parameter and the time zone offset in the target time zone parameter is less than or equal to a preset difference.
[0070] The hardware time self-calibration mechanism can effectively offset the timing rate deviation caused by temperature drift and aging of the vehicle hardware crystal oscillator, ensuring the long-term accuracy of the vehicle's timekeeping. At the same time, parameter matching detection can promptly detect occasional failures of time zone parameters due to storage anomalies and signal interference. Relying on the cloud-based abnormal log aggregation and analysis capabilities, it can provide data support for the reliability optimization of timing modules for batch vehicles.
[0071] In one embodiment, after performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: When vehicle 1 is turned off and the vehicle information meets the data download conditions, the incremental update package of the updated rules in the cloud rule base is downloaded from the cloud server 2. If the incremental update package successfully passes the hash verification, the incremental update package is saved to the secure storage area; When vehicle 1 is detected to be powered on, the incremental update package in the secure storage area is loaded and merged into the local rule base.
[0072] Specifically, refer to Figure 6 The cloud-based rule update service monitors the IANA Time Zone Database and time zone change announcements from various governments 24 / 7. When a policy change is detected and the official announcement clearly states the effective date, the service automatically creates a change task. After manual review and confirmation, the new parameters are written to the cloud dynamic database 30 days before the effective date, and an incremental update package (differential package, approximately 30KB) containing only the changed country and fields is generated and pushed to the vehicle terminal via the cloud.
[0073] When vehicle 1 is in a powered-off state (i.e., before entering sleep mode after power-off), if the vehicle information meets the data download conditions (e.g., the vehicle network communication module is connected to the network, the remaining battery power is greater than a preset level, and there are no diagnostic tasks), the vehicle controller downloads the incremental update package of the updated rules from the cloud rule base from the cloud server 2, thereby realizing a silent incremental update from the cloud rule base to the local rule base. The incremental update package is generated by the cloud server 2 after performing a difference analysis on the complete rule base, and only contains the changed content, which can significantly reduce the download size compared to the complete rule base.
[0074] The hash verification can specifically include performing RSA digital signature verification and SHA-256 hash value verification on the incremental update packet. The RSA digital signature verification is used to verify the credibility of the source of the incremental update packet, and the SHA-256 hash value verification is used to verify the integrity of the content of the incremental update packet. The dual verification can prevent the incremental update packet from being hijacked, tampered with or forged during transmission, and ensure the legality and integrity of the updated content.
[0075] When vehicle 1 is powered on again, the incremental update package in the secure storage area is loaded and merged into the local rule base, and the version number of the local rule base is updated. After the merge is completed, the update success event is reported to the cloud server 2. The loading and merging operation is executed by the vehicle controller's bootloader to ensure the atomicity of the update process and the vehicle 1 power-on initialization process, and to avoid the risk of write conflicts caused by directly updating the local rule base during driving.
[0076] The silent incremental update mechanism compresses the download size of the complete rule base, significantly reducing the traffic consumption and download time of the vehicle communication module. The background pre-download during the standby phase and merging upon power-on processing logic avoids the computational power occupation during the vehicle's power-on operation phase, ensuring that the vehicle controller's computational power is always prioritized for core tasks such as driving control and safety monitoring. It also avoids the risk of the original local rule base being corrupted or invalidated due to update package verification failure or download interruption during the update process. At the same time, the hash verification process can accurately identify data packet corruption or tampering caused by network fluctuations and transmission interference during the download process, ensuring the consistency between the local rule base and the cloud rule base after the update, and keeping the vehicle time zone calibration rules up-to-date.
[0077] In one embodiment, after performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: The local rule base hash value and version information are periodically uploaded to the cloud server 2 according to the second preset cycle, wherein the cloud server 2 performs repair judgment on the local rule base based on the rule base hash value and version information; Upon receiving a repair instruction from the cloud server 2, the repair data package corresponding to the repair instruction is downloaded from the cloud server 2; The local rule base is repaired based on the repair data package.
[0078] Specifically, refer to Figure 6The vehicle controller periodically uploads the rule base hash value and version information of the local rule base to the cloud server 2 according to a second preset cycle (e.g., 24 hours). After receiving the rule base hash value and version information reported by each vehicle, the cloud server 2 compares it with the baseline rule base on the cloud side, and performs a repair judgment on the local rule base based on the comparison result. If an anomaly is detected, a remote repair mechanism is triggered. Specifically, the cloud server 2 compares the rule base hash value reported by each vehicle with the hash value of the baseline rule base, and compares the version number in the version information reported by each vehicle with the version number of the cloud rule base. If the rule base hash value is inconsistent with the hash value of the baseline rule base (i.e., the local rule base has data corruption or loss), a first-level corruption flag is triggered. If the difference between the local rule base version number and the cloud rule base version number is greater than a preset version difference threshold (i.e., the local rule base version is seriously lagging), a second-level lag flag is triggered. If the abnormal calibration logs uploaded by vehicle 1 reach 3 or more times, a third-level abnormal flag is triggered. Based on any of the above criteria, cloud server 2 determines that the vehicle's local rule library is abnormal. If cloud server 2 determines that the vehicle's local rule library is abnormal, it extracts the complete time zone policy package (including overlay static library files and dependent rules) for that country from the latest baseline database based on the vehicle's VIN-bound location information, generates a dedicated repair instruction and repair data package, and sends it to the vehicle. Upon receiving the repair instruction from cloud server 2, the vehicle downloads the corresponding repair data package from cloud server 2, and repairs the local rule library according to the repair data package. Specifically, it uses a dual-partition backup mechanism to completely replace or repair the local static library and resets the rule state machine. After the repair is completed, a full-scenario calibration is forcibly triggered, and a successful repair log is reported. The entire process is fully automatic, requiring no user awareness or in-store visits, significantly reducing overseas after-sales costs. The repair process is executed the next time the vehicle is powered on, overlaying or merging the time zone calibration information from the repair data package into the local rule library, requiring no in-store visits or user intervention.
[0079] The cloud-based monitoring and remote repair mechanism identifies rule loss, corruption, or version misalignment issues in the local rule base due to storage anomalies or incomplete incremental updates by matching and verifying hash values and version information. Compared to redistributing the entire rule base, the differentiated repair mechanism reduces the amount of data that needs to be transmitted, significantly shortens the repair processing time, and avoids unnecessary waste of vehicle network traffic. In conjunction with the cloud-based proactive identification and triggering mechanism, it can automatically complete the self-healing of the local rule base without interfering with the normal operation of the vehicle, ensuring that the rule foundation upon which the vehicle's time zone synchronization calibration depends remains intact and usable at all times.
[0080] After each complete vehicle time zone synchronization calibration, the vehicle controller packages the complete evidence chain of this calibration into a structured data block (e.g., a JSON format data block) and uploads it to the cloud data lake via an encrypted MQTT channel for permanent backup, supporting post-audit and remote fault location. The structured data block includes, but is not limited to: the calibration strategy log, operating condition snapshots (including scenario classification results and hardware status information), the rule base version used (local rule base version and cloud rule base version), a vehicle ECU synchronization success flag, and a local rule base integrity hash value. Specifically, the strategy log records the execution time, execution duration, and target calibration rule used in this calibration; the operating condition snapshot records the vehicle hardware status and network communication status during this calibration; the vehicle ECU synchronization success flag indicates the time synchronization results of each ECU in the vehicle; and the local rule base integrity hash value is used to verify the data integrity of the local rule base in the cloud.
[0081] Cloud server 2 aggregates calibration logs, anomaly repair records, and deviation trends reported by self-diagnostics from vehicles operating globally on a monthly cycle. Through aggregated analysis, it generates a global timezone adaptation health report, identifying target regions with a sudden increase in calibration failure rate or a sustained rate exceeding 0.5%. A deep rule review is then initiated: importing official policy documents and crowdsourced calibration data for the region, and fine-tuning parameters and conducting simulation verification using a rule editor. Upon approval, the optimized rule package becomes the baseline version of the new generation dynamic rule library, and the static fallback library image is updated simultaneously. The new version is then pushed to all vehicles operating overseas via OTA in batches, updating the static library and resetting the dynamic rule cache.
[0082] The cloud backup mechanism for the logs can reliably, structurally, and encryptedly preserve the complete evidence chain of a calibration to the cloud permanently, avoiding the loss of calibration logs due to vehicle maintenance, change of ownership, or other scenarios. Through cloud aggregation and analysis, it can also identify potential regular problems in batches of vehicles, providing data support for the iterative optimization of the vehicle time zone calibration strategy.
[0083] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the vehicle time zone calibration method as described in any of the preceding claims.
[0084] Specifically, the computer-readable storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks. When the computer program stored on the computer-readable storage medium is loaded and executed by the processor, it can guide the vehicle controller to complete each step of the vehicle time zone calibration method described in any of the above embodiments, thereby achieving adaptive identification and differentiated calibration of the time zone calibration conditions for vehicles traveling at sea, and improving the accuracy and reliability of the vehicle's time zone synchronization calibration.
[0085] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the vehicle time zone calibration method as described in any of the preceding claims.
[0086] The computer program product may take the form of any combination of one or more readable media, including but not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. When the computer program / instructions in the computer program product are loaded and executed by the vehicle controller, they can automatically determine the time zone calibration conditions of the vehicle going to sea, automatically match the corresponding target calibration rules, and automatically execute the entire process of vehicle time zone synchronization calibration.
[0087] It should be understood that the application of this application is not limited to the examples above. Those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims. Those skilled in the art can understand that implementing all or part of the processes of the above embodiments and making equivalent changes according to the claims of this application still fall within the scope of this application.
Claims
1. A vehicle time zone calibration method, characterized in that, The vehicle time zone calibration method includes: When the vehicle is powered on, the time zone calibration condition is determined based on the collected vehicle information. The time zone calibration condition includes a positioning network condition, a positioning network-free condition, and a positioning offline condition. Based on the time zone calibration conditions, obtain the time zone calibration information corresponding to the vehicle information from the local rule base or the cloud rule base, and determine the target calibration rule based on the time zone calibration information; Perform vehicle time zone synchronization calibration according to the target calibration rules.
2. The vehicle time zone calibration method as described in claim 1, characterized in that, Based on the time zone calibration conditions, obtain the time zone calibration information corresponding to the vehicle information from the local rule base or cloud rule base, and determine the target calibration rule based on the time zone calibration information, including: When the time zone calibration condition is a location network condition, the first time zone calibration information corresponding to the vehicle information is obtained from the cloud rule base according to the vehicle location parameter in the vehicle information, and the target calibration rule is determined according to the matching result between the location parsing result and the first time zone calibration information. When the time zone calibration condition is a non-location network condition, the first time zone calibration information obtained from the cloud rule base based on the vehicle location parameters in the vehicle information will be used as the target calibration rule. When the time zone calibration condition is a non-location offline condition, the target calibration rule is determined based on the second time zone calibration information obtained from the local rule base based on the vehicle location parameters and photovoltaic panel voltage data in the vehicle information, wherein the time zone calibration information is either the first time zone calibration information or the second time zone calibration information.
3. The vehicle time zone calibration method as described in claim 2, characterized in that, Based on the matching results between the positioning analysis results and the calibration information of the first time zone, the target calibration rules are determined, including: If the positioning analysis result matches the first time zone calibration information successfully, the positioning analysis result is used as the target calibration rule. A successful match indicates that the time zone identifier in the positioning analysis result is the same as the time zone identifier in the first time zone calibration information, and the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is less than a preset time difference. If the positioning analysis result fails to match the first time zone calibration information, the first time zone calibration information is used as the target calibration rule. The failure to match indicates that the time zone identifier in the positioning analysis result is different from the time zone identifier in the first time zone calibration information, and / or the time difference between the time offset in the positioning analysis result and the time offset in the first time zone calibration information is greater than or equal to a preset time difference.
4. The vehicle time zone calibration method as described in claim 2, characterized in that, Based on the second time zone calibration information obtained from the local rule base using the vehicle location parameters and photovoltaic panel voltage data from the vehicle information, the target calibration rules are determined, including: If the photovoltaic panel voltage data is not found in the vehicle information, the third time zone calibration information obtained from the local rule base based on the vehicle location parameters will be used as the target calibration rule. If the photovoltaic panel voltage data exists in the vehicle information, the predicted time zone offset is determined based on the photovoltaic panel voltage data, and the fourth time zone calibration information obtained from the local rule base based on the vehicle location parameters and the predicted time zone offset is used as the target calibration rule, wherein the second time zone calibration information is the third time zone calibration information or the fourth time zone calibration information.
5. The vehicle time zone calibration method as described in claim 4, characterized in that, Determining the predicted time zone offset based on the photovoltaic panel voltage data includes: Based on the voltage time-series curve corresponding to the preset duration in the photovoltaic panel voltage data, determine the median value of sunrise time and the median value of daytime duration within the preset duration; The predicted longitude is determined based on the median value of the sunrise time, and the predicted latitude is determined based on the median value of the daytime duration. The validity of the predicted longitude and the predicted latitude is determined based on the matching results between the predicted longitude, the predicted latitude and the vehicle-mounted land and ocean grid database. If the data for the predicted longitude and the predicted latitude are valid, the predicted time zone offset is determined based on the ratio of the predicted longitude to the preset time zone coefficient.
6. The vehicle time zone calibration method as described in claim 5, characterized in that, After determining the data validity of the predicted longitude and predicted latitude based on the matching results between the predicted longitude, the predicted latitude and the vehicle-mounted land and ocean grid database, the method further includes: If the data validity of the predicted longitude and the predicted latitude is invalid, and / or the median value of the daytime duration is less than the daytime duration threshold, the preset duration is extended according to the preset time step, and the step of determining the median value of sunrise time and the median value of daytime duration within the preset duration based on the voltage time series curve corresponding to the preset duration in the photovoltaic panel voltage data is re-executed. If the preset duration extension number reaches the preset number, and the validity of the re-obtained predicted longitude and predicted latitude data is invalid, and / or the median value of the daytime duration is less than the daytime duration threshold, the third time zone calibration information obtained from the local rule base based on the vehicle location parameters will be used as the target calibration rule.
7. The vehicle time zone calibration method as described in claim 1, characterized in that, After performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: The vehicle hardware time is periodically calculated according to the first preset cycle, and the calibration time difference between it and the local reference time determined based on the target calibration rule is detected. The parameter matching result between the currently effective time zone parameter and the target time zone parameter in the target calibration rule is also detected. If the calibration time difference is greater than the preset time difference, the timing rate of the vehicle hardware time is adjusted according to the historical offset record; If the number of times the parameter matching result fails to match reaches a threshold, a recalibration task is triggered, and the abnormal calibration log is uploaded to the cloud server.
8. The vehicle time zone calibration method as described in claim 1, characterized in that, After performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: When the vehicle is turned off and the vehicle information meets the data download conditions, the incremental update package of the updated rules in the cloud rule base is downloaded from the cloud server. If the incremental update package successfully passes the hash verification, the incremental update package is saved to the secure storage area; When the vehicle is detected to be powered on, the incremental update package in the secure storage area is loaded and merged into the local rule base.
9. The vehicle time zone calibration method as described in claim 1, characterized in that, After performing vehicle time zone synchronization calibration according to the target calibration rule, the method further includes: The local rule base hash value and version information are periodically uploaded to the cloud server according to the second preset cycle, wherein the cloud server performs repair judgment on the local rule base based on the rule base hash value and version information; Upon receiving a repair instruction from the cloud server, download the repair data package corresponding to the repair instruction from the cloud server; The local rule base is repaired based on the repair data package.
10. A vehicle, characterized in that, It includes a vehicle body and a vehicle controller, the vehicle controller being used to implement the vehicle time zone calibration method as described in any one of claims 1-9.
11. A vehicle time zone calibration system, characterized in that, The vehicle time zone calibration system includes a cloud server and at least one vehicle as described in claim 10.
