ID-BASED CONTROL UNIT-KEY FOB PAIRING

• US 20140025951A1
• Filed: 07/15/2013
• Published: 01/23/2014
• Est. Priority Date: 07/17/2012
• Status: Active Grant

• Current Assignee: Texas Instruments, Inc.
• Original Assignee: Texas Instruments, Inc.
• Inventors: HO, Jin-Meng, PEETERS, Eric
• Granted Patent: US 9,166,958 B2
• Time in Patent Office: Days
• US Class Current: 713/168
• CPC Class Codes: B60K 2360/23 using reflectors
• CPC Class Codes: B60K 2360/25 using filters
• CPC Class Codes: B60K 2360/27 using semi-transparent optical elements
• CPC Class Codes: B60K 2360/31 Virtual images
• CPC Class Codes: B60K 2360/334 Projection means
• CPC Class Codes: B60K 2360/349 Adjustment of brightness
• CPC Class Codes: B60K 2360/77 Instrument locations other than the dashboard
• CPC Class Codes: B60K 2370/1529 Head-up displays
• CPC Class Codes: B60K 2370/23 using reflectors
• CPC Class Codes: B60K 2370/25 using filters
• CPC Class Codes: B60K 2370/334 Projection means
• CPC Class Codes: B60K 35/00 Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
• CPC Class Codes: B60K 35/213 Virtual instruments
• CPC Class Codes: B60K 35/23 Head-up displays [HUD] optical aspects of head-up displays G02B27/01
• CPC Class Codes: B60K 35/60 Instruments characterised by their location or relative disposition in or on vehicles arrangements of lighting devices on dashboards B60Q3/10
• CPC Class Codes: B60K 37/02 Arrangement of instruments arrangement of lighting devices for dashboards B60Q3/10
• CPC Class Codes: B60R 2325/108 Encryption
• CPC Class Codes: B60R 25/24 using electronic identifiers containing a code not memorised by the user
• CPC Class Codes: G02B 2027/0118 comprising devices for improving the contrast of the display / brillance control visibility
• CPC Class Codes: G02B 26/0833 the reflecting element being a micromechanical device, e.g. a MEMS mirror, DMD G02B26/0825 takes precedence; micromechanical devices in general B81B
• CPC Class Codes: G02B 27/01 : Head-up displays
• CPC Class Codes: G02B 27/0101 : characterised by optical features G02B27/0172 takes precedence
• CPC Class Codes: G02B 5/30 : Polarising elements light-modulating devices with active elements G02F1/00
• CPC Class Codes: G06K 7/10227 : loading programming parameters or programs into the interrogator, e.g. for configuring the interrogator
• CPC Class Codes: G07C 2009/00769 : with data transmission performed by wireless means
• CPC Class Codes: G07C 9/00309 : operated with bidirectional data transmission between data carrier and locks
• CPC Class Codes: H01S 5/4012 : Beam combining, e.g. by the use of fibres, gratings, polarisers, prisms
• CPC Class Codes: H01S 5/4093 : Red, green and blue [RGB] generated directly by laser action or by a combination of laser action with nonlinear frequency conversion
• CPC Class Codes: H04L 2209/24 : Key scheduling, i.e. generating round keys or sub-keys for block encryption
• CPC Class Codes: H04L 2209/80 : Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 2209/805 : Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• CPC Class Codes: H04L 2209/84 : Vehicles
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/061 : for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 9/0822 : using key encryption key
• CPC Class Codes: H04L 9/0838 : Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these network architectures or network communication protocols for key exchange in a packet data network H04L63/061
• CPC Class Codes: H04L 9/0844 : with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys
• CPC Class Codes: H04L 9/0861 : Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/0897 : involving additional devices, e.g. trusted platform module [TPM], smartcard or USB
• CPC Class Codes: H04L 9/14 : using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/3013 : involving the discrete logarithm problem, e.g. ElGamal or Diffie-Hellman systems
• CPC Class Codes: H04L 9/3066 : involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
• CPC Class Codes: H04L 9/3263 : involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/3268 : using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
• CPC Class Codes: H04L 9/3271 : using challenge-response
• CPC Class Codes: H04N 9/3129 : scanning a light beam on the display screen scanning a light beam on a screen in displays other than projection devices G09G3/02; scanning systems in general G02B26/10; projectors using laser light sources in general H04N9/3161
• CPC Class Codes: H04N 9/3155 : for controlling the light source light source control per se H05B35/00 – H05B47/00; control of an illumination source for displays in general G09G3/3406
• CPC Class Codes: H04N 9/3167 : for polarizing the light beam polarizing optical systems per se G02B27/28
• CPC Class Codes: H04W 12/04 : Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/50 : Secure pairing of devices
• CPC Class Codes: H05B 47/11 : by determining the brightness or colour temperature of ambient light
• CPC Class Codes: H05B 47/14 : by determining electrical parameters of the light source
• CPC Class Codes: Y02B 20/40 : Control techniques providing energy savings, e.g. smart controller or presence detection

Abstract

A key fob-control unit pairing device that includes a transceiver to transmit and receive signals, a memory to store a key fob identification (KFID) and a control unit identification (CUID), and a processor coupled to said transceiver and memory. The processor is to authenticate the key fob using identification (ID) authenticated key agreement protocol based on the KFID, and to transmit an encrypted CUID to the key fob.

Claims

1. A key fob-control unit pairing device, comprising:

a transceiver to transmit and receive signals;

a memory to store a key fob identification (KFID) and a control unit identification (CUID); and

a processor coupled to said transceiver and memory and to;

authenticate the key fob using an identification (ID) authenticated key agreement protocol based on the KFID; and

transmit an encrypted CUID to the key fob.

2. The device of claim 1, wherein the ID authenticated key agreement protocol performed by the processor also generates a common secret encryption key shared between the key fob and the pairing device.

3. The device of claim 2, wherein the processor generates the encrypted CUID with the common secret encryption key.

4. The device of claim 1, wherein the ID authenticated key agreement protocol is based on elliptical curve cryptography.

5. The device of claim 1, wherein the ID authenticated key agreement protocol is based on Diffie-Hellman key agreement protocols.

6. The device of claim 1, wherein the KFID and the CUID are eight character hexadecimal words.

7. The device of claim 1, wherein the KFID is used as a password for authentication.

8. The device of claim 1, wherein the KFID is received by the processor via the transceiver from the key fob.

9. A key fob, comprising:

a transceiver to receive and send signals;

a memory to store a key fob identification (KFID); and

a processor coupled to said transceiver and memory to;

execute, along with a pairing device, an identification (ID) authenticated key agreement protocol based on the KFID to authenticate a pairing device and to generate a common secret encryption key known only by the processor and the pairing device;

receive, from the pairing device, a control unit identification (CUID) encrypted by the pairing device with the common secret encryption key;

execute along with the control unit associated with the CUID an ID authenticated key agreement protocol based on the CUID to authenticate the control unit and to generate a second common secret encryption key known only by the processor and the control unit; and

receive, from the control unit, an operation key encrypted by the control unit with the second common secret encryption key.

10. The key fob of claim 9, wherein ID authenticated key agreement protocol is based on elliptic curve cryptography.

11. The key fob of claim 9, wherein the KFID and the CUID authenticated key agreement protocol is based on Diffie-Hellman key agreement protocols.

12. The key fob of claim 9, wherein the processor is to decrypt the operation key with the second common secret encryption key.

13. The key fob of claim 9, wherein the KFID and the CUID are eight character hexadecimal words.

14. The key fob of claim 9, wherein the encrypted operation key is received wirelessly.

15. The key fob of claim 9, wherein processor decrypts the encrypted CUID using the common secret encryption key.

16. The key fob of claim 9, wherein the processor decrypts the operation key using the second common secret encryption key.

17. A method for pairing a key fob with a vehicle, comprising:

executing, by a pairing device and a key fob, an ID authenticated key agreement protocol based on a KFID to authenticate one another and to generate an encryption key DHKey1;

encrypting, by the pairing device, a control unit identification (CUID) with DHKey1;

transmitting, by the pairing device, the encrypted CUID to a key fob;

executing, by the key fob and a control unit, an ID authenticated key agreement protocol based on the CUID to authenticate one another and to generate an encryption key DHKey2;

encrypting, by the control unit, an operation key with DHKey2; and

transmitting, by the control unit, the encrypted operation key to the key fob.

18. The method of claim 17, further comprising:

inserting the CUID into a storage device of the control unit; and

transmitting the CUID to a vehicle dealer.

19. The method of claim 17, further comprising:

inserting a unique ID into a key fob (KFID).

20. The method of claim 17, further comprising reading the KFID of the key fob.