Methods and systems for verifying the integrity of vehicle network data

By storing data in blocks in the vehicle network database and using the blake2d algorithm to calculate checksums, combined with Spark tasks for data verification, the problem of low efficiency in verifying large amounts of big data and incremental data in the vehicle network scenario is solved, and efficient and accurate data integrity management is achieved.

CN123116346APending Publication Date: 2026-11-17ALIBABA CLOUD COMPUTING CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510631024.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the context of connected vehicles, existing technologies struggle to effectively handle data integrity verification for large datasets, especially incremental data verification, which is both inefficient and inaccurate.

Method used

By storing data in blocks according to timestamps and vehicle identifiers in the vehicle network database, and using the blake2d algorithm to calculate the checksum of the data blocks, combined with Spark tasks to perform row-level and interval data integrity checks, efficient verification of incremental data is achieved.

Benefits of technology

It improves the efficiency and accuracy of data verification, ensuring the integrity and reliability of data in the vehicle-to-everything (V2X) scenario, and is suitable for applications with high reliability and real-time requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123116346A_ABST
    Figure CN123116346A_ABST
Patent Text Reader

Abstract

This specification provides a method and system for verifying the integrity of vehicle network data. The method includes: receiving vehicle data generated by a data generation component and storing the vehicle data in a vehicle network database, wherein the vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers; determining checkpoint information for a data verification task and selecting data to be verified in the vehicle network database based on the checkpoint information; determining an initial checksum corresponding to the data to be verified, and data dimension information of the initial checksum, including row data dimensions and block data dimensions; calculating a target checksum corresponding to the initial checksum according to the data dimension information; and performing the data verification task on the data to be verified based on the initial checksum and the target checksum to obtain a data verification result. Data verification is performed from different data dimensions to ensure verification accuracy and reliability.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments in this specification relate to the field of database technology, and in particular to a method and system for verifying the integrity of vehicle network data. Background Technology

[0002] A database is a repository for organizing, storing, and managing data according to a data structure. It is a large collection of organized, shareable, and centrally managed data that is stored permanently on a computer. Data comes from many sources, such as travel records, spending records, web pages browsed, and sent messages. Besides text data, images, music, and sound are also considered data.

[0003] Data stored in database systems involves processing by multiple data engines, such as message engines, streaming engines, and wide table engines. To ensure that data stored in the database system is not corrupted, lost, or duplicated, data integrity verification is necessary. However, in the context of connected vehicles, the large data volume and difficulty in handling incremental data mean that there is currently no effective method for data integrity verification. Therefore, improving the efficiency and reliability of data integrity verification is a pressing issue that needs to be addressed. Summary of the Invention

[0004] In view of this, embodiments of this specification provide a method for verifying the integrity of vehicle network data. One or more embodiments of this specification also relate to a vehicle network data integrity verification system, a vehicle network data integrity verification device, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies existing in the prior art.

[0005] According to a first aspect of the embodiments of this specification, a method for verifying the integrity of vehicle network data is provided, comprising:

[0006] The system receives vehicle data generated by a data generation component and stores the vehicle data in a vehicle network database. The vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers.

[0007] Determine the checkpoint information for the data verification task, and select the data to be checked in the vehicle network database based on the checkpoint information;

[0008] Determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum. The data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database.

[0009] Calculate the target checksum corresponding to the initial checksum according to the data dimension information;

[0010] Based on the initial checksum and the target checksum, the data verification task is performed on the data to be checked to obtain the data verification result.

[0011] According to a second aspect of the embodiments of this specification, a vehicle network data integrity verification system is provided. The system includes a data generation component, a data storage component, and a data verification component, wherein...

[0012] The data generation component is used to generate vehicle data and send the vehicle data to the data storage component;

[0013] The data storage component is used to store the vehicle data in the vehicle network database, and the vehicle network database stores the vehicle data in blocks according to timestamp and vehicle identifier;

[0014] The data verification component is used to determine the checkpoint information of the data verification task, and select the data to be checked in the vehicle network database according to the checkpoint information; determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum, wherein the data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database; calculate the target checksum corresponding to the initial checksum according to the data dimension information; and perform the data verification task on the data to be checked based on the initial checksum and the target checksum to obtain the data verification result.

[0015] According to a third aspect of the embodiments of this specification, a device for verifying the integrity of vehicle network data is provided, comprising:

[0016] The generation module is configured to receive vehicle data generated by the data generation component and store the vehicle data in a vehicle network database, wherein the vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers;

[0017] The selection module is configured to determine the checkpoint information for the data verification task and select the data to be checked in the vehicle network database based on the checkpoint information.

[0018] The determination module is configured to determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum. The data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database.

[0019] The calculation module is configured to calculate the target checksum corresponding to the initial checksum according to the data dimension information;

[0020] The execution module is configured to perform the data verification task on the data to be checked based on the initial checksum and the target checksum, and obtain the data verification result.

[0021] According to a fourth aspect of the embodiments of this specification, a computing device is provided, comprising:

[0022] Memory and processor;

[0023] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the above-mentioned vehicle network data integrity verification method.

[0024] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, implement the steps of the above-described method for verifying the integrity of vehicle network data.

[0025] According to a sixth aspect of the embodiments of this specification, a computer program product is provided, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method for verifying the integrity of vehicle network data.

[0026] One embodiment of this specification implements the generation of vehicle data through a data generation component. The vehicle data is then segmented and stored in a vehicle network database according to timestamps and vehicle identifiers. This enables subsequent data querying and verification based on data segments, improving processing efficiency. By determining checkpoint information for the data verification task, and selecting data to be verified in the vehicle network database based on this checkpoint information, the system can filter out data requiring verification based on the timestamp information at the time of data storage. This achieves data verification for incremental data, improving verification efficiency. Furthermore, by determining the initial checksum and its data dimension information, the system can calculate the target checksum corresponding to the initial checksum. The initial and target checksums are then used to execute the data verification task, achieving data verification from different data dimensions and ensuring the accuracy and reliability of the data verification. Attached Figure Description

[0027] Figure 1A A schematic diagram of the framework of a method for verifying the integrity of vehicle network data according to an embodiment of this specification is shown;

[0028] Figure 1B A system flowchart of a vehicle network data integrity verification system according to an embodiment of this specification is shown;

[0029] Figure 2 This is a flowchart of a method for verifying the integrity of vehicle network data according to one embodiment of this specification;

[0030] Figure 3 This is a flowchart illustrating the process of a method for verifying the integrity of vehicle network data according to one embodiment of this specification.

[0031] Figure 4 This is a schematic diagram of the structure of a vehicle network data integrity verification device provided in one embodiment of this specification;

[0032] Figure 5 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0033] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0034] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0035] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0036] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0037] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0038] Multi-model database: A multi-model database is a cloud-native database service suitable for any scale and multiple models. It supports various data models, including wide column, time series, search, and file, to meet the needs of different service scenarios. Due to its compatibility with multiple standard interfaces, it is widely used in various large-scale services and internet applications.

[0039] Multi-model databases are commonly used in the connected vehicle industry to store vehicle data uploaded by each vehicle, such as speed, location, and tire pressure. They primarily utilize the message engine, streaming engine, wide table engine, and computation engine of a multi-model database for data storage, processing, and querying. In connected vehicle scenario testing, we need to test data integrity, ensuring that data passing through the message engine, streaming engine, and wide table engine is not corrupted, lost, or duplicated. Data integrity verification in this scenario presents the following challenges: large data volumes and difficulty in handling incremental data. Large data volumes result in lengthy full-scale verification, making it difficult to meet real-time requirements; large data scenarios typically involve streaming data being written to the database, thus requiring support for incremental data verification.

[0040] Current data verification methods typically employ checksums or hash algorithms, but these methods are inefficient and have limited coverage; or they use mathematical statistical methods but cannot guarantee verification accuracy.

[0041] Based on this, this specification provides a method for verifying the integrity of vehicle network data. This specification also relates to a vehicle network data integrity verification system, a vehicle network data integrity verification device, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0042] See Figure 1A , Figure 1AThis diagram illustrates a framework of a method for verifying the integrity of vehicle-to-everything (V2X) data according to an embodiment of this specification. In specific application scenarios, such as V2X applications, big data is collected and received, including vehicle data. This collected data is then stored and verified. In V2X applications, vehicles periodically send data collected by their sensors to the cloud, where it is stored and analyzed. In testing scenarios, vehicle data can be generated using a data generation component, following the format of the actual collected data to ensure consistency between the test and real-world usage scenarios. After obtaining the application data, a checksum is calculated and written to a multi-modal database (V2X database). During data writing, the V2X database stores data in blocks based on the vehicle data's collection or generation timestamp and vehicle identifier. Specifically, the generated data is sent to the message queue of the database component. Flink tasks read data from the message queue and write it to the backend database (wide table / Iceberg). The data is ultimately stored in wide table or Iceberg (Iceberg is an open table format for large-scale data analysis scenarios). The data is divided into blocks by time and vehicle to optimize query efficiency. The backend uses wide table / Iceberg to store data. When designing the tables, for wide table, (timestamp, object identifier (e.g., vehicle identifier, device identifier)) is used as the primary key; for Iceberg, (timestamp, object identifier) ​​is used as the partitioning basis. In this way, the characteristics of the big data storage component itself (sorted by primary key, partitioned and divided) can be used to improve data query efficiency. When the data is generated, a checksum field is added to each row of data to verify the integrity of the data. At the same time, the data is divided into blocks according to the timestamp and object identifier, and a checksum is calculated for the checksum field of the data in each block. This checksum is used to calculate the integrity of the data block. The blake2d algorithm is used, which supports incremental calculation of checksums. Therefore, in scenarios where data is generated in real time, the checksum of the data block can be updated incrementally. The data is divided into blocks by hour, and the checksums of the data blocks are stored in the database.

[0043] By calculating and storing data checksums, subsequent data validation can be performed using these checksums. Specifically, the data validation module validates the data stored in the database, using Spark tasks to verify the integrity of data stored in wide tables or Iceberg tables, including row-level and range-level data integrity. If checksum mismatches are found, these data are output for further processing or analysis. Based on this, this database architecture can effectively manage and validate the integrity of large-scale datasets, especially in scenarios requiring high reliability and real-time performance, such as connected vehicles.

[0044] See Figure 1B , Figure 1B This diagram illustrates a system flowchart of a vehicle-to-everything (V2X) data integrity verification system according to an embodiment of this specification. The system includes a data generation component 102, a data storage component 104, and a data verification component 106.

[0045] The data generation component 102 is used to generate vehicle data and send the vehicle data to the data storage component.

[0046] The data storage component 104 is used to store the vehicle data in the vehicle network database, and the vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers.

[0047] The data verification component 106 is used to determine the checkpoint information of the data verification task, and select the data to be checked in the vehicle network database according to the checkpoint information; determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum, wherein the data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database; calculate the target checksum corresponding to the initial checksum according to the data dimension information; and perform the data verification task on the data to be checked based on the initial checksum and the target checksum to obtain the data verification result.

[0048] In practical applications, the vehicle network data integrity verification system provided in this specification can implement the vehicle network data integrity verification method provided in the above embodiments. Therefore, according to... Figure 1AThe provided framework diagram is used for explanation. The data generation component can be understood as a component used to generate vehicle data. During testing, since it's impossible to collect actual project application data, the data generation component can be used to simulate and generate vehicle data. The process of generating vehicle data involves calculating row and block checksums. Specifically, the data generation component generates simulated initial vehicle data, which is equivalent to the collected vehicle data. After obtaining the initial vehicle data, the component simultaneously calculates the row and block checksums. The row checksum is added as a field to the initial vehicle data to form the vehicle data. This vehicle data can then be sent to the data storage component for database storage. The block checksum is directly stored in the checksum database and retrieved during subsequent block data verification. In practical applications, the data generation component can also collect initial vehicle data and then calculate checksums on that initial data to generate the actual vehicle data.

[0049] Correspondingly, a data storage component can be understood as a component used to store vehicle data. This component can be a database component such as a message engine component, a streaming engine component, or a wide table engine component, for example... Figure 1A The big data components include message queues, Flink stream processing, and wide tables / Iceberg. After receiving vehicle data from the data generation component, the data storage component calls various big data components according to the database's storage logic to store the vehicle data in the connected vehicle database. During data storage, the connected vehicle database divides the data into blocks based on the vehicle's timestamp and vehicle identifier for subsequent data querying and verification. The connected vehicle database can be understood as a database for storing connected vehicle project data. The vehicle data in the connected vehicle database can be used to execute other project logic within the connected vehicle project, such as vehicle positioning and autonomous driving. The connected vehicle database can also directly store block checksums sent by the data generation component, facilitating subsequent block-level verification. Integrity checks can be performed on the vehicle data in the connected vehicle database after data storage to ensure its integrity, facilitating downstream tasks based on the vehicle data. The data verification component performs data verification tasks, including row-level and range-level data integrity checks. If checksum mismatches are found, these data are output for further processing or analysis.

[0050] Based on this, the vehicle network data integrity verification system provided in this manual can effectively manage and verify the integrity of large-scale datasets, especially in scenarios such as vehicle networks that require high reliability and real-time performance.

[0051] See Figure 2 , Figure 2 A flowchart of a method for verifying the integrity of vehicle network data according to an embodiment of this specification is shown, which specifically includes the following steps.

[0052] Step 202: Receive vehicle data generated by the data generation component and store the vehicle data in the vehicle network database. The vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers.

[0053] The data generation component can be understood as a component used to generate vehicle data. This component generates vehicle data and calculates corresponding checksums within a test scenario. Specifically, it adds a row checksum to each row of data during generation to verify the integrity of that row. Simultaneously, it divides the data into blocks based on the timestamp and vehicle identifier, calculating a block checksum for each block's row checksum to verify the block's integrity. Subsequently, during data storage, the vehicle network database also stores vehicle data in blocks according to timestamps and vehicle identifiers.

[0054] In practical applications, the data generation component can also collect data uploaded by vehicles and sensors, and calculate corresponding checksums for this data. After generating or collecting vehicle data, the vehicle data can be stored in the vehicle network database. Specifically, the vehicle data can be passed to the data storage component, which then executes the database storage logic to achieve data storage.

[0055] Step 204: Determine the checkpoint information for the data verification task, and select the data to be checked in the vehicle network database according to the checkpoint information.

[0056] The data verification task can be understood as performing integrity verification on the data stored in the vehicle network database. Specifically, the data verification task can include row data verification tasks and block data verification tasks. The row data verification task involves periodically reading row data from the database, calculating the row checksum for each row, and comparing it with the row checksum field to verify incremental single data entries. The block data verification task involves periodically reading block data from the database, calculating the block checksum for data blocks within a fixed time period (e.g., each hour), and comparing it with the previously calculated block checksum data. It records time periods of mismatch. When reading data, only the block checksum field needs to be read, improving reading speed and enabling verification of incremental datasets.

[0057] In practical applications, to correctly execute data validation tasks, it is necessary to determine the checkpoint information for the data validation task. Checkpoint information can be understood as the validation timestamp information of the data validation task. Based on the checkpoint information, it can be determined which time periods or intervals of data in the database need to be checked in this data validation task. The data to be checked can then be selected based on the checkpoint information; this data is the data whose integrity needs to be checked in this data validation task.

[0058] In practical implementation, since the database stores corresponding row checksums and block checksums during data storage, these checksums are also used for subsequent data verification. This manual uses application data in a vehicle-to-everything (V2X) scenario as an example to illustrate the integrity verification method for V2X data. In this scenario, each row of data includes a timestamp, vehicle identifier, attribute fields, and a row checksum. The timestamp is the time the data was collected, the vehicle identifier is the identifier of the vehicle from which the data originated, the attribute fields contain the vehicle's attribute information such as location and speed, and the row checksum is the checksum of all fields in this row of data. Therefore, the data collected for each vehicle is stored in the form of row data to ensure the accuracy of data storage for each row of data, facilitating subsequent integrity verification of each row of data from the row data perspective. Correspondingly, the row data will be divided into blocks according to fixed time and vehicle identification. A block of data can be understood as a dataset consisting of all row data corresponding to a vehicle within a fixed time period. The dataset metadata is used to record the information required for verification of each data block in the dataset, including fields such as start time, vehicle identification, data volume, and block checksum. The start time is the timestamp of the start of the data block, the vehicle identification is the identification of the vehicle from which the data comes, the data volume is the number of row data contained in the data block, and the block checksum is the overall checksum calculated from the row checksums of all row data in the data block.

[0059] Based on this, by storing and dividing data into row data and block data formats when storing data in the database, and calculating the corresponding row checksum and block checksum during the storage process, the incremental data stored can be accurately obtained when performing subsequent data verification tasks, and data verification can be performed on the incremental data according to different data dimensions, thereby improving the accuracy and efficiency of data verification.

[0060] Furthermore, in order to accurately determine the checkpoint information of the data verification task, it is necessary to first determine the task attribute information of the data verification task. Specifically, determining the checkpoint information of the data verification task includes: determining the task attribute information of the data verification task; obtaining the historical checkpoints corresponding to the data verification task; calculating the target checkpoint based on the task attribute information and the historical checkpoints; and determining the checkpoint information based on the historical checkpoints and the target checkpoint.

[0061] The task attribute information can be understood as the attribute information of the data validation task. This information may include validation dimensions and time information. Based on the task attribute information, the corresponding checkpoint information can be determined. Historical checkpoints can be understood as the start timestamp of the data to be validated in this data validation task, and the target checkpoint can be understood as the end timestamp of the data to be validated in this data validation task. Based on the historical and target checkpoints, the data required for this data validation task can be filtered from the database, i.e., filtered according to the data storage timestamp, providing data support for subsequent data validation.

[0062] In practical applications, task attribute information refers to all parameters or settings related to a specific data verification task. This information guides the specific implementation of data verification. For example, task attribute information may include verification dimension information to specify the data dimension to be verified, such as row data verification and / or block data verification; verification time information to specify the time range for verification, such as start timestamp and end timestamp; and other possible task attributes such as verification frequency, task execution time, and number of times the task is executed.

[0063] In practice, the task attribute information stores the end timestamp of the previous data verification task, which serves as the start timestamp of the current task, i.e., the historical checkpoint. A historical checkpoint typically refers to the data timestamp when the last verification operation was completed; it records the data timestamp reached during the last verification. The target checkpoint represents the timestamp at the end of the current data verification task. Based on the verification time information in the task attribute information and the historical checkpoints, the time point covered by the current verification application can be determined as the target checkpoint. For example, if the task attribute information specifies incremental verification every 10 minutes, and the previous checkpoint (historical checkpoint) is 00:05, then the target checkpoint is 00:15. After determining the historical and target checkpoints, they are used as the checkpoint information for the current data verification task.

[0064] In a specific embodiment of this specification, task attribute information for data verification tasks is determined. This task attribute information includes verification dimension and verification time. Based on the task attribute information, the data verification tasks can be identified as row data verification tasks and block data verification tasks. The verification time for each of the two verification tasks is determined based on the verification time: the row data verification task verifies row data within 5 minutes, and the block data verification task verifies block data within 1 hour. Based on the historical checkpoint 00:00, the target checkpoint for the row data verification task is determined to be 00:05, and the target checkpoint for the block data verification task is determined to be 01:00. Based on the determined target checkpoints for the two verification tasks and the historical checkpoints, the checkpoint information for each verification task is determined. Subsequently, the data to be checked can be filtered according to the checkpoint information.

[0065] Based on this, by identifying the checkpoint information for the data verification task, the checkpoint information can be used to filter the data to be checked, reducing the resource consumption caused by unnecessary full scans. This method is suitable for streaming data processing, effectively managing large-scale datasets, and ensuring data consistency and integrity.

[0066] Furthermore, after determining the checkpoint information, the data to be checked in this data verification task can be selected using the checkpoint information to ensure the reliability of the data verification. Specifically, selecting the data to be checked in the vehicle network database based on the checkpoint information includes: determining the data source corresponding to the data verification task in the vehicle network database; determining the timestamp interval corresponding to the data source based on the historical checkpoints and the target checkpoints; and selecting the data to be checked in the data source based on the timestamp interval.

[0067] In this context, the data source for a data validation task can be understood as the data stored in a database. The data source can be data stored on a specific data node within the database, or data stored on all data nodes across the entire database. The determination of the data source depends on the actual validation requirements. For example, if data validation is needed on data stored on a specific data node, then that data node is the data source, and subsequent data selection for validation will begin from that node. Conversely, if validation is needed on all data within the database, then the entire database will be the data source, and subsequent data selection for validation will begin from that database.

[0068] In practical applications, since historical checkpoints and target checkpoints are timestamps of related data, the timestamp range corresponding to the data source can be determined based on these checkpoints. Based on this timestamp range and the timestamp fields included in the stored data, the data to be checked can be selected from the data source. Once the data source is determined, the next step is to define a timestamp range using the historical checkpoint (the timestamp at the end of the last verification) and the target checkpoint (the timestamp at the end of the current verification plan). This range represents the time frame of all data that may have changed since the last verification. After determining the timestamp range, data whose timestamps fall within this range can be found in the selected data source, and this filtered data can be used as the data to be checked for subsequent data verification.

[0069] In practice, the data source can be a data source table schema in a database. When the data validation task SparkSession is generated, it can define the data source it needs to validate, thereby obtaining the data source corresponding to the data validation task. In a specific embodiment of this specification, the data source table corresponding to the data validation task is determined, and the data to be validated is filtered from the data source table based on checkpoint information.

[0070] Based on this, by determining the data source corresponding to the data verification task, the dataset that needs to be verified can be effectively narrowed down, the verification efficiency can be improved, and the data to be checked can be filtered from the data source according to the checkpoint information to ensure the reliability of the data verification.

[0071] Step 206: Determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum. The data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database.

[0072] The initial checksum can be understood as the checksum calculated when the data to be checked is stored. The initial checksum can be the row checksum corresponding to a row of data or the block checksum corresponding to a block of data. Therefore, the corresponding data dimension information differs for different initial checksums. The data dimension information for the row checksum is the row data dimension, and the data dimension information for the block checksum is the block data dimension.

[0073] In practical applications, when storing each row of data in the database, a corresponding row checksum is calculated based on the specific data fields of the row data. The row checksum is then stored in the database along with the specific data fields as a data field itself. When performing data validation on the row data later, the row checksum corresponding to each row data can be directly parsed from the data fields. Using the row checksum, data validation can be performed on each row data at the row data level, which helps to quickly locate which specific row of data has been changed or corrupted.

[0074] Accordingly, the database divides the row data corresponding to the same vehicle identifier within a fixed time period into blocks, or data chunks. Each block contains all row data within that fixed time period, and the division is specifically implemented according to relevant data conditions. For example, it might divide the data into blocks based on the row data corresponding to each vehicle identifier, thus dividing all the data collected for a single vehicle within a fixed time period into one block. After calculating the block checksum based on the row checksum of all row data within that block, it's easy to subsequently use the block checksum to verify the entire data chunk. This improves efficiency when processing large amounts of data by dividing the data into blocks.

[0075] Furthermore, since the verification dimensions of the data verification task are different, the initial checksum and data dimension information corresponding to the data to be checked are also different. Specifically, determining the initial checksum corresponding to the data to be checked and the data dimension information of the initial checksum includes: parsing the data to be checked to obtain the initial row checksum corresponding to the data to be checked, and determining the data dimension information of the initial row checksum as the row data dimension; and / or, determining a checksum data table, searching for the initial block checksum corresponding to the data to be checked in the checksum data table, and determining the data dimension information of the initial block checksum as the block data dimension.

[0076] In a data validation task that performs row-level validation, the data to be checked is parsed to obtain the checksum field for each row. Based on this checksum field, the initial row checksum for each row is determined, and the data dimension information of the initial row checksum is defined as the row data dimension. In a data validation task that performs block-level validation, a checksum table specifically used to store block checksums is searched in the database. The initial block checksum for each block in the data to be checked, along with the corresponding data dimension information, is then retrieved from this checksum table, defining the block data dimension.

[0077] In practical applications, if row data validation is performed, each row of data in the data to be inspected needs to be validated. This requires first obtaining the row checksum corresponding to each row, determining the data dimension as the row data dimension. This ensures that the target row checksum is calculated according to the corresponding row data dimension, thus completing the row data validation for each row in the data to be inspected. If block data validation is performed, each block of data in the data to be inspected needs to be validated. Since the data to be inspected within a preset time period may include block data of multiple different objects, such as block data corresponding to multiple different vehicle identifiers, the block checksum corresponding to each block can be determined, and the data dimension information is determined as the block data dimension. This ensures that the target block checksum is calculated according to the corresponding block data dimension, thus completing the data validation for each block in the data to be inspected.

[0078] In practice, when performing data validation tasks, whether for row data or block data, the key is to accurately obtain the initial checksum and verify the data integrity based on its data dimension information. A data validation task can simultaneously include both row and block validation of the data to be checked; therefore, row data validation and block data validation tasks can be executed concurrently.

[0079] In a specific embodiment of this specification, after determining the data to be checked, the data verification task is a row data verification task. The initial row checksum corresponding to each row data is parsed from the data to be checked. The initial row checksum can be the row checksum calculated by a predetermined algorithm such as blake2b, CRC, MD5, etc. when each row data is stored. The data dimension information is determined as the row data dimension, and the target row checksum is calculated according to the row data dimension.

[0080] In another specific embodiment of this specification, after determining the data to be checked, the data verification task is a block data verification task. The initial block checksum corresponding to each block data is parsed from the data to be checked. The initial block checksum can be the block checksum calculated by a predetermined algorithm such as blake2b, CRC, MD5, etc. when each block data is stored. After the initial block checksum is calculated, it will be stored in the checksum data table for querying during subsequent block data verification. Specifically, the block checksum corresponding to each block data can be found from the checksum data table according to the timestamp, block number, and other identification information of the block data, and the data dimension information is determined as the block data dimension. The target block checksum is then calculated according to the block data dimension.

[0081] Based on this, by determining the travel checksum and block checksum, it is possible to verify the data to be inspected from different data dimensions, effectively ensuring the integrity and accuracy of the data.

[0082] Step 208: Calculate the target checksum corresponding to the initial checksum according to the data dimension information.

[0083] Once the data dimension information is determined, the target checksum corresponding to the initial checksum can be calculated according to the corresponding data dimension information.

[0084] In practical applications, when the data dimension information is row data dimension, the calculated target checksum is also the target row checksum corresponding to the initial row checksum; when the data dimension information is block data dimension, the calculated target checksum is also the target block checksum corresponding to the initial block checksum.

[0085] In practice, if the data verification task includes row data verification task and block data verification task, the row data verification task and block data verification task can be executed separately, and the corresponding target row checksum or target block checksum can be calculated according to their respective data dimension information.

[0086] Furthermore, the initial checksum includes an initial row checksum, and the data dimension information includes row data dimensions; calculating the target checksum corresponding to the initial checksum according to the data dimension information includes: determining the row data to be checked in the data to be checked according to the row data dimensions; and calculating the target row checksum corresponding to the initial row checksum according to the row data to be checked.

[0087] In this context, with the initial checksum being the initial row checksum and the data dimension information being the row data dimension, the calculated target checksum is the target row checksum. Since the row checksum is calculated based on the data fields of each row, when the data dimension information is determined to be the row data dimension, each row to be checked can be read from the data to be checked. The row to be checked is the row data determined from the data to be checked based on the row data dimension. The corresponding target row checksum is calculated based on the data fields of each row to be checked. Subsequently, the corresponding initial row checksum and the corresponding target row checksum can be compared to complete the row data verification at the row data dimension.

[0088] In practical applications, when performing data validation tasks, a function for calculating row checksums can be registered in advance, and then called subsequently to calculate the corresponding row checksums. For example, the function `spark UDF(UDF, User-Defined Function)` can be registered as a `blake2b` algorithm function, and then the `blake2b` algorithm function can be called to calculate the row checksums.

[0089] In a specific embodiment of this specification, the data dimension information is the row data dimension, indicating that data validation needs to be performed on each row of data. An initial row checksum is determined from the data to be checked, and a target row checksum is calculated based on the data fields of each row by calling the row checksum calculation function. Subsequently, using the initial row checksum and the target row checksum, row data dimension validation can be performed on each row of data to be checked.

[0090] Based on this, by calculating the target row checksum for each row of data to be checked, subsequent row-level verification can be performed using the target row checksum. This effectively completes data verification at the row level, ensuring data integrity and accuracy. Row data verification is suitable for scenarios requiring high-precision data verification, such as financial transaction records and healthcare data management.

[0091] Accordingly, the initial checksum includes an initial block checksum, and the data dimension information includes block data dimensions; calculating the target checksum corresponding to the initial checksum according to the data dimension information includes: determining the block data to be checked in the data to be checked and the row checksum to be calculated corresponding to the block data to be checked according to the block data dimension information; and calculating the target block checksum corresponding to the initial block checksum according to the row checksum to be calculated.

[0092] Specifically, when the initial checksum is the initial block checksum and the data dimension information is the block data dimension, the calculated target checksum is the target block checksum. Since the block checksum is calculated based on the row checksums of all rows contained in the block data, when the data dimension information is determined to be the block data dimension, the target block checksum corresponding to each block data can be calculated based on the row checksums to be calculated for the block data to be checked in the data to be checked.

[0093] In practical applications, each block of data contains rows of data within a preset time period, and each row of data corresponds to its own row checksum. Therefore, the block checksum of the data block can be calculated based on the row checksum of each row of data. This allows the calculation of the block checksum to support incremental data updates. The block checksum corresponding to the current block of data is calculated using the row checksums of existing rows of data. After data is updated and added to the block of data, the block checksum corresponding to the current block of data can be calculated directly using the existing block checksums and the row checksums of the added rows of data, without having to recalculate the block checksum based on the row checksums of all rows of data. This improves the calculation speed of the block checksum during data storage.

[0094] In practice, after determining that the data dimension information is block data dimension, the block data to be inspected in the data to be inspected can be identified. Since the data to be inspected may include multiple block data to be inspected within the same time period, it is necessary to determine the row checksum to be calculated for each block data to be inspected. The row checksum to be calculated can be understood as the row checksum corresponding to all rows contained in each block data to be inspected. Based on the checksum to be calculated for each block data to be inspected, the target block checksum corresponding to each block data to be inspected can be calculated. Subsequently, using the target block checksum and the initial block checksum, data verification at the block data dimension can be performed for each block data to be inspected.

[0095] In a specific embodiment of this specification, the data dimension information is the block data dimension. The block data to be inspected is determined within the data to be inspected. The block data to be inspected consists of a data block composed of row data corresponding to each vehicle identifier within a preset time period. Block data verification needs to be performed based on the block data to be inspected. The row checksum to be calculated for each block data to be inspected is determined. The row checksum to be calculated is the row checksum of the row data in each block data to be inspected. The target block checksum for each cross-data segment to be inspected is calculated based on the row checksum to be calculated.

[0096] Based on this, by calculating the target block checksum for each block of data to be checked, subsequent block verification at the block data level can be performed using the target block checksum. This effectively completes data verification at the block data level, ensuring data integrity and accuracy. Block data verification is applicable to large-scale datasets and scenarios requiring incremental updates, such as log file analysis and distributed storage systems.

[0097] Step 210: Based on the initial checksum and the target checksum, perform the data verification task on the data to be checked to obtain the data verification result.

[0098] After determining the initial checksum and the target checksum, a data verification task can be performed on the data to be checked based on the initial checksum and the target checksum to obtain the data verification result. Specifically, since the data verification task involved in the above embodiment includes row data verification task and block data verification task, the data verification result also includes row data verification result and block data verification result.

[0099] Furthermore, the data verification task is performed on the data to be checked based on the initial checksum and the target checksum to obtain a data verification result, including: performing the data verification task on the row data to be checked based on the initial row checksum and the target row checksum; comparing the initial row checksum and the target row checksum to obtain a row data comparison result corresponding to the row data to be checked; and generating the data verification result of the data verification task based on the row data comparison result.

[0100] In the case where the data dimension information is row data dimension, it means that the data verification task is to perform row data verification. At this time, the row data verification task can be performed by comparing the initial row checksum with the target row checksum. By comparing the initial row checksum with the target row checksum, the row data comparison result corresponding to the row data to be checked is obtained. The row data comparison result can be understood as the verification result corresponding to each row data. The overall data verification result of the data verification task is generated based on the row data comparison result corresponding to each row data.

[0101] In practical applications, the core of row data validation is to compare the initial row checksum of each row to be checked with the target row checksum to verify the integrity and consistency of each row in the data to be checked. By providing data validation at the row data level, the row checksum of each row is compared one by one to ensure the accuracy of each row.

[0102] In a specific embodiment of this specification, the row data to be inspected is the vehicle attribute data uploaded by the vehicle at each time point. By comparing the initial row checksum and the target row checksum of each row data, the row data comparison result corresponding to each row data to be inspected is determined. Based on the row data comparison result, the row data verification result of the data verification task is generated. Subsequently, the row data verification result can be used to determine which rows of data in the data to be inspected have data problems, so as to facilitate the summary report.

[0103] Based on this, by comparing the initial checksum of each row of data with the target checksum, it is possible to effectively detect whether the data has been tampered with, damaged or lost. The determined row data comparison results can accurately and quickly locate the problematic row data, which facilitates rapid processing of data anomalies.

[0104] Accordingly, the data verification task is performed on the data to be checked based on the initial checksum and the target checksum to obtain a data verification result, including: performing the data verification task on the block data to be checked based on the initial block checksum and the target block checksum; comparing the initial block checksum and the target block checksum to obtain a block data comparison result corresponding to the block data to be checked; and generating the data verification result of the data verification task based on the block data comparison result.

[0105] In cases where the data dimension information is block data, a block data verification task can be performed on the block data to be checked using the initial block checksum and the target block checksum. By comparing the initial block checksum with the target block checksum, the block data comparison result of the block data pair to be checked can be obtained. The block data comparison result is the data verification result corresponding to each block data to be checked. Based on the block data comparison result corresponding to each block data, the overall data verification result of the data verification task is generated.

[0106] In practical applications, since the data to be inspected consists of all rows of data within a preset time period, each data block can be divided according to the data block partitioning rules specific to the application scenario. For example, in the vehicle networking application scenario, the row data for each vehicle identifier within the preset time period can be partitioned according to time and vehicle identifier. Furthermore, when reading the data to be inspected, attention must be paid to the issue of data persistence to avoid incomplete data reading and impact on subsequent data verification results if the data block has not yet been persisted to disk during the data verification task.

[0107] In practice, since the data to be checked is determined using historical and target checkpoints from the checkpoint information, when considering data persistence to disk, it's necessary to wait an additional preset time after the timestamp of the target checkpoint. This ensures the data persistence operation is completed, accurately retrieving data between historical and target checkpoints and assembling it into block data. It should be noted that the persistence time can be set according to the specific database's operating configuration; it's sufficient to ensure the preset time covers the time required for a complete row of data to be collected and stored in the database.

[0108] In a specific embodiment of this specification, the block data to be inspected consists of vehicle data with vehicle identifier A within one hour. The block data includes all rows of data for that vehicle. The initial block checksum is compared with the calculated target block checksum. Specifically, the comparison operation can be a join operation between the initial block checksum and the target block checksum to obtain the block data comparison result for the block data to be inspected. The data block comparison result may include "vehicle identifier, start time of the block data, initial block checksum, target block checksum, expected number of data rows in the block data, and actual number of data rows in the block data." The block data comparison result for each block data to be inspected generates the data verification result for the data verification task.

[0109] Based on this, by comparing the initial block checksum of the block data to be inspected with the target row checksum, it is possible to effectively detect whether the block data has been tampered with, damaged or lost. Compared with the row data check dimension, the block data check dimension can improve the data check efficiency.

[0110] Furthermore, in order to facilitate the subsequent execution of the next data verification task, after the completion of this data verification task, it is necessary to update the checkpoints and obtain the data verification results. The method further includes: updating the historical checkpoints according to the target checkpoints to obtain updated historical checkpoints, wherein the updated historical checkpoints are used to determine the checkpoint information of the target data verification task.

[0111] After the current data verification task is completed, the historical checkpoints can be updated based on the target checkpoint of this task, that is, the next checkpoint is used as the checkpoint for the next data verification task. This ensures that the historical checkpoints of each data verification task correspond to the target checkpoint of the previous data verification task, avoiding data verification failures due to incorrect checkpoints.

[0112] In practical applications, after updating the historical checkpoints based on the target checkpoints, the updated historical checkpoints can be obtained. The updated historical checkpoints are used to determine the checkpoint information for the target data verification task, i.e., the next data verification task. In other words, when the next data verification task determines the historical checkpoints, the updated historical checkpoints will be used as the historical checkpoints.

[0113] In practice, proper management of checkpoint information is crucial for ensuring the continuity and accuracy of data verification during the execution of data verification tasks. By updating historical checkpoints as the target checkpoints for the current data verification task, it can be ensured that each data verification task is based on the latest and correct starting point, avoiding data verification failures due to checkpoint errors.

[0114] In a specific embodiment of this specification, the checkpoint information for this data verification task is as follows: the historical checkpoint is 00:00, and the target checkpoint is 00:05. After the completion of this data verification task, the historical checkpoint can be updated using the target checkpoint, resulting in an updated historical checkpoint of 00:05. When determining the checkpoint for the next data verification task, the corresponding historical checkpoint will be the updated historical checkpoint of 00:05, thereby ensuring that the start time of the next data verification task is relative to the end time of the current data verification task, thus ensuring the reliability of the data verification task.

[0115] Based on this, effectively managing and updating checkpoint information in data verification tasks ensures that each verification task is based on accuracy, thereby improving system reliability and data integrity.

[0116] Furthermore, after obtaining the data verification results, data with data anomalies in the data to be inspected can be recorded to facilitate maintenance personnel in repairing the data anomalies. After obtaining the data verification results, the method further includes: determining the damage information of the target damaged data in the data to be inspected based on the data verification results; and storing the damage information in the data verification result table.

[0117] The target damaged data can be understood as data with anomalies in the data to be inspected. The damage information of the target damaged data can be understood as the attribute information corresponding to the target damaged data, such as the data location and data content. The damage information is stored in the data verification result table. The data verification result table can be understood as a data table specifically used to store the data information of abnormal data. The data verification result table can reflect the task execution results of each data verification task and enable maintenance personnel to quickly locate the data anomaly based on the data verification result table, thereby enabling rapid repair of the data anomaly.

[0118] In a specific embodiment of this specification, based on the data verification results, the target damaged data is determined to be the row data of row 100 in the data to be inspected. The damage information of this row data is determined, including the data position of the row data, the initial row checksum and the target checksum of the row data, etc. The damage information is stored in the data verification result table.

[0119] Therefore, by recording and storing the damage information of the target damaged data, the operability and maintainability of the data verification task can be significantly improved. This facilitates the rapid identification of problematic data using the verification results, providing a sufficient basis for subsequent repairs. The data verification result table helps maintenance personnel efficiently complete data repair work.

[0120] This specification provides a method for verifying the integrity of vehicle network data, comprising: receiving vehicle data generated by a data generation component and storing the vehicle data in a vehicle network database, wherein the vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers; determining checkpoint information for a data verification task and selecting data to be checked in the vehicle network database based on the checkpoint information; determining an initial checksum corresponding to the data to be checked, and data dimension information of the initial checksum, wherein the data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data blocks in the vehicle network database; calculating a target checksum corresponding to the initial checksum according to the data dimension information; and performing the data verification task on the data to be checked based on the initial checksum and the target checksum to obtain a data verification result. This method achieves the goal of improving data verification efficiency by determining checkpoint information for a data verification task and selecting data to be checked based on the checkpoint information, enabling the filtering of data to be checked based on the timestamp information at the time of data storage, thereby performing data verification on incremental data. Secondly, by determining the initial checksum of the data to be inspected, as well as the data dimension information of the initial checksum, the target checksum corresponding to the initial checksum can be calculated based on the data dimension information. Thus, the data verification task can be performed using the initial checksum and the target checksum, achieving the purpose of data verification of the data to be inspected from different data dimension information, and ensuring the accuracy and reliability of data verification.

[0121] The following is in conjunction with the appendix Figure 3 Taking the application of the vehicle network data integrity verification method provided in this specification in a navigation software platform as an example, the integrity verification method of the vehicle network data will be further explained. Among other things, Figure 3 This specification illustrates a flowchart of a method for verifying the integrity of vehicle network data according to an embodiment, which includes the following steps.

[0122] Step 302: Determine the task attribute information of the data verification task, obtain the historical checkpoints corresponding to the data verification task, and calculate the target checkpoint based on the task attribute information and historical checkpoints.

[0123] In one feasible approach, the data verification task involves performing row data verification on row data from the past 5 minutes and block data verification on block data from the past 30 minutes. Based on the task attribute information of the data verification task, the historical checkpoint is determined as the target checkpoint 00:00 of the previous data verification task. The target checkpoint for the row data verification task is calculated as 00:05, and the target checkpoint for the block data verification task is calculated as 00:30.

[0124] Step 304: Determine the data source corresponding to the data verification task in the vehicle network database, determine the timestamp range corresponding to the data source based on the historical checkpoints and the target checkpoints, and select the data to be checked from the data source based on the timestamp range.

[0125] In one feasible approach, the data source corresponding to the data verification task is determined within the vehicle-to-everything (V2X) database. This data source includes vehicle data from the V2X database corresponding to the navigation software platform. The timestamp intervals, defined as "00:00-00:05" and "00:00-00:30," are determined based on historical and target checkpoints. Based on these timestamp intervals, the data sources are used to select the row data to be verified and the block data to be verified.

[0126] Step 306: Determine the initial checksum corresponding to the data to be checked, as well as the data dimension information of the initial checksum.

[0127] In one feasible approach, the data to be inspected is parsed to obtain the initial row checksum corresponding to the data to be inspected, and the data dimension information of the initial row checksum is determined as the row data dimension. A checksum data table is determined, and the initial block checksum corresponding to the data to be inspected is found in the checksum data table, and the data dimension information of the initial block checksum is determined as the block data dimension.

[0128] Step 308: Calculate the target checksum corresponding to the initial checksum according to the data dimension information.

[0129] In one feasible approach, the row data to be inspected in the data to be inspected is determined based on the row data dimension. The row data to be inspected is each piece of vehicle data, which may include data such as data upload time, vehicle speed, and vehicle coordinates. The target row checksum corresponding to the initial row checksum is calculated based on the row data to be inspected.

[0130] In one feasible approach, the block data to be inspected in the data to be inspected is determined based on the block data dimension information. The block data to be inspected includes all vehicle data within 30 minutes and the row checksum to be calculated corresponding to the block data to be inspected. The target block checksum corresponding to the initial block checksum is calculated based on the row checksum to be calculated.

[0131] Step 310: Execute the data verification task on the data to be checked based on the initial checksum and the target checksum to obtain the data verification result.

[0132] In one feasible approach, a data verification task is performed on the row data to be inspected based on an initial row checksum and a target row checksum. The initial row checksum is compared with the target row checksum to obtain the row data comparison result corresponding to the row data to be inspected. The data verification result of the data verification task is generated based on the row data comparison result. The data verification result indicates that data loss has occurred for a certain vehicle data.

[0133] In one feasible approach, a data verification task is performed on the block data to be inspected based on the initial block checksum and the target block checksum. The initial block checksum is compared with the target block checksum to obtain the block data comparison result corresponding to the block data to be inspected. The data verification result of the data verification task is generated based on the block data comparison result. The data verification result indicates that vehicle data in a certain data block within the time period is lost.

[0134] Step 312: Update the historical checkpoints based on the target checkpoints to obtain the updated historical checkpoints.

[0135] In one feasible approach, the target checkpoint is "00:30". The historical checkpoint is updated using the target checkpoint to obtain the updated historical checkpoint, which is "00:30" and used as the historical checkpoint for the next data verification task.

[0136] Step 314: Based on the data verification results, determine the damage information of the target damaged data in the data to be inspected, and store the damage information in the data verification result table.

[0137] In one feasible approach, based on the data verification results, the target corrupted data is determined to be a specific row of data and the block of data in the data to be inspected. The corresponding corruption information is determined as the initial checksum, target checksum, data location, and other information of the target corrupted data. The corruption information is stored in the data verification result table, enabling maintenance personnel to quickly locate the corrupted data in the event of data anomalies, facilitating data anomaly repair.

[0138] This specification provides a method for verifying the integrity of vehicle network data. It generates vehicle data using a data generation component, and stores the vehicle data in blocks according to timestamps and vehicle identifiers in a vehicle network database. This allows for subsequent data querying and verification based on data blocks, improving processing efficiency. By determining checkpoint information for the data verification task, and selecting data to be verified in the vehicle network database based on this checkpoint information, the method allows filtering of data requiring verification based on the timestamp information at the time of data storage. This achieves data verification for incremental data, improving verification efficiency. Furthermore, by determining the initial checksum and data dimension information of the data to be verified, the method allows calculation of the target checksum corresponding to the initial checksum. The initial and target checksums are then used to execute the data verification task, achieving data verification from different data dimensions and ensuring the accuracy and reliability of the data verification.

[0139] Corresponding to the above method embodiments, this specification also provides embodiments of a vehicle network data integrity verification device. Figure 4 This specification illustrates a schematic diagram of a vehicle network data integrity verification device according to one embodiment. Figure 4 As shown, the device includes:

[0140] The generation module 402 is configured to receive vehicle data generated by the data generation component and store the vehicle data in a vehicle network database, wherein the vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers.

[0141] Selection module 404 is configured to determine the checkpoint information of the data verification task and select the data to be checked in the vehicle network database according to the checkpoint information;

[0142] The determination module 406 is configured to determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum. The data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database.

[0143] Calculation module 408 is configured to calculate the target checksum corresponding to the initial checksum according to the data dimension information;

[0144] The execution module 410 is configured to perform the data verification task on the data to be checked based on the initial checksum and the target checksum, and obtain the data verification result.

[0145] Optionally, the selection module 404 is further configured to: determine the task attribute information of the data verification task; obtain the historical checkpoints corresponding to the data verification task; calculate the target checkpoint based on the task attribute information and the historical checkpoints; and determine checkpoint information based on the historical checkpoints and the target checkpoints.

[0146] Optionally, the selection module 404 is further configured to: determine the data source corresponding to the data verification task; determine the timestamp interval corresponding to the data source based on the historical checkpoint and the target checkpoint; and select the data to be checked from the data source based on the timestamp interval.

[0147] Optionally, the determining module 406 is further configured to parse the data to be inspected, obtain the initial row checksum corresponding to the data to be inspected, and determine the data dimension information of the initial row checksum as the row data dimension; and / or, determine a checksum data table, search for the initial block checksum corresponding to the data to be inspected in the checksum data table, and determine the data dimension information of the initial block checksum as the block data dimension.

[0148] Optionally, the calculation module 408 is further configured to determine the row data to be checked in the data to be checked based on the row data dimension; and to calculate the target row checksum corresponding to the initial row checksum based on the row data to be checked.

[0149] Optionally, the calculation module 408 is further configured to: determine the block data to be inspected in the data to be inspected, and the row checksum to be calculated corresponding to the block data to be inspected, based on the block data dimension information; and calculate the target block checksum corresponding to the initial block checksum based on the row checksum to be calculated.

[0150] Optionally, the execution module 410 is further configured to perform the data verification task on the row data to be checked based on the initial row checksum and the target row checksum; compare the initial row checksum with the target row checksum to obtain the row data comparison result corresponding to the row data to be checked; and generate the data verification result of the data verification task based on the row data comparison result.

[0151] Optionally, the execution module 410 is further configured to perform the data verification task on the block data to be checked based on the initial block checksum and the target block checksum; compare the initial block checksum with the target block checksum to obtain the block data comparison result corresponding to the block data to be checked; and generate the data verification result of the data verification task based on the block data comparison result.

[0152] Optionally, the device further includes an update module configured to update the historical checkpoints according to the target checkpoints to obtain updated historical checkpoints, wherein the updated historical checkpoints are used to determine the checkpoint information for the target data verification task.

[0153] Optionally, the device further includes a storage module configured to determine damage information of the target damaged data in the data to be inspected based on the data verification result; and store the damage information in a data verification result table.

[0154] This specification provides a vehicle-to-everything (V2X) data integrity verification device, comprising: a generation module configured to receive vehicle data generated by a data generation component and store the vehicle data in a V2X database, wherein the V2X database stores the vehicle data in blocks according to timestamps and vehicle identifiers; a selection module configured to determine checkpoint information for a data verification task and select data to be checked in the V2X database based on the checkpoint information; a determination module configured to determine an initial checksum corresponding to the data to be checked and data dimension information of the initial checksum, wherein the data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data blocks in the V2X database; a calculation module configured to calculate a target checksum corresponding to the initial checksum according to the data dimension information; and an execution module configured to execute the data verification task on the data to be checked based on the initial checksum and the target checksum, and obtain a data verification result. This device achieves the goal of improving data verification efficiency by determining checkpoint information for a data verification task and selecting data to be checked based on the checkpoint information, enabling the filtering of data to be checked based on the timestamp information at the time of data storage, thereby achieving data verification for incremental data. Secondly, by determining the initial checksum of the data to be inspected, as well as the data dimension information of the initial checksum, the target checksum corresponding to the initial checksum can be calculated based on the data dimension information. Thus, the data verification task can be performed using the initial checksum and the target checksum, achieving the purpose of data verification of the data to be inspected from different data dimension information, and ensuring the accuracy and reliability of data verification.

[0155] The above is a schematic scheme of a vehicle network data integrity verification device according to this embodiment. It should be noted that the technical solution of this vehicle network data integrity verification device and the technical solution of the vehicle network data integrity verification method described above belong to the same concept. For details not described in detail in the technical solution of the vehicle network data integrity verification device, please refer to the description of the technical solution of the vehicle network data integrity verification method described above.

[0156] Figure 5A structural block diagram of a computing device 500 according to one embodiment of this specification is shown. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0157] The computing device 500 also includes an access device 540, which enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 540 may include one or more of any type of wired or wireless network interface (e.g., a network interface controller (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0158] In one embodiment of this specification, the above-described components of the computing device 500 and Figure 5 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 5 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0159] Computing device 500 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). Computing device 500 can also be a mobile or stationary server.

[0160] The processor 520 is used to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the above-mentioned vehicle network data integrity verification method.

[0161] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-described method for verifying the integrity of vehicle network data belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above-described method for verifying the integrity of vehicle network data.

[0162] An embodiment of this specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the above-described method for verifying the integrity of vehicle network data.

[0163] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solution of the above-described method for verifying the integrity of vehicle network data. Details not described in detail in the technical solution of the storage medium can be found in the description of the technical solution of the above-described method for verifying the integrity of vehicle network data.

[0164] An embodiment of this specification also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the steps of the above-described method for verifying the integrity of vehicle network data.

[0165] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-mentioned vehicle network data integrity verification method belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-mentioned vehicle network data integrity verification method.

[0166] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0167] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0168] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0169] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0170] The preferred embodiments disclosed above are merely illustrative of this specification. Optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described in this specification. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification.

Claims

1. A method for verifying the integrity of vehicle network data, comprising: The system receives vehicle data generated by a data generation component and stores the vehicle data in a vehicle network database. The vehicle network database stores the vehicle data in blocks according to timestamps and vehicle identifiers. Determine the checkpoint information for the data verification task, and select the data to be checked in the vehicle network database based on the checkpoint information; Determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum. The data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database. Calculate the target checksum corresponding to the initial checksum according to the data dimension information; Based on the initial checksum and the target checksum, the data verification task is performed on the data to be checked to obtain the data verification result.

2. The method according to claim 1, wherein determining the checkpoint information for the data verification task includes: Determine the task attribute information for the data verification task; Obtain the historical checkpoints corresponding to the data verification task, and calculate the target checkpoint based on the task attribute information and the historical checkpoints. Checkpoint information is determined based on the historical checkpoints and the target checkpoint.

3. The method according to claim 2, wherein selecting the data to be inspected in the vehicle network database based on the inspection point information includes: Determine the data source corresponding to the data verification task in the vehicle network database; The timestamp interval corresponding to the data source is determined based on the historical checkpoints and the target checkpoints, and the data to be checked is selected from the data source based on the timestamp intervals.

4. The method according to claim 1, determining the initial checksum corresponding to the data to be inspected, and the data dimension information of the initial checksum, includes: The data to be inspected is parsed to obtain the initial row checksum corresponding to the data to be inspected, and the data dimension information of the initial row checksum is determined as the row data dimension; And / or, A checksum data table is determined, and the initial block checksum corresponding to the data to be checked is found in the checksum data table. The data dimension information of the initial block checksum is determined to be the block data dimension.

5. The method according to claim 4, wherein the initial checksum includes an initial row checksum, and the data dimension information includes row data dimensions; Calculate the target checksum corresponding to the initial checksum according to the data dimension information, including: The row data to be inspected in the data to be inspected is determined based on the row data dimension. Calculate the target row checksum corresponding to the initial row checksum based on the row data to be checked.

6. The method according to claim 4, wherein the initial checksum includes an initial block checksum, and the data dimension information includes block data dimensions; Calculate the target checksum corresponding to the initial checksum according to the data dimension information, including: The block data to be inspected in the data to be inspected and the row checksum to be calculated corresponding to the block data to be inspected are determined based on the block data dimension information. Calculate the target block checksum corresponding to the initial block checksum based on the checksum of the row to be calculated.

7. The method according to claim 5, wherein the data verification task is performed on the data to be checked based on the initial checksum and the target checksum to obtain a data verification result, comprising: The data verification task is performed on the row data to be checked based on the initial row checksum and the target row checksum. By comparing the initial row checksum with the target row checksum, the row data comparison result corresponding to the row data to be checked is obtained; The data verification result of the data verification task is generated based on the row data comparison result.

8. The method according to claim 6, wherein the data verification task is performed on the data to be checked based on the initial checksum and the target checksum to obtain a data verification result, comprising: The data verification task is performed on the block data to be checked based on the initial block checksum and the target block checksum. By comparing the initial block checksum with the target block checksum, the block data comparison result corresponding to the block data to be checked is obtained; The data verification result of the data verification task is generated based on the block data comparison result.

9. The method according to claim 2, after obtaining the data verification result, the method further includes: The historical checkpoints are updated based on the target checkpoints to obtain updated historical checkpoints, wherein the updated historical checkpoints are used to determine the checkpoint information for the target data verification task.

10. The method according to any one of claims 1-9, after obtaining the data verification result, the method further includes: Based on the data verification results, the damage information of the target damaged data is determined in the data to be inspected; The damage information is stored in the data verification result table.

11. A vehicle-to-everything (V2X) data integrity verification system, the system comprising a data generation component, a data storage component, and a data verification component, wherein, The data generation component is used to generate vehicle data and send the vehicle data to the data storage component; The data storage component is used to store the vehicle data in the vehicle network database, and the vehicle network database stores the vehicle data in blocks according to timestamp and vehicle identifier; The data verification component is used to determine the checkpoint information of the data verification task, and select the data to be checked in the vehicle network database according to the checkpoint information; determine the initial checksum corresponding to the data to be checked, and the data dimension information of the initial checksum, wherein the data dimension information includes row data dimension and block data dimension, and the block data dimension corresponds to the data block in the vehicle network database; Calculate the target checksum corresponding to the initial checksum according to the data dimension information; perform the data verification task on the data to be checked based on the initial checksum and the target checksum to obtain the data verification result.

12. A computing device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the vehicle network data integrity verification method according to any one of claims 1 to 10.

13. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the vehicle network data integrity verification method according to any one of claims 1 to 10.

14. A computer program product comprising a computer program or instructions which, when executed by a processor, implement the steps of the vehicle network data integrity verification method according to any one of claims 1 to 10.