Secure smartphone based access and start authorization system for vehicles
A Bluetooth enabled Smartphone may be used for both access control and start authorization in a secure and safe way, and embodiments are backward-compatible with conventional vehicle access and start systems. A smart phone acts as an intermediary authorization device to a code generator which effectively resembles a car key that is installed in a vehicle. A Bluetooth transceiver and the code generator—and, optionally, for the retrofit solution, an RF/LF transceiver—are added to the vehicle. The Bluetooth transceiver communicates with the smart phone. The code generator communicates with electronic control units in the vehicle that control access, immobilization, and engine start. The communication may happen via a wired connection or, in the case of the retrofit solution, via an RF/LF transceiver that mimics an additional car key programmed to the vehicle.
1. An apparatus comprising:
a transceiver-and-code-generator module that is configured to be installed in a vehicle having one or more vehicle electronic control units, wherein the transceiver-and-code-generator module includes:
a Bluetooth transceiver configured to establish a Bluetooth connection with a smartphone;
a code generator including a code-generator memory, the code generator is configured to:
communicate a secret key to the one or more vehicle electronic control units while learning the code generator to the vehicle,
subsequently use the secret key to encrypt communications between the code generator and the vehicle,
encrypt the secret key with a random number AUTH,
store the encrypted secret key in the code-generator memory, and
not store in the code-generator memory the secret key in unencrypted form thereby preventing unauthorized access, via the code generator, to the secret key by a person who has access to the vehicle.
2. The apparatus of claim 1 , wherein the code generator stores either an encryption key used to encrypt and decrypt the secret key or the secret key in encrypted form.
3. The apparatus of claim 1 , wherein the smartphone is enabled via a backend service that distributes, in a secure manner using public/private key infrastructure, either a unique number used for encrypting the secret key or the secret key in encrypted form.
4. The apparatus of claim 1 , wherein the code generator is configured to maintain contact with the smartphone via a periodic polling scheme.
5. The apparatus of claim 4 , wherein the code generator is configured to use received signal strength indicator criteria to limit the range of the Bluetooth connection.
6. The apparatus of claim 5 , wherein the code generator is configured to, upon interruption of the Bluetooth connection, erase from memory any stored instances of the secret key in decrypted form to prevent unauthorized access to the secret key.
7. The apparatus of claim 1 , wherein the code generator is configured to generate the random number AUTH.
8. The apparatus of claim 1 , wherein the code generator is configured to encrypt the random number AUTH and send the random number AUTH in encrypted form to the backend service.
9. The apparatus of claim 8 , wherein the code generator is configured to delete the random number AUTH from code-generator memory.
10. The apparatus of claim 1 , wherein the code generator is configured to generate and store in local memory a random number AUTH.
11. The apparatus of claim 10 , wherein the code generator is configured to encrypt the secret key with both the random number AUTH and with PUB_cloud and to send the encrypted secret key to the cloud.
12. The apparatus of claim 11 , wherein the secret key is additionally encrypted with a hashed user PIN.
13. The apparatus of claim 11 , wherein the cloud is configured to store the encrypted secret key and to associate the encrypted secret key with a corresponding vehicle identification number.
14. The apparatus of claim 13 , wherein the code generator is configured to delete the secret key from local memory.