Vehicle Kanban data processing method, electronic equipment and readable storage medium

Abstract

The embodiment of the invention discloses a vehicle billboard data processing method, electronic equipment and a readable storage medium. According to the method, the electronic control unit of the vehicle locally processes the vehicle data to generate the billboard data, directly responds to the query request of the target equipment, and transmits the billboard data to the target equipment to be displayed. The problems of interruption and distortion in the transmission process of the vehicle data between the vehicle and the remote terminal equipment are effectively avoided, the reliability and the accuracy of the billboard data can be improved, the network bandwidth occupation and the resource consumption are reduced, and the communication traffic and the traffic cost are effectively reduced.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method for processing vehicle dashboard data, an electronic device, and a readable storage medium. Background Technology

[0002] Real-time monitoring of vehicle operation relies on the collection and analysis of various data. Dashboard data serves as a key indicator that intuitively reflects the vehicle's status, such as total mileage, average fuel consumption, number of speeding violations, and periodic failure rate. However, traditional methods of processing dashboard data are prone to data acquisition failures or data loss, resulting in poor accuracy of the dashboard data. Summary of the Invention

[0003] To address the shortcomings of existing technologies, this application provides a method for processing vehicle dashboard data, an electronic device, and a readable storage medium, which can improve the reliability and accuracy of dashboard data and reduce network bandwidth usage and resource consumption.

[0004] Firstly, this application provides a method for processing vehicle dashboard data, which is applied to the electronic control unit of a vehicle. The method includes:

[0005] The collected vehicle data is processed to obtain vehicle dashboard data; In response to a request from the target device to query dashboard data, the dashboard data is sent to the target device for display.

[0006] Secondly, this application also provides a method for processing vehicle dashboard data, which is applied to a target device, the method comprising: The configuration information of the vehicle's dashboard data is sent to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller. Send a request command to the gateway controller or domain controller to query dashboard data; Receive dashboard data sent by the gateway controller or domain controller, and display the dashboard data.

[0007] Thirdly, this application also provides a vehicle dashboard data processing device applied to the vehicle's electronic control unit, the device comprising: The processing unit is used to process the collected vehicle data to obtain vehicle dashboard data. The first sending unit is used to respond to the request command from the target device to query the dashboard data and send the dashboard data to the target device for display.

[0008] Fourthly, this application also provides a vehicle dashboard data processing apparatus applied to a target device, the apparatus comprising: The second sending unit is used to send the configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit in order to configure the gateway controller or domain controller. The third sending unit is used to send a request command to the gateway controller or domain controller to query dashboard data; The display unit is used to receive dashboard data sent by the gateway controller or domain controller and display the dashboard data.

[0009] Fifthly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the vehicle signage data processing method as provided in the first or second aspect above.

[0010] Sixthly, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the vehicle signboard data processing method provided in the first or second aspect.

[0011] In a seventh aspect, embodiments of this application also provide a computer program product, including a computer program or instructions, wherein the computer program or instructions are executed by a processor using the method for processing vehicle signage data provided in the first or second aspect.

[0012] The vehicle dashboard data processing method provided in this application processes vehicle data locally in the vehicle's electronic control unit to generate dashboard data, and directly responds to the query request of the target device by transmitting the dashboard data to the target device for display. This effectively avoids the problems of interruption and distortion of vehicle data during transmission between the vehicle and the remote terminal device, improves the reliability and accuracy of the dashboard data, reduces network bandwidth usage and resource consumption, and effectively reduces communication volume and traffic costs. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is an application scenario diagram of the vehicle dashboard data processing method provided in the embodiments of this application; Figure 2 A schematic diagram of the first process of a method for processing vehicle dashboard data provided in an embodiment of this application; Figure 3A second flowchart illustrating the method for processing vehicle dashboard data provided in an embodiment of this application; Figure 4 A schematic block diagram of a vehicle dashboard data processing device provided in an embodiment of this application; Figure 5 A schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0015] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0017] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0018] It should also be further understood that the term “and / or” as used in this application specification and the appended claims can be understood as any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0019] Furthermore, in this application, unless otherwise explicitly specified or limited in the embodiments, the terms "installation," "connection," "joining," and "fixing" appearing in the embodiments should be interpreted broadly. For example, a connection can be a fixed connection, a detachable connection, or an integral part; it can also be a mechanical connection, an electrical connection, etc. Of course, it can also be a direct connection, or an indirect connection through an intermediate medium, or it can be the internal communication between two components, or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific implementation.

[0020] In related technologies, when viewing vehicle dashboard data, it is usually necessary for the backend to remotely connect to the vehicle, obtain the signal values ​​of each ECU through the vehicle's TBOX, and then the backend uses an algorithm to calculate the dashboard data.

[0021] However, this method is highly dependent on the external network environment. In areas with weak signal coverage or in scenarios with network fluctuations, the original data transmission is prone to interruption or loss, resulting in incomplete or distorted dashboard data, which cannot meet the stringent real-time requirements of vehicle diagnosis and maintenance.

[0022] Meanwhile, the backend needs to continuously receive and process massive amounts of raw vehicle signals, which not only significantly increases communication bandwidth usage but also drives up traffic costs and system resource consumption, placing an additional burden on the vehicle communication network. Especially in complex operating conditions with frequent signal exchanges within the vehicle, this mode is difficult to adapt to the needs of efficient data management in unstable network environments.

[0023] To address this, this application provides a method for processing vehicle dashboard data. This method generates dashboard data by processing vehicle data locally in the vehicle's electronic control unit and directly responding to query requests from the target device. The dashboard data is then transmitted to the target device for display. This effectively avoids interruptions and distortions in the transmission of vehicle data between the vehicle and the remote terminal device, improving the reliability and accuracy of the dashboard data, reducing network bandwidth usage and resource consumption, and effectively lowering communication volume and traffic costs.

[0024] Please see Figure 1 , Figure 1 This diagram illustrates an application scenario for the vehicle dashboard data processing method provided in this embodiment. The vehicle dashboard data processing method provided in this embodiment can be applied to the Electronic Control Unit (ECU) 111 of vehicle 110 and the target device 120. The target device can be a remote terminal device, a vehicle-mounted terminal, or a vehicle diagnostic device. Specifically, the vehicle dashboard data processing method can be applied to the gateway controller 1111 or the domain controller 1112 of the ECU 111.

[0025] It should be noted that the application scenarios described in the following embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0026] The following is a detailed explanation of the processing method for the vehicle dashboard data provided in this application.

[0027] like Figure 2 As shown, the method for processing vehicle dashboard data is applied in the electronic control unit, and the method includes the following steps S210~S220.

[0028] S210. Process the collected vehicle data to obtain the vehicle's dashboard data; S220. In response to the request instruction from the target device to query the dashboard data, the dashboard data is sent to the target device for display.

[0029] In this embodiment, the Electronic Control Unit (ECU) can be understood as an electronic device in a vehicle used to control specific functions or systems. The ECU integrates a processor, memory, and communication interface, enabling it to acquire vehicle sensor signals in real time, execute preset control logic, and interact with other ECUs. In this application, the ECU can be configured to process vehicle data to generate dashboard data and send the dashboard data.

[0030] Vehicle data can be understood as the raw signals or parameters generated in real time by various sensors or ECUs during vehicle operation, such as vehicle speed, engine speed, throttle opening, and temperature. Vehicle data reflects the real-time operating status of the vehicle.

[0031] Kanban data can be understood as aggregated data obtained by processing, calculating, and aggregating collected vehicle data, which can intuitively reflect the overall operating status or specific performance indicators of the vehicle. Examples include total mileage, average fuel consumption, number of speeding violations, and failure rate.

[0032] The target device can be understood as a user terminal or system that sends query requests to the vehicle's electronic control unit and receives dashboard data for display. The target device may include, but is not limited to, vehicle diagnostic equipment, in-vehicle terminals, or remote monitoring equipment.

[0033] A request instruction can be understood as a command sent by the target device to the electronic control unit to request specific dashboard data. Request instructions typically include the intent of the request and information on the possible range or type of data.

[0034] Specifically, in the process of processing vehicle dashboard data in the electronic control unit (ECU) of this application, the ECU can be the vehicle's gateway controller or domain controller, which has the ability to communicate with other ECUs within the vehicle and can acquire various types of raw vehicle data. By integrating the dashboard data processing logic and storage functions into the vehicle's internal ECU, this application ensures the real-time performance and stability of data processing and avoids dependence on external network environments.

[0035] After collecting vehicle data, the electronic control unit can process the collected vehicle data to obtain the vehicle dashboard data.

[0036] For example, the electronic control unit can pre-store a fixed set of data processing algorithms and Kanban data item definitions. When the vehicle is running, the electronic control unit will periodically collect specific raw vehicle data from the vehicle's internal bus (such as the CAN bus), such as vehicle speed signals, engine speed signals, etc.

[0037] Subsequently, the collected raw data will be calculated and aggregated according to a preset algorithm to generate corresponding dashboard data, such as calculating the vehicle's cumulative mileage, average speed, or the number of speeding incidents within a specific time period.

[0038] Meanwhile, the generated dashboard data is stored in the memory of the electronic control unit and updated periodically.

[0039] Furthermore, in response to a request from a target device to query dashboard data, when the target device needs to obtain the vehicle's dashboard data, it sends a query command to the electronic control unit. This query command can be a simple, general query instruction that directs the electronic control unit to send all currently stored dashboard data. Upon receiving this command, the electronic control unit recognizes the query request for dashboard data and prepares to send the data.

[0040] Furthermore, during the process of sending dashboard data to the target device, the electronic control unit (ECU) can send the generated dashboard data to the target device after responding to a query command. Data transmission can be conducted through the communication link established between the ECU and the target device.

[0041] For example, the electronic control unit can use a preset universal communication protocol to package all available dashboard data into data frames and transmit them to the target device. After receiving the dashboard data, the target device can parse and format it, and finally present it on the device's display interface for the user to view.

[0042] In this application, by integrating the vehicle's dashboard data processing function into the vehicle's internal electronic control unit, localized processing of vehicle data and generation of dashboard data are achieved. This avoids data loss or inaccuracy caused by poor network conditions, ensuring the accuracy and reliability of the dashboard data. Furthermore, this application only sends dashboard data upon receiving a query request from the target device, significantly reducing the communication volume and bandwidth costs required for continuously transmitting large amounts of raw vehicle data, thus improving resource utilization.

[0043] In some embodiments, processing the collected vehicle data to obtain the vehicle dashboard data includes: acquiring configuration information of the dashboard data based on the target device; and collecting and processing the vehicle data based on the configuration information to obtain the dashboard data.

[0044] In this embodiment, during the process of obtaining the configuration information of the dashboard data based on the target device, parameters defining the rules for generating the dashboard data can be obtained from an external device. The configuration information may include the unique identifier, name, calculation algorithm, relevant electronic control unit signals, unit, statistical period, and frequency of the dashboard data.

[0045] Specifically, the electronic control unit (ECU) can receive configuration information directly sent by the target device. For example, the target device can be a diagnostic device, which can transmit configuration information directly to the ECU through a diagnostic interface; or the target device can be a remote device, which transmits configuration information to the ECU through the vehicle's TBOX module.

[0046] In addition, the electronic control unit can also proactively send a request to the target device to obtain specific configuration information, and then receive the configuration information sent by the target device in response to the request. This method is suitable for situations where the electronic control unit needs to dynamically update or verify configuration information, such as when the system starts up or when a specific event is triggered.

[0047] Furthermore, during the process of collecting and processing vehicle data based on configuration information, the electronic control unit can be guided to perform actual vehicle data collection and calculation based on the acquired configuration information to generate the final dashboard data.

[0048] Specifically, the electronic control unit (ECU) can collect relevant vehicle data in real time based on the collection frequency and data source (e.g., a specific ECU signal) defined in the configuration information. Subsequently, the ECU can calculate and process the real-time collected data according to the algorithm specified in the configuration information to generate dashboard data. For example, the configuration information might specify collecting the vehicle speed signal every 100ms and calculating the number of speeding violations; the ECU will then execute this rule.

[0049] In addition, the electronic control unit can also collect the required vehicle data in batches according to the data items listed in the configuration information within a preset period (e.g., every minute, every hour). After the collection period ends, the batch data is processed and calculated uniformly to generate or update dashboard data. For example, the configuration information can be used to specify that the total mileage is calculated once a day, and the electronic control unit summarizes the mileage data and calculates it at the end of the day.

[0050] In this application, the electronic control unit is configured using the configuration information provided by the target device, thereby enabling flexible definition and generation of vehicle dashboard data. This makes the dashboard data generation process no longer fixed, but dynamically adjustable and customized according to different target devices (such as diagnostic devices or remote devices) or different application scenarios.

[0051] For example, diagnostic equipment can be configured with detailed dashboard data for fault diagnosis, while remote equipment can be configured with summary dashboard data for vehicle operation monitoring.

[0052] This application avoids the problems of network instability, data loss, and increased communication and bandwidth costs associated with traditional solutions that rely on remotely acquiring large amounts of raw vehicle data for calculations within the vehicle, by collecting and processing data based on configuration information inside the vehicle. Simultaneously, the electronic control unit directly generates and updates dashboard data within the vehicle, ensuring the real-time nature, accuracy, and reliability of the data, significantly reducing the burden on external communication, and improving the efficiency and adaptability of the entire system.

[0053] In some embodiments, generating the configuration information for the dashboard data based on the target device includes: acquiring the configuration information sent by the target device and writing the configuration information into the electronic control unit.

[0054] In this embodiment, during the process of acquiring configuration information sent by the target device, the electronic control unit can receive data from the external target device used to define the rules and parameters for generating dashboard data. Specifically, the electronic control unit can establish a communication connection with the target device, for example, through a vehicle diagnostic interface or a wireless communication module, to receive the configuration information transmitted by the target device.

[0055] Simultaneously, the electronic control unit can also passively listen for configuration information broadcasts or point-to-point transmissions from target devices. For example, when a diagnostic device is connected to a vehicle, it proactively sends preset dashboard data configuration information to the electronic control unit.

[0056] In addition, the electronic control unit can also proactively request the target device to obtain the latest configuration information. For example, when starting up or detecting an update to the configuration information, the electronic control unit may request to download the configuration information from a remote server or in-vehicle terminal.

[0057] Furthermore, during the process of writing configuration information to the electronic control unit (ECU), the received configuration information can be stored in the ECU's internal memory for later use in processing vehicle data. Specifically, after receiving the configuration information, the ECU can parse and verify it to ensure the integrity and validity of the data.

[0058] Meanwhile, the verified configuration information can be directly written to the non-volatile memory (such as EEPROM or Flash memory) of the electronic control unit to ensure that the configuration information can be permanently saved even after the vehicle is powered off.

[0059] In addition, during the writing process, the electronic control unit can use mechanisms such as redundant storage, checksums, or cyclic redundancy check to ensure the reliability of data storage.

[0060] In one implementation, the configuration information can be temporarily stored and quickly accessed in the volatile memory (such as RAM) of the electronic control unit first, and then hardened to non-volatile memory after confirming that the configuration is valid and the system is running stably. This method allows for testing or rollback operations before formal writing, thereby improving the flexibility and security of configuration updates.

[0061] In this application, the electronic control unit can directly obtain and store the configuration information of the dashboard data from the target device, thereby ensuring the reliability of the source and the persistence of the storage of the configuration information, avoiding the risk of data loss or tampering that may be introduced in the intermediate links, and significantly improving the accuracy and real-time performance of the configuration information. As a result, the electronic control unit can efficiently process the collected vehicle data based on the latest and correct configuration parameters and generate accurate dashboard data. This not only improves the reliability and efficiency of dashboard data generation, but also provides stronger autonomy and flexibility for vehicle internal data processing, reduces the dependence on continuous interaction with external systems, and thus optimizes the overall system performance.

[0062] In some embodiments, obtaining the configuration information sent by the target device and writing the configuration information into the electronic control unit includes: if the target device is a diagnostic device of the vehicle, obtaining the configuration information sent by the diagnostic device based on a first transmission protocol between the diagnostic device and the electronic control unit, and writing the configuration information into the electronic control unit; if the target device is a remote device of the vehicle, receiving the configuration information sent by the remote device based on the vehicle's TBOX module; obtaining the configuration information after the TBOX module has converted the configuration information to a new format, and writing the converted configuration information into the electronic control unit.

[0063] In this embodiment, the diagnostic device can be understood as a dedicated device used for vehicle fault diagnosis, parameter configuration, software remapping, and other functions. The diagnostic device can be a handheld diagnostic instrument that connects directly to the vehicle's diagnostic port via a physical interface; it can also be PC-based diagnostic software working in conjunction with a VCI (Vehicle Communication Interface) device, which can connect to the PC via USB or Bluetooth and then communicate with the vehicle via the VCI; or it can be integrated into a diagnostic workstation in a repair shop to provide more comprehensive diagnostic functions.

[0064] The first transmission protocol can be understood as the communication standard followed by which diagnostic equipment and electronic control units communicate for data. For example, the first transmission protocol can be the Controller Area Network (CAN) protocol, which is a serial communication protocol widely used in automobiles and has high reliability and real-time performance; or the first transmission protocol can be the K-line protocol, which is a single-wire bidirectional serial communication protocol based on the ISO 9141 standard; the first transmission protocol can also be an Ethernet-based diagnostic protocol (DoIP), which is suitable for high-speed data transmission and remote diagnostics.

[0065] During the process of acquiring configuration information sent by the diagnostic device and writing the configuration information to the electronic control unit, the electronic control unit can receive diagnostic messages sent by the diagnostic device through its communication interface, parse the configuration data in the messages, and store them in non-volatile memory (such as EEPROM or Flash).

[0066] Remote devices can be understood as vehicle backend devices that communicate with vehicles via wireless networks to enable remote monitoring, diagnostics, or configuration. Remote devices can be mobile terminals such as smartphones and tablets, interacting with the vehicle through specific applications; or they can be remote servers located in the cloud, managing and controlling the vehicle through a backend system.

[0067] A TBOX module can be understood as a vehicle telematics box. It acts as a bridge for communication between the vehicle and external networks, typically integrating cellular communication modules, GPS modules, etc. The TBOX module is responsible for data transmission and protocol conversion between the vehicle and remote devices. For example, it communicates with a remote server via a cellular network (such as 4G / 5G) and with the electronic control unit (ECU) via the vehicle's internal bus (such as the CAN bus).

[0068] During the process of acquiring the configuration information after it has been formatted and converted by the TBOX module and writing the converted configuration information to the electronic control unit (ECU), remote devices can send configuration information via application layer protocols such as HTTP / MQTT. After receiving the configuration information, the TBOX module can convert it from an application layer protocol format (such as JSON or XML) to a vehicle internal diagnostic protocol (such as the UDS diagnostic message format), and then send it to the ECU via the CAN bus. For example, the TBOX module can parse the JSON-formatted configuration data sent by the remote device, extract key parameters, encapsulate it into a WriteDataByIdentifier service request conforming to the UDS protocol, and then send it to the ECU via the CAN bus.

[0069] In this application, by adopting a differentiated processing mechanism for different target device types, the compatibility problem of configuration information in the process of writing to the electronic control unit is solved, ensuring that the configuration information can be correctly received and stored regardless of the device type.

[0070] Furthermore, when the target device is a diagnostic device, configuration information can be directly obtained and written based on the first transmission protocol, avoiding the risks associated with network dependence. When the target device is a remote device, the configuration information is received and converted through the TBOX module, solving the problem of incompatible configuration information formats sent by remote devices. This allows the converted configuration information to be recognized and processed by the electronic control unit, thereby ensuring the integrity and availability of the configuration information and improving the flexibility and reliability of the vehicle dashboard data processing method.

[0071] In some embodiments, the step of sending the dashboard data to the target device in response to a request instruction from the target device to query the dashboard data for display includes: parsing the request instruction to obtain type information of the target device and identification information of the dashboard data; determining the protocol type between the target device and the electronic control unit based on the type information; determining the dashboard data corresponding to the identification information based on the identification information, and sending the dashboard data corresponding to the identification information to the target device based on the protocol type for display of the dashboard data.

[0072] In this embodiment, during the process of parsing the request command to obtain the type information of the target device and the identification information of the dashboard data, the electronic control unit can receive the query request of the target device and perform structured analysis on the query request to extract the key information contained therein.

[0073] Type information is used to identify the type of target device initiating the query, such as a diagnostic device, vehicle terminal, or remote device. Identification information is used to specify which dashboard data(s) the target device is requesting, for example, by using a unique ID or name.

[0074] During the parsing process, a preset communication protocol format can be used. For example, if the request command is a diagnostic message based on the CAN bus, the electronic control unit can parse the device type and data identifier according to specific bytes or bit fields of the message; if the request command is an HTTP or TCP / IP message based on an IP network, relevant information can be obtained by parsing specific fields in the message header or data payload.

[0075] Protocol type can be understood as the communication protocol that the electronic control unit needs to select for data transmission after identifying the type of the target device. Different target devices may support or require different communication protocols. For example, diagnostic devices typically use diagnostic protocols (such as UDS over CAN or DoIP), vehicle terminals may use vehicle Ethernet protocols or specific internal bus protocols, while remote devices may communicate using cellular network protocols (such as HTTP / MQTT) through a TBOX module.

[0076] In this application, the electronic control unit can maintain a mapping table or configuration rules to associate specific device types with corresponding protocol types. For example, when the target device is identified as a diagnostic device, a first transmission protocol is determined to be used; when the target device is identified as an in-vehicle terminal, a second transmission protocol is determined to be used; and when the target device is identified as a remote device, a third transmission protocol is determined to be used.

[0077] Specifically, in the process of determining the dashboard data corresponding to the identification information based on the identification information and sending the dashboard data to the target device for display based on the protocol type, this application can, after determining the target device type and communication protocol and parsing the identification information of the dashboard data, retrieve the corresponding latest dashboard data from the dashboard data list stored internally based on the identification information. The dashboard data may have been pre-calculated and updated by the electronic control unit.

[0078] Subsequently, the electronic control unit calls the communication module or driver that matches the determined protocol type, encapsulates the retrieved dashboard data according to the format specified by the protocol, and sends it to the target device through the corresponding physical interface. For example, if the protocol type is CAN diagnostic protocol, the dashboard data is encapsulated into CAN messages and sent; if the protocol type is Ethernet protocol, the dashboard data is encapsulated into TCP / IP packets and sent. After receiving the data, the target device can display the dashboard data corresponding to the identification information on its display interface.

[0079] In this application, by parsing request instructions, the electronic control unit can accurately identify the request source and specific data requirements, thereby avoiding blindly sending or sending irrelevant data. Simultaneously, this application dynamically determines the appropriate communication protocol based on the type information of the target device, ensuring data transmission compatibility and efficiency, and effectively solving the problem of data transmission errors or inefficiencies caused by protocol incompatibility between different devices.

[0080] For example, highly reliable diagnostic protocols can be used for diagnostic equipment; high-speed vehicle network protocols can be used for in-vehicle terminals; and remote devices can be converted and transmitted remotely via a TBOX module. This customized transmission method based on device type and protocol allows dashboard data to be transmitted and displayed in the most suitable way for the target device, thereby optimizing the acquisition and display experience of vehicle dashboard data and improving the flexibility and robustness of the entire data processing system.

[0081] In some embodiments, the step of sending the dashboard data corresponding to the identification information to the target device based on the protocol type for displaying the dashboard data includes: if the type information indicates that the target device is a diagnostic device for the vehicle, sending the dashboard data corresponding to the identification information to the diagnostic device according to a first transmission protocol between the diagnostic device and the electronic control unit, so as to display the dashboard data corresponding to the identification information in the diagnostic device; if the type information indicates that the target device is an in-vehicle terminal for the vehicle, sending the dashboard data corresponding to the identification information to the in-vehicle terminal according to a second transmission protocol between the in-vehicle terminal and the electronic control unit, so as to display the dashboard data corresponding to the identification information in the in-vehicle terminal.

[0082] In this embodiment, type information can be used to identify the specific category of the target device. When the type information indicates that the target device is a vehicle diagnostic device, it can be determined that the dashboard data needs to be transmitted to an external device specifically used for vehicle fault diagnosis, data reading, and parameter configuration. Diagnostic devices typically have specific communication interfaces and protocol stacks for interacting with the vehicle's electronic control unit.

[0083] Specifically, the request command may include a device type field, the value of which is preset to a specific code for "diagnostic device," such as an integer value or a string. The electronic control unit (ECU) reads and identifies this field when parsing the request command. Additionally, the ECU can infer the device type by identifying the source port or connection channel of the request command. For example, certain physical interfaces or logical ports may be dedicated to diagnostic device connections.

[0084] The first transmission protocol can be understood as a set of specific rules and formats followed for data communication between diagnostic equipment and electronic control units (ECUs). The first transmission protocol ensures that the diagnostic equipment can correctly send commands, receive, and parse the dashboard data returned by the ECU. The first transmission protocol can adopt the ISO 14229 (UDS, Unified Diagnostic Services) protocol, which is widely used in automotive diagnostics and supports various diagnostic functions, including data reading and fault code management. Alternatively, the first transmission protocol can also adopt the SAE J1939 protocol, which is mainly used in commercial vehicles and heavy machinery, communicating via a CAN bus and is suitable for transmitting vehicle operating data and diagnostic information.

[0085] In the process of sending the dashboard data corresponding to the identification information to the diagnostic device, this application can encapsulate and transmit the dashboard data generated inside the electronic control unit and associated with the specific identification information to the diagnostic device according to the type of the diagnostic device and the first transmission protocol adopted, so that the diagnostic device can receive the required data and perform subsequent display or analysis.

[0086] Specifically, the electronic control unit first retrieves the corresponding dashboard data from its internal storage based on the identification information. Then, it formats this data according to the first transmission protocol, such as adding a protocol header and checksum, and sends it to the diagnostic device via a physical interface, such as CAN or DoIP. Alternatively, the electronic control unit can first buffer the dashboard data in a transmission buffer, and finally, the communication module sends the data out in segments or as a whole according to the frame structure and timing requirements of the first transmission protocol.

[0087] The dashboard data corresponding to the displayed identification information can be understood as the data that the diagnostic equipment receives, parses, and presents in a user-understandable format. This allows technicians or users to intuitively view the vehicle's operating status, performance indicators, or fault information.

[0088] Meanwhile, after receiving the data, the diagnostic device's built-in software application parses the data frames of the first transmission protocol, extracts the original dashboard data, and then displays this data on the diagnostic device's screen in the form of text, charts, dashboards, etc. through a graphical user interface.

[0089] When the type information indicates that the target device is a vehicle's in-vehicle terminal, it can be determined that the dashboard data needs to be transmitted to the vehicle's internal display device, such as the infotainment system or instrument panel display. The in-vehicle terminal typically communicates with the electronic control unit (ECU) via the vehicle's internal bus and is responsible for providing vehicle information to the driver or passengers. Similarly, the request command may include a device type field, whose value is preset to a specific code for "in-vehicle terminal." The ECU recognizes this field when parsing the request command. Additionally, the ECU also infers that the device type is an in-vehicle terminal by identifying the source ECU of the request command, such as the infotainment system ECU.

[0090] The second transmission protocol can be understood as a set of specific rules and formats followed for data communication between the vehicle terminal and the electronic control unit. The second transmission protocol ensures that the vehicle terminal can correctly request, receive, and parse the dashboard data returned by the electronic control unit, and adapts to the characteristics of the vehicle's internal communication environment, such as real-time performance and reliability.

[0091] The second transmission protocol can be the CAN (Controller Area Network) protocol, one of the most commonly used bus protocols inside vehicles, which has high reliability and real-time performance and is suitable for transmitting various vehicle data. Alternatively, the second transmission protocol can also be the LIN (Local Interconnect Network) protocol, which is suitable for low-cost, low-speed vehicle subsystem communication, such as window and seat controls, and can also be used to transmit simple dashboard data.

[0092] Furthermore, during the process of sending the signboard data corresponding to the identification information to the vehicle terminal, the signboard data generated inside the electronic control unit and associated with specific identification information can be encapsulated and transmitted to the vehicle terminal according to the type of the vehicle terminal and the second transmission protocol adopted, so that the vehicle terminal can receive the required data and perform subsequent display.

[0093] Specifically, the electronic control unit can retrieve the corresponding dashboard data from its internal storage based on the identification information, then format this data according to the second transmission protocol and send it to the vehicle terminal via the vehicle's internal bus, such as the CAN bus. Alternatively, the electronic control unit can use its integrated communication controller to package the dashboard data into data frames conforming to the second transmission protocol and broadcast or send them point-to-point to the vehicle terminal.

[0094] In this application, when the target device is identified as a vehicle diagnostic device, the system uses a first transmission protocol specifically designed for diagnostic communication to transmit data, ensuring that the diagnostic device can efficiently and accurately receive and parse dashboard data and display it professionally on its interface. When the target device is identified as a vehicle's in-vehicle terminal, the system switches to a second transmission protocol suitable for in-vehicle communication, seamlessly transmitting dashboard data to the in-vehicle terminal. This allows for real-time and intuitive display on the vehicle's dashboard or central control screen, effectively avoiding data transmission failures, data parsing errors, or display anomalies caused by protocol incompatibility. This significantly improves the reliability, compatibility, and display accuracy of dashboard data transmission, thereby optimizing the user experience of obtaining and viewing vehicle dashboard data.

[0095] In some embodiments, the step of sending the dashboard data corresponding to the identification information to the target device based on the protocol type for displaying the dashboard data includes: if the type information indicates that the target device is a remote device, sending the dashboard data corresponding to the identification information to the TBOX module based on the third transmission protocol between the vehicle's TBOX module and the electronic control unit; and transmitting the dashboard data corresponding to the identification information to the remote device based on the TBOX module, so as to display the dashboard data corresponding to the identification information in the remote device.

[0096] In this embodiment, during the process of determining that the target device is a remote device based on type information, the electronic control unit can identify the target device requesting dashboard data as a remote device by parsing the device type field in the received request instruction or by querying a preset device registry associated with the request source. For example, the request instruction may contain a specific encoded value, which is predefined as representing "remote device"; or, the electronic control unit may search for the corresponding device type in an internally maintained device list based on the IP address or port number of the request source.

[0097] Electronic control units can be vehicle gateway controllers, acting as a central communication hub capable of communicating with all other electronic control units in the vehicle; or they can be vehicle domain controllers, responsible for managing specific functional domains and integrating the functions of multiple electronic control units.

[0098] The third transmission protocol can be understood as the communication protocol used between the electronic control unit and the TBOX module for transmitting dashboard data. The third transmission protocol needs to ensure efficient and reliable data transmission within the vehicle's internal network and be compatible with the TBOX module's interface. For example, the third transmission protocol could be the CAN (Controller Area Network) protocol, a widely used serial communication protocol in automobiles, offering high reliability and real-time performance; alternatively, it could be the Automotive Ethernet protocol, providing higher bandwidth and more flexible network topologies suitable for transmitting large amounts of data; or it could be a diagnostic protocol (such as UDS on CAN / DoIP), utilizing diagnostic communication mechanisms to transmit specific dashboard data.

[0099] Specifically, during the process of sending the dashboard data corresponding to the identification information to the TBOX module, the electronic device can pass the prepared dashboard data corresponding to the identification information to the TBOX module. Specifically, the dashboard data can be encapsulated into data frames or messages conforming to a third transmission protocol and sent to the TBOX module via the vehicle network interface; alternatively, the electronic control unit can call the application programming interface (API) or service interface provided by the TBOX module to pass the dashboard data as a parameter to the TBOX module, which will then handle the subsequent processing.

[0100] During the process of transmitting the Kanban data corresponding to the identification information to the remote device based on the TBOX module, after receiving the Kanban data sent by the electronic control unit, the TBOX module is responsible for transmitting it to the remote device through an external communication network (such as cellular network, Wi-Fi, etc.). Simultaneously, the TBOX module performs protocol conversion on the received Kanban data (e.g., from the vehicle's internal protocol to internet protocols such as HTTP and MQTT), and sends it to the server or application on the remote device through its built-in communication module (such as a 4G / 5G module); alternatively, the TBOX module can establish a secure VPN tunnel or encrypted connection to ensure the security and integrity of the Kanban data during transmission to the remote device.

[0101] In this application, the electronic control unit can efficiently and stably send dashboard data to the TBOX module via a third transmission protocol within the vehicle, avoiding the complexity and instability that may arise from direct communication with external networks. Subsequently, the TBOX module, as a professional remote communication unit, is responsible for protocol conversion of the data and secure transmission to the remote device. This effectively avoids problems such as network instability, data loss, or protocol mismatch that may occur during remote transmission, ensuring that the dashboard data can accurately and completely reach the remote device for display. This significantly improves the reliability and efficiency of remote data transmission, reduces the communication burden on the electronic control unit, and optimizes the robustness of the overall system, thereby solving the reliability problem of remote device data transmission.

[0102] In the vehicle dashboard data processing method provided in this embodiment of the invention, vehicle data is locally processed in the vehicle's electronic control unit to generate dashboard data, and the dashboard data is transmitted to the target device for display in direct response to the query request of the target device. This effectively avoids the problems of interruption and distortion of vehicle data during transmission between the vehicle and the remote terminal device, improves the reliability and accuracy of the dashboard data, reduces network bandwidth occupation and resource consumption, and effectively reduces communication volume and traffic costs.

[0103] In some embodiments, such as Figure 3 As shown, this embodiment of the invention also provides a method for processing vehicle dashboard data, which is applied to a target device. The method includes steps S310, S320 and S330.

[0104] S310. Send the configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller. S320. Send a request command to the gateway controller or the domain controller to query the dashboard data; S330. Receive the dashboard data sent by the gateway controller or the domain controller, and display the dashboard data.

[0105] In this application, the data processing mechanism inside the vehicle is actively configured by the target device and on-demand query is realized, which effectively solves the problem of data loss caused by network dependence and reduces communication traffic costs.

[0106] Specifically, the target device can send the configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller. The configuration information includes parameters such as the unique identifier of the dashboard data item, the calculation algorithm, and the associated ECU signals, enabling the gateway controller or domain controller to autonomously generate and update dashboard data based on the raw signals obtained from the vehicle's internal bus, without continuous background intervention.

[0107] The target device sends a request command to the gateway controller or domain controller to query the dashboard data, which is triggered only when the user needs to view the data. It instructs the gateway controller or domain controller to return the dashboard data with the specified identifier, thus avoiding the periodic polling of the original signal in traditional solutions.

[0108] It should be noted that when the electronic control unit has both a gateway controller and a domain controller, this application prioritizes configuring the gateway controller through the target device so that the gateway controller can process vehicle data and generate vehicle dashboard data.

[0109] In the vehicle dashboard data processing method provided in this embodiment of the invention, the configuration information of the vehicle dashboard data is sent to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller, and a request command to query the dashboard data is sent to the gateway controller or domain controller. Finally, the dashboard data sent by the gateway controller or domain controller is received and displayed. This ensures the stability and real-time performance of the dashboard data generation, avoids the impact of network fluctuations on the dashboard data, and effectively avoids the risk of dashboard data loss. At the same time, this application only transmits simplified dashboard data during querying, rather than continuously transmitting a large amount of raw signal, which greatly reduces communication traffic and costs and optimizes system resource utilization efficiency.

[0110] In some embodiments, the present invention also provides a vehicle signage data processing apparatus 400, which is used to execute any embodiment of the aforementioned vehicle signage data processing method.

[0111] Specifically, please refer to Figure 4 , Figure 4 This is a schematic block diagram of the vehicle dashboard data processing device 400 provided in an embodiment of the present invention.

[0112] like Figure 4 As shown, the vehicle dashboard data processing device 400 provided in this application is applied in the vehicle's electronic control unit. The device includes a processing unit 410 and a first sending unit 420.

[0113] The processing unit 410 is used to process the collected vehicle data to obtain the vehicle dashboard data; the first sending unit 420 is used to send the dashboard data to the target device in response to the target device's request command to query the dashboard data, so as to display the dashboard data.

[0114] The vehicle dashboard data processing device 400 provided in this application embodiment can process vehicle data locally in the vehicle's electronic control unit to generate dashboard data, and directly respond to the query request of the target device, transmitting the dashboard data to the target device for display. This effectively avoids the problems of interruption and distortion of vehicle data during transmission between the vehicle and the remote terminal device, improves the reliability and accuracy of the dashboard data, reduces network bandwidth occupation and resource consumption, and effectively reduces communication volume and traffic costs.

[0115] In some embodiments, the present invention also provides a vehicle dashboard data processing apparatus applied to a target device, the apparatus including a second sending unit, a third sending unit, and a display unit.

[0116] The second sending unit is used to send the configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit for configuring the gateway controller or domain controller; the third sending unit is used to send a request command to the gateway controller or domain controller to query the dashboard data; the display unit is used to receive the dashboard data sent by the gateway controller or domain controller and display the dashboard data.

[0117] The vehicle dashboard data processing device provided in this application embodiment can send the configuration information of the vehicle dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller, send a request command to the gateway controller or domain controller to query the dashboard data, and finally receive the dashboard data sent by the gateway controller or domain controller and display the dashboard data. This ensures the stability and real-time performance of the dashboard data generation, avoids the impact of network fluctuations on the dashboard data, and effectively avoids the risk of dashboard data loss. At the same time, this application only transmits simplified dashboard data during querying, rather than continuously transmitting a large amount of raw signal, which greatly reduces communication traffic and costs and optimizes system resource utilization efficiency.

[0118] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the above-mentioned vehicle dashboard data processing device and each unit can be referred to the corresponding description in the foregoing method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0119] The aforementioned vehicle dashboard data processing device can be implemented as a computer program, which can, for example... Figure 5 It runs on the electronic device shown.

[0120] Please see Figure 5 , Figure 5 This is a schematic block diagram of an electronic device provided in an embodiment of the present invention.

[0121] See Figure 5 The device 500 includes a processor 502, a memory, and a network interface 505 connected via a system bus 501, wherein the memory may include a storage medium 503 and internal memory 504.

[0122] The storage medium 503 may store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, it enables the processor 502 to perform a method for processing vehicle signage data.

[0123] The processor 502 provides computing and control capabilities to support the operation of the entire device 500.

[0124] The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can perform a method for processing vehicle sign data.

[0125] This network interface 505 is used for network communication, such as providing data transmission. Those skilled in the art will understand that... Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the device 500 to which the present invention is applied. The specific device 500 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0126] The processor 502 is used to run the computer program 5032 stored in the memory to perform the following functions: process the collected vehicle data to obtain the vehicle dashboard data; and in response to the target device's request to query the dashboard data, send the dashboard data to the target device for display.

[0127] The processor 502 is used to run the computer program 5032 stored in the memory to perform the following functions: sending the configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller; sending a request command to the gateway controller or domain controller to query the dashboard data; receiving the dashboard data sent by the gateway controller or domain controller and displaying the dashboard data.

[0128] Those skilled in the art will understand that Figure 5 The embodiments of device 500 shown do not constitute a limitation on the specific configuration of device 500. In other embodiments, device 500 may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, in some embodiments, device 500 may include only a memory and processor 502. In such embodiments, the structure and function of the memory and processor 502 are similar to those shown. Figure 5 The embodiments shown are consistent and will not be described again here.

[0129] It should be understood that, in this embodiment of the invention, the processor 502 may be a Central Processing Unit (CPU), or it may be other general-purpose processors 502, digital signal processors 502 (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor 502 may be a microprocessor 502, or it may be any conventional processor 502, etc.

[0130] According to one aspect of this application, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the following steps: processing collected vehicle data to obtain vehicle dashboard data; and, in response to a request instruction from a target device to query dashboard data, sending the dashboard data to the target device for display.

[0131] According to one aspect of this application, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the following steps: sending configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller; sending a request instruction to the gateway controller or domain controller to query the dashboard data; receiving the dashboard data sent by the gateway controller or domain controller, and displaying the dashboard data.

[0132] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0133] In another embodiment of the invention, a computer storage medium is provided. This storage medium can be a non-volatile computer-readable storage medium or a volatile storage medium. The storage medium stores a computer program 5032, which, when executed by a processor 502, performs the following steps: processing collected vehicle data to obtain vehicle dashboard data; and, in response to a request instruction from a target device to query dashboard data, sending the dashboard data to the target device for display.

[0134] In another embodiment of the invention, a computer storage medium is provided. This storage medium can be a non-volatile computer-readable storage medium or a volatile storage medium. The storage medium stores a computer program 5032, which, when executed by a processor 502, performs the following steps: sending configuration information of the vehicle's dashboard data to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller; sending a request instruction to the gateway controller or domain controller to query the dashboard data; receiving the dashboard data sent by the gateway controller or domain controller, and displaying the dashboard data.

[0135] The storage medium can be any computer-readable storage medium that can store program code, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0136] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0137] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0138] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0139] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods provided in the various embodiments of this application.

[0140] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing vehicle dashboard data, characterized in that, An electronic control unit applied to a vehicle, the method comprising: The collected vehicle data is processed to obtain the vehicle's dashboard data; In response to a request command from a target device to query the dashboard data, the dashboard data is sent to the target device for display.

2. The method for processing vehicle dashboard data according to claim 1, characterized in that, The process of processing the collected vehicle data to obtain the vehicle dashboard data includes: Based on the target device, obtain the configuration information of the dashboard data; Based on the configuration information, the vehicle data is collected and processed to obtain the dashboard data.

3. The method for processing vehicle dashboard data according to claim 2, characterized in that, The step of obtaining the configuration information for the dashboard data based on the target device includes: The configuration information sent by the target device is obtained and written into the electronic control unit.

4. The method for processing vehicle dashboard data according to claim 3, characterized in that, The step of acquiring the configuration information sent by the target device and writing the configuration information into the electronic control unit includes: If the target device is a diagnostic device for the vehicle, the configuration information sent by the diagnostic device is obtained based on the first transmission protocol between the diagnostic device and the electronic control unit, and the configuration information is written into the electronic control unit. If the target device is a remote device of the vehicle, the configuration information sent by the remote device is received based on the vehicle's TBOX module; The configuration information after the TBOX module has converted the configuration information into a new format is obtained, and the converted configuration information is written to the electronic control unit.

5. The method for processing vehicle dashboard data according to any one of claims 1-4, characterized in that, The step of responding to a request command from a target device to query the dashboard data and sending the dashboard data to the target device for display includes: The request command is parsed to obtain the type information of the target device and the identification information of the dashboard data; The protocol type between the target device and the electronic control unit is determined based on the type information; Based on the identification information, determine the dashboard data corresponding to the identification information, and based on the protocol type, send the dashboard data corresponding to the identification information to the target device for display.

6. The method for processing vehicle dashboard data according to claim 5, characterized in that, The step of sending the dashboard data corresponding to the identification information to the target device based on the protocol type for displaying the dashboard data includes: If the type information indicates that the target device is a diagnostic device for the vehicle, the dashboard data corresponding to the identification information is sent to the diagnostic device according to the first transmission protocol between the diagnostic device and the electronic control unit, so as to display the dashboard data corresponding to the identification information in the diagnostic device; If the type information indicates that the target device is the vehicle's in-vehicle terminal, the dashboard data corresponding to the identification information is sent to the in-vehicle terminal according to the second transmission protocol between the in-vehicle terminal and the electronic control unit, so as to display the dashboard data corresponding to the identification information in the in-vehicle terminal.

7. The method for processing vehicle dashboard data according to claim 5, characterized in that, The step of sending the dashboard data corresponding to the identification information to the target device based on the protocol type for displaying the dashboard data includes: If the type information indicates that the target device is a remote device, based on the third transmission protocol between the vehicle's TBOX module and the electronic control unit, the dashboard data corresponding to the identification information is sent to the TBOX module; Based on the TBOX module, the Kanban data corresponding to the identification information is transmitted to the remote device so that the Kanban data corresponding to the identification information can be displayed on the remote device.

8. A method for processing vehicle dashboard data, characterized in that, Applied to a target device, the method includes: The configuration information of the vehicle's dashboard data is sent to the gateway controller or domain controller of the vehicle's electronic control unit to configure the gateway controller or domain controller. Send a request command to the gateway controller or the domain controller to query the dashboard data; Receive the dashboard data sent by the gateway controller or the domain controller, and display the dashboard data.

9. An electronic device, characterized in that, The device includes a memory and a processor, the memory storing a computer program, characterized in that the processor executes the computer program to implement the steps of the method for processing vehicle signboard data according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform a method for processing vehicle signboard data as described in any one of claims 1 to 8.

Images