Vehicle driving data storage method, device and equipment and storage medium

Abstract

The invention discloses a vehicle driving data storage method, device and equipment and a storage medium, and relates to the technical field of data storage, and the method comprises the steps: obtaining the original driving data of a target vehicle uploaded by a vehicle machine system; caching the original driving data based on the holder identity information ciphertext of the target vehicle to obtain all driving data cached in a first preset time period corresponding to the holder identity information ciphertext; the holder identity information ciphertext is a ciphertext obtained by encrypting the holder identity information through an asymmetric encryption algorithm by the vehicle machine system; and processing all the driving data by using a Hash algorithm, and storing the processed data to a distributed block chain network. In this way, the management node can perform hash processing on the identity information ciphertext of the owner of the vehicle and the vehicle driving data, and store the information to the distributed block chain network; and if the data is changed, the hash value is also changed, so that the non-tampering property of the data is improved, and the credibility of the driving data is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of data storage, and in particular to a vehicle driving data storage method, device, equipment and storage medium. Background Art

[0002] The vehicle driving data system relies on offline entity support. Traditional vehicle driving data is generated by vehicle driving, including but not limited to real-time vehicle operation and driving behavior. After the user generates the data, it is stored in a local file. After a dispute occurs between a car dealer and the actor, the vehicle driving data can often be used as key evidence. Since the vehicle driving data is provided by the car dealer, it is impossible to determine whether the data has been modified after it is obtained, and where the data has been modified.

[0003] In summary, how to store vehicle driving data to prevent the vehicle driving data from being tampered with and ensure the accuracy of the data is a technical problem that needs to be solved urgently. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide a vehicle driving data storage method, device, equipment and storage medium, which can store vehicle driving data encrypted by hash through blockchain to prevent vehicle driving data from being tampered with and ensure the accuracy of the data. The specific scheme is as follows:

[0005] In a first aspect, the present application provides a method for storing vehicle driving data, which is applied to a management node, where the management node is a node registered by a vehicle sales service provider in a distributed blockchain network, including:

[0006] Obtain the original driving data of the target vehicle uploaded by the vehicle system;

[0007] The original driving data is cached based on the ciphertext of the owner identity information of the target vehicle to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the owner identity information; the ciphertext of the owner identity information is the ciphertext obtained by encrypting the owner identity information by the vehicle system through an asymmetric encryption algorithm;

[0008] All the driving data are processed using a hash algorithm, and the processed data are stored in a distributed blockchain network.

[0009] Optionally, before obtaining the original driving data of the target vehicle uploaded by the vehicle system, the method further includes:

[0010] The vehicle system determines the public key and private key of the corresponding asymmetric encryption algorithm according to the identity information of the corresponding holder;

[0011] The holder identity information is encrypted using the public key to obtain the holder identity information ciphertext, so as to cache the original driving data based on the holder identity information ciphertext of the target vehicle.

[0012] Optionally, after obtaining the ciphertext of the holder identity information, the method further includes:

[0013] The vehicle system performs hash encryption on the ciphertext of the holder's identity information to obtain a corresponding identity information hash value;

[0014] Accordingly, the caching of the original driving data based on the ciphertext of the identity information of the owner of the target vehicle includes:

[0015] The original driving data is cached based on the identity information hash value corresponding to the ciphertext of the identity information of the holder of the target vehicle.

[0016] Optionally, the obtaining of original driving data of the target vehicle uploaded by the vehicle system includes:

[0017] Generating original driving data including the identity information hash value and driving status information of the target vehicle through the vehicle computer system; the driving status information is information in plain text form or information in cipher text form encrypted by the public key;

[0018] The original driving data generated within a second preset time period uploaded by the vehicle system is obtained.

[0019] Optionally, the caching of the original driving data based on the ciphertext of the holder identity information of the target vehicle to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the holder identity information includes:

[0020] Determine whether there is a target cache space containing the identity information of the owner of the target vehicle in the locally cached historical driving data;

[0021] If the target cache space does not exist, creating a target cache space for caching the original driving data based on the holder identity information ciphertext, and caching the original driving data into the target cache space, so as to obtain all the driving data cached within the first preset time period corresponding to the holder identity information ciphertext;

[0022] If the target cache space exists, the original driving data is cached in the target cache space to obtain all the driving data cached within the first preset time period corresponding to the holder identity information ciphertext.

[0023] Optionally, the processing of all the driving data using a hash algorithm and storing the processed data in a distributed blockchain network includes:

[0024] At the end of the first preset time period, the ciphertext of the holder identity information, the entire driving data and the corresponding timestamp are hashed to obtain a corresponding data fingerprint;

[0025] All the driving data, the ciphertext of the holder's identity information and the data fingerprint are packaged and processed, and the corresponding packaged data is stored in the distributed blockchain network.

[0026] Optionally, storing the corresponding packaged data in the distributed blockchain network includes:

[0027] Based on the Byzantine fault-tolerant algorithm, consensus verification operations are performed on the packaged data with other management nodes, and the packaged data is stored in the distributed blockchain network after consensus is reached.

[0028] In a second aspect, the present application provides a vehicle driving data storage device, which is applied to a management node, wherein the management node is a node registered by a vehicle sales service provider in a distributed blockchain network, including:

[0029] A data acquisition module is used to acquire the original driving data of the target vehicle uploaded by the vehicle system;

[0030] A data caching module, configured to cache the original driving data based on the ciphertext of the holder identity information of the target vehicle, so as to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the holder identity information; the ciphertext of the holder identity information is the ciphertext obtained by encrypting the holder identity information by the vehicle system through an asymmetric algorithm;

[0031] The data storage module is used to process all the driving data using a hash algorithm and store the processed data in a distributed blockchain network.

[0032] In a third aspect, the present application provides an electronic device, including:

[0033] Memory, used to store computer programs;

[0034] The processor is used to execute the computer program to implement the aforementioned vehicle driving data storage method.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned vehicle driving data storage method is implemented.

[0036] It can be seen that in this application, the management node is a node registered by the vehicle sales service provider in the distributed blockchain network. In the process of storing vehicle driving data, the original driving data of the target vehicle uploaded by the vehicle system is first obtained; then the original driving data is cached based on the ciphertext of the holder identity information of the target vehicle to obtain all the driving data cached within the first preset time period corresponding to the ciphertext of the holder identity information; the ciphertext of the holder identity information is the ciphertext obtained by encrypting the holder identity information by the vehicle system through an asymmetric encryption algorithm; then the hash algorithm is used to process all the driving data, and the processed data is stored in the distributed blockchain network. In this way, the management node can hash the ciphertext of the vehicle's holder identity information and the related vehicle driving data, and store the processed data through the distributed blockchain network; if the data changes on a certain node, the related hash value will also change, which improves the data's immutability and increases the credibility and validity of the driving data. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0038] Figure 1 A flow chart of a vehicle driving data storage method provided by this application;

[0039] Figure 2 A flow chart of a specific vehicle driving data storage method provided by this application;

[0040] Figure 3 A flow chart of a specific vehicle driving data storage method provided by this application;

[0041] Figure 4 A schematic diagram of the structure of a vehicle driving data storage device provided in this application;

[0042] Figure 5 A structural diagram of an electronic device provided for this application. DETAILED DESCRIPTION

[0043] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0044] The vehicle driving data system relies on offline entity support. Traditional vehicle driving data is generated by vehicle driving, including but not limited to real-time vehicle operation and driving behaviors. After the user generates the data, it is stored in a local file. After a dispute occurs between a car dealer and an actor, the vehicle driving data can often be issued as key evidence. Since the vehicle driving data is provided by the car dealer, it is impossible to determine whether the data has been modified after it is obtained, and the location of the data modification. To this end, the present application provides a vehicle driving data storage solution that can store vehicle driving data to prevent the vehicle driving data from being tampered with and ensure the accuracy of the data.

[0045] See also Figure 1 As shown, the embodiment of the present application discloses a vehicle driving data storage method, which is applied to a management node, and the management node is a node registered by a vehicle sales service provider in a distributed blockchain network, and may include:

[0046] Step S11, obtaining the original driving data of the target vehicle uploaded by the vehicle system.

[0047] In this embodiment, for vehicles equipped with the Internet of Vehicles function, the vehicle system can upload the driving data to the management node corresponding to the vehicle sales service provider, and the management node can access the vehicle's driving data through the background system. Specifically, the vehicle system collects the vehicle's driving data in real time through sensors and controllers, and after data preprocessing, it is stored in the internal memory of the vehicle system. After that, the collected driving data can be packaged into data packets, and the driving data in the form of data packets can be uploaded to the designated management node through the built-in communication module. During the data upload process, the vehicle system will authenticate and authorize with the management node to ensure the legitimacy and accuracy of the data.

[0048] It is understandable that before obtaining the original driving data of the target vehicle uploaded by the vehicle system, the process may also include: the vehicle system determines the public key and private key of the corresponding asymmetric encryption algorithm according to the corresponding holder identity information; encrypts the holder identity information using the public key to obtain the holder identity information ciphertext, so as to cache the original driving data based on the holder identity information ciphertext of the target vehicle. Specifically, in this embodiment, the public key and private key of the corresponding asymmetric encryption algorithm can be determined according to the holder identity information. The holder can save the private key by himself or enable cloud hosting under the premise of ensuring data security. The cloud hosting system is a wallet system. In order to ensure the security of the private key, the cloud hosting system adopts distributed shard storage technology to divide the private key into n parts and store them in a distributed file system (i.e., HDFS, Hadoop Distributed File System). At the same time, the cloud hosting system provides a data block backup and recovery mechanism to ensure data reliability and security. When querying the private key, it is necessary to access multiple servers at the same time to obtain the complete private key returned by the server response, so as to further ensure data security. The identity information of the holder includes but is not limited to name, gender, email address, mobile phone number, identity certificate number, registration application timestamp, etc. In this embodiment, the identity information of the holder can be encrypted based on the public key of the asymmetric encryption algorithm to obtain the ciphertext of the identity information of the holder. The asymmetric encryption algorithm includes but is not limited to the RSA algorithm (RSA, i.e. Rivest-Shamir-Adleman), the ECC algorithm (ECC, i.e. Error Correcting Code, error checking and correction), such as the DH algorithm (DH, i.e. Diffie-Hellman, Diffie-Hellman), the ECDH algorithm (ECDH, i.e. Elliptic Curve Diffie-Hellman keyExchange, elliptic curve Diffie-Hellman key exchange), etc.

[0049] In a specific implementation, after obtaining the holder identity information ciphertext, the method may further include: performing hash encryption on the holder identity information ciphertext through the vehicle system to obtain a corresponding identity information hash value; accordingly, caching the original driving data based on the holder identity information ciphertext of the target vehicle may include: caching the original driving data based on the identity information hash value corresponding to the holder identity information ciphertext of the target vehicle. Accordingly, caching the original driving data based on the holder identity information ciphertext of the target vehicle may include: caching the original driving data based on the identity information hash value corresponding to the holder identity information ciphertext of the target vehicle. Specifically, after the holder's identity information is encrypted using the public key and the corresponding holder's identity information ciphertext is obtained, the holder's identity information ciphertext can be hashed using a hash encryption algorithm to obtain a corresponding identity information hash value, so that the original driving data can be cached in the management node using the identity information hash value. The identity information hash value is used as the holder's unique feature code. Each holder has a unique feature code that cannot be repeated, which is equivalent to the holder's unique identity identification code, which is used to ensure the uniqueness of the identification code when uploading data. Among them, the hash encryption algorithm includes but is not limited to the MD5 algorithm (MD5, i.e., Message-DigestAlgorithm 5, a message digest algorithm), the SHA algorithm (SHA, i.e., Secure Hash Algorithm, secure hash algorithm), the CRC algorithm (CRC, i.e., Cyclic Redundancy Check, cyclic redundancy check), etc.

[0050] In this embodiment, the acquisition of the original driving data of the target vehicle uploaded by the vehicle system may include: generating original driving data including the identity information hash value and the driving status information of the target vehicle through the vehicle system; the driving status information is information in plain text or information in cipher text encrypted by the public key; and acquiring each of the original driving data generated within the second preset time period uploaded by the vehicle system. Specifically, the vehicle system of each vehicle may use the identity information hash value corresponding to the holder, i.e., the feature code, in combination with the driving status information of the target vehicle to generate the original driving data. At the same time, the holder may choose to encrypt the driving status information in plain text or with a public key to obtain the original driving data, and the driving status information does not include the holder's identity information to ensure the user's personal privacy. Among them, the driving status information of the vehicle may include throttle and brake positions, seat belt usage, airbag deployment, vehicle speed, temperature, driving time, driving outside probe data, tire speed, engine torque, throttle position, brake position, gear position, air conditioning and other equipment working conditions, vehicle fault information, vehicle geographic location, vehicle historical location, vehicle emission information and other information. After the vehicle system generates the original driving data, the original driving data within the second preset time period is uploaded to the management node based on the identity information hash value corresponding to the holder, that is, the feature code. In this embodiment, it is necessary to set a reasonable second preset time period in combination with the usage scenario and frequency of the vehicle, and the second preset time period is not fixed and can be dynamically adjusted according to actual conditions.

[0051] Step S12: cache the original driving data based on the ciphertext of the holder identity information of the target vehicle to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the holder identity information; the ciphertext of the holder identity information is the ciphertext obtained by encrypting the holder identity information by the vehicle system through an asymmetric encryption algorithm.

[0052] In this embodiment, the caching of the original driving data based on the ciphertext of the holder identity information of the target vehicle to obtain all the driving data cached within the first preset time period corresponding to the ciphertext of the holder identity information may include: determining whether there is a target cache space belonging to the holder identity information of the target vehicle in the historical driving data cached locally; if the target cache space does not exist, creating a target cache space for caching the original driving data based on the ciphertext of the holder identity information, and caching the original driving data to the target cache space to obtain all the driving data cached within the first preset time period corresponding to the ciphertext of the holder identity information; if the target cache space exists, caching the original driving data to the target cache space to obtain all the driving data cached within the first preset time period corresponding to the ciphertext of the holder identity information. Specifically, the management node needs to access the local cache system and search the local cache system for whether there is a target cache space for the ciphertext of the holder identity information or the hash value of the identity information belonging to the target vehicle. If there is enough target cache space, you can continue to use the cache space to store new driving data; if the target cache space is insufficient or does not exist, you need to clean up some historical driving data, increase the cache space, or take other measures to ensure the storage of driving data.

[0053] In a specific implementation, if the local cache system of the management node does not have a target cache space for the holder identity information ciphertext or identity information hash value belonging to the target vehicle, a target cache space for caching the original driving data is created in the local cache system of the management node based on the holder identity information ciphertext or identity information hash value, and the original driving data is cached in the target cache space to obtain all the driving data cached within the first preset time period corresponding to the holder identity information ciphertext or identity information hash value. In another specific implementation, if the local cache system of the management node has a target cache space for the holder identity information ciphertext or identity information hash value belonging to the target vehicle, the original driving data can be cached in the target cache space to obtain all the driving data cached within the first preset time period corresponding to the holder identity information ciphertext or identity information hash value. In the local cache system of the management node, the same holder identity information will accumulate to form historical driving data, and the driving data of the same holder is only accumulated under the same holder identity information. After reaching the first preset time, the management node can obtain all the driving data cached within the first preset time period.

[0054] Step S13: Use a hash algorithm to process all the driving data, and store the processed data in a distributed blockchain network.

[0055] In this embodiment, after the management node obtains all the driving data cached within the first preset time period from the local cache system, it can use the hash algorithm to process all the driving data and store the processed data in the distributed blockchain network. The existence of the cache further improves the throughput of the blockchain system, avoids the performance waste caused by encrypting the holder's identity information every time, and avoids the problem of inconsistent identity information hash values ​​caused by hashing the ciphertext of different holders' identity information, thereby reducing the pressure on the blockchain system.

[0056] As can be seen from the above, in this embodiment, the management node is a node registered by the vehicle sales service provider in the distributed blockchain network. In the process of storing vehicle driving data, the original driving data of the target vehicle uploaded by the vehicle system is first obtained; then the original driving data is cached based on the ciphertext of the holder identity information of the target vehicle to obtain all the driving data cached within the first preset time period corresponding to the ciphertext of the holder identity information; the ciphertext of the holder identity information is the ciphertext obtained by encrypting the holder identity information by the vehicle system through an asymmetric encryption algorithm; then the hash algorithm is used to process all the driving data, and the processed data is stored in the distributed blockchain network. In this way, the management node can hash the ciphertext of the vehicle's holder identity information and the related vehicle driving data, and store the processed data through the distributed blockchain network; if the data changes on a certain node, the related hash value will also change, which improves the data's immutability and increases the credibility and validity of the driving data.

[0057] Through the above embodiments, the vehicle driving data can be obtained based on the identity information of the target vehicle owner, and the data can be uploaded to the distributed blockchain network. Next, in order to further improve the immutability of the driving data, data verification is performed. Figure 2 As shown, the embodiment of the present application further discloses a vehicle driving data storage method, which is applied to a management node, and the management node is a node registered by a vehicle sales service provider in a distributed blockchain network, and may include:

[0058] Step S21: At the end of the first preset time period, the holder identity information ciphertext, the entire driving data and the corresponding timestamp are hashed to obtain a corresponding data fingerprint.

[0059] In this embodiment, at the end of the first preset time period, the management node can use a hash encryption algorithm to hash the holder identity information ciphertext, the entire driving data and the corresponding timestamp to obtain a corresponding data fingerprint. In this way, the driving data and the holder's personal information can be stored after the hash algorithm.

[0060] Step S22: Packaging all the driving data, the ciphertext of the holder's identity information and the data fingerprint.

[0061] It is understandable that the management node packages the driving data, the holder's identity information ciphertext, and the data fingerprint into blocks, and the management node corresponding to a single vehicle sales service provider uploads the data and stores it in the distributed blockchain network. In the distributed blockchain network, each vehicle sales service provider is regarded as a node, and each node can elect different managers through strategies for management. Due to the large number of nodes, when a node changes a certain data, the hash value of the block will change accordingly, and the newly generated content of the node will not be recognized by most nodes, thereby preventing tampering and increasing the credibility and validity of driving data.

[0062] Step S23: Based on the Byzantine fault-tolerant algorithm, consensus verification operations are performed on the packaged data with other management nodes, and the packaged data is stored in the distributed blockchain network after consensus is reached.

[0063] It should be noted that when the consensus verification operation for the packaged data is performed with other management nodes based on the Byzantine fault tolerance algorithm, the driving data packaged into blocks will be sent to all management nodes in the distributed blockchain network, and the sending node will broadcast a request to require other management nodes to verify the packaged data. After receiving the broadcast request, each management node will verify the packaged driving data by checking the integrity of the driving data, the validity of the signature, the rationality of the timestamp, etc., and each management node will exchange information multiple times to ensure that each management node can obtain the verification results of other management nodes. After multiple information exchanges and verifications, if most management nodes believe that the packaged driving data is valid, a consensus can be reached. After reaching a consensus, the distributed blockchain network will record this decision and store the packaged driving data in the distributed blockchain network. In this way, a blockchain consensus is reached between each node, and the holder's identity information and the car driving data are stored after the hash algorithm. If a node changes, the hash value will also change, so that the driving data can be detected to be tampered with.

[0064] After the driving data is stored in the distributed blockchain network, data verification can be further performed. Specifically, the vehicle owner first queries the historical driving data corresponding to the holder's identity information in the distributed blockchain network based on the holder's identity information ciphertext or identity information hash value that can verify the holder's identity, and calls the data without exposing personal privacy. After the data call is successful, the driving data to be verified is obtained, and then the holder's identity information ciphertext in the data to be verified can be decrypted using the private key corresponding to the holder's identity information, and the decrypted holder's identity information ciphertext is compared with the plaintext holder's identity information to obtain the verification result. When retrieving the data, the holder's information will not be exposed. While protecting the holder's privacy, the required driving data and past historical records are retrieved, ensuring the traceability of the information.

[0065] See also Figure 3As shown, in this embodiment, the vehicle sales service provider is regarded as a large member node, and each car is regarded as a scattered small node. The driving record of the car is uploaded to the central network and entered into the blockchain system. The specific process of storing the driving data of the car can be: the vehicle system sends a driving data chain request to the management node; the management node determines whether the identity information of the vehicle holder is a new user; if the vehicle holder is a new user, the holder registers personal purchase information and generates an asymmetric key; the vehicle system encrypts the holder's identity information based on the public key of the asymmetric key, and caches the holder's identity information ciphertext in the relational database; if the vehicle holder is not a new user, the ciphertext cached in the relational database is directly read; then the vehicle system hashes the holder's identity information ciphertext; after each interval n (h, hours), the vehicle's driving status information and identity information hash value are compressed and packaged and uploaded to the management node; finally, after reaching a consensus, the management node stores the data in the distributed blockchain network. That is, the holder applies for public and private keys in combination with identity information including but not limited to name, gender, email address, ID number, etc. The public key is used to encrypt the identity information, and the encrypted holder identity information ciphertext can be cached on the platform network. Further, when the driving data of interval n (h) is uploaded to the chain, the management node can query the holder identity information ciphertext, and obtain the identity information hash value after hashing the holder identity information ciphertext, so as to package the vehicle driving status information and the identity information hash value and upload it to the blockchain. When requesting a transaction, the vehicle's vehicle system initiates a request to the management node corresponding to the vehicle sales service provider, and each management node reaches a consensus and performs distributed storage on the blockchain. The driving data of the car is stored in the distributed blockchain network system. Due to the characteristics of the blockchain, the management nodes of all vehicle sales service providers jointly form a supervisor to ensure the originality and integrity of the data and cannot be tampered with. After the data is stored in the distributed blockchain network, data verification can be performed. In the process of data verification, the cached holder identity information ciphertext can be checked first, and decrypted using the private key. If the decryption results are consistent, it proves that the driving data belongs to the holder, that is, the authenticity can be judged by the decryption results. The private key can be stored in multiple email addresses filled in by the holder when registering, and can be called back simultaneously when needed. And because the private key is stored in the vehicle system, security is greatly improved. On the contrary, if the private key is accidentally lost, the holder of the driving data cannot be verified.

[0066] As can be seen from the above, in this embodiment, the management node hashes and encrypts the ciphertext of the holder's identity information, all driving data and the corresponding timestamp to obtain the corresponding data fingerprint, and then packages all driving data, the ciphertext of the holder's identity information and the data fingerprint for processing, and finally performs consensus verification operations on the packaged data with other management nodes based on the Byzantine fault tolerance algorithm, and stores the packaged data in the distributed blockchain network after reaching a consensus. In this way, the management node can hash the ciphertext of the vehicle's holder's identity information and the related vehicle driving data, and store the processed data through the distributed blockchain network after reaching a consensus; if the data changes on a certain node, the related hash value will also change, which improves the data's immutability and increases the credibility and validity of the driving data.

[0067] Accordingly, see Figure 4 As shown, the embodiment of the present application also provides a vehicle driving data storage device, which is applied to a management node. The management node is a node registered by a vehicle sales service provider in a distributed blockchain network, and may include:

[0068] The data acquisition module 11 is used to acquire the original driving data of the target vehicle uploaded by the vehicle system;

[0069] The data cache module 12 is used to cache the original driving data based on the ciphertext of the owner identity information of the target vehicle to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the owner identity information; the ciphertext of the owner identity information is the ciphertext obtained by encrypting the owner identity information by the vehicle system through an asymmetric algorithm;

[0070] The data storage module 13 is used to process all the driving data using a hash algorithm and store the processed data in a distributed blockchain network.

[0071] As can be seen from the above, the management node in this application can perform hash processing on the ciphertext of the vehicle owner's identity information and the related vehicle driving data, and store the processed data through a distributed blockchain network; if the data changes on a certain node, the related hash value will also change, which improves the data's immutability and increases the credibility and validity of the driving data.

[0072] In some specific embodiments, the device may further include:

[0073] A key determination module, used for the vehicle system to determine the public key and private key of the corresponding asymmetric encryption algorithm according to the corresponding holder identity information;

[0074] The information encryption module is used to encrypt the holder identity information using the public key to obtain the holder identity information ciphertext, so as to cache the original driving data based on the holder identity information ciphertext of the target vehicle.

[0075] In some specific implementations, the information encryption module may further include:

[0076] A ciphertext encryption unit, used to perform hash encryption on the ciphertext of the holder's identity information through the vehicle system to obtain a corresponding identity information hash value;

[0077] Accordingly, the data cache module 12 may include:

[0078] The first data cache unit is used to cache the original driving data based on the identity information hash value corresponding to the ciphertext of the identity information of the owner of the target vehicle.

[0079] In some specific implementations, the data acquisition module 11 may include:

[0080] A data generating unit, configured to generate original driving data including a hash value of the identity information and driving status information of the target vehicle through the vehicle system; the driving status information is information in plain text or information in cipher text encrypted by the public key;

[0081] The data acquisition unit is used to acquire the original driving data generated within a second preset time period uploaded by the vehicle system.

[0082] In some specific implementations, the data cache module 12 may include:

[0083] A conditional judgment unit, used to judge whether there is a target cache space for the identity information of the owner of the target vehicle in the historical driving data cached locally;

[0084] a cache space creation unit, configured to create a target cache space for caching the original driving data based on the holder identity information ciphertext if the target cache space does not exist, and cache the original driving data into the target cache space, so as to obtain all the driving data cached within a first preset time period corresponding to the holder identity information ciphertext;

[0085] The second data cache unit is used to cache the original driving data into the target cache space if the target cache space exists, so as to obtain all the driving data cached within a first preset time period corresponding to the holder identity information ciphertext.

[0086] In some specific implementations, the data storage module 13 may include:

[0087] A data encryption unit, configured to perform hash encryption on the ciphertext of the holder identity information, the entire driving data and the corresponding timestamp at the end of the first preset time period to obtain a corresponding data fingerprint;

[0088] The data storage submodule is used to package all the driving data, the holder's identity information ciphertext and the data fingerprint, and store the corresponding packaged data in the distributed blockchain network.

[0089] In some specific implementations, the data storage submodule may include:

[0090] The data storage unit is used to perform consensus verification operations on the packaged data with other management nodes based on the Byzantine fault tolerance algorithm, and store the packaged data in the distributed blockchain network after reaching a consensus.

[0091] Furthermore, the present application also discloses an electronic device. Figure 5 : This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the figure cannot be regarded as any limitation on the scope of use of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the vehicle driving data storage method disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0092] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0093] In addition, the memory 22 as a carrier for resource storage may be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon may include an operating system 221, a computer program 222, etc., and the storage method may be temporary storage or permanent storage.

[0094] The operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, and can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program that can be used to complete the vehicle driving data storage method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks.

[0095] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the vehicle driving data storage method disclosed above. The specific steps of the method can refer to the corresponding contents disclosed in the above embodiments, and will not be repeated here.

[0096] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0097] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0098] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0099] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0100] The technical solution provided by the present application is introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technicians in this field, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A vehicle driving data storage method, characterized in that: Applied to a management node, the management node is a node registered by a vehicle sales service provider in a distributed blockchain network, the method comprising: Obtain the original driving data of the target vehicle uploaded by the vehicle system; The original driving data is cached based on the ciphertext of the owner identity information of the target vehicle to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the owner identity information; the ciphertext of the owner identity information is the ciphertext obtained by encrypting the owner identity information by the vehicle system through an asymmetric encryption algorithm; All the driving data are processed using a hash algorithm, and the processed data are stored in a distributed blockchain network.

2. The vehicle driving data storage method according to claim 1, characterized in that: Before obtaining the original driving data of the target vehicle uploaded by the vehicle system, the method further includes: The vehicle system determines the public key and private key of the corresponding asymmetric encryption algorithm according to the identity information of the corresponding holder; The holder identity information is encrypted using the public key to obtain the holder identity information ciphertext, so as to cache the original driving data based on the holder identity information ciphertext of the target vehicle.

3. The vehicle driving data storage method according to claim 2, characterized in that: After obtaining the ciphertext of the holder's identity information, the method further includes: The vehicle system performs hash encryption on the ciphertext of the holder's identity information to obtain a corresponding identity information hash value; Accordingly, the caching of the original driving data based on the ciphertext of the identity information of the owner of the target vehicle includes: The original driving data is cached based on the identity information hash value corresponding to the ciphertext of the identity information of the holder of the target vehicle.

4. The vehicle driving data storage method according to claim 3, characterized in that: The obtaining of the original driving data of the target vehicle uploaded by the vehicle system includes: Generating original driving data including the identity information hash value and driving status information of the target vehicle through the vehicle computer system; the driving status information is information in plain text form or information in cipher text form encrypted by the public key; The original driving data generated within a second preset time period uploaded by the vehicle system is obtained.

5. The vehicle driving data storage method according to claim 1, characterized in that: The caching of the original driving data based on the ciphertext of the holder identity information of the target vehicle to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the holder identity information includes: Determine whether there is a target cache space containing the identity information of the owner of the target vehicle in the locally cached historical driving data; If the target cache space does not exist, creating a target cache space for caching the original driving data based on the holder identity information ciphertext, and caching the original driving data into the target cache space, so as to obtain all the driving data cached within the first preset time period corresponding to the holder identity information ciphertext; If the target cache space exists, the original driving data is cached in the target cache space to obtain all the driving data cached within the first preset time period corresponding to the holder identity information ciphertext.

6. The vehicle driving data storage method according to any one of claims 1 to 5, characterized in that: The method of processing all the driving data using a hash algorithm and storing the processed data in a distributed blockchain network includes: At the end of the first preset time period, the ciphertext of the holder identity information, the entire driving data and the corresponding timestamp are hashed to obtain a corresponding data fingerprint; All the driving data, the ciphertext of the holder's identity information and the data fingerprint are packaged and processed, and the corresponding packaged data is stored in the distributed blockchain network.

7. The vehicle driving data storage method according to claim 6, characterized in that: The storing of the corresponding packaged data to the distributed blockchain network includes: Based on the Byzantine fault-tolerant algorithm, consensus verification operations are performed on the packaged data with other management nodes, and the packaged data is stored in the distributed blockchain network after consensus is reached.

8. A vehicle driving data storage device, characterized in that: Applied to a management node, the management node is a node registered by a vehicle sales service provider in a distributed blockchain network, and the device includes: A data acquisition module is used to acquire the original driving data of the target vehicle uploaded by the vehicle system; A data caching module, configured to cache the original driving data based on the ciphertext of the holder identity information of the target vehicle, so as to obtain all the driving data cached within a first preset time period corresponding to the ciphertext of the holder identity information; the ciphertext of the holder identity information is the ciphertext obtained by encrypting the holder identity information by the vehicle system through an asymmetric algorithm; The data storage module is used to process all the driving data using a hash algorithm and store the processed data in a distributed blockchain network.

9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor is used to execute the computer program to implement the vehicle driving data storage method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein, when the computer program is executed by a processor, the vehicle driving data storage method as described in any one of claims 1 to 7 is implemented.

Images