Method and vehicle for synchronously displaying a time of day in a vehicle

Abstract

The embodiment of the application provides a kind of method and vehicle for synchronously displaying time in vehicle, wherein, vehicle includes information processing box, cockpit host and multiple display modules, the method includes: information processing box is powered on in response to vehicle, obtains the global system positioning time that positioning module collected in vehicle, and the network protocol time that network module collected in vehicle;Information processing box is based on global system positioning time and network protocol time, determines precision protocol time, and precision protocol time is transmitted to cockpit host;Cockpit host is according to precision protocol time, synchronously updates initial display time in multiple display modules, obtains target display time.The technical problem that multiple display modules are different in display time is solved.

Description

Technical Field

[0001] This application relates to the field of data processing, and more particularly to a method and a vehicle for synchronously displaying time in a vehicle. Background Technology

[0002] Currently, the cockpit head unit has multiple clock sources, such as the Generic Precision Time Protocol (gPTP) clock transmitted from outside the vehicle, the Real-Time Clock (RTC) of the cockpit head unit's Microcontroller Unit (MCU), and the Network Time Protocol (NTP) clock of the cockpit head unit. Typically, the cockpit head unit displays the time simultaneously on multiple display modules (such as the central control screen and the instrument panel) to generate an intuitive sense of time.

[0003] In related technologies, multiple display modules are driven by multiple processors (System on Chip, or SOC for short). Each processor has an independent clock source, which causes the time of each controller to be out of sync, resulting in a technical problem of asynchronous display time in multiple display modules. Summary of the Invention

[0004] This application provides a method and vehicle for synchronously displaying time in a vehicle, aiming to solve the technical problem of asynchronous time display in multiple display modules.

[0005] According to one embodiment of this application, a method for synchronously displaying time in a vehicle is provided. The vehicle includes an information processing box, a cockpit host, and multiple display modules. The method may include: the information processing box, in response to the vehicle being powered on, acquiring the global positioning time (GPS) collected by the vehicle's positioning module and the network protocol time (NAT) collected by the vehicle's network module; the information processing box, based on the GPS and NAT, determining a precise protocol time and transmitting the precise protocol time to the cockpit host; and the cockpit host, according to the precise protocol time, synchronously updating the initial display time in the multiple display modules to obtain the target display time.

[0006] The above-mentioned optional embodiments of this application can achieve the following beneficial effects: by utilizing high-precision global system positioning time and network protocol time, more accurate precision protocol time can be obtained, which improves the accuracy of time synchronization between modules inside the vehicle, thereby ensuring that the time information of display modules such as the central control screen and instrument screen is accurate and avoiding time display abnormalities caused by time asynchrony.

[0007] Optionally, the information processing box transmits the precise protocol time to the cockpit host, including: a first device deployed in the information processing box generates a time synchronization message in response to determining the precise protocol time, wherein the time synchronization message is used to transmit the precise protocol time to the cockpit host; the first device uses the vehicle's central control unit to send the time synchronization message to the cockpit control module in the cockpit host; the cockpit host synchronously updates the initial display time in multiple display modules according to the precise protocol time to obtain the target display time, including: the cockpit control module updates its kernel time according to the precise protocol time in the time synchronization message, and updates the initial display time of the central control screen in multiple display modules according to the updated kernel time to obtain the target display time.

[0008] The above-mentioned optional embodiments of this application can achieve the following beneficial effects: by deploying a first device in the information processing box (Tbox) and using the vehicle's central control unit as an intermediary, time synchronization messages are transmitted to the cockpit host to update the kernel time of the cockpit control module. Furthermore, according to the updated kernel time, the initial display time of the central control screen in the display module is adjusted, thereby achieving precise time synchronization and ensuring that the time displayed on the central control screen and the instrument panel is consistent and accurate. This optimizes the time display on the central control screen and the instrument panel, not only improving the accuracy of time synchronization and the robustness of the system, but also enhancing the consistency of user experience, and ultimately effectively solving the problem of time asynchrony.

[0009] Optionally, the cockpit main unit includes a microprocessor that controls the cockpit control module. The cockpit control module updates its kernel time according to the precision protocol time in the time synchronization message. This includes: the cockpit control module, in response to receiving the time synchronization message, generating a real-time clock request and transmitting the real-time clock request to the microprocessor, wherein the real-time clock request requests the microprocessor to calibrate the real-time clock time according to the precision protocol time; a board-level support package in the cockpit main unit initiates a time synchronization service and uses the time synchronization service to obtain the calibrated real-time clock time from the microprocessor; the board-level support package synchronizes the calibrated real-time clock time to the kernel of the cockpit control module to obtain the kernel time.

[0010] The optional embodiments described above in this application achieve the following beneficial effects: When a time synchronization message (e.g., a gPTP time synchronization message) is received, the cockpit control module responds immediately. The cockpit control module sends a real-time clock request to the microprocessor, requesting the microprocessor to calibrate its internal real-time clock according to a precise protocol time (e.g., the precise time of gPTP). A time synchronization service is initiated via a board-level support package to synchronize the calibrated real-time clock to the kernel of the cockpit control module, thereby updating the kernel time. By utilizing precise protocol time, the time synchronization accuracy and consistency between the cockpit host microprocessor and the cockpit control module are enhanced, accurate time calibration during system startup is achieved, the time recovery capability of the cockpit system in fault conditions is strengthened, and ultimately, the reliability and user experience of the entire cockpit system are improved.

[0011] Optionally, the method may further include: in response to receiving a real-time clock request, the microprocessor transmits the calibrated real-time clock time to the instrument control module in the cockpit main unit.

[0012] The above-described optional embodiments of this application can achieve the following beneficial effects: during vehicle operation, the cockpit host can monitor and automatically calibrate the real-time clock of the internal microprocessor in real time, and calibrate the real-time clock in response to a real-time clock request, thereby ensuring that the real-time clock can still be monitored and automatically calibrated in real time even without a network connection or GPS signal.

[0013] Optionally, the method may further include: the cockpit control module, in response to the completion of network time service preparation in the cockpit host, acquiring the standard network protocol time, and adjusting the kernel time and the real-time clock time of the microprocessor to the standard network protocol time; the microprocessor transmitting the adjusted real-time clock time to the instrument control module; and the instrument control module synchronizing the initial display time of the instrument panel in the display module to the set real-time clock time.

[0014] The above-described optional embodiments of this application achieve the following beneficial effects: By controlling the cockpit control module in the cockpit host to obtain standard network protocol time, the cockpit system can still obtain standard network protocol time (i.e., NTP time) via WiFi or a stable data network connection even when the vehicle cannot receive GPS signals or the fourth-generation mobile communication technology (4G) network is abnormal, serving as an alternative for time synchronization. The kernel time of the cockpit control module and the real-time clock time of the microprocessor are adjusted to the standard network protocol time. This adjustment process not only synchronizes the internal time of the cockpit host but also ensures that the real-time clock time of the MCU is consistent with the standard network protocol time, improving the accuracy of the time display. The microprocessor (MCU) is controlled to transmit the adjusted real-time clock time to the instrument control module. This step transmits the time synchronization signal from the cockpit host to the instrument panel, ensuring that the time displayed on the instrument panel is consistent with the time of the cockpit host. The instrument control module is controlled to synchronize the initial display time of the instrument screen in the display module to the set real-time clock time. Through this process, the time display on the instrument screen is accurately updated, achieving time synchronization with the central control screen and other cockpit display modules.

[0015] Optionally, the method may further include: the cockpit control module, in response to obtaining the standard network protocol time, determining whether the standard network protocol time and the target display time displayed on the central control screen are synchronized; the cockpit control module, in response to the asynchronous relationship between the standard network protocol time and the target display time displayed on the central control screen, updating the target display time to the standard network protocol time.

[0016] The optional embodiments described above achieve the following beneficial effects: By acquiring standard network protocol time through the cockpit control module and adjusting the target display time on the central control screen using this standard network protocol time, synchronization between the target display time on the central control screen and the Internet standard time is achieved. This allows for rapid identification and immediate correction even if time display deviations occur for a short period due to system errors or network latency, improving the time display accuracy of the central control screen and ensuring the accuracy of the obtained time information. Through this mechanism, the cockpit system can continuously provide accurate time information, enhancing user trust in the overall cockpit system and improving the stability and reliability of the cockpit electronic system. Even if the time synchronization link is occasionally interrupted, time accuracy can be quickly restored.

[0017] According to one embodiment of this application, a vehicle is also provided, including: an information processing box, configured to, in response to the vehicle being powered on, acquire a global system positioning time collected by a positioning module in the vehicle, and a network protocol time collected by a network module in the vehicle; determine a precise protocol time based on the global system positioning time and the network protocol time, and transmit the precise protocol time to a cockpit host; a cockpit host, configured to, according to the precise protocol time, synchronously update the initial display time in multiple display modules to obtain a target display time; and multiple display modules, including at least a central control screen and an instrument panel screen, for displaying the target display time.

[0018] Optionally, the cockpit main unit may include: a cockpit control module, used to receive the precision protocol time; update the kernel time according to the precision protocol time; update the initial display time of the central control screen according to the updated kernel time to obtain the target display time; a microprocessor, used to acquire the precision protocol time transmitted by the cockpit control module and synchronize the precision protocol time to the instrument control module; and an instrument control module, used to update the initial display time of the instrument screen to the target display time according to the precision protocol time in response to receiving the precision protocol time synchronization.

[0019] Optionally, the information processing box includes: a first device for generating a time synchronization message in response to determining a precise protocol timing; and sending the time synchronization message to the cockpit control module in the cockpit host using the vehicle's central control unit.

[0020] Optionally, the cockpit host includes: a board-level support package for starting a time synchronization service and using the time synchronization service to obtain a calibrated real-time clock from the microprocessor; and synchronizing the calibrated real-time clock to the kernel of the cockpit control module to obtain the kernel time.

[0021] According to another aspect of the embodiments of this application, an electronic device is provided, including a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute instructions to implement the method described above.

[0022] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to perform the above-described method when run by a processor.

[0023] According to another aspect of the embodiments of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the above-described method.

[0024] According to another aspect of the embodiments of this application, a vehicle is provided, including an on-board processor and an on-board memory, wherein the on-board memory is used to store a computer program; and the on-board processor is used to execute the computer program stored in the memory to implement the above method.

[0025] It should be noted that the general descriptions above and the detailed descriptions below are merely illustrative and explanatory for this application and do not constitute a limitation thereof. Attached Figure Description

[0026] Figure 1 This is a flowchart illustrating a method for synchronously displaying time in a vehicle according to an embodiment of this application;

[0027] Figure 2 This is a schematic diagram illustrating the principle of a dual-SOC cockpit main unit time synchronization scheme provided in one embodiment of this application;

[0028] Figure 3 This is a schematic diagram of a dual SOC cockpit main unit time synchronization system provided in one embodiment of this application;

[0029] Figure 4 This is a flowchart of the CarTimeSync time synchronization process of a cockpit host Android FW provided in one embodiment of this application;

[0030] Figure 5 This is a schematic diagram of a vehicle system architecture provided in one embodiment of this application;

[0031] Figure 6 This is a structural diagram of a device for synchronously displaying time in a vehicle according to an embodiment of this application;

[0032] Figure 7 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0033] To make the technical problems, technical solutions, and beneficial effects solved by this application clearer, the following detailed description is provided in conjunction with embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0034] Currently, cockpit head units have multiple clock sources, such as a gPTP clock transmitted from outside the vehicle, the RTC clock of the cockpit head unit's MCU, and the network NTP clock. Typically, the cockpit head unit displays the time simultaneously on both the central control screen and the instrument cluster screen to provide an intuitive sense of time. However, if the time displayed on the instrument cluster screen differs from the actual time, or if the time displayed on the central control screen differs from the time displayed on the instrument cluster screen, it can easily cause confusion and complaints.

[0035] In related technologies, the central control screen and instrument panel are each driven by two System-on-Chip (SOCs), each with its own independent clock source. Clock synchronization between the central control screen and instrument panel is achieved by synchronizing the time with the vehicle's Central Control Unit (CCU). If the CCU's time source malfunctions, the central control screen and instrument panel cannot achieve time synchronization. As mentioned above, due to the numerous controllers in the vehicle, each with its own independent clock source, time asynchrony occurs. The instrument panel and central control screen in the cockpit are each driven by two SOCs, with minimal interaction between them, leading to inconsistencies in the displayed time or deviations from the actual time. Therefore, there is a technical problem of time asynchrony across multiple display modules.

[0036] To address the aforementioned issues, this application provides a method for synchronizing the display time in a vehicle, specifically addressing the processing of multiple clock sources by the cockpit host. This method may include: in response to vehicle power-on, acquiring the vehicle's Global System for Positioning (GPS) time and Network Protocol (LPT) time, wherein the GPS time is collected by the vehicle's positioning module and the LPT time is collected by the vehicle's network module; controlling an information processing box to determine a precise LPT time based on the GPS time and LPT time; and controlling the cockpit host to update the initial display time in multiple display modules according to the precise LPT time to obtain a target display time. This achieves the goal of ensuring that the cockpit center console screen and instrument panel remain synchronized with other controllers in the vehicle, while simultaneously improving the time accuracy of the center console screen and instrument panel.

[0037] The method for synchronously displaying time in a vehicle provided in this application embodiment achieves the following technical effects: the information processing box, as the time source of the whole vehicle, determines the precise time protocol time based on the global system positioning time and network protocol time, and transmits the precise time protocol time to the cockpit host, so as to use the cockpit host to control the display modules in the vehicle to display the precise time protocol time, thereby achieving the purpose of controlling multiple display modules to display time synchronously, thus solving the technical problem of asynchronous display time in multiple display modules, and achieving the technical effect of controlling the display time of multiple display modules to display synchronously.

[0038] Example 1

[0039] This application provides a method for synchronously displaying time in a vehicle. The vehicle includes an information processing box, a cockpit host, and multiple display modules. The information processing box can be a Telematics Box (TBOX). The cockpit host, also known as a cockpit system, controls the simultaneous display of time on multiple display modules. The cockpit host can synchronize time to various components within the vehicle and send time synchronization signals to other controllers. The multiple display modules may include, but are not limited to, the vehicle's central control screen and instrument panel.

[0040] Please refer to Figure 1 , Figure 1 This is a flowchart of a method for synchronously displaying time in a vehicle according to an embodiment of this application, including the following steps:

[0041] S102: In response to the vehicle power-on, the information processing box acquires the global system positioning time collected by the vehicle's positioning module and the network protocol time collected by the vehicle's network module. The global system positioning time is collected by the vehicle's positioning module, and the network protocol time is collected by the vehicle's network module.

[0042] In step S102, the aforementioned global positioning time can be the time collected by the positioning module in the vehicle, or it can be the GPS time. The aforementioned positioning module can be a Global Positioning System (GPS) module. The aforementioned network protocol time can be the time collected by the network module in the vehicle, or it can be the Network Time Protocol (NTP) time. The aforementioned network module can be a 4G module or a Wi-Fi module.

[0043] Optionally, when the vehicle is powered on, a self-test and initialization process can begin. The vehicle's positioning module (e.g., GPS module) can collect the Global System for Mapping (GSMT) time, which provides a high-precision time reference and can be used to calibrate the time of multiple modules within the vehicle. Simultaneously, to improve time accuracy, the vehicle's network module (e.g., a 4G module or Wi-Fi module in the T-box) can collect the network protocol time, which can be NTP time, providing the vehicle with an internet-based time synchronization option.

[0044] S104: The information processing box determines the precision protocol time based on the global system positioning time and network protocol time, and transmits the precision protocol time to the cockpit main unit.

[0045] In step S104, the aforementioned information processing box can be a Telematics Box (TBOX), which can be used to process the Global System for Positioning (GPS) time and network protocol time to determine the precise protocol time. The precise protocol time can be the gPTP time.

[0046] Optionally, precise protocol time can be obtained by using TBOX to perform relative calibration between GPS time and NTP time.

[0047] For example, after obtaining GPS and NTP times, the TBOX internal software can be used to combine the GPS and NTP times for time fusion. When a GPS signal is available, the GPS time is preferred because it is more accurate. When there is no GPS signal, the NTP time can be used as an alternative time source. The gPTP master device in the TBOX can use the most accurate of these two time sources as a reference to correct the local time to ensure accuracy. Optionally, the time priority can be: GPS time > NTP time > RTC time.

[0048] Optionally, the control information processing box, based on a comprehensive comparison of Global System for Positioning (GPS) time and network protocol time, selects a more accurate time source to determine the precision protocol time, and can transmit the aforementioned precision protocol time to the aforementioned cockpit main unit. This precision protocol time can refer to the most suitable time after calibration and fusion, or it can be gPTP time, which can be used to provide microsecond-level precise synchronization.

[0049] S106: The cockpit main unit synchronously updates the initial display time in multiple display modules according to the precise protocol time to obtain the target display time.

[0050] In step S106, the initial display time can be the time when the display module first starts displaying. The target display time can be the time after the display module adjusts its display according to the precision protocol.

[0051] Optionally, the cockpit host can be controlled to send a precise protocol time to itself. The cockpit host can then synchronize this precise protocol time to the internal cockpit SOC and instrument SOC, thereby synchronously updating the initial display time on the central control screen and instrument panel displays. This ensures that the final target display time displayed on multiple display modules is consistent with the precise protocol time. Under the control of the cockpit host, the time of multiple display modules is updated, achieving precise positioning and synchronization of the entire vehicle's time. The precise synchronization of multiple time display modules throughout the vehicle avoids time discrepancies between different display modules, ensuring the accuracy and reliability of vehicle operation and driving information. This solves the problem of the cockpit system failing to accurately synchronize time when the internal vehicle network environment is unstable or certain time sources fail, especially in cases where the time display on the central control screen and instrument panel is inconsistent.

[0052] The following example uses a dual-display module. Figure 2 This is a schematic diagram illustrating the principle of a dual-SOC cockpit main engine time synchronization scheme according to an embodiment of this application, as shown below. Figure 1 As shown, the solution may include: cockpit host 201, remote information processing box 202, central controller 203, central control screen 204, and instrument panel 205, etc.

[0053] Optionally, the telematics box 202 serves as the vehicle's time source. After obtaining the GPS and NTP times, it can determine the precise protocol time based on these times. The determined precise protocol time is then transmitted to the central controller 203 as a clock signal via Ethernet. The central controller 203 forwards the determined precise protocol time to all nodes on the vehicle via Ethernet, thereby ensuring that the time of all controllers in the vehicle remains consistent. After the central controller 203 transmits the precise protocol time to the cockpit host 201, the cockpit host 201 can simultaneously display the determined precise protocol time on display modules (e.g., the central control screen 204 and the instrument panel 205).

[0054] Optionally, the cockpit host 201 may include two independent SOCs, namely cockpit SOC 2011 (i.e., Android SOC) and instrument SOC 2012 (i.e., QNX SOC). Cockpit SOC 2011 can be used to drive the central control screen 204, and instrument SOC 2012 can be used to drive the instrument screen 205.

[0055] Optionally, after the MCU 2014 in the cockpit main unit 201 receives the updated RTC time information from the cockpit SOC 2011, it can synchronize the time to the instrument SOC 2012. The instrument SOC 2012 can run a real-time operating system and is mainly used for instrument screen display.

[0056] Optionally, if the precise protocol time transmission from Tbox to CCU is interrupted or abnormal, the cockpit SOC 2011 of the cockpit host 201 can attempt to obtain time data through other means (such as Wi-Fi module 2013).

[0057] Optionally, even when the cockpit main unit 201 is turned off or powered off, the RTC crystal 2015 in the cockpit main unit 201 can continue to operate, providing a stable time signal.

[0058] Optionally, the cockpit main unit 201 can transmit data to the display module via Low-Voltage Differential Signaling (LVDS).

[0059] Alternatively, the cockpit SOC 2011, MCU 2014, and instrumentation SOC 2012 can transmit data via the Serial Peripheral Interface (SPI).

[0060] Based on steps S102 to S106 above, the information processing box responds to the vehicle power-on by acquiring the global system positioning time collected by the positioning module in the vehicle and the network protocol time collected by the network module in the vehicle. The information processing box transmits the precise protocol time to the cockpit host based on the global system positioning time and the network protocol time. The cockpit host synchronously updates the initial display time in multiple display modules according to the precise protocol time to obtain the target display time. That is, in this embodiment, the information processing box, as the time source of the whole vehicle, determines the precise time protocol time based on the global system positioning time and the network protocol time, and transmits the precise time protocol time to the cockpit host (also known as the cockpit system) so as to use the cockpit host to control the display modules in the vehicle to display the precise time protocol time, thereby achieving the purpose of controlling multiple display modules to display time synchronously, thus solving the technical problem of asynchronous display time in multiple display modules and realizing the technical effect of controlling the display time of multiple display modules to display synchronously.

[0061] The method described in this embodiment will now be further explained.

[0062] As an optional embodiment, step S104, where the information processing box transmits the precise protocol time to the cockpit host, includes: a first device deployed in the information processing box generates a time synchronization message in response to determining the precise protocol time, wherein the time synchronization message is used to transmit the precise protocol time to the cockpit host; the first device uses the vehicle's central control unit to send the time synchronization message to the cockpit control module in the cockpit host; the cockpit host synchronously updates the initial display time in multiple display modules according to the precise protocol time to obtain the target display time, including: the cockpit control module updates its kernel time according to the precise protocol time in the time synchronization message, and updates the initial display time of the central control screen in multiple display modules according to the updated kernel time to obtain the target display time.

[0063] In this embodiment, the first device can be a gPTP master, which can be deployed in an information processing box. The first device can initiate a time synchronization message in response to determining the precise protocol time, ensuring that nodes in the network can achieve accurate time synchronization. The time synchronization message is used to transmit the precise protocol time to the cockpit host and can be built based on the precise protocol time. The cockpit control module can be a cockpit SOC, also known as a cockpit Android system or Android SOC. The kernel time can be the kernel management time of the cockpit control module and can be the base reference time.

[0064] Optionally, the Tbox may include a GPS module and a 4G module. The GPS module can be used to obtain GPS time (also known as GPS time), and the 4G module can be used to obtain NTP time (also known as NTP time) from the 4G network. Both GPS and NTP times can be used as the vehicle's clock source. A gPTP master can be deployed on the Tbox, initiating time synchronization messages to the central control unit (CCU). The CCU can then send these time synchronization messages to the cockpit host. The cockpit control module within the cockpit host, acting as a gPTP slave, receives these messages. The cockpit control module updates its kernel time according to the precise protocol time in the time synchronization message and synchronizes the vehicle's system time accordingly.

[0065] Optionally, the Tbox receives time information from GPS and 4G networks, which is converted into a precise protocol format (PPP) time. Inside the Tbox, a gPTP master device is deployed, responsible for processing the PPP time and generating time synchronization messages. Based on the determined PPP time, the gPTP master device generates a time synchronization message, which may include a precise timestamp and synchronization data for subsequent time synchronization operations. The Tbox sends the time synchronization message to the vehicle's central control unit (CCU) via Ethernet. The CCU, as the central node of the network, is responsible for forwarding this precise time information to the cockpit host. Upon receiving the time synchronization message, the CCU forwards it via Ethernet to the cockpit control module (a System-on-a-Chip driven by Android) within the cockpit host. At this stage, the gPTP time information (i.e., the PPP time) begins to propagate into the cockpit system.

[0066] Optionally, the Android SOC in the cockpit host acts as a gPTP slave node. Upon receiving a time synchronization message, it can start a time synchronization service (TimeSyncService). This service is responsible for parsing the precise protocol time in the time synchronization message and then updating the kernel time using the precise protocol time. TimeSyncService calibrates the precise protocol time with the kernel time of the cockpit control module, updating the kernel's clock reference. The updated kernel time can be passed to the CarTimeSync service in the Android firmware (FW). This service obtains the kernel time and transmits it to the central control screen display module, updating the initial display time of the central control screen. After receiving the precise time information from the CarTimeSync service, the central control screen displays the updated time, i.e., the "target display time," ensuring that the time displayed on the central control screen is consistent with the precise protocol time, providing a high-precision time display to the user.

[0067] In this embodiment, by deploying a gPTP master device, the high precision of the Precision Time Protocol (NTP) ensures the accuracy and reliability of time information during transmission. gPTP is more precise than the traditional NTP time synchronization method, achieving microsecond-level synchronization accuracy. Designing the transmission path of time synchronization messages via the CCU not only leverages the CCU's pivotal role in the vehicle's internal network but also increases the robustness of time synchronization. Even if the direct connection between the information processing box and the cockpit host fails, time information can still reach the cockpit host through the CCU's forwarding function, ensuring the time accuracy of the cockpit system remains unaffected. Simultaneously, the cockpit control module in the cockpit host can automatically adjust the kernel time based on the gPTP time synchronization messages. This automatic update mechanism reduces the need for manual adjustments, improving the system's automation level and efficiency. Furthermore, the updated kernel time directly affects the time display on the central control screen, ensuring that the displayed time is highly consistent with the actual time and avoiding confusion caused by time deviations.

[0068] In intelligent cockpit systems, the accuracy and consistency of time display directly impact the user's driving experience. The methods described above specifically address the time asynchrony issue caused by differences in time sources between the cockpit main unit and other vehicle control units. This is particularly effective when the cockpit main unit contains multiple System-on-Chip (SOCs), ensuring that even if each SOC has an independent clock source, a unified and accurate time information transmission and display can be achieved through the cockpit main unit's internal clock synchronization mechanism.

[0069] As an optional embodiment, the cockpit main unit includes a microprocessor and a cockpit control module. The cockpit control module updates its kernel time according to the precision protocol time in the time synchronization message. This includes: the cockpit control module, in response to receiving the time synchronization message, generating a real-time clock request and transmitting the real-time clock request to the microprocessor, wherein the real-time clock request requests the microprocessor to calibrate the real-time clock time according to the precision protocol time; a board-level support package in the cockpit main unit initiates a time synchronization service and uses the time synchronization service to obtain the calibrated real-time clock time from the microprocessor; the board-level support package synchronizes the calibrated real-time clock time to the kernel of the cockpit control module to obtain the kernel time.

[0070] In this embodiment, the aforementioned microprocessor (Microcontroller Unit, or MCU for short) can be used to perform time-related functions and can also be called a microcontroller or microcontroller unit.

[0071] Optionally, after receiving the gPTP time from the CCU, the cockpit control module can use the time synchronization service of the Hardware Abstraction Layer (HAL) to calibrate the MCU's real-time clock (RTC time) and update the kernel time. When the Android side of the cockpit host powers on, the cockpit control module can initiate an RTC time request (i.e., a real-time clock request) to the MCU through the Virtual Hardware Abstraction Layer (vhal) and transmit the real-time clock request to the microprocessor.

[0072] Optionally, the cockpit head unit's time synchronization and arbitration are implemented in Android. The cockpit head unit's MCU generates RTP CLK time via an RTC crystal oscillator. After the Android system of the cockpit head unit boots up (equivalent to the vehicle powering on), the BoardSupport Package (BSP) starts the TimeSyncService service. The TimeSyncService service can obtain the MCU's real-time clock (also known as RTC time) and synchronize it to the kernel, forming kernelTime. After the Android firmware's CarTimeSync starts, it directly obtains the system time and displays it on the central control screen. The system time can be the time displayed on the screen; updating the system time is to correct the time displayed on the screen.

[0073] Optionally, when the cockpit control module receives a time synchronization message (e.g., a gPTP time synchronization message), it immediately responds by generating a real-time clock request. The cockpit control module sends the real-time clock request to the microprocessor, requesting the microprocessor to calibrate the real-time clock according to a precise protocol time (such as the precise time of gPTP). A TimeSyncService can be started through the BSP layer. This TimeSyncService can be a service layer program that can handle time synchronization requests and interact directly with hardware (e.g., the MCU). Using the time synchronization service, the calibrated real-time clock time can be obtained from the microprocessor. The TimeSyncService communicates with the microprocessor to obtain the real-time clock value calibrated according to the precise protocol time. The TimeSyncService can further synchronize the calibrated real-time clock value to the kernel time of the cockpit control module, updating the kernel clock to ensure that all system operations are based on a unified and accurate time base.

[0074] In this embodiment, a precise protocol (such as gPTP) is used for time synchronization to ensure a more accurate time base for the cockpit main unit and reduce time errors. Establishing a time synchronization mechanism between the cockpit control module and the microprocessor enhances the time consistency of all parts of the cockpit system, avoiding time deviations between different components. When an external time source (such as the Tbox) fails, the cockpit main unit can quickly restore time synchronization through the microprocessor's real-time clock and internal time synchronization service, reducing the functional impact caused by time asynchrony.

[0075] Optionally, by utilizing precise protocol timing, the time synchronization accuracy and consistency between the cockpit mainframe microprocessor and the cockpit control module are enhanced, accurate time calibration is achieved during system startup, the time recovery capability of the cockpit system in case of failure is strengthened, and ultimately the reliability and user experience of the entire cockpit system are improved.

[0076] As an alternative embodiment, the method may further include: in response to receiving a real-time clock request, the microprocessor transmits the calibrated real-time clock time to the instrument control module in the cockpit main unit.

[0077] In this embodiment, if the microprocessor receives a real-time clock request, it can be controlled to transmit the calibrated real-time clock time to the instrument control module in the cockpit main unit. This instrument control module can be an instrument system-on-a-chip (SOC).

[0078] Optionally, after receiving a real-time clock request, the MCU can synchronously send the calibrated real-time clock time from the request to the instrument control module in the cockpit host. Then, it sends a VHA signal to the Android-side TimeSyncService to notify that the time request has been responded to, thus forming a closed loop.

[0079] Optionally, when the microprocessor in the cockpit host receives a real-time clock request (i.e., a real-time clock calibration request) initiated by the cockpit host, the microprocessor can update the RTC using the latest and most accurate precision protocol time according to the received calibration request, and then transmit the updated real-time clock time to the instrument control module through an internal communication mechanism (such as a USB interface or CAN bus) to ensure that the time displayed on the instrument panel is synchronized with the time of the cockpit system and other vehicle modules.

[0080] As an optional embodiment, the method may further include: the cockpit control module acquiring a standard network protocol time in response to the completion of network time service preparation in the cockpit host; adjusting the kernel time of the cockpit control module and the real-time clock time of the microprocessor to the standard network protocol time; controlling the microprocessor to transmit the adjusted real-time clock time to the instrument control module; and controlling the instrument control module to synchronize the initial display time of the instrument panel in the display module to the set real-time clock time.

[0081] In this embodiment, the aforementioned network time service can be an NTP service. The aforementioned standard network protocol time can be NTP network time.

[0082] Optionally, if the cockpit head unit is connected to WiFi or obtains network access from the TBOX, after the cockpit head unit's NTPService is ready, the cockpit control module can use the CarTimeSync service to obtain the NTP network time and send the standard network protocol time to the central control unit's TimeSyncService via Vhal. The TimeSyncService then sets the standard network protocol time in the central control unit's KernelTime and the MCU's RTC. Upon receiving the standard network protocol time, the MCU directly synchronizes it to the QNX instrument cluster's TimeSyncService, which then transmits it to the KernelTime, and finally displays the time on the instrument cluster screen.

[0083] Optionally, when the cockpit host is connected to the network and the NTP (Network Time Protocol) service is ready, the cockpit control module can obtain the standard network protocol time via the network. Upon receiving the standard network protocol time, the cockpit control module synchronizes the kernel time to the standard network protocol time by invoking the time adjustment function. This step ensures that the cockpit host's internal clock is consistent with the network time server's clock. Simultaneously, the TimeSyncService service in the HAL layer of the cockpit host synchronizes the standard network protocol time obtained from NTP to the microprocessor's real-time clock, adjusting the real-time clock time to the standard network protocol time. The RTC is a hardware clock that continues to keep time even when the system is in sleep mode or experiencing a power outage. By updating the RTC, the time accuracy of the cockpit host is ensured in any state.

[0084] Optionally, after receiving the updated RTC time, the microprocessor sends the adjusted real-time clock time to the instrument control module (a SOC driven by the QNX system) via an internal communication mechanism (such as SPI, I2C, etc.). Upon receiving the adjusted real-time clock time, the instrument control module updates its internal time base. After updating its internal time base, the instrument control module synchronizes the time displayed on the instrument panel to the new real-time clock time. This means that the time information on the instrument panel will reflect the latest time synchronization result, remaining consistent with the cockpit main unit and network time.

[0085] Through the steps described above, even when gPTP time synchronization is unavailable (e.g., due to Ethernet failure or the Tbox's inability to obtain GPS or 4G network time), the cockpit system can still obtain time information from the network via NTP service, maintaining time synchronization and accuracy. This mechanism enhances the robustness of the cockpit system in complex environments, ensuring that the time display on the central control screen and instrument panel will not show significant deviations even when the external time source is disconnected, thus maintaining a good user experience. Furthermore, RTC time synchronization between the microprocessor and the instrument control module further improves the accuracy and stability of the time display, allowing for rapid restoration of accurate time display even after the cockpit main unit restarts from hibernation.

[0086] In this embodiment, by deploying a network time service in the cockpit host and acquiring standard network protocol time, the system can quickly switch to an NTP time source even if the primary time source (such as GPS or gPTP) fails, maintaining the continuity and reliability of time synchronization. Regardless of whether the cockpit host receives GPS, gPTP, or NTP time, the time displayed on the instrument panel remains consistent with the central control screen, avoiding user confusion and potential driving safety issues caused by time asynchrony. By directly adjusting the kernel time of the cockpit control module and the real-time clock time of the microprocessor, the latency during time synchronization is reduced, improving the response speed of the cockpit system during startup or network recovery, and ensuring that the accuracy of the time display meets the high standards required for intelligent cockpits.

[0087] As an optional embodiment, the method may further include: the cockpit control module, in response to obtaining the standard network protocol time, determining whether the standard network protocol time and the target display time displayed on the central control screen are synchronized; the cockpit control module, in response to the asynchronous relationship between the standard network protocol time and the target display time displayed on the central control screen, updating the target display time to the standard network protocol time.

[0088] In this embodiment, if the cockpit control module obtains the standard network protocol time, it can determine whether the standard network protocol time and the target display time shown on the central control screen are synchronized. If the standard network protocol time and the target display time shown on the central control screen are asynchronous, the target display time can be updated to the standard network protocol time.

[0089] Optionally, once the central control unit's gPTP is ready, the Android side's gPTP Slava synchronizes the CCU's time, then directly updates the gPTP time to the kernel time, and simultaneously sends a VHA signal to CarTimeSync, notifying CarTimeSync that the highest priority gPTP time has been synchronized, eliminating the need to synchronize lower priority times such as NTP. CarTimeSync then updates the system time display and shows it on the central control screen.

[0090] Figure 3 This is a schematic diagram of a dual-SOC cockpit main engine time synchronization system provided in one embodiment of this application, as shown below. Figure 3 As shown, the telematics unit 301 obtains precise time information through its built-in GPS and 4G network modules. This time information can serve as a clock source and may include both GPS and NTP times. A gPTP master 302 is deployed on the telematics unit 301 to initiate time synchronization messages. The gPTP master 302 can send time information to the central controller 303 via Ethernet. After receiving the precise protocol time from the telematics unit 301, the central controller 303 forwards the precise protocol time to other control units on the vehicle via Ethernet, including the cockpit host 304. This ensures time synchronization for all controllers throughout the vehicle.

[0091] Optionally, the Android system in the cockpit host 304 acts as a gPTP slave to receive precise protocol timing from the central controller 303. Upon receiving the message, the TimeSyncService service of the hardware abstraction layer calibrates the real-time clock of the microcontroller 305 and updates the Android kernel time, which becomes the kernel time. This Android system can be deployed within the cockpit SoC.

[0092] Optionally, after the Android system of the cockpit main unit 304 starts up, it directly obtains the system time through the time synchronization service and displays it on the central control screen. This step ensures that the time on the central control screen is accurate.

[0093] Optionally, after the cockpit host 304 obtains the NTP time via a network (such as WiFi or from a Tbox), the in-vehicle time synchronization service sends the NTP time to the central control unit's time synchronization service through a virtual hardware abstraction layer. The time synchronization service then sets the calibrated time into the central control unit's kernel time and the microcontroller 305's real-time clock. After receiving the new time information, the microcontroller 305 can directly synchronize the received time to the instrument cluster's time synchronization service, which then adjusts the instrument cluster's kernel time, thereby updating the instrument cluster's time display and achieving consistency and accuracy between the central control screen and the instrument cluster's time.

[0094] Optionally, time synchronization and arbitration for the cockpit host 304 are implemented in the Android system. Time information synchronized via gPTP is preferred because it offers the highest accuracy. Once gPTP time synchronization is ready, the Android-side gPTP slave can update the gPTP time to the kernel time and signal through the virtual hardware abstraction layer to notify the onboard time synchronization service that it does not need to resynchronize lower-priority time sources (such as NTP time). This ensures the use of the most accurate time source while reducing unnecessary network load and CPU resource consumption.

[0095] Optionally, if the central controller 303 fails to update or send the gPTP time (possibly due to a damaged Ethernet transmission link), and if network time (via WiFi) is available, the Android system in the cockpit host synchronizes the NTP time every 3 minutes for display on the central control screen. The NTP time is then synchronized to the central controller 303, which in turn transmits it to the QNX instrument cluster system for display, thus maintaining time consistency between the central control screen and the instrument cluster. If network time is also unavailable, the central control screen and instrument cluster directly use the RTC time from the central controller 303 for display. While this may not be as accurate as gPTP or NTP time, it provides a basic time reference.

[0096] In conclusion, Figure 3 It clearly demonstrates how the cockpit system ensures the time accuracy and consistency of the central control screen and instrument panel under various network conditions through multi-level time sources (gPTP, NTP, RTC) and multi-step synchronization mechanisms, thereby providing a stable user experience and system performance.

[0097] Optionally, CarTimeSync can be parsed using gPTP and NTP timestamps to obtain the time source. Figure 4 This is a flowchart of the CarTimeSync time synchronization process of a cockpit host Android FW provided in one embodiment of this application, as shown below. Figure 4As shown, the process may include the following steps.

[0098] Step S401: Parse the configuration file to obtain the time source.

[0099] In this embodiment, the CarTimeSync configuration file (timesync.json) is used to obtain the time source.

[0100] Optionally, after CarTimeSync starts, it can load configuration information from the timesync.json file, including the priorities of various time sources, synchronization periods, and actions to be taken under specific conditions. Based on the priority settings in timesync.json, CarTimeSync may first attempt to use the gPTP time (if available), followed by the NTP time. If none of these time sources are available, the MCU's RTC time will be used.

[0101] Optionally, timesync.json can also include time synchronization strategies, such as how CarTimeSync selects and switches time sources when both gPTP and NTP times are available to ensure maximum time accuracy and synchronization. The configuration file can also include parameters for correcting time discrepancies. These parameters help the CarTimeSync service make necessary adjustments during time synchronization to compensate for time deviations caused by network latency or other factors.

[0102] Optionally, the CarTimeSync service can monitor the synchronization status of gPTP and NTP times according to the rules in timesync.json and perform corresponding operations. For example, when gPTP time synchronization is successful, CarTimeSync will update the kernel time and simultaneously notify the user to stop NTP time synchronization attempts.

[0103] Step S402: Monitor the gPTP time synchronization status.

[0104] In this embodiment, when the cockpit host Android system starts up, the CarTimeSync service begins to run. The CarTimeSync service can obtain the precision time protocol time synchronization status through a virtual hardware abstraction layer interface, such as the Car Application Programming Interface (Car API).

[0105] Step S403: Determine if gPTP is synchronized.

[0106] In this embodiment, it is determined whether gPTP is synchronized. If it is synchronized, step S404 can be executed; if not, step S406 can be executed.

[0107] Optionally, if the gPTP time synchronization status indicates that the time has been synchronized, CarTimeSync will directly use the gPTP time as the time source and update the kernel time. At the same time, it will send the time information to the TimeSyncService service on the central control unit via VHAL, thereby updating the display time on the central control screen.

[0108] Step S404: Cancel gPTP status monitoring.

[0109] In this embodiment, if gPTP synchronization is successful, gPTP status monitoring can be cancelled.

[0110] Step S405: Disable NTP time synchronization.

[0111] In this embodiment, after canceling gPTP status monitoring, NTP time synchronization can be turned off.

[0112] Step S406: Obtain the NTP time.

[0113] In this embodiment, if gPTP time synchronization fails (e.g., due to Ethernet transmission link failure), the process proceeds to the next step of obtaining the NTP time. This NTP time can also be referred to as the NTP time.

[0114] Step S407: Update the system time via NTP time.

[0115] In this embodiment, the CarTimeSync service checks the Network Time Protocol (NTP) synchronization status. If NTP synchronization is successful, the CarTimeSync service obtains the network time from the NTP time server and updates the system time.

[0116] Step S408: Determine whether the NTP time is synchronized.

[0117] In this embodiment, it is determined whether the NTP time is synchronized. If it is synchronized, step S409 can be executed; if it is not synchronized, step S410 can be executed.

[0118] Step S409: Update the display time on the instrument panel via VHAL.

[0119] In this embodiment, the updated system time can also be sent to the TimeSyncService service on the central control unit via VHAL to update the time displayed on the central control screen. Simultaneously, the CarTimeSync service synchronizes the NTP time to the TimeSyncService service on the instrument cluster via the MCU (microcontroller unit), ensuring time synchronization between the instrument cluster and the central control screen.

[0120] Step S410: Use the kernel's real-time clock time.

[0121] In this embodiment, if NTP time synchronization also fails, it means that the cockpit head unit cannot synchronize time from either the vehicle's internal time source (gPTP) or obtain time from an external network. In this case, the CarTimeSync service can rely on the real-time clock (RTC) of the cockpit head unit's internal MCU to provide time information. The RTC time can be updated before the cockpit head unit goes to sleep, using the current actual time as the reference, thus ensuring the accuracy of the RTC time for a certain period of time even without an external time source. The RTC time can be the real-time clock time.

[0122] In this embodiment, the gPTP time is first obtained via VHAL, then it is determined whether the gPTP and NTP times are synchronized. If they are synchronized, NTP time synchronization is disabled; if they are not synchronized, the system time is updated via NTP. Next, it is determined whether the NTP times are synchronized. If they are, the NTP time is updated to the instrument's QNX via the MCU through VHAL; if they are not synchronized, CarTimeSync uses the RTC time from Kernet Time to update the system time. The aforementioned NTP time can be the obtained standard network protocol time.

[0123] Optionally, CarTimeSync can listen to the gPTP time synchronization status by calling the Car API to determine whether the gPTP time and NTP time are synchronized. If they are synchronized, it cancels the gPTP status listening and disables NTP time synchronization. If the gPTP time is not synchronized, it obtains the NTP time and updates the NTP time to the system time.

[0124] In this embodiment, when the CCU fails to update or send gPTPP time (e.g., due to a damaged Ethernet transmission link), if network time is available (WiFi connection is established), the Android system synchronizes NTP time from the network every 3 minutes. This NTP time is then displayed on the central control screen, and the NTP is sent to the MCU, which in turn transmits it to the instrument cluster (QNX) for display, thus synchronizing the time between the central control system and the instrument cluster. If network time is also unavailable, the central control system and the instrument cluster directly use the MCU's RTP for actual display. To avoid inaccurate RTC time in the MCU due to prolonged operation of the cockpit main unit, the current actual time can be synchronized to the MCU's RTC clock before each sleep cycle. When the MCU is in sleep mode, RTC timing begins based on the actual time, ensuring time accuracy upon startup.

[0125] Optionally, gPTP time has the highest priority in time source utilization, followed by NTP time, and lastly RTC time. When gPTP time synchronization is successful, CarTimeSync can immediately use the gPTP time and notify the cessation of synchronization attempts from other time sources (such as disabling NTP time synchronization). If gPTP time is unavailable but NTP time can be synchronized, then NTP time will be used. Conversely, if NTP time is also unavailable, RTC time will be used as a backup time source.

[0126] Optionally, the cockpit main unit can flexibly switch time sources under different conditions (normal or abnormal). It can prioritize the use of gPTP time to ensure the highest accuracy, then use NTP time to deal with the failure of the vehicle's internal time source, and finally rely on RTC time to ensure basic time display, maintaining time synchronization and accuracy even in extreme cases. This multi-level time source processing strategy significantly enhances the cockpit system's time management capabilities and user experience when facing complex environmental changes.

[0127] Optionally, when the cockpit control module (usually running on an Android system) in the cockpit host successfully obtains the latest time information from the network time server (NTP server), it obtains the standard network protocol time. The cockpit control module can compare the obtained standard network protocol time with the target display time currently displayed on the central control screen to check if there is a time difference between the two, in order to determine whether time synchronization adjustment is needed. If it is found that there is a deviation between the current display time on the central control screen and the standard network time, the cockpit control module will automatically perform a time update operation to adjust the initial display time of the central control screen to the standard network protocol time, ensuring that the time information displayed on the central control screen is synchronized with the network time.

[0128] In this embodiment, not only is the problem of time display errors caused by network or system issues on the central control screen resolved, but the system's time synchronization capability is also enhanced by introducing network time as a redundant clock source. This ensures that even if the primary time source (such as gPTP) fails, the accuracy and integrity of the time display can be maintained through the backup time source (network time).

[0129] Optionally, in this embodiment, the time of multiple controllers in the vehicle all originates from the TBOX, achieving clock synchronization for all vehicle controls. The cockpit host's time synchronization is prioritized, ensuring that while the cockpit host synchronizes with the vehicle's time, its own time source (e.g., NTP time and RTC time) is introduced to guarantee the accuracy and time synchronization of the time displayed on the central control screen and instrument panel.

[0130] Optionally, in the event of abnormal vehicle timing, the cockpit main unit utilizes network time to improve the accuracy of its timing. The MCU's RTC processing logic is optimized to improve the accuracy of the cockpit main unit's power-on time.

[0131] In this application embodiment, a method for synchronously displaying time in a vehicle is proposed. This method uses an information processing box as the time source for the entire vehicle, determines a precise time protocol time based on the Global System for Positioning (GPS) time and network protocol time, and transmits the precise time protocol time to the cockpit host. The cockpit host then controls the display modules in the vehicle to display the precise time protocol time, thereby achieving the purpose of controlling multiple display modules to display time synchronously. This solves the technical problem of asynchronous display times in multiple display modules and achieves the technical effect of controlling the display times of multiple display modules to display synchronously.

[0132] Example 2

[0133] According to an embodiment of this application, a vehicle is also provided. It should be noted that this vehicle can be used to execute the method for synchronously displaying time in a vehicle as described in Embodiment 1.

[0134] This application also provides a vehicle, please refer to the embodiments thereof. Figure 5 , Figure 5 This is a schematic diagram of a vehicle system architecture provided in one embodiment of this application, as shown below. Figure 5 As shown, the vehicle 500 may include: an information processing box 502, a cockpit host 504, and a display module 506.

[0135] Information processing box 502 is used to respond to vehicle power-on by acquiring the global system positioning time collected by the positioning module in the vehicle and the network protocol time collected by the network module in the vehicle; based on the global system positioning time and the network protocol time, it determines the precise protocol time and transmits the precise protocol time to the cockpit host.

[0136] The cockpit main unit 504 is used to synchronously update the initial display time in multiple display modules according to a precise protocol to obtain the target display time.

[0137] Multiple display modules 506, including at least a central control screen and an instrument panel, are used to display the target display time.

[0138] In this embodiment, the cockpit main unit may further include: a cockpit control module, configured to receive a precision protocol time; update the kernel time according to the precision protocol time; update the initial display time of the central control screen in multiple display modules according to the updated kernel time to obtain a target display time; a microprocessor, configured to acquire the precision protocol time transmitted by the cockpit control module and synchronize the precision protocol time to the instrument control module; and an instrument control module, configured to, in response to receiving the precision protocol time synchronization, update the initial display time of the instrument screen in multiple display modules to the target display time according to the precision protocol time.

[0139] Optionally, the cockpit control module can be a cockpit SOC. The instrument control module can be an instrument SOC.

[0140] Optionally, the system may also include a central control unit for acquiring precision protocol timing from the information processing box and transmitting the precision protocol timing to the cockpit control module.

[0141] In this embodiment, the information processing box includes: a first device for generating a time synchronization message in response to determining the precision protocol time; and sending the time synchronization message to the cockpit control module in the cockpit host using the vehicle's central control unit.

[0142] Optionally, the first device mentioned above can be a gPTP master clock.

[0143] In this embodiment, the cockpit host includes: a board-level support package for starting a time synchronization service and using the time synchronization service to obtain a calibrated real-time clock time from the microprocessor; and synchronizing the calibrated real-time clock time to the kernel of the cockpit control module to obtain the kernel time.

[0144] Example 3

[0145] According to an embodiment of this application, a device for synchronously displaying the time in a vehicle is also provided. It should be noted that this device for synchronously displaying the time in a vehicle can be used to execute the method for synchronously displaying the time in a vehicle described in Embodiment 1.

[0146] This application also provides a device 600 for synchronously displaying the time in a vehicle. Please refer to [link / reference]. Figure 6 , Figure 6This is a structural diagram of a device for synchronously displaying time in a vehicle according to an embodiment of this application, as shown below. Figure 6 As shown, the device 600 for synchronously displaying the time in the vehicle may include: an acquisition unit 602, a determination unit 604, and an update unit 608.

[0147] The acquisition unit 602 is used to acquire the vehicle's global system positioning time and network protocol time in response to the vehicle being powered on. The global system positioning time is collected by the positioning module in the vehicle, and the network protocol time is collected by the network module in the vehicle.

[0148] The determining unit 604 is used to control the information processing box to determine the precise protocol time based on the global system positioning time and network protocol time.

[0149] The update unit 608 is used to control the cockpit main unit to update the initial display time in multiple display modules according to the precise protocol time to obtain the target display time.

[0150] The device for synchronously displaying time in a vehicle provided in this application embodiment achieves the following technical effects: Through the acquisition unit, in response to vehicle power-on, the vehicle's global positioning system (GPS) time and network protocol time are acquired, wherein the GPS time is collected by the vehicle's positioning module and the network protocol time is collected by the vehicle's network module; through the determination unit, the information processing box is controlled to determine the precise protocol time based on the GPS time and network protocol time; through the update unit, the cockpit host is controlled to update the initial display time in multiple display modules according to the precise protocol time to obtain the target display time, thereby solving the technical problem of asynchronous display times in multiple display modules and achieving the technical effect of synchronously displaying the display times in multiple display modules.

[0151] It should be noted that the above-mentioned units can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0152] Example 4

[0153] This application also provides an electronic device 70, please refer to... Figure 7 , Figure 7 This is a structural diagram of an electronic device provided in one embodiment of the present application, including a processor 710 and a memory 720, wherein the memory 710 is used to store computer programs; the processor 720 is used to execute the programs stored in the memory 710 to implement the method for synchronously displaying time in a vehicle as described in any embodiment of the present application.

[0154] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0155] Step S1: In response to the vehicle power-on, obtain the vehicle's global system positioning time and the vehicle's network protocol time. The global system positioning time is collected by the positioning module in the vehicle, and the network protocol time is collected by the network module in the vehicle.

[0156] Step S2: Control the information processing box to determine the precise protocol time based on the global system positioning time and network protocol time;

[0157] Step S3: Control the cockpit main unit to update the initial display time in multiple display modules according to the precise protocol time to obtain the target display time.

[0158] The electronic device provided in this application embodiment achieves the following technical effects: the information processing box is used as the time source of the whole vehicle. Based on the global system positioning time and network protocol time, the precise time protocol time is determined and transmitted to the cockpit host. The cockpit host controls the display modules in the vehicle to display the precise time protocol time, thereby achieving the purpose of controlling multiple display modules to display the time synchronously. This solves the technical problem of asynchronous display time in multiple display modules and achieves the technical effect of controlling the display time of multiple display modules to display synchronously.

[0159] Those skilled in the art will understand that Figure 7 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones (such as Android phones, iOS phones, etc.), tablets, PDAs, and mobile internet devices (MIDs) and other terminal devices. Figure 7 This does not limit the structure of the aforementioned electronic device. For example, electronic device 70 may also include components that are more... Figure 7 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 7 The different configurations shown.

[0160] Example 5

[0161] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method for synchronously displaying time in a vehicle as described in any embodiment of this application.

[0162] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0163] Step S1: In response to the vehicle power-on, obtain the vehicle's global system positioning time and the vehicle's network protocol time. The global system positioning time is collected by the positioning module in the vehicle, and the network protocol time is collected by the network module in the vehicle.

[0164] Step S2: Control the information processing box to determine the precise protocol time based on the global system positioning time and network protocol time;

[0165] Step S3: Control the cockpit main unit to update the initial display time in multiple display modules according to the precise protocol time to obtain the target display time.

[0166] The electronic device provided in this application embodiment achieves the following technical effects: the information processing box is used as the time source of the whole vehicle. Based on the global system positioning time and network protocol time, the precise time protocol time is determined and transmitted to the cockpit host. The cockpit host controls the display modules in the vehicle to display the precise time protocol time, thereby achieving the purpose of controlling multiple display modules to display the time synchronously. This solves the technical problem of asynchronous display time in multiple display modules and achieves the technical effect of controlling the display time of multiple display modules to display synchronously.

[0167] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0168] The electronic device provided in this application embodiment achieves the following technical effects:

[0169] In this application, "multiple" refers to two or more.

[0170] In this application, unless otherwise expressly defined, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0171] The terms “first,” “second,” “third,” “fourth,” etc., in this application (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0172] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0173] Unless otherwise specified, all steps in this application may be performed sequentially or randomly. For example, if a method includes steps A and B, it means that the method may include steps A and B performed sequentially, or it may include steps B and A performed sequentially. For example, if a method may also include step C, it means that step C may be added to the method in any order. For example, the method may include steps A, B, and C, or it may include steps A, C, and B, or it may include steps C, A, and B, etc.

[0174] The above are merely preferred embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for synchronously displaying time in a vehicle, characterized in that, The method is applied in a vehicle, which includes an information processing box, a cockpit host, and multiple display modules, and includes: In response to the vehicle being powered on, the information processing box acquires the global system positioning time collected by the positioning module in the vehicle, and the network protocol time collected by the network module in the vehicle. The information processing box determines the precise protocol time based on the global system positioning time and the network protocol time, and transmits the precise protocol time to the cockpit main unit; The cockpit main unit synchronously updates the initial display time in multiple display modules according to the precision protocol to obtain the target display time.

2. The method according to claim 1, characterized in that, The information processing box transmits the precise protocol in real time to the cockpit main unit, including: In response to determining the precision protocol time, the first device deployed in the information processing box generates a time synchronization message, wherein the time synchronization message is used to transmit the precision protocol time to the cockpit host. The first device uses the vehicle's central control unit to send the time synchronization message to the cockpit control module in the cockpit host; The cockpit main unit synchronously updates the initial display time of multiple display modules according to the precise protocol to obtain the target display time, including: The cockpit control module updates its kernel time according to the precision protocol time in the time synchronization message, and updates the initial display time of the central control screen in the multiple display modules according to the updated kernel time, to obtain the target display time.

3. The method according to claim 2, characterized in that, The cockpit main unit includes a microprocessor, and the cockpit control module updates its kernel time according to the precise protocol time in the time synchronization message, including: In response to receiving the time synchronization message, the cockpit control module generates a real-time clock request and transmits the real-time clock request to the microprocessor, wherein the real-time clock request is used to request the microprocessor to calibrate the real-time clock according to the precision protocol time. The board-level support package in the cockpit host starts a time synchronization service and uses the time synchronization service to obtain the calibrated real-time clock time from the microprocessor. The board-level support package synchronizes the calibrated real-time clock time to the kernel of the cockpit control module to obtain the kernel time.

4. The method according to claim 3, characterized in that, The method further includes: In response to the real-time clock request, the microprocessor transmits the calibrated real-time clock time to the instrument control module in the cockpit main unit.

5. The method according to claim 4, characterized in that, The method further includes: The cockpit control module responds to the completion of network time service preparation in the cockpit host by obtaining the standard network protocol time and adjusting the kernel time and the real-time clock time of the microprocessor to the standard network protocol time. The microprocessor transmits the adjusted real-time clock time to the instrument control module; The instrument control module synchronizes the initial display time of the instrument screen in the display module with the set real-time clock time.

6. The method according to claim 5, characterized in that, The method further includes: The cockpit control module, in response to acquiring the standard network protocol time, determines whether the standard network protocol time and the target display time displayed on the central control screen are synchronized; The cockpit control module responds asynchronously to the standard network protocol time and the target display time displayed on the central control screen, updating the target display time to the standard network protocol time.

7. A vehicle, characterized in that, include: The information processing box is used to, in response to the vehicle being powered on, acquire the global system positioning time collected by the positioning module in the vehicle and the network protocol time collected by the network module in the vehicle; determine the precise protocol time based on the global system positioning time and the network protocol time, and transmit the precise protocol time to the cockpit host. The cockpit main unit is used to synchronously update the initial display time in multiple display modules according to the precise protocol time to obtain the target display time; The plurality of display modules, including at least a central control screen and an instrument panel screen, are used to display the target display time.

8. The vehicle according to claim 7, characterized in that, The cockpit main unit includes: The cockpit control module is used to receive the precision protocol time; update the kernel time according to the precision protocol time; update the initial display time of the central control screen according to the updated kernel time, and obtain the target display time; The microprocessor is used to acquire the precision protocol time transmitted by the cockpit control module and synchronize the precision protocol time to the instrument control module; The instrument control module is used to update the initial display time of the instrument screen to the target display time in response to receiving the precision protocol time synchronization, according to the precision protocol time.

9. The vehicle according to claim 8, characterized in that, The information processing box also includes: A first device is configured to generate a time synchronization message in response to determining the precision protocol timing; and to send the time synchronization message to the cockpit control module in the cockpit host using the vehicle's central control unit.

10. The vehicle according to claim 8, characterized in that, The cockpit main unit includes: A board-level support package is used to start a time synchronization service and use the time synchronization service to obtain a calibrated real-time clock time from the microprocessor; the calibrated real-time clock time is synchronized to the kernel of the cockpit control module to obtain the kernel time.

Images