# US 2021/0345110 A1 · System and Method for Authenticating a Connection Between a User Device and a Vehicle

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0345110 A1
- Document ID: US20210345110A1
- Status: Published application
- Kind: A1
- Application number: 17/346,823
- Filed: 2021-06-14
- Published: 2021-11-04
- Earliest claimed: 2019-04-16
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Girish Shivalingappa Revadigar; Zhuo Wei; Tieyan Li; Yanjiang Yang; Hai Yu
- Web page: https://patentgrep.com/patent/US20210345110A1

## CPC

- B60R 25/24: using electronic identifiers containing a code not memorised by the user
- H04W 12/069: using certificates or pre-shared keys
- H04B 17/318: Received signal strength
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W 12/03: Protecting confidentiality, e.g. by encryption
- H04W 12/0431: Key distribution or pre-distribution; Key agreement
- H04W 12/122: Counter-measures against attacks; Protection against rogue devices
- H04W 12/50: Secure pairing of devices
- H04W 12/79: Radio fingerprint
- B60R 2325/101: Bluetooth®
- B60R 2325/108: Encryption
- B60R: VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04B: TRANSMISSION
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for authenticating a connection between a user device and a vehicle includes sending, by the vehicle, a first wireless signal through a connection channel, receiving, by the vehicle, a second wireless signal through the connection channel, and acquiring, by the vehicle, a second signal strength sequence from second N continuous signal strength characteristics (PFVeh) of the second wireless signal, receiving, by the user device from the vehicle, the first wireless signal, acquiring a first signal strength sequence from first N continuous signal strength characteristics (PFUDev) of the first wireless signal, and communicating, by the user device, the first signal strength sequence to the vehicle.

## Claims

### Claim 1

A user device comprising:
a memory configured to store programming instructions; and
a processor coupled to the memory, wherein the programming instructions cause the processor to be configured to:
send, to a vehicle, a second wireless signal through a connection channel;
receive, from the vehicle, a first wireless signal through the connection channel;
acquire a first signal strength sequence from first N continuous signal strength characteristics (PFUDev) of the first wireless signal; and
communicate the first signal strength sequence to the vehicle.

### Claim 2 (depends on 1)

The user device of claim 1, wherein the first signal strength sequence comprises the PFUDev.

### Claim 3 (depends on 2)

The user device of claim 2, wherein the first signal strength sequence further comprises a user string (SUDev) and a correction data C.

### Claim 4 (depends on 3)

The user device of claim 3, wherein the programming instructions further cause the processor to be configured to:
filter the PFUDev using a low-pass filter to obtain a filtered PFUDev; and
generate the SUDev and the correction data C by inputting the filtered PFUDev to a generate (gen) function of a fuzzy extractor mechanism.

### Claim 5 (depends on 1)

The user device of claim 1, wherein before acquiring the first signal strength sequence, the programming instructions further cause the processor to be configured to communicate, to the vehicle, an initiation instruction for authenticating the user device.

### Claim 6 (depends on 5)

The user device of claim 5, wherein the initiation instruction comprises:
an initiation message authentication code (MAC) (MIni) instructing the vehicle to authenticate the initiation instruction based on a BLUETOOTH user device (BUD) key (KBTUDev) that is shared between the user device and the vehicle; or
a sign (S) instructing the vehicle to authenticate the initiation instruction based on a public-key infrastructure (PKI)-private key associated with the user device (KeyPriv_UDev) that is shared between the user device and the vehicle.

### Claim 7 (depends on 6)

The user device of claim 6, wherein the initiation instruction is validated, and wherein before acquiring the first signal strength sequence, the programming instructions further cause the processor to be configured to:
receive an acknowledgement instruction from the vehicle, wherein the acknowledgement instruction is based on an encrypted acknowledgement message and an acknowledgement MAC (MAck), wherein the encrypted acknowledgement message comprises a nonce n, a random string r, and an acknowledgement command, wherein the encrypted acknowledgement message is encrypted using a corresponding BUD key (KBTUDev), and wherein the MAck is based on the encrypted acknowledgement message and the KBTUDev;
validate the acknowledgement instruction using the KBTUDev.

### Claim 8 (depends on 6)

The user device of claim 6, wherein the programming instructions further cause the processor to be configured to:
detect a BLUETOOTH Low Energy (BLE) beacon from the vehicle; and
establish, in response to the detecting, a BLUETOOTH pairing between the user device and the vehicle using a BLUETOOTH connection key (KeyBTcon), wherein the KeyBTcon is shared between the user device and the vehicle.

### Claim 9

A vehicle comprising:
a memory configured to store programming instructions; and
a processor coupled to the memory, wherein the programming instructions cause the processor to be configured to:
send, to a user device, a first wireless signal through a connection channel;
receive, from the user device, a second wireless signal through the connection channel;
acquire a second signal strength sequence from second N continuous signal strength characteristics (PFVeh) of the second wireless signal;
receive, from the user device in response to sending the first wireless signal, a first signal strength sequence from first N continuous signal strength characteristics (PFUDev) of the first wireless signal; and
authenticate a connection between the user device and the vehicle based on the first signal strength sequence and the second signal strength sequence.

### Claim 10 (depends on 9)

The vehicle of claim 9, wherein the first signal strength sequence comprises the PFUDev.

### Claim 11 (depends on 10)

The vehicle of claim 10, wherein the first signal strength sequence further comprises a user string (SUDev) and a correction data C, wherein the SUDev and the correction data C are based on a filtered PFUDev.

### Claim 12 (depends on 11)

The vehicle of claim 11, wherein the programming instructions further cause the processor to be configured to:
extract the correction data C from the first signal strength sequence;
filter the correction data C using a low pass filter to obtain a filtered correction data C;
filter the PFVeh using the low pass filter to obtain a filtered PFVeh;
generate a vehicle string (SVeh) by inputting the filtered PFVeh and the filtered correction data C to a reproduce (rep) function of a fuzzy extractor mechanism; and
authenticate, based on the SUDev and the SVeh, the connection.

### Claim 13 (depends on 12)

The vehicle of claim 12, wherein the programming instructions further cause the processor to be configured to identify that the connection is valid based on characters at M corresponding positions in the SUDev and the SVeh being the same, and wherein the M is a positive integer greater than or equal to a preset threshold.

### Claim 14 (depends on 9)

The vehicle of claim 9, wherein before acquiring the second signal strength sequence, the programming instructions further cause the processor to be configured to:
receive an initiation instruction from the user device; and
authenticate the user device based on the initiation instruction.

### Claim 15 (depends on 14)

The vehicle of claim 14, wherein the initiation instruction comprises:
an initiation message authentication code (MAC) (MIni) indicating an instruction for the vehicle to authenticate the initiation instruction based on a BLUETOOTH user device (BUD) key (KBTUDev) that is shared between the user device and the vehicle; or
a sign (S) indicating an instruction for the vehicle to authenticate the initiation instruction based on a public-key infrastructure (PKI)-private key associated with the user device (KeyPriv_UDeva) and the KBTUDev and a PKI-public key associated with the vehicle (KeyPub_Veh),
wherein the KeyPriv_UDev and the KeyPub_Veh are shared between the user device and the vehicle.

### Claim 16 (depends on 9)

The vehicle of claim 9, wherein before receiving the second wireless signal, the programming instructions cause the processor to be configured to:
emit a BLUETOOTH Low Energy (BLE) beacon; and
establish a BLUETOOTH pairing between the user device and the vehicle using a BLUETOOTH connection key (KeyBTcon) based on whether the BLE beacon is detected, wherein the KeyBTcon is shared between the user device and the vehicle.

### Claim 17

A system comprising:
a vehicle configured to send a first wireless signal through a connection channel; and
a user device coupled to the vehicle and configured to:
receive, from the vehicle, the first wireless signal through the connection channel;
send, to the vehicle, a second wireless signal through the connection channel;
acquire a first signal strength sequence from first N continuous signal strength characteristics (PFUDev) of the first wireless signal; and
communicate the first signal strength sequence to the vehicle,
wherein the vehicle is further configured to:
receive, from the user device, the second wireless signal through the connection channel;
acquire a second signal strength sequence from second N continuous signal strength characteristics (PFVeh) of the second wireless signal; and
receive, from the user device, the first signal strength sequence,
wherein the first signal strength sequence and the second signal strength sequence are for authenticating a connection between the user device and the vehicle.

### Claim 18 (depends on 17)

The system of claim 17, wherein the first signal strength sequence comprises the PFUDev.

### Claim 19 (depends on 18)

The system of claim 18, wherein the first signal strength sequence further comprises a user string (SUDev) and a correction data C.

### Claim 20 (depends on 19)

The system of claim 19, wherein the user device is further configured to:
filter the PFUDev by a low pass filter to obtain a filtered PFUDev; and
generate the SUDev and the correction data C by inputting the filtered PFUDev to a generate (gen) function of a fuzzy extractor mechanism.

### Claim 21 (depends on 17)

The system of claim 17, wherein before acquiring the first signal strength sequence, the user device is further configured to communicate, to the vehicle, an initiation instruction instructing to authenticate the user device.

### Claim 22 (depends on 21)

The system of claim 21, wherein the initiation instruction comprises:
an initiation message authentication code (MAC) (MIni) instructing the vehicle to authenticate the initiation instruction based on a BLUETOOTH user device (BUD) key (KBTUDev) that is shared between the user device and the vehicle; or
a sign (S) instructing the vehicle to authenticate the initiation instruction based on a public-key infrastructure (PKI)-private key associated with the user device (KeyPriv_UDev) that is shared between the user device and the vehicle.

### Claim 23 (depends on 21)

The system of claim 21, wherein the vehicle is further configured to:
identify that the initiation instruction is valid; and
communicate, in response to the identifying, an acknowledgement instruction to the user device, wherein the acknowledgement instruction is based on an encrypted acknowledgement message and an acknowledgement MAC (MAck), wherein the encrypted acknowledgement message comprises a nonce n, a random string r, and an acknowledgement command, wherein the encrypted acknowledgement message is encrypted using a corresponding BLUETOOTH user device (BUD) key (KBTUDev), and wherein the MAck is based on the encrypted acknowledgement message and the KBTUDev, and
wherein the user device is further configured to validate the acknowledgement instruction using the KBTUDev.

### Claim 24 (depends on 21)

The system of claim 21, wherein the vehicle is further configured to emit a BLUETOOTH Low Energy (BLE) beacon, and wherein the user device is further configured to:
detect the BLE beacon; and
establish, in response to the detecting, a BLUETOOTH pairing between the user device and the vehicle using a BLUETOOTH connection key (KeyBTcon), wherein the KeyBTcon is shared between the user device and the vehicle.
