Display method and device, vehicle, medium and program product

Abstract

The invention relates to a display method and device, a vehicle, a medium and a program product in the technical field of electric digital data processing. The method comprises the following steps: receiving tire data sent by a tire sensor; according to the types of the application programs corresponding to the tire data, a target domain controller is determined, different types of application programs are installed through software development kits configured in different domain controllers, and the types are used for representing iterative updating requirements of the application programs; and according to the tire data, executing tire information display through the application program installed in the target domain controller. Therefore, the problem of fusion of the Bluetooth tire pressure and the whole vehicle Bluetooth is solved, the cost is saved, the flexibility, the maintainability and the intelligent level of the system are greatly enhanced, and safer, more efficient and more comfortable driving experience is brought to a user.

Description

Technical Field

[0001] The present disclosure relates to the technical field of electronic digital data processing, and in particular to a display method, device, vehicle, medium and program product. Background Art

[0002] Vehicles can realize tire pressure monitoring function through intelligent networking. Tire pressure monitoring mostly adopts RF (Radio Frequency) technology solution, and Bluetooth tire sensors can also be used to reuse the vehicle's car machine Bluetooth as a tire pressure receiving module.

[0003] In related scenarios, TPMS (Tire Pressure Monitoring System) uses sensor technology, wireless transmission and receiving technology, etc. to monitor the air pressure, temperature and other information of all tires in real time. It will issue an alarm when the air pressure, temperature or tire pressure monitoring system is abnormal, and provide prompts on the instrument side. Summary of the invention

[0004] To overcome the problems existing in the related art, the present disclosure provides a display method, device, vehicle, medium and program product.

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a display method, including: Receive tire data sent by tire sensors; Determining a target domain controller according to a type of application corresponding to the tire data, wherein different types of applications are installed through software development kits configured in different domain controllers, and the type is used to indicate an iterative update requirement of the application; Based on the tire data, tire information display is performed by the application installed in the target domain controller.

[0006] Optionally, when the application corresponding to the type representation does not have an iterative update requirement, the software development kit of the application is configured in a first domain controller, wherein the first domain controller is a domain controller that interacts with a driver layer; In the case that the application corresponding to the type representation has an iterative update requirement, the software development kit of the application is configured in a second domain controller, wherein the second domain controller is a domain controller that interacts with the application layer.

[0007] Optionally, the first domain controller is a domain controller configured with a Bluetooth digital key module, the Bluetooth digital key module is connected to a Bluetooth anchor point, and the second domain controller is a domain controller configured with a vehicle system.

[0008] Optionally, the application that does not have the iterative update requirement includes at least one of the following: a data analysis application, an alarm application, a diagnostic application, and an NVM application.

[0009] Optionally, the application program that meets the iterative update requirement includes at least one of the following: a tire pressure self-positioning learning application program, a tire data display application program, a self-triggered rescue application program, and a multi-level alarm prompt application program.

[0010] Optionally, the method further comprises: The upgrade data is received through the second domain controller, and the application configured in the second domain controller is updated according to the upgrade data.

[0011] Optionally, the performing tire information display by the application installed in the target domain controller according to the tire data includes: Transmitting the tire data to the target domain controller via a clock-synchronized bus, wherein different buses are clock-synchronized via different protocols; Based on the tire data, tire information display is performed by the application installed in the target domain controller.

[0012] Optionally, the performing tire information display by the application installed in the target domain controller according to the tire data includes: Obtaining a timestamp of a first type of signal carried in the tire data; According to the timestamp, the tire information corresponding to the first type of signal is displayed through the application installed in the target domain controller.

[0013] Optionally, the clock synchronization includes at least one of the following: Ethernet clock synchronization and local area network clock synchronization.

[0014] According to a second aspect of an embodiment of the present disclosure, there is provided a display device, including: A receiving module, configured to receive tire data sent by a tire sensor; a determination module configured to determine a target domain controller according to a type of an application corresponding to the tire data, wherein different types of the application are installed through software development kits configured in different domain controllers, and the type is used to indicate an iterative update requirement of the application; The display module is configured to perform tire information display through the application installed in the target domain controller according to the tire data.

[0015] According to a third aspect of an embodiment of the present disclosure, a vehicle is provided, comprising: processor; a memory for storing processor-executable instructions; The processor is configured to execute the executable instructions stored in the memory to implement the method described in any one of the first aspects.

[0016] According to a fourth aspect of an embodiment of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any one of the methods described in the first aspect are implemented.

[0017] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, which implements the steps of any one of the methods in the first aspect when executed by a processor.

[0018] The technical solution provided by the embodiment of the present disclosure may include the following beneficial effects: receiving tire data sent by a tire sensor; determining a target domain controller according to the type of application corresponding to the tire data, wherein different types of the application are installed through software development kits configured on different domain controllers, and the type is used to indicate the iterative update requirements of the application; and executing tire information display through the application installed in the target domain controller according to the tire data. In this way, different types of applications are deployed on different domain controllers, and they can be deployed on appropriate domain controllers according to the update frequency and importance of the application, thereby achieving optimal configuration of system resources. Each domain controller can undertake different numbers and types of applications according to its processing power and load conditions, thereby improving the overall performance and stability of the system. It not only solves the problem of integrating Bluetooth tire pressure with vehicle Bluetooth and achieves cost savings, but also greatly enhances the flexibility, maintainability and intelligence level of the system, bringing users a safer, more efficient and comfortable driving experience.

[0019] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0021] Figure 1 The figure is a flow chart of a display method according to an exemplary embodiment.

[0022] Figure 2 The figure is a schematic diagram showing the integration of Bluetooth tire pressure and digital key according to an exemplary embodiment.

[0023] Figure 3 It is a schematic diagram showing another integration of Bluetooth tire pressure and digital key according to an exemplary embodiment.

[0024] Figure 4 An implementation according to an exemplary embodiment is shown Figure 1 Flowchart of step S13 in FIG.

[0025] Figure 5 is a block diagram of a display device according to an exemplary embodiment.

[0026] Figure 6 is a block diagram of a vehicle according to an exemplary embodiment. DETAILED DESCRIPTION

[0027] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0028] It should be noted that all actions of acquiring signals, information or data in the present disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the device is located and with the authorization given by the owner of the corresponding device.

[0029] Before introducing a method involved in the present disclosure, let’s first introduce the technical problems existing in the relevant scenarios. In Bluetooth tire pressure monitoring, in order to save costs, a separate Bluetooth receiving module is not set as the receiving module of the tire Bluetooth sensor, but the receiving module of the tire Bluetooth sensor is shared with the Bluetooth receiving modules of other systems. However, for the tire pressure self-positioning learning function that occupies a large amount of system RAM (Random-Access Memory) and flash (Flash EEPROM Memory) resources, the selection requirements for the shared receiving module are high, which will increase the selection cost. For products that have already been selected, if you want to use this self-positioning learning function, it may be limited by the code space and cannot be integrated into the already designed car computer or Bluetooth digital key system, resulting in an inability to implement it.

[0030] Furthermore, if the existing in-vehicle digital key and vehicle computer module have been developed, the selection has been completed, and the remaining RAM and flash resources are insufficient and cannot be used directly. More importantly, if the tire pressure self-positioning learning function is integrated into the digital key module, when the tire pressure self-positioning learning function is undergoing functional iteration, OTA (Over-the-Air) is required to transmit the updated data to the digital key module.

[0031] However, the entire transmission path for transmitting the update data to the digital key module via OTA is long, and there may be a risk of interception or tampering. Especially in a public wireless network environment, the security of the data is even more difficult to guarantee. If the update data of the tire pressure self-positioning learning function is maliciously tampered with, the system may not work properly or even cause safety hazards. At the same time, there are problems with transmission delay and stability. Due to the long transmission path, network delays or instability may occur during the OTA upgrade process, resulting in the update data being unable to be transmitted to the digital key module in a timely and complete manner, thereby affecting the normal iteration of the tire pressure self-positioning learning function. In addition, if an interruption occurs during the transmission process, retransmission may be required, further extending the upgrade time.

[0032] Figure 1 is a flow chart of a display method according to an exemplary embodiment. Figure 1 As shown, the method can be applied to a vehicle, wherein the vehicle can be configured with multiple domain controllers, for example, the vehicle can be configured with a power domain controller, a chassis domain controller, a body domain controller, an autonomous driving domain controller, and a cockpit domain controller. The method includes the following steps.

[0033] In step S11 , tire data sent by a tire sensor is received.

[0034] The tire sensor may be an electronic device installed inside or outside the tire of the vehicle, and is used to monitor the tire's air pressure, temperature and other parameters in real time, and send these data to a receiving device of the vehicle by wireless means. For example, the tire sensor may include a tire pressure sensor.

[0035] Among them, tire data can be tire status information collected by tire sensors, including tire pressure, temperature, acceleration and battery voltage. Tire sensors can collect tire pressure, temperature, tire life, tread, load and other information, and display them through the vehicle computer. For example: when a tire leaks and suddenly drops, an alarm signal can be generated immediately; when the tire pressure signal is lost during driving, a tire pressure loss alarm signal can be generated; when the pressure inside the tire is too high, a high pressure threshold alarm signal can be generated; when the pressure inside the tire is too low, a low pressure threshold alarm signal can be generated; when the tire pressure temperature is too high, a high temperature alarm signal can be generated; when replacing the tire pressure sensor, the tire pressure position can be learned through the tire pressure self-positioning learning function without the need to hold the activation device.

[0036] The sampling period of the tire sensor in each mode is shown in the following table:

[0037] Table 1 In the disclosed embodiment, the tire sensor collects data such as tire pressure and temperature in real time through the built-in sensor element, and sends the data to the vehicle's Bluetooth receiving device through wireless Bluetooth communication technology. After receiving the data, the Bluetooth receiving device decodes it and transmits it to the corresponding processing unit.

[0038] For example: When the vehicle is driving, the tire sensor monitors the tire pressure in real time. When the pressure is lower than the preset value, the sensor sends this information to the vehicle's Bluetooth receiver module via Bluetooth. After receiving the data, the Bluetooth receiver module decodes it and transmits it to the vehicle's bus system.

[0039] In step S12, a target domain controller is determined according to the type of application corresponding to the tire data.

[0040] Among them, different types of applications are installed through software development kits configured in different domain controllers, and the type is used to represent the iterative update requirements of the application.

[0041] Among them, the application is a software program installed on the vehicle domain controller, which is used to process tire data and perform specific functions, such as tire information display, alarm prompts, etc. The domain controller is an independent computing unit in the vehicle electronic architecture, responsible for data processing and control within a specific area or functional domain. For example, the power domain controller, chassis domain controller, body domain controller, and cockpit domain controller mentioned above. The Software Development Kit (SDK) is used for programming interfaces, tools, library files, and documentation for developing applications for specific platforms or domain controllers. The SDK provides interfaces for interacting with hardware and underlying software, which can simplify the application development process.

[0042] In the disclosed embodiment, different domain controllers in the vehicle electronic architecture are responsible for different functional domains. According to the type of tasks that need to be processed by tire data, such as information display, alarm prompts, etc., and the iterative update requirements of the application, the most appropriate target domain controller is selected to process the data.

[0043] For example: Assume that there is an application for displaying tire information on the vehicle, and the application is installed on the cockpit domain controller. When the Bluetooth receiving module receives the data sent by the tire pressure sensor, it determines that the data should be processed by the cockpit domain controller according to the preset rules. Therefore, the data is sent to the application on the cockpit domain controller through the bus for processing.

[0044] In the disclosed embodiment, the types of applications can be divided into basic function applications and application function applications according to the iterative update requirements of the applications. Basic function applications are related to communication connections and basically do not change, while application function applications are related to algorithm user scenarios and are continuously iterated OTA as the functions are developed. The basic function application and the application function application are respectively integrated in the digital key module and the vehicle machine module, so that very little RAM and flash resources are occupied. The problem of insufficient RAM and flash resources of the domain controller can be solved, and costs can be saved in the selection process.

[0045] In the disclosed embodiments, different types of applications are installed through software development kits configured in different domain controllers. During the OTA upgrade process, only applications with iterative update requirements need to be updated in the domain controller, and applications without iterative update requirements do not need to be updated in the domain controller. During the update process of applications with iterative update requirements, applications without iterative update requirements can keep running. Therefore, both the size of the downloaded data packet and the time consumed for the iterative update will be shortened, reducing the risk of the update data not being able to be transmitted in a timely and complete manner due to network delays or instability, thereby reducing the risk of normal iteration of the tire pressure self-positioning learning function.

[0046] In step S13, tire information display is performed by the application installed in the target domain controller according to the tire data.

[0047] In the disclosed embodiment, after receiving the tire data, the application on the target domain controller processes and analyzes the data according to the preset logic and algorithm. The processing results (such as tire pressure value, temperature value, etc.) will be displayed on the vehicle display screen, which can be an instrument display screen or a central control display screen. The visualization of tire data is achieved, and the driver's perception of the vehicle status is improved.

[0048] For example: After receiving tire pressure data, the application running on the body domain controller parses and processes the data, and transmits the parsed and processed data to the application running on the cockpit domain controller through the CAN (Controller Area Network) bus. After receiving the tire pressure data, the application running on the cockpit domain controller further converts and compares it to obtain the processing result, and displays the processing result (such as low tire pressure, normal temperature, etc.) on the vehicle's dashboard or central control display. You can understand the current status of the tire by viewing the information on the display and take corresponding measures (such as inflating, checking the tire, etc.).

[0049] The above technical solution receives tire data sent by the tire sensor; determines the target domain controller according to the type of application corresponding to the tire data, wherein different types of applications are installed through software development kits configured on different domain controllers, and the type is used to indicate the iterative update requirements of the application; and executes tire information display through the application installed in the target domain controller according to the tire data. In this way, different types of applications are deployed on different domain controllers, and they can be deployed on appropriate domain controllers according to the update frequency and importance of the application, thereby achieving optimal configuration of system resources. Each domain controller can take on different numbers and types of applications according to its processing power and load conditions, thereby improving the overall performance and stability of the system. It not only solves the problem of integrating Bluetooth tire pressure with vehicle Bluetooth and achieves cost savings, but also greatly enhances the flexibility, maintainability and intelligence level of the system, bringing users a safer, more efficient and comfortable driving experience.

[0050] Optionally, when the application corresponding to the type representation does not have an iterative update requirement, the software development kit of the application is configured in a first domain controller, wherein the first domain controller is a domain controller that interacts with a driver layer.

[0051] Among them, in the vehicle electronic architecture, the driver layer is the software layer that directly interacts with the vehicle hardware and is responsible for controlling the operation of the hardware devices. The driver layer software usually includes device drivers, underlying communication protocol stacks, etc.

[0052] In the disclosed embodiment, for applications that do not require iterative updates, these applications have basic functions such as parsing. In order to reduce system complexity and improve stability, their software development kits are configured on the domain controller that interacts with the driver layer. Such domain controllers can be responsible for controlling the underlying hardware devices of the vehicle, such as sensors, actuators, etc. Placing applications that do not require updates on such domain controllers can reduce the risks and complexity brought about by system updates.

[0053] For example, suppose there is an application for parsing data and performing protocol conversion. This application does not need to be updated iteratively. The SDK of this application can be configured on the domain controller that interacts with the driver layer. This domain controller may also be responsible for controlling other underlying hardware devices. By placing the application here, it can ensure that the communication between it and these devices is more stable and efficient.

[0054] In the case that the application corresponding to the type representation has an iterative update requirement, the software development kit of the application is configured in a second domain controller, wherein the second domain controller is a domain controller that interacts with the application layer.

[0055] Compared with the driver layer, the application layer is a software layer that interacts with users or performs specific functions. The application layer software usually includes various application programs, user interfaces, data processing algorithms, etc.

[0056] In the embodiments of the present disclosure, for applications that require frequent iterations and updates, in order to support rapid functional iterations and user experience optimization, their software development kits (SDKs) are usually configured on domain controllers that interact with the application layer. Such domain controllers are usually responsible for processing user input, displaying information, performing advanced data processing, and other functions. Placing applications that require frequent updates on such domain controllers can make software updates and upgrades more convenient.

[0057] For example, suppose there is an application that provides tire self-positioning function. This application needs to be updated frequently to support the improvement of the accuracy of self-positioning learning. The SDK of this application can be configured on the domain controller that interacts with the application layer. This domain controller can also be responsible for controlling user interface devices such as vehicle systems and display screens. By placing the application here, it can be ensured that it can quickly respond to user input and display requirements, while supporting rapid function iteration and user experience optimization.

[0058] Optionally, the first domain controller is a domain controller configured with a Bluetooth digital key module, the Bluetooth digital key module is connected to a Bluetooth anchor point, and the second domain controller is a domain controller configured with a vehicle system.

[0059] The Bluetooth anchor point is a fixed point or interface inside the vehicle for communicating with Bluetooth devices (such as Bluetooth digital key modules). It can be located in the center of the vehicle or in the four corners of the vehicle, for example, the front left, rear left, front right and rear right of the vehicle, to ensure that the Bluetooth signal can cover the entire interior of the vehicle.

[0060] Among them, the In-vehicle Infotainment System (IVI system) is a multimedia entertainment and information system installed in the car. It integrates multiple functions to enhance the driving experience, provide navigation services, enhance in-car entertainment, and ensure convenient communication.

[0061] See Table 2 and Figure 2 As shown, the application functions in different domain controllers can be distinguished by the following system components and functions:

[0062] Table 2 In the disclosed embodiment, the first domain controller may be, for example, a vehicle body domain controller, and the second domain controller may be a cockpit domain controller. The Bluetooth digital key module may not only receive a Bluetooth key signal sent by a digital vehicle key through a Bluetooth anchor point, but may also receive tire data sent by a sensor configured on a vehicle tire through a Bluetooth anchor point.

[0063] In the disclosed embodiment, the first domain controller is configured as a domain controller including a Bluetooth digital key module. The Bluetooth digital key module realizes wireless communication with other parts of the vehicle by connecting to a Bluetooth anchor point. This reuse of the Bluetooth digital key module as a Bluetooth receiving module can reduce costs and enable the Bluetooth digital key module to interact and work with other vehicle systems more conveniently.

[0064] For example: Assume that a vehicle is equipped with a Bluetooth digital key module for keyless entry and start. This module is configured on the first domain controller and connected to the vehicle's Bluetooth anchor point. When a user approaches the vehicle with a key with Bluetooth function, the Bluetooth digital key module can communicate with the key through the Bluetooth anchor point to verify the user's identity and unlock the vehicle. This configuration improves the safety and convenience of the vehicle. At the same time, this module also receives tire data sent by the tire sensor in real time.

[0065] Alternatively, see Figure 3 As shown, the application that does not have the iterative update requirement includes at least one of the following: a data analysis application, an alarm application, a diagnostic application, and an NVM application.

[0066] The data analysis application is responsible for receiving, analyzing and processing tire data from tire sensors. These data include temperature, tire pressure, etc. The data analysis application converts these raw data for use by other applications or systems.

[0067] Alarm applications are applications that monitor tire conditions and trigger alarms when abnormal conditions are detected. These abnormal conditions may include tire overheating, low tire pressure, etc. Alarm applications alert the driver to the vehicle status by emitting sound, light or text prompts.

[0068] Diagnostic Application An application used to detect, analyze and record tire failures to obtain fault codes, sensor data and system status information. The diagnostic application helps technicians quickly locate and solve tire problems.

[0069] NVM (Node Version Manager) applications are applications that interact with the vehicle's non-volatile memory (such as EEPROM, Flash memory). These applications are used to store and retrieve tire configuration data, calibration parameters, fault records, etc.

[0070] In the disclosed embodiment, the application programs that do not have the iterative update requirements are responsible for the basic functions and safety monitoring of the vehicle, such as data analysis, alarm, and diagnosis. Since their functions are relatively fixed and have high real-time requirements, they usually do not need to be updated. For example, the data analysis application program can analyze the data from the sensor in real time to ensure accurate monitoring of the vehicle status; the alarm application program can immediately trigger an alarm when an abnormal situation is detected to alert the driver.

[0071] Alternatively, see Figure 3 As shown, the application program that meets the iterative update requirement includes at least one of the following: a tire pressure self-positioning learning application program, a tire data display application program, a self-triggered rescue application program, and a multi-level alarm prompt application program.

[0072] Among them, the tire pressure self-positioning learning application is an application that can automatically identify and record the position of each tire of the vehicle. After the vehicle changes tires or tire positions, the application can relearn and update tire position information to ensure the accuracy of the tire pressure monitoring system. This type of application usually needs to be updated frequently to adapt to different tire configurations and vehicle conditions.

[0073] Tire data display applications are applications responsible for displaying tire status information (such as tire pressure, temperature). They usually communicate with the vehicle's tire pressure monitoring system (TPMS) to obtain real-time data and display this information in graphical or text form on the vehicle's display. Since tire data may change as the vehicle is used, tire data display applications need to be updated regularly to keep the information accurate.

[0074] Self-triggering rescue applications are applications that can automatically trigger rescue services when a vehicle breakdown or emergency is detected. These applications are usually integrated with the vehicle's emergency call system or a third-party rescue service provider, and can automatically send a rescue request when the vehicle is involved in an accident, breaks down, or requires emergency repairs. Because the demand for rescue services may change over time and location, self-triggering rescue applications need to be updated regularly to adapt to these changes.

[0075] Multi-level alarm applications are applications that can provide different levels of alarms based on the severity of vehicle faults. They are usually able to distinguish between minor faults, serious faults, and emergency faults, and notify the driver through different sounds, lights, or text prompts. This type of application needs to be updated regularly to ensure the accuracy and effectiveness of the alarm prompts, and also needs to adapt to different driver preferences and vehicle configurations. For example, for tire pressure alarms, an alarm is issued when the tire pressure is 75% of the calibrated value, an alarm is issued when the tire pressure is 85% of the calibrated value, and a red tire pressure alarm is issued when the tire pressure reaches 75% of the calibrated value.

[0076] In the disclosed embodiment, the application with the iterative update requirement needs to adapt to different tire configurations, driver preferences and emergency rescue requirements, and therefore needs to be frequently updated to maintain the accuracy and effectiveness of the functions. For example, the tire pressure self-positioning learning application can automatically update the tire position information to ensure the accuracy of the tire pressure monitoring system; the tire data display application can be regularly updated to display the latest tire status information; the self-trigger rescue application can update the rescue service provider's contact information and rescue process to ensure timely and effective rescue services in emergency situations.

[0077] Optionally, the method further comprises: The upgrade data is received through the second domain controller, and the application configured in the second domain controller is updated according to the upgrade data.

[0078] Among them, upgrade data refers to the file package used to update the software application in the domain controller, which usually contains new program code, configuration files, resource files, etc. This data may come from the cloud background of the vehicle manufacturer.

[0079] In the disclosed embodiment, the upgrade data can be transmitted from the cloud backend to the vehicle via wireless communication. The upgrade data is encrypted and signed to ensure its integrity and source reliability. It may also need to be compressed before being transmitted to the domain controller to save bandwidth and time. After receiving the data, the domain controller verifies its integrity and signature, then decompresses and prepares to apply the update. The update process may involve operations such as replacing old files, adding new files, or modifying configuration files.

[0080] In this way, the software library of the Bluetooth tire pressure receiving module can be disassembled into a basic library and an application library, which can be integrated into the digital key and the vehicle system respectively, solving the integration problem of Bluetooth tire pressure and vehicle Bluetooth. An independent Bluetooth receiving module can be saved as a receiving device for the Bluetooth tire pressure sensor. On the basis of reusing the Bluetooth anchor point of the whole vehicle, the software can be disassembled into a basic library and an application library, and the application library can be continuously upgraded along with the vehicle system.

[0081] Alternatively, see Figure 4 As shown, in step S13, the tire information display is performed by the application installed in the target domain controller according to the tire data, including: In step S131, the tire data is transmitted to the target domain controller via the clock-synchronized bus.

[0082] Wherein, different buses perform clock synchronization through different protocols.

[0083] Clock synchronization is the process of adjusting the time between different domain controllers to ensure that their time bases are consistent. In the vehicle's internal network, clock synchronization can ensure the accuracy of data timestamps and coordinate operations between different systems.

[0084] The bus is a channel for transmitting data in the vehicle's internal network. Different buses may use different communication protocols, such as CAN (Controller Area Network), LIN (Local Interconnect Network) or MOST (Media Oriented Systems Transport).

[0085] In the disclosed embodiment, the tire data is first collected and prepared for transmission. To ensure the accuracy and consistency of the data, different bus systems perform clock synchronization through their respective protocols. The clock synchronization process may involve operations such as sending time synchronization messages and adjusting the local clock to match the reference clock. After the clock synchronization is completed, the tire data is packaged and sent to the bus where the target domain controller is located. Otherwise, the bus delay cannot exceed 100ms.

[0086] In step S132, tire information display is performed through the application installed in the target domain controller according to the tire data.

[0087] In the disclosed embodiment, after receiving the tire data, the target domain controller processes and displays it through the application installed thereon. The application first parses the received data packet and extracts the tire data (such as pressure, temperature, etc.). Then, according to the preset logic and interface design, the data is displayed on the vehicle dashboard or infotainment system in an intuitive manner (such as charts, numbers or warning lights). This process may also involve operations such as data verification, filtering and formatting to ensure the accuracy of the display.

[0088] Optionally, in step S132, the performing tire information display through the application installed in the target domain controller according to the tire data includes: A timestamp of a first type of signal carried in the tire data is obtained.

[0089] The first type of signal is a signal with a high latency requirement, such as tire pressure, temperature, wheel speed, etc. The second type of signal is a signal with a low latency requirement, such as battery voltage signal. The timestamp is used to indicate the exact moment when the tire status data is captured by the sensor.

[0090] In the disclosed embodiment, when the tire sensor collects data, it will simultaneously record a timestamp to indicate the time when the data was captured. This timestamp is usually packaged with the data and sent to the target domain controller. After receiving the data packet, the application of the target domain controller first parses the timestamp information in the data.

[0091] According to the timestamp, the tire information corresponding to the first type of signal is displayed through the application installed in the target domain controller.

[0092] In the disclosed embodiment, the application obtains the first type of signal (such as tire pressure) and its corresponding timestamp, and displays this information according to the preset logic and interface design. The display method may include displaying the pressure value in digital form on the dashboard, or displaying the pressure status in a graphical manner (such as a bar chart or dashboard). In addition, the application may also sort and display the data according to the timestamp to ensure that the user sees the latest and most accurate information. By obtaining the timestamps carried in the tire data and performing the tire information display corresponding to the first type of signal according to these timestamps, the timing, accuracy and user-friendliness of the data are ensured.

[0093] Optionally, the clock synchronization includes at least one of the following: Ethernet clock synchronization and local area network clock synchronization.

[0094] In the disclosed embodiment, as shown in Table 3, the tire pressure, temperature, acceleration, and battery voltage can all be sampled and adjusted within the following time periods:

[0095] Table 3 In the disclosed embodiment, since the data reporting period of the tire pressure sensor is usually 60 seconds per packet, 1 second in alarm mode, and can be set to 500ms at the fastest, in order to ensure that data between domain controllers can be synchronized in time, the message period on the CAN bus cannot be less than 200ms. By increasing 1pps (Pulses Per Second) for LAN clock synchronization, the CAN clock synchronization problem can be solved.

[0096] In the disclosed embodiment, Ethernet clock synchronization is performed through GPTP (Generalized Precision Time Protocol). As an extended and optimized version of PTP (Precision Time Protocol), GPTP can rely on the physical layer of network devices to implement nanosecond timestamp marking and reduce delay jitter introduced by software. In this way, multiple clock domains can be divided in a complex network environment, which can solve the clock synchronization problem of two domain controllers.

[0097] The present disclosure also provides a display device. Figure 5 As shown, including: The receiving module 510 is configured to receive tire data sent by the tire sensor; The determination module 520 is configured to determine a target domain controller according to a type of an application corresponding to the tire data, wherein different types of the application are installed through software development kits configured in different domain controllers, and the type is used to indicate an iterative update requirement of the application; The display module 530 is configured to display tire information through the application installed in the target domain controller according to the tire data.

[0098] Optionally, when the application corresponding to the type representation does not have an iterative update requirement, the software development kit of the application is configured in a first domain controller, wherein the first domain controller is a domain controller that interacts with a driver layer; In the case that the application corresponding to the type representation has an iterative update requirement, the software development kit of the application is configured in a second domain controller, wherein the second domain controller is a domain controller that interacts with the application layer.

[0099] Optionally, the first domain controller is a domain controller configured with a Bluetooth digital key module, the Bluetooth digital key module is connected to a Bluetooth anchor point, and the second domain controller is a domain controller configured with a vehicle system.

[0100] Optionally, the application that does not have the iterative update requirement includes at least one of the following: a data analysis application, an alarm application, a diagnostic application, and an NVM application.

[0101] Optionally, the application program that meets the iterative update requirement includes at least one of the following: a tire pressure self-positioning learning application program, a tire data display application program, a self-triggered rescue application program, and a multi-level alarm prompt application program.

[0102] Optionally, the device further includes: an upgrade module configured to: The upgrade data is received through the second domain controller, and the application configured in the second domain controller is updated according to the upgrade data.

[0103] Optionally, the display module 530 is configured as follows: Transmitting the tire data to the target domain controller via a clock-synchronized bus, wherein different buses are clock-synchronized via different protocols; Based on the tire data, tire information display is performed by the application installed in the target domain controller.

[0104] Optionally, the display module 530 is configured as follows: Obtaining a timestamp of a first type of signal carried in the tire data; According to the timestamp, the tire information corresponding to the first type of signal is displayed through the application installed in the target domain controller.

[0105] Optionally, the clock synchronization includes at least one of the following: Ethernet clock synchronization and local area network clock synchronization.

[0106] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0107] The present disclosure also provides a vehicle, including: processor; a memory for storing processor-executable instructions; The processor is configured to execute the executable instructions stored in the memory to implement the method described in any one of the aforementioned embodiments.

[0108] The embodiments of the present disclosure further provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method described in any one of the aforementioned embodiments are implemented.

[0109] The present disclosure also provides a computer program product, including a computer program, which implements the steps of any one of the methods in the aforementioned embodiments when executed by a processor.

[0110] Figure 6 6 is a block diagram of a vehicle 600 according to an exemplary embodiment. For example, the vehicle 600 may be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicles. The vehicle 600 may be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.

[0111] Reference Figure 6 , the vehicle 600 may include various subsystems, for example, an infotainment system 610, a perception system 620, a decision control system 630, a drive system 640, and a computing platform 650. The vehicle 600 may also include more or fewer subsystems, and each subsystem may include multiple components. In addition, each subsystem and each component of the vehicle 600 may be interconnected by wire or wireless means.

[0112] In some embodiments, the infotainment system 610 may include a communication system, an entertainment system, and a navigation system, etc.

[0113] The perception system 620 may include several sensors for sensing information about the environment around the vehicle 600. For example, the perception system 620 may include a global positioning system (the global positioning system may be a GPS system, or a Beidou system or other positioning systems), an inertial measurement unit (IMU), a laser radar, a millimeter wave radar, an ultrasonic radar, and a camera.

[0114] The decision control system 630 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.

[0115] The drive system 640 may include components that provide powered motion for the vehicle 600. In one embodiment, the drive system 640 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of an internal combustion engine, an electric motor, and an air compression engine. The engine is capable of converting energy provided by the energy source into mechanical energy.

[0116] Some or all functions of the vehicle 600 are controlled by a computing platform 650. The computing platform 650 may include at least one processor 651 and a memory 652, and the processor 651 may execute instructions 653 stored in the memory 652.

[0117] The processor 651 may be any conventional processor, such as a commercially available CPU. The processor may also include a graphics processor (Graphic Process Unit, GPU), a field programmable gate array (Field Programmable Gate Array, FPGA), a system on chip (System on Chip, SOC), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC) or a combination thereof.

[0118] The memory 652 may be implemented by any type of volatile or nonvolatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0119] In addition to the instructions 653 , the memory 652 may also store data, such as road maps, route information, and data such as the location, direction, and speed of the vehicle. The data stored in the memory 652 may be used by the computing platform 650 .

[0120] In the embodiment of the present disclosure, the processor 651 may execute the instruction 653 to complete all or part of the steps of the above-mentioned display method.

[0121] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

[0122] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A display method, characterized in that: include: Receive tire data sent by tire sensors; Determining a target domain controller according to a type of application corresponding to the tire data, wherein different types of applications are installed through software development kits configured in different domain controllers, and the type is used to indicate an iterative update requirement of the application; Based on the tire data, tire information display is performed by the application installed in the target domain controller.

2. The method according to claim 1, characterized in that: In the case that the application corresponding to the type representation does not have an iterative update requirement, configuring the software development kit of the application in a first domain controller, wherein the first domain controller is a domain controller that interacts with a driver layer; In the case that the application corresponding to the type representation has an iterative update requirement, the software development kit of the application is configured in a second domain controller, wherein the second domain controller is a domain controller that interacts with the application layer.

3. The method according to claim 2, characterized in that The first domain controller is a domain controller configured with a Bluetooth digital key module, and the Bluetooth digital key module is connected to a Bluetooth anchor point. The second domain controller is a domain controller configured with a vehicle system.

4. The method according to claim 2, characterized in that: The application program that does not have the iterative update requirement includes at least one of the following: a data analysis application program, an alarm application program, a diagnostic application program, and an NVM application program.

5. The method according to claim 2, characterized in that: The application program that meets the iterative update requirement includes at least one of the following: a tire pressure self-positioning learning application program, a tire data display application program, a self-triggering rescue application program, and a multi-level alarm prompt application program.

6. The method according to claim 2, characterized in that The method further comprises: The upgrade data is received through the second domain controller, and the application configured in the second domain controller is updated according to the upgrade data.

7. The method according to any one of claims 1 to 6, characterized in that The step of displaying tire information by the application installed in the target domain controller according to the tire data includes: Transmitting the tire data to the target domain controller via a clock-synchronized bus, wherein different buses are clock-synchronized via different protocols; Based on the tire data, tire information display is performed by the application installed in the target domain controller.

8. The method according to claim 7, characterized in that The step of displaying tire information by the application installed in the target domain controller according to the tire data includes: Obtaining a timestamp of a first type of signal carried in the tire data; According to the timestamp, the tire information corresponding to the first type of signal is displayed through the application installed in the target domain controller.

9. The method according to claim 7, characterized in that: The clock synchronization includes at least one of the following: Ethernet clock synchronization and local area network clock synchronization.

10. A display device, characterized in that: include: A receiving module, configured to receive tire data sent by a tire sensor; a determination module configured to determine a target domain controller according to a type of an application corresponding to the tire data, wherein different types of the application are installed through software development kits configured in different domain controllers, and the type is used to indicate an iterative update requirement of the application; The display module is configured to perform tire information display through the application installed in the target domain controller according to the tire data.

11. A vehicle, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to execute the executable instructions stored in the memory to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

13. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 9.

Images