Internet of vehicles security system based on DAG lattice block chain and working method
By adopting the DAG lattice blockchain structure in the Internet of Vehicles environment and using the division of labor between trusted centers and roadside unit nodes, the blockchain synchronization and forking problems in the Internet of Vehicles are solved, and security and efficiency are improved, and the Transaction information transmission and blockchain consistency in high dynamic environments.
Patent Information
- Application Number
- CN202410962559.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-17
- Publication Date
- 2024-11-15
AI Technical Summary
In the Internet of Vehicles environment, the single-chain structure leads to difficulty in block synchronization and frequent forking, low TPS, and the unified DAG structure ledger cannot be maintained between nodes, affecting the security and efficiency of the blockchain.
Using a DAG lattice blockchain-based security system, public-private key pairs are generated through a trusted center, and the vehicle node stores the cropped blockchain. The roadside unit nodes act as the full node to perform all blockchain functions, using the Gossip protocol Ensure blockchain consistency and treat transactions as blocks for interchangeable use, reducing account chain coupling.
Avoid frequent updates of blockchains in the region by vehicles, improves overall security of blockchain, reduces account chain coupling, facilitates transmission of transaction information in environments with limited bandwidth and high dynamics, maintains a unified DAG structure ledger, and ensures mobile Blockchain consistency between nodes.
Smart Images

Figure CN118972806A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of Internet of Vehicles security and blockchain technology, and in particular to an Internet of Vehicles security system and a working method based on a DAG lattice blockchain. Background Art
[0002] With the development of wireless communication technology and the automotive industry, the Internet of Vehicles has made significant progress, bringing many conveniences to humans in terms of safety and entertainment. The secure sharing and storage of data in the Internet of Vehicles is the premise for the safe operation of the system. However, the nodes in the Internet of Vehicles face security issues such as centralization, security, privacy, and trust during the communication process.
[0003] Blockchain is a decentralized distributed technology used in non-secure environments. Applying blockchain technology in the Internet of Vehicles environment can solve the security issues of the Internet of Vehicles. There have been many studies on the application of blockchain in the Internet of Vehicles environment, including architecture, identity authentication mechanism, privacy protection, trust management, certificate management, data sharing, etc. The blockchain storage structures currently used in the Internet of Vehicles environment include single chain structure and directed acyclic graph (DAG) structure.
[0004] Due to the dynamic connectivity of the Internet of Vehicles, when a single-chain structure is applied in the Internet of Vehicles environment, there are problems with block synchronization and frequent forks, which also leads to a low TPS of the system. The DAG structure allows the blockchain to fork, allowing transactions to reach parallel consensus, which can greatly improve the TPS of the blockchain system. However, when the DAG structure is applied in the Internet of Vehicles environment, there is still the problem that a unified DAG structure ledger cannot be maintained between nodes.
[0005] In the Internet of Vehicles environment, applications related to the Internet of Vehicles are mainly realized through the interaction between nodes and surrounding nodes, which has the characteristics of local aggregation. For each node, more attention is paid to the transactions generated by the vehicle nodes around it, and the transactions generated by nodes that are not within the communication range do not need to be obtained in real time. Therefore, the present invention proposes a security system and working method for the Internet of Vehicles based on the DAG lattice blockchain, which can take advantage of this feature to consider a new blockchain storage structure to meet the needs of using blockchain in the Internet of Vehicles. Summary of the invention
[0006] The purpose of the present invention is to provide a vehicle networking security system and working method based on DAG lattice blockchain, which avoids frequent updates of local blockchains by vehicles, improves the overall security of blockchains, reduces the coupling between account chains, facilitates transactions to be able to operate asynchronously between account chains, is conducive to the transmission of node transaction information in a vehicle networking environment with limited bandwidth and high dynamics, is conducive to maintaining a unified DAG lattice structure ledger between nodes, and is conducive to maintaining consistent blockchain ledger information between mobile nodes.
[0007] To achieve the above-mentioned purpose, the present invention provides a vehicle networking security system based on DAG lattice blockchain, including a trusted center, a vehicle node and a roadside unit node;
[0008] As an absolutely trusted entity, the trusted center is used to generate public and private key pairs for vehicles and roadside units, and assist roadside units in verifying account information created by blockchain nodes;
[0009] As a lightweight node, the vehicle node has limited storage capacity and stores the pruned blockchain;
[0010] As a full node, the roadside unit node has the characteristics of large storage space and strong computing power. It executes all blockchain functions and stores all transaction records.
[0011] Preferably, the operations performed by the vehicle include generating transactions, verifying transactions, forwarding transactions, and participating in consensus;
[0012] The operations performed by the roadside unit include generating transactions, verifying transactions, forwarding transactions, participating in consensus, and updating vehicle credit scores.
[0013] Preferably, the vehicles and roadside units together form a blockchain network;
[0014] The vehicles communicate with each other and with the roadside units by wireless means;
[0015] Roadside units communicate with each other via wired means and through the Gossip protocol to ensure the consistency of the blockchain.
[0016] Preferably, a component model of a vehicle networking security system based on a DAG lattice blockchain includes nodes, accounts, transactions, and ledgers;
[0017] (1) A node is software running on an entity in a blockchain network, following the relevant blockchain protocols and running all or part of the blockchain-related operations, including generating transactions, verifying transactions, consensus transactions, and storing transactions;
[0018] (2) An account is the identity of a blockchain node participating in the system. For ease of management, each node has only one account.
[0019] (3) A transaction is a series of operations that cause the blockchain to change state. Node behaviors include node creation of accounts, node broadcasting of messages, obtaining messages from other nodes, and roadside units updating vehicle credit scores.
[0020] (4) The ledger is data maintained jointly by all accounts, and each account has an account chain.
[0021] Preferably, the transaction structure of the Internet of Vehicles security system based on the DAG lattice blockchain includes: account creation transaction T acount_create , message sending transaction T message_send , Credit Points Send Transaction T reputation_send and receive transaction T receive .
[0022] Preferably, application scenarios include node account creation, node message broadcasting, obtaining messages from other nodes, and roadside units updating vehicle credit scores.
[0023] Therefore, the present invention adopts the above-mentioned Internet of Vehicles security system and working method based on DAG lattice blockchain, and the beneficial effects are as follows:
[0024] (1) Vehicle nodes can store more vehicle transaction information, avoiding frequent updates of local blockchains by vehicles and improving the overall security of the blockchain;
[0025] (2) The roadside unit node regards a transaction as a block, and transactions and blocks can be used interchangeably, which is conducive to transmission in the bandwidth-limited and highly dynamic Internet of Vehicles environment;
[0026] (3) In the present invention, each account maintains its own account chain, and separates a transaction under the traditional blockchain into a sending transaction and a receiving transaction, which are stored in the sending and receiving account chains respectively, thereby reducing the coupling between account chains and facilitating asynchronous operations of transactions between account chains;
[0027] (4) The present invention is conducive to maintaining a unified DAG structure ledger between nodes, and is conducive to maintaining consistent blockchain ledger information between mobile nodes.
[0028] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 This is a network structure diagram of a vehicle networking security system based on a DAG lattice blockchain of the present invention;
[0030] Figure 2 It is a ledger data structure of a vehicle networking security system based on a DAG lattice blockchain of the present invention;
[0031] Figure 3 It is the account creation transaction structure of the present invention;
[0032] Figure 4 It is the message sending transaction structure of the present invention;
[0033] Figure 5 It is the credit distribution transaction structure of the present invention;
[0034] Figure 6 It is the present invention that receives the transaction structure. DETAILED DESCRIPTION
[0035] The technical solution of the present invention is further described below through the accompanying drawings and embodiments.
[0036] The present invention discloses a vehicle networking security system based on a DAG lattice blockchain, comprising: a trusted center, a vehicle node and a roadside unit node.
[0037] Among them, the trusted center, as an absolutely trusted entity, is used to generate public-private key pairs for vehicles and roadside units, and assist roadside units in verifying the account information created by blockchain nodes; vehicle nodes, as lightweight nodes, have limited storage capacity and store the pruned blockchain; roadside unit nodes, as full nodes, have the characteristics of large storage space and strong computing power, and can execute all blockchain functions and store all transaction records.
[0038] In the system, the operations performed by vehicles include: generating transactions, verifying transactions, forwarding transactions, and participating in consensus; the operations performed by roadside units include: generating transactions, verifying transactions, forwarding transactions, participating in consensus, and updating vehicle credit scores.
[0039] Example
[0040] 1. Internet of Vehicles security system model based on DAG lattice blockchain.
[0041] like Figure 1 As shown in the figure, in the system, vehicles and roadside units together form a blockchain network. When vehicles and roadside units join the blockchain network, they first obtain the public and private key pairs through the trusted center; then the public key is added to the blockchain as an account.
[0042] Vehicles communicate with each other and with roadside units wirelessly, such as DSRC, 5G, etc. Roadside units communicate with each other by wire, and they communicate with each other through the Gossip protocol to ensure the consistency of the blockchain.
[0043] The entities of this system mainly include: trusted center, vehicles and roadside units.
[0044] 1. The trusted center is an absolutely trusted entity that generates public and private key pairs for vehicles and roadside units, and assists roadside units in verifying account information created by blockchain nodes.
[0045] 2. As a lightweight node, the vehicle has limited storage capacity and stores a pruned blockchain. In order for the vehicle to verify transactions and participate in consensus, the pruned blockchain stored by the vehicle should at least contain account creation transactions, the latest message-related transactions, and credit score-related transactions for the vehicle itself and other vehicles around it.
[0046] When a vehicle is moving, the surrounding vehicles are constantly changing, causing the vehicle to frequently update the local pruned blockchain. Therefore, in order to avoid frequent updates of the local blockchain by the vehicle, the Internet of Vehicles security system based on the DAG lattice blockchain can encourage vehicles to store more vehicle transaction information and improve the overall security of the blockchain.
[0047] 3. As a full node, the roadside unit has the characteristics of large storage space and strong computing power. It can execute all blockchain functions and store all transaction records.
[0048] Updating credit scores requires a large amount of computing power, a complex calculation process, and transaction information from other vehicles, so it is completed by a roadside unit that executes a full node.
[0049] For messages sent by nodes, the roadside unit must judge whether the messages are true or false. If it is found that a false message is sent, its credit points will be deducted; if a true message is sent, its credit points will be rewarded. Nodes with high credit points have more opportunities to generate blocks and obtain rewards, and the messages generated are processed first; for nodes with low credit points, messages are not accepted by other nodes and cannot receive priority services.
[0050] Therefore, the system model proposed by the present invention can help the vehicle maintain normality through the above-mentioned judgment criteria.
[0051] 2. The component model of the Internet of Vehicles security system based on the DAG lattice blockchain, including nodes, accounts, transactions and ledgers.
[0052] 1. Nodes are software running on entities in the blockchain network. They follow the relevant protocols of the blockchain and run all or part of the blockchain-related operations, including generating transactions, verifying transactions, consensus transactions, storing transactions, etc. In this system, both vehicles and roadside units participate in the blockchain network as blockchain nodes and jointly maintain the blockchain.
[0053] The nodes running on the vehicle are called vehicle nodes, denoted as:
[0054] VNode i ∈{VNode1, VNode2,...,VNode N}
[0055] Where N is the number of vehicles.
[0056] The node running on the roadside unit is called a roadside unit node, denoted as:
[0057] RNode i ∈{RNode1,RNode2,...,RNode M}
[0058] Where M is the number of roadside units.
[0059] 2. The account is the identity of the blockchain node participating in the system. For ease of management, each node has only one account.
[0060] Each account consists of a public-private key pair {P r , S r}. Among them, the public key P r The entire network is open to the public and is used to identify each account; the private key S r The account is kept by itself and is not disclosed to the public. The public and private key pairs of the account are generated by the trusted center, which is an absolutely reliable basic service facility that will not be attacked maliciously. It is also used to generate identity authentication, issue certificates, etc.
[0061] Before joining the blockchain network, vehicle nodes and roadside unit nodes must first generate a public-private key pair through a trusted center. The public-private key pair of a vehicle account is generated through the fixed attributes of the vehicle (vehicle license plate, vehicle type, vehicle manufacturer, and owner information); the public-private key pair of a roadside unit account is generated through the fixed attributes of the roadside unit (number).
[0062] The system includes vehicle accounts and roadside unit accounts, which represent vehicle nodes and roadside unit nodes respectively.
[0063] The vehicle account is recorded as:
[0064] VAC i ∈{VAC1,VAC2,…,VVAC N}
[0065] Where N is the number of vehicles.
[0066] The roadside unit account is recorded as:
[0067] RAC i ∈{RAC1,RAC2,...,RAC M}
[0068] Where M is the number of roadside units.
[0069] 3. A transaction is a series of operations that cause the state of the blockchain to change.
[0070] In traditional blockchain, multiple transactions need to be packaged into a block, which is then stored in the blockchain after verification and consensus. However, it takes a certain amount of time to package blocks, and the packaged blocks are generally large, which is not conducive to transmission in the highly dynamic and bandwidth-limited Internet of Vehicles environment.
[0071] Therefore, in the system proposed in the present invention, a transaction is regarded as a block, and transaction and block can be used interchangeably.
[0072] In traditional blockchain, all accounts maintain a chain, one operation is regarded as a transaction, and one transaction may involve two accounts, which is not conducive to asynchronous transactions between account chains. For the blockchain based on lattice structure proposed by the present invention, each account maintains its own account chain, and separates a transaction under the traditional blockchain into sending transactions and receiving transactions, which are stored in the sending and receiving account chains respectively, reducing the coupling between account chains and facilitating asynchronous operations of transactions between account chains.
[0073] In the Internet of Vehicles environment, the main behaviors of nodes include node account creation, node message broadcasting, receiving messages from other nodes, and roadside units updating vehicle credit scores.
[0074] Therefore, the transaction types involved include: Account creation transaction T acount_create , message sending transaction T message_send , Credit Points Send Transaction T reputation_send , receive transaction T receive .
[0075] Among them, the account creation transaction T acount_create Used to create a node account; message sending transaction T message_send and receive transaction T receive Appear in pairs and complete a message sending together; credit points send transaction T reputation_send and receive transaction T receive Appear in pairs and jointly complete a credit score update operation.
[0076] Special note: account creation transaction T acount_create Only one account is involved, so no corresponding receiving transaction is required.
[0077] 4. The ledger is data maintained jointly by all accounts, and each account has an account chain.
[0078] For each account, the transaction content on the account chain includes: transactions related to messages and transactions related to credit points. In order to improve the transaction processing speed, facilitate transaction query, and asynchronously process transactions related to messages and transactions related to credit points, this article divides the account chain into a message chain (Message Chain) and a credit chain (ReputationChain) for storage. The ledger adopts a DAG lattice structure for storage, such as Figure 2 shown.
[0079] The Genesis Block is generated by the system at initialization. It is the parent block of all account creation transactions. The account creation transaction is the genesis transaction of the account chain. The message chain and credit sub-chain are linked to the account creation transaction T acount_create Among them, the message sending transaction and the receiving transaction exist in pairs and must be referenced by the corresponding receiving transaction; similarly, the credit point sending transaction and the receiving transaction exist in pairs and must be referenced by the corresponding receiving transaction.
[0080] The change of node credit score is caused by the behavior of the node. The behavior of the node refers to whether the node sends the correct message, that is, the behavior of the node can be reflected by the message sending transaction; similarly, the credit score sending transaction must reference the corresponding message sending transaction that causes the credit score change.
[0081] 3. The transaction structure of the Internet of Vehicles security system based on the DAG lattice blockchain.
[0082] 1. Account creation transaction T acount_create .
[0083] To create an account, the blockchain node must first send a Figure 3 The account creation transaction shown. Among them, the type field identifies the type of transaction, and its value is account_create; the account field indicates the account address to be created; difficulty is the difficulty of proof of work; nonce is a random number that meets the difficulty of PoW; the timestamp field indicates the time when the transaction was created; signature is the signature of the account sending the transaction, which can make the signing account unable to deny its signature on the one hand, and on the other hand, it can also determine whether the transaction content has been tampered with by malicious nodes, thereby ensuring the integrity of the information transmission process; signature is the hash value of the transaction content (except the signature field) encrypted by the transaction generator using his own private key, that is,
[0084] signature=E Sr {H1(type,account,nonce,difficulty,timestamp)}
[0085] Among them, S r is the private key of the transaction generator, and H1 is the hash algorithm.
[0086] 2. Message sending transaction T message_send .
[0087] When a node sends a message, it first needs to send a Figure 4The message sending transaction shown. Among them, the type field identifies the type of transaction, and its value is message_send; the previous field identifies the hash value of the previous block; the source field is the account address that sends the transaction; the destination field is the account address that receives the transaction; the msg field is used to indicate the message sent, including desc and content. desc is the description information of content, and content refers to the specific content of the message to be sent, including the public content plaintext_cont and the encrypted content ciphertext_cont. desc and plaintext_cont are displayed in plain text in the transaction, and other nodes can view them directly; ciphertext_cont is displayed in ciphertext in the transaction, and can only be decrypted and viewed with the decryption key after the sender authorizes it. signature is generated by the transaction generator using his own private key to encrypt the hash value of the transaction content (except the signature field), that is,
[0088] signature=E Sr {H1(type,previous,source,
[0089] destination,nonce,difficulty,timestamp,msg)}
[0090] Among them, S r is the private key of the transaction generator, and H1 is the hash algorithm.
[0091] 3. Credit points send transaction T reputation_send .
[0092] When the roadside unit updates the node's credit information, it needs to send a Figure 5 The credit score sending transaction shown. The type field identifies the type of transaction, and its value is reputation_send; the destination field indicates the account address of the node (vehicle or roadside unit) whose credit score needs to be updated; the associate field is the hash value of the corresponding transaction that causes the node's credit score to change, which is used to associate the node's credit score change with the node's behavior; the reputation field records the node's credit score, where desc describes the node's credit score update method, and score records the node's updated credit score; timestamp dest It is the timestamp when the node whose credit score is updated signs the transaction; signature and signature dest They respectively represent the signatures of the transaction by the transaction generator (i.e. the roadside unit that updates the node credit score) and the node whose credit score is updated.
[0093] Since the credit score update is completed through the roadside unit, the credit score needs to be recorded on the credit score chain of the updated credit score node. Therefore, the updating node (roadside unit) and the updated node need to jointly sign the transaction before the credit score update can take effect and be added to the credit score chain.
[0094] By using the joint signature method, the updated node can track the credit score changes and avoid the updated node from modifying the credit score. At the same time, it can prevent the roadside unit from being attacked and maliciously updating the node's credit score. dest The hash value of the field is encrypted and generated, that is,
[0095]
[0096] Among them, S r is the private key of the transaction generator, and H1 is the hash algorithm. dest The node whose credit score is updated uses its own private key to verify the transaction content (except signature and dest The hash value of the field is encrypted and generated, that is,
[0097]
[0098] in, It is the private key of the node whose credit score is updated, and H1 is the hash algorithm.
[0099] 4. Receive transaction T receive .
[0100] When a node receives a message sending transaction or a credit sending transaction, it needs to send a Figure 6 The receiving transaction shown. The type field is used to identify the type of receiving transaction; if a receiving transaction is initiated for a message sending transaction, the type field is message_receive; if a receiving transaction is initiated for a credit point sending transaction, the type field is reputation_receive. The destination field indicates the account address of the receiving transaction, which is consistent with the content of the source field; the associate field points to the hash value of the corresponding sending transaction, which is used to associate the receiving transaction with the sending transaction. The signature is generated by the transaction generator using his own private key to encrypt the hash value of the transaction content (except the signature field), that is,
[0101]
[0102]
[0103] Among them, S r is the private key of the transaction generator, and H1 is the hash algorithm. Only when the receiving transaction and the corresponding sending transaction are both agreed upon and added to the blockchain, an operation can be considered completed.
[0104] 4. The working process of the Internet of Vehicles security system based on DAG lattice blockchain.
[0105] In the Internet of Vehicles environment, driving safety and traffic efficiency are enhanced and intelligent traffic management is achieved mainly through communication between vehicles or between vehicles and roadside units.
[0106] Therefore, in the system proposed by the present invention, the application scenarios mainly include node account creation, node message broadcasting, message acquisition from other nodes, and roadside unit updating vehicle credit score. In the Internet of Vehicles security system based on DAG lattice blockchain, the working methods of the above four application scenarios are as follows:
[0107] 1. Create a node account.
[0108] When a node first joins the blockchain, it needs to create an account. The specific process is as follows:
[0109] S11, node A∈VNode i ||RNode i Register information in the trusted center and obtain the public and private key pair
[0110] S12. Node A generates an account creation transaction T acount_create , sign the transaction and send it to the roadside unit; the account field is the public key of node A
[0111] S13. The roadside unit B∈RNode that receives the transaction i Verify the public key account through a trusted center Whether it has been registered in the trusted center.
[0112] S14. If the verification is successful, the transaction is verified and consensus is reached, and it is added to the account chain of the account as the genesis transaction of the account.
[0113] 2. The node broadcasts the message.
[0114] Vehicles or roadside units need to frequently broadcast some warning messages, road condition messages, early warning messages, etc. to improve driving safety and communication efficiency. The specific process is as follows:
[0115] S21, node A∈VNodei ||RNode i Generate message and send transaction T message_send , sign and broadcast to surrounding nodes.
[0116] It should be noted that since the broadcast message has no specific destination node, and the transaction corresponding to the message needs to be stored on the message chain of node A, the content of the destination field is the same as the source field, which is the account address of node A. desc Recorded in the desc field of msg, the content info that can be publicly accessed by other nodes pub Recorded in the plaintext_cont field, the content that needs to be authorized for other nodes to access info auth After encryption, it is recorded in the ciphertext_cont field, i.e.
[0117] ciphertext_cont=E A P r (info auth )
[0118] S22. After receiving the transaction sent by node A, other nodes verify and reach consensus on the transaction and add it to the message chain of node A.
[0119] S23, T message_send After joining the blockchain, node A generates and receives transaction T receive , sign and send the transaction to the network.
[0120] S24, other nodes receive T receive After that, the transaction is verified and consensus is reached, and it is added to the message chain of node A.
[0121] 3. Get messages from other nodes.
[0122] Node B∈VNode in the network i ||RNode i Need to send to other nodes A∈VNode i ||RNode i To obtain content, or to obtain access rights to the encrypted content on the message chain from node A. For node A, if it decrypts the ciphertext on the blockchain each time, then encrypts it with node B's public key, and then sends it to node B, it will undoubtedly cause great trouble to node A as the data owner. Therefore, the proxy re-encryption technology is adopted, and node A only needs to encrypt the ciphertext with the re-encryption key and send it to node B. The specific process of node B obtaining messages from node A is as follows:
[0123] S31, Node B generates a message to send transaction T message_send , signed and broadcast to surrounding nodes; the destination field is the account address of node A, and the desc field of the msg field records the name of the content obtained from node A or the hash value of a block on the message chain of node A.
[0124] S32. Other nodes receive transaction T message_send After that, the transaction is verified and agreed upon, and added to the message chain of node B.
[0125] S33. Node A generates and receives transaction T receive , and sends the transaction to the network for consensus; at the same time, node A generates the message ciphertext Data according to the content that node B needs to obtain Encry .
[0126] Among them, generate Data Encry The process is as follows:
[0127] S331, node A uses its own common key and Node B's public key Generate re-encryption key Re-Key A→B .
[0128] S332, Node A generates data Data to be sent to Node B s ; If the content that node B needs to obtain is ordinary content C that is not on the blockchain comm , then we need to comm Encryption, then
[0129]
[0130] If the content that node B needs to obtain is content M on the blockchain that requires authorized access encry ,but
[0131] Data s =M encry
[0132] S333, Node A uses the re-encryption algorithm Re-Enc to send the data Data to Node B s Encryption, then
[0133] Data Encry =Re-Enc(Data s ,Re-Key A→B )
[0134] S34, Node A generates a message to send transaction T message_send, sign and broadcast to surrounding nodes; the destination field is the account address of node B, and the ciphertext Data of the message needs to be sent to node B Encry Recorded in the ciphertext_cont field.
[0135] S35. After receiving the received transaction, other nodes verify and reach consensus on the transaction and add it to the message chain of node A.
[0136] S36, Node B decrypts Data using its own private key Encry Get the required content and generate the receiving transaction T receive , and sends the transaction to the network.
[0137] S37. After receiving the received transaction, other nodes verify and reach consensus on the transaction and add it to the message chain of the corresponding account of node B.
[0138] 4. RSU updates vehicle credit score.
[0139] Roadside unit node A∈RNode in the network i According to other nodes B∈VNode i ||RNode i The credit score of node B is updated by the behavior of the node, and node B is incentivized or punished by updating the information score.
[0140] The specific process of node A updating node B's credit score is as follows:
[0141] S41, Node A generates credit points and sends transaction T reputation_send , signed and sent to node B; where the destination field is the account address of node B, the associate field is the hash value of the corresponding transaction that causes the change in node B's credit score, the desc of the reputation field describes the update method of node B's credit score, and the score field records the updated credit score of node B.
[0142] S42. After receiving the transaction, Node B verifies the transaction. After verification, it adds the timestamp dest The field records the current time, signs the transaction again, and broadcasts it to surrounding nodes; at the same time, node B generates a receiving transaction T receive , and sends the transaction to the network.
[0143] S43. After receiving the credit point sending transaction, other nodes verify and reach consensus on the transaction and add it to the message chain of the corresponding account of node B.
[0144] S44. Transaction T reputation_sendAfter joining the blockchain, node B generates and receives transaction T receive , sign and send the transaction to the network.
[0145] S45. After receiving the received transaction, other nodes verify and reach consensus on the transaction and add it to the message chain of the corresponding account of node B.
[0146] Therefore, the present invention adopts the above method to avoid frequent updates of the local blockchain by the vehicle, improve the overall security of the blockchain, reduce the coupling between account chains, facilitate asynchronous operations of transactions between account chains, and facilitate the transmission of node transaction information in a bandwidth-limited and highly dynamic Internet of Vehicles environment, and facilitate the maintenance of a unified DAG lattice structure ledger between nodes, and facilitate the maintenance of consistent blockchain ledger information between mobile nodes.
[0147] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that they can still modify or replace the technical solution of the present invention with equivalents, and these modifications or equivalent replacements cannot cause the modified technical solution to deviate from the spirit and scope of the technical solution of the present invention.
Claims
1. A vehicle networking security system based on DAG lattice blockchain, characterized by: Includes trusted centers, vehicle nodes, and roadside unit nodes; As an absolutely trusted entity, the trusted center is used to generate public and private key pairs for vehicles and roadside units, and assist roadside units in verifying account information created by blockchain nodes; As a lightweight node, the vehicle node has limited storage capacity and stores the pruned blockchain; As a full node, the roadside unit node has the characteristics of large storage space and strong computing power. It executes all blockchain functions and stores all transaction records.
2. According to claim 1, a vehicle networking security system based on DAG lattice blockchain is characterized in that: Operations performed by the vehicle, including generating transactions, verifying transactions, forwarding transactions, and participating in consensus; The operations performed by the roadside unit include generating transactions, verifying transactions, forwarding transactions, participating in consensus, and updating vehicle credit scores.
3. According to claim 1, a vehicle networking security system based on DAG lattice blockchain is characterized in that: Vehicles and roadside units together form a blockchain network; The vehicles communicate with each other and with the roadside units by wireless means; Roadside units communicate with each other via wired means and through the Gossip protocol to ensure the consistency of the blockchain.
4. According to claim 1, a vehicle networking security system based on DAG lattice blockchain is characterized in that: The component model of the Internet of Vehicles security system based on the DAG lattice blockchain, including nodes, accounts, transactions, and ledgers; (1) A node is software running on an entity in a blockchain network, following the relevant blockchain protocols and running all or part of blockchain-related operations, including generating transactions, verifying transactions, consensus transactions, and storing transactions; (2) An account is the identity of a blockchain node participating in the system. For ease of management, each node has only one account. (3) A transaction is a series of operations that cause the blockchain to change state. Node behaviors include node creation of accounts, node broadcasting of messages, obtaining messages from other nodes, and roadside units updating vehicle credit scores. (4) The ledger is data maintained jointly by all accounts, and each account has an account chain.
5. According to claim 1, a vehicle networking security system based on DAG lattice blockchain is characterized in that: The transaction structure of the Internet of Vehicles security system based on the DAG lattice blockchain includes account creation transaction T acount_create , message sending transaction T message_send , Credit Points Send Transaction T reputation_send and receive transaction T receive .
6. The vehicle networking security system based on DAG lattice blockchain according to claim 1 is characterized by: Application scenarios include node account creation, node message broadcasting, receiving messages from other nodes, and roadside units updating vehicle credit scores.
Citation Information
Patent Citations
Collaborative caching method based on lightweight block chain in Internet of Vehicles environment
CN110535687A
Decentralized identity authentication device and method for privacy protection of Internet of Vehicles
CN112437108A
Access control method and device based on block chain, and storage medium
CN115643577A
