NFC Vehicle Key Registration Method, System, Terminal Device, and Storage Medium

Abstract

The present application discloses an NFC vehicle key registration method and system. The method is applied to a terminal device and includes: when receiving an NFC vehicle key registration request, requesting the software development kit (SDK) on the terminal device to add a data packet for the NFC vehicle key; wherein, when receiving the request, the SDK creates a security domain on the security module in the terminal device to download and install an Applet applet for the NFC vehicle key through the storage space of the security domain to complete the creation of a blank NFC vehicle key card; requesting personalization data from a card issuing system through a cloud server to complete the card writing operation for the blank NFC vehicle key card; obtaining the registration information of the NFC vehicle key, and determining a target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle; and sending the registration information to the vehicle based on the target communication channel so that the vehicle stores the registration information in a key controller.

Description

Technical Field

[0001] The present application relates to the field of vehicles, and particularly to an NFC (Near Field Communication) vehicle key registration method, system, terminal device, and storage medium. Background Art

[0002] In traditional automotive door lock systems, a mechanical lock or a welcome switch is generally installed on the vehicle door, and an antenna module and a lock control structure are installed at the vehicle handle. At the same time, users also need to use an additional key to enter the vehicle body, which is very inconvenient; in addition, it is rather troublesome to handle the situation when the key is lost. With the continuous progress of electronic technology, the integration between automobiles and electronics has become more and more common. In addition, the popularity of mobile phones is getting higher and higher. Replacing the vehicle key with a mobile phone and enabling the mobile phone to perform the functions of the vehicle key is a highlight of the future integration of automobiles and electronics. Summary of the Invention

[0003] The purpose of the present application is to solve at least one of the above technical problems to some extent.

[0004] To this end, the first object of the present application is to propose an NFC vehicle key registration method. This method realizes the registration scenario of the NFC vehicle key of the vehicle, so that the vehicle door can be opened only by using the user's terminal device, replacing the vehicle key to achieve the unlocking function.

[0005] The second object of the present application is to propose an NFC vehicle key registration system.

[0006] The third object of the present application is to propose a terminal device.

[0007] The fourth object of the present application is to propose a computer-readable storage medium.

[0008] To achieve the above object, the NFC vehicle key registration method according to the first aspect embodiment of the present application is applied to a terminal device, and the method includes:

[0009] When receiving an NFC vehicle key registration request input by a user, request the software development kit SDK on the terminal device to add a data packet for the NFC vehicle key; wherein, when receiving the request, the software development kit SDK creates a security domain on the security module in the terminal device to download and install the Applet applet of the NFC vehicle key through the storage space of the security domain to complete the creation of the NFC vehicle key blank card;

[0010] Receive the creation completion result of the NFC vehicle key blank card returned by the software development kit SDK, and request personalization data from the card issuing system through the cloud server to complete the card writing operation of the NFC vehicle key blank card;

[0011] Obtain the registration information of the NFC vehicle key, and determine a target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle.

[0012] Send the registration information to the vehicle based on the target communication channel, so that the vehicle stores the registration information in the key controller.

[0013] The NFC vehicle key registration system according to the second aspect embodiment of the present application includes: a terminal device, a cloud server, a card issuing system, and a vehicle, where

[0014] The terminal device includes a remote vehicle control client, a software development kit (SDK), and a security module. The remote vehicle control client is used to request the SDK to add a data packet for the NFC vehicle key when receiving a user input NFC vehicle key registration request.

[0015] The SDK is used to create a security domain on the security module when receiving the request, and download and install an Applet applet of the NFC vehicle key through the storage space of the security domain to complete the creation of the NFC vehicle key blank card.

[0016] The remote vehicle control client is further used to receive the creation completion result of the NFC vehicle key blank card returned by the SDK, and request personalization data from the card issuing system through the cloud server to complete the card writing operation of the NFC vehicle key blank card.

[0017] The remote vehicle control client is further used to obtain the registration information of the NFC vehicle key, determine a target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle, and send the registration information to the vehicle based on the target communication channel.

[0018] The vehicle is used to store the registration information in the key controller on the vehicle.

[0019] The terminal device according to the third aspect embodiment of the present application includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the NFC vehicle key registration method according to the first aspect embodiment of the present application.

[0020] The computer-readable storage medium according to the fourth aspect embodiment of the present application stores a computer program, and when the computer program is executed by a processor, it implements the NFC vehicle key registration method according to the first aspect embodiment of the present application.

[0021] According to the technical solution of the embodiment of the present application, through the remote vehicle control client and software development kit (SDK) on the terminal device, and the card issuing system, the registration of the NFC vehicle key is realized, and the target communication channel for transmitting the registration information is determined from the connections among the terminal device, the cloud server, and the vehicle. Then, based on the target communication channel, the registration information of the NFC vehicle key is sent to the vehicle, so that the vehicle stores the registration information in the key controller. Without affecting the user experience, the registration scenario of the NFC vehicle key of the vehicle is realized. In this way, the user can control the unlocking and locking of the vehicle by using the NFC vehicle key that has been registered with the vehicle key controller, and only needs to use the user's terminal device to open the vehicle door, replacing the vehicle key to realize the unlocking function. In addition, by determining the target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle, even in the case of no network condition of the vehicle, it can ensure that the registration information is sent to the vehicle, greatly improving the registration success rate of the NFC vehicle key.

[0022] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:

[0024] Figure 1 is a flowchart of a method for registering an NFC vehicle key according to an embodiment of the present application.

[0025] Figure 2 is a structural block diagram of an NFC vehicle key registration system according to an embodiment of the present application.

[0026] Figure 3 is an interaction schematic diagram of an NFC vehicle key registration system according to an embodiment of the present application.

[0027] Figure 4 is a flowchart of activating an NFC vehicle key service through a Bluetooth channel according to an embodiment of the present application.

[0028] Figure 5 is a structural schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0029] Embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application and should not be construed as limiting the present application.

[0030] The NFC vehicle key registration method, system, terminal device, and storage medium according to an embodiment of the present application will be described below with reference to the accompanying drawings.

[0031] Figure 1 It is a flowchart of an NFC vehicle key registration method according to an embodiment of the present application. It should be noted that the NFC vehicle key registration method of the embodiment of the present application can be applied to a terminal device. Among them, the terminal device may include a remote vehicle control client, a software development kit SDK, and a security module SE. The terminal device may be a hardware device such as a mobile phone, a tablet computer, a wearable device, etc. with various operating systems. Optionally, the NFC vehicle key registration method of the embodiment of the present application is described from the perspective of the remote vehicle control client.

[0032] As Figure 1 shown, the NFC vehicle key registration method may include:

[0033] Step 101, when receiving a user input NFC vehicle key registration request, request the software development kit SDK to add a data packet for the NFC vehicle key; wherein, when the software development kit SDK receives the request, it creates a security domain on the security module to download and install an Applet applet of the NFC vehicle key through the storage space of the security domain to complete the creation of a blank NFC vehicle key card.

[0034] For example, a remote vehicle control client APP for remotely controlling a vehicle is installed on the terminal device. The user can register, delete, and manage NFC vehicle keys through the remote vehicle control client APP. After the user opens the remote vehicle control client APP and successfully logs in with a cloud service account and password, the user can click "Add Mobile NFC Key" in the key management interface of the remote vehicle control client APP to request the registration of the NFC vehicle key. When the remote vehicle control client receives the user input NFC vehicle key registration request, it can request the software development kit SDK on the terminal device to add a data packet for the NFC vehicle key. When the software development kit SDK receives the request, it creates a security domain on the security module to download and install an Applet applet of the NFC vehicle key through the storage space of the security domain to complete the creation of a blank NFC vehicle key card.

[0035] Among them, in the embodiments of the present application, the Applet applet can be understood as a small application program written in the Java programming language, and this program can be included in an HTML (an application of the Standard Generalized Markup Language) page. The HTML file code of the web page containing the Applet has <applet>and< / applet> such a pair of tags in the middle. When a Java-supported web browser encounters this pair of tags, it will download the corresponding small application program code and execute the Applet on the local terminal device.

[0036] Step 102, receive the creation completion result of the NFC vehicle key blank card returned by the software development kit (SDK), and request personalization data from the card-issuing system through the cloud server to complete the card writing operation of the NFC vehicle key blank card.

[0037] Optionally, after the software development kit (SDK) completes the creation of the NFC vehicle key blank card, it will return the creation completion result of the NFC vehicle key blank card to the remote vehicle control client. After receiving the creation completion result of the NFC vehicle key blank card, the remote vehicle control client can request personalization data from the cloud server. When receiving this request, the cloud server can request personalization data from the card-issuing system. Among them, the cloud server can be understood as the server corresponding to the remote vehicle control client.

[0038] In the embodiments of the present application, when receiving the personalization data sent by the card-issuing system forwarded by the cloud server, a card writing instruction can be sent to the software development kit (SDK); among them, the card writing instruction is used to instruct the software development kit (SDK) to write the personalization data into the NFC vehicle key blank card.

[0039] That is to say, when the card-issuing system receives a request for personalization data, it can send the personalization data to the cloud server, and the cloud server forwards the personalization data to the remote vehicle control client. When receiving the personalization data, the remote vehicle control client can send the card writing instruction to the software development kit (SDK), and the card writing instruction carries the personalization data. When receiving the card writing instruction, the software development kit (SDK) can write the personalization data into the NFC vehicle key blank card and synchronize the personalization data to the security module (SE) of the terminal device and the SEI-TSM (a system for managing the mobile security module SE) system to complete the writing operation of the NFC vehicle key blank card.

[0040] To ensure the communication security of personalized data, optionally, in an embodiment of the present application, before requesting personalized data from the card issuing system through the cloud server, the remote vehicle control client may apply to the software development kit (SDK) for a communication temporary public-private key pair, and the software development kit (SDK) applies to the security module (SE) for a temporary public-private key pair. After generating the temporary public-private key pair, the security module (SE) may send the public key in the public-private key pair to the remote vehicle control client through the software development kit (SDK). The remote vehicle control client sends the public key to the card issuing system for storage through the cloud server. In this way, when the card issuing system issues personalized data, it may first encrypt the personalized data using the public key and send the ciphertext to the remote vehicle control client through the cloud server. After receiving the encrypted personalized data, the remote vehicle control client may decrypt the ciphertext using the private key in the public-private key pair to obtain the personalized data issued by the card issuing system.

[0041] In some embodiments of the present application, the above-mentioned personalized data may include, but is not limited to, communication keys required for the mobile NFC vehicle key to communicate with the vehicle, etc., or may also include other personalized data.

[0042] Step 103: Obtain the registration information of the NFC vehicle key and determine the target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle.

[0043] Optionally, when receiving the write card result returned by the software development kit (SDK), it may be prompted that the application of the NFC vehicle key is successful. At this time, the registration information of the NFC vehicle key may be obtained, and the target communication channel for transmitting the registration information is determined from the connections among the terminal device, the cloud server, and the vehicle.

[0044] It should be noted that due to the frequent lack of network or network failure at the vehicle end, the registration information of the NFC vehicle key cannot be sent to the key controller at the vehicle end through the cloud server, resulting in the inavailability of the key after registration and affecting the user experience. To solve this problem, the embodiment of the present application determines the target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle, so as to ensure that the registration information can be sent to the vehicle, which can greatly improve the registration success rate of the NFC vehicle key. Specifically, after obtaining the registration information of the NFC vehicle key, the registration information may be first sent to the cloud server to enable the cloud server to detect whether the network channel between the vehicle and the cloud server is normal; when receiving the feedback from the cloud server that the network channel is normal, the network channel between the vehicle and the cloud server is determined as the target communication channel for transmitting the registration information.

[0045] Step 104: Send the registration information to the vehicle based on the target communication channel so that the vehicle stores the registration information in the key controller. It should be noted that this key controller integrates NFC and Bluetooth and is responsible for receiving and processing NFC and Bluetooth key signals.

[0046] Among them, in the embodiments of the present application, the registration information of the NFC vehicle key may include but is not limited to the ID number of the NFC key card, the type of the NFC key card, the communication key required for communication between the NFC vehicle key and the vehicle, the validity period of the NFC key card, and the key status. Among them, the key status may include an available status, an invalid status (or unavailable status), etc.

[0047] Optionally, after the software development kit (SDK) performs the card writing operation on the NFC vehicle key, it will return a successful card writing result for the NFC vehicle key. When the remote vehicle control client receives the successful card writing result returned by the SDK, it prompts the user that the application for the NFC vehicle key is successful, obtains the registration information of the NFC vehicle key, and sends the registration information to the vehicle. When the vehicle receives the registration information of the NFC vehicle key, it can store the registration information in the key controller. It can be understood that the key controller has an NFC module, and the registration information of the NFC vehicle key is stored in this NFC module. In this way, when the user's handheld terminal device is close to the vehicle, the NFC vehicle key of the terminal device performs near-field communication with the key controller on the vehicle, so as to realize unlocking and locking control of the vehicle through the NFC vehicle key.

[0048] It should be noted that the remote vehicle control client can send the registration information of the NFC vehicle key to the vehicle online through the network channel; or, when the network channel is abnormal, the remote vehicle control client sends the registration information of the NFC vehicle key to the vehicle offline through the Bluetooth channel. That is to say, after the remote vehicle control client obtains the registration information of the NFC vehicle key, it can send the registration information to the cloud server. The cloud server can detect whether the network channel between it and the vehicle is normal. Among them, the network channel can be a wireless network channel such as 4G or 5G, and when the network channel is normal, it sends the registration information to the wireless network module on the vehicle through this network channel. The wireless network module on the vehicle converts the registration information into a corresponding CAN signal and sends the CAN signal to the key controller for storage, so as to achieve the purpose of synchronizing the registration information of the NFC vehicle key to the key controller. Among them, the corresponding relationship between the cloud service account and the vehicle identification number of the vehicle is stored in the cloud server. In this way, when the cloud server synchronizes the registration information of the NFC vehicle key to the key controller on the vehicle, it can find the corresponding vehicle based on this corresponding relationship and send the registration information of the NFC vehicle key to the key controller of this vehicle for storage through the network channel.

[0049] In order to ensure that the registration information of the NFC vehicle key can be synchronized to the vehicle's key controller in a timely manner, in an embodiment of the present application, when the remote vehicle control client receives the above-mentioned network channel anomaly returned by the cloud server, it detects whether the Bluetooth channel between the terminal device and the vehicle is in a connected state; when the Bluetooth channel is in a connected state, the Bluetooth channel between the terminal device and the vehicle is determined as the target communication channel for transmitting the registration information. That is to say, when the cloud server detects an anomaly in the network channel between the vehicle and itself, that is, there is an anomaly in the network channel between the vehicle and the cloud server, it can return the detection result of the network channel to the remote vehicle control client. When the remote vehicle control client receives the above-mentioned network channel anomaly returned by the cloud server, it detects whether the Bluetooth key between the terminal device and the vehicle is available, that is, it detects whether the Bluetooth channel between the terminal device and the vehicle is in a connected state. If the Bluetooth channel is in a connected state, the registration information is sent to the vehicle through the Bluetooth channel. It should be noted that the Bluetooth module on the vehicle can be integrated in the key controller. Therefore, the remote vehicle control client can directly send the registration information of the NFC vehicle key to the key controller through the Bluetooth channel for storage.

[0050] When the network channel between the vehicle and the cloud server is abnormal and the Bluetooth key is not logged in, the remote vehicle control client cannot send the registration information of the NFC vehicle key to the vehicle through the Bluetooth channel, resulting in the unavailability of the NFC vehicle key after successful registration. For the disclosure of the vehicle being offline and the Bluetooth key not being logged in, the user can use the key activation function in the remote vehicle control client to synchronize the key information. Optionally, in an embodiment of the present application, when the Bluetooth channel is in a disconnected state, a Bluetooth connection is established between the terminal device and the vehicle; when the Bluetooth connection is successful, the key controller on the vehicle is authenticated; when the authentication of the key controller is successful, the Bluetooth connection between the terminal device and the vehicle is determined as the target communication channel for transmitting the registration information.

[0051] That is to say, when the Bluetooth channel between the terminal device and the vehicle is in an unconnected state, the remote vehicle control client can prompt the user to turn on the Bluetooth on the terminal and prompt the user to log in to the Bluetooth key to establish a Bluetooth connection between the terminal device and the vehicle. When the Bluetooth connection between the terminal device and the vehicle is successful, the remote vehicle control client sends the Bluetooth name, password, and vehicle identification number stored by itself to the vehicle, so that the vehicle compares the Bluetooth name, password, and vehicle identification number stored by itself with those sent by the remote vehicle control client to implement the authentication of the remote vehicle control client and the key controller on the vehicle. When the Bluetooth name, password, and vehicle identification number stored by the vehicle are consistent with those sent by the remote vehicle control client, the remote vehicle control client determines that the authentication with the key controller on the vehicle is successful, and when the authentication of the key controller is successful, it sends the registration information of the NFC vehicle key to the key controller for storage through the Bluetooth connection.

[0052] According to the NFC vehicle key registration method of the embodiments of the present application, the registration of the NFC vehicle key is realized through the remote vehicle control client and the software development kit SDK on the terminal device, and the card issuing system, and the target communication channel for transmitting the registration information is determined from the connection between the terminal device, the cloud server, and the vehicle, and then the registration information of the NFC vehicle key is sent to the vehicle based on the target communication channel, so that the vehicle stores the registration information in the key controller, and the registration scenario of the NFC vehicle key of the vehicle is realized without affecting the user experience. In this way, the user can realize the control of unlocking and locking the vehicle by using the NFC vehicle key that has been registered with the vehicle key controller, and only need to use the user's terminal device to open the vehicle door, replacing the vehicle key to realize the unlocking function. In addition, by determining the target communication channel for transmitting the registration information from the connection between the terminal device, the cloud server, and the vehicle, for example, even in the case of no network condition of the vehicle, it can ensure that the registration information is sent to the vehicle, greatly improving the registration success rate of the NFC vehicle key.

[0053] Figure 2 is a structural block diagram of an NFC vehicle key registration system according to an embodiment of the present application. As Figure 2 shown, the NFC vehicle key registration system 200 may include: a terminal device 210, a cloud server 220, a card issuing system 230, and a vehicle 240. Among them, the terminal device 210 includes a remote vehicle control client 211, a software development kit SDK 212, and a security module 213.

[0054] Specifically, when the remote vehicle control client 211 receives an NFC vehicle key registration request input by the user, it requests the software development kit SDK 212 to add a data packet for the NFC vehicle key.

[0055] The software development kit (SDK) 212 is used to create a security domain on the security module 213 when a request is received, and download and install the Applet of the NFC vehicle key through the storage space of the security domain to complete the creation of the blank card of the NFC vehicle key.

[0056] The remote vehicle control client 211 is also used to receive the creation completion result of the blank card of the NFC vehicle key returned by the software development kit (SDK) 212, and request personalized data from the cloud server 220.

[0057] The cloud server 220 is used to forward the request for personalized data to the card issuing system 230, receive the personalized data issued by the card issuing system 230 according to the request, and send the personalized data issued by the card issuing system 230 to the remote vehicle control client 211.

[0058] The remote vehicle control client 211 is also used to send a card writing instruction to the software development kit (SDK) 212 when receiving the personalized data sent by the cloud server 220.

[0059] The software development kit (SDK) 212 is also used to write the personalized data into the blank card of the NFC vehicle key according to the card writing instruction.

[0060] The remote vehicle control client 211 is also used to prompt that the application for the NFC vehicle key is successful when receiving the card writing result returned by the software development kit (SDK) 212, obtain the registration information of the NFC vehicle key, determine the target communication channel for transmitting the registration information from the connection between the terminal device, the cloud server and the vehicle, and send the registration information to the vehicle 240 based on the target communication channel.

[0061] The vehicle 240 is used to store the registration information in the key controller 241 on the vehicle 240.

[0062] It should be noted that the remote vehicle control client can send the registration information of the NFC vehicle key to the vehicle online through the network channel; or, when the network channel is abnormal, the remote vehicle control client sends the registration information of the NFC vehicle key to the vehicle offline through the Bluetooth channel. Specifically, in an embodiment of the present application, the remote vehicle control client 211 is specifically used for: sending the registration information to the cloud server 220; the cloud server 220 is also used to detect whether the network channel between the vehicle 240 and the cloud server 220 is normal. The remote vehicle control client 211 is also used to determine the network channel between the vehicle 240 and the cloud server 220 as the target communication channel for transmitting the registration information when receiving the feedback from the cloud server 220 that the network channel is normal.

[0063] In order to ensure that the registration information of the NFC vehicle key can be synchronized to the vehicle's key controller in a timely manner, in an embodiment of the present application, the remote vehicle control client 211 is further configured to detect whether the Bluetooth channel between the terminal device 210 and the vehicle 240 is in a connected state when receiving feedback from the cloud server 220 that the network channel is abnormal; when the Bluetooth channel is in a connected state, the Bluetooth channel between the terminal device 210 and the vehicle 240 is determined as the target communication channel for transmitting the registration information.

[0064] When the network channel between the vehicle and the cloud server is abnormal and the Bluetooth key is not logged in, the remote vehicle control client cannot send the registration information of the NFC vehicle key to the vehicle through the Bluetooth channel, resulting in the unavailability of the NFC vehicle key after successful registration. For the disclosure of the vehicle being offline and the Bluetooth key not being logged in, the user can use the key activation function in the remote vehicle control client to synchronize the key information. In an embodiment of the present application, the remote vehicle control client 211 is further configured to establish a Bluetooth connection between the terminal device 210 and the vehicle 240 when the Bluetooth channel is in a disconnected state; when the Bluetooth connection is successful, authenticate the key controller 241 on the vehicle 240; when the authentication of the key controller 241 is successful, the Bluetooth connection between the terminal device 210 and the vehicle 240 is determined as the target communication channel for transmitting the registration information.

[0065] According to the NFC vehicle key registration system of the embodiments of the present application, the registration of the NFC vehicle key is realized through the remote vehicle control client and the software development kit SDK on the terminal device, as well as the card issuing system, and the target communication channel for transmitting the registration information is determined from the connections between the terminal device, the cloud server, and the vehicle. Furthermore, based on the target communication channel, the registration information of the NFC vehicle key is sent to the vehicle, so that the vehicle stores the registration information in the key controller. Without affecting the user experience, the registration scenario of the vehicle's NFC vehicle key is realized. In this way, the user can control the unlocking and locking of the vehicle by using the NFC vehicle key that has been registered with the vehicle key controller, and only needs to use the user's terminal device to open the vehicle door, replacing the vehicle key to achieve the unlocking function. In addition, by determining the target communication channel for transmitting the registration information from the connections between the terminal device, the cloud server, and the vehicle, even in the case of the vehicle having no network condition, it can be ensured that the registration information is sent to the vehicle, greatly improving the registration success rate of the NFC vehicle key.

[0066] It should be noted that the NFC vehicle key registration system according to the embodiments of the present application can be used to create and register an NFC vehicle key on a terminal device, and synchronize the registration information of the NFC vehicle key to the key controller on the vehicle for storage, so that the key controller stores the registration information of the NFC vehicle key. In this way, when the user brings the terminal device close to the vicinity of the key controller, the unlocking and locking control of the vehicle can be realized. To facilitate those skilled in the art to understand the present application, the interaction process of the NFC vehicle key registration system will be illustrated by way of example below. First, the functions of the systems involved in the NFC vehicle key blank issuance process are introduced as follows: Remote vehicle control client APP: Front end, the user can register, delete, and manage keys through the APP; SP-TSM system: Back-end server, providing the installation package of the mobile phone NFC vehicle key mini-program application; Software Development Kit SDK: Download and install the mini-program, store application personalization data, support unlocking and locking the vehicle door and trunk in the powerless mode by swiping the card; SEI-TSM: Back-end server, managing the mobile phone security module SE; Card issuance system: Back-end server, key management, key generation and management, personalization data generation and management.

[0067] According to the above system functions, in this embodiment, as Figure 3 shown, the interaction process of the NFC vehicle key registration system is as follows:

[0068] S1: The user opens the remote vehicle control client APP and logs in through the cloud service account and password;

[0069] S2: After successful login, the user finds the key management interface on the display interface of the remote vehicle control client APP and clicks to select "Add mobile phone NFC vehicle key";

[0070] S3: When the remote vehicle control client APP receives the NFC vehicle key registration request input by the user, it sends the NFC vehicle key registration request to the mobile phone factory wallet APP (providing a Wallet Kit open service, which can manage cards, certificates, tickets, coupons, keys, etc. in life). The wallet APP queries whether the mobile phone supports NFC and feeds back the result to the remote vehicle control client APP;

[0071] S4: If the feedback result is that the mobile phone NFC is supported, then the mobile phone NFC vehicle key is activated; if the feedback result is that the mobile phone NFC is not supported, then an error prompt is returned;

[0072] S5: The remote vehicle control client APP requests a short message verification code from the cloud server. The cloud server sends a short message to the mobile phone number reserved by the vehicle owner when purchasing the vehicle. The user obtains the vehicle owner's authorization by inputting the short message verification code;

[0073] S6: After the short message verification is passed, the remote vehicle control client APP requests to add a Pass package from the mobile phone SDK;

[0074] S7: After receiving the request, the mobile SDK verifies the signature and checks whether the type of the Pass package added in the request is selected as NFC card;

[0075] S8: After the mobile SDK successfully verifies the signature, it applies to the wallet server to create a white card. The wallet server allocates card resources and returns the application result to the mobile SDK;

[0076] S9: After the blank card application is successful, the mobile SDK requests the wallet server to create an SSD and download an application. The wallet server sends an SSD creation and application download instruction to the mobile SDK. The mobile SDK creates a security domain on the mobile phone's security module SE according to the instruction to download and install the NFC car key Applet through the storage space of the security domain to complete the creation of the NFC car key blank card;

[0077] S10: After the SSD is created and the application is downloaded successfully, the SDK requests pre-personalization from the wallet server; wherein the pre-personalization may be a public-private key pair preset by the wallet server for the NFC car key blank card for communication;

[0078] S11: The wallet server sends a pre-personalization instruction to the mobile SDK, and the mobile SDK forwards the pre-personalization instruction sent by the wallet server to the mobile security module SE for storage;

[0079] S12: After pre-personalization is completed, the mobile SDK returns the result of adding the Pass package to the remote vehicle control client APP;

[0080] S13: After the Pass package is added successfully, the remote control car client APP applies for an interactive TOKEN from the mobile SDK, and the mobile SDK returns the TOKEN to the remote control car client APP, which stores the TOKEN.

[0081] S14: The remote control vehicle client APP applies to the mobile SDK for a temporary public key for card communication, and the mobile SDK applies to the mobile security module SE for a temporary public-private key pair, and returns the public key to the mobile SDK, which forwards the public key to the remote control vehicle client APP for storage;

[0082] S15: The remote vehicle control client APP requests personalized data from the cloud server, and the cloud server requests personalized data from the card issuing system;

[0083] S16: The card issuing system issues personalized data and uses public key encryption to transmit the ciphertext to the SP-TSM system; the SP-TSM system sends the ciphertext to the remote vehicle control client APP through the cloud server;

[0084] S17: The remote vehicle control client APP sends a card writing instruction to the mobile phone SDK, and the mobile phone SDK performs card writing personalization to write the personalization data sent by the card issuing system into the NFC vehicle key;

[0085] S18: The mobile phone SDK synchronizes the personalization data to the mobile phone security module SE and the SEI-TSM system;

[0086] S19: The mobile phone SDK returns the card writing personalization result to the remote vehicle control client APP;

[0087] S20: The remote vehicle control client APP prompts that the vehicle key application is successful;

[0088] S21: The remote vehicle control client APP returns the registration result for the NFC vehicle key to the cloud server. When the vehicle is online, the cloud server sends the key registration information to the vehicle through a network channel (such as a 4G channel or a 5G channel); when the vehicle is offline, the remote vehicle control client APP detects whether the Bluetooth key is connected. When it detects that the Bluetooth key is logged in and a connection is established with the vehicle, the remote vehicle control client APP sends the key registration information to the vehicle through the Bluetooth channel;

[0089] S22: The key controller on the vehicle side stores the registration information of the NFC vehicle key. The registration information may include the key ID, key status, etc. The key controller returns the result to the cloud server or the remote vehicle control client APP;

[0090] S23: After the cloud server receives the successful response for storing the registration information of the NFC vehicle key returned by the vehicle, it returns the key registration success result to the remote vehicle control client APP;

[0091] S24: After the remote vehicle control client APP receives the key registration success response, it updates the key list, and the registration of the mobile phone NFC vehicle key is successful.

[0092] For step S21, when the vehicle is offline and the Bluetooth key is not logged in, the remote vehicle control client APP cannot send the key registration information to the vehicle through the Bluetooth channel, resulting in the inavailability of the key after successful registration. For the condition where the vehicle is offline and the Bluetooth key is not logged in, the user can use the key activation function in the remote vehicle control client APP to synchronize the key information. Figure 4 The business flow chart for activating the NFC vehicle key through the Bluetooth channel when the vehicle is offline is as follows. The specific operation steps are as follows:

[0093] Continuing from the above S21: The vehicle is offline, and the remote vehicle control client APP detects that the Bluetooth key is not connected and executes step S25;

[0094] S25: After the user logs in to the remote vehicle control client APP, the user can click "NFC vehicle key of this device" on the key management interface of the APP and click to activate the key;

[0095] S26: The remote vehicle control client APP prompts the user to turn on the Bluetooth of the mobile phone to automatically log in to the Bluetooth key and establish a Bluetooth connection between the mobile phone and the vehicle;

[0096] S27: After the Bluetooth connection is successful, the remote vehicle control client APP and the vehicle-side key controller perform identity authentication;

[0097] S28: After the authentication is successful, the remote vehicle control client APP automatically jumps to the key activation interface and completes the following steps:

[0098] i. The remote vehicle control client APP sends the registration instruction of the NFC vehicle key and the key registration information (such as including the key ID, key status, etc.) to the vehicle through the Bluetooth channel, and at the same time prompts the user "The key is being activated. Please do not move away from the vehicle and keep the Bluetooth connection", and waits for the vehicle response with a countdown.

[0099] ii. The vehicle key controller stores the key ID and key status and returns the key activation result response to the remote vehicle control client APP;

[0100] iii. After the remote vehicle control client APP receives the successful response, it displays "Activation result". The user clicks to complete, and the remote vehicle control client APP returns to the key management interface and updates the key list;

[0101] iv. When it is detected that the mobile phone has a network, the remote vehicle control client APP synchronizes the key activation result to the cloud server; if the mobile phone has no network, it waits to synchronize the key activation information to the cloud server when logging in to the cloud service account next time;

[0102] v. If the activation fails, the remote vehicle control client APP prompts the user that the activation fails and please try again later, and detects whether the Bluetooth connection is disconnected.

[0103] It should be noted that the embodiments of the present application provide a solution for sending NFC vehicle key information and registration instructions through the Bluetooth channel between the mobile phone and the in-vehicle unit. It can realize the synchronization of NFC vehicle key registration information under the conditions of vehicle offline and no network, and complete the automatic sending of NFC vehicle keys or the manual activation of NFC vehicle keys. For users, there is no difference in the operation process of the remote vehicle control client APP between automatically sending NFC vehicle keys through the Bluetooth channel and the cloud server sending NFC vehicle key registration information when the vehicle is online. To activate the key through the Bluetooth channel, the user only needs to click the activation control of the NFC vehicle key using the remote vehicle control client APP, turn on the Bluetooth of the mobile phone, and approach the vehicle. After establishing a Bluetooth connection, one-key activation of the NFC vehicle key can be achieved. Without affecting the user experience, the present application realizes the scenario of registering the mobile phone NFC vehicle key under the condition of no network for the vehicle. The mobile phone NFC vehicle key registration method of the present application can realize that under the condition of vehicle offline, the mobile phone sends key registration instructions and key information to the vehicle-side key controller through the Bluetooth channel, and the vehicle side updates the key list and key status, without relying on the vehicle 4G terminal and network. Therefore, it can be compatible with vehicles without network signals, which is convenient for users to use.

[0104] To implement the above embodiments, the present application also proposes a terminal device. As Figure 5 shown, the terminal device 500 may include: a memory 510, a processor 520, and a computer program 530 stored on the memory 510 and executable on the processor 520. When the processor 520 executes the program 530, it implements the NFC vehicle key registration method described in any of the above embodiments of the present application.

[0105] To implement the above embodiments, the present application also proposes a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the NFC vehicle key registration method described in any of the above embodiments of the present application.

[0106] In the description of this specification, the description with reference to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0107] Any process or method description represented in a flowchart or otherwise described herein can be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logic function or process. The scope of the preferred embodiments of the present application includes additional implementations where functions may be executed not in the order shown or discussed, including in a substantially simultaneous manner according to the functions involved or in a reverse order, which should be understood by those skilled in the art to which the embodiments of the present application pertain.

[0108] Logic and / or steps represented in a flowchart or otherwise described herein, for example, can be considered a sequenced list of executable instructions for implementing a logical function and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device. As used in this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection having one or more wires (electronic device), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable medium on which the program can be printed, as the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or other suitable processing as necessary, and then stored in a computer memory.

[0109] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one of the following techniques known in the art or a combination thereof can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), and the like.

[0110] Those of ordinary skill in the art can understand that all or part of the steps carried out in the methods of the above embodiments can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0111] In addition, in each of the embodiments of the present application, each functional unit can be integrated into a processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. When the above integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0112] The storage medium mentioned above can be a read-only memory, a magnetic disk, an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. An NFC vehicle key registration method, characterized in that, the method is applied to a terminal device, and the method includes: when receiving an NFC vehicle key registration request input by a user, requesting the software development kit SDK on the terminal device to add a data packet for the NFC vehicle key; wherein, when receiving the request, the software development kit SDK creates a security domain on the security module in the terminal device to download and install the Applet applet of the NFC vehicle key through the storage space of the security domain to complete the creation of the NFC vehicle key blank card; receiving the creation completion result of the NFC vehicle key blank card returned by the software development kit SDK, and requesting personalized data from the card issuing system through the cloud server to complete the card writing operation of the NFC vehicle key blank card; obtaining the registration information of the NFC vehicle key, and determining a target communication channel for transmitting the registration information from the connection between the terminal device, the cloud server and the vehicle; sending the registration information to the vehicle based on the target communication channel, so that the vehicle stores the registration information in the key controller.

2. The method according to claim 1, characterized in that, determining a target communication channel for transmitting the registration information from the connection between the terminal device, the cloud server and the vehicle includes: sending the registration information to the cloud server, so that the cloud server detects whether the network channel between the vehicle and the cloud server is normal; when receiving the feedback from the cloud server that the network channel is normal, determining the network channel between the vehicle and the cloud server as the target communication channel for transmitting the registration information.

3. The method according to claim 2, characterized in that, further includes: when receiving the feedback from the cloud server that the network channel is abnormal, detecting whether the Bluetooth channel between the terminal device and the vehicle is in a connected state; when the Bluetooth channel is in a connected state, determining the Bluetooth channel between the terminal device and the vehicle as the target communication channel for transmitting the registration information.

4. The method according to claim 3, characterized in that, further includes: when the Bluetooth channel is in a disconnected state, establishing a Bluetooth connection between the terminal device and the vehicle; when the Bluetooth connection is successful, authenticating the key controller on the vehicle; when the authentication of the key controller is successful, determining the Bluetooth connection between the terminal device and the vehicle as the target communication channel for transmitting the registration information.

5. An NFC vehicle key registration system, characterized in that, includes: a terminal device, a cloud server, a card issuing system and a vehicle, wherein, the terminal device includes a remote vehicle control client, a software development kit SDK and a security module, wherein, the remote vehicle control client is used for requesting the software development kit SDK to add a data packet for the NFC vehicle key when receiving an NFC vehicle key registration request input by a user; The software development kit (SDK) is used to create a security domain on the security module when the request is received, so as to download and install the Applet applet of the NFC vehicle key through the storage space of the security domain to complete the creation of the blank card of the NFC vehicle key; The remote vehicle control client is further configured to receive the creation completion result of the blank card of the NFC vehicle key returned by the software development kit (SDK), and request personalization data from the card issuing system through the cloud server to complete the card writing operation of the blank card of the NFC vehicle key; The remote vehicle control client is further configured to obtain the registration information of the NFC vehicle key, determine a target communication channel for transmitting the registration information from the connections among the terminal device, the cloud server, and the vehicle, and send the registration information to the vehicle based on the target communication channel; The vehicle is configured to store the registration information in a key controller on the vehicle.

6. The system according to claim 5, wherein, the remote vehicle control client is specifically configured to: send the registration information to the cloud server; the cloud server is further configured to detect whether the network channel between the vehicle and the cloud server is normal; the remote vehicle control client is further configured to, when receiving the feedback from the cloud server that the network channel is normal, determine the network channel between the vehicle and the cloud server as the target communication channel for transmitting the registration information.

7. The system according to claim 6, wherein, the remote vehicle control client is further configured to: when receiving the feedback from the cloud server that the network channel is abnormal, detect whether the Bluetooth channel between the terminal device and the vehicle is in a connected state; when the Bluetooth channel is in a connected state, determine the Bluetooth channel between the terminal device and the vehicle as the target communication channel for transmitting the registration information.

8. The system according to claim 7, wherein, the remote vehicle control client is further configured to: when the Bluetooth channel is in a non-connected state, establish a Bluetooth connection between the terminal device and the vehicle; when the Bluetooth connection is successful, authenticate the key controller on the vehicle; when the authentication of the key controller is successful, determine the Bluetooth connection between the terminal device and the vehicle as the target communication channel for transmitting the registration information.

9. A terminal device, wherein, it includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the NFC vehicle key registration method according to any one of claims 1 to 4 is implemented.

10. A computer-readable storage medium, on which a computer program is stored, wherein, when the computer program is executed by a processor, the NFC vehicle key registration method according to any one of claims 1 to 4 is implemented.

Images