Blockchain-based connected vehicle fleet identity authentication method and device, and medium

Abstract

The application relates to a blockchain-based networked vehicle fleet identity authentication method, device and medium, wherein the method is applied to a roadside device and comprises the following steps: responding to a pseudonym application request of a target vehicle; sending corresponding pseudonym information to the target vehicle based on the pseudonym application request, and feeding pseudonym information issuance records to a cross-domain subnode corresponding to the target vehicle; responding to a vehicle fleet establishment request of the target vehicle; determining fleet identity information based on the identity of a fleet member and the pseudonym information of the target vehicle, and sending the encrypted fleet identity information to vehicles corresponding to the fleet members; and performing member identity authentication of the networked vehicle fleet in the blockchain based on the fleet identity information. Through the application, the problem of high cross-domain authentication complexity in the process of fleet member identity authentication based on a PKI mechanism is solved, and fleet member identity authentication in a dynamic change state of the fleet members is supported, so that the communication security of the fleet members in the dynamic change process is ensured.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a blockchain-based method, device, and medium for authenticating the identity of connected vehicle fleets. Background Technology

[0002] In a connected vehicle environment, intelligent connected vehicles equipped with onboard units (OBUs) can share real-time status information with each other through vehicle-to-everything (V2X) technology, enabling autonomous driving scenarios such as platooning and cooperative driving. By communicating with devices equipped with roadside units (RSUs), intelligent connected vehicles can further enhance their perception of the traffic environment during operation.

[0003] A connected vehicle fleet, consisting of multiple intelligent connected vehicles (ICVs), typically employs a certificate-based PKI mechanism for authentication of communication terminals within the connected vehicle environment to ensure the security of communication based on vehicle-to-everything (V2X) technology. Communication terminals in a connected vehicle environment generally fall into two categories: intelligent connected vehicles equipped with onboard units (OBUs) and devices equipped with roadside units (RSUs). Before communication, each communication terminal in a connected vehicle network needs to apply for a corresponding digital certificate from a Certificate Authority (CA). During communication, the digital certificate is used to sign the communication message, and the signature, along with the digital certificate and the communication message content, is broadcast. When a connected vehicle terminal receives a communication message from another connected vehicle terminal, it verifies the signature using the corresponding digital certificate to ensure the integrity of the message content and the legitimacy of the message source. The vehicles in the above process usually belong to the same trust domain, so they can be authenticated by the same Certificate Authority (CA) using the PKI mechanism. If the vehicles in the fleet belong to different trust domains, different Certificate Authorities (CAs) are needed to authenticate the vehicles in the corresponding trust domains. This requires a higher-level certificate authority to provide a corresponding trust list mechanism to achieve cross-domain authentication. However, achieving cross-domain authentication in this way is highly complex and it is difficult to ensure the security of vehicle privacy information.

[0004] There is currently no effective solution to the problem of high complexity in cross-domain authentication during the identity authentication process of connected vehicle fleets based on PKI mechanism. Summary of the Invention

[0005] This embodiment provides a blockchain-based method, device, and medium for authenticating the identity of connected vehicle fleets, in order to solve the problem of high complexity in cross-domain authentication during the fleet identity authentication process based on PKI mechanism in related technologies.

[0006] Firstly, this embodiment provides a blockchain-based method for authenticating the identity of connected vehicle fleets. The blockchain includes a root node and multiple cross-domain child nodes. The root node generates corresponding node identity information for the multiple cross-domain child nodes and publishes the node public key in each node's identity information to the blockchain. The multiple cross-domain child nodes reach consensus based on each node's identity information. The vehicle network includes roadside devices and vehicles. The root node is also used to register the roadside devices in the vehicle network and publish the registration information of the roadside devices to the blockchain. The multiple cross-domain child nodes are used to register vehicles in the corresponding domains of each cross-domain child node in the vehicle network and publish the vehicle registration information to the blockchain. The method also includes batch generating pseudonym information and distributing the pseudonym information to the roadside devices. The method is applied to the roadside devices and includes:

[0007] In response to a pseudonym request for a target vehicle, wherein the target vehicle is any vehicle in the vehicle network;

[0008] Based on the pseudonym application request, the corresponding pseudonym information is sent to the target vehicle, and the pseudonym information issuance record is fed back to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle synchronizes the pseudonym information issuance record to the blockchain.

[0009] In response to the fleet establishment request of the target vehicle, the fleet establishment request includes the identity identifiers of the fleet members and the pseudonym information of the target vehicle;

[0010] Based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle, the fleet identity information is determined, and the fleet identity information is encrypted and sent to the vehicle corresponding to the fleet member;

[0011] Based on the fleet identity information, the members of the connected fleet are authenticated in the blockchain.

[0012] In some embodiments, determining the fleet identity information based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle includes:

[0013] The identity of the target vehicle is verified based on the pseudonym information of the target vehicle, and the identity verification result of the target vehicle is obtained.

[0014] Based on the identity authentication result of the target vehicle that has passed the authentication, the identity identifier of the fleet member is sent to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle generates fleet identity information according to the identity identifier of the fleet member and publishes the fleet identity information to the blockchain;

[0015] The response is the fleet identity information fed back by the cross-domain sub-node corresponding to the target vehicle.

[0016] In some embodiments, the process of authenticating the membership of the connected vehicle fleet based on the fleet identity information in the blockchain includes:

[0017] In response to the second identity authentication request from the first vehicle to the second vehicle, the second identity authentication request includes the second pseudonym information of the second vehicle, the second fleet identity information of the fleet to which the second vehicle belongs, and the first fleet identity information of the first vehicle to which the first vehicle belongs;

[0018] Based on the second pseudonym information, the pseudonym identity of the second vehicle is authenticated in the blockchain to obtain the pseudonym identity authentication result of the second vehicle.

[0019] Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity information of the second fleet, and the identity information of the first fleet, the consistency between the fleet to which the first vehicle and the second vehicle belong is authenticated to obtain the fleet consistency authentication result.

[0020] The fleet conformity authentication result is fed back to the first vehicle so that the first vehicle and the second vehicle can conduct fleet collaborative communication.

[0021] In some embodiments, the second pseudonym information includes a second pseudonym identity public key, and the authentication of the pseudonym identity of the second vehicle in the blockchain based on the second pseudonym information to obtain the pseudonym identity authentication result of the second vehicle includes:

[0022] The second pseudonym information is sent to the cross-domain sub-node corresponding to the first vehicle, so that the cross-domain sub-node corresponding to the first vehicle can authenticate the registration information of the second vehicle in the blockchain based on the second pseudonym information, and obtain the registration information authentication result.

[0023] The system responds to the registration information authentication result fed back by the cross-domain sub-node corresponding to the first vehicle.

[0024] Based on the authentication result of the successfully authenticated registration information, the validity period of the second pseudonym information is authenticated to obtain the legality authentication result of the second pseudonym information;

[0025] The validity authentication result of the second pseudonym information is fed back to the first vehicle, so that the first vehicle can perform signature authentication on the broadcast information of the second vehicle based on the public key of the second pseudonym identity, and obtain the signature authentication result of the broadcast information of the second vehicle. The broadcast information of the second vehicle is used to transmit the second identity authentication request to the first vehicle.

[0026] The system responds to the signature authentication result of the broadcast information of the second vehicle fed back by the first vehicle, and obtains the pseudonym authentication result of the second vehicle based on the signature authentication result of the broadcast information of the second vehicle.

[0027] In some embodiments, the fleet identity information includes the negotiation keys of fleet members, the fleet identity public key, and the fleet identifier. The second identity authentication request also includes second authentication information of the second fleet, which is generated based on the negotiation keys of the second fleet members and the second fleet identity public key.

[0028] The process of verifying the consistency between the first vehicle and the fleet to which the second vehicle belongs, based on the pseudonym authentication result of the successfully authenticated second vehicle, the identity information of the second fleet, and the identity information of the first fleet, to obtain a fleet consistency authentication result includes:

[0029] Based on the pseudonym authentication result of the second vehicle that has passed authentication, the second fleet identifier of the second fleet is sent to the cross-domain sub-node corresponding to the first vehicle in the blockchain, so that the cross-domain sub-node corresponding to the first vehicle can determine the authentication result of the second fleet identifier in the blockchain;

[0030] In response to the authentication result of the second fleet identifier fed back by the cross-domain sub-node corresponding to the first vehicle, based on the authentication result of the second fleet identifier that has been successfully authenticated, as well as the negotiation key of the first fleet member and the public key of the first fleet identity in the first fleet identity information, the first authentication information of the first fleet is determined.

[0031] Based on the second information to be authenticated and the first authentication information, the consistency between the first vehicle and the fleet to which the second vehicle belong is authenticated, and the fleet consistency authentication result is obtained.

[0032] In some embodiments, the fleet identity information includes a fleet member identity list, which records the vehicle identity information of the fleet members. The process of authenticating the consistency between the fleet to which the first vehicle and the second vehicle belong, based on the pseudonym authentication result of the authenticated second vehicle, the second fleet identity information, and the first fleet identity information, to obtain a fleet consistency authentication result, includes:

[0033] Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity list of the first fleet member corresponding to the first vehicle and the identity list of the second fleet member corresponding to the second vehicle are used to authenticate the consistency of the fleet to which the first vehicle and the second vehicle belong, and obtain the fleet consistency authentication result.

[0034] In some embodiments, after sending the fleet identification information to the vehicles corresponding to the fleet members, the method further includes:

[0035] The system responds to the entry application information of the first target fleet member vehicle for the vehicle to be joined. The entry application information includes the pseudonym information of the first target fleet member vehicle, the identity information of the first target fleet to which the first target fleet member vehicle belongs, and the verification result of the first target fleet member vehicle for the entry request of the vehicle to be joined. The first target fleet member vehicle is any vehicle in the first target fleet, and the first target fleet is any fleet in the blockchain.

[0036] Based on the pseudonym information of the vehicles of the first target fleet members, the pseudonym identity of the vehicles of the first target fleet members is verified in the blockchain to obtain the pseudonym identity verification result of the vehicles of the first target fleet members.

[0037] Based on the pseudonym identity authentication results of the vehicles of the first target fleet members and the identity information of the first target fleet, the fleet identity information of the vehicles of the first target fleet members is authenticated to obtain the fleet authentication results of the first target fleet members;

[0038] The fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined are sent to the cross-domain sub-node corresponding to the vehicle to be joined in the blockchain, so that the cross-domain sub-node corresponding to the vehicle to be joined can determine the joining result of the vehicle to be joined based on the fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined.

[0039] The response determines the queuing result of the vehicle to be enqueued by the cross-domain sub-node corresponding to the vehicle to be enqueued.

[0040] In some embodiments, if the queuing result of the vehicle to be enqueued is "agree to enqueue", the method further includes:

[0041] The identity identifier of the vehicle to be joined is sent to the cross-domain sub-node corresponding to the vehicle to be joined, so that the cross-domain sub-node corresponding to the vehicle to be joined updates the identity information of the first target fleet based on the identity identifier of the vehicle to be joined and the identity identifiers of all member vehicles in the first target fleet, and publishes the updated identity information of the first target fleet to the blockchain;

[0042] In response to the updated identity information of the first target fleet federated by the cross-domain sub-node corresponding to the vehicle to be joined, the updated identity information of the first target fleet is sent to all vehicles of the first target fleet members and the vehicle to be joined.

[0043] In some embodiments, after sending the fleet identification information to the vehicles corresponding to the fleet members, the method further includes:

[0044] In response to the departure request information of the second target fleet member vehicle, the departure request information includes the pseudonym information of the second target fleet member vehicle and the identity information of the second target fleet to which the second target fleet member vehicle belongs. The second target fleet member vehicle is any vehicle in the second target fleet, and the second target fleet is any fleet in the blockchain.

[0045] Based on the pseudonym information of the vehicles of the second target fleet members, the pseudonym identity of the vehicles of the second target fleet members is verified in the blockchain to obtain the pseudonym identity verification result of the vehicles of the second target fleet members;

[0046] Based on the pseudonym identity authentication results of the vehicles of the second target fleet members and the identity information of the second target fleet, the fleet identity information of the vehicles of the second target fleet members is authenticated to obtain the fleet authentication results of the second target fleet members;

[0047] The fleet authentication results of the vehicles of the second target fleet members are sent to the cross-domain sub-nodes corresponding to the vehicles of the second target fleet members, so that the cross-domain sub-nodes corresponding to the vehicles of the second target fleet members update the identity information of the second target fleet and publish the updated identity information of the second target fleet to the blockchain;

[0048] The system responds to the updated identity information of the second target fleet corresponding to the cross-domain sub-nodes of the second target fleet members, and then encrypts and sends the updated identity information of the second target fleet to all vehicles in the second target fleet except for the second target fleet members.

[0049] Secondly, this embodiment provides a blockchain-based fleet identity authentication system. The blockchain includes a root node and multiple cross-domain child nodes. The root node generates corresponding node identity information for the multiple cross-domain child nodes and publishes the node public key in each node identity information to the blockchain. The multiple cross-domain child nodes reach consensus based on each node identity information. The vehicle network includes roadside devices and vehicles. The root node is also used to register the roadside devices in the vehicle network and publish the registration information of the roadside devices to the blockchain. The multiple cross-domain child nodes are used to register vehicles in the corresponding domains of each cross-domain child node in the vehicle network and publish the vehicle registration information to the blockchain. The system also includes a device for batch generating pseudonym information and distributing the pseudonym information to the roadside devices. The device includes:

[0050] The first request-response module is used to respond to the pseudonym application request of the target vehicle, which is any vehicle that has been registered in the blockchain;

[0051] The sending module is used to send the corresponding pseudonym information to the target vehicle based on the pseudonym application request, and to feed back the pseudonym information issuance record to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle will synchronize the pseudonym information issuance record to the blockchain.

[0052] The second request response module is used to respond to the fleet establishment request of the target vehicle, the fleet establishment request including the identity identifiers of the fleet members and the pseudonym information of the target vehicle;

[0053] The identity information determination module is used to determine the fleet identity information based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle, and to encrypt the fleet identity information and send it to the vehicle corresponding to the fleet member.

[0054] The identity authentication module is used to authenticate the members of the connected fleet in the blockchain based on the fleet identity information.

[0055] Thirdly, this embodiment provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the blockchain-based fleet identity authentication method described in any embodiment of the first aspect above.

[0056] Fourthly, this embodiment provides a storage medium storing a computer program that, when executed by a processor, implements the blockchain-based fleet identity authentication method described in any embodiment of the first aspect above.

[0057] Compared to related technologies, the blockchain-based connected vehicle fleet identity authentication method provided in this embodiment authenticates multiple cross-domain child nodes through the root node in the blockchain to obtain node identity information. The public key from the node identity information is then published to the blockchain. Furthermore, multiple cross-domain child nodes reach consensus based on their respective node identity information, thus achieving mutual trust and recognition among multiple cross-domain child nodes within the same blockchain. Further, the root node registers roadside devices in the vehicle network, and cross-domain child nodes register vehicles in their respective domains, sending the registration information to the blockchain. This enables roadside devices and vehicles in the vehicle network to communicate across domains based on the same blockchain, reducing the complexity of cross-domain authentication during fleet member identity authentication. Moreover, the distributed consensus mechanism of the blockchain enables decentralized data management, ensuring the immutability of data on the blockchain in scenarios where multiple parties participate in joint maintenance. This ensures the security of privacy information such as the identity of connected vehicle fleet members, thereby preventing intruders from binding fleet member identities to vehicle locations, which could lead to vehicle tracking. In addition, cross-domain sub-nodes are also used to generate pseudonym information in batches and distribute the pseudonym information to roadside equipment. This allows the roadside equipment to assign corresponding pseudonym information to vehicles based on their pseudonym application requests. Then, the roadside equipment synchronizes the distribution record of the pseudonym information to the blockchain, which enables vehicles to perform vehicle identity authentication based on the pseudonym information in the blockchain. Therefore, in the process of authenticating the identity of connected vehicle fleet members, communication authentication is conducted using pseudonym information, which effectively avoids the leakage of privacy information such as the identity of connected vehicle fleet members.

[0058] Details of one or more embodiments of this application are set forth in the following drawings and description to make other features, objects and advantages of this application more readily apparent. Attached Figure Description

[0059] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0060] Figure 1 This is a schematic diagram illustrating an application scenario of a blockchain-based connected vehicle fleet identity authentication method provided in an embodiment of this application;

[0061] Figure 2 This is a flowchart of a blockchain-based connected vehicle fleet identity authentication method provided in an embodiment of this application;

[0062] Figure 3 This is a flowchart illustrating an embodiment of a blockchain-based connected vehicle fleet identity authentication method provided in this application.

[0063] Figure 4This is an interactive flowchart of collaborative communication among members of a connected vehicle fleet, provided in an embodiment of this application.

[0064] Figure 5 This is a structural block diagram of a blockchain-based connected vehicle fleet identity authentication device provided in an embodiment of this application;

[0065] Figure 6 This is an internal structural diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0066] To better understand the purpose, technical solution, and advantages of this application, the application is described and illustrated below in conjunction with the accompanying drawings and embodiments.

[0067] Unless otherwise defined, the technical or scientific terms used in this application shall have the general meaning as understood by one of ordinary skill in the art to which this application pertains. Words such as “a,” “an,” “an,” “the,” “the,” and “these,” used in this application, do not indicate quantitative limitation and may be singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that comprises a series of steps or modules (units) is not limited to the listed steps or modules (units) but may include steps or modules (units) not listed, or may include other steps or modules (units) inherent to such processes, methods, products, or devices. The terms “connected,” “linked,” and “coupled,” used in this application, are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. The term “multiple” used in this application refers to two or more. The "and / or" operator describes the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: A alone, A and B simultaneously, and B alone. Typically, the character " / " indicates that the objects before and after it are in an "or" relationship. The terms "first," "second," and "third," etc., used in this application are merely for distinguishing similar objects and do not represent a specific ordering of the objects.

[0068] In a connected vehicle environment, intelligent connected vehicles equipped with onboard units (OBUs) can share real-time status information with each other through vehicle-to-everything (V2X) technology, enabling autonomous driving scenarios such as platooning and cooperative driving. By communicating with devices equipped with roadside units (RSUs), intelligent connected vehicles can further enhance their perception of the traffic environment during operation.

[0069] To ensure the security of vehicle-to-everything (V2X) communication in connected vehicle fleets, a certificate-based PKI mechanism is typically used to authenticate communication terminals in the connected vehicle environment. Communication terminals in a connected vehicle environment generally fall into two categories: intelligent connected vehicles equipped with onboard units (OBUs) and devices equipped with roadside units (RSUs). Before communication, a terminal in a connected vehicle network needs to apply for a corresponding digital certificate from a Certificate Authority (CA). During communication, the digital certificate is used to sign the communication message, and the signature, along with the digital certificate and the communication message content, is broadcast. When a connected vehicle terminal receives a communication message from another connected vehicle terminal, it verifies the signature using the corresponding digital certificate to ensure the integrity of the message content and the legitimacy of the message source. The vehicles in the above process usually belong to the same trust domain, so they can be authenticated by the same Certificate Authority (CA) using the PKI mechanism. If the vehicles in the fleet belong to different trust domains, different Certificate Authorities (CAs) are needed to authenticate the vehicles in the corresponding trust domains. This requires a higher-level certificate authority to provide a corresponding trust list mechanism to achieve cross-domain authentication. However, this method of cross-domain authentication is highly complex, and the communication content can be monitored by hackers for a long time, which can easily lead to the leakage of private information such as vehicle location and driving trajectory, thus resulting in low security of user privacy information.

[0070] Therefore, how to reduce the complexity of cross-domain authentication during the identification process of connected vehicle fleet members is a problem that needs to be solved.

[0071] The blockchain-based connected vehicle fleet identity authentication method provided in this application can be applied to, for example... Figure 1 In the application environment shown, Figure 1 This is a schematic diagram illustrating an application scenario of a blockchain-based connected vehicle fleet identity authentication method provided in this application embodiment. The blockchain includes a root node and multiple cross-domain child nodes 101, which can communicate with each other. Each cross-domain child node 101 can be implemented using an independent server or a server cluster composed of multiple servers. Furthermore, the data of each cross-domain child node 101 in the blockchain is stored in multiple data blocks, and a regulatory agency 102 supervises the data in each cross-domain node 101. The vehicle-to-everything (V2X) network includes roadside equipment 103 and vehicles 104. Vehicles 104 are equipped with onboard units (OBUs), enabling V2X communication between vehicles 104 and roadside equipment 103 via the OBUs.

[0072] This application provides a blockchain-based connected vehicle fleet identity authentication method. The blockchain includes a root node and multiple cross-domain child nodes 101. The root node is the trust anchor of the system. The root node's certificate is pre-installed in the blockchain-based connected vehicle fleet identity authentication system. The root node is used to generate node identity information for multiple cross-domain child nodes. Multiple cross-domain child nodes reach consensus based on the identity information of each node.

[0073] Specifically, the root node generates identity certificates for each cross-domain child node, and the cross-domain child nodes conduct secure consensus communication by verifying each other's identity certificates.

[0074] Specifically, the root nodes are chosen as two large prime numbers, p and q, derived from the elliptic curve E:y 2 =x 3 A point on the equation +ax+b (mod p) and a point at infinity O generate an additive group G of order q, where a and b are non-negative integers less than p in a finite field, and the generator of G is P. Define a hash function. Random selection As the system key, the public key is calculated as T. pk =t*P. This completes the initialization of the public and private keys for each cross-domain child node.

[0075] Furthermore, the common parameters {G, P, p, q, a, b, T} are... pk The broadcast is sent to all vehicles in the vehicle network and roadside equipment, and recorded on the blockchain.

[0076] Node identity information may include the node's identity key pair {C pkj C skj} and the signature Sig corresponding to each cross-domain child node t (H0(C pkj ), where the identity key pair {C pkj C skj In}, C pkj For cross-domain child nodes CA j The node's public key, C skj For cross-domain child nodes CA j The root node publishes the node's private key, j, which is the number of cross-domain child nodes and is a positive integer. Furthermore, the root node publishes the node's public key from the identity information of each cross-domain child node to the blockchain.

[0077] The vehicle-to-everything (V2X) network includes roadside units (RSUs) and vehicles. The root node is also used to register the roadside units in the V2X network and generate their registration information. This registration information may include the roadside unit (RSU). n The corresponding key pair {R pkn ,r n}, R pkn Roadside Units (RSUs)n The public key is broadcast to the blockchain by the root node. n Roadside Units (RSUs) n The private key was used by the roadside unit (RSU). n Loaded locally, where n is the number of roadside devices, and n is a positive integer.

[0078] Cross-domain sub-nodes are used to register vehicles in the corresponding domains of each cross-domain sub-node in the vehicle network and generate vehicle registration information. In one embodiment, the vehicles V in each domain i To the cross-domain child node CA in the corresponding domain j Submit identity verification information (VID) i Cross-domain child node CA j After successful verification, a long-term valid identity key pair {V} will be generated for it. pki V ski} and encrypted it before sending it to vehicle V i , where V pki For vehicle V i public key, V ski For vehicle V i The private key, where i is the number of vehicles and i is a positive integer. Further, the cross-domain child node CA... j For vehicle V i Generate vehicle registration information, i.e., vehicle identity certificate VT i Vehicle identification document VT i Including: VT i {DID i V pki C pkj Sig cski (H0(VID i )),S i The cross-domain sub-node will transfer the vehicle identity certificate VT. i Published to the blockchain, DID i For vehicle V i Decentralized identifier, S i VT as vehicle identification document i The status of the credential can be either valid or invalid.

[0079] Cross-domain sub-nodes can also be used to generate pseudonym information in batches and then encrypt the pseudonym information before sending it to roadside equipment.

[0080] Figure 2 This is a flowchart illustrating a blockchain-based connected vehicle fleet identity authentication method provided in an embodiment of this application. The method is applied to roadside equipment, which can be an electronic device. Optionally, the electronic device can be a server or a terminal device, but this application is not limited thereto. Specifically, as shown... Figure 2As shown, the process includes the following steps:

[0081] Step S201: Respond to the pseudonym application request for the target vehicle.

[0082] The target vehicle is any vehicle in the Internet of Vehicles (IoV).

[0083] For example, before any vehicle in the vehicle network needs to communicate, it needs to send a pseudonym request to the roadside equipment in the corresponding domain to identify the vehicle as the target vehicle, that is, the target vehicle is any vehicle in the vehicle network. Further, the roadside equipment receives the pseudonym request sent by the target vehicle.

[0084] Specifically, the target vehicle encrypts the pseudonym request using the public key of the roadside device in the corresponding domain, and sends the encrypted pseudonym request to the roadside device.

[0085] In the above implementation process, the cross-domain child node sends the generated pseudonym information to the roadside equipment, so that the roadside equipment can assign pseudonym information to the vehicle. This can effectively avoid the vehicle frequently requesting pseudonym information from the child node, which would cause excessive pressure on the child node and further improve the vehicle's communication efficiency.

[0086] As another embodiment, if there is no pseudonym information in the roadside equipment, the target vehicle can directly send a pseudonym request to the child node, thereby enabling the child node to assign pseudonym information to the target vehicle.

[0087] Step S202: Based on the pseudonym application request, send the corresponding pseudonym information to the target vehicle and feed back the pseudonym information issuance record to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle will synchronize the pseudonym information issuance record to the blockchain.

[0088] Furthermore, after receiving the encrypted pseudonym request, the roadside equipment decrypts it using its own private key to obtain the decrypted pseudonym request, and assigns pseudonym information to the target vehicle based on the decrypted pseudonym request.

[0089] Specifically, the encryption request may include the target vehicle's identity credential VT. i Once the roadside equipment receives the decrypted pseudonym request, it will use the target vehicle's identity document VT... i The identity information of the target vehicle is authenticated; that is, the roadside equipment verifies the target vehicle's decentralized identifier (DID) in the blockchain. i Obtain the target vehicle's block identity credential from the blockchain, and use the target vehicle's public key V. pki The block identity credential is verified by signature. After successful signature verification, the node's public key C is used. pkjThe system retrieves the vehicle signature information from the blockchain identity credential. If the blockchain vehicle signature information matches the vehicle signature information sent by the target vehicle, it indicates that the target vehicle is registered in the blockchain, thus authenticating the target vehicle's identity within the blockchain. If the blockchain vehicle signature information does not match the vehicle signature information sent by the target vehicle, it indicates that the target vehicle is not registered in the blockchain.

[0090] When the target vehicle is identified as a registered vehicle in the blockchain, the roadside equipment assigns pseudonym information to the target vehicle. This pseudonym information may include a short-lived pseudonym identity key pair {P}. pki ,P ski} and the corresponding kana expiration time T pi .

[0091] Furthermore, the assigned pseudonym information is encrypted using the target vehicle's public key, and the encrypted pseudonym information is sent to the target vehicle.

[0092] Furthermore, each roadside device sends the allocation record of each pseudonym information to the corresponding child node in the same domain, thereby enabling the child node to synchronize the distribution record of pseudonym information to the blockchain, which facilitates traceability based on the pseudonym allocation record in the blockchain and ensures the privacy and security of pseudonym information.

[0093] Step S203: Respond to the fleet establishment request of the target vehicle.

[0094] The fleet establishment request includes the identification of fleet members and the pseudonym information of the target vehicle.

[0095] Step S204: Based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle, determine the fleet identity information, encrypt the fleet identity information, and send it to the vehicle corresponding to the fleet member.

[0096] Step S205: Based on the fleet identity information, perform member identity authentication of the connected fleet in the blockchain.

[0097] For example, when the target vehicle V in the vehicle network i When a fleet needs to be established, the target vehicle V i A fleet establishment request needs to be sent to the roadside equipment. The fleet establishment request includes the identification identifiers of the fleet members. i And the pseudonym information of the target vehicle, and the target vehicle V i During communication with roadside equipment, all communication messages are encrypted using the other party's public key, and the convoy member's identification e i Includes vehicle identification number (DID) i and random key negotiation factor n i .

[0098] Furthermore, after receiving a convoy establishment request from a target vehicle, the roadside equipment determines the convoy identity information based on the pseudonym information of the target vehicle and the identity identifiers of the convoy members in the convoy establishment request. The determined convoy identity information is then encrypted and sent to all vehicles within the convoy. Specifically, the encryption process involves querying the corresponding vehicle identity public key in the blockchain based on the convoy member's identity identifier, encrypting the convoy identity information using the vehicle identity public key, and then distributing it to the respective vehicles.

[0099] Furthermore, the roadside equipment authenticates the identities of fleet members in the blockchain based on the fleet identity information of each vehicle's fleet.

[0100] In the above implementation process, consensus is achieved through multiple cross-domain sub-nodes in the blockchain, thereby ensuring mutual trust among the multiple cross-domain sub-nodes and enabling information sharing among them. Furthermore, the root node registers roadside devices in the vehicle network, and the cross-domain sub-nodes register vehicles in their respective domains, sending the registration information to the blockchain. This allows roadside devices and vehicles in the vehicle network to communicate across domains based on the same blockchain, reducing the complexity of cross-domain authentication during fleet member identity verification. Moreover, based on the distributed consensus mechanism of the blockchain, decentralized data management is achieved, ensuring the immutability of data on the blockchain in scenarios where multiple parties participate in joint maintenance. This ensures the security of privacy information such as the identity of connected fleet members, thereby avoiding the risk of intruders binding fleet member identities with vehicle locations, leading to vehicle tracking. In addition, cross-domain sub-nodes are also used to generate pseudonym information in batches and distribute the pseudonym information to roadside equipment. This allows the roadside equipment to assign corresponding pseudonym information to vehicles based on their pseudonym application requests. Then, the roadside equipment synchronizes the distribution record of the pseudonym information to the blockchain, which enables vehicles to perform vehicle identity authentication based on the pseudonym information in the blockchain. Therefore, in the process of authenticating the identity of connected vehicle fleet members, communication authentication is conducted using pseudonym information, which effectively avoids the leakage of privacy information such as the identity of connected vehicle fleet members.

[0101] In some embodiments, determining the fleet identity information based on the identification of the fleet members and the pseudonym information of the target vehicle may include the following steps:

[0102] Step 1: Authenticate the target vehicle based on its pseudonym information to obtain the authentication result.

[0103] Step 2: Based on the identity authentication result of the target vehicle that has passed the authentication, send the identity identifiers of the fleet members to the cross-domain sub-nodes corresponding to the target vehicle, so that the cross-domain sub-nodes corresponding to the target vehicle can generate fleet identity information according to the identity identifiers of the fleet members and publish the fleet identity information to the blockchain.

[0104] Step 3: Respond to the fleet identity information fed back by the cross-domain sub-node corresponding to the target vehicle.

[0105] For example, after receiving a fleet establishment request from a target vehicle, the roadside equipment performs identity authentication on the target vehicle based on the pseudonym information of the target vehicle in the fleet establishment request, and obtains the identity authentication result of the target vehicle.

[0106] Once the target vehicle's identity verification is successful, the roadside equipment will identify the convoy members. i The message is sent to the cross-domain sub-node corresponding to the target vehicle. Further, the cross-domain sub-node corresponding to the target vehicle determines the destination based on the fleet member's identity identifier (e). i Generate fleet identity information, which includes the fleet identity public key Q. pki Team identification information QDID i and the team members' negotiation key r i Simultaneously, the cross-domain sub-node corresponding to the target vehicle stores a list of fleet member identity identifiers {e1,e2,…,e...} on the blockchain. k}, where k is the number of team members.

[0107] Specifically, the cross-domain sub-node corresponding to the target vehicle creates a fleet identity key pair {Q}. pki Q ski} and team identification information QDID i , where Q pki Q is the team's identity public key. ski This is the private key for fleet identity. It represents the list of fleet member identifiers {e1, e2, ..., e} corresponding to the target vehicle. k The cross-domain sub-node corresponding to the target vehicle calculates the fleet member negotiation key r. i =n1+n2+…+n k , where k is the number of team members.

[0108] Furthermore, the cross-domain sub-node corresponding to the target vehicle sends the fleet identity information to the blockchain and the target vehicle's V... i In the corresponding roadside equipment, the vehicle's fleet identity information is obtained from the cross-domain sub-nodes corresponding to the target vehicle.

[0109] Furthermore, after receiving the fleet identity information, the roadside equipment sends the fleet identity information to each vehicle in the fleet. Specifically, after receiving the fleet identity information, the roadside equipment uses the pseudonymous public key P of each fleet member vehicle to transmit the fleet identity information. pki After encryption and signing, the information is sent to the corresponding vehicle in the convoy. Each vehicle in the convoy verifies the signature of the received information and then decrypts it, thereby obtaining the convoy's identity information.

[0110] In the above implementation process, the vehicle is identified based on the pseudonym information in the vehicle fleet establishment request. After the vehicle identification is successful, the identity identifier of the fleet member is sent to the corresponding cross-domain sub-node, which facilitates the cross-domain sub-node to establish fleet identity information in the blockchain and synchronize the fleet identity information to the blockchain, thus realizing the on-chaining of fleet identity information. The fleet information is then fed back to the roadside equipment, so that the roadside equipment can obtain the fleet identity information fed back by the cross-domain sub-node corresponding to the target vehicle.

[0111] In some embodiments, authenticating the identity of members of a connected vehicle fleet in a blockchain based on fleet identity information may include the following steps:

[0112] Step 1: Respond to the second identity authentication request from the first vehicle to the second vehicle. The second identity authentication request includes the pseudonym information of the second vehicle, the identity information of the second fleet to which the second vehicle belongs, and the identity information of the first fleet to which the first vehicle belongs.

[0113] Step 2: Authenticate the pseudonym identity of the second vehicle in the blockchain based on the pseudonym information of the second vehicle, and obtain the pseudonym identity authentication result of the second vehicle.

[0114] Step 3: Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity information of the second fleet, and the identity information of the first fleet, authenticate the consistency of the fleet to which the first vehicle and the second vehicle belong, and obtain the fleet consistency authentication result.

[0115] Step 4: Feed back the fleet conformity certification result to the first vehicle so that the first vehicle and the second vehicle can conduct fleet collaborative communication.

[0116] For example, once a fleet is successfully established, members of the fleet can communicate with each other, but before the vehicles of the fleet members can communicate, the fleet identity information to which the vehicles of the fleet members belong needs to be authenticated.

[0117] Specifically, when the second vehicle needs to communicate with the first vehicle in a convoy, the second vehicle can send a broadcast message. This broadcast message transmits a second authentication request to the first vehicle. Specifically, the broadcast message includes the second authentication request. The second vehicle V2 can be any vehicle whose pseudonym information has been obtained from the vehicle network, and the first vehicle V1 can be any vehicle in the vehicle network other than the second vehicle. If the second vehicle needs to communicate with the first vehicle in the vehicle network, the second vehicle can send a broadcast message, i.e., a second authentication request, within the vehicle network. Specifically, the broadcast message can include: the second vehicle's pseudonym information {M2, P...} pk2 ,T p2 Sig psk2 (H0(H0(VID2)||M2||DID2||T p2 ))),Sig vsk2 (H0(P pk2 The identity information of the second team to which the second vehicle belongs, and the identity information of the first team to which the first vehicle belongs.

[0118] Wherein, M2 represents the status information of the second vehicle, which may include its driving or stationary status, P pk2 T is the public key for the pseudonym of the second vehicle. p2 For the expiration time of the pseudonym for the second vehicle, Sig psk2 (H0(H0(VID2)||M2||DID2||T p2 Sign the pseudonym certificate for the second vehicle, Sig vsk2 (H0(P pk2 The first vehicle signs the identity information of the second vehicle. After the first vehicle obtains the second identity authentication request of the second vehicle, it sends the second identity authentication request of the second vehicle to the roadside equipment, so that the roadside equipment obtains the second identity authentication request of the first vehicle for the second vehicle.

[0119] Furthermore, the roadside equipment authenticates the registration information of the second vehicle in the blockchain based on the pseudonym information of the second vehicle, and obtains the registration information authentication result.

[0120] Furthermore, the roadside equipment authenticates the pseudonym identity of the second vehicle based on the registration information authentication result, and obtains the pseudonym identity authentication result of the second vehicle.

[0121] Once the roadside equipment obtains the pseudonym authentication result of the second vehicle, it verifies the consistency between the first and second vehicles' fleets based on the identity information of the second and first fleets, thus obtaining the fleet consistency authentication result.

[0122] Furthermore, the roadside equipment feeds back the fleet conformity certification result to the first vehicle. When the fleet conformity certification result indicates that the first vehicle and the second vehicle belong to the same fleet, the first vehicle V1 can conduct fleet cooperative communication with the second vehicle V2.

[0123] In the above implementation process, the second vehicle is authenticated in the blockchain based on the second pseudonym information of the second vehicle in the second identity authentication request, so as to accurately determine the pseudonym information of the second vehicle. Furthermore, after the second pseudonym authentication of the second vehicle is passed, the fleet consistency authentication of the fleet to which the first vehicle and the second vehicle belong is performed to obtain the fleet consistency authentication result, so as to facilitate the first vehicle and the second vehicle to conduct collaborative communication between the fleets based on the fleet consistency authentication result.

[0124] In some embodiments, the second pseudonym information includes a second pseudonym identity public key. The pseudonym identity of the second vehicle is authenticated in the blockchain based on the second pseudonym information to obtain the pseudonym identity authentication result of the second vehicle, including the following steps:

[0125] Step 1: Send the second pseudonym information to the cross-domain sub-node corresponding to the first vehicle, so that the cross-domain sub-node corresponding to the first vehicle can authenticate the registration information of the second vehicle in the blockchain based on the second pseudonym information and obtain the registration information authentication result.

[0126] Step 2: Respond to the registration information authentication result fed back by the cross-domain sub-node corresponding to the first vehicle.

[0127] Step 3: Based on the authentication result of the verified registration information, authenticate the validity period of the second pseudonym information to obtain the legality authentication result of the second pseudonym information.

[0128] Step 4: Feed back the validity authentication result of the second pseudonym information to the first vehicle, so that the first vehicle can sign and authenticate the broadcast information of the second vehicle based on the public key of the second pseudonym identity, and obtain the signature authentication result of the broadcast information of the second vehicle. The broadcast information of the second vehicle is used to transmit the second identity authentication request to the first vehicle.

[0129] Step 5: Respond to the signature authentication result of the broadcast information of the second vehicle fed back by the first vehicle, and obtain the pseudonym authentication result of the second vehicle based on the signature authentication result of the broadcast information of the second vehicle.

[0130] For example, after the roadside device obtains the second pseudonym information, it sends the second pseudonym information to the cross-domain sub-node in the blockchain corresponding to the first vehicle. Further, the cross-domain sub-node corresponding to the first vehicle queries the blockchain for the second vehicle identity credential VT2 corresponding to the second vehicle V2 based on the second pseudonym information issuance record. Further, it uses the public key C of the cross-domain sub-node corresponding to the second vehicle... pk2 Public key V for the second vehicle pk2 The verification process is performed. If the verification passes, it indicates that the second vehicle sending the broadcast information has been registered in the blockchain. Furthermore, the cross-domain sub-node corresponding to the first vehicle uses the verified public key V of the second vehicle. pk2 Signature Sig in broadcast messages vsk2 (H0(P pk2 The signature in the broadcast message is verified to match the second vehicle identity credential VT obtained from the blockchain. i If the signatures in the blockchain match, the verification is successful, meaning that the registered second vehicle corresponds to the second vehicle recorded in the blockchain, thus realizing the authentication result of the registration information of the second vehicle.

[0131] Once the second vehicle registration information is verified, the expiration time T of the second pseudonym information for the second vehicle will be obtained. p2 If the expiration time T of the second pseudonym information p2 If the second pseudonym is valid within its validity period, then the authentication result for the legality of the second pseudonym is passed. If the expiration time T of the second pseudonym is... p2 If the validity period is not within the validity period, the authentication result of the second pseudonym information is "failed", thus obtaining the authentication result of the second pseudonym information of the second vehicle.

[0132] Furthermore, when the authentication result of the second pseudonym information is successful, the roadside equipment feeds back the successful authentication result of the second pseudonym information to the first vehicle V1. The first vehicle V1 then uses the pseudonym identity public key P of the second vehicle. pk2 The first vehicle V1 verifies the signature of the broadcast information sent by the second vehicle by performing signature verification, thereby obtaining the signature authentication result of the broadcast information of the second vehicle, and effectively ensuring the authenticity and integrity of the broadcast information. Further, the first vehicle V1 sends the signature authentication result of the broadcast information of the second vehicle to the roadside equipment.

[0133] The roadside equipment receives the signature authentication result of the broadcast information of the second vehicle sent by the first vehicle. When the signature authentication result of the broadcast information of the second vehicle is successful, the pseudonym authentication result of the second vehicle is obtained. When the signature authentication result of the broadcast information of the second vehicle is unsuccessful, the pseudonym authentication result of the second vehicle is obtained.

[0134] In the aforementioned vehicle identity authentication process, the roadside equipment sends the second pseudonym information to the cross-domain sub-node, which facilitates the cross-domain sub-node to authenticate the registration information of the second vehicle in the blockchain based on the second pseudonym information. After the second registration information is authenticated, the validity period of the second pseudonym information is verified, and then the broadcast information obtained by the first vehicle is signed and authenticated by the second vehicle. This ensures the authenticity and integrity of the broadcast information and realizes the pseudonym identity authentication of the second vehicle, thereby improving the accuracy of vehicle identity authentication.

[0135] In some embodiments, the fleet identity information includes the negotiation keys of fleet members, the fleet identity public key, and the fleet identifier. The second identity authentication request also includes the second authentication information of the second fleet, which is generated based on the negotiation keys of the second fleet members and the second fleet identity public key. Based on the pseudonym authentication result of the authenticated second vehicle, the second fleet identity information, and the first fleet identity information, the consistency between the fleet to which the first vehicle and the second vehicle belong is authenticated to obtain the fleet consistency authentication result, which may include the following steps:

[0136] Step 1: Based on the pseudonym authentication result of the second vehicle that has passed authentication, send the second fleet identifier of the second fleet to the cross-domain sub-node corresponding to the first vehicle in the blockchain, so that the cross-domain sub-node corresponding to the first vehicle can determine the authentication result of the second fleet identifier in the blockchain.

[0137] Step 2: Response to the authentication result of the second fleet identifier fed back by the cross-domain sub-node corresponding to the first vehicle. Based on the authentication result of the successfully authenticated second fleet identifier, as well as the negotiation key of the first fleet member and the public key of the first fleet identity in the first fleet identity information, determine the first authentication information of the first fleet.

[0138] Step 3: Based on the second information to be certified and the first certification information, verify the consistency of the fleet to which the first vehicle and the second vehicle belong, and obtain the fleet consistency certification result.

[0139] For example, the fleet identity information includes the negotiation keys of the fleet members, the fleet identity public key, and the fleet identifier. The second identity authentication request also includes the second authentication information of the second fleet, which is based on the negotiation key r of the second fleet members. i And the second team's identity public key Q pk2 Generated.

[0140] Specifically, the second vehicle uses the fleet identity public key Q from the fleet identity information to which it belongs. pk2 And the negotiation key r of the convoy members of the second vehicle i Generate a symmetric encryption key Q e2 =Qpk2 r i Furthermore, the message authentication code (HMAC) is determined based on the symmetric encryption key. Qei (P pk2 This allows us to obtain the second piece of information to be authenticated.

[0141] Once the pseudonym authentication result of the second vehicle is passed, the roadside equipment sends the second fleet identification information QDID2 of the second vehicle to the cross-domain sub-node corresponding to the first vehicle in the blockchain, so that the cross-domain sub-node corresponding to the first vehicle can determine the fleet authentication result of the second fleet in the blockchain based on the second fleet identification information QDID2.

[0142] Once the second fleet's fleet authentication result is passed, the cross-domain sub-node corresponding to the first vehicle will send the result back to the roadside equipment. Then, the roadside equipment will determine the first authentication information of the first fleet based on the negotiation key of the first fleet member and the first fleet's identity public key in the first fleet's identity information.

[0143] Specifically, the roadside equipment determines the negotiation key r of the first fleet members in the blockchain based on the identity information of the first fleet. i Furthermore, based on the negotiated key r of the team members i Generate a symmetric encryption key Q using the public key of the first team's identity information. e1 =Q' pk1 r i The first authentication information (HMAC) is determined based on the generated symmetric encryption key. Qe1 (P pk1 ).

[0144] Furthermore, the second information to be certified and the first certification information are used to verify the consistency of the fleet to which the first vehicle and the second vehicle belong, resulting in a fleet consistency certification result. Specifically, if the first certification information HMAC... Qe1 (P pk1 ) and the second authentication information HMAC Qe2 (P pk2 If the HMAC (Message Authentication Code) of the first vehicle matches, it can be determined that the first vehicle and the second vehicle belong to the same convoy. Qe1 (P pk1 HMAC (Message Authentication Code) of the Second Team Qe2 (P pk2 If the results are different, then the first vehicle and the second vehicle do not belong to the same fleet, and the final fleet consistency certification result is obtained.

[0145] In the above implementation process, after the pseudonym identity authentication of the second vehicle is passed, the fleet identifier of the second fleet is sent to the cross-domain sub-node corresponding to the first vehicle. This facilitates the cross-domain sub-node corresponding to the first vehicle to authenticate the registration information of the second fleet in the blockchain, that is, to obtain the authentication result of the second fleet identifier. After the second identifier authentication result is passed, the first authentication information of the first fleet is determined according to the identity information of the first fleet, and the first authentication information is compared with the second authentication information to determine whether the fleet to which the first vehicle and the second vehicle belong is consistent. When the fleet to which the first vehicle and the second vehicle belong is consistent, the first vehicle and the second vehicle can carry out cooperative communication between the fleets.

[0146] In some embodiments, the fleet identity information includes a fleet member identity list, which records the vehicle identity information of the fleet members. Based on the pseudonym authentication result of the authenticated second vehicle, the second fleet identity information, and the first fleet identity information, the consistency between the fleet to which the first vehicle and the second vehicle belong is authenticated to obtain a fleet consistency authentication result. This may include: based on the pseudonym authentication result of the authenticated second vehicle, the first fleet member identity list corresponding to the first vehicle, and the second fleet member identity list corresponding to the second vehicle, the consistency between the fleet to which the first vehicle and the second vehicle belong is authenticated to obtain a fleet consistency authentication result.

[0147] For example, when the fleet identity information includes a list of fleet member identities, fleet consistency verification can be performed directly on the roadside equipment. The fleet member list is used to record the vehicle identity information of the fleet members.

[0148] Specifically, once the pseudonym identity of the second vehicle is verified, the vehicle identity information of the team members in the first team member identity list can be compared with that of the team members in the second team member identity list. If the vehicle identity information of the team members in both lists is the same and includes the vehicle identity information of both the first and second vehicles, then the first and second vehicles belong to the same team; otherwise, the first and second vehicles belong to different teams, thus obtaining the team consistency verification result.

[0149] In the above implementation process, the fleet identity information includes a list of fleet member identities, so that when performing fleet consistency authentication, authentication can be performed directly on the roadside equipment, reducing the complexity of fleet authentication and improving the efficiency of fleet authentication.

[0150] In some embodiments, after sending the fleet identification information to the vehicles corresponding to the fleet members, the following steps may also be included:

[0151] Step 1: Respond to the joining application information of the first target team member vehicle. The joining application information includes the pseudonym information of the first target team member vehicle, the identity information of the first target team to which the first target team member vehicle belongs, and the verification result of the joining request of the first target team member vehicle. The first target team member vehicle is any vehicle in the first target team, and the first target team is any team in the blockchain.

[0152] Step 2: Based on the pseudonym information of the vehicles of the first target convoy members, perform pseudonym identity authentication on the blockchain to obtain the pseudonym identity authentication result of the vehicles of the first target convoy members.

[0153] Step 3: Based on the pseudonym identity authentication results of the vehicles of the first target fleet members and the identity information of the first target fleet, authenticate the fleet identity information of the vehicles of the first target fleet members to obtain the fleet authentication results of the first target fleet members.

[0154] Step 4: Send the fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined to the cross-domain sub-node corresponding to the vehicle to be joined in the blockchain, so that the cross-domain sub-node corresponding to the vehicle to be joined can determine the joining result of the vehicle to be joined based on the fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined.

[0155] Step 5: Response to the queuing result of the cross-domain sub-node corresponding to the vehicle to be enqueued.

[0156] For example, once a fleet is successfully established, other vehicles can apply to join it. Specifically, when a vehicle needs to join the fleet, it needs to send a joining request to all member vehicles in the fleet. Furthermore, all member vehicles in the fleet need to authenticate the vehicle applying to join. That is, the vehicle to be joined needs to send a joining request to each member vehicle in the fleet. Further, when any member vehicle in the fleet receives the joining request from the vehicle to be joined, it needs to verify the validity of the pseudonym information of the vehicle to be joined and the validity and validity of the domain range corresponding to the vehicle to be joined. After the verification is successful, any member vehicle in the fleet sends the joining request information of the vehicle to be joined to the roadside equipment.

[0157] Specifically, any convoy in the blockchain is designated as the first target convoy, and any member vehicle in the first target convoy is designated as member vehicle V of the first target convoy. l .

[0158] Vehicle V awaiting joining m To the first target convoy member vehicle V lSend a platooning application; the platooning application information may include the vehicle V to be joined. m The pseudonym information, when the first target convoy member vehicle V l According to the vehicle V waiting to join the team m The validity of the pseudonym information in the joining application of the vehicle to be joined, as well as the validity and timeliness of the domain range corresponding to the vehicle to be joined, are verified to obtain the verification result of the joining request of the first target fleet member vehicle to the vehicle to be joined.

[0159] Furthermore, the first target convoy member vehicle V l Send V of vehicles waiting to join the platoon to roadside equipment m The application information for joining the team may include the vehicle V of the first target team member. l The information includes the pseudonym information, the identity information of the first target convoy to which the vehicles of the first target convoy belong, and the verification result of the first target convoy member vehicles' convoy entry requests. In addition, the convoy entry application information may also include: {DID} l DID m QDID l ,T e ,EQ}, where DID l Vehicle V for the first target team members l Vehicle identification, DID m For vehicles waiting to join the team V m Vehicle identification, QDID l The team identifiers for the vehicles belonging to the first target team members are: EQ for joining the team, and T for joining the team. e This refers to the application submission time.

[0160] Furthermore, the roadside equipment, based on the vehicle V of the first target convoy members... l The pseudonym information is used in the blockchain to identify the first target convoy members and vehicle V. l Perform pseudonym verification to obtain the vehicle V of the first target convoy members. l The result of pseudonym identity verification.

[0161] When the first target team member vehicle V l After the pseudonym identity verification result is passed, the roadside equipment verifies the fleet identity information of the vehicles belonging to the first target fleet based on the identity information of the first target fleet, and obtains the fleet authentication result of the first target fleet members, thereby determining the legitimacy of the fleet identity information to which the vehicles belonging to the first target fleet members belong.

[0162] Furthermore, once the roadside equipment has completed the authentication of the fleet identity information of each member vehicle in the first target fleet, it sends the fleet authentication result of each member vehicle in the first target fleet and the verification result of each member vehicle's request for joining the fleet to the cross-domain sub-node corresponding to the vehicle to join the fleet in the blockchain.

[0163] Furthermore, the cross-domain sub-node corresponding to the vehicle to be joined determines the vehicle V to be joined based on the fleet authentication result of each member vehicle in the first target fleet and the verification result of each member vehicle's request to join the vehicle. m The queuing results. Specifically, the cross-domain sub-nodes corresponding to the vehicles to be enqueued are determined based on a time threshold range T. limit Within the system, the number of fleet authentication results received from member vehicles and the number of verification results from member vehicles for the joining requests of vehicles awaiting joining are used to determine the vehicle V to be joined. m The results of the team recruitment.

[0164] As one example, when the fleet authentication result of all member vehicles in the first target member fleet is passed, and the verification result of the joining request of the vehicle to be joined by all member vehicles is passed, then the vehicle to be joined, V, will be added to the fleet. n The joining result was confirmed as passed, meaning that vehicle V was approved to join the team. m Join the first target team.

[0165] As another embodiment, when more than 50% of the member vehicles in the first target member fleet have passed fleet authentication and the verification result of the joining request of the vehicle to be joined by each corresponding member vehicle has passed, then the vehicle to be joined will be V m The joining result was confirmed as passed, meaning that vehicle V was approved to join the team. m Join the first target team.

[0166] As another embodiment, when more than 80% of the member vehicles in the first target member fleet have passed fleet authentication and the verification result of the joining request of the vehicle to be joined by each corresponding member vehicle has passed, then the vehicle to be joined, V, will be added to the fleet. m The joining result was confirmed as passed, meaning that vehicle V was approved to join the team. m Join the first target team.

[0167] It should be noted that this embodiment of the application only uses the fleet authentication results of all member vehicles, 50% of member vehicles, and 80% of member vehicles, as well as the verification results of the joining request of the vehicle to join the fleet, as examples. In actual application, other numbers of member vehicles may also be used, and there is no limitation here.

[0168] When the cross-domain sub-node corresponding to the vehicle to be joined is determined, the vehicle to be joined, V, is... mAfter verifying the queuing request, the queuing result of the vehicle to be queued is sent to the roadside equipment, so that the roadside equipment can obtain the vehicle V to be queued. m The results of the team joining are as follows, among which, vehicle V is waiting to join the team. m The result of joining the team can be either agreeing to join or disagreeing to join.

[0169] Furthermore, the cross-domain sub-node corresponding to the vehicle to be joined will enqueue the vehicle V. m The results of joining the team are synchronized to the blockchain.

[0170] In the above implementation process, when a vehicle to be joined needs to apply to join the fleet, an entry request needs to be sent to all vehicles in the fleet. Furthermore, all members of the fleet need to verify the entry request of the vehicle to be joined through roadside equipment. That is, the roadside equipment verifies the entry request of the vehicle to be joined based on the entry request of the fleet members and sends the verification of the entry request of each fleet member to the cross-domain sub-node corresponding to the vehicle to be joined. Furthermore, the cross-domain sub-node corresponding to the vehicle to be joined determines the entry result of the vehicle to be joined based on the verification result of the entry request of the fleet members and the number of members in the fleet who agree to the entry of the vehicle to be joined. This allows the entry information of the vehicle to be joined to be certified in the blockchain, thereby improving the security of vehicle entry.

[0171] In some embodiments, if the queuing result for the vehicle to be joined is "accepted to join," the following steps may also be included:

[0172] Step 1: Send the identity identifier of the vehicle to be joined to the cross-domain sub-node corresponding to the vehicle in the blockchain, so that the cross-domain sub-node corresponding to the vehicle to be joined can update the identity information of the first target fleet based on the identity identifier of the vehicle to be joined and the identity identifiers of all member vehicles in the first target fleet, and publish the updated identity information of the first target fleet to the blockchain.

[0173] Step 2: Respond to the updated identity information of the first target fleet from the cross-domain sub-node corresponding to the vehicle to be joined, and send the updated identity information of the first target fleet to all vehicles of the first target fleet members and the vehicle to be joined.

[0174] For example, when vehicle V is waiting to join the platoon m After joining the first target convoy, the roadside equipment can also V-shaped the vehicles waiting to join the convoy. m identity identifier e m Send to the blockchain and the vehicle V to be joined m Within the child nodes of the same domain, further, the cross-domain child nodes corresponding to the vehicles to be enqueued are determined based on the vehicle V to be enqueued. m identity identifier em and the identification marks of all members and vehicles in the first target convoy. i The identity information of the first target convoy will be updated. Specifically, the vehicles awaiting convoy entry will be... m identity identifier e m Add the identified vehicles of the first target convoy to the list of identifying members, and obtain the updated list of identifying members of the first target convoy. i_list ={e1,e2,…,e k}, where k is the number of team members in the first target team. Furthermore, the child nodes calculate the negotiation key r for each team member. i =n1+n2+…+n k This allows us to obtain the updated identity information {QDID} of the first target convoy. i Q pki ,r i}

[0175] Furthermore, when the cross-domain sub-node corresponding to the vehicle to be joined updates the identity information of the first target fleet, it publishes the updated identity information of the first target fleet to the blockchain and the roadside equipment, thereby enabling the roadside equipment to send the updated identity information of the first target fleet to all vehicles of the first target fleet members and vehicles to be joined.

[0176] In the above implementation process, after a vehicle to be joined joins the first target convoy, the identity key of the vehicle to be joined is sent to the cross-domain sub-node corresponding to the vehicle to be joined in the blockchain. This allows the cross-domain sub-node corresponding to the vehicle to be joined to update the identity information of the first target convoy based on the identity key of the vehicle to be joined. Furthermore, the updated identity information of the first target convoy is synchronized to the blockchain, so that the blockchain can store the update record of the identity information of the first target convoy. Furthermore, the roadside equipment sends the updated identity information of the first target convoy to each convoy member in the updated first target convoy, so that the convoy members can communicate based on the updated convoy identity information.

[0177] In some embodiments, after sending the fleet identification information to the vehicles corresponding to the fleet members, the method further includes:

[0178] Step 1: Respond to the departure request information of the second target fleet member vehicle. The departure request information includes the pseudonym information of the second target fleet member vehicle and the identity information of the second target fleet to which the second target fleet member vehicle belongs. The second target fleet member vehicle is any vehicle in the second target fleet, and the second target fleet is any fleet in the blockchain.

[0179] Step 2: Based on the pseudonym information of the vehicles of the second target convoy members, perform pseudonym identity authentication on the blockchain to obtain the pseudonym identity authentication result of the vehicles of the second target convoy members.

[0180] Step 3: Based on the pseudonym identity authentication results of the vehicles of the second target fleet members and the identity information of the second target fleet, authenticate the fleet identity information of the vehicles of the second target fleet members to obtain the fleet authentication results of the second target fleet members.

[0181] Step 4: Send the fleet authentication results of the second target fleet member vehicles to the cross-domain sub-nodes corresponding to the second target fleet member vehicles, so that the cross-domain sub-nodes corresponding to the second target fleet member vehicles can update the identity information of the second target fleet and publish the updated identity information of the second target fleet to the blockchain.

[0182] Step 5: Respond to the updated identity information of the second target convoy corresponding to the cross-domain sub-nodes of the second target convoy members' vehicles, and send the updated identity information of the second target convoy to all vehicles in the second target convoy except for the second target convoy members' vehicles after encrypting it.

[0183] For example, when a vehicle in a convoy needs to leave the convoy, it needs to send a convoy leave application to the roadside equipment. Specifically, any convoy in the blockchain is identified as the second target convoy, and any vehicle in the second target convoy is identified as a member vehicle of the second target convoy.

[0184] When a vehicle in the second target convoy needs to leave the convoy, it sends a departure request to the roadside equipment in the same area. The departure request may include the pseudonym of the vehicle and the identity information of the second target convoy to which the vehicle belongs.

[0185] Furthermore, the roadside equipment performs pseudonym identity verification on the second target convoy member vehicles in the blockchain based on the pseudonym information of the second target convoy member vehicles, thereby obtaining the pseudonym identity verification result of the second target convoy member vehicles.

[0186] Furthermore, once the pseudonym identity verification result of the second target fleet member vehicle is passed, the fleet to which the second target fleet member vehicle belongs is verified based on the identity information of the second target fleet, thereby determining whether the vehicle applying to leave the fleet is a member vehicle of the second target fleet, and obtaining the fleet verification result of the second target fleet member.

[0187] If the pseudonym information of the vehicle requesting to join the convoy is verified, and the vehicle requesting to join the convoy is a member of the second target convoy, the verification result is sent to the cross-domain sub-node corresponding to the second target convoy member vehicle in the blockchain. Further, the cross-domain sub-node corresponding to the second target convoy member vehicle updates the identity information of the second target convoy. Specifically, the cross-domain sub-node corresponding to the second target convoy member vehicle deletes relevant information about the second target convoy member vehicle from the blockchain, such as the identity identifier of the second target convoy member vehicle from the deleted identity information. Based on the updated list of convoy member identity identifiers, the vehicle member negotiation key is calculated, and the convoy identity key pair {Q' is updated synchronously. pki ,Q' ski This allows us to obtain the updated identity information of the second target convoy.

[0188] Furthermore, the cross-domain sub-nodes corresponding to the vehicles of the second target convoy will synchronize the updated identity information of the second target convoy in the blockchain and send it to the corresponding roadside equipment.

[0189] Furthermore, the roadside equipment encrypts the updated identity information of the second target convoy and sends it to all vehicles in the second target convoy except for the vehicles of the second target convoy members. The specific encryption process is to query the corresponding vehicle identity public key in the blockchain based on the identity identifier of the convoy member, encrypt the convoy identity information using the vehicle identity public key, and then send it to the corresponding vehicle, so that the convoy member vehicles can conduct collaborative communication among convoy members based on the updated convoy identity information.

[0190] In the above implementation process, when a member vehicle in the convoy needs to apply for departure, it sends a departure application information to the roadside equipment. This allows the roadside equipment to perform pseudonym authentication for the vehicle applying for departure and authentication for the convoy members. After successful authentication, the vehicle departure information is updated on the blockchain, which facilitates the recording of vehicle departure information on the blockchain and ensures the accuracy of convoy updates.

[0191] Figure 3 This is a flowchart illustrating an embodiment of a blockchain-based connected vehicle fleet identity authentication method provided in this application. Figure 3 As shown, the process includes the following steps:

[0192] Step S301: Register the vehicle and roadside equipment to generate vehicle identity credentials.

[0193] Specifically, a blockchain-based vehicle identity authentication system is initialized. This system includes the underlying blockchain network and nodes that maintain the blockchain ledger. Nodes provide identity registration services to terminal devices and maintain vehicle identity credentials. The entire lifecycle of vehicle and fleet identity credentials—including application, update, and revocation—is recorded in a distributed ledger jointly maintained by all blockchain nodes to provide anomaly tracing capabilities and support regulatory verification. The blockchain includes a root node and multiple cross-domain child nodes. The root node is the system's trust anchor, and its certificate is pre-installed in the system during the blockchain network initialization phase. The root node generates identity certificates for its child nodes. The number of child nodes is j∈{1,2,…,j}, and the root node is the CA for the cross-domain child nodes. j Generate identity key pair {C pkj C skj} and signature Sig t (H0(C pkj And publish the public key on the blockchain.

[0194] The vehicle-to-everything (V2X) network includes vehicles and roadside units (RSUs). The identity information of the RSUs is initialized. The number of RSUs is n∈{1,2,…,n}, and the root node is the RSU. n Generate identity key pair {R pkn ,r n RSU preloads the key r in its local memory. n Public key R pkn The broadcast is transmitted to all roadside devices and vehicles in the vehicle-to-everything (V2X) network and recorded on the blockchain.

[0195] Initialize vehicle identity information. The vehicle needs to submit an identity registration application through a child node CA to obtain a legitimate identity within the vehicle network. Detailed identity verification information (VID) is required during the application process. i After the child node CA verifies the identity and passes the verification, a long-term valid identity key pair {V} is generated for it. pki V ski The relevant materials are encrypted and sent to the vehicle. A vehicle identity certificate (VT) is created. i {DID i V pki C pkj Sig cski (H0(VID i )),S i The data is then submitted to the blockchain, supporting cross-domain identity authentication between multiple CAs (such as different car manufacturers) that have vehicle registration permissions.

[0196] Specifically, DID iThis serves as a unique identifier for a vehicle in the blockchain. Based on this identifier, a corresponding vehicle identity certificate can be generated using cryptographic methods. When vehicles communicate with each other, the vehicle identity certificate in the blockchain is queried through this identifier, and its validity is verified, thereby achieving identity authentication.

[0197] Vehicle travel trajectories are often sensitive information; therefore, pseudonyms are required in actual communication to protect users' real identities. Sub-node CAs generate pseudonym information in batches and encrypt it before sending it to the Roadside Units (RSUs) to avoid excessive pressure on the sub-node CAs due to frequent data queries. Based on the validity period of the pseudonym information, the status of the pseudonym information stored in the local database of the RSUs is updated in batches. The RSUs decrypt the pseudonym information, verify its legitimacy, and then store it in their local database.

[0198] The vehicle selects an RSU based on the distance and reliability of the roadside unit (RSU) and requests a pseudonym from it. If there is no RSU within communication range, it directly requests one from the child node. The request information includes {DID}. i H0(VID) i ),V pki Sig vski (H0(DID i ||H0(VID i )||V pki )))}, and use R pkn Encryption is required. RSU or CA j The RSU verifies the security and legality of the vehicle application information. Upon successful verification, the RSU sends a short-term valid pseudonym key pair {P} to the vehicle. pki ,P ski} and the corresponding kana expiration time T pi And use V to record the distribution of pseudonyms. pki The encrypted message is sent to the child node CA, which then writes it to the blockchain. This enables the information in the blockchain to support anomaly tracing and ensure privacy and security. The vehicle verification RSU's signature is used, employing V... ski After decryption, obtain the corresponding pseudonym identity key pair {P} from the pseudonym information. pki ,P ski When a pseudonym is updated due to revocation, expiration, or other reasons, the child node CA will update the local data stored in the RSU based on the application record in the blockchain.

[0199] Specifically, the RSU's process for verifying the security and legality of vehicle application information includes:

[0200] Step 1: Obtain the blockchain to acquire the identity certificate VT for the vehicle registered under a pseudonym. i Using V pki Verify the signature.

[0201] Step 2: Use C pkj Sign and decrypt the application information, then combine the decrypted information with H0(VID). i The decrypted information is compared and verified. If the decrypted information is consistent with H0(VID), then... i If the information matches, it indicates that the vehicle identity authentication has been successful, thus achieving vehicle identity authentication.

[0202] In step S302, the vehicle communicates using pseudonym information and creates a fleet identity credential.

[0203] Specifically, when vehicle V i During V2X communication with other vehicles based on pseudonym information, the vehicle V i Send a broadcast message, wherein the broadcast message includes {M i ,P pki ,T pi Sig pski (H0(H0(VID i )||M i ||DID i ||T pi ))),Sig vski (H0(P pki ))}, where M i For vehicle status information, T pi This refers to the expiration time of the vehicle's pseudonym information.

[0204] Vehicle V j Received V i After broadcasting the information, the identity of the broadcaster is verified. The verification process includes the following steps:

[0205] Step 1: Vehicle V j Submit vehicle V to RSU i Identity verification application.

[0206] Step 2: Query vehicle V based on pseudonym issuance records in a local database or blockchain. i The corresponding VT i And verify V pki The legality is verified as in step 2 of step S301 above.

[0207] Step 3: RSU uses the verified V pki Sig vski (H0(P pki )) Verify signature.

[0208] Step 4: The RSU verifies the expiration time of the pseudonym and, after confirming that the pseudonym information is within the validity period, issues a V-notification to the vehicle. j Return V i Identity verification result.

[0209] Step 5: Vehicle V j Use P pki Verify V i Broadcast message signatures ensure the authenticity and integrity of the information.

[0210] Furthermore, when a vehicle needs to establish a convoy, the vehicle sends a convoy establishment request to the RSU, which includes the identification identifiers of the convoy members. i All communication between the two parties is encrypted using the other party's public key. After decrypting the queuing request, the RSU verifies its security and legitimacy. If the verification is successful, the RSU sends the request to the child CA node, which then generates an identity key pair {Q} for the convoy. pki Q ski Create a unique QDID for your fleet. i Generate a negotiation key r for each team member based on their identity identifier. i The team's identity credential {QDID} i Q pki ,r i The fleet identity credential is the fleet's identity information. After successful creation, the child node CA records the fleet identity and fleet establishment application information in the blockchain ledger. The fleet identity credential is then issued from the child node CA to the RSU. The RSU uses the vehicle identity public key to encrypt the information, adds a signature, and sends it to the fleet member vehicles. The vehicles verify the signature, decrypt the information, and obtain the fleet member identity.

[0211] Vehicles that obtain fleet status are based on Q pki and r i Generate symmetric encryption key Q ei =Q pki r i Calculate the Message Authentication Code (HMAC) Qei (P pki This information is broadcast within the V2X communication message. The message authentication code is calculated based on the latest fleet identity credentials. To improve communication efficiency, a list of fleet member identity credentials and the verified fleet member's P are stored in the RSU. pki The hash value is used to facilitate the rapid identification of team members.

[0212] The regulatory body MA assesses the reputation of vehicles based on records in the blockchain. If a malicious vehicle is detected, it requests the child node CA to query the pseudonym application records stored in the blockchain to obtain all pseudonym identities for the vehicle and updates the vehicle identity certificate VT in the blockchain. i If the status is invalid, add all pseudonyms to the revocation list and delete the corresponding vehicle identity record from the corresponding fleet identity authorization certificate list.

[0213] In step S303, the vehicle to be joined initiates a joining request. After all team members verify and approve the request, the vehicle to be joined obtains a team member identity identifier.

[0214] Specifically, the vehicle to be joined broadcasts a request to all member vehicles in the convoy to join the convoy to which it belongs. The request includes the convoy member identification e. m .

[0215] Team member vehicle V l For vehicle V requesting to join the convoy m The identity's cryptographic validity, geographical validity, and timeliness are verified. Upon successful verification, a queuing request is sent to the RSU, with all communication between the two parties encrypted using the other party's public key. The RSU first verifies the pseudonym information of the submitted vehicle and the legitimacy of the fleet members' identities. After successful verification, the request is sent to the CA. The CA records the queuing request information of the requesting vehicle in the blockchain and queries the time threshold T. limit The system records the application information for the vehicle currently requesting to join the fleet. If the verified applicant in the record is one of all fleet members, the vehicle's joining request will be approved. Specifically, the joining application may include {DID} l DID m QDID l T e , EQ}. Where EQ is the queue entry request identifier, T e This refers to the application submission time. Once the application is approved, the CA will update the fleet QDID. i List of team member identification e i_list ={e1,e2,…,e k} Calculate the team member negotiation key r based on the team member identity list. i =n1+n2+…+n k And simultaneously update the team member identity information {QDID} in the blockchain. i Q pki ,r i}, where k is the number of team members. The updated team member identity information is sent to the vehicle V at a distance of [distance V]. m RSUs within a certain distance threshold near the latest location are encrypted using the public key of the vehicle applying for platooning, and then signed and sent to all platoon members.

[0216] Step S304: Authenticate the identity of the fleet members' vehicles and conduct fleet collaborative communication after the fleet members' identity authentication is successful.

[0217] When vehicles need to conduct collaborative communication within the same fleet, they request verification of their pseudonym identity from the RSU. After successful pseudonym authentication, they then request verification of their fleet member identity from the RSU. Fleet member identity verification is performed by calculating the corresponding message authentication code, and the specific process includes the following steps: based on the Q in the fleet member identity information... pki and r i Generate symmetric encryption key Q ei =Q pki r i Calculate the Message Authentication Code (HMAC) Qei (P pki It then compares the information with the V2X communication information broadcast by the vehicle. If they match, the verification is successful, and a convoy cooperation message can be sent to initiate platooning.

[0218] Figure 4 This is an interactive flowchart of collaborative communication among members of a connected vehicle fleet, provided in an embodiment of this application. Figure 4 As shown, when vehicle V i Vehicle V from the same convoy is required. j When conducting cooperative communication, vehicle V i To vehicle V j Sending communication messages, further, vehicle V j According to the communication message, vehicle V i The system retrieves the pseudonym information and requests pseudonym identity verification from the roadside equipment. Furthermore, the roadside equipment queries the child nodes for identity credentials and verifies the pseudonym identity based on the query results, thereby facilitating the determination of the vehicle's V (vehicle identification number). i The verification result of the pseudonym information, when vehicle V is determined i After verifying the pseudonym identity, the system will send a message to vehicle V. j Send the pseudonym authentication result, and further, vehicle V j Verification vehicle V j The message signature completes pseudonym authentication after the message verification is successful.

[0219] Furthermore, vehicle V j The system requests fleet member identity authentication from the roadside equipment. Further, the roadside equipment queries the child nodes for fleet member identity credentials. Based on the query results, it verifies the fleet member's identity and sends the fleet member identity authentication result back to vehicle V. j This enabled the authentication of team members' identities.

[0220] Furthermore, vehicle V j After obtaining the fleet member identity verification results, determine vehicle V. j With vehicle V i Whether they are from the same fleet, if vehicle V j With vehicle Vi If they are from the same convoy, then vehicle V j To vehicle V i Send collaboration messages.

[0221] Step S305: Update the fleet identity information when the vehicle leaves the fleet.

[0222] When a vehicle needs to leave the convoy, the convoy member vehicles V i A dequeue request is submitted to the RSU. All communication between the two parties is encrypted using the other party's public key. The request information includes {DID}. i QDID i T d DQ, H0(VID) i )}. Where DQ is the departure request identifier, T d This refers to the application submission time.

[0223] The RSU first verifies the pseudonym information of the submitted vehicles and the legitimacy of the fleet members' identities. Upon successful verification, the request is sent to the CA. The CA updates the fleet member identity identifiers in the blockchain and distributes them to the RSU, while simultaneously recording the departure request. The fleet's QDID is used for this purpose. i The fleet identity key pair {Q' needs to be updated synchronously. pki ,Q' ski}, and delete the team member identification list e i_list The corresponding team member identification identifiers. Based on the updated team member identification identifier list e i_list ={e1,e2,…,e k}, calculate the negotiation key r of the vehicle occupants. i =n1+n2+…+n k , where k is the number of convoy members after a vehicle leaves the convoy. RSU encrypts the updated convoy identity information using the updated vehicle identity public key, adds a signature, and sends it to all convoy members.

[0224] In the above implementation process, the root node in the blockchain authenticates multiple cross-domain child nodes to obtain node identity information, and publishes the public key from the node identity information to the blockchain. Furthermore, multiple cross-domain child nodes reach consensus based on their respective node identity information, thus achieving mutual trust and recognition among multiple cross-domain child nodes within the same blockchain. Further, the root node registers roadside devices in the vehicle network, and cross-domain child nodes register vehicles in their respective domains, sending the registration information to the blockchain. This enables roadside devices and vehicles in the vehicle network to communicate across domains based on the same blockchain, reducing the complexity of cross-domain authentication during fleet member identity verification. Moreover, the distributed consensus mechanism of the blockchain enables decentralized data management, ensuring the immutability of data on the blockchain in scenarios where multiple parties participate in joint maintenance, thereby ensuring the security of privacy information such as the identity of connected fleet members. Furthermore, by authenticating fleet members during their entry or exit from the fleet, connected fleet identity authentication is achieved during dynamic changes in fleet members. Authentication of connected fleet members based on the blockchain ensures communication security during dynamic changes in fleet members.

[0225] It should be noted that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0226] This embodiment also provides a blockchain-based fleet member identity authentication device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. The terms "module," "unit," "subunit," etc., used below refer to combinations of software and / or hardware that perform a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0227] Figure 5This is a structural block diagram of a blockchain-based connected vehicle fleet identity authentication device provided in this application embodiment. The blockchain includes a root node and multiple cross-domain child nodes. The root node is used to generate corresponding node identity information for the multiple cross-domain child nodes and publish the node public key in each node identity information to the blockchain. The multiple cross-domain child nodes reach consensus based on the node identity information. The vehicle network includes roadside equipment and vehicles. The root node is also used to register the roadside equipment in the vehicle network and publish the registration information of the roadside equipment to the blockchain. The multiple cross-domain child nodes are used to register vehicles in the corresponding domains of each cross-domain child node in the vehicle network and publish the vehicle registration information to the blockchain. They are also used to generate pseudonym information in batches and distribute the pseudonym information to the roadside equipment, such as... Figure 5 As shown, the device includes:

[0228] The first request response module 501 is used to respond to the pseudonym application request of the target vehicle, which is any vehicle that has been registered in the blockchain.

[0229] The sending module 502 is used to send the corresponding pseudonym information to the target vehicle based on the pseudonym application request, and to feed back the pseudonym information issuance record to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle will synchronize the pseudonym information issuance record to the blockchain.

[0230] The second request response module 503 is used to respond to the fleet establishment request of the target vehicle. The fleet establishment request includes the identity identifiers of the fleet members and the pseudonym information of the target vehicle.

[0231] The identity information determination module 504 is used to determine the identity information of the fleet based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle, and then encrypt the fleet identity information and send it to the vehicle corresponding to the fleet member.

[0232] The identity authentication module 505 is used to authenticate the members of the connected fleet in the blockchain based on the fleet identity information.

[0233] In some embodiments, the identity information determination module 504 is further configured to:

[0234] The identity of the target vehicle is verified based on the pseudonym information of the target vehicle, and the identity verification result of the target vehicle is obtained.

[0235] Based on the identity authentication result of the target vehicle that has passed the authentication, the identity identifier of the fleet members is sent to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle generates fleet identity information according to the identity identifier of the fleet members and publishes the fleet identity information to the blockchain;

[0236] The response responds to the fleet identity information fed back by the cross-domain sub-node corresponding to the target vehicle.

[0237] In some embodiments, the identity authentication module 505 is specifically used for:

[0238] In response to the first vehicle’s second identity authentication request to the second vehicle, the second identity authentication request includes the second pseudonym information of the second vehicle, the second fleet identity information of the fleet to which the second vehicle belongs, and the first fleet identity information of the first vehicle to which the first vehicle belongs;

[0239] The pseudonym identity of the second vehicle is authenticated in the blockchain based on the second pseudonym information, and the pseudonym identity authentication result of the second vehicle is obtained.

[0240] Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity information of the second fleet, and the identity information of the first fleet, the consistency between the fleet to which the first vehicle and the second vehicle belong is authenticated to obtain the fleet consistency authentication result.

[0241] The fleet conformity certification results are fed back to the first vehicle, enabling the first vehicle and the second vehicle to conduct fleet collaborative communication.

[0242] In some embodiments, the identity authentication module 505 is specifically used for:

[0243] The second pseudonym information is sent to the cross-domain sub-node corresponding to the first vehicle, so that the cross-domain sub-node corresponding to the first vehicle can authenticate the registration information of the second vehicle in the blockchain based on the second pseudonym information and obtain the registration information authentication result.

[0244] The system responds to the registration information authentication result returned by the cross-domain sub-node corresponding to the first vehicle.

[0245] Based on the authentication result of the verified registration information, the validity period of the second pseudonym information is authenticated to obtain the legality authentication result of the second pseudonym information;

[0246] The validity authentication result of the second pseudonym information is fed back to the first vehicle, so that the first vehicle can sign and authenticate the broadcast information of the second vehicle based on the public key of the second pseudonym identity, and obtain the signature authentication result of the broadcast information of the second vehicle. The broadcast information of the second vehicle is used to transmit the second identity authentication request to the first vehicle.

[0247] The signature authentication result of the broadcast information of the second vehicle is responded to by the first vehicle, and the pseudonym authentication result of the second vehicle is obtained based on the signature authentication result of the broadcast information of the second vehicle.

[0248] In some embodiments, the fleet identity information includes the negotiation keys of fleet members, the fleet identity public key, and the fleet identifier. The second identity authentication request also includes second authentication information of the second fleet, which is generated based on the negotiation keys of the second fleet members and the second fleet identity public key. The identity authentication module 505 is specifically used for:

[0249] Based on the pseudonym authentication result of the second vehicle that has passed authentication, the second fleet identifier of the second fleet is sent to the cross-domain sub-node corresponding to the first vehicle in the blockchain, so that the cross-domain sub-node corresponding to the first vehicle can determine the authentication result of the second fleet identifier in the blockchain;

[0250] The system responds to the authentication result of the second fleet identifier fed back by the cross-domain sub-node corresponding to the first vehicle. Based on the authentication result of the successfully authenticated second fleet identifier, as well as the negotiation key of the first fleet member and the first fleet identity public key in the first fleet identity information, the system determines the first authentication information of the first fleet.

[0251] Based on the second information to be certified and the first certification information, the consistency between the fleet to which the first vehicle and the second vehicle belong is certified, and the fleet consistency certification result is obtained.

[0252] In some embodiments, the fleet identity information includes a fleet member identity list, which records the vehicle identity information of the fleet members. The identity authentication module 505 is specifically used for:

[0253] Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity list of the first fleet members corresponding to the first vehicle and the identity list of the second fleet members corresponding to the second vehicle are used to authenticate the consistency of the fleet to which the first vehicle and the second vehicle belong, and obtain the fleet consistency authentication result.

[0254] In some embodiments, the identity authentication module 505 is further configured to:

[0255] The response is to the entry application information of the first target team member vehicle to the entry application information, which includes the pseudonym information of the first target team member vehicle, the identity information of the first target team to which the first target team member vehicle belongs, and the verification result of the entry request of the first target team member vehicle to the entry application information. The first target team member vehicle is any vehicle in the first target team, and the first target team is any team in the blockchain.

[0256] Based on the pseudonym information of the vehicles of the first target team members, the pseudonym identity of the vehicles of the first target team members is verified in the blockchain to obtain the pseudonym identity verification result of the vehicles of the first target team members.

[0257] Based on the pseudonym identity authentication results of the vehicles of the first target fleet members and the identity information of the first target fleet, the fleet identity information of the vehicles of the first target fleet members is authenticated to obtain the fleet authentication results of the first target fleet members;

[0258] The fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined are sent to the cross-domain sub-node corresponding to the vehicle to be joined in the blockchain, so that the cross-domain sub-node corresponding to the vehicle to be joined can determine the joining result of the vehicle to be joined based on the fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined.

[0259] The response determines the queuing result of the vehicle to be enqueued, as determined by the cross-domain sub-node corresponding to the vehicle to be enqueued.

[0260] In some embodiments, if the queuing result for the vehicle to be joined is "accepted," the identity authentication module 505 is further used for:

[0261] The identity identifier of the vehicle to be joined is sent to the cross-domain sub-node corresponding to the vehicle to be joined, so that the cross-domain sub-node corresponding to the vehicle to be joined updates the identity information of the first target vehicle based on the identity identifier of the vehicle to be joined and the identity identifiers of all member vehicles in the first target vehicle, and publishes the updated identity information of the first target vehicle to the blockchain.

[0262] The system responds to the updated identity information of the first target fleet from the cross-domain sub-node corresponding to the vehicle to be joined, and sends the updated identity information of the first target fleet to all vehicles of the first target fleet members and the vehicle to be joined.

[0263] In some embodiments, the identity authentication module 505 is further configured to:

[0264] In response to the departure request information of the second target fleet member vehicle, the departure request information includes the pseudonym information of the second target fleet member vehicle and the identity information of the second target fleet to which the second target fleet member vehicle belongs. The second target fleet member vehicle is any vehicle in the second target fleet, and the second target fleet is any fleet in the blockchain;

[0265] Based on the pseudonym information of the vehicles of the second target convoy members, the pseudonym identity of the vehicles of the second target convoy members is verified in the blockchain to obtain the pseudonym identity verification result of the vehicles of the second target convoy members.

[0266] Based on the pseudonym identity authentication results of the vehicles of the second target fleet members and the identity information of the second target fleet, the fleet identity information of the vehicles of the second target fleet members is authenticated to obtain the fleet authentication results of the second target fleet members;

[0267] The fleet authentication results of the vehicles of the second target fleet members are sent to the cross-domain sub-nodes corresponding to the vehicles of the second target fleet members, so that the cross-domain sub-nodes corresponding to the vehicles of the second target fleet members update the identity information of the second target fleet and publish the updated identity information of the second target fleet to the blockchain;

[0268] The system responds to the updated identity information of the second target convoy from the cross-domain sub-nodes corresponding to the member vehicles of the second target convoy, and then encrypts and sends the updated identity information of the second target convoy to all vehicles in the second target convoy except for the member vehicles of the second target convoy.

[0269] It should be noted that the above modules can be functional modules or program modules, and can be implemented through software or hardware. For modules implemented through hardware, the above modules can reside in the same processor; or the above modules can be located in different processors in any combination.

[0270] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, Figure 6 This is an internal structural diagram of a computer device provided in an embodiment of this application. The computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database stores data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a blockchain-based connected vehicle fleet identity authentication method.

[0271] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0272] In one embodiment, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0273] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0274] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0275] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0276] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0277] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of patent protection. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims

1. A blockchain-based method for authenticating the identity of connected vehicle fleets, characterized in that, The blockchain includes a root node and multiple cross-domain child nodes. The root node is used to generate corresponding node identity information for the multiple cross-domain child nodes and publish the node public key in each node identity information to the blockchain. The multiple cross-domain child nodes reach consensus based on each node identity information. The vehicle network includes roadside devices and vehicles. The root node is also used to register the roadside devices in the vehicle network and publish the registration information of the roadside devices to the blockchain. The multiple cross-domain child nodes are used to register vehicles in the corresponding domains of each cross-domain child node in the vehicle network and publish the vehicle registration information to the blockchain. They are also used to generate pseudonym information in batches and distribute the pseudonym information to the roadside devices. The method is applied to the roadside devices and includes: In response to a pseudonym request for a target vehicle, the target vehicle being any vehicle already registered in the vehicle network; Based on the pseudonym application request, the corresponding pseudonym information is sent to the target vehicle, and the pseudonym information issuance record is fed back to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle synchronizes the pseudonym information issuance record to the blockchain. In response to the fleet establishment request of the target vehicle, the fleet establishment request includes the identity identifiers of the fleet members and the pseudonym information of the target vehicle; Based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle, the fleet identity information is determined, and the fleet identity information is encrypted and sent to the vehicle corresponding to the fleet member; Based on the fleet identity information, the members of the connected fleet are authenticated in the blockchain.

2. The blockchain-based connected vehicle fleet identity authentication method according to claim 1, characterized in that, The process of determining the fleet identity information based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle includes: The identity of the target vehicle is verified based on the pseudonym information of the target vehicle, and the identity verification result of the target vehicle is obtained. Based on the identity authentication result of the target vehicle that has passed the authentication, the identity identifier of the fleet member is sent to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle generates fleet identity information according to the identity identifier of the fleet member and publishes the fleet identity information to the blockchain; The response is the fleet identity information fed back by the cross-domain sub-node corresponding to the target vehicle.

3. The blockchain-based connected vehicle fleet identity authentication method according to claim 1, characterized in that, The process of authenticating the identity of members of the connected vehicle fleet in the blockchain based on the fleet identity information includes: In response to the second identity authentication request from the first vehicle to the second vehicle, the second identity authentication request includes the second pseudonym information of the second vehicle, the second fleet identity information of the fleet to which the second vehicle belongs, and the first fleet identity information of the first vehicle to which the first vehicle belongs; Based on the second pseudonym information, the pseudonym identity of the second vehicle is authenticated in the blockchain to obtain the pseudonym identity authentication result of the second vehicle. Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity information of the second fleet, and the identity information of the first fleet, the consistency between the fleet to which the first vehicle and the second vehicle belong is authenticated to obtain the fleet consistency authentication result. The fleet conformity authentication result is fed back to the first vehicle so that the first vehicle and the second vehicle can conduct fleet collaborative communication.

4. The blockchain-based connected vehicle fleet identity authentication method according to claim 3, characterized in that, The second pseudonym information includes a second pseudonym identity public key. The step of authenticating the pseudonym identity of the second vehicle in the blockchain based on the second pseudonym information to obtain the pseudonym identity authentication result of the second vehicle includes: The second pseudonym information is sent to the cross-domain sub-node corresponding to the first vehicle, so that the cross-domain sub-node corresponding to the first vehicle can authenticate the registration information of the second vehicle in the blockchain based on the second pseudonym information and obtain the registration information authentication result. The system responds to the registration information authentication result fed back by the cross-domain sub-node corresponding to the first vehicle. Based on the authentication result of the successfully authenticated registration information, the validity period of the second pseudonym information is authenticated to obtain the legality authentication result of the second pseudonym information; The validity authentication result of the second pseudonym information is fed back to the first vehicle, so that the first vehicle can perform signature authentication on the broadcast information of the second vehicle based on the public key of the second pseudonym identity, and obtain the signature authentication result of the broadcast information of the second vehicle. The broadcast information of the second vehicle is used to transmit the second identity authentication request to the first vehicle. The system responds to the signature authentication result of the broadcast information of the second vehicle fed back by the first vehicle, and obtains the pseudonym authentication result of the second vehicle based on the signature authentication result of the broadcast information of the second vehicle.

5. The blockchain-based connected vehicle fleet identity authentication method according to claim 3, characterized in that, The fleet identity information includes the negotiation keys of the fleet members, the fleet identity public key, and the fleet identifier. The second identity authentication request also includes the second authentication information of the second fleet, which is generated based on the negotiation keys of the second fleet members and the second fleet identity public key. The process of verifying the consistency between the first vehicle and the fleet to which the second vehicle belongs, based on the pseudonym authentication result of the successfully authenticated second vehicle, the identity information of the second fleet, and the identity information of the first fleet, to obtain a fleet consistency authentication result includes: Based on the pseudonym authentication result of the second vehicle that has passed authentication, the second fleet identifier of the second fleet is sent to the cross-domain sub-node corresponding to the first vehicle in the blockchain, so that the cross-domain sub-node corresponding to the first vehicle can determine the authentication result of the second fleet identifier in the blockchain; In response to the authentication result of the second fleet identifier fed back by the cross-domain sub-node corresponding to the first vehicle, based on the authentication result of the second fleet identifier that has been successfully authenticated, and the negotiation key of the first fleet member and the public key of the first fleet identity in the first fleet identity information, the first authentication information of the first fleet is determined. Based on the second information to be authenticated and the first authentication information, the consistency between the first vehicle and the fleet to which the second vehicle belong is authenticated, and the fleet consistency authentication result is obtained.

6. The blockchain-based connected vehicle fleet identity authentication method according to claim 3, characterized in that, The fleet identity information includes a fleet member identity list, which records the vehicle identity information of the fleet members. The consistency between the fleet to which the first vehicle and the second vehicle belong, based on the authenticated pseudonym identity verification result of the second vehicle, the second fleet identity information, and the first fleet identity information, is verified to obtain a fleet consistency verification result, including: Based on the pseudonym authentication result of the second vehicle that has passed authentication, the identity list of the first fleet member corresponding to the first vehicle and the identity list of the second fleet member corresponding to the second vehicle are used to authenticate the consistency of the fleet to which the first vehicle and the second vehicle belong, and obtain the fleet consistency authentication result.

7. The blockchain-based connected vehicle fleet identity authentication method according to claim 1, characterized in that, After encrypting the fleet identity information and sending it to the vehicles corresponding to the fleet members, the process further includes: The system responds to the entry application information of the first target fleet member vehicle for the vehicle to be joined. The entry application information includes the pseudonym information of the first target fleet member vehicle, the identity information of the first target fleet to which the first target fleet member vehicle belongs, and the verification result of the first target fleet member vehicle for the entry request of the vehicle to be joined. The first target fleet member vehicle is any vehicle in the first target fleet, and the first target fleet is any fleet in the blockchain. Based on the pseudonym information of the vehicles of the first target fleet members, the pseudonym identity of the vehicles of the first target fleet members is verified in the blockchain to obtain the pseudonym identity verification result of the vehicles of the first target fleet members. Based on the pseudonym identity authentication results of the vehicles of the first target fleet members and the identity information of the first target fleet, the fleet identity information of the vehicles of the first target fleet members is authenticated to obtain the fleet authentication results of the first target fleet members; The fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined are sent to the cross-domain sub-node corresponding to the vehicle to be joined in the blockchain, so that the cross-domain sub-node corresponding to the vehicle to be joined can determine the joining result of the vehicle to be joined based on the fleet authentication results of all member vehicles in the first target fleet and the verification results of the joining request of the vehicle to be joined. The response determines the queuing result of the vehicle to be enqueued by the cross-domain sub-node corresponding to the vehicle to be enqueued.

8. The blockchain-based connected vehicle fleet identity authentication method according to claim 7, characterized in that, If the queuing result for the vehicle to be joined is "accept joining", the method further includes: The identity identifier of the vehicle to be joined is sent to the cross-domain sub-node corresponding to the vehicle to be joined, so that the cross-domain sub-node corresponding to the vehicle to be joined updates the identity information of the first target fleet based on the identity identifier of the vehicle to be joined and the identity identifiers of all member vehicles in the first target fleet, and publishes the updated identity information of the first target fleet to the blockchain; In response to the updated identity information of the first target fleet federated by the cross-domain sub-node corresponding to the vehicle to be joined, the updated identity information of the first target fleet is sent to all member vehicles in the first target fleet and the vehicle to be joined.

9. The blockchain-based connected vehicle fleet identity authentication method according to claim 1, characterized in that, After sending the fleet identification information to the vehicles corresponding to the fleet members, the process further includes: In response to the departure request information of the second target fleet member vehicle, the departure request information includes the pseudonym information of the second target fleet member vehicle and the identity information of the second target fleet to which the second target fleet member vehicle belongs. The second target fleet member vehicle is any vehicle in the second target fleet, and the second target fleet is any fleet in the blockchain. Based on the pseudonym information of the vehicles of the second target fleet members, the pseudonym identity of the vehicles of the second target fleet members is verified in the blockchain to obtain the pseudonym identity verification result of the vehicles of the second target fleet members; Based on the pseudonym identity authentication results of the vehicles of the second target fleet members and the identity information of the second target fleet, the fleet identity information of the vehicles of the second target fleet members is authenticated to obtain the fleet authentication results of the second target fleet members; The fleet authentication results of the vehicles of the second target fleet members are sent to the cross-domain sub-nodes corresponding to the vehicles of the second target fleet members, so that the cross-domain sub-nodes corresponding to the vehicles of the second target fleet members update the identity information of the second target fleet and publish the updated identity information of the second target fleet to the blockchain; The system responds to the updated identity information of the second target fleet corresponding to the cross-domain sub-nodes of the second target fleet members, and then encrypts and sends the updated identity information of the second target fleet to all vehicles in the second target fleet except for the second target fleet members.

10. A blockchain-based connected vehicle fleet identity authentication device, characterized in that, The blockchain includes a root node and multiple cross-domain child nodes. The root node generates corresponding node identity information for the multiple cross-domain child nodes and publishes the node public key in each node identity information to the blockchain. The multiple cross-domain child nodes reach consensus based on each node identity information. The vehicle network includes roadside equipment and vehicles. The root node is also used to register the roadside equipment in the vehicle network and publish the registration information of the roadside equipment to the blockchain. The multiple cross-domain child nodes are used to register vehicles in the corresponding domains of each cross-domain child node in the vehicle network and publish the vehicle registration information to the blockchain. The root node is also used to generate pseudonym information in batches and distribute the pseudonym information to the roadside equipment. The device includes: The first request-response module is used to respond to the pseudonym application request of the target vehicle, which is any vehicle that has been registered in the blockchain; The sending module is used to send the corresponding pseudonym information to the target vehicle based on the pseudonym application request, and to feed back the pseudonym information issuance record to the cross-domain sub-node corresponding to the target vehicle, so that the cross-domain sub-node corresponding to the target vehicle will synchronize the pseudonym information issuance record to the blockchain. The second request response module is used to respond to the fleet establishment request of the target vehicle, the fleet establishment request including the identity identifiers of the fleet members and the pseudonym information of the target vehicle; The identity information determination module is used to determine the fleet identity information based on the identity identifiers of the fleet members and the pseudonym information of the target vehicle, and to encrypt the fleet identity information and send it to the vehicle corresponding to the fleet member. The identity authentication module is used to authenticate the members of the connected fleet in the blockchain based on the fleet identity information.

11. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the blockchain-based connected vehicle identity authentication method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the blockchain-based connected vehicle identity authentication method as described in any one of claims 1 to 9.

Images