A bluetooth key symmetric key authentication method and system

Abstract

The application discloses a Bluetooth key symmetric key authentication method and system, which comprises the following steps: initiating Bluetooth automatic pairing to a TBox, checking pairing by the TBox; sending a LEAF type check key to the TBox, and comparing the LEAF key with a ROOT key saved by the TBox; initiating a seed application to the TBox, generating an encrypted seed when the TBox receives the application, and returning the seed; performing MD5 on the seed+VIN+date by the TBox, and obtaining a 32-bit string used as an encrypted key of a control instruction; checking the encrypted key; encrypting the control instruction by using the encrypted key, and outputting the ciphertext to the TBox; decrypting the control instruction by using the encrypted key after the TBox receives the ciphertext control instruction, and executing the control instruction; and encrypting the execution result by the TBox, and returning the execution result. The technical scheme of the application establishes a Bluetooth interaction scheme between a mobile phone APP (mobile phone) and a TBox (a TBox provided with a Bluetooth key device), and the whole scheme adopts a symmetric encryption system, so that the information safety is ensured, and the rapidity of instruction response is considered.

Description

Technical Field

[0001] This invention relates to the field of vehicle Bluetooth key technology, and in particular to a Bluetooth key symmetric key authentication method and system. Background Technology

[0002] The application of in-vehicle TBox Bluetooth key functionality is becoming increasingly widespread. Its basic functions have evolved from traditional locking and unlocking to more intelligent near-field vehicle control functions, such as turning on / off welcome lights, controlling the air conditioning, starting / stopping the engine, and opening / closing windows. Because it can control the vehicle, Bluetooth keys are required to have a higher level of security, and the communication data between the mobile app and the in-vehicle TBox must be strictly encrypted to prevent interception or cracking over the air.

[0003] The existing problem is that the data transmission between the TBox Bluetooth key system and the mobile Bluetooth key APP is mostly implemented in plaintext or simple encryption. This data can be easily intercepted and cracked over the air, which can easily lead to vehicle security problems. At best, it can cause property loss inside the vehicle; at worst, it can lead to vehicle theft and affect personal safety.

[0004] In summary, how to achieve encrypted authentication of data between a mobile phone with a Bluetooth key APP (hereinafter referred to as the mobile APP) and a TBox equipped with a Bluetooth key device (hereinafter referred to as the TBox) to prevent the data between the TBox Bluetooth key system and the mobile Bluetooth key APP from being intercepted and cracked is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The main objective of this invention is to propose a Bluetooth key symmetric key authentication method and system, which aims to achieve data encryption authentication between a mobile phone calibrated with a Bluetooth key APP and a TBox equipped with a Bluetooth key device.

[0006] The technical solution of this invention to solve the above-mentioned technical problems is to provide a Bluetooth key symmetric key authentication method, comprising the following steps:

[0007] Initiate automatic Bluetooth pairing to the TBox; the TBox verifies the pairing.

[0008] The LEAF key is sent to the TBox, which then compares the LEAF key with the ROOT key stored in its own memory.

[0009] A seed request is sent to TBox. When TBox receives the request, it generates an encrypted seed and sends this seed back.

[0010] TBox performs MD5 hashing on "seed+VIN+date" and the resulting 32-bit string is used as the encryption key for control commands.

[0011] Verify the encrypted key;

[0012] The control commands are encrypted using an encryption key and then transmitted to the TBox in ciphertext.

[0013] After receiving the encrypted control command, TBox first decrypts the control command using the encryption key and then executes the control command.

[0014] TBox encrypts the execution result and sends it back.

[0015] Furthermore, in the step of sending a LEAF-type verification key to the TBox, and the TBox comparing the LEAF key with its own stored ROOT key,

[0016] The LEAFKey contains a ROOT-type verification key, and the application information is encrypted using AES128 symmetric encryption.

[0017] Furthermore, in the step of sending a LEAF-type verification key to the TBox, and the TBox comparing the LEAF key with its own stored ROOT key,

[0018] The ROOT key is generated according to the rules as a ROOTKey string. It is encrypted using AES128 symmetric encryption. The 16-bit string is converted into 16 bytes of hexadecimal data and stored in TBox. This key can be stored in the security encryption chip and is only used to verify LEAF type check key data.

[0019] Furthermore, in the step of initiating a seed request to TBox, TBox generating an encrypted seed upon receiving the request, and returning this seed for transmission,

[0020] The seed is a 16-byte random number randomly generated by TBox and stored in its own memory.

[0021] Furthermore, in the step where the TBox performs MD5 hashing on "seed+VIN+date" and uses the resulting 32-bit string as the encryption key for control commands,

[0022] The date includes the year, month, and day.

[0023] To address the aforementioned technical problems, this invention also proposes a Bluetooth key symmetric key authentication system, comprising the following steps:

[0024] The mobile app initiates automatic Bluetooth pairing with the TBox, and the TBox verifies the pairing.

[0025] The mobile app initiates identity verification by sending a LEAF-type verification key to the TBox. The TBox then compares the LEAF key with the ROOT key stored in its own database.

[0026] The mobile app sends a seed request to the TBox. When the TBox receives the request, it generates an encrypted seed and returns the seed to the mobile app.

[0027] The mobile app and TBox perform MD5 hashing on "seed+VIN+date" and the resulting 32-bit string is used as the encryption key for control commands.

[0028] Both the mobile app and TBox verify the encrypted key;

[0029] The mobile app encrypts the control commands using an encryption key and transmits them to the TBox in ciphertext. The TBox receives the ciphertext control commands, decrypts them using the encryption key, and executes the commands.

[0030] TBox encrypts the execution result and returns it to the mobile app.

[0031] The mobile app decrypts and executes the results, which are then displayed on the interface.

[0032] The technical solution of this invention establishes a Bluetooth interaction scheme between a mobile APP (mobile phone) and a TBox (a TBox equipped with a Bluetooth key device). The scheme adopts a symmetric encryption system to ensure information security while also taking into account the speed of command response. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0034] Figure 1 This is a flowchart illustrating the Bluetooth key symmetric key authentication method of the present invention.

[0035] Figure 2 This is an example diagram of the seed described in this invention;

[0036] Figure 3 This is a Bluetooth communication flowchart of the Bluetooth key symmetric key authentication method and system described in this invention. Detailed Implementation

[0037] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0038] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0039] Furthermore, in this invention, descriptions involving "first," "second," etc., are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "several" or "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0040] In this invention, unless otherwise explicitly specified and limited, the terms "connection," "fixed," etc., should be interpreted broadly. For example, "fixed" can mean a fixed connection, a detachable connection, or an integral part; it can mean a mechanical connection or an electrical connection; it can mean a direct connection or an indirect connection through an intermediate medium; it can mean the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0041] Furthermore, the technical solutions of the various embodiments of the present invention can be combined with each other, but only if they are based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by the present invention.

[0042] This invention proposes a Bluetooth key symmetric key authentication method, which aims to achieve data encryption authentication between a mobile phone calibrated with a Bluetooth key APP and a TBox equipped with a Bluetooth key device.

[0043] The specific details of the Bluetooth key symmetric key authentication method proposed in this invention will be described below in specific embodiments:

[0044] In the technical solution of this embodiment, such as Figure 1As shown, a Bluetooth key symmetric key authentication method includes the following steps:

[0045] S10: Initiates automatic Bluetooth pairing to TBox, TBox verifies pairing;

[0046] Understandably, if the TBox verification and pairing are successful, proceed to step S20; otherwise, end the process.

[0047] S20: Send the LEAF verification key to the TBox, and the TBox will compare the LEAF key with the ROOT key stored in its own memory;

[0048] Understandably, if the comparison is successful, proceed to step S30; otherwise, end the process.

[0049] S30: Initiate a seed request to TBox. When TBox receives the request, it generates an encrypted seed and sends this seed back.

[0050] S40: TBox performs MD5 hashing on “seed+VIN+date”, and the resulting 32-bit string is used as the encryption key for control commands;

[0051] S50: Verify the encrypted key;

[0052] Understandably, verifying the encrypted key involves both the mobile app and the TBox verifying the encrypted key. If both verifications are successful, proceed to step S60; otherwise, the process ends.

[0053] S60: Encrypt control commands using an encryption key and transmit them to the TBox in ciphertext;

[0054] S70: After receiving the encrypted control command, TBox first decrypts the control command using the encryption key and then executes the control command;

[0055] S80: TBox encrypts the execution result and sends it back.

[0056] Understandably, the technical solution of this application establishes a Bluetooth interaction scheme between a mobile APP (mobile phone) and a TBox (a TBox equipped with a Bluetooth key device). The scheme adopts a symmetric encryption system to ensure information security while taking into account the speed of command response.

[0057] Furthermore, in the step of sending a LEAF-type verification key to the TBox, and the TBox comparing the LEAF key with its own stored ROOT key,

[0058] The LEAFKey contains a ROOT-type verification key and application information (including user ID, application date, and validity period), and is encrypted using AES128 symmetric encryption.

[0059] Understandably, the password used here is the same 16-byte encryption key in the ROOTKey. When the mobile app requests a LEAF-type verification key, it sends the encrypted data to the TSP, which then forwards it to the mobile app (the app does not verify the LEAFKey). This is used for identity verification after the mobile app successfully connects to BLE. The maximum validity period of a LEAFKey is six months. After six months from the date of LEAFKey application, a new LEAFKey application needs to be initiated, which is controlled by the mobile app.

[0060] Furthermore, in the step of sending a LEAF-type verification key to the TBox, and the TBox comparing the LEAF key with its own stored ROOT key,

[0061] The ROOT key is generated according to the rules as a ROOTKey string. It is encrypted using AES128 symmetric encryption. The 16-bit string is converted into 16 bytes of hexadecimal data and stored in TBox. This key can be stored in the security encryption chip and is only used to verify LEAF type check key data.

[0062] Furthermore, such as Figure 2 As shown, in the step of initiating a seed request to TBox, TBox generating an encrypted seed upon receiving the request, and then sending this seed back,

[0063] The seed is a 16-byte random number randomly generated by TBox and stored in its own memory.

[0064] Furthermore, in the step where the TBox performs MD5 hashing on "seed+VIN+date" and uses the resulting 32-bit string as the encryption key for control commands,

[0065] The date includes the year, month, and day.

[0066] In one feasible implementation, the encryption key is a 32-bit string obtained by performing an MD5 hash of "seed + VIN + date (year, month, day)" on the TBox and the mobile app. This string is used as the key for encrypting the control commands. The command encryption uses AES128, and the format of the encrypted data depends on the Bluetooth protocol.

[0067] To address the aforementioned technical problems, this invention also proposes a Bluetooth key symmetric key authentication system, such as... Figure 3 As shown, it includes the following steps:

[0068] The mobile app initiates automatic Bluetooth pairing with the TBox, and the TBox verifies the pairing.

[0069] The mobile app initiates identity verification by sending a LEAF-type verification key to the TBox. The TBox then compares the LEAF key with the ROOT key stored in its own database.

[0070] The mobile app sends a seed request to the TBox. When the TBox receives the request, it generates an encrypted seed and returns the seed to the mobile app.

[0071] The mobile app and TBox perform MD5 hashing on "seed+VIN+date" and the resulting 32-bit string is used as the encryption key for control commands.

[0072] Both the mobile app and TBox verify the encrypted key;

[0073] The mobile app encrypts the control commands using an encryption key and transmits them to the TBox in ciphertext. The TBox receives the ciphertext control commands, decrypts them using the encryption key, and executes the commands.

[0074] TBox encrypts the execution result and returns it to the mobile app.

[0075] The mobile app decrypts and executes the results, which are then displayed on the interface.

[0076] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A Bluetooth key symmetric key authentication method, characterized by, The method comprises the following steps: Bluetooth automatic pairing is initiated to the TBox, and the TBox checks the pairing; A LEAF type check key is sent to the TBox, and the TBox compares the LEAF key with a ROOT key stored by itself; A seed application is initiated to the TBox, and the TBox generates an encrypted seed when receiving the application and returns the seed; The TBox performs MD5 on "seed+VIN+date" to obtain a 32-bit string used as an encryption key of the control instruction; The encryption key is checked; The control instruction is encrypted by using the encryption key, and the encrypted control instruction is sent to the TBox; The TBox receives the encrypted control instruction, decrypts the control instruction by using the encryption key, and executes the control instruction; The TBox encrypts the execution result and sends it back.

2. The Bluetooth key symmetric key authentication method of claim 1, wherein, In the step of sending the LEAF type check key to the TBox and comparing the LEAF key with the ROOT key stored by the TBox, The LEAF key comprises a ROOT type check key and application information, and is encrypted by using an AES128 symmetric encryption mode.

3. The Bluetooth key symmetric key authentication method of claim 1, wherein, In the step of sending the LEAF type check key to the TBox and comparing the LEAF key with the ROOT key stored by the TBox, The ROOT key is a ROOT key string generated according to a rule, is encrypted by using an AES128 symmetric encryption mode, is converted into 16 bytes of 16 hexadecimal data, and is stored in the TBox. The key can be stored in a secure encryption chip and is used only for verifying the LEAF type check key data.

4. The Bluetooth key symmetric key authentication method of claim 1, wherein, In the step of initiating a seed application to the TBox and generating an encrypted seed by the TBox when receiving the application and returning the seed, The seed is a 16-byte random number randomly generated by the TBox and stored in the memory of the TBox.

5. The Bluetooth key symmetric key authentication method of claim 1, wherein, In the step of performing MD5 on "seed+VIN+date" by the TBox to obtain a 32-bit string used as an encryption key of the control instruction, The date comprises year, month and day.

6. A Bluetooth key symmetric key authentication system, characterized by, The method comprises the following steps: Bluetooth automatic pairing is initiated to the TBox by the mobile phone APP, and the TBox checks the pairing; Identity check is initiated by the mobile phone APP, and a LEAF type check key is sent to the TBox, and the TBox compares the LEAF key with a ROOT key stored by itself; A seed application is initiated to the TBox by the mobile phone APP, and the TBox generates an encrypted seed when receiving the application and returns the seed to the mobile phone APP; The mobile phone APP and the TBox perform MD5 on "seed+VIN+date" to obtain a 32-bit string used as an encryption key of the control instruction; The encryption key is checked by the mobile phone APP and the TBox; The control instruction is encrypted by the mobile phone APP by using the encryption key, and the encrypted control instruction is sent to the TBox, The TBox receives the encrypted control instruction, decrypts the control instruction by using the encryption key, and executes the control instruction; TBox will encrypt the execution result and return to the mobile APP, The mobile APP decrypts the execution result and displays it on the interface.

Images