Authentication manager

Patent metadata

Field	Value
Publication number	US-10974696-B2
Application number	US-201816048501-A
Country	US
Kind code	B2
Filing date	Jul 30, 2018
Priority date	Jul 30, 2018
Publication date	Apr 13, 2021
Grant date	Apr 13, 2021

Abstract

A vehicle includes a transceiver and a processor. The processor is programmed to generate a user identifier responsive to receipt of authentication rights to the vehicle via the transceiver, and responsive to occurrence of a scheduled time and location specified by the authentication rights, activate a phone key of the authentication rights corresponding to the user identifier with a key manager and activate a passcode of the authentication rights corresponding to the user identifier with a passcode manager.

First claim

What is claimed is:

1. A vehicle comprising:
a transceiver; and
a processor programmed to
receive, to the vehicle via the transceiver, authentication rights as a download of a schedule of uses of the vehicle for a day, the schedule of uses including a plurality of uses for the day,
generate one or more user identifiers responsive to receipt of the authentication rights to the vehicle, and
responsive to occurrence of a scheduled time and location specified by the schedule of uses of the authentication rights, activate a phone key of the authentication rights corresponding to one of the user identifiers with a key manager and activate a passcode of the authentication rights corresponding to the one of the user identifiers with a passcode manager, such that the phone key and passcode can be used for authentication once activated but not before being activated.

2. The vehicle of claim 1 , wherein the passcode is a one-time use key.

3. The vehicle of claim 1 , wherein the processor is further programmed to delete the authentication rights from the vehicle responsive to completion of the access to the vehicle.

4. The vehicle of claim 3 , wherein the processor is further programmed to determine completion of the access to the vehicle responsive to one or more of expiration of a period of time specified by the trip information, or movement of the vehicle to a destination location specified by the trip information.

5. The vehicle of claim 1 , wherein the passcode manager includes a keypad accessible on an exterior of the vehicle and configured to receive the passcode via user input to the keypad.

6. The vehicle of claim 1 , wherein the passcode manager includes a touchscreen accessible on an exterior of the vehicle and configured to receive the passcode via user input to the touchscreen.

7. The system of claim 1 , wherein the processor is further programmed to receive the schedule of uses for the day at a beginning of the day.

8. The system of claim 1 , wherein the processor is further programmed to:
responsive to occurrence of a second scheduled time and second location specified by the schedule of uses of the authentication rights, activate a second phone key of the authentication rights corresponding to a second one of the user identifiers with the key manager and activate a second passcode of the authentication rights corresponding to the second one of the user identifiers with the passcode manager, such that the second phone key and second passcode can be used for authentication once activated but not before being activated.

9. A method comprising:
responsive to receipt, by a vehicle from a server, of a phone key, a passcode, and a schedule of uses of the vehicle for a day, the schedule of uses including a plurality of uses for the day, sending the phone key in an inactive state to a vehicle key manager and the passcode in the inactive state to a vehicle passcode manager, such that, when in the inactive state, the phone key and passcode cannot be used for authentication; and
responsive to occurrence of a scheduled time and location at the vehicle as indicated by the schedule of uses, activating the phone key with the key manager and the passcode with the passcode manager, such that once activated, the phone key and passcode can be used for authentication.

10. The method of claim 9 , further comprising:
generating a user identifier corresponding to the phone key and passcode; and
activating the phone key with the key manager and the passcode with the passcode manager by indicating the user identifier to the key manager and the passcode manager.

11. The method of claim 9 , wherein the passcode manager includes a keypad, and further comprising:
receiving the passcode via user input to the keypad; and
validating the passcode based on the activating having occurred.

12. The method of claim 9 , wherein the passcode manager includes a touchscreen, and further comprising receiving the passcode via user input to the touchscreen.

13. The method of claim 9 , further comprising deleting the authentication rights from the vehicle responsive to completion of the access to the vehicle.

14. The method of claim 13 , further comprising determining completion of the access to the vehicle responsive to one or more of expiration of a period of time specified by the trip information, or movement of the vehicle to a destination location specified by the trip information.

15. A non-transitory computer-readable medium comprising instructions that, when executed by a processor of a vehicle, cause the vehicle to:
responsive to receipt, by a vehicle from a server, of a phone key, a passcode, and a schedule of uses of the vehicle for a day, the schedule of uses including a plurality of uses for the day, send the phone key in an inactive state to a vehicle key manager and the passcode in the inactive state to a vehicle passcode manager, such that, when in the inactive state, the phone key and passcode cannot be used for authentication; and
responsive to occurrence of a scheduled time and location at the vehicle as indicated by the schedule of uses, activate the phone key with the key manager and the passcode with the passcode manager, such that once activated, the phone key and passcode can be used for authentication.

16. The medium of claim 15 , further comprising:
generating a user identifier corresponding to the phone key and passcode; and
activating the phone key with the key manager and the passcode with the passcode manager by indicating the user identifier to the key manager and the passcode manager.

17. The medium of claim 15 , wherein the passcode manager includes a keypad, and further comprising receiving the passcode via user input to the keypad.

18. The medium of claim 15 , wherein the passcode manager includes a touchscreen, and further comprising receiving the passcode via user input to the touchscreen.

19. The medium of claim 15 , further comprising deleting the authentication rights from the vehicle responsive to completion of the access to the vehicle.

20. The medium of claim 19 , further comprising determining completion of the access to the vehicle responsive to one or more of expiration of a period of time specified by the trip information, or movement of the vehicle to a destination location specified by the trip information.

21. The medium of claim 15 , further comprising deactivating the authentication rights from the vehicle responsive to completion of the access to the vehicle.

Assignees

• Ford Global Tech Llc

Inventors

• Mcnabb David
• Sharma Shubham

Classifications

• H04W12/06

  Authentication · CPC title

• G06Q30/0645

  Rental transactions; Leasing transactions · CPC title

• G07C9/00563

  using personal physical data of the operator, e.g. finger prints, retinal images, voicepatterns · CPC title

• H04W4/44

  for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H] · CPC title

• G06F21/46 Primary

  by designing passwords or checking the strength of passwords · CPC title