Key verification method and device, vehicle, storage medium, electronic equipment and program product

Abstract

The disclosure provides a key verification method and device, a vehicle, a storage medium, an electronic device and a program product, and relates to the technical field of Internet of Vehicles. The method comprises the following steps: a key verification request is sent to a target vehicle; the key verification request comprises at least a to-be-verified shared user key certificate; the to-be-verified shared user key certificate comprises at least a car owner key public key, a car owner key public key signature and a sharing proof; the car owner key public key signature is a signature of the car owner key public key by a car owner identity private key; and the to-be-verified shared user key certificate is activated in response to the key verification request passing verification. By embedding the car owner key public key in the shared user key certificate, the history public key of the car owner does not need to be stored when the key verification is performed, and the sharing proof in the shared user key certificate can be verified; the verification of the shared user key certificate is unbonded from the re-opening of the car owner key, and the change of the car owner key will not affect the verification of the target shared user key certificate.

Description

Technical Field

[0001] This disclosure relates to the field of vehicle networking technology, and in particular to a key verification method, device, vehicle, storage medium, electronic device, and program product. Background Technology

[0002] A digital car key is a method of accessing and starting a vehicle using wireless communication technology. It replaces the traditional physical key with a smartphone, smartwatch, or other wearable device. Car owners can generate shareable keys through an app and share them with designated users. By sharing the shareable key with designated users, car owners can grant them access to their vehicle without physically exchanging traditional keys. Sharing digital car keys offers convenience and a good user experience.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this disclosure provides a key verification method, device, vehicle, storage medium, electronic device, and program product.

[0005] According to a first aspect of the present disclosure, a key verification method is provided, comprising: sending a key verification request to a target vehicle; the key verification request including at least a shared user key certificate to be verified; the shared user key certificate to be verified including at least: a vehicle owner's key public key, a vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature being a signature of the vehicle owner's key public key by the vehicle owner's identity private key; and activating the shared user key certificate to be verified in response to the key verification request being verified successfully.

[0006] In some exemplary embodiments of this disclosure, the shared user key certificate to be verified further includes: the shared user key public key and / or the vehicle server CA signature.

[0007] According to a second aspect of the present disclosure, a key verification method is provided, comprising: receiving a car key sharing request; the car key sharing request including at least: target sharing device information and target vehicle information; responding to the car key sharing request, creating a sharing user key certificate; the sharing user key certificate including at least: a vehicle owner's key public key, a vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature being a signature of the vehicle owner's private key on the vehicle owner's key public key; and sending the sharing user key certificate to the target sharing device and the target vehicle based on the target sharing device information and the target vehicle information.

[0008] In some exemplary embodiments of this disclosure, the shared user key certificate further includes: a shared user key public key and / or a vehicle server CA signature.

[0009] In some exemplary embodiments of this disclosure, the method further includes: obtaining the vehicle owner key public key and the vehicle owner identity private key through a pre-stored vehicle owner key certificate; and signing the vehicle owner key public key with the vehicle owner identity private key to obtain the vehicle owner key public key signature.

[0010] According to a third aspect of the present disclosure, a key verification method is provided, comprising: receiving a key verification request; the key verification request including at least a shared user key certificate to be verified; the shared user key certificate to be verified including at least: a vehicle owner's key public key, a vehicle owner's key public key signature, and a sharing proof; the vehicle owner's key public key signature being a signature of the vehicle owner's key public key by the vehicle owner's identity private key; verifying the vehicle owner's key public key signature using a pre-stored vehicle owner's identity public key; verifying the sharing proof using the vehicle owner's key public key if the vehicle owner's key public key signature passes verification; and activating the shared user key certificate to be verified in response to the successful verification of the sharing proof.

[0011] In some exemplary embodiments of this disclosure, the method further includes: obtaining the vehicle owner's identity public key through a pre-stored vehicle owner key certificate.

[0012] In some exemplary embodiments of this disclosure, the vehicle owner key certificate further includes: a first vehicle owner key public key; the vehicle owner key public key is different from the first vehicle owner key public key.

[0013] In some exemplary embodiments of this disclosure, activating the shared user key certificate to be verified includes: activating a pre-stored shared user key certificate corresponding to the shared user key certificate to be verified.

[0014] According to a fourth aspect of the present disclosure, a key verification device is provided, comprising: a key verification request sending module, configured to send a key verification request to a target vehicle; the key verification request includes at least a shared user key certificate to be verified; the shared user key certificate to be verified includes at least: a vehicle owner's key public key, a vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's key public key by the vehicle owner's identity private key; and an activation module, configured to activate the shared user key certificate to be verified in response to the key verification request being verified successfully.

[0015] According to a fifth aspect of the present disclosure, a key verification device is provided, comprising: a car key sharing request receiving module, configured to receive a car key sharing request; the car key sharing request includes at least: target sharing device information and target vehicle information; a sharing user key certificate creation module, configured to create a sharing user key certificate in response to the car key sharing request; the sharing user key certificate includes at least: a vehicle owner key public key, a vehicle owner key public key signature, and a sharing proof; the vehicle owner key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner key public key; and a sharing user key certificate sending module, configured to send the sharing user key certificate to the target sharing device and the target vehicle according to the target sharing device information and the target vehicle information.

[0016] According to a sixth aspect of the present disclosure, a key verification device is provided, comprising: a key verification request receiving module, configured to receive a key verification request; the key verification request includes at least a shared user key certificate to be verified; the shared user key certificate to be verified includes at least: a vehicle owner's key public key, a vehicle owner's key public key signature, and a sharing proof; the vehicle owner's key public key signature is a signature of the vehicle owner's key public key by the vehicle owner's identity private key; a vehicle owner's key public key signature verification module, configured to verify the vehicle owner's key public key signature using a pre-stored vehicle owner's identity public key; a sharing proof verification module, configured to verify the sharing proof using the vehicle owner's key public key in response to the vehicle owner's key public key signature passing verification; and an activation module, configured to activate the shared user key certificate to be verified in response to the sharing proof passing verification.

[0017] According to a seventh aspect of the present disclosure, an electronic device is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to implement any of the key verification methods described in the present disclosure.

[0018] According to an eighth aspect of the present disclosure, a vehicle is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to: implement the steps of any of the verification methods described herein.

[0019] According to a ninth aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the key verification method described in any one of the preceding claims.

[0020] According to a tenth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements any of the key verification methods described in the present disclosure.

[0021] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0022] In this embodiment, by embedding the vehicle owner's public key into the shared user key certificate, the sharing proof in the shared user key certificate can be verified without storing the vehicle owner's historical public key during key verification. To ensure the legitimacy of the vehicle owner's public key, the vehicle owner's public key is signed using the vehicle owner's private key to obtain the vehicle owner's public key signature. The vehicle owner's private key is the unique credential held by the vehicle owner and will not change with changes to the vehicle key. This allows for the verification of the vehicle key's legitimacy using the vehicle owner's public key signature when the vehicle owner's public key changes. The verification of the shared user key certificate is decoupled from the reactivation of the vehicle owner's key, ensuring that changes to the vehicle owner's key do not affect the verification of the target shared user key certificate, thus optimizing the verification and user experience of the shared user key.

[0023] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0024] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0025] Figure 1 This is a flowchart illustrating a key verification method according to an exemplary embodiment of the present disclosure. Figure 1

[0026] Figure 2 This is a flowchart illustrating a key verification method according to an exemplary embodiment of the present disclosure. Figure 2 .

[0027] Figure 3 This is a flowchart illustrating a key verification method according to an exemplary embodiment of the present disclosure. Figure 3 .

[0028] Figure 4 This is a scenario diagram illustrating a key verification method according to an exemplary embodiment of the present disclosure.

[0029] Figure 5 This is an interactive key verification method illustrated according to an exemplary embodiment of the present disclosure. Figure 1 .

[0030] Figure 6 This is a first block diagram illustrating a key verification device according to an exemplary embodiment of the present disclosure.

[0031] Figure 7 This is a second block diagram illustrating a key verification device according to an exemplary embodiment of the present disclosure.

[0032] Figure 8 This is a third block diagram illustrating a key verification device according to an exemplary embodiment of the present disclosure.

[0033] Figure 9 This is a functional block diagram of a vehicle according to an exemplary embodiment of the present disclosure.

[0034] Figure 10 This is a block diagram illustrating an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0035] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0036] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0037] With the increasing adoption of digital car keys, more and more car owners are sharing their digital car keys with other users for vehicle authorization. When a car owner authorizes a user with their key, the shared user's key is sent to the user's target sharing device. The user then needs to authenticate their key the first time they use it.

[0038] In the existing ICCOA standard specification protocol process, when a shared user key is used for the first time, the owner key certificate needs to be activated. If it is not activated, the shared user key will not be able to complete the verification and activation. Specifically, based on the existing authentication protocol, if the owner key is in normal use, i.e., activated, the shared user key can interact with the vehicle for authentication. After successful verification, the shared user key can be activated, at which point the user can start and use the vehicle.

[0039] If the owner's key changes, for example, if the owner reactivates the owner's key, the shared user key that was previously shared with other users will be inactive. Because the updated owner's key information is missing, the shared user key cannot be verified in the vehicle and therefore cannot be used.

[0040] Figure 1 This is a flowchart illustrating a key verification method according to an exemplary embodiment of the present disclosure. Figure 1 The method described in this embodiment can be applied to electronic devices, including smartphones, smartwatches, smart glasses, smart tablets, and other smart wearable devices.

[0041] In some implementations, the key verification method of this disclosure includes:

[0042] In step S110, a key verification request is sent to the target vehicle; the key verification request includes at least the key certificate of the sharing user to be verified; the key certificate of the sharing user to be verified includes at least: the owner's key public key, the owner's key public key signature, and the sharing proof; the owner's key public key signature is the signature of the owner's identity private key on the owner's key public key;

[0043] This disclosure can be applied to a target sharing device for a sharing user, which serves as the user's credential for key verification and vehicle use. The vehicle owner's device serves as the vehicle owner's credential for vehicle use. The vehicle server is responsible for processing data requests from the vehicle, vehicle owner's device, and target sharing device and providing corresponding services. The vehicle owner's device, target sharing device, vehicle, and vehicle server are interconnected.

[0044] The target sharing device already stores the unverified sharing user key certificate sent by the vehicle server; this unverified sharing user key certificate is created by the vehicle server based on the vehicle key sharing request. When creating the unverified sharing user key certificate, the vehicle server uses the vehicle owner's private key to sign the vehicle owner's key public key to obtain the vehicle owner's key public key signature, and embeds the vehicle owner's key public key signature, the vehicle owner's key public key, and the sharing proof into the unverified sharing user key certificate.

[0045] The aforementioned sharing proof is used to verify the authenticity and legality of sharing a user's key certificate through digital signature. It is typically a data structure or document containing specific information designed to ensure that the sharing operation meets expected security standards and allows the recipient to verify the source and permissions of the sharing. This sharing proof may include: the identity of the authorized object, the time range of the authorization, and the type of authorized permissions. The vehicle owner's private key and public key are generated and stored by the vehicle server; these are collectively referred to as the vehicle owner's public-private key. Each vehicle owner possesses a unique vehicle owner public-private key. However, a vehicle owner's key public key and private key can be changed, or a vehicle owner may have multiple key public and private keys; these keys are bound to the vehicle owner's identity public and private key. For example, when a vehicle owner changes from a first vehicle owner device to a second, their vehicle owner's identity public and private key remains unchanged, but their corresponding key public and private keys will change.

[0046] When the target sharing device performs key verification, it sends a key verification request to the target vehicle. The key verification request includes at least the key certificate of the sharing user to be verified.

[0047] The vehicle receives the key certificate of the user to be verified and performs key verification. During key verification, the vehicle's terminal stores the owner's identity public key, which is used to verify the owner's key public key signature. The owner's identity public key and private key can mutually verify each other through digital signatures. Therefore, after the owner's key public key signature is verified, the sharing proof is then verified using the owner's key public key. The sharing proof ensures the legitimacy of the user's key certificate. After the sharing proof is verified, the user's key certificate to be verified is activated, and the overall verification is successful. The owner's key public key signature is verified based on the owner's identity public key. Since the owner's identity public key and private key are unique to one owner, the legitimacy of the owner's key public key is guaranteed and does not change with changes to the car key. After successful verification, the vehicle sends a key verification request to the target sharing device. The owner's key public key signature verification is successful, and the sharing proof is verified using the owner's key public key. If the sharing proof verification is successful... The system uses the owner's key public key signature to verify the legitimacy of the car key public key, and debinds the verification of the shared user's key certificate from the reactivation of the owner's key. Changes to the owner's key will not affect the verification of the shared user's key certificate, thus not affecting the target shared user's normal use of the vehicle.

[0048] In step S120, in response to the successful verification of the key verification request, the key certificate of the sharing user to be verified is activated.

[0049] The target sharing device receives and verifies the key verification request from the vehicle. Upon successful verification, the target sharing device activates the key certificate of the user to be verified. Based on the activated key certificate, the target sharing device is authorized to access and use the vehicle.

[0050] In this embodiment, by embedding the vehicle owner's public key into the shared user key certificate, the sharing proof in the shared user key certificate can be verified without storing the vehicle owner's historical public key during key verification. To ensure the legitimacy of the vehicle owner's public key, the vehicle owner's public key is signed using the vehicle owner's private key to obtain the vehicle owner's public key signature. The vehicle owner's private key is the unique credential held by the vehicle owner and will not change with changes to the vehicle key. This allows for the verification of the vehicle key's legitimacy using the vehicle owner's public key signature when the vehicle owner's key changes. The verification of the shared user key certificate is decoupled from the reactivation of the vehicle owner's key, ensuring that changes to the vehicle owner's key do not affect the verification of the shared user key certificate, thus optimizing the verification and user experience of the shared user key.

[0051] The embodiments disclosed herein are compatible with ICCOA standards and specifications, do not introduce an additional certificate system, and can be integrated with the standard models of other equipment manufacturers in the future.

[0052] In this embodiment of the disclosure, the shared user key certificate to be verified further includes: the shared user key public key and / or the vehicle server CA signature.

[0053] The public key of the shared user key in the certificate to be verified is used for authentication. Through digital signature technology, users can prove that they have the corresponding private key of the shared user key without having to expose it directly.

[0054] As a Certificate Authority (CA), one of the main responsibilities of the vehicle server is to issue digital certificates to various entities participating in the connected vehicle system (such as vehicles, owner devices, and target sharing devices). These certificates contain public keys and other identifying information and are signed by the vehicle server's private key. The vehicle server's CA signature in the shared user key certificate to be verified provides a mechanism to confirm that a public key indeed belongs to the claimed entity. By verifying the CA signature, the connected vehicle system can effectively defend against man-in-the-middle attacks.

[0055] Figure 2 This is a flowchart illustrating a key verification method according to an exemplary embodiment of the present disclosure. Figure 2The method described in this embodiment can be applied to a vehicle server. This vehicle server may include local servers and cloud servers, and the server can be deployed on a single computer or a computer cluster consisting of multiple computers.

[0056] In some implementations, the key verification method of this disclosure includes:

[0057] In step S210, a car key sharing request is received; the car key sharing request includes at least: target sharing device information and target vehicle information;

[0058] When a car owner wants to authorize a user to use the vehicle, they send a car key sharing request to the car server through the car owner's device.

[0059] The vehicle server receives a car key sharing request from the vehicle owner's device. The target sharing device information in this request refers to information about the target sharing device that the vehicle owner wants to share, such as the target sharing device's account and IP address. Simultaneously, the car key sharing request also includes target vehicle information, which refers to information about the vehicle that the vehicle owner wants to authorize for sharing, such as the vehicle's IP address, license plate number, vehicle identification number (VIN), and drive unit number.

[0060] In step S220, in response to the car key sharing request, a sharing user key certificate is created; the sharing user key certificate includes at least: the car owner's key public key, the car owner's key public key signature, and a sharing certificate; the car owner's key public key signature is a signature of the car owner's identity private key on the car owner's key public key;

[0061] The vehicle server responds to the car key sharing request sent by the vehicle owner's device and creates a sharing user key certificate based on the car key sharing request.

[0062] The process of a vehicle server creating a shared user key certificate includes: obtaining the vehicle owner's public key, sharing proof, and vehicle owner's private key; signing the vehicle owner's public key using the vehicle owner's private key to obtain the vehicle owner's public key signature; and creating the shared user key certificate by embedding the vehicle owner's public key signature, vehicle owner's public key, and sharing proof into the shared user key certificate. The vehicle owner's public key and vehicle owner's public key signature can be used as extensions in the shared user key certificate.

[0063] In step S230, the sharing user key certificate is sent to the target sharing device and the target vehicle based on the target sharing device information and the target vehicle information.

[0064] In this embodiment, the target sharing device account and IP address are obtained from the target sharing device information, and the sharing user key certificate is sent to the target sharing device. Within the target sharing device, the received sharing user key certificate is the sharing user key certificate to be verified.

[0065] Obtain the target vehicle's IP address from the target vehicle information and send the shared user key certificate to the target vehicle. Within the target vehicle, the user key certificate is used to verify the shared user key certificate to be verified.

[0066] In this embodiment, when a vehicle owner shares their car key with a sharing user, the vehicle owner's device sends a car key sharing request to the vehicle server. The vehicle server then generates and creates a sharing user key certificate based on the request. The sharing user key certificate is then distributed to the vehicle and the target sharing device. Because the vehicle owner's public key is embedded in the sharing user key certificate each time a key is shared, it is not necessary to store the vehicle owner's historical public key during key verification to verify the sharing proof in the sharing user key certificate. The vehicle owner's public key is signed using the vehicle owner's private key to obtain a vehicle owner key public key signature. The vehicle owner's private key is the unique credential held by the vehicle owner, ensuring the legitimacy of the vehicle owner's public key. This signature does not change with changes to the car key, thus enabling verification of the car key's legitimacy even when the vehicle owner's key changes. This decouples the verification of the sharing user key certificate from the reactivation of the vehicle owner's key, ensuring that changes to the vehicle owner's key do not affect the verification of the sharing user key certificate, thereby optimizing the verification and user experience of the sharing user key.

[0067] In this embodiment of the disclosure, the shared user key certificate also includes: the shared user key public key and / or the vehicle server CA signature.

[0068] In this embodiment, the public key of the shared user key in the shared user key certificate is used for authentication. Through digital signature technology, users can prove that they have the corresponding private key of the shared user key without having to expose it directly.

[0069] The vehicle server CA signature in the shared user key certificate provides a mechanism to verify that a public key indeed belongs to the claimed entity. By verifying the CA signature, the vehicle-to-everything (V2X) system can effectively defend against man-in-the-middle attacks.

[0070] In this embodiment of the disclosure, the method further includes: obtaining the vehicle owner's key public key and the vehicle owner's identity private key through a pre-stored vehicle owner's key certificate; and signing the vehicle owner's key public key with the vehicle owner's identity private key to obtain the vehicle owner's key public key signature.

[0071] In this embodiment, the vehicle server also pre-stores a vehicle owner's key certificate, which includes a vehicle owner's key public key and a vehicle owner's identity public key. The vehicle owner's identity public key is used to determine the vehicle owner's identity private key, and the vehicle owner's key public key is signed using the vehicle owner's identity private key to obtain a vehicle owner's key public key signature. Since the vehicle owner's identity private key is a unique credential held by a vehicle owner and does not change with changes to the vehicle key, the vehicle owner's key public key signature obtained by signing with the vehicle owner's identity private key can be verified using the vehicle owner's identity public key, thereby achieving the verification of the vehicle owner's identity legitimacy.

[0072] Figure 3 This is a flowchart illustrating a key verification method according to an exemplary embodiment of the present disclosure. Figure 3 The method of this embodiment can be applied to an electronic device, which may include a vehicle. The vehicle may be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicle.

[0073] In some implementations, the key verification method of this disclosure includes:

[0074] In step S310, a key verification request is received; the key verification request includes at least the shared user key certificate to be verified; the shared user key certificate to be verified includes at least: the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner's key public key;

[0075] When the target sharing device performs key verification, it sends a key verification request to the target vehicle.

[0076] The vehicle receives a key verification request; the key verification request includes the shared user key certificate to be verified; the shared user key certificate verification includes at least the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate.

[0077] The request message is transmitted via a secure channel (such as TLS encrypted communication) to ensure the confidentiality and integrity of the transmission process. The request must contain the complete data structure of the shared user key certificate. This prevents man-in-the-middle attacks and ensures that the request has not been tampered with or eavesdropped on.

[0078] In step S320, the signature of the vehicle owner's key public key is verified using the pre-stored vehicle owner's identity public key;

[0079] The vehicle pre-stores the owner's public key, which is sent to the vehicle by the vehicle server. Within the vehicle, the owner's public and private keys are unique public and private keys belonging to the owner and do not change with the vehicle key. The owner's public key can be used to verify the signature of the owner's key public key.

[0080] The vehicle owner's public key is an authoritative identifier of the vehicle owner's identity. It is usually issued by a trusted Certificate Authority (CA) and stored on the vehicle server, which then sends it to the target vehicle.

[0081] The vehicle uses the locally stored owner's identity public key to verify the signature of the owner's key public key in the certificate sent by the friend's device. If the verification is successful, it means that the owner's copper key public key is a legitimate public key certified by the car manufacturer's cloud, that is, the owner's identity private key has indeed signed the public key.

[0082] In step S330, in response to the verification of the vehicle owner's key public key signature, the sharing proof is verified using the vehicle owner's key public key;

[0083] When the verification of the signature using the vehicle owner's identity public key against the vehicle owner's key public key is successful, the sharing proof is further verified within the vehicle using the vehicle owner's key public key. This sharing proof may include: the identity identifier of the authorized object, the authorized time range, and the authorized permission type, etc.

[0084] The vehicle uses the verified owner's key public key to verify the sharing certificate within the same certificate. Essentially, the sharing certificate is a verification of the digital signature of the owner's key private key on the friend's device (such as device ID, permissions, validity period, etc.), confirming that the sharing certificate was indeed issued by the legitimate owner's key private key. The purpose of this step is to verify that the sharing certificate was indeed issued by the owner's key private key.

[0085] By decoupling the real-time status of the friend's key and the car owner's key, the vehicle does not need to store or rely on the historical master key public key. Each time a key is shared, the friend's key certificate dynamically embeds the car owner's key public key and its signature for that sharing session. The vehicle only needs to verify its validity; no pre-storage is required. If the vehicle relies on certificates stored on its own, when the car owner's key is updated (e.g., when the key is reactivated), the vehicle needs to synchronously update all relevant friend certificates. Our solution avoids this problem by dynamically carrying the public key.

[0086] In step S340, in response to the successful verification of the sharing proof, the sharing user key certificate to be verified is activated.

[0087] Once the sharing certificate is successfully verified using the vehicle owner's public key, the sharing user's key certificate can be activated. Based on the activated sharing user's key certificate, the target sharing device is authorized to access the vehicle and can then unlock and use it.

[0088] In this embodiment, when verifying a key verification request, the owner's key public key signature is first verified based on the owner's identity public key. Since the owner's identity public key and private key are unique to the same owner, the legitimacy of the owner's key public key is guaranteed and does not change with changes to the car key. If the owner's key public key signature verification is successful, the sharing certificate is verified using the owner's key public key. If the sharing certificate verification passes, the shared user key certificate to be verified is activated. The owner's key public key signature is obtained by signing the owner's key public key with the owner's identity private key. The owner's identity private key is the owner's unique credential and does not change with changes to the car key. This allows for the verification of the car key public key's legitimacy using the owner's key public key signature when the owner's key changes. This decouples the verification of the shared user key certificate from the reactivation of the owner's key, ensuring that changes to the owner's key do not affect the verification of the shared user key certificate, thus optimizing the verification and user experience of the shared user key.

[0089] In this embodiment of the disclosure, the method further includes: obtaining the vehicle owner's identity public key through a pre-stored vehicle owner key certificate.

[0090] The vehicle has a pre-stored owner's key certificate, which is sent to the vehicle from the vehicle server. The owner's key certificate includes the owner's public key, which can be extracted from the owner's key certificate.

[0091] In this embodiment of the disclosure, the vehicle owner key certificate further includes: a first vehicle owner key public key; the vehicle owner key public key is different from the first vehicle owner key public key.

[0092] In this embodiment, the vehicle owner's key certificate stores the vehicle owner's key public key and a first vehicle owner's key public key. When the vehicle owner's key public key changes, the vehicle server generates a corresponding first vehicle owner's key public key. For example, when the vehicle owner's device changes, the vehicle owner's device will request a new vehicle owner's key certificate from the vehicle server, and the new vehicle owner's key certificate will embed the first vehicle owner's key public key. The first vehicle owner's key public key is different from the original vehicle owner's key public key. Although the vehicle owner's key public key has changed, the target sharing device can still activate and verify based on the original vehicle owner's key public key, thus not affecting the target sharing device's use of the vehicle. The target sharing device can continue to use the vehicle until the vehicle owner changes or the vehicle owner cancels the key authorization for the target sharing device.

[0093] In this embodiment of the disclosure, activating the shared user key certificate to be verified includes: activating a pre-stored shared user key certificate corresponding to the shared user key certificate to be verified.

[0094] In this embodiment, the shared user key certificate generated by the vehicle server is sent to the target sharing device and the target vehicle respectively. The target vehicle has a pre-stored shared user key certificate, which corresponds to the shared user key certificate to be verified. By activating the shared user key certificate corresponding to the shared user key certificate to be verified, the vehicle can be unlocked when subsequent unlocking authentication is performed in the target vehicle by interacting with the activated shared user key certificate in the target sharing device.

[0095] Figure 4 This is a scenario diagram illustrating a key verification method according to an exemplary embodiment of this disclosure. For example... Figure 4 As shown, the vehicle server creates a user key certificate based on the car key sharing request. The specific process includes: obtaining the vehicle owner's key public key, sharing proof, and vehicle owner's identity private key; using the vehicle owner's identity private key to sign the vehicle owner's key public key to obtain the vehicle owner's key public key signature; creating a shared user key certificate, and embedding the vehicle owner's key public key signature, vehicle owner's key public key, and sharing proof into the shared user key certificate.

[0096] The vehicle server sends the sharing user key certificate to the target sharing device based on the target sharing device information; upon receiving the sharing user key certificate, the target sharing device identifies the corresponding sharing user key certificate to be verified.

[0097] The vehicle server sends the shared user key certificate to the target vehicle based on the target vehicle information; the vehicle server also sends the vehicle owner's public key to the target vehicle; upon receiving the shared user key certificate, the corresponding shared user key certificate to be verified is confirmed.

[0098] When the target sharing device performs key verification, it sends a key verification request to the target vehicle. The key verification request includes the key certificate of the sharing user to be verified.

[0099] The target vehicle receives a key verification request and verifies the owner's key public key signature using the pre-stored owner's identity public key. If the owner's key public key signature is verified, the sharing certificate is verified using the owner's key public key. If the sharing certificate is verified, the key certificate of the user to be verified is activated.

[0100] The activated, unverified shared user key certificate can be used for mutual authorization between the target vehicle and the target shared device. When the target shared device is used, the target vehicle can be unlocked and used.

[0101] Figure 5 This is an interactive key verification method illustrated according to an exemplary embodiment of the present disclosure. Figure 1 .like Figure 5 As shown, the key verification method provided in this embodiment involves a vehicle server, a target vehicle, a vehicle owner's device, and a target sharing device.

[0102] In this embodiment, the interaction process of the key verification method includes:

[0103] The vehicle owner's device sends a car key sharing request to the vehicle server;

[0104] The vehicle server receives a car key sharing request and creates a sharing user key certificate based on the request. The specific process includes: obtaining the vehicle owner's key public key, sharing proof, and vehicle owner's identity private key; using the vehicle owner's identity private key to sign the vehicle owner's key public key to obtain the vehicle owner's key public key signature; creating a sharing user key certificate and embedding the vehicle owner's key public key signature, vehicle owner's key public key, and sharing proof into the sharing user key certificate.

[0105] The vehicle server sends the sharing user key certificate to the target sharing device based on the target sharing device information;

[0106] The vehicle server sends the shared user key certificate to the target vehicle based on the target vehicle information;

[0107] The target sharing device sends a key verification request to the target vehicle; the key verification request includes at least the key certificate of the sharing user to be verified; the key certificate of the sharing user to be verified includes at least: the owner's key public key, the owner's key public key signature, and the sharing proof;

[0108] The target vehicle receives a key verification request; the owner's key public key signature is verified using the pre-stored owner identity public key; in response to the owner's key public key signature being verified, the sharing certificate is verified using the owner's key public key; in response to the sharing certificate being verified, the key certificate of the user to be verified is activated.

[0109] Upon successful verification of the key verification request, the key certificate of the user to be verified is activated.

[0110] The following are embodiments of the apparatus disclosed herein, which can be used to execute embodiments of the method disclosed herein. For details not disclosed in the apparatus embodiments of this disclosure, please refer to the embodiments of the method disclosed herein.

[0111] Figure 6 This is a first block diagram illustrating a key verification device according to an exemplary embodiment of the present disclosure. The device of this embodiment can be applied to electronic devices.

[0112] like Figure 6 As shown, the key verification device 600 may include: a key verification request sending module 610 and an activation module 620.

[0113] The key verification request sending module 610 is used to send a key verification request to the target vehicle; the key verification request includes at least the key certificate of the sharing user to be verified; the key certificate of the sharing user to be verified includes at least: the owner's key public key, the owner's key public key signature, and the sharing proof; the owner's key public key signature is a signature of the owner's key public key by the owner's identity private key;

[0114] The activation module 620 is used to activate the key certificate of the sharing user to be verified in response to the successful verification of the key verification request.

[0115] Figure 7 This is a second block diagram illustrating a key verification device according to an exemplary embodiment of the present disclosure. The device of this embodiment can be applied to electronic devices.

[0116] like Figure 7 As shown, the key verification device 700 may include: a car key sharing request receiving module 710, a sharing user key certificate creation module 720, and a sharing user key certificate sending module 730.

[0117] The car key sharing request receiving module 710 is used to receive car key sharing requests; the car key sharing request includes at least: target sharing device information and target vehicle information;

[0118] The shared user key certificate creation module 720 is used to create a shared user key certificate in response to the car key sharing request; the shared user key certificate includes at least: the car owner's key public key, the car owner's key public key signature, and a sharing certificate; the car owner's key public key signature is a signature of the car owner's identity private key on the car owner's key public key;

[0119] The shared user key certificate sending module 730 is used to send the shared user key certificate to the target shared device and the target vehicle based on the target shared device information and the target vehicle information.

[0120] Figure 8 This is a third block diagram illustrating a key verification device according to an exemplary embodiment of the present disclosure. The device of this embodiment can be applied to a vehicle.

[0121] like Figure 8 As shown, the key verification device 800 may include: a key verification request receiving module 810, a vehicle owner key public key signature verification module 820, a sharing proof verification module 830, and an activation module 840.

[0122] The key verification request receiving module 810 is used to receive a key verification request; the key verification request includes at least a shared user key certificate to be verified; the shared user key certificate to be verified includes at least: the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner's key public key;

[0123] The vehicle owner key public key signature verification module 820 is used to verify the vehicle owner key public key signature using the pre-stored vehicle owner identity public key;

[0124] The sharing proof verification module 830 is used to verify the sharing proof using the vehicle owner's key public key in response to the verification of the vehicle owner's key public key signature.

[0125] Activation module 840 is used to activate the sharing user key certificate to be verified in response to the successful verification of the sharing proof.

[0126] Figure 9 This is a functional block diagram of a vehicle according to an exemplary embodiment of the present disclosure. The vehicle 900 can be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicles. The vehicle 900 can be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.

[0127] Reference Figure 9 The vehicle 900 may include various subsystems, such as an infotainment system 910, a perception system 920, a decision control system 930, a drive system 940, and a computing platform 950. The vehicle 900 may also include more or fewer subsystems, and each subsystem may include multiple components. Furthermore, each subsystem and component of the vehicle 900 can be interconnected via wired or wireless means.

[0128] In some embodiments, the infotainment system 910 may include a communication system, an entertainment system, and a navigation system, etc.

[0129] The perception system 920 may include several sensors for sensing information about the environment surrounding the vehicle 900. For example, the perception system 920 may include a global positioning system (which may be GPS, BeiDou, or other positioning systems), an inertial measurement unit (IMU), lidar, millimeter-wave radar, ultrasonic radar, and a camera device.

[0130] The decision control system 930 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.

[0131] The drive system 940 may include components that provide powered motion to the vehicle 900. In one embodiment, the drive system 940 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of internal combustion engines, electric motors, and compressed air engines. The engine is capable of converting energy provided by the energy source into mechanical energy.

[0132] Some or all of the functions of the vehicle 900 are controlled by a computing platform 950. The computing platform 950 may include at least one processor 951 and a memory 952, the processor 951 being able to execute instructions 953 stored in the memory 952.

[0133] Processor 951 can be any conventional processor, such as a commercially available CPU. Processors may also include graphics processing units (GPUs), field-programmable gate arrays (FPGAs), systems-on-chips (SoCs), application-specific integrated circuits (ASICs), or combinations thereof.

[0134] The memory 952 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0135] In addition to instruction 953, memory 952 can also store data, such as road maps, route information, vehicle position, direction, speed, and other data. The data stored in memory 952 can be used by computing platform 950.

[0136] In this embodiment of the disclosure, the processor 951 may execute instruction 953 to complete all or part of the steps of the above-described data transmission method.

[0137] Figure 10 This is a block diagram illustrating an electronic device according to an exemplary embodiment of the present disclosure. For example, device 1100 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

[0138] Reference Figure 10The device 1100 may include one or more of the following components: a processing component 1002, a memory 1004, a power supply component 1006, a multimedia component 10010, an audio component 1010, an input / output (I / O) interface 1012, a sensor component 1014, and a communication component 1016.

[0139] Processing component 1002 typically controls the overall operation of device 1000, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1002 may include one or more processors 1020 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1002 may include one or more modules to facilitate interaction between processing component 1002 and other components. For example, processing component 1002 may include a multimedia module to facilitate interaction between multimedia component 10010 and processing component 1002.

[0140] Memory 1004 is configured to store various types of data to support the operation of device 1000. Examples of this data include instructions for any application or method operating on device 1000, contact data, phonebook data, messages, pictures, videos, etc. Memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0141] Power supply component 1006 provides power to various components of device 1000. Power supply component 1006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 1000.

[0142] Multimedia component 10010 includes a screen that provides an output interface between the device 1000 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 10010 includes a front-facing camera and / or a rear-facing camera. When the device 1000 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0143] Audio component 1010 is configured to output and / or input audio signals. For example, audio component 1010 includes a microphone (MIC) configured to receive external audio signals when device 1000 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1004 or transmitted via communication component 1016. In some embodiments, audio component 1010 also includes a speaker for outputting audio signals.

[0144] I / O interface 1012 provides an interface between processing component 1002 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0145] Sensor assembly 1014 includes one or more sensors for providing state assessments of various aspects of device 1000. For example, sensor assembly 1014 may detect the on / off state of device 1000, the relative positioning of components such as the display and keypad of device 1000, changes in the position of device 1000 or a component of device 1000, the presence or absence of user contact with device 1000, the orientation or acceleration / deceleration of device 1000, and temperature changes of device 1000. Sensor assembly 1014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1014 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1014 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0146] Communication component 1016 is configured to facilitate wired or wireless communication between device 1000 and other devices. Device 1000 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, other communication standards, or combinations thereof. In some embodiments of this disclosure, communication component 1016 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of this disclosure, communication component 1016 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0147] In some embodiments of this disclosure, the apparatus 1000 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0148] In some embodiments of this disclosure, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1004 including instructions, which can be executed by a processor 1020 of the device 1000 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0149] In some embodiments of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the key verification method described in any of the preceding claims.

[0150] In some embodiments of this disclosure, a computer program product includes a computer program that, when executed by a processor, implements any of the key verification methods described herein.

[0151] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0152] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A key verification method, characterized in that, include: Send a key verification request to the target vehicle; The key verification request includes at least the key certificate of the sharing user to be verified. The shared user key certificate to be verified includes at least: the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner's key public key; Upon successful verification of the key verification request, the key certificate of the sharing user to be verified is activated.

2. The method according to claim 1, characterized in that, The shared user key certificate to be verified also includes: the shared user key public key and / or the vehicle server CA signature.

3. A key verification method, characterized in that, include: Receive car key sharing request; The car key sharing request includes at least: target sharing device information and target vehicle information; In response to the car key sharing request, a sharing user key certificate is created; the sharing user key certificate includes at least: the car owner's key public key, the car owner's key public key signature, and a sharing certificate; the car owner's key public key signature is a signature of the car owner's identity private key on the car owner's key public key; Based on the target sharing device information and the target vehicle information, the sharing user key certificate is sent to the target sharing device and the target vehicle.

4. The method according to claim 3, characterized in that, The shared user key certificate also includes: the shared user key public key and / or the vehicle server CA signature.

5. The method according to claim 3, characterized in that, The method further includes: Obtain the vehicle owner's key public key and the vehicle owner's identity private key through the pre-stored vehicle owner key certificate; The vehicle owner's private key is used to sign the vehicle owner's public key to obtain the vehicle owner's public key signature.

6. A key verification method, characterized in that, include: Receive key verification request; The key verification request includes at least the key certificate of the sharing user to be verified. The shared user key certificate to be verified includes at least: the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner's key public key; The signature of the vehicle owner's key public key is verified by using the pre-stored vehicle owner's identity public key; In response to the verification of the vehicle owner's key public key signature, the sharing proof is verified using the vehicle owner's key public key; In response to the successful verification of the sharing proof, the key certificate of the sharing user to be verified is activated.

7. The method according to claim 6, characterized in that, The method further includes: The owner's identity public key is obtained by using the pre-stored owner key certificate.

8. The method according to claim 7, characterized in that, The vehicle owner key certificate also includes: a first vehicle owner key public key; the vehicle owner key public key is different from the first vehicle owner key public key.

9. The method according to claim 6, characterized in that, Activating the shared user key certificate to be verified includes: Activate the pre-stored shared user key certificate corresponding to the shared user key certificate to be verified.

10. A key verification device, characterized in that, include: The key verification request sending module is used to send a key verification request to the target vehicle; The key verification request includes at least the key certificate of the sharing user to be verified. The shared user key certificate to be verified includes at least: the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner's key public key; The activation module is used to activate the key certificate of the sharing user to be verified in response to the successful verification of the key verification request.

11. A key verification device, characterized in that, include: The car key sharing request receiving module is used to receive car key sharing requests; The car key sharing request includes at least: target sharing device information and target vehicle information; The shared user key certificate creation module is used to create a shared user key certificate in response to the car key sharing request; the shared user key certificate includes at least: the car owner's key public key, the car owner's key public key signature, and a sharing certificate; the car owner's key public key signature is a signature of the car owner's identity private key on the car owner's key public key; The shared user key certificate sending module is used to send the shared user key certificate to the target shared device and the target vehicle based on the target shared device information and the target vehicle information.

12. A key verification device, characterized in that, include: The key verification request receiving module is used to receive key verification requests; The key verification request includes at least the key certificate of the sharing user to be verified. The shared user key certificate to be verified includes at least: the vehicle owner's key public key, the vehicle owner's key public key signature, and a sharing certificate; the vehicle owner's key public key signature is a signature of the vehicle owner's identity private key on the vehicle owner's key public key; The vehicle owner key public key signature verification module is used to verify the signature of the vehicle owner key public key using the pre-stored vehicle owner identity public key; The sharing proof verification module is used to verify the sharing proof using the vehicle owner's key public key in response to the verification of the vehicle owner's key public key signature. The activation module is used to activate the key certificate of the sharing user to be verified in response to the successful verification of the sharing proof.

13. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the key verification method according to any one of claims 1-2 and 3-5 by executing the executable instructions.

14. A vehicle, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured as follows: The steps of implementing the key verification method according to any one of claims 6 to 9.

15. 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 key verification method according to any one of claims 1-2, 3-5, and 6-9.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the key verification method according to any one of claims 1-2, 3-5, and 6-9.

Images