Digital key activation method based on digital key cloud platform, and device and medium

Abstract

A digital key activation method based on a digital key cloud platform, and a device and a medium, which relate to the field of smart keys. The method comprises: in response to a request for a mobile terminal to pair with a vehicle, a vehicle OEM server requesting the acquisition of a pairing password from a digital key cloud platform (101); after acquiring the pairing password returned by the vehicle OEM server, the mobile terminal pairing with the vehicle, so as to generate a digital key of the vehicle (102); the mobile terminal sending the digital key to the digital key cloud platform for activation, and returning an activation result to the mobile terminal (103); and after the mobile terminal synchronizes the activation result with the vehicle, the activation of the digital key taking effect (104). Therefore, the problem of digital keys of different vehicle OEMs being unable to be uniformly managed due to the fact that the connection complexity between device OEM servers of different brands and different vehicle OEM servers is high can be solved.

Description

Digital key activation method, device and medium based on digital key cloud platform Cross-referencing

[0001] This application claims priority to Chinese Patent Application No. 2024115463029, filed on November 1, 2024, entitled "Digital Key Activation Method, Device and Medium Based on Digital Key Cloud Platform", which is incorporated herein by reference in its entirety. Technical Field

[0002] This application relates to the field of smart keys, and in particular to a digital key activation method, device and medium based on a digital key cloud platform. Background Technology

[0003] With the development of intelligent vehicle technology, more and more vehicles are equipped with digital key systems. Compared to traditional keys, digital keys are more convenient to carry. However, the generation and use of digital keys requires a connection between the device original equipment manufacturer (DOEM) server of the mobile terminal and the vehicle original equipment manufacturer (VOEM) server. However, the connection process between the device OEM servers of different brands of mobile terminals and the vehicle OEM servers of different brands is complex and cumbersome. For example, if there are 5 different brands of device OEMs and 5 different vehicle OEM servers, this would require 25 (5×5) point-to-point connection channels. Establishing these connection channels is cumbersome and costly, and the digital keys from different vehicle OEMs cannot be managed uniformly.

[0004] Therefore, how to reduce the connection complexity of OEM servers for different brands of equipment and different vehicle OEM servers, and improve the convenience and efficiency of digital key management, is an urgent problem to be solved. Summary of the Invention

[0005] The purpose of this application is to provide a digital key activation method, device, and medium based on a digital key cloud platform. This method utilizes the digital key cloud platform to connect with OEM servers of different brands of mobile terminals and different vehicle OEM servers. This allows the OEM servers of different brands of mobile terminals and different vehicle OEM servers to communicate and connect through the digital key cloud platform, reducing the connection complexity of different brand OEM servers and different vehicle OEM servers. Furthermore, the digital key cloud platform enables unified management of digital keys, achieving more convenient, secure, and efficient digital key activation and management.

[0006] To address the aforementioned technical problems, this application provides a digital key activation method based on a digital key cloud platform, comprising: in response to a request for pairing between a mobile terminal and a vehicle, a vehicle OEM server requests a pairing password from the digital key cloud platform; wherein the pairing password is used to pair the mobile terminal with the vehicle; after obtaining the pairing password returned by the vehicle OEM server, the mobile terminal pairs with the vehicle to generate a digital key for the vehicle; the mobile terminal sends the digital key to the digital key cloud platform for activation, and returns the activation result to the mobile terminal; after the mobile terminal synchronizes the activation result to the vehicle, the digital key activation takes effect.

[0007] Embodiments of this application also provide an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the digital key activation method based on a digital key cloud platform as described above.

[0008] Embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the digital key activation method based on a digital key cloud platform as described above.

[0009] This application introduces a digital key cloud platform for unified management of digital keys. In response to a pairing request between a mobile terminal and a vehicle, the vehicle OEM server requests a pairing password from the digital key cloud platform. This pairing password is used to pair the mobile terminal with the vehicle. After receiving the pairing password from the vehicle OEM server, the mobile terminal pairs with the vehicle, generating a digital key. The mobile terminal sends the digital key to the digital key cloud platform for activation, and the activation result is returned to the mobile terminal. After the mobile terminal synchronizes the activation result to the vehicle, the digital key activation takes effect. In other words, this solution utilizes a digital key cloud platform to connect the device OEM servers of different brands of mobile terminals and different vehicle OEM servers, reducing the connection complexity between these servers. By controlling the issuance of pairing passwords and the activation of digital keys between the mobile terminal and the vehicle through the digital key cloud platform, unified management of digital keys is achieved, resulting in more convenient, secure, and efficient digital key activation and management.

[0010] In addition, in response to the pairing request between the mobile terminal and the vehicle as described above, the vehicle OEM server requests a pairing password from the digital key cloud platform, including: the mobile terminal initiating a vehicle binding request to the vehicle OEM server through a pre-installed vehicle OEM application; wherein the vehicle binding request includes vehicle identification information and vehicle owner information; the vehicle OEM server binds the vehicle owner to the vehicle and requests a pairing password from the digital key cloud platform.

[0011] Additionally, after the vehicle OEM server requests a pairing password from the digital key cloud platform as described above, the process includes: the digital key cloud platform generating the pairing password, a salt value, and a verifier, and sending the verifier to the vehicle; wherein the verifier is used to verify the pairing password; the digital key cloud platform creating a URL link containing the pairing password, and returning the pairing password and the URL link to the vehicle OEM server; the vehicle OEM server sending a pairing message to the mobile terminal via SMS, the pairing message containing the URL link.

[0012] In addition, in response to the pairing request between the mobile terminal and the vehicle as described above, the vehicle OEM server requests a pairing password from the digital key cloud platform, including: initiating a pairing request to the vehicle OEM server through the vehicle OEM application pre-installed on the mobile terminal, requesting pairing with the vehicle; the pairing request includes vehicle owner information; the vehicle OEM server verifies whether the vehicle owner information matches the vehicle owner, and after verification, the vehicle OEM server requests a pairing password from the digital key cloud platform.

[0013] Additionally, after the vehicle OEM server requests a pairing password from the digital key cloud platform as described above, the process includes: the digital key cloud platform generating the pairing password, a salt value, and a verifier, and sending the verifier to the vehicle; wherein the verifier is used to verify the pairing password; the digital key cloud platform creating a URL link containing the pairing password, and returning the pairing password and the URL link to the vehicle OEM server; and the vehicle OEM server returning the pairing password to the mobile terminal via the API of the vehicle OEM application.

[0014] Additionally, as described above, after the mobile terminal obtains the pairing password returned by the vehicle OEM server, it pairs with the vehicle to generate a digital key for the vehicle. This includes: the mobile terminal initiating pairing with the vehicle based on the pairing password, obtaining the vehicle's identification information and digital certificate, and simultaneously sending the mobile terminal's identification information and digital certificate to the vehicle; the mobile terminal generating the digital key in the vehicle OEM application based on the vehicle's identification information and digital certificate, and the mobile terminal's own identification information and digital certificate; the digital key is used to control the vehicle.

[0015] In addition, as described above, the mobile terminal sends the digital key to the digital key cloud platform for activation, including: the mobile terminal sending the digital key to the digital key cloud platform through the device OEM server; the digital key cloud platform registering the digital key as activated, and returning the activation result to the mobile terminal after registration.

[0016] In addition, after the digital key is activated as described above, the process further includes: the digital key cloud platform sending a notification message to the vehicle OEM server indicating that the vehicle and the mobile terminal have been successfully paired; the vehicle OEM server requesting a new pairing password from the digital key cloud platform after receiving the notification message; the digital key cloud platform generating the new pairing password, creating a new URL link containing the pairing password, and returning the new pairing password and the new URL link to the vehicle OEM server; the vehicle OEM server sending a new pairing message to the mobile terminal via SMS, the new pairing message containing the new URL link; wherein, the new pairing password is used to enable the mobile terminal to pair with the vehicle again after the digital key expires or is lost, so as to regenerate the digital key. Attached Figure Description

[0017] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0018] Figure 1 is a detailed flowchart of a digital key activation method based on a digital key cloud platform according to an embodiment of this application;

[0019] Figure 2 is a detailed flowchart of another embodiment of the digital key activation method based on a digital key cloud platform of this application;

[0020] Figure 3 is a detailed flowchart of another embodiment of the digital key activation method based on a digital key cloud platform of this application.

[0021] Figure 4 is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details are presented in the various embodiments of this application to enable readers to better understand this application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in this application can be implemented. It should be noted that the directional terms such as "upper," "lower," "left," and "right" described in the embodiments of this application are used to describe the angles shown in the accompanying drawings and should not be construed as limiting the embodiments of this application. Furthermore, in the context, it should be understood that when it is mentioned that an element is connected "upper" or "lower" to another element, it can not only be directly connected to the other element "upper" or "lower," but also indirectly connected to the other element "upper" or "lower" through an intermediate element. The division of the following embodiments is for the convenience of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined and referenced with each other without contradiction.

[0023] Before detailing this solution, we will first explain its implementation background. This solution is based on the CCC (3C) Digital Key (DK) specification. The 3C (Car Connectivity Consortium) is a global cross-industry organization dedicated to developing standards for smartphone-to-vehicle connectivity solutions. In July 2021, the CCC defined UWB as the core technology of the third-generation digital key and released the CCC R3 (third-generation digital key) specification. CCC R3 uses NFC / BLE / UWB as its foundational radio technologies. This system employs asymmetric cryptography to mutually sign and authenticate vehicles and devices, revealing its identity only to known vehicles. Only by using the private key corresponding to the public key stored in the vehicle for signature calculation can the device unlock, lock, start the engine, and perform other functions. However, the mutual signing and authentication process between vehicles and devices requires connections between the corresponding device OEM server and the vehicle OEM server for data exchange. Furthermore, the digital key systems of different vehicle OEMs operate independently, and different vehicle OEMs need to manage connections to different brand device OEMs, making the connection process cumbersome and the use and management of digital keys complex.

[0024] To address the aforementioned issues, this application provides a digital key activation method based on a digital key cloud platform. This embodiment connects the digital key cloud platform with vehicle OEM servers and device OEM servers to form a cloud-based system, which, together with terminals (mobile terminals and vehicles), enables the relevant operations of the digital key. As shown in Figure 1, the method of this embodiment specifically includes the following steps.

[0025] Step 101: In response to the request for pairing between the mobile terminal and the vehicle, the vehicle OEM server requests the pairing password from the digital key cloud platform.

[0026] The pairing password is used to pair the mobile terminal with the vehicle.

[0027] Specifically, in this embodiment, the mobile terminal is an electronic device with wireless communication capabilities such as Bluetooth and the ability to install applications. It can be a smartphone, and this application does not impose any specific limitations on this. To enable the mobile terminal to obtain a digital key and control the vehicle via it, the mobile terminal first initiates a pairing request to the vehicle's OEM server. The vehicle OEM server then requests a pairing password from the digital key cloud platform. Only after obtaining the pairing password can the mobile terminal pair and connect with the vehicle and generate its digital key.

[0028] It should be noted that the vehicles covered by this solution must support digital key functionality, and the vehicle's OEM must have connected to the digital key cloud platform. Simultaneously, the OEM of the mobile terminal's device must also have connected to the digital key cloud platform. In this embodiment, the vehicle OEM actually includes a Vehicle OEM Server and Vehicle OEM Services. The Vehicle OEM Server includes a Digital Key Server (DK-Server) and a Vehicle OEM Server API, used to handle standard and extended business processes. The Vehicle OEM Services include a Manufacturing Execution System (MES), a Driver Monitoring System (DMS), a Telematics Service Provider (TSP), and an application server. In this embodiment, the Vehicle OEM Server and Vehicle OEM Services are not distinguished and are collectively referred to as the Vehicle OEM Server, which will not be elaborated further below.

[0029] Step 102: After obtaining the pairing password returned by the vehicle OEM server, the mobile terminal pairs with the vehicle to generate the vehicle's digital key.

[0030] Specifically, after the vehicle OEM server requests a pairing password from the digital key cloud platform, the digital key cloud platform responds by returning the pairing password to the vehicle OEM server. The mobile terminal, upon receiving the pairing password from the vehicle OEM server, pairs with the vehicle using this password. The pairing can be performed via Bluetooth or wireless connections such as Near Field Communication (NFC); ​​this application does not impose specific limitations on this method. It should be noted that during pairing, the distance between the mobile terminal used by the vehicle owner and the vehicle must be within a preset distance. The value of the preset distance can be determined based on actual needs; this application does not impose specific limitations on this method. After obtaining the pairing password, the mobile terminal pairs with the vehicle using the pairing password. During the pairing process, the two interact to generate the relevant data required for the digital key, including but not limited to their respective identification information and digital certificates. After obtaining the relevant data required to generate the digital key, the mobile terminal generates the digital key.

[0031] Step 103: The mobile terminal sends the digital key to the digital key cloud platform for activation and returns the activation result to the mobile terminal.

[0032] Specifically, after a digital key is generated on a mobile terminal, it only exists on the mobile terminal and is not immediately effective. Because the digital key cloud platform includes CCC-compliant services such as Track Key, Manage Key, and Health Check, it provides unified management of the digital key. Therefore, the digital key needs to be sent to the digital key cloud platform for activation, and the activation result should be returned to the mobile terminal to inform it that the digital key cloud platform has initiated the activation process.

[0033] Step 104: After the mobile terminal synchronizes the activation result to the vehicle, the digital key activation takes effect.

[0034] Specifically, after the mobile terminal obtains the activation result, it will interact with the vehicle again to synchronize the activation result to the vehicle and inform the vehicle that "the digital key has been activated". This allows the vehicle to recognize the digital key and respond to its control, and the digital key activation officially takes effect.

[0035] Compared to related technologies, this application introduces a digital key cloud platform for unified management of digital keys. In response to a pairing request between a mobile terminal and a vehicle, the vehicle OEM server requests a pairing password from the digital key cloud platform. This pairing password is used to pair the mobile terminal with the vehicle. After receiving the pairing password from the vehicle OEM server, the mobile terminal pairs with the vehicle, generating a digital key. The mobile terminal sends the digital key to the digital key cloud platform for activation, and the activation result is returned to the mobile terminal. After the mobile terminal synchronizes the activation result to the vehicle, the digital key is activated. In other words, this solution utilizes a digital key cloud platform to connect the device OEM servers of different brands of mobile terminals and different vehicle OEM servers, reducing the connection complexity between these servers. By controlling the issuance of pairing passwords and the activation of digital keys between the mobile terminal and the vehicle through the digital key cloud platform, unified management of digital keys is achieved, resulting in more convenient, secure, and efficient digital key activation and management.

[0036] Another embodiment of this application relates to a digital key activation method based on a digital key cloud platform. This embodiment is a supplement to the foregoing embodiment and specifically includes the following:

[0037] In one example, step 101 may specifically include the following steps:

[0038] The mobile terminal initiates a vehicle binding request to the vehicle OEM server through a pre-installed vehicle OEM application; the vehicle binding request includes vehicle identification information and vehicle owner information; the vehicle OEM server binds the vehicle owner and the vehicle and requests a pairing password from the digital key cloud platform.

[0039] Specifically, when a user (vehicle owner) has purchased a vehicle and is about to use it for the first time, a vehicle OEM application needs to be pre-installed. This application then sends a binding request to the vehicle OEM server. The vehicle OEM application is typically developed and integrated by the vehicle's main unit or the vehicle manufacturer, and its basic functions are vehicle-related, such as user manuals, power management, and vehicle settings. The vehicle OEM application connects to the vehicle OEM server via a public network. The vehicle OEM server handles vehicle data, user (owner) authentication, and provides corresponding computing services and data management for the application. After purchasing the vehicle, the user needs to authenticate their ownership to control it. The user (owner) uses their mobile terminal to initiate a vehicle binding request to the vehicle OEM server through the pre-installed vehicle OEM application. This request includes vehicle identification information and owner information. Upon receiving the binding request, the vehicle OEM server parses it, obtains the vehicle identification information and owner information, and uses the vehicle identification information to uniquely identify the vehicle and bind it to the user's mobile terminal. This allows the user to subsequently obtain a digital key through the mobile terminal to control the vehicle. Since this is the first time the vehicle is bound to the user's mobile terminal, it means that the mobile terminal has not yet obtained a digital key. After the vehicle OEM server completes the binding process, it returns a vehicle binding response to the vehicle OEM application on the mobile terminal and automatically requests a pairing password from the digital key cloud platform so that the mobile terminal can subsequently obtain the digital key.

[0040] Accordingly, in one example, as shown in Figure 2, after the vehicle OEM server requests the pairing password from the digital key cloud platform, the following steps are included:

[0041] Step 201: The digital key cloud platform generates a pairing password, a salt value, and a verifier, and sends the verifier to the vehicle; the verifier is used to verify the pairing password.

[0042] Specifically, after receiving a request from the vehicle OEM server to obtain a pairing password, the digital key cloud platform generates a corresponding pairing password. This request can carry information about the mobile terminal and the vehicle. The pairing password generated by the digital key cloud platform enables the mobile terminal corresponding to the information carried in the request from the vehicle OEM server to pair with the vehicle. Furthermore, the pairing password generated by the digital key cloud platform can simultaneously generate a salt and a verifier. The salt is used to encrypt the pairing password to improve security, and the verifier is used to verify the pairing password. The digital key cloud platform sends the verifier to the vehicle via telematics, forwarded by the vehicle OEM server, for the vehicle to verify the pairing password. It should be noted that in this embodiment, all data transmission between the digital key cloud platform and the vehicle is achieved through forwarding by the vehicle OEM server, which will not be elaborated further hereafter.

[0043] Step 202: The digital key cloud platform creates a URL (Uniform Resource Locator) link containing the pairing password and returns the pairing password and URL link to the vehicle OEM server.

[0044] Specifically, after the digital key cloud platform successfully sends the authenticator to the vehicle via telematics and receives the vehicle's response, the digital key cloud platform creates a URL link containing the pairing password and returns the pairing password and URL link to the vehicle's OEM server. This pairing password and URL link is the digital key cloud platform's response to the vehicle's OEM server's request to obtain the pairing password.

[0045] Step 203: The vehicle OEM server sends a pairing message to the mobile terminal via SMS, and the pairing message contains a URL link.

[0046] Specifically, after obtaining the pairing password and URL link from the digital key cloud platform, the vehicle OEM server sends a pairing message to the mobile terminal via SMS, which includes the URL link. It should be noted that users need to log in to the vehicle OEM application using a phone number; therefore, the vehicle OEM server can obtain the phone number corresponding to the mobile terminal and send an SMS.

[0047] In one example, step 102 may include the following steps:

[0048] The mobile terminal begins pairing with the vehicle based on the pairing password, obtains the vehicle's identification information and digital certificate, and simultaneously sends the mobile terminal's identification information and digital certificate to the vehicle; the mobile terminal generates a digital key in the vehicle's OEM application based on the vehicle's identification information and digital certificate, as well as the mobile terminal's own identification information and digital certificate; the digital key is used to control the vehicle.

[0049] Specifically, after the vehicle OEM server sends a pairing message containing a URL link to the mobile terminal via SMS, the mobile terminal receives the pairing password returned by the vehicle OEM server. The user can click the URL link in the SMS, which triggers the mobile terminal to open a "wallet" application (APP) to initiate pairing with the vehicle. In this embodiment, "wallet" refers to the "wallet" APP that comes pre-installed on different mobile terminals, such as Apple Wallet, Huawei Wallet, Samsung Wallet, etc., which support storing digital keys. After receiving the pairing password transmitted by the mobile terminal via NFC or other wireless communication methods, the vehicle calls the authenticator transmitted by the digital key cloud platform to verify the pairing password sent by the mobile terminal. After successful verification, the vehicle and the mobile terminal begin data interaction. The mobile terminal obtains information needed to generate a digital key, including the vehicle's identification information and digital certificate, and simultaneously sends its own identification information and digital certificate to the vehicle. The mobile terminal generates a digital key in the vehicle OEM application based on the obtained vehicle identification information and digital certificate, as well as its own identification information and digital certificate. It should be noted that the vehicle OEM application includes a Digital Key Software Development Kit (DK SDK) for generating and managing digital keys.

[0050] In another example, step 103 includes the following steps: the mobile terminal sends the digital key to the digital key cloud platform through the device OEM server; the digital key cloud platform registers the digital key as activated and returns the activation result to the mobile terminal after registration is completed.

[0051] Specifically, in this embodiment, all data interaction between the mobile terminal and the digital key cloud platform is conducted through the device OEM server. The device OEM server provides services and manages data for the mobile terminal's "wallet" application. The mobile terminal sends the digital key to the digital key cloud platform, which registers the digital key as activated and returns an activation result. The activation result informs the mobile terminal that the digital key has been activated. The activation result may include the graphic of the digital key displayed on the mobile terminal in "card" form, the vehicle model, the vehicle name, and relevant custom data from the vehicle's factory settings; this application does not impose specific limitations on this. After returning the activation result to the mobile terminal, the mobile terminal then interacts with the vehicle to inform the vehicle of the digital key's activation status, and the digital key officially becomes effective.

[0052] Compared to related technologies, this embodiment generates a pairing password and a URL link containing the pairing password through a digital key cloud platform. The vehicle OEM server then sends this link to the mobile terminal via SMS, enabling the mobile terminal to obtain the pairing password and pair with the vehicle to generate a digital key for vehicle control. In other words, this solution, by distributing the pairing password through the digital key cloud platform, enables the control of digital key generation and activation via the platform, achieving unified management of digital keys that is more convenient, secure, and efficient.

[0053] Another embodiment of this application relates to a digital key activation method based on a digital key cloud platform. This embodiment is an alternative to the foregoing embodiment. This embodiment provides another implementation process for step 101, which specifically includes the following contents.

[0054] The vehicle OEM application pre-installed on the mobile terminal initiates a pairing request to the vehicle OEM server to pair with the vehicle; the pairing request contains the vehicle owner information; the vehicle OEM server verifies whether the vehicle owner information matches the vehicle owner, and after verification, the vehicle OEM server requests the pairing password from the digital key cloud platform.

[0055] Specifically, this embodiment addresses a scenario where the user's (vehicle owner's) mobile terminal has already been bound to the vehicle and does not currently have a digital key. A "Start Pairing" button can be set in the vehicle OEM application. By clicking this button, the vehicle OEM application initiates a pairing request to the vehicle OEM server, requesting pairing with the vehicle. The pairing request includes the vehicle owner's information. Since the mobile terminal has already been bound to the vehicle, the vehicle OEM server verifies whether the vehicle owner information stored for that terminal matches the owner information included in the pairing request; that is, it performs a vehicle ownership verification to determine if the current mobile terminal is authorized to pair with the vehicle. After verification, the vehicle OEM server requests a pairing password from the digital key cloud platform. Correspondingly, in another example, after the vehicle OEM server requests the pairing password from the digital key cloud platform, the following steps are included: the digital key cloud platform generates a pairing password, a salt value, and a validator, and sends the validator to the vehicle; wherein, the validator is used to verify the pairing password; the digital key cloud platform creates a URL link containing the pairing password and returns the pairing password and the URL link to the vehicle OEM server; the vehicle OEM server returns the pairing password to the mobile terminal through the vehicle OEM application's API.

[0056] Specifically, after receiving a request from the vehicle OEM server to obtain a pairing password, the digital key cloud platform generates a corresponding pairing password. This request can carry information about the mobile terminal and the vehicle. The pairing password generated by the digital key cloud platform enables the mobile terminal corresponding to the information in the request from the vehicle OEM server to pair with the vehicle. Furthermore, the pairing password generated by the digital key cloud platform can simultaneously generate a salt and a verifier. The salt is used to encrypt the pairing password to improve security, and the verifier is used to verify the pairing password. The digital key cloud platform sends the verifier to the vehicle via telematics, forwarded by the vehicle OEM server, for the vehicle to verify the pairing password. After successfully sending the verifier to the vehicle via telematics and receiving a response from the vehicle, the digital key cloud platform creates a URL link containing the pairing password and returns the pairing password and URL link to the vehicle OEM server. This pairing password and URL link constitute the digital key cloud platform's response to the vehicle OEM server's request to obtain the pairing password. Since the user initiated a request to obtain the pairing password by clicking the "Start Pairing" button in the vehicle OEM application, the vehicle OEM server can return the pairing password to the mobile terminal as a response via the vehicle OEM application's API.

[0057] After the mobile terminal obtains the pairing password returned by the vehicle OEM server, the URL link triggers the mobile terminal to open its wallet and initiate pairing with the vehicle. Accordingly, the mobile terminal then uses the pairing password to pair with the vehicle through its wallet, obtains the vehicle's identification information and digital certificate, and simultaneously sends its own identification information and digital certificate to the vehicle. The steps of the mobile terminal generating a digital key in the vehicle OEM application based on the vehicle's identification information and digital certificate, and the mobile terminal sending the digital key to the digital key cloud platform through the device OEM server, and the digital key cloud platform registering the digital key as activated and returning the activation result to the mobile terminal after registration, are all the same as in the aforementioned embodiments. The implementation details of each step in the above embodiments remain valid in this embodiment and will not be repeated here.

[0058] Compared to related technologies, this embodiment generates a pairing password and a URL link containing the pairing password through a digital key cloud platform. The vehicle OEM server then sends this link via API to the vehicle OEM application pre-installed on the mobile terminal. This allows the mobile terminal to obtain the pairing password, pair with the vehicle, and generate a digital key to control the vehicle. In other words, this solution, by issuing the pairing password through the digital key cloud platform, enables the control of digital key generation and activation via the platform, achieving unified management of digital keys that is more convenient, secure, and efficient.

[0059] Another embodiment of this application relates to a digital key activation method based on a digital key cloud platform. This embodiment is a supplementary embodiment to the foregoing embodiments. As shown in FIG3, this embodiment specifically includes the following steps.

[0060] Step 301: The digital key cloud platform sends a notification message to the vehicle OEM server indicating that the vehicle and the mobile terminal have been successfully paired.

[0061] Step 302: After receiving the notification information, the vehicle OEM server requests a new pairing password from the digital key cloud platform.

[0062] Step 303: The digital key cloud platform generates a new pairing password, creates a new URL link containing the pairing password, and returns the new pairing password and the new URL link to the vehicle OEM server.

[0063] Step 304: The vehicle OEM server sends a new pairing message to the mobile terminal via SMS. The new pairing message contains a new URL link. The new pairing password is used to enable the mobile terminal to pair with the vehicle again after the digital key expires or is deleted, so as to generate a new digital key.

[0064] Specifically, this embodiment addresses a scenario where a mobile terminal obtains a valid digital key and stores it in a wallet in the form of a "card," but the digital key becomes invalid or is deleted from the wallet and can no longer be used.

[0065] To prevent the digital key from being accidentally deleted or invalidated and thus unusable again, after steps 101-104 are completed, the digital key cloud platform sends a notification message to the vehicle OEM server indicating successful pairing between the vehicle and the mobile terminal. Upon receiving the notification message, the vehicle OEM server requests a new pairing password, salt value, and new verifier from the digital key cloud platform; the new verifier is sent to the vehicle by the digital key cloud platform. The digital key cloud platform generates a new pairing password, creates a new URL link containing the pairing password, and returns the new pairing password and new URL link to the vehicle OEM server; the vehicle OEM server sends a new pairing message to the mobile terminal via SMS, which includes the new URL link. At this point, if the previous digital key becomes invalid or is deleted from the wallet, the user can click the new URL link to initiate the same pairing process between the mobile terminal and the vehicle as in the previous embodiment, activating and generating the digital key again. It is easy to see that this embodiment is a repetition of the steps in the previous embodiments, and the implementation details of the relevant steps remain valid in this embodiment, so they will not be repeated here.

[0066] Compared with related technologies, this embodiment, after the current digital key is activated and takes effect, requests a new pairing password from the digital key cloud platform again through the vehicle OEM server. A new URL link containing the new pairing password is then sent to the mobile terminal via SMS, allowing the mobile terminal to reactivate a digital key after the current digital key expires. This makes obtaining the digital key more convenient. Another embodiment of this application relates to an electronic device, as shown in FIG4, including at least one processor 402; and a memory 401 communicatively connected to the at least one processor 402. The memory 401 stores instructions executable by the at least one processor 402, which, when executed, enable the at least one processor 402 to perform any of the above-described embodiments of the digital key activation method based on the digital key cloud platform.

[0067] The memory 401 and processor 402 are connected via a bus, which can include any number of interconnecting buses and bridges. The bus connects various circuits of one or more processors 402 and memory 401 together. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 402 is transmitted over a wireless medium via an antenna, which further receives data and transmits it to processor 402.

[0068] The processor 402 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 401 can be used to store data used by the processor 402 during operation. The electronic device in this embodiment can be a physical key, a mobile terminal, etc., and this application does not specifically limit it.

[0069] Another embodiment of this application relates to a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements any of the above-described embodiments of the digital key activation method based on a digital key cloud platform.

[0070] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0071] Those skilled in the art will understand that the above embodiments are specific implementations of this application, and in practical applications, various changes can be made in form and detail without departing from the spirit and scope of this application.

Claims

1. A method for activating a digital key based on a digital key cloud platform, comprising: In response to a request to pair a mobile terminal with a vehicle, the vehicle OEM server requests a pairing password from the digital key cloud platform; wherein, the pairing password is used to pair the mobile terminal with the vehicle. After obtaining the pairing password returned by the vehicle OEM server, the mobile terminal pairs with the vehicle and generates a digital key for the vehicle. The mobile terminal sends the digital key to the digital key cloud platform for activation and returns the activation result to the mobile terminal. After the mobile terminal synchronizes the activation result to the vehicle, the digital key becomes activated.

2. The method according to claim 1, wherein, In response to the request for pairing between the mobile terminal and the vehicle, the vehicle OEM server requests a pairing password from the digital key cloud platform, including: The mobile terminal initiates a vehicle binding request to the vehicle OEM server through a pre-installed vehicle OEM application; wherein the vehicle binding request includes vehicle identification information and vehicle owner information; The vehicle OEM server binds the vehicle owner to the vehicle and requests a pairing password from the digital key cloud platform.

3. The method according to claim 2, wherein, After the vehicle OEM server requests the pairing password from the digital key cloud platform, it includes: The digital key cloud platform generates the pairing password, salt value, and verifier, and sends the verifier to the vehicle; wherein, the verifier is used to verify the pairing password; The digital key cloud platform creates a URL link containing the pairing password and returns the pairing password and the URL link to the vehicle OEM server; The vehicle OEM server sends a pairing message to the mobile terminal via SMS, and the pairing message contains the URL link.

4. The method according to claim 1, wherein, In response to a request from the mobile terminal to pair with the vehicle, the vehicle OEM server requests a pairing password from the digital key cloud platform, including: The mobile terminal initiates a pairing request to the vehicle OEM server via a vehicle OEM application pre-installed on it, requesting pairing with the vehicle; the pairing request includes vehicle owner information. The vehicle OEM server verifies whether the vehicle owner information matches the vehicle owner. After verification, the vehicle OEM server requests a pairing password from the digital key cloud platform.

5. The method according to claim 4, wherein, After the vehicle OEM server requests the pairing password from the digital key cloud platform, it includes: The digital key cloud platform generates the pairing password, salt value, and verifier, and sends the verifier to the vehicle; wherein, the verifier is used to verify the pairing password; The digital key cloud platform creates a URL link containing the pairing password and returns the pairing password and the URL link to the vehicle OEM server; The vehicle OEM server returns the pairing password to the mobile terminal through the interface of the vehicle OEM application.

6. The method according to claim 3 or 5, wherein, After obtaining the pairing password returned by the vehicle OEM server, the mobile terminal pairs with the vehicle and generates a digital key for the vehicle, including: The mobile terminal begins pairing with the vehicle based on the pairing password, obtains the vehicle's identification information and digital certificate, and simultaneously sends the mobile terminal's identification information and digital certificate to the vehicle. The mobile terminal generates the digital key in the vehicle OEM application based on the vehicle's identification information and digital certificate, as well as the mobile terminal's identification information and digital certificate; the digital key is used to control the vehicle.

7. The method according to claim 6, wherein, The mobile terminal sends the digital key to the digital key cloud platform for activation, including: The mobile terminal sends the digital key to the digital key cloud platform through the device OEM server; The digital key cloud platform registers the digital key as activated, and returns the activation result to the mobile terminal after registration is complete.

8. The method according to claim 1, wherein, After the digital key is activated, it also includes: The digital key cloud platform sends a notification message to the vehicle OEM server indicating that the vehicle and the mobile terminal have been successfully paired. After receiving the notification information, the vehicle OEM server requests a new pairing password from the digital key cloud platform. The digital key cloud platform generates the new pairing password, creates a new URL link containing the pairing password, and returns the new pairing password and the new URL link to the vehicle OEM server. The vehicle OEM server sends a new pairing message to the mobile terminal via SMS, and the new pairing message contains the new URL link. The new pairing password is used to enable the mobile terminal to pair with the vehicle again after the digital key becomes invalid or lost, so as to generate the digital key again.

9. An electronic device, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the digital key activation method based on the digital key cloud platform as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, which, when executed by a processor, implements the digital key activation method based on a digital key cloud platform as described in any one of claims 1 to 8.

Images