Blockchain-based cross-domain authentication method, system, device and medium for Internet of Vehicles

Abstract

The present invention relates to the field of vehicle networks, and to a cross-domain authentication method for vehicle networks based on blockchain, comprising: a trusted authentication center initializes system parameters and registers identity information of roadside units RSU and vehicle V in the vehicle network; each roadside unit RSU periodically broadcasts its own identity information; and vehicle V ij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The identity information of the vehicle is verified; if the vehicle V ij If the authentication is successful, the vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ij ; The roadside unit RSU ij Through zero-knowledge proof, the vehicle V ij The anonymous identity is authenticated. If the authentication is successful, a roadside unit RSU is established. ij With vehicle V ij The connection between the roadside units RSU ij With vehicle V ij The present invention also proposes a cross-domain authentication system, device and storage medium for Internet of Vehicles based on blockchain. The present invention can improve the authentication efficiency and reduce the storage and computing overhead on the blockchain.

Description

Technical Field

[0001] The present invention relates to the field of Internet of Vehicles, and in particular to a blockchain-based Internet of Vehicles cross-domain authentication method, system, device and medium. Background Art

[0002] In recent years, the security and trust of the Internet of Vehicles has received great attention from the country. Compared with traditional communication systems, the Internet of Vehicles system has more elements and forms, and the information interaction scenarios are more complex. The Internet of Vehicles system involves a large amount of information exchange. Ensuring the identity authenticity and information integrity and confidentiality of the interactive entities is crucial to preventing attacks such as information tampering and identity forgery. Establishing a secure identity authentication mechanism can effectively ensure the security of the Internet of Vehicles system. A safe and reliable identity authentication mechanism is the basis for the healthy development of the Internet of Vehicles, which will help promote the interconnection and secure communication of the Internet of Vehicles across industries and regions, thereby promoting the comprehensive development of the Internet of Vehicles industry.

[0003] The development of cross-domain authentication technology will significantly improve the overall security and practicality of the Internet of Vehicles. Vehicles can switch seamlessly between different areas to ensure the continuity and reliability of communication, which is crucial for the implementation of autonomous driving and intelligent transportation systems. In addition, through an efficient cross-domain authentication mechanism, traffic accidents caused by authentication delays can be reduced, the level of intelligent traffic flow management can be improved, and a safer and more efficient traffic environment can be achieved.

[0004] Existing cross-domain authentication schemes are mainly divided into those that rely on third-party trusted institutions and those based on blockchain technology. Since the introduction of trusted third-party institutions to assist in the cross-domain sharing of authentication information will result in additional communication overhead, blockchain technology has become the current mainstream solution. However, with the continuous growth of the amount of authentication information stored on the blockchain, the inherent performance bottlenecks of blockchain technology, such as throughput limitations, storage constraints, and query delays, have become increasingly apparent. Existing authentication schemes still have significant deficiencies in authentication delay and computational overhead, and therefore need to be improved. Summary of the invention

[0005] In order to reduce the storage and computing overhead on the blockchain and improve the authentication efficiency, this application provides a blockchain-based Internet of Vehicles cross-domain authentication method, system, device and storage medium.

[0006] In order to achieve the above-mentioned purpose of the present invention, according to the first aspect of the present invention, the present invention provides a cross-domain authentication method of Internet of Vehicles based on blockchain.

[0007] The present invention provides a blockchain-based Internet of Vehicles cross-domain authentication method, comprising:

[0008] The trusted authentication center initializes system parameters and registers the identity information of the roadside unit RSU and the identity information of the vehicle V in the Internet of Vehicles;

[0009] Each roadside unit RSU periodically broadcasts its own identity information;

[0010] Vehicle V ij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The identity information of RSU is verified; ij represents the jth roadside unit RSU in the i-th domain, V ij represents the jth vehicle V in the i-th domain;

[0011] If the vehicle V ij If the authentication is successful, the vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ii ;

[0012] The roadside unit RSU ij Respond to cross-domain authentication requests through zero-knowledge proof of vehicle V ij The anonymous identity is authenticated. If the authentication is successful, a roadside unit RSU is established. ij With vehicle V ij The connection between the roadside units RSU ij With vehicle V ij Cross-domain communication; if authentication fails, the roadside unit RSU ij Reject Vehicle V ij Cross-domain authentication request.

[0013] Optionally, a roadside unit (RSU) ij The identity information is {R rij , RID ij , rpk ij，1 , A ij , T rij}, where R rij Roadside unit information generated by a trusted authentication center, RID ij Roadside Unit RSU ij The identity of rpk ij，1 Roadside Unit RSU ij The generated public key, A ij Roadside Unit RSU ij The key generated by the trusted certification center during registration, T rij For RSU ij The timestamp generated by the trusted certification authority during registration;

[0014] The vehicle Vij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The steps to verify identity information include:

[0015] Vehicle V ij Enter the roadside unit RSU ij When the communication range is

[0016] Verify R rij ·P i =A ij +H1(RID ij , rpk ij，1 , A ij , T rij )TPK i Is it true, where P i is the generator, H1(RID ij , rpk ij，1 , A ij , T rij ) is a hash function, TPK i is the system public key;

[0017] If so, then the vehicle V ij Roadside Unit RSU ij Authentication successful;

[0018] If not, then the vehicle V ij Roadside Unit RSU ij Authentication failed.

[0019] Optionally, the vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ij include:

[0020] S401: Vehicle V ij Random Selection Calculate C ij =c ij ·P i , C ij is the vehicle V ij The first proof value generated;

[0021] Then we get α ij =H2(c ij ·rpk ij，1 , RID ij ,aid ij , T1);

[0022] β ij =α ij H1(aidij , vpk ij，1 , B ij , T vij ) -1 ;

[0023] Among them, α ij is the first intermediate value, β ij The second intermediate value, H2(c ij ·rpk ij，1 , RID ij ,aid ij , T1) represents the hash function, aid ij For vehicle V ij Anonymous identity of vehicle V ij Timestamp when sending cross-domain authentication request, vpk ij，1 For vehicle V ij The generated public key, B ij For vehicle V ij The key generated by the trusted certification center during registration, T vij For vehicle V ij The timestamp generated by the trusted certification authority during registration;

[0024] S402: Based on the first intermediate value α ij and the second intermediate value β ij Determine vehicle V ij Commitment information and certification information;

[0025] The calculation formula for commitment information is π ij =c ij +β ij R vij ;

[0026] The calculation formula of the proof information is γ ij =β ij B ij ; δ ij =α ij TPK i ;

[0027] π ij For vehicle V ij The commitment value of ij For vehicle V ij The second proof value, δ ij For vehicle V ij The third proof value of

[0028] S403: Based on vehicle V ij The commitment information and proof information generate vehicle V ij Cross-domain authentication information;

[0029] The cross-domain authentication information is The zone identity witness value generated for the proxy server; AID ij For vehicle V ij AID ij ={aid ij , T vij};

[0030] S404: Generate a cross-domain authentication request based on the cross-domain identity authentication information and send it to the roadside unit RSU ij .

[0031] Optionally, the roadside unit RSU ij Through zero-knowledge proof, the vehicle V ij The steps for anonymous identity authentication include:

[0032] S501: RSU ij Check whether the timestamp T1 exceeds the preset time range. If it does not exceed the preset time range, the verification is passed and step S502 is executed; if it exceeds the preset time range, the authentication fails;

[0033] S502: Verify π ij ·P i =C ij +γ ij +δ ij Is it true? If the equation is true, then the vehicle V ij If the anonymous identity authentication is passed, step S503 is executed; if not, the authentication fails;

[0034] S503: Roadside Unit RSU ij According to the vehicle V ij Anonymous ID aid ij Request the RSA cumulative value of all vehicle cross-domain identities in domain i from the proxy server AS And calculate the ID ij =H3(R vij , AID ij ), ID ij For vehicle V ij identity information; H3(R vij , AID ij ) represents a hash function;

[0035] S504: Use Hprime function to convert ID ij Mapped to a prime number x ij , get vehicle V ij The prime identity of x ij ;

[0036] S505: Verification Is it equal to like Then the vehicle V ij Pseudonymous identity is legal, roadside unit RSU ij Complete the vehicle V ij Cross-domain authentication; if Then the cross-domain authentication fails.

[0037] Optionally, for vehicle V ij The prime identity of x ij and the zone identity witness value generated by the proxy server Processing to obtain When using the exponentiation operation to calculate The value of

[0038] x ij Expressed in binary form, x ij =x k 2 k +x k-1 2 k-1 +x k-2 2 k-2 +…+x22 2 +x12 1 +x02 0 , x k ∈{0,1} and x k =1,

[0039] but

[0040] get The value of .

[0041] Optionally, the method further comprises:

[0042] Roadside Unit RSU ij Upon receiving cross-domain authentication requests issued by multiple vehicles V, determining the domains to which the multiple vehicles V issuing the cross-domain authentication requests belong;

[0043] If the roadside unit RSU ij When cross-domain authentication requests from different vehicles V in the same domain are received, batch confirmation is performed on the cross-domain authentication requests from different vehicles V in the same domain.

[0044] Optionally, the batch confirmation of cross-domain authentication requests of different vehicles V in the same domain includes:

[0045] S601: When the roadside unit RSU ij When receiving cross-domain authentication requests from different vehicles V in the same domain, for n vehicles from the same domain m, the roadside unit RSUij Random Generation t is a random integer, a is the index of the vehicle that issued the cross-domain authentication request in domain m;

[0046] S602: Verify the equation through zero knowledge Is it established? m is the generator, π ma For vehicle V ma The commitment value, C ma is the vehicle V ma The first proof value generated; γ ma For vehicle V ma The second proof value, δ ma For vehicle V ma The third proof value of

[0047] If the equation If the pseudonyms of n vehicles in domain m are all verified,

[0048] Then the batch cross-domain authentication of n vehicles in domain m fails;

[0049] S603: Verify each vehicle Is it equal to

[0050] is the RSA cumulative value of the cross-domain identities of all vehicles in domain m, The zone identity witness value generated by the proxy server for domain m, x mn For vehicle V mn The prime identity of

[0051] Calculate all The product of

[0052] Calculate all x mn The product of

[0053] Use the recursive algorithm PowerRecur(n, A, x) to calculate Where A is the first array, x is the second array, and n represents the size of the array;

[0054] like Then the batch cross-domain verification is passed; if Then batch cross-domain verification fails.

[0055] In order to solve the above problems, the present invention also provides a vehicle network cross-domain authentication system based on blockchain, which is used to implement the above vehicle network cross-domain authentication method based on blockchain, wherein the system includes at least two domains, each domain includes a trusted authentication center, a roadside unit, a vehicle and a proxy server, and the proxy servers of each domain together constitute a blockchain;

[0056] The trusted authentication center is used to initialize system parameters and register the identity information of the roadside unit and the vehicle in the Internet of Vehicles;

[0057] Roadside units are used to monitor vehicle driving data information in real time;

[0058] The proxy server is used to process cross-domain authentication requests;

[0059] The blockchain stores smart contracts for cross-domain authentication, and the RSA cumulative values ​​of the cross-domain identities of all vehicles in each domain are stored in the blockchain.

[0060] In order to solve the above problem, the present invention further provides an electronic device, the electronic device comprising:

[0061] at least one processor; and,

[0062] a memory communicatively connected to the at least one processor; wherein,

[0063] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the above-mentioned blockchain-based Internet of Vehicles cross-domain authentication method.

[0064] In order to solve the above problems, the present invention also provides a computer-readable storage medium, in which at least one computer program is stored. The at least one computer program is executed by a processor in an electronic device to implement the above-mentioned blockchain-based Internet of Vehicles cross-domain authentication method.

[0065] In summary, this application includes the following beneficial technical effects:

[0066] The anonymous identity of the vehicle is generated under the supervision and management of the trusted center, so that the vehicle can use the pseudonym for cross-domain authentication. The vehicle uses the pseudonym to complete interactive authentication with the RSU; when the vehicle commits malicious acts, the anonymous protection of the vehicle identity information is achieved; the trusted authentication center TA can obtain the real identity of the vehicle and achieve traceability of malicious acts; only vehicles with legal registration information and identity certificates can generate verifiable authentication requests, thereby resisting impersonation attacks; each pseudonym and cross-domain authentication request of the vehicle includes a timestamp to ensure the timeliness of the pseudonym and request information to avoid forgery and replay attacks;

[0067] In this application, the number of communication rounds for both vehicles and RSUs is relatively small, and the parameters used in the authentication protocol are necessary parameters to meet security requirements, and no unnecessary irrelevant parameters are added to occupy the number of communication bytes. Therefore, under the premise of meeting security requirements, the communication overhead of this application is low;

[0068] Batch verification of vehicles in the same domain can reduce the computational overhead of point multiplication operations, reduce computing costs, and reduce storage and computing overhead on the blockchain. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] Figure 1 A system architecture diagram of a blockchain-based Internet of Vehicles cross-domain authentication system provided in one embodiment of the present invention;

[0070] Figure 2 A schematic diagram of a process flow of a cross-domain authentication method for Internet of Vehicles based on blockchain provided by an embodiment of the present invention;

[0071] Figure 3 A schematic diagram of a process of a cross-domain authentication method for Internet of Vehicles based on blockchain provided by another embodiment of the present invention;

[0072] Figure 4 A schematic diagram of the structure of an electronic device for implementing the blockchain-based Internet of Vehicles cross-domain authentication method provided in one embodiment of the present invention.

[0073] Reference numerals: 10, processor; 11, memory; 12, communication bus; 13, communication interface.

[0074] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0075] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0076] In the description of the present invention, it is necessary to understand that the terms "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0077] In the description of the present invention, unless otherwise specified and limited, it should be noted that the terms "installed", "connected" and "connected" should be understood in a broad sense. For example, it can be a mechanical connection or an electrical connection, or it can be the internal connection between two components. It can be a direct connection or an indirect connection through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms can be understood according to the specific circumstances.

[0078] Reference Figure 1 , an embodiment of the present invention provides a cross-domain authentication system for Internet of Vehicles based on blockchain.

[0079] The cross-domain authentication system for Internet of Vehicles based on blockchain described in the present invention can be loaded in an electronic device. According to the functions to be implemented, the cross-domain authentication system for Internet of Vehicles based on blockchain includes at least two domains, each domain includes a Trust Authority (TA), a Road Side Unit (RSU), a Vehicle (V) and an Agent Server (AS), and the Agent Servers of each domain together constitute a blockchain;

[0080] The trusted authentication center is used to initialize system parameters and register the identity information of roadside units and vehicles in the Internet of Vehicles; the roadside units are used to monitor vehicle driving data information in real time; the proxy server is used to process cross-domain authentication requests; the blockchain stores smart contracts for cross-domain authentication, and the RSA cumulative values ​​of the cross-domain identities of all vehicles in each domain are stored in the blockchain; the proxy server can determine the vehicle quantity information and vehicle identity information of each domain based on the RSA cumulative values ​​of each domain.

[0081] refer to Figure 1 and Figure 2 , the cross-domain authentication methods of Internet of Vehicles based on blockchain include:

[0082] S1. The trusted authentication center initializes system parameters and registers the identity information of the roadside unit RSU and the identity information of the vehicle V in the Internet of Vehicles.

[0083] Specifically, the steps for the trusted authentication center to initialize the system are: select a security parameter λ to generate an RSA modulus (N, X′, Y′), X, Y are two large prime numbers, N=XY, the length of N is λ, the initial system parameters are {N, H1(·), H2(·), H3(·), H4(·)}, N is the system modulus, H1(·), H2(·), H3(·) and H4(·) are all hash functions.

[0084] At the same time, the trusted authentication center of each domain performs the trusted authentication center initialization. The steps of the trusted authentication center initialization are as follows: the trusted authentication center TA in domain i i Randomly select an order q and a generator P i The additive cyclic group G i , i is the index value of the domain, the trusted authentication center TA in domain i i Random Selection As the system private key, calculate TPK i =TSK i ·P i As the system master public key, TA i Public TPK i ,q,P i , G i , complete the initialization of the trusted certification center.

[0085] When registering the identity information of the roadside unit RSU, the roadside unit RSU applies for registration to the local trusted authentication center TA: Specifically, the RSU in domain i ij First randomly select Calculate rpk ij，1 =rsk ij，1 ·P i , where i is the index value of the domain in the cross-domain authentication system, j is the index of the terminal identity in each domain, and both i and j are positive integers; Roadside Unit RSU ij represents the jth roadside unit RSU in the i-th domain, rsk ij，1 Roadside Unit RSU ij The randomly selected private key generated, P i It is the trusted authentication center TA in domain i i The published additive cyclic group G i The generator of , “·” represents the dot addition operation, rsk ij，1 ·P i Denotes a point P on the cyclic group i Perform rsk ij，1 Compared with the traditional bilinear pairing operation, the use of elliptic curve group addition operation can reduce the computational overhead and improve the authentication efficiency.

[0086] After that, the roadside unit RSU ij TA i Initiate a registration request {RID ij , rpk ij，1}, where RID ij Roadside Unit RSU ij The identity of rpk ij，1 Roadside Unit RSU ijGenerated public key; Trusted Certification Authority TA i Accepts the response to the roadside unit RSU after receiving the registration request ij Registration request, first check RID ij Authenticity, Trusted Certification Center TA i Random Selection Calculate A ij =a ij ·P i , R rij =a ij +H1(RID ij , rpk ij，1 , A ij , T rij )TSK i ,TSK i is the system private key, and finally the trusted authentication center TA i The generated registration information {R rij , A ij , T rij}Send to RSU ij , where R rij A is the roadside unit registration information generated by the trusted authentication center. ij Roadside Unit RSU ij The key generated by the trusted certification center during registration, T rij For RSU ij The timestamp generated by the trusted certification authority during registration;

[0087] RSU ij Received from the Trusted Authentication Authority TA i After registering the information, first check the timestamp T rij Is it within the allowed time range? Verify R rij ·P i =A ij +H1(RID ij , rpk ij，1 , A ij , T rij )TPK i Is it true that H1(·) is a collision-resistant one-way hash function, RID ij , rpk ij，1 , A ij , T rij is the input value of the hash function H1(·);

[0088] If R rij ·P i =A ij +H1(RID ij , rpk ij，1 , A ij , Trij )TPK i If R rij ·P i ≠A ij +H1(RID ij , rpk ij，1 , A ij , T rij )TPK i , the registration fails.

[0089] When registering the identity information of vehicle V, vehicle V applies for registration to the local trusted authentication center TA: Specifically, vehicle V in domain i ij Random Selection V ij represents the jth vehicle V in the i-th domain; calculate vpk ij，1 =vsk ij，1 ·P i , to the trusted authentication center TA i Initiate a registration request (VID ij , vpk ij，1}; Among them, VID ij For vehicle V ij Identity identifier, vpk ij，1 For vehicle V ij The generated public key;

[0090] Trusted Certification Authority i After receiving the request, respond to the vehicle registration request and check the VID first ij The authenticity of For vehicle V ij Generate pseudonymous AID ij ={aid ij , T vij}; represents the XOR operation, H2(·) is a collision-resistant one-way hash function, TSK i , T vij is the input value of the hash function H2(·), T vij For vehicle V ij Trusted Certification Authority TA i The timestamp of generation;

[0091] Trusted Certification Authority i Random Selection Calculate B ij =b ij ·P i , based on pseudonymous AID ij For vehicle V ij Generate vehicle registration information R vij

[0092] R vij =b ij +H1(aid ij , vpk ij，1 , B ij , T vij )TSK i , then the trusted authentication center TA i {R vij , B ij , AID ij}Send to vehicle V ij ; R rij TA is a trusted authentication center i Generated roadside unit information, B ij For vehicle V ij The key generated by the trusted authentication center during registration, AID ij For vehicle V ij alias;

[0093] Vehicle V ij Upon receipt of registration information {R vij , B ij , AID ij}, first check the timestamp T vij Is it within the allowed time range? Verify R vik ·P i =B ij +H1(aid ij , vpk ij，1 , B ij , T vij )TPK i Is it established?

[0094] If R vij ·P i =B ij +H1(aid ij , vpk ij，1 , B ij , T vij )TPK i If the vehicle V ij Registration is successful; if R vij ·P i ≠B ij +H1(aid ij , vpk ij，1 , B ij , T vij )TPK i , then the vehicle V ij Registration failed.

[0095] Vehicle V ijAfter successful registration, the trusted authentication center TA i Set the vehicle V ij Registration information {R vij , AID ij} to the proxy server AS, which calculates the vehicle V ij Identity information ID ij =H3(R vij , AID ij ), and use the Hprime function to convert ID ij Map to a prime number to get the vehicle V ij The prime identity of x ij =Hprime(ID ij ), the Hprime function is to convert ID ij Mapping to non-odd prime number x ij , using vehicle V ij The prime identity of x ij Calculate the cumulative identity value of all registered vehicles in the entire domain.

[0096] x ij Add to the RSA accumulator to get the cumulative value of all registered vehicle identities in domain i And generate a witness value m is the index value of all registered vehicles in domain i; the accumulated value Packed into the block, the witness value Send to vehicle V ij , complete the preliminary preparations for cross-domain authentication.

[0097] The anonymous identity of the vehicle is generated under the supervision and management of the trusted center, allowing the vehicle to use a pseudonym for cross-domain authentication. The vehicle uses the pseudonym to complete interactive authentication with the roadside unit; when the vehicle engages in malicious behavior, the anonymous protection of the vehicle identity information is achieved.

[0098] When a vehicle engages in malicious behavior, the trusted center TA can obtain the vehicle's true identity and achieve traceability of the malicious behavior; only vehicles with legitimate IDs and relevant identity information can generate verifiable authentication requests, thereby resisting impersonation attacks; each pseudonym and cross-domain authentication request includes a timestamp to ensure the timeliness of the pseudonym and request information to avoid forgery and replay attacks.

[0099] S2, each roadside unit RSU periodically broadcasts its own identity information;

[0100] Specifically, the roadside unit RSU ij The identity information is {R rij , RID ij , rpk ij，1 , Aij , T rij}

[0101] S3, Vehicle V ij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The identity information of the vehicle is verified; if the vehicle V ij If the authentication is successful, the vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ij ;

[0102] It should be noted that the roadside unit RSU here ij The value of i and the vehicle V ij The value of i can take different values, roadside unit RSU ij The value of j and the vehicle V ij The value of j can also take different values. Only i and j are used to represent different terminals in different domains without specific value orientation. For example, in the specific example, vehicle V 31 (representing the first vehicle V in domain 3) enters the roadside unit RSU 28 (representing the 8th roadside unit RSU in domain 2) can be used for roadside unit RSU 28 The identity information of the vehicle is verified; if the vehicle V 31 If the authentication is successful, the vehicle V 31 Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU 28 .

[0103] Roadside Unit RSU ij The identity information is {R rij , RID ij , rpk ij，1 , A ij , T rij}, vehicle V ij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The steps to verify identity information include:

[0104] Vehicle V ij Enter the roadside unit RSU ij When the communication range is

[0105] Verify R rij ·P i =A ij +H1(RID ij , rpk ij，1 , A ij , T rij)TPK i Is it true, where P i is the generator, H1(RID ij , rpk ij，1 , A ij , T rij ) is a hash function, TPK i is the system public key;

[0106] If so, then the vehicle V ij Roadside Unit RSU ij Authentication successful;

[0107] If not, then the vehicle V ij Roadside Unit RSU ij Authentication failed.

[0108] S4, Roadside Unit RSU ij Respond to cross-domain authentication requests through zero-knowledge proof of vehicle V ij The anonymous identity is authenticated. If the authentication is successful, a roadside unit RSU is established. ij With vehicle V ij The connection between the roadside units RSU ij With vehicle V ij Cross-domain communication; if authentication fails, the roadside unit RSU ij Reject Vehicle V ij Cross-domain authentication request.

[0109] Vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ij include:

[0110] S401: Vehicle V ij Random Selection Calculate C ij =c ij ·P i ;

[0111] C ij is the vehicle V ij The first proof value generated;

[0112] Then we get α ij =H2(c ij ·rpk ij，1 , RID ij ,aid ij , T1);

[0113] β ij =α ij H1(aid ij , vpk ij，1 , Bij , T vij ) -1 ;

[0114] Among them, α ij is the first intermediate value, β ij The second middle value, aid ij For vehicle V ij Anonymous identity of vehicle V ij The timestamp when the cross-domain authentication request was sent;

[0115] S402: Based on the first intermediate value α ij and the second intermediate value β ij Determine vehicle V ij Commitment information and certification information;

[0116] The calculation formula for commitment information is π ij =c ij +β ij R vij ;

[0117] The calculation formula of the proof information is γ ij =β ij B ij ; δ ij =α ij TPK i ;

[0118] π ij For vehicle V ij Committed value for roadside unit RSU ij Verify identity; ij For vehicle V ij The second proof value, δ ij For vehicle V ij The third proof value of the vehicle is obtained by using the second proof value γ without exposing the vehicle private key. ij and the third proof value δ ij Proof Vehicle V ij Validity of the private key;

[0119] S403: Based on vehicle V ij The commitment information and proof information generate vehicle V ij Cross-domain authentication information;

[0120] The cross-domain authentication information is The zone identity witness value generated for the proxy server; AID ij For vehicle V ij AID ij ={aid ij , T vij};

[0121] S404: Generate a cross-domain authentication request based on the cross-domain identity authentication information and send it to the roadside unit RSU ij .

[0122] Roadside Unit RSU ij Through zero-knowledge proof, the vehicle V ij The steps for anonymous identity authentication include:

[0123] S501: RSU ij Check whether the timestamp T1 exceeds the preset time range. If it does not exceed the preset time range, the verification is passed and step S502 is executed; if it exceeds the preset time range, the authentication fails;

[0124] S502: Verify π ij ·P i =C ij +γ ij +δ ij Is it true? If the equation is true, then the vehicle V ij If the anonymous identity authentication is passed, step S503 is executed; if not, the authentication fails;

[0125] The following is a specific example of vehicle V ij The verification basis of anonymous authentication is described as follows: Assuming that the RSU in domain j is used j1 Used to verify vehicle V i 1 identity then π i1 ·P i =(c i1 +β i1 R vi1 )·P i

[0126] =C i1 +α i1 ·H1(aid i1 , vpk i1,1 , B i1 , T vi1 ) -1 ·(b i1 +H1(aid i1 , vpk i1，1 , B i1 , T vil )TSK i )·P i

[0127] =C i1 +α i1 .H1(aid i1 , vpk i1，1 , Bi1 , T vi1 ) -1 ·B i1 +α i1 ·TPK i

[0128] =C i1 +β i1 ·B i1 +δ i1

[0129] =C i1 +γ i1 +δ i1 ,

[0130] During the verification process, the real identity of the vehicle V is hidden because of the use of pseudonyms. i1 ·P i =C i1 +γ i1 +δ i1 , RSU j1 It can be seen that V i1 is a pseudonym from domain i called AID i1 The vehicle V is completed ij Anonymous identity authentication.

[0131] S503: Roadside Unit RSU ij According to the vehicle V ij Anonymous ID aid ij Request the RSA cumulative value of all vehicle cross-domain identities in domain i from the proxy server AS And calculate the ID ij =H3(R vij , AID ij ), ID ij For vehicle V ij identity information; H3(R vij , AID ij ) is a hash function, and the input value of the hash function is R vij and AID ij .

[0132] S504: Use Hprime function to convert ID ij Mapped to a prime number x ij , get vehicle V ij The prime identity of x ij ;

[0133] S505: Verification Is it equal to like Then the vehicle V ij Pseudonymous identity is legal, roadside unit RSUij Complete the vehicle V ij Cross-domain authentication; if Then the cross-domain authentication fails.

[0134] In the preferred implementation of this embodiment, the exponentiation operation is used to Calculate the value of

[0135] x ij Expressed in binary form, x ij =x k 2 k +x k-1 2 k-1 +x k-2 2 k-2 +…+x22 2 +x12 1 +x02 0 , x k ∈{0,1} and x k =1,

[0136] but get Value

[0137] (mod N) represents the remainder operation, which is to divide a number by N to get the remainder. To the middle (·) 2 Each calculation result must be subjected to the mod N operation;

[0138] The exponentiation method effectively converts n independent and time-consuming modular exponentiation operations into a series of multiplication and square operations, reducing the algorithm complexity to O(2log2n), thereby improving the accuracy of The computational efficiency of the value.

[0139] Reference Figure 3 In another embodiment of the present application, the Internet of Vehicles cross-domain authentication method based on blockchain further includes:

[0140] S5, Roadside Unit RSU ij Upon receiving cross-domain authentication requests issued by multiple vehicles V, determining the domains to which the multiple vehicles V issuing the cross-domain authentication requests belong;

[0141] S6, if the roadside unit RSU ij When cross-domain authentication requests from different vehicles V in the same domain are received, batch confirmation is performed on the cross-domain authentication requests from different vehicles V in the same domain.

[0142] Batch confirmation of cross-domain authentication requests of different vehicles V in the same domain includes:

[0143] S601: When the roadside unit RSU ij When receiving cross-domain authentication requests from different vehicles V in the same domain, for n vehicles from the same domain m, the roadside unit RSU ij Random Generation

[0144] t is a random integer, a is the index of the vehicle that issued the cross-domain authentication request in domain m;

[0145] S602: Verify the equation through zero knowledge Whether it is established, so as to determine the correctness of the vehicle pseudonym in batches; among them, P m is the generator, π ma For vehicle V ma The commitment value, C ma is the vehicle V ma The first proof value generated; γ ma For vehicle V ma The second proof value, δ ma For vehicle V ma The third proof value of

[0146] If the equation If the pseudonyms of n vehicles in domain m are all verified,

[0147] Then the batch cross-domain authentication of n vehicles in domain m fails.

[0148] Specifically, for n vehicles in domain m, we have

[0149]

[0150] Add the left and right sides of the above n equations to get Multiply each term by v i , is to reduce the possibility of paired malicious signatures being authenticated. Batch verification of vehicles in the same domain can reduce the computational overhead of point multiplication operations and reduce computing costs.

[0151] S603: Verify each vehicle Is it equal to

[0152] is the RSA cumulative value of the cross-domain identities of all vehicles in domain m, The zone identity witness value generated by the proxy server for domain m, x mn For vehicle V mn The prime identity of

[0153] Calculate all The product of

[0154] Calculate all x mn The product of

[0155] Use the recursive algorithm PowerRecur(n,A,x) to calculate Among them, A is the first array, and its elements are A i , i = 1, 2, ..., n; x is the second array, the elements of which are x i , i=1, 2, ..., n; n represents the size of the first array and the second array;

[0156] like Then the batch cross-domain verification is passed; if Then batch cross-domain verification fails.

[0157] In this embodiment, the process of using the recursive algorithm PowerRecur to process the input data n, A, x to obtain y is as follows:

[0158] Split the first array A into

[0159] A L =(A1, A2, ..., A n / 2 ), A R =(A n / 2+1 , A n / 2+2 , …, A n ), where A L is the left half of the first array A, A R is the right half of the elements of the first array A;

[0160] After that, split the second array x to get

[0161] x L =(x1, x2, ..., x n / 2 ), x R =(x n / 2+1 , x n / 2+2 , …, x n ), where x L is the left half of the elements of the second array x, x R is the right half of the elements of the second array x;

[0162] Then, calculate x L * =x1x2…x n / 2 , x R * =x R / 2+1 x n / 2+2 …xn ;

[0163] L = PowerRecur(n / 2, A L , x L ), R = PowerRecur(n / 2, A R , x R );

[0164] Among them, x L * is the third intermediate value, which represents the product of the left half of the elements of the second array x; R * is the fourth intermediate value, indicating the product of the right half of the elements of the second array x; L is the fifth intermediate value, indicating the product of the elements of array A L and x L The result of calling the function PowerRecur with the parameter, R is the sixth intermediate value, indicating that the array A R and x R The result of calling the function PowerRecur for the parameter;

[0165] final “·” indicates multiplication.

[0166] The various variations and specific examples of the Internet of Vehicles cross-domain authentication method based on blockchain provided in this embodiment are also applicable to the Internet of Vehicles cross-domain authentication system based on blockchain provided in the above embodiments. Through the above detailed description of the Internet of Vehicles cross-domain authentication method based on blockchain, those skilled in the art can clearly know the implementation method of the Internet of Vehicles cross-domain authentication system based on blockchain. For the sake of brevity of the specification, it will not be described in detail here.

[0167] The present application also discloses an electronic device, such as Figure 4 , which is a schematic diagram of the structure of an electronic device of a vehicle network cross-domain authentication method based on blockchain provided by an embodiment of the present invention. The electronic device may include at least one processor 10, a memory 11 connected to at least one processor for communication, a communication bus 12, and a communication interface 13, and may also include a computer program stored in the memory 11 and executable on the processor 10, such as a method program for vehicle network cross-domain authentication based on blockchain.

[0168] Among them, the processor 10 can be composed of an integrated circuit in some embodiments, for example, it can be composed of a single packaged integrated circuit, or it can be composed of multiple integrated circuits packaged with the same function or different functions, including one or more central processing units (CPU), microprocessors, digital processing chips, graphics processors and various control chips. The processor 10 is the control core (Control Unit) of the electronic device, and uses various interfaces and lines to connect the various components of the entire electronic device. It runs or executes the program or module stored in the memory 11 (for example, a method for executing cross-domain authentication of the Internet of Vehicles based on blockchain, etc.), and calls the data stored in the memory 11 to execute various functions of the electronic device and process data.

[0169] The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 11 may be an internal storage unit of an electronic device, such as a mobile hard disk of the electronic device. In other embodiments, the memory 11 may also be an external storage device of an electronic device, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Furthermore, the memory 11 may also include both an internal storage unit of the electronic device and an external storage device. The memory 11 can not only be used to store application software and various types of data installed in the electronic device, such as the code of the cross-domain authentication method program of the Internet of Vehicles based on blockchain, but also can be used to temporarily store data that has been output or is to be output.

[0170] The communication bus 12 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. The bus is configured to realize connection and communication between the memory 11 and at least one processor 10, etc.

[0171] The communication interface 13 is used for communication between the above-mentioned electronic device and other devices, including a network interface and a user interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is generally used to establish a communication connection between the electronic device and other electronic devices. The user interface may be a display (Display), an input unit (such as a keyboard (Keyboard)), and optionally, the user interface may also be a standard wired interface, a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emi tt ing Diode, organic light-emitting diode) touch device, etc. Among them, the display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the electronic device and to display a visualized user interface.

[0172] Figure 4 Only an electronic device with components is shown, and those skilled in the art will understand that Figure 4 The structure shown does not constitute a limitation on the electronic device, and may include fewer or more components than shown, or combine certain components, or arrange the components differently. For example, although not shown, the electronic device may also include a power supply (such as a battery) for supplying power to each component. Preferably, the power supply may be logically connected to at least one processor 10 through a power management device, so that functions such as charging management, discharging management, and power consumption management are implemented through the power management device. The power supply may also include any components such as one or more DC or AC power supplies, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, etc. The electronic device may also include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

[0173] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited by this structure.

[0174] Furthermore, if the module / unit integrated in the electronic device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile.

[0175] The embodiment of the present application provides a computer-readable storage medium, for example, including: any entity or device, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM) that can carry the computer program code. The computer-readable storage medium stores a computer program that can be loaded by a processor and execute the cross-domain authentication method of the Internet of Vehicles based on blockchain in the above embodiment.

[0176] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", "an implementation", "a preferred implementation" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0177] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

Claims

1. A cross-domain authentication method for Internet of Vehicles based on blockchain, characterized in that: The method comprises: The trusted authentication center initializes system parameters and registers the identity information of the roadside unit RSU and the identity information of the vehicle V in the Internet of Vehicles; Each roadside unit RSU periodically broadcasts its own identity information; Vehicle V ij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The identity information of RSU is verified; ij represents the jth roadside unit RSU in the i-th domain, V ij represents the jth vehicle V in the i-th domain; roadside unit RSU ij The value of i and the vehicle V ij The value of i can take different values, roadside unit RSU ij The value of j and the vehicle V ij The value of j can also take different values, using i and j to represent different terminals in different domains; If the vehicle V ij If the authentication is successful, the vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ij ; The roadside unit RSU ij Respond to cross-domain authentication requests through zero-knowledge proof of vehicle V ij The anonymous identity is authenticated. If the authentication is successful, a roadside unit RSU is established. ij With vehicle V ij The connection between the roadside units RSU ij With vehicle V ij Cross-domain communication; if authentication fails, the roadside unit RSU ij Reject Vehicle V ij Cross-domain authentication request; The method further comprises: Roadside Unit RSU ij Upon receiving cross-domain authentication requests issued by multiple vehicles V, determining the domains to which the multiple vehicles V issuing the cross-domain authentication requests belong; If the roadside unit RSU ij When receiving cross-domain authentication requests from different vehicles V in the same domain, batch confirmation is performed on the cross-domain authentication requests from different vehicles V in the same domain; The batch confirmation of cross-domain authentication requests of different vehicles V in the same domain includes: S601: When the roadside unit RSU ij When receiving cross-domain authentication requests from different vehicles V in the same domain, for n vehicles from the same domain m, the roadside unit RSU ij Random Generation t is a random integer; S602: Verify the equation through zero knowledge Is it established? m is the generator, π ma For vehicle V ma The commitment value, C ma is the vehicle V ma The first proof value generated; γ ma For vehicle V ma The second proof value, δ ma For vehicle V ma The third proof value of , a is the index of the vehicle that issued the cross-domain authentication request in domain m; If the equation If the pseudonyms of n vehicles in domain m are all verified, Then the batch cross-domain authentication of n vehicles in domain m fails; S603: Verify each vehicle Is it equal to is the RSA cumulative value of the cross-domain identities of all vehicles in domain m, The zone identity witness value generated by the proxy server for domain m, x mn For vehicle V mn The prime identity of Calculate all The product of Calculate all x mn The product of Use the recursive algorithm PowerRecur(n,A,x) to calculate Where A is the first array, x is the second array, and n represents the size of the array; like Then the batch cross-domain verification is passed; if Then batch cross-domain verification fails.

2. The cross-domain authentication method for Internet of Vehicles based on blockchain as claimed in claim 1, characterized in that: Roadside Unit RSU ij The identity information is {Rr ij ,RID ij ,rpk ij,1 ,A ij ,T rij }, where R rij Roadside unit registration information generated by a trusted authentication center, RID ij Roadside Unit RSU ij The identity of rpk ij,1 Roadside Unit RSU ij The generated public key, A ij Roadside Unit RSU ij The key generated by the trusted certification center during registration, T rij For RSU ij The timestamp generated by the trusted certification authority during registration; The vehicle V ij Entering the Roadside Unit RSU ij The communication range of the roadside unit RSU ij The steps to verify identity information include: Vehicle V ij Enter the roadside unit RSU ij When the communication range is Verify R rij ·P i =A ij +H1(RID ij , rpk ij，1 , A ij , T rij )TPK i Is it true, where P i is the generator, H1(RID ij ,rpk ij,1 ,A ij ,T rij ) is a hash function, TPK i is the system public key; If so, then the vehicle V ij Roadside Unit RSU ij Authentication successful; If not, then the vehicle V ij Roadside Unit RSU ij Authentication failed.

3. The cross-domain authentication method for Internet of Vehicles based on blockchain as claimed in claim 2, characterized in that: The vehicle V ij Generate a cross-domain authentication request using an anonymous identity and send it to the roadside unit RSU ij include: S401: Vehicle V ij Random Selection Calculate C ij =c ij ·P i , C ij is the vehicle V ij The first proof value generated; Then we get α ij =H2(c ij ·rpk ij,1 ,RID ij ,aid ij ,T1); b ij =a ij H1(aid ij ,vpk ij,1 ,B ij ,T vij ) -1 ; Among them, α ij is the first intermediate value, β ij The second intermediate value, H2(c ij ·rpk ij,1 ,RID ij ,aid ij ,T1) represents the hash function, aid ij For vehicle V ij Anonymous identity of vehicle V ij Timestamp when sending cross-domain authentication request, vpk ij,1 For vehicle V ij The generated public key, B ij For vehicle V ij The key generated by the trusted certification center during registration, T vij For vehicle V ij The timestamp generated by the trusted certification authority during registration; S402: According to the first intermediate value α ij and the second intermediate value β ij Determine vehicle V ij Commitment information and certification information; The calculation formula for commitment information is π ij =c ij +β ij R vij ; The calculation formula of the proof information is γ ij =β ij B ij ; δ ij =α ij TPK i ; π ij For vehicle V ij The commitment value of ij For vehicle V ij The second proof value, δ ij For vehicle V ij The third proof value of S403: Based on vehicle V ij The commitment information and proof information generate vehicle V ij Cross-domain authentication information; Vehicle V ij The cross-domain authentication information is {AID ij ,γ ij ,δ ij ,π ij ,R ij ,W xij ,C ij ,T1},W xij The zone identity witness value generated for the proxy server; AID ij For vehicle V ij AID ij ={aid ij ,T vij }; S404: Generate a cross-domain authentication request based on the cross-domain identity authentication information and send it to the roadside unit RSU ij .

4. The cross-domain authentication method for Internet of Vehicles based on blockchain as claimed in claim 3, characterized in that: The roadside unit RSU ij Through zero-knowledge proof, the vehicle V ij The steps for anonymous identity authentication include: S501: RSU ij Check whether the timestamp T1 exceeds the preset time range. If it does not exceed the preset time range, the verification is passed and step S502 is executed; if it exceeds the preset time range, the authentication fails; S502: Verify π ij ·P i =C ij +γ ij +δ ij Is it true? If the equation is true, then the vehicle V ij If the anonymous identity authentication is passed, step S503 is executed; if not, the authentication fails; S503: Roadside Unit RSU ij According to the vehicle V ij Anonymous ID aid ij Request the RSA cumulative value of all vehicle cross-domain identities in domain i from the proxy server AS And calculate the ID ij =H3(R vij ,AID ij ), ID ij For vehicle V ij identity information; H3(R vij ,AID ij ) represents a hash function; S504: Use Hprime function to convert ID ij Mapped to a prime number x ij , get vehicle V ij The prime identity of x ij ; S505: Verification Is it equal to like Then the vehicle V ij Pseudonymous identity is legal, roadside unit RSU ij Complete the vehicle V ij Cross-domain authentication; if Then the cross-domain authentication fails.

5. The cross-domain authentication method for Internet of Vehicles based on blockchain as claimed in claim 4 is characterized in that: For vehicle V ij The prime identity of x ij and the zone identity witness value generated by the proxy server Processing to obtain When using the exponentiation operation to calculate The value of x ij Expressed in binary form, x ij =x k 2 k +x k-1 2 k-1 +x k-2 2 k-2 +…+x22 2 +x12 1 +x02 0 ,x k ∈{0,1} and x k =1, but get The value of .

6. A vehicle network cross-domain authentication system based on blockchain, used to implement the vehicle network cross-domain authentication method based on blockchain as claimed in any one of claims 1 to 5, characterized in that: It includes at least two domains, each domain includes a trusted authentication center, a roadside unit, a vehicle, and a proxy server, and the proxy servers of each domain together constitute a blockchain; The trusted authentication center is used to initialize system parameters and register the identity information of the roadside unit and the vehicle in the Internet of Vehicles; Roadside units are used to monitor vehicle driving data information in real time; The proxy server is used to process cross-domain authentication requests; The blockchain stores smart contracts for cross-domain authentication, and the RSA cumulative values ​​of the cross-domain identities of all vehicles in each domain are stored in the blockchain.

7. An electronic device, characterized in that: The electronic device comprises: at least one processor (10); and, a memory (11) communicatively connected to the at least one processor (10); The memory (11) stores a computer program that can be executed by the at least one processor (10), and the computer program is executed by the at least one processor (10) so that the at least one processor (10) can execute the blockchain-based Internet of Vehicles cross-domain authentication method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program; when the computer program is executed by the processor, the blockchain-based Internet of Vehicles cross-domain authentication method is implemented as described in any one of claims 1 to 5.

Images