Internet of Vehicles data transmission method, system, device and medium
By screening IoV data on the terminal side and completing data on the platform side, the problems of low data quality and large storage space occupied in IoV data transmission are solved, and refined data processing and integrity assurance are achieved.
Patent Information
- Application Number
- CN202510902644.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-01
- Publication Date
- 2025-09-19
AI Technical Summary
There are problems in the transmission of Internet of Vehicles data, such as low data quality and excessive storage space occupied by duplicate or erroneous data.
On the terminal side, the received Internet of Vehicles data is compared with historical data to filter out duplicate and erroneous data, and on the platform side, the data is completed through the heartbeat detection mechanism to ensure data integrity.
It improves the data precision, reduces transmission traffic and storage space, corrects data errors caused by network jitter or disconnection, and provides a better data foundation.
Smart Images

Figure CN120676023A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of vehicle networking technology, and in particular to a vehicle networking data transmission method, system, device and medium. Background Art
[0002] The uplink transmission of IoV data primarily proceeds from the vehicle to the terminal, then to the gateway, and finally to the platform for visualization (the gateway and platform can be considered a layer). Sensors on various vehicle components typically transmit vehicle data using either fixed-frequency or variable-frequency transmission. Regardless of the two methods, after receiving vehicle data, the terminal always transmits it to the gateway at a fixed frequency, often much lower than the vehicle's frequency. This is done to reduce traffic consumption and storage pressure on the platform layer.
[0003] However, the above solution can make data "rough" and even cause data loss. For example, a data item might be sent 10 times per second by the vehicle, with each change occurring. However, the terminal only receives and sends it to the gateway twice per second. This results in eight data changes being lost during gateway storage, resulting in the data being "smoothed out" and becoming "rough." Furthermore, many IoV data items, such as vehicle speed, elevation, and some switching variables, can report large amounts of duplicate data over a period of time. For example, when stopped in traffic, the vehicle's location, speed, and other information remain unchanged, yet data continues to be reported. This redundant data often accounts for the bulk of data transmission and platform storage. Furthermore, occasional data misreporting and false alarms can accumulate, consuming significant bandwidth and reducing data quality.
[0004] In summary, the current status of data transmission in the Internet of Vehicles will generally result in problems such as low overall data quality and duplicate or erroneous data taking up too much storage space. Summary of the Invention
[0005] The purpose of the present invention is to provide a method, system, device and medium for Internet of Vehicles data transmission, which can solve the problems of low overall data quality and excessive storage space occupation caused by repeated or erroneous data caused by Internet of Vehicles data transmission.
[0006] To solve the above technical problems, an embodiment of the present invention provides a method for transmitting data in an Internet of Vehicles (IoV), comprising the following steps: Each time the terminal receives Internet of Vehicles data sent by the vehicle, it compares the currently received Internet of Vehicles data with the historically received Internet of Vehicles data that has the same data item as the currently received Internet of Vehicles data to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, thereby determining whether to send the currently received Internet of Vehicles data to the platform; The structure of the data item of the Internet of Vehicles data includes a valid flag. If network jitter or disconnection occurs during the process of the vehicle sending the current Internet of Vehicles data to the terminal, the terminal will invalidate the valid flag of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data before sending it to the platform. When the platform receives Internet of Vehicles data continuously sent by the terminal, if the time interval between two consecutive Internet of Vehicles data belonging to the same data item is greater than the frequency at which the terminal sends Internet of Vehicles data to the platform, the previous Internet of Vehicles data belonging to the same data item will be used to fill the gap until the corresponding Internet of Vehicles data exists at all frequency time points at which the terminal sends Internet of Vehicles data to the platform; Among them, if the valid flag of the Internet of Vehicles data used by the platform when filling in the Internet of Vehicles data is invalid, all the frequency time points of the missing Internet of Vehicles data will be filled in with invalid data.
[0007] Optionally, comparing the currently received Internet of Vehicles data with historically received Internet of Vehicles data having the same data item as the currently received Internet of Vehicles data to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, so as to determine whether to send the currently received Internet of Vehicles data to the platform, includes: If the currently received Internet of Vehicles data is the same as the previously received Internet of Vehicles data, the currently received Internet of Vehicles data is determined to be duplicate data, and the currently received Internet of Vehicles data is chosen not to be sent to the platform; If the currently received Internet of Vehicles data is different from the historically received Internet of Vehicles data, determining whether the currently received Internet of Vehicles data is abnormal data is based on the data items of the currently received Internet of Vehicles data and the comparison results between the currently received Internet of Vehicles data and the historically received Internet of Vehicles data; If the data is abnormal, choose not to send the currently received Internet of Vehicles data to the platform.
[0008] Optionally, the determining whether the currently received Internet of Vehicles data is abnormal data based on a data item of the currently received Internet of Vehicles data and a comparison result between the currently received Internet of Vehicles data and historically received Internet of Vehicles data includes: If the data item of the currently received Internet of Vehicles data is vehicle speed data, subtracting the currently received Internet of Vehicles data from the historically received Internet of Vehicles data; wherein the historically received Internet of Vehicles data is the last received Internet of Vehicles data having the same data item as the currently received Internet of Vehicles data; If the subtraction result falls outside the first threshold range, it is determined that the currently received Internet of Vehicles data is abnormal data.
[0009] Optionally, the determining whether the currently received Internet of Vehicles data is abnormal data based on a data item of the currently received Internet of Vehicles data and a comparison result between the currently received Internet of Vehicles data and historically received Internet of Vehicles data includes: If the data item of the currently received Internet of Vehicles data is tire pressure data, obtaining the difference between the slope of the historically received Internet of Vehicles data and the slope of the historically received Internet of Vehicles data plus the currently received Internet of Vehicles data; wherein the historically received Internet of Vehicles data is the Internet of Vehicles data received n times before the data item is the same as the currently received Internet of Vehicles data, where n is an integer greater than 1; If the difference falls outside the second threshold range, it is determined that the currently received Internet of Vehicles data is abnormal data.
[0010] Optionally, the terminal uses a heartbeat detection mechanism to detect in real time whether network jitter or network disconnection occurs when the vehicle sends current Internet of Vehicles data to the terminal.
[0011] An embodiment of the present invention further provides a vehicle network data transmission system, comprising: The terminal is configured to compare the currently received Internet of Vehicles data with the historically received Internet of Vehicles data that has the same data item as the currently received Internet of Vehicles data each time it receives Internet of Vehicles data from the entire vehicle, to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, and to determine whether to send the currently received Internet of Vehicles data to the platform; The structure of the data item of the Internet of Vehicles data includes a valid flag. If network jitter or disconnection occurs during the process of the vehicle sending the current Internet of Vehicles data to the terminal, the terminal is further configured to invalidate the valid flag of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data before sending it to the platform. The platform is used to, when receiving IoV data continuously sent by a terminal, use the previous IoV data belonging to the same data item to fill in the gap if the time interval between two consecutive IoV data belonging to the same data item is greater than the frequency at which the terminal sends IoV data to the platform, until the corresponding IoV data exists at all frequency points at which the terminal sends IoV data to the platform; Among them, if the valid flag of the Internet of Vehicles data used when filling in the Internet of Vehicles data is invalid, the platform is also used to fill in all the frequency time points of the missing Internet of Vehicles data with invalid data.
[0012] An embodiment of the present invention also provides a computer device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above-mentioned vehicle network data transmission method.
[0013] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned vehicle network data transmission method when executed by a processor.
[0014] The vehicle network data transmission method provided by the present invention has at least the following beneficial effects: Each time the terminal receives IoV data from the vehicle, it first determines whether the currently received IoV data is duplicate or erroneous based on historically received IoV data with the same data item as the currently received IoV data, and then determines whether to send the currently received IoV data to the platform. This prevents the terminal from sending duplicate and erroneous data to the platform. This can occur when the terminal sends data to the platform at a fixed or variable frequency, resulting in some frequency points without data. In this case, when the platform continuously receives IoV data from the terminal, if it detects that the time interval between two consecutive IoV data items belonging to the same data item is greater than the frequency at which the terminal sends IoV data to the platform, it uses the previous IoV data item to complete the gap until corresponding IoV data exists at all frequency points at which the terminal sends IoV data to the platform. This data completion mechanism allows duplicate data not sent by the terminal to be fully displayed on the platform side, and can also complete erroneous data that was not sent to the platform into correct data on the platform side, increasing the precision of the data and improving data quality. While preventing the terminal from sending duplicate and erroneous data to the platform, which consumes data traffic, it also enables the platform to obtain complete data for better vehicle status analysis.
[0015] In the above scheme, once there is a situation of network jitter or disconnection from the vehicle layer to the terminal layer, when the platform completes the data, the previous data will be supplemented to the time point when the vehicle did not report the data (invalid data), resulting in data errors. Therefore, when the terminal encounters network jitter or disconnection, the valid flag position of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data will be invalidated before being sent to the platform. In this way, when the platform is completing the Internet of Vehicles data, if the valid flag bit of the Internet of Vehicles data used is invalid, the frequency time points of the missing Internet of Vehicles data will all be filled with invalid data, which can avoid data errors and achieve effective data completion.
[0016] In summary, the present invention can screen out redundant and invalid data, reduce transmission traffic and storage space, and increase the precision of data by performing data detection and network monitoring on the terminal side. At the same time, when data completion is required due to network connectivity problems, it can correct erroneous completions, eliminate the misleading nature of the data, and lay a better data foundation for subsequent data viewing and analysis operations. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:
[0018] Figure 1 A schematic flow chart of a method for transmitting data in an Internet of Vehicles (IoV) provided by the present invention; Figure 2 A schematic diagram of the overall process of data transmission provided by the present invention; Figure 3 A schematic diagram of a data detection process provided by the present invention; Figure 4 A schematic diagram of a process flow of a heartbeat detection mechanism provided by the present invention; Figure 5 This is a data completion schematic diagram provided by the present invention. DETAILED DESCRIPTION
[0019] To make the objectives, technical solutions, and advantages of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below in conjunction with specific embodiments of the present invention and corresponding drawings. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.
[0020] The technical solutions provided by various embodiments of the present invention are described in detail below with reference to the accompanying drawings.
[0021] One embodiment of the present invention relates to a method for transmitting data in an Internet of Vehicles (IoV) network. The specific process of the method for transmitting data in an IoV network (IoV) network can be as follows: Figure 1 Shown, including: Step 101: Each time the terminal receives Internet of Vehicles data sent by the vehicle, it compares the currently received Internet of Vehicles data with the historically received Internet of Vehicles data that has the same data item as the currently received Internet of Vehicles data to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, and to determine whether to send the currently received Internet of Vehicles data to the platform. Among them, the structure of the data item of the Internet of Vehicles data contains a valid flag bit. If network jitter or network disconnection occurs when the entire vehicle sends the current Internet of Vehicles data to the terminal, the terminal will invalidate the valid flag position of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data before sending it to the platform.
[0022] Step 102: When the platform continuously receives IoV data sent by the terminal, if the time interval between two consecutive IoV data belonging to the same data item is greater than the frequency at which the terminal sends IoV data to the platform, the previous IoV data belonging to the same data item is used to fill the gap until the corresponding IoV data exists at all frequency points at which the terminal sends IoV data to the platform. Among them, if the valid flag of the Internet of Vehicles data used by the platform when filling in the Internet of Vehicles data is invalid, all the frequency time points of the missing Internet of Vehicles data will be filled in with invalid data.
[0023] The following is a detailed description of the implementation details of the vehicle network data transmission method of this embodiment. The following content is only for the convenience of understanding the implementation details and is not necessary for the implementation of this solution.
[0024] In step 101, if the currently received Internet of Vehicles data is the same as the historically received Internet of Vehicles data, it is determined that the currently received Internet of Vehicles data is duplicate data, and the currently received Internet of Vehicles data is not sent to the platform; if the currently received Internet of Vehicles data is different from the historically received Internet of Vehicles data, it is determined whether the currently received Internet of Vehicles data is abnormal data based on the data items of the currently received Internet of Vehicles data and the comparison results between the currently received Internet of Vehicles data and the historically received Internet of Vehicles data; if it is abnormal data, it is determined not to send the currently received Internet of Vehicles data to the platform.
[0025] Among them, if the data item of the currently received Internet of Vehicles data is vehicle speed data, the currently received Internet of Vehicles data is subtracted from the historically received Internet of Vehicles data; wherein the historically received Internet of Vehicles data is the last received Internet of Vehicles data with the same data item as the currently received Internet of Vehicles data; if the subtraction result falls outside the first threshold range, it is determined that the currently received Internet of Vehicles data is abnormal data If the data item of the currently received Internet of Vehicles data is tire pressure data, then the difference between the slope of the historically received Internet of Vehicles data and the slope of the historically received Internet of Vehicles data plus the currently received Internet of Vehicles data is obtained; wherein, the historically received Internet of Vehicles data is the Internet of Vehicles data received n times before the same data item as the currently received Internet of Vehicles data, and n is an integer greater than 1; if the difference falls outside the second threshold range, it is determined that the currently received Internet of Vehicles data is abnormal data.
[0026] In a specific implementation, this embodiment provides a data detector, which is a device that performs detection and verification at the terminal after data is transmitted from the vehicle to the terminal. Figure 2 As shown in the following figure, the detection and verification process is as follows Figure 3As shown in the figure. Each time a terminal receives data, the detector stores a copy of this data in the data item channel, called the "last stored data" (i.e., previously received IoV data). This data is used for calculation and comparison with the next received data (i.e., currently received IoV data). The detector then checks whether the corresponding data item "last stored data" and the current data match the configured detection rules. If the test fails, the data is not reported to the gateway. If it passes, the data is reported to the gateway. The data detector is configurable, including data item channel configuration, detection calculation rule configuration, and "last stored data" aggregation rule configuration.
[0027] (1) Configure the data item channel. For each receivable data item, set up a channel specifically for storing and detecting the data item.
[0028] (2) Configure detection calculation rules. Each channel can configure its own detection rules based on the different data item requirements. Detection rules can be customized based on specific data items, such as "pass if not equal" (applicable to repeated data), "pass if the result of subtracting two data falls within or outside a certain threshold range" (applicable to removing occasional erroneous data with sharp increases or decreases, such as vehicle speed data), etc.
[0029] (3) Configure the aggregation rules for the "last stored data". Generally speaking, the "last stored data" only stores the data received by the channel last time. However, for detection error data or vehicle abnormal data, the "last stored data" can be not only the last data, but also the previous n data (n is configurable). The aggregation rules are also configurable. Some data that has been in a stable change trend, such as tire pressure data, can store the previous n data. Combined with the detection calculation rule, it is set to "calculate the difference between the slope of the previous n data and the slope of the n+1 data and the result falls within a certain threshold range to pass." If the calculation result is significantly different from the set threshold, it can be regarded as error or abnormal data according to the configuration. For such data, different data items, different calculation rules or thresholds can be regarded as data that does not pass or data of abnormal vehicle status that can pass. If abnormal vehicle data is detected, not only the original data but also the accompanying alarm data can be sent. That is, if the current Internet of Vehicles data is duplicate data or abnormal data, the current Internet of Vehicles data will be sent to the platform, and the alarm data will be sent to the platform simultaneously. The abnormal alarm will be issued at the terminal-gateway layer, and the abnormality will be discovered earlier.
[0030] This not only saves a significant amount of traffic for transmitting duplicate data between the terminal and the gateway, but also saves a significant amount of storage space on the gateway. This eliminates any data missed due to a slower reception frequency than the vehicle data reporting frequency, improving data quality and allowing for the removal of erroneous data or the reporting of vehicle anomaly alerts. The entire data detector is configurable, allowing flexible configuration and the development of various rules to meet diverse data needs.
[0031] In step 102, as to how to fully display the duplicate data on the platform, a completion mechanism can be added to the platform layer. According to the original frequency of the terminal reporting to the gateway, if the time interval between two consecutive identical data items is greater than this frequency, the data of the previous item will be used to complete the gap until data is available at all frequency time points. However, if the network jitter or disconnection occurs between the vehicle layer and the terminal layer, when the platform completes the data, the previous data will be added to the time point when the vehicle did not report data (invalid data), resulting in data errors. In order to correct errors, a vehicle-terminal heartbeat detection mechanism is introduced.
[0032] The specific operations are as follows: (1) Add a valid flag to the structure of the data item reported by the Internet of Vehicles.
[0033] (2) The terminal sends a detection message to the vehicle layer at a certain frequency. If the terminal does not receive a normal response from the vehicle layer before sending the detection message again (that is, the timeout period is the detection message sending cycle), the terminal sends the "last stored data" of each data item to the gateway once, and the data valid flag is set to "invalid". Until the connection is restored, the terminal sends an immediate reception message with a "valid" data valid flag to the gateway, such as Figure 4 shown.
[0034] (3) When the platform is completing the data, it will check the valid data flag in the message in turn. If there is no data at a fixed-frequency time node, the latest reported data will be searched for by time to complete the data. If the data is marked as "valid", it means that the data gap at this time node is caused by duplicate data or error data, and the terminal did not send it, so this data will be used to complete the data normally; if the data is marked as "invalid", it means that the data gap at this time node is caused by network jitter or disconnection, so all subsequent missing data will be filled as "invalid data" until a message with a "valid" flag is encountered again, and normal data parsing and display work will be performed, such as Figure 5 shown.
[0035] If this mechanism is not introduced, when completing the data, the "invalid" data will be filled in as the "last stored data", which may cause errors and misleading information.
[0036] This embodiment uses data monitoring and heartbeat detection on the terminal side to filter out redundant and invalid data, reduce transmission traffic and storage space, increase data refinement, and detect vehicle anomalies based on configured rules. When data is supplemented due to network connectivity issues, incorrect supplements are corrected, eliminating misleading data and laying a better data foundation for subsequent data viewing and analysis.
[0037] The steps of the various methods above are divided only for the purpose of clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are within the scope of protection of the present invention. Adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of the invention.
[0038] Another embodiment of the present invention relates to a vehicle network data transmission system. The implementation details of the vehicle network data transmission system of this embodiment are described in detail below. The following content is only provided for ease of understanding and is not required for implementing this solution. The vehicle network data transmission system of this embodiment includes: The terminal is configured to compare the currently received Internet of Vehicles data with the historically received Internet of Vehicles data that has the same data item as the currently received Internet of Vehicles data each time it receives Internet of Vehicles data from the entire vehicle, to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, and to determine whether to send the currently received Internet of Vehicles data to the platform; The structure of the data item of the Internet of Vehicles data includes a valid flag. If network jitter or disconnection occurs during the process of the vehicle sending the current Internet of Vehicles data to the terminal, the terminal is further configured to invalidate the valid flag of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data before sending it to the platform. The platform is used to, when receiving IoV data continuously sent by a terminal, use the previous IoV data belonging to the same data item to fill in the gap if the time interval between two consecutive IoV data belonging to the same data item is greater than the frequency at which the terminal sends IoV data to the platform, until the corresponding IoV data exists at all frequency points at which the terminal sends IoV data to the platform; Among them, if the valid flag of the Internet of Vehicles data used when filling in the Internet of Vehicles data is invalid, the platform is also used to fill in all the frequency time points of the missing Internet of Vehicles data with invalid data.
[0039] It is not difficult to find that this embodiment is a system embodiment corresponding to the above-mentioned method embodiment, and this embodiment can be implemented in conjunction with the above-mentioned method embodiment. The relevant technical details and technical effects mentioned in the above-mentioned embodiment are still valid in this embodiment, and to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the above-mentioned embodiment.
[0040] It is worth noting that all modules involved in this embodiment are logical modules. In actual applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. In addition, to highlight the innovations of the present invention, this embodiment does not include units that are not closely related to solving the technical problems proposed by the present invention. However, this does not mean that other units do not exist in this embodiment.
[0041] Another embodiment of the present invention relates to a computer device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle network data transmission method in the above-mentioned embodiments.
[0042] The memory and processor are connected using a bus, which can include any number of interconnected buses and bridges. The bus connects various circuits of one or more processors and memories. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits. These are all well known in the art and are therefore not described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be a single component or multiple components, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor is transmitted over a wireless medium via an antenna. Furthermore, the antenna receives data and transmits it to the processor.
[0043] The processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory can be used to store data used by the processor when performing operations.
[0044] Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.
[0045] That is, those skilled in the art will understand that all or part of the steps in the above-described method embodiments can be implemented by instructing the relevant hardware through a program. The program is stored in a storage medium and includes a number of instructions for causing a device (such as a microcontroller or chip) or a processor to execute all or part of the steps in the method embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0046] Those skilled in the art will appreciate that the above embodiments are specific embodiments for implementing the present invention, and that in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present invention.
Claims
1. A vehicle network data transmission method, characterized in that: The method comprises: Each time the terminal receives Internet of Vehicles data sent by the vehicle, it compares the currently received Internet of Vehicles data with the historically received Internet of Vehicles data that has the same data item as the currently received Internet of Vehicles data to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, thereby determining whether to send the currently received Internet of Vehicles data to the platform; The structure of the data item of the Internet of Vehicles data includes a valid flag. If network jitter or disconnection occurs during the process of the vehicle sending the current Internet of Vehicles data to the terminal, the terminal will invalidate the valid flag of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data before sending it to the platform. When the platform receives Internet of Vehicles data continuously sent by the terminal, if the time interval between two consecutive Internet of Vehicles data belonging to the same data item is greater than the frequency at which the terminal sends Internet of Vehicles data to the platform, the previous Internet of Vehicles data belonging to the same data item will be used to fill the gap until the corresponding Internet of Vehicles data exists at all frequency time points at which the terminal sends Internet of Vehicles data to the platform; Among them, if the valid flag of the Internet of Vehicles data used by the platform when filling in the Internet of Vehicles data is invalid, all the frequency time points of the missing Internet of Vehicles data will be filled in with invalid data.
2. The vehicle network data transmission method according to claim 1, characterized in that: The comparing the currently received Internet of Vehicles data with the historically received Internet of Vehicles data having the same data item as the currently received Internet of Vehicles data to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, so as to determine whether to send the currently received Internet of Vehicles data to the platform, includes: If the currently received Internet of Vehicles data is the same as the previously received Internet of Vehicles data, the currently received Internet of Vehicles data is determined to be duplicate data, and the currently received Internet of Vehicles data is chosen not to be sent to the platform; If the currently received Internet of Vehicles data is different from the historically received Internet of Vehicles data, determining whether the currently received Internet of Vehicles data is abnormal data is based on the data items of the currently received Internet of Vehicles data and the comparison results between the currently received Internet of Vehicles data and the historically received Internet of Vehicles data; If the data is abnormal, choose not to send the currently received Internet of Vehicles data to the platform.
3. The method for transmitting data in an Internet of Vehicles according to claim 2, wherein: The determining whether the currently received Internet of Vehicles data is abnormal data based on the data items of the currently received Internet of Vehicles data and the comparison result between the currently received Internet of Vehicles data and the historically received Internet of Vehicles data includes: If the data item of the currently received Internet of Vehicles data is vehicle speed data, subtracting the currently received Internet of Vehicles data from the historically received Internet of Vehicles data; wherein the historically received Internet of Vehicles data is the last received Internet of Vehicles data having the same data item as the currently received Internet of Vehicles data; If the subtraction result falls outside the first threshold range, it is determined that the currently received Internet of Vehicles data is abnormal data.
4. The method for transmitting data in an Internet of Vehicles according to claim 2, wherein: The determining whether the currently received Internet of Vehicles data is abnormal data based on the data items of the currently received Internet of Vehicles data and the comparison result between the currently received Internet of Vehicles data and the historically received Internet of Vehicles data includes: If the data item of the currently received Internet of Vehicles data is tire pressure data, obtaining the difference between the slope of the historically received Internet of Vehicles data and the slope of the historically received Internet of Vehicles data plus the currently received Internet of Vehicles data; wherein the historically received Internet of Vehicles data is the Internet of Vehicles data received n times before the data item is the same as the currently received Internet of Vehicles data, where n is an integer greater than 1; If the difference falls outside the second threshold range, it is determined that the currently received Internet of Vehicles data is abnormal data.
5. The method for transmitting data in an Internet of Vehicles according to claim 1, wherein: The terminal uses a heartbeat detection mechanism to detect in real time whether network jitter or disconnection occurs during the process of the vehicle sending current Internet of Vehicles data to the terminal.
6. A vehicle network data transmission system, characterized in that: The system comprises: The terminal is used to compare the currently received Internet of Vehicles data with the historically received Internet of Vehicles data with the same data items as the currently received Internet of Vehicles data each time it receives Internet of Vehicles data from the entire vehicle, to determine whether the currently received Internet of Vehicles data is duplicate data or erroneous data, and to determine whether to send the currently received Internet of Vehicles data to the platform. The structure of the data item of the Internet of Vehicles data includes a valid flag. If network jitter or disconnection occurs during the process of the vehicle sending the current Internet of Vehicles data to the terminal, the terminal is further configured to invalidate the valid flag of the historically received Internet of Vehicles data that is the same as the data item of the currently received Internet of Vehicles data before sending it to the platform. The platform is used to, when receiving IoV data continuously sent by a terminal, use the previous IoV data belonging to the same data item to fill in the gap if the time interval between two consecutive IoV data belonging to the same data item is greater than the frequency at which the terminal sends IoV data to the platform, until the corresponding IoV data exists at all frequency points at which the terminal sends IoV data to the platform; Among them, if the valid flag of the Internet of Vehicles data used when filling in the Internet of Vehicles data is invalid, the platform is also used to fill in all the frequency time points of the missing Internet of Vehicles data with invalid data.
7. A computer device, characterized in that: include: at least one processor; And, a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the vehicle network data transmission method as described in any one of claims 1 to 5.
8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the vehicle network data transmission method according to any one of claims 1 to 5 is implemented.