Message change report data acquisition method based on UART serial port and vehicle

By introducing data acquisition solutions for MCU and CAN buses based on the UART serial port, combined with timestamp checking and automatic frame filling technology, the problem of insufficient data transmission capabilities of UART serial port is solved, and efficient remote data acquisition and reporting is achieved, which improves the Vehicle data integrity and after-sales problem solving efficiency.

CN118921389APending Publication Date: 2024-11-08FAW CAR CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411188400.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the prior art, the hardware cost of the UART serial port is low but the data transmission capability is weak, making it difficult to meet the needs of remote troubleshooting and data acquisition, resulting in low efficiency in solving after-sales problem problems.

Method used

Based on the UART serial port, the MCU microcontroller unit is used to identify the changes in message data, send it to the CAN bus, and combine it with TBOX and IVI modules to realize periodic data acquisition and reporting to the cloud, and adopt the timestamp checksum dynamic alignment strategy. Automatic frame filling to improve data integrity and standardization.

Benefits of technology

Maximize the transmission efficiency of UART serial ports, avoid delays and lags caused by resource occupation, improve the trust and integrity of vehicle data, reduce after-sales complaints, and improve problem-solving efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921389A_ABST
    Figure CN118921389A_ABST
Patent Text Reader

Abstract

The invention discloses a message change report data acquisition method based on a UART serial port and a vehicle, and belongs to the technical field of data acquisition, and the method comprises the following steps: when a wake-up instruction is received, automatically calling an RDS component starting script, enabling the RDS component to start and load a data acquisition task, and registering data acquisition interfaces of a TBOX module and an IVI module; a periodic timer is started, a data acquisition interface is called, the TBOX module and the IVI module execute a data acquisition task strategy, acquired data is processed and reported to a cloud end, whether the task is finished or not is judged, and if yes, the acquisition task is finished. According to the invention, the transmission efficiency of a UART serial port is utilized to the maximum extent, and the problems of delay, jamming, heating and the like of a controller application layer due to over-high resource occupation are avoided; a strategy of performing verification and dynamic alignment by adopting an MCU timestamp and a system timestamp is adopted, so that the situation that the trust of a user on vehicle-related data is reduced due to inaccurate printing caused by independently adopting one of the two timestamps is avoided; and an automatic frame supplementing scheme based on IVI, TBOX and RDS is adopted, so that the integrity and normalization of vehicle data are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention discloses a message change reporting data acquisition method based on a UART serial port and a vehicle, belonging to the technical field of data acquisition. Background Art

[0002] With the popularization of smart cockpits in the automotive electronics industry, the electronic control solutions for the whole vehicle tend to be systematic and integrated, and the number of controllers with operating systems is increasing. In the design of controllers with operating systems, the underlying MCU and the upper MPU usually use URAT or SPI communication solutions. Among them, the UART solution has lower hardware cost and weaker data transmission capacity, while the SPI solution has higher hardware cost and stronger data transmission capacity.

[0003] In the current industry, fault troubleshooting is also tending towards electronic and information-based. Compared with traditional offline maintenance, remote troubleshooting can greatly reduce troubleshooting costs and improve problem-solving efficiency. Therefore, a remote data collection solution has great advantages in solving after-sales problems. Summary of the invention

[0004] In view of the defects of the prior art, the present invention proposes a method and vehicle for collecting message change reports based on a UART serial port, which can reduce hardware costs and enhance data transmission capabilities. At the same time, a solution for remote data collection based on a UART solution is provided to achieve standardization of vehicle data, improve problem solving efficiency, and reduce after-sales complaints.

[0005] The technical solution of the present invention is as follows:

[0006] According to a first aspect of an embodiment of the present invention, a method for collecting message change reporting data based on a UART serial port is provided, which is applied to a message change reporting data collection system based on a UART serial port, including an MCU microcontroller unit. When the MCU microcontroller unit recognizes that any bit of the message data of the MPU microprocessor unit changes, the message data is sent to a sending mailbox, the sending mailbox is sent to a CAN bus through a CAN transceiver, and the CAN bus transmits the message data to a receiving mailbox through a CAN transceiver. The MCU microcontroller unit periodically obtains the message data of the receiving mailbox and transmits it to the MPU microprocessor unit. The MPU microcontroller unit obtains the message data sent by the ECU electronic controller unit and transmits it to the RDS component through the TBOX module. The RDS component can obtain the sent message data through the IVI module and the TBOX module respectively, including:

[0007] When the wake-up command is received, the RDS component startup script is automatically called to enable the RDS component to start loading the data acquisition task and register the data acquisition interface of the TBOX module and the IVI module;

[0008] Start the periodic timer, call the data acquisition interface, the TBOX module and the IVI module execute the data acquisition task strategy, collect data, process and report it to the cloud, and determine whether the task is completed. If so, the collection task is completed.

[0009] Preferably, if it is determined that the task has not been completed, data collection, processing and reporting to the cloud will continue until the task is completed.

[0010] Preferably, the TBOX module executes a data acquisition task strategy, including:

[0011] The RDS component records the MCU timestamp and its corresponding TBOX system time;

[0012] When receiving a message from the MCU, it is necessary to determine whether the difference between the timestamp in the current message and the TBOX system time is within the error range compared with the last recorded time:

[0013] Yes, based on the current timestamp;

[0014] No, the offset calculation is performed based on the latest system timestamp and MCU;

[0015] The processed frames are inserted into the data acquisition buffer, and after the task time is over, they are inserted into the data acquisition buffer of TBOX and IVI and wait for reporting.

[0016] Preferably, the IVI module executes a data acquisition task strategy, including:

[0017] The RDS component needs to determine whether the current frame is an event frame:

[0018] If yes, generate and cache interpolated frames according to predefined rules, and execute the next step;

[0019] No, the processed frame is inserted into the data acquisition buffer, and after the task time is over, it is inserted into the data acquisition buffer of TBOX and IVI and waits for reporting;

[0020] Start the cache timer. When the timing time is up, insert the next frame into the cache. After the task time is up, insert it into the data acquisition cache of TBOX and IVI and wait for reporting.

[0021] According to a second aspect of an embodiment of the present invention, a message change reporting data acquisition device based on a UART serial port is provided, comprising:

[0022] The startup module is used to automatically call the RDS component startup script when receiving a wake-up command, so that the RDS component starts loading the data acquisition task and registers the data acquisition interface of the TBOX module and the IVI module;

[0023] The acquisition module is used to start the periodic timer and call the data acquisition interface. The TBOX module and the IVI module execute the data acquisition task strategy, collect data, process and report it to the cloud, and determine whether the task is completed. If so, the acquisition task is completed.

[0024] Preferably, the acquisition module is used to:

[0025] The RDS component records the MCU timestamp and its corresponding TBOX system time;

[0026] When receiving a message from the MCU, it is necessary to determine whether the difference between the timestamp in the current message and the TBOX system time is within the error range compared with the last recorded time:

[0027] Yes, based on the current timestamp;

[0028] No, the offset calculation is performed based on the latest system timestamp and MCU;

[0029] The processed frames are inserted into the data acquisition buffer, and after the task time is over, they are inserted into the data acquisition buffer of TBOX and IVI and wait for reporting.

[0030] Preferably, the acquisition module is used to:

[0031] The RDS component needs to determine whether the current frame is an event frame:

[0032] If yes, generate and cache interpolated frames according to predefined rules, and execute the next step;

[0033] No, the processed frame is inserted into the data acquisition buffer, and after the task time is over, it is inserted into the data acquisition buffer of TBOX and IVI and waits for reporting;

[0034] Start the cache timer. When the timing time is up, insert the next frame into the cache. After the task time is up, insert it into the data acquisition cache of TBOX and IVI and wait for reporting.

[0035] According to a third aspect of an embodiment of the present invention, there is provided a vehicle, comprising:

[0036] one or more processors;

[0037] a memory for storing the one or more processor-executable instructions;

[0038] Wherein, the one or more processors are configured to:

[0039] Execute the method described in the first aspect of the embodiment of the present invention.

[0040] According to a fourth aspect of an embodiment of the present invention, a non-temporary computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of a terminal, the terminal is enabled to execute the method described in the first aspect of the embodiment of the present invention.

[0041] According to a fifth aspect of an embodiment of the present invention, an application product is provided. When the application product is running on a terminal, the terminal executes the method described in the first aspect of the embodiment of the present invention.

[0042] The beneficial effects of the present invention are:

[0043] The present invention provides a message change reporting data acquisition method based on a UART serial port and a vehicle, which maximizes the transmission efficiency of the UART serial port and avoids delay, jamming, heating and other problems in the controller application layer due to excessive resource occupation; adopts an MCU timestamp and a system timestamp to perform verification and dynamic alignment strategy to avoid the situation where inaccurate printing occurs when only one of them is adopted, resulting in a reduction in user trust in vehicle-related data; and adopts an automatic frame supplementation solution based on IVI, TBOX and RDS to improve the integrity and standardization of vehicle data.

[0044] 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 invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 The present invention is a flow chart of a method for collecting message change reporting data based on a UART serial port according to an exemplary embodiment.

[0046] Figure 2 The present invention is a flow chart of a method for collecting message change reporting data based on a UART serial port according to an exemplary embodiment.

[0047] Figure 3 The present invention is a structural schematic block diagram of a data acquisition device for reporting message changes based on a UART serial port according to an exemplary embodiment.

[0048] Figure 4 The present invention is a schematic block diagram of a vehicle structure according to an exemplary embodiment. DETAILED DESCRIPTION

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

[0050] In the description of the present invention, it should be noted that the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc. indicate orientations or positional relationships based on the orientations or positional relationships described in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0051] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0052] The embodiment of the present invention provides a method for collecting message change reports based on a UART serial port, which is implemented by a terminal. The terminal at least includes a CPU, etc.

[0053] Embodiment 1:

[0054] Figure 1 and 2 A method for collecting message change reporting data based on a UART serial port is shown according to an exemplary embodiment, and is applied to a message change reporting data collection system based on a UART serial port, including an MCU microcontroller unit. When the MCU microcontroller unit recognizes that any bit of the message data of the MPU microprocessor unit changes, the message data is sent to a sending mailbox, and the sending mailbox is sent to a CAN bus through a CAN transceiver. The CAN bus transmits the message data to a receiving mailbox through a CAN transceiver. The MCU microcontroller unit periodically obtains the message data of the receiving mailbox and transmits it to the MPU microprocessor unit. The MPU microcontroller unit obtains the message data sent by the ECU electronic controller unit and transmits it to the RDS component through the TBOX module. The RDS component can obtain the sent message data through the IVI module and the TBOX module respectively, including:

[0055] When the wake-up command is received, the RDS component startup script is automatically called to enable the RDS component to start loading the data acquisition task and register the data acquisition interface of the TBOX module and the IVI module;

[0056] Start the periodic timer and call the data acquisition interface. The TBOX module and the IVI module execute the data acquisition task strategy, collect data, process and report it to the cloud, and determine whether the task is completed. If so, the collection task is completed. If it is determined that the task is not completed, continue to collect data, process and report it to the cloud until the task is completed.

[0057] The above TBOX module executes the data collection task strategy, including:

[0058] The RDS component records the MCU timestamp and its corresponding TBOX system time;

[0059] When receiving a message from the MCU, it is necessary to determine whether the difference between the timestamp in the current message and the TBOX system time is within the error range compared with the last recorded time:

[0060] Yes, based on the current timestamp;

[0061] No, the offset calculation is performed based on the latest system timestamp and MCU;

[0062] The processed frames are inserted into the data acquisition buffer, and after the task time is over, they are inserted into the data acquisition buffer of TBOX and IVI and wait for reporting.

[0063] The above IVI module executes the data acquisition task strategy, including:

[0064] The RDS component needs to determine whether the current frame is an event frame:

[0065] If yes, generate and cache interpolated frames according to predefined rules, and execute the next step;

[0066] No, the processed frame is inserted into the data acquisition buffer, and after the task time is over, it is inserted into the data acquisition buffer of TBOX and IVI and waits for reporting;

[0067] Start the cache timer. When the timing time is up, insert the next frame into the cache. After the task time is up, insert it into the data acquisition cache of TBOX and IVI and wait for reporting.

[0068] Among them: Regarding the time alignment of TBOX data time, TBOX needs to determine whether the timestamp information of the MCU and the timestamp of the TBOX system time meet a certain time interval. If the time interval is small, it is considered that the current RDS time is more accurate, but if the time interval is large, it is considered that the RDS time is accurate, and the time offset is recalculated based on the recorded MCU timestamp. This way of timestamp printing minimizes the time error of the data.

[0069] There are two ways to insert frames: TBOX inserts frames according to the data acquisition cycle. IVI inserts frames. Due to the particularity of the IVI frame format, there are often trigger-type frames, which will enable the concept of a cache timer. When the time is met, the frame insertion process will be performed, which greatly improves the consistency of the acquisition message and the bus message.

[0070] Embodiment 2:

[0071] Figure 3 The present invention is a structural schematic block diagram of a device for collecting message changes and reporting data based on a UART serial port according to an exemplary embodiment, the device comprising:

[0072] The startup module 210 is used to automatically call the RDS component startup script when receiving the wake-up instruction, so that the RDS component starts loading the data acquisition task and registers the data acquisition interface of the TBOX module and the IVI module;

[0073] The acquisition module 220 is used to start the periodic timer, call the data acquisition interface, and the TBOX module and the IVI module execute the data acquisition task strategy, collect data, process and report it to the cloud, and determine whether the task is completed. If so, the acquisition task is completed.

[0074] Preferably, the acquisition module 220 is used to:

[0075] The RDS component records the MCU timestamp and its corresponding TBOX system time;

[0076] When receiving a message from the MCU, it is necessary to determine whether the difference between the timestamp in the current message and the TBOX system time is within the error range compared with the last recorded time:

[0077] Yes, based on the current timestamp;

[0078] No, the offset calculation is performed based on the latest system timestamp and MCU;

[0079] The processed frames are inserted into the data acquisition buffer, and after the task time is over, they are inserted into the data acquisition buffer of TBOX and IVI and wait for reporting.

[0080] Preferably, the acquisition module 220 is used to:

[0081] The RDS component needs to determine whether the current frame is an event frame:

[0082] If yes, generate and cache interpolated frames according to predefined rules, and execute the next step;

[0083] No, the processed frame is inserted into the data acquisition buffer, and after the task time is over, it is inserted into the data acquisition buffer of TBOX and IVI and waits for reporting;

[0084] Start the cache timer. When the timing time is up, insert the next frame into the cache. After the task time is up, insert it into the data acquisition cache of TBOX and IVI and wait for reporting.

[0085] This application maximizes the transmission efficiency of the UART serial port to avoid delays, freezes, heating and other problems in the controller application layer due to excessive resource usage; adopts the strategy of verification and dynamic alignment of MCU timestamp and system timestamp to avoid inaccurate printing when using only one of them, which reduces users' trust in vehicle-related data; adopts an automatic frame filling solution based on IVI, TBOX, and RDS to improve the integrity and standardization of vehicle data.

[0086] Embodiment three:

[0087] Figure 4 300 is a block diagram of a vehicle 300 provided in an embodiment of the present application. For example, the vehicle 300 may be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicles. The vehicle 300 may be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle. The vehicle 300 may also be equipped with a brake-by-wire system.

[0088] Reference Figure 4 , the vehicle 300 may include various subsystems, for example, an infotainment system 310, a perception system 320, a decision control system 330, a drive system 340, and a computing platform 350. The vehicle 300 may also include more or fewer subsystems, and each subsystem may include multiple components. In addition, each subsystem and each component of the vehicle 300 may be interconnected by wire or wireless means.

[0089] In some embodiments, the infotainment system 310 may include a communication system, an entertainment system, and a navigation system, among others.

[0090] The perception system 320 may include several sensors for sensing information about the environment around the vehicle 300. For example, the perception system 320 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.

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

[0092] The drive system 340 may include components that provide power movement for the vehicle 300. In one embodiment, the drive system 340 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.

[0093] Some or all functions of the vehicle 300 are controlled by a computing platform 350. The computing platform 350 may include at least one processor 351 and a memory 352, and the processor 351 may execute instructions 353 stored in the memory 352.

[0094] The processor 351 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.

[0095] The memory 352 may be implemented by any type of volatile or nonvolatile storage 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 storage, flash memory, magnetic disk or optical disk.

[0096] In addition to instructions 353 , memory 352 may also store data, such as road maps, route information, vehicle location, direction, speed, etc. The data stored in memory 352 may be used by computing platform 350 .

[0097] In the embodiment of the present disclosure, the processor 351 may execute the instruction 353 to complete all or part of the steps of the above-mentioned method for collecting message change reporting data based on the UART serial port.

[0098] Embodiment 4:

[0099] In an exemplary embodiment, a computer-readable storage medium is also provided, on which a computer program is stored. When the program is executed by a processor, a method for collecting message change reporting data based on a UART serial port is implemented as provided in all the inventive embodiments of the present application.

[0100] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.

[0101] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0102] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0103] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0104] Embodiment five:

[0105] In an exemplary embodiment, an application product is also provided, including one or more instructions, which can be executed by the processor 351 of the above-mentioned device to complete the above-mentioned UART serial port-based message change reporting data collection method.

[0106] Although the embodiments of the present invention have been disclosed above, they are not limited to the applications listed in the specification and the embodiments. It can be fully applied to various fields suitable for the present invention. For those familiar with the art, additional modifications can be easily realized. Therefore, without departing from the general concept defined by the claims and equivalent scope, the present invention is not limited to the specific details and the illustrations shown and described here.

Claims

1. A method for collecting message change reporting data based on a UART serial port, which is applied to a message change reporting data collection system based on a UART serial port, comprising an MCU microcontroller unit. When the MCU microcontroller unit identifies that any bit of the message data of the MPU microprocessor unit has changed, the message data is sent to a sending mailbox, the sending mailbox is sent to a CAN bus through a CAN transceiver, the CAN bus transmits the message data to a receiving mailbox through a CAN transceiver, the MCU microcontroller unit periodically obtains the message data in the receiving mailbox and transmits it to the MPU microprocessor unit, the MPU microcontroller unit obtains the message data sent by the ECU electronic controller unit and transmits it to the RDS component through the TBOX module, the RDS component can obtain the sent message data through the IVI module and the TBOX module respectively, characterized in that: include: When the wake-up command is received, the RDS component startup script is automatically called to enable the RDS component to start loading the data acquisition task and register the data acquisition interface of the TBOX module and the IVI module; Start the periodic timer, call the data acquisition interface, the TBOX module and the IVI module execute the data acquisition task strategy, collect data, process and report it to the cloud, and determine whether the task is completed. If so, the collection task is completed.

2. A method for collecting message changes and reporting data based on a UART serial port according to claim 1, characterized in that: If it is determined that the task has not been completed, data collection, processing and reporting to the cloud will continue until the task is completed.

3. A method for collecting message changes and reporting data based on a UART serial port according to claim 1, characterized in that: The TBOX module executes the data acquisition task strategy, including: The RDS component records the MCU timestamp and its corresponding TBOX system time; When receiving a message from the MCU, it is necessary to determine whether the difference between the timestamp in the current message and the TBOX system time is within the error range compared with the last recorded time: Yes, based on the current timestamp; No, the offset calculation is performed based on the latest system timestamp and MCU; The processed frames are inserted into the data acquisition buffer, and after the task time is over, they are inserted into the data acquisition buffer of TBOX and IVI and wait for reporting.

4. A method for collecting message changes and reporting data based on a UART serial port according to claim 3, characterized in that: The IVI module executes the data acquisition task strategy, including: The RDS component needs to determine whether the current frame is an event frame: If yes, generate and cache interpolated frames according to predefined rules, and execute the next step; No, the processed frame is inserted into the data acquisition buffer, and after the task time is over, it is inserted into the data acquisition buffer of TBOX and IVI and waits for reporting; Start the cache timer. When the timing time is up, insert the next frame into the cache. After the task time is up, insert it into the data acquisition cache of TBOX and IVI and wait for reporting.

5. A message change reporting data acquisition device based on a UART serial port, characterized in that: include: The startup module is used to automatically call the RDS component startup script when receiving a wake-up command, so that the RDS component starts loading the data acquisition task and registers the data acquisition interface of the TBOX module and the IVI module; The acquisition module is used to start the periodic timer and call the data acquisition interface. The TBOX module and the IVI module execute the data acquisition task strategy, collect data, process and report it to the cloud, and determine whether the task is completed. If so, the acquisition task is completed.

6. A message change reporting data acquisition device based on a UART serial port according to claim 5, characterized in that: The acquisition module is used for: The RDS component records the MCU timestamp and its corresponding TBOX system time; When receiving a message from the MCU, it is necessary to determine whether the difference between the timestamp in the current message and the TBOX system time is within the error range compared with the last recorded time: Yes, based on the current timestamp; No, the offset calculation is performed based on the latest system timestamp and MCU; The processed frames are inserted into the data acquisition buffer, and after the task time is over, they are inserted into the data acquisition buffer of TBOX and IVI and wait for reporting.

7. A message change reporting data acquisition device based on a UART serial port according to claim 5, characterized in that: The acquisition module is used for: The RDS component needs to determine whether the current frame is an event frame: If yes, generate and cache interpolated frames according to predefined rules, and execute the next step; No, the processed frame is inserted into the data acquisition buffer, and after the task time is over, it is inserted into the data acquisition buffer of TBOX and IVI and waits for reporting; Start the cache timer. When the timing time is up, insert the next frame into the cache. After the task time is up, insert it into the data acquisition cache of TBOX and IVI and wait for reporting.

8. A vehicle, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to execute the steps of a method for collecting message change reporting data based on a UART serial port as described in any one of claims 1 to 4.

9. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the program instructions are executed by a processor, the steps of a method for collecting message change reports based on a UART serial port as described in any one of claims 1 to 4 are implemented.