Establishing BLE communication between a remote key fob and a vehicle

Abstract

A method for communication between a vehicle remote key fob (110) and a vehicle (120) is proposed. The key fob (110) and the vehicle (120) are configured to communicate using the BLE and NFC communication protocols. The method includes pairing (S10) of the key fob (110) and the vehicle (120) for the NFC communication protocol. The method includes exchanging (S20), using the NFC communication protocol, a BLE key (132) between the key fob (110) and the vehicle (120). The method includes establishing (S30) BLE communication between the key fob (110) and the vehicle (120) using the exchanged BLE key (132). The method improves the establishment of BLE communication between the remote key fob (110) and the vehicle (120). [Fig. 2]

Description

Title of the invention: Establishing BLE communication between a remote key fob and a vehicle. Technical field

[0001] This disclosure relates to a method of communication between a vehicle remote key fob and a vehicle, a computer program for such a remote key fob and / or vehicle system, a storage medium for such a program and a remote key fob configured for such a communication method. Technical background

[0002] Vehicle remote key fobs, often called "key fobs" or "key identifiers," are now used to perform various vehicle functions, such as unlocking the doors and / or starting the vehicle when the user approaches. To perform these functions, the key fobs are configured to communicate with the system using several communication protocols. For example, the key fob and the system can be configured to communicate using an NFC (Near Field Communication) communication protocol and a BLE (Bluetooth Low Energy) communication protocol.

[0003] As illustrated in [Fig. 1] describing the prior art, for each communication protocol, before communicating with said protocol, the key fob 110 is generally paired with the vehicle 120, in particular to secure the use of the functions. The key fob 110 and the vehicle 120 perform, in particular, a first secure pairing S10 for the NFC protocol and a second pairing SI1 for the BLE protocol. The second pairing SU includes, in particular, the secure exchange of a shared BLE key between the identifier and the vehicle. A privilege escalation step can be performed beforehand at the vehicle level so that such pairings are authorized by the vehicle.

[0004] For the NFC protocol, S10 pairing is generally less complex, as the NFC protocol is only usable over short distances, which reduces security risks, particularly identity theft. NFC S10 pairing can, for example, be performed once the key fob 110 is placed on a support inside the vehicle and detected on that support by the vehicle. As for the BLE protocol, it can be used over longer distances. This is particularly true when the user is outside the vehicle, which necessitates the use of more complex pairing algorithms (such as the ECDH key exchange protocol, an acronym for Elliptic Curve Diffie-Hellman). These pairing algorithms typically include cryptographic encryption, which is time-consuming to execute. Furthermore, BLE SI 1 pairing may require an S12 action from the user on the key fob before initiating. Establishing BLE communication between the key fob and the vehicle is therefore longer and more complex. Moreover, because BLE pairing is performed before the BLE protocol is used, it reduces the responsiveness of the functions subsequently executed based on the established BLE communication.

[0005] There is therefore a need to improve the establishment of BLE communication between a key fob and a vehicle, in particular to accelerate the time of establishing BLE communication. Summary

[0006] A method for communication between a vehicle remote key fob and a vehicle is proposed. The key fob and the vehicle are configured to communicate using the BLE and NFC communication protocols. The method includes pairing the key fob and the vehicle for the NFC communication protocol. The method includes exchanging a BLE key between the key fob and the vehicle using the NFC communication protocol. The method includes establishing BLE communication between the key fob and the vehicle using the exchanged BLE key.

[0007] The key fob may include non-volatile memory. The BLE key exchange may include the vehicle sending the BLE key to the key fob using the NFC communication protocol, the key fob receiving the sent BLE key, and the key fob recording the received BLE key on the non-volatile memory.

[0008] The exchange of the BLE key may further include, before the BLE key is sent, encryption of the BLE key. The recorded BLE key may be the encrypted BLE key.

[0009] The transmission may include sending a command to register the BLE key to non-volatile memory. The sent command may be encrypted.

[0010] The method may further include deleting the BLE key stored on the non-volatile memory.

[0011] The key fob may include a BLE component. Establishing BLE communication may include waking up the BLE component, reading the BLE key exchanged by the woken BLE component, and carrying out one or more BLE exchanges between the key fob and the vehicle using the read BLE key.

[0012] The vehicle may include a mounting bracket. Pairing the key fob and the vehicle for the NFC communication protocol may involve placing the key fob on the vehicle's mounting bracket.

[0013] A first computer program for a key fob is also proposed. The first computer program comprises instructions which, when the program is executed by a processor in the key fob, cause the latter to implement said process with a vehicle.

[0014] A second computer program for a vehicle system is also proposed. The second computer program includes instructions which, when the program is executed by a processor of the vehicle system, cause the latter to implement said method with a key fob.

[0015] A third computer program is also proposed, comprising the first computer program and the second computer program.

[0016] A computer-readable storage medium is also proposed on which the first computer program, the second computer program and / or the third computer program is recorded.

[0017] A vehicle remote control key fob configured to perform BLE and NFC communications with a vehicle is also proposed. The key fob is configured to communicate with the vehicle using said method. Brief description of the figures

[0018] Non-limiting examples will be described with reference to the following figures:

[0019] [Fig.1] illustrates an example of an existing solution for establishing BLE communication.

[0020] Figure [Fig. 2] illustrates an example of a process flowchart.

[0021] Figs. 3, 4, 5 and 6 illustrate examples of remote key housing and vehicle configured to perform the process. Detailed description

[0022] With reference to the flowchart in [Fig. 2], a method for communication between a vehicle remote key fob and a vehicle is proposed. The key fob and the vehicle are configured to communicate using the BLE and NFC communication protocols. The method includes pairing (S10) of the key fob and the vehicle for the NFC communication protocol. The method includes exchanging (S20), using the NFC communication protocol, a BLE key between the key fob and the vehicle. The method includes establishing (S30) BLE communication between the key fob and the vehicle using the exchanged BLE key.

[0023] The method improves the establishment of BLE communication between the remote key box and the vehicle.

[0024] Indeed, the method establishes BLE communication using existing NFC communication, which simplifies and facilitates the BLE pairing process securely. In particular, since the NFC protocol is only usable over short distances, the risk of identity theft is greatly reduced, and the exchange of the BLE key using the NFC protocol is therefore secure. Furthermore, by using a simple exchange of the BLE key via the NFC protocol, the method avoids the need for complex pairing algorithms. Exchanging the BLE key using the NFC protocol is thus much faster than executing a more complex algorithm such as the ECDH key exchange protocol.

[0025] Furthermore, the method improves the responsiveness of the functions to be performed, which are subsequently executed based on the established BLE communication. Indeed, the BLE key exchange is carried out prior to the use of the BLE protocol, and by accelerating this exchange, the method ultimately reduces the time elapsed between the launch of a function using the BLE protocol and its execution.

[0026] The vehicle and the key fob are configured to communicate using the NFC (Near Field Communication) and BLE (Bluetooth Low Energy) communication protocols. For each protocol, communication refers to the exchange, for example periodic, of signals between the key fob and the vehicle's system according to the communication protocol.

[0027] The BLE communication protocol is used by the vehicle and the key fob when the key fob is within a certain perimeter around the vehicle; that is, exchanges using this BLE protocol (i.e., BLE exchanges) can be carried out within this perimeter. This perimeter can include all positions located at a distance from the vehicle less than or equal to a predetermined distance (for example, 40 meters). On a 2D plane representing the ground, in the absence of obstacles, this perimeter can be represented by a circle centered on the vehicle and having a radius equal to the predetermined distance.

[0028] The NFC communication protocol can be used over shorter distances. For example, the NFC protocol can be used by the vehicle and the key fob when the key fob is inside the vehicle. The vehicle may include a mounting bracket inside the passenger compartment, for example, near the dashboard next to the driver. The NFC protocol can be used when the key fob is less than one meter from this mounting bracket (for example, a distance less than twenty centimeters from this support), for example when the key case is placed on this support located inside the vehicle.

[0029] The steps of the process can be performed by the key fob or by the vehicle. Alternatively, one or more steps can be performed by the key fob and one or more other steps by the vehicle. In some examples, certain steps can also be performed by both devices together (key fob and vehicle).

[0030] In some examples, the vehicle may have registered several key fobs. In this case, when a user carrying one of these key fobs enters the vehicle, the steps of the process can be executed for that key fob. For example, the process can begin after the user has placed the key fob on the holder. When another of the key fobs is placed on the holder (for example, after being placed by the same user or by another user), the process can be repeated for that other key fob.

[0031] The method includes S10 pairing of the key fob and the vehicle for the NFC communication protocol. S10 pairing can be performed once the user wearing the key fob is inside the vehicle. S10 pairing can be performed in any way. For example, S10 pairing may include the user placing the key fob on a designated holder inside the vehicle. S10 pairing may then include the vehicle detecting the key fob on the holder. S10 pairing may also include the vehicle identifying the key fob, for example, by the vehicle registering a key fob reference number.S10 pairing may involve the exchange of an NFC key (digital key) between the key fob and the vehicle, for example, subsequently stored on a secure element (NFC component) that each device contains. Once paired, NFC communication is established between the key fob and the vehicle, and the key fob and the vehicle can exchange signals according to the NFC protocol.

[0032] The method comprises the S20 exchange, using the NFC communication protocol, of a BLE key between the key fob and the vehicle. The S20 exchange is carried out according to the NFC communication protocol, which means that the S20 exchange is performed by an exchange of one or more signals between the key fob and the vehicle using the NFC communication protocol.

[0033] The S20 exchange can be carried out in any way. In examples, the S20 exchange may include the steps S21, S22, and S23 illustrated in [Fig. 2]. The S20 exchange may include an S21 transmission, via the vehicle, using the NFC communication protocol, from the BLE key to the key fob. For example, The key fob may include non-volatile memory, and the S21 transmission may include sending a command to register the BLE key to the non-volatile memory. The non-volatile memory may be included in a secure element of the key fob.

[0034] The S21 transmission may precede the generation of a BLE key and the recording of this BLE key, for example, in the vehicle's memory. The exchanged BLE key may be specific to the key fob. The BLE key may be an encryption key, i.e., a parameter used as input to a cryptographic operation employed during subsequent BLE exchanges. It may be symmetric and encoded in binary form (for example, using at least 128 bits).

[0035] The S21 transmission may include the transmission, by the vehicle, of an NFC signal containing the BLE key and / or the registration command. For example, the S21 transmission may include encoding the BLE key and / or the registration command in the NFC signal, and then transmitting this NFC signal.

[0036] The S20 exchange can then include a reception S22, by the key fob, of the sent BLE key. The S22 reception can include the key fob receiving the NFC signal emitted by the vehicle and reading the received NFC signal to decode the BLE key and / or the registration command included in that NFC signal. The S20 exchange can then include a registration S23, by the key fob, of the received BLE key. For example, the S20 exchange can include registering the received BLE key onto the key fob's non-volatile memory. The key fob can be configured to automatically register the received BLE key upon receiving such a signal containing such a BLE key. When the S21 transmission includes sending a BLE key registration command, the key fob can be configured to execute this command to register the BLE key onto the non-volatile memory.

[0037] In some examples, the S20 exchange of the BLE key may further include, prior to the transmission of the BLE key, encryption of the BLE key. In this case, the BLE key sent in step S21 and received in step S22 may be the encrypted BLE key. The stored BLE key may also be the encrypted BLE key. The S21 transmission may include sending a command to store this encrypted BLE key in non-volatile memory. For example, the key may be encrypted using encryption algorithms such as SCP03 combining AES-128 CBC and CMAC, or AES-128 CCM. Alternatively, the storage command sent may be encrypted. In this case, the S20 exchange of the BLE key may also include, before the S21 step, encryption of the BLE key registration command, and the S21 transmission may include transmission of the encrypted command. For example, the command may be encrypted using encryption algorithms such as SCP03 (combining AES-128 CBC and AES-128 CMAC) or AES-128 CCM.

[0038] In other examples, the S20 exchange can be carried out differently, and may not include some of these steps S21 to S23, and / or may include one or more additional steps, and / or one or more alternative steps to steps S21 to S23. For example, the BLE key can be generated by the key fob, and then sent by the key fob to the vehicle.

[0039] The method then includes establishing BLE communication (S30) between the key fob and the vehicle using the exchanged BLE key. In some examples, establishing BLE communication (S30) may include waking up the BLE component (S31). In these examples, the BLE component may be switched off before this step. For example, the BLE component may have previously switched off automatically after a period of inactivity. The BLE component may be woken up (S31) by the secure element of the key fob, for example, once the BLE key has been received. Alternatively, the BLE component may be woken up (S31) after the user has pressed one of the buttons on the key fob.

[0040] Once the BLE component is awakened, the S30 establishment of the BLE communication may include an S32 read of the BLE key previously exchanged during the NFC exchange by the awakened BLE component. For example, the S32 read may include sending the BLE key stored in non-volatile memory to the BLE component. In some examples, sending the BLE key may include the secure element sending a command to read the BLE key to the BLE component. As with sending the BLE key from the vehicle to the key fob, the BLE key may be encrypted, or the read command itself may be encrypted (for example, using the same algorithms as previously mentioned). The S32 read may then include storing the BLE key (for example, with its decryption) in the BLE component's memory.

[0041] After the S32 reading of the BLE key, the S30 establishment of the BLE communication may include an implementation S33 of one or more BLE exchanges between the key fob and the vehicle using the read BLE key. Each exchange between the two devices (key fob and vehicle) may include encryption of a BLE signal by the first of the two devices using the exchanged BLE key, transmission of the encrypted BLE signal by the first of the two devices to the second, reception of the BLE signal sent by the second of the two devices, and decoding of the BLE signal received by the second of the two devices using the exchanged BLE key.

[0042] In other examples, the S30 establishment of the BLE communication may be carried out differently, and may not include some or all of these steps S31 to S33, and / or may include one or more additional steps, and / or one or more alternative steps to steps S31 to S33. For example, the BLE component may already be awake at the time of execution of this step, and the S30 establishment of BLE communication may directly include the S32 read step of the exchanged BLE key.

[0043] In examples, once the BLE key is received by the BLE component, the process may include an S40 deletion of the BLE key stored in non-volatile memory. For example, the BLE key may be stored in a specific location in non-volatile memory, and the S40 deletion may include modifying the value stored in that specific location to overwrite the value of the BLE key (for example, with a null value). Deleting the BLE key improves the security of the established BLE communication, since it prevents subsequent malicious retrieval of the BLE key.

[0044] Examples will now be described with reference to Figures 3 to 6.

[0045] Figure 3 illustrates an example of a vehicle remote control key fob 110 The key fob 110 is configured to perform BLE and NFC communications with a vehicle 120. It is configured to communicate with the vehicle 120 according to the method shown in [Fig. 2]. The key fob 110 includes a UWB component 111 for performing UWB communication with the vehicle 120. The key fob 110 also includes a secure element 113 configured for performing NFC communication with the vehicle 110. The secure element 113 may include a digital key 131 used to perform this NFC communication with the vehicle 110. The key fob 110 also includes a BLE component 112, configured for performing BLE exchanges with the vehicle 120.

[0046] The vehicle 120 can be a car, a motorcycle, a truck, or more generally any land vehicle. The vehicle 120 includes a BLE component 122, configured to perform BLE exchanges with the key fob 110. The BLE component 122 may include a BLE transceiver. The BLE component 122 includes a memory on which the BLE key 132 exchanged with the key fob 110 is stored. The vehicle 120 includes a UWB component 121 for performing UWB communication with the key fob 110. The vehicle 120 includes a security element 123. The security element 123 may include a digital key 131 used to perform NFC communication with the vehicle. The vehicle 120 also includes a host component 124. The host component 124 is configured to generate the BLE key 132 exchanged between the vehicle 120 and the key box 110 and stored on the BLE component 122.These different vehicle components can be integrated together into a system.

[0047] The security element 123 of the vehicle 110 and the secure element 113 of the key fob 110 can be configured to perform NFC exchanges after S10 pairing of the two devices for this NFC communication protocol. Specifically, one of these NFC exchanges may include the BLE 132 key to facilitate the exchange of this BLE 132 key between the two devices. Once exchanged, the BLE 132 key can be read S32 by the BLE 112 component. The S32 reading of the BLE 132 key may include the BLE component storing the BLE 132 key in memory.

[0048] Figure 4 illustrates an example of implementing the method using a key fob 110 and a vehicle 120. The key fob 110 includes a BLE component 112 and a secure element 113. The vehicle 120 also includes a BLE component 122 and a secure element 123. The method includes S10 pairing of the key fob 110 and the vehicle 120 for the NFC communication protocol. S10 pairing is performed once the user wearing the key fob 110 is inside the vehicle 120, and the user places the key fob on a designated holder inside the vehicle. S10 pairing includes detection, by the vehicle 120, of the key fob 110 on said holder. S10 pairing is performed by the secure element 113 of the key case and the secure element 123 of the vehicle 120, from a digital key 131.Once paired, NFC communication is established between the key fob and the vehicle, and the key fob 110 and the vehicle 120 can exchange signals according to the NFC protocol.

[0049] The method then includes the exchange S20, using the NFC communication protocol, of a BLE key 132 between the key fob 110 and the vehicle 120. The S20 exchange is carried out according to the NFC communication protocol, meaning that the S20 exchange is performed by exchanging at least one signal between the key fob 110 and the vehicle 120 according to the NFC communication protocol. The S20 exchange includes the transmission, by the vehicle 120, using the NFC communication protocol, of a command to register the BLE key 132 to the key fob 120 in the non-volatile memory of the secure element 113. In some examples, the transmitted BLE key may be encrypted. In this case, the registration command may not be encrypted 133. Alternatively, the registration command sent may be encrypted 134. In this case, the BLE key of the registration command may not be encrypted.The S20 exchange then includes an execution, by the key box 110, of the received command 133, 134 resulting in the recording of the BLE key 132 on the non-volatile memory of the secure element 113.

[0050] The method then includes establishing BLE communication between the key fob and the vehicle using the exchanged BLE key. Establishing BLE communication includes waking up the BLE component 112 and then an S32 read of the exchanged BLE key 132 by the woken-up BLE component 112. The S32 read includes executing a command to read the stored BLE key 132 from the secure element 113. The same applies to sending the BLE key from the vehicle to the key case, the BLE key can be encrypted in the read command 135, or the read command itself can be encrypted 136. The S32 read can then include a record of the BLE key 132 (for example with its decryption) on a memory of the BLE component 112.

[0051] After the S32 reading of the BLE key, the S30 establishment of the BLE communication may include carrying out one or more BLE exchanges between the key box 110 and the vehicle 120 using the BLE key 132. Once the BLE key 132 has been received by the BLE component 112, the method may optionally also include deleting the BLE key 132 stored on the non-volatile memory of the secure element 113, in order to improve the security of the established BLE communication.

[0052] Figure 5 illustrates an example of a vehicle remote control key fob 110. The vehicle remote control key fob 110, or "identifier," may include a protective housing enclosing the key fob components. The protective housing may be made of plastic, metal, and / or rubberized plastic. The key fob 110 may include a logo, for example, made of metal. The logo may be located on the outer casing of the protective housing, and / or the logo may represent a manufacturer's brand. The key fob 110 may include, inside the protective housing, a metal insert that allows the vehicle 120 to be opened and / or started manually by inserting and manipulating the insert into a respective lock of the vehicle 120.

[0053] The key fob 110 includes a BLE component 112, configured to perform BLE communication with a vehicle, and comprising, for example, a microprocessor. The key fob 110 also includes an antenna 116 connected to the BLE component 112. The antenna 116 is configured to transmit or receive BLE signals. The microprocessor of the BLE component 112 may have in memory a computer program enabling BLE communication and performing various specific functions. The BLE component 112 may have in memory the BLE key 132 exchanged with the vehicle 120. The key fob 110 also includes a UWB component 111 for performing UWB communication with a vehicle.

[0054] Figure 6 illustrates an example of a vehicle 120 configured for carrying out the method. The vehicle 120 includes a vehicle system 125. The vehicle system 125 includes the BLE component 122, the UWB component 121, the security element 123, and the host component 124. The vehicle system 125 also includes at least one BLE / UWB anchor 126, each comprising a respective UWB component and a respective BLE component. Each BLE / UWB anchor 126 is configured to communicate using the UWB and BLE communication protocols with the key fob 110. The vehicle system 125 also includes the bracket located inside the vehicle on which the key fob 110 can be The holder includes an NFC component. NFC pairing can be performed once the 110 key fob is placed on this holder.

Claims

Demands

1. A method for communication between a vehicle remote key fob (110) and a vehicle (120), the key fob (110) and the vehicle (120) being configured to communicate using the BLE (Bluetooth Low Energy) and NFC (Near Field Communication) communication protocols, the method comprising: • pairing (S10) of the key fob (110) and the vehicle (120) according to the NFC communication protocol; • exchange (S20), using the NFC communication protocol, of a BLE key (132) between the key fob (110) and the vehicle (120); and • establishment (S30) of a BLE communication between the key fob (110) and the vehicle (120) using the exchanged BLE key (132).

2. A method according to claim 1, wherein the key case (110) includes a non-volatile memory (113), the exchange (S20) of the BLE key comprising: • a sending (S21), by the vehicle (120), and using the NFC communication protocol, of the BLE key (132) to the key case (110); • a reception (S22), by the key case (110), of the BLE key (132) sent; and • a recording (S23), by the key case (110), of the BLE key (132) received on the non-volatile memory (113).

3. A method according to claim 2, wherein the exchange (S20) of the BLE key (132) further comprises, prior to the sending (S21) of the BLE key (132), an encryption of the BLE key, the recorded BLE key being the encrypted BLE key.

4. A method according to claim 2, wherein the transmission (S21) comprises sending a command to record the BLE key to the non-volatile memory (113), the sent command being encrypted.

5. A method according to any one of claims 2 to 4, wherein the method further comprises: • a deletion (S40) of the BLE key (132) stored on 1 a non-volatile memory (113).

6. A method according to any one of the preceding claims, wherein the key case (110) includes a BLE component (112), the establishment (S30) of BLE communication comprising: • waking up (S31) the BLE component (112); • reading (S32) the BLE key (132) exchanged during step (S20), by the woken-up BLE component (112); and • an implementation (S33) of one or more BLE exchanges between the key case (110) and the vehicle (120) using the read BLE key (132).

7. A method according to any one of the preceding claims, wherein the vehicle (120) includes a support (127), the pairing (S10) of the key fob (110) and the vehicle (120) for the NFC communication protocol comprising: • a placement of the key fob (110) on the support (127) of the vehicle.

8. Computer program for key fob (110) and / or vehicle system (120) comprising instructions which, when the program is executed by a processor, cause the processor to implement the method according to any one of claims 1 to 7.

9. Computer-readable storage medium on which the computer program according to claim 8 is recorded.

10. Vehicle remote control key case (110) configured to perform BLE and NFC communications with a vehicle (120), the key case (110) being configured to communicate with the vehicle (120) according to the method of any one of claims 1 to 7.

Images