IP Library Granted Patent US 10,140,468
Granted Patent B2
US 10,140,468 · App. 15/874,549 · Granted Nov 27, 2018

Secure start system for an autonomous vehicle

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,140,468
App. No.
15/874,549
Granted
Nov 27, 2018
Kind
B2
Abstract

A secure start system for an autonomous vehicle (AV) can transmit credentials to an authentication system based on detecting startup of the autonomous vehicle. When the credentials are authenticated the system can receive a tunnel key from the authentication system, and establish, using the tunnel key, a private communications session with a backend vault of the authentication system. The system may then retrieve a verification key and an autonomous key from the backend vault, and verify, using the verification key, that the file system was cryptographically signed by the authentication system, and decrypt the file system using the autonomous key to enable the autonomous mode.

Claims (66)

1. A secure start system for an autonomous vehicle, the secure start system comprising:

a communications router;

a compute stack storing a cryptographically signed and encrypted file system, and comprising a plurality of drives to execute the file system to enable an autonomous mode of the autonomous vehicle; and

wherein the compute stack comprises a master node including one or more memory resources that execute secure start instructions, causing the secure start system to:

based on detecting startup of the autonomous vehicle, transmit credentials to a backend authentication system via the communications router;

receive, when the credentials are authenticated, a tunnel key from the backend authentication system;

establish, using the tunnel key, a private communications session with a backend vault of the backend authentication system;

retrieve a verification key and an autonomous key from the backend vault;

verify, using the verification key, that the file system was cryptographically signed by the backend authentication system; and

decrypt the file system using the autonomous key to enable the autonomous mode.

2. The secure start system of claim 1 , wherein the executed instructions further cause the secure start system to:

retrieve, in response to detecting startup of the autonomous vehicle, a basic key from write protected memory of the secure start system; and

unlock, using the basic key, a basic mode of an autonomous vehicle operating system (AVOS), the basic mode enabling network communications with the backend authentication system.

3. The secure start system of claim 1 , wherein the executed instructions further cause the secure start system to:

receive the credentials from a user of the autonomous vehicle.

4. The secure start system of claim 3 , wherein the credentials are received via one of a mobile computing device executing a designated application for operating the autonomous vehicle or an input interface of the autonomous vehicle.

5. The secure start system of claim 1 , wherein the tunnel key comprises an Internet Protocol Security (IPsec) tunnel key, and wherein the private communications session comprises an IPsec tunnel to the backend vault to retrieve the verification key and the autonomous key.

6. The secure start system of claim 1 , wherein the executed instructions cause the secure start system to transmit the credentials to a demilitarized zone of the backend authentication system to receive the tunnel key.

7. The secure start system of claim 1 , wherein the executed instructions further cause the secure start system to:

transmit the credentials to a communications gate of the backend vault; and

receive, when the credentials are authenticated by the communications gate, a time-limited token to access the backend vault;

wherein the executed instructions cause the secure start system to retrieve the verification key and the autonomous key from the backend vault using the time-limited token.

8. An autonomous vehicle comprising:

a sensor system to dynamically generate sensor data indicating a situational environment of the autonomous vehicle;

an acceleration, braking, and steering system;

a compute stack storing a cryptographically signed and encrypted file system, and comprising a plurality of drives to execute the file system to operate the acceleration, braking, and steering system in an autonomous mode; and

a secure start system connected to the compute stack, the secure start system comprising:

a communications router;

one or more processors; and

one or more memory resources storing secure start instructions that, when executed by the one or more processors, cause the secure start system to:

based on detecting startup of the autonomous vehicle, transmit credentials to a backend authentication system via the communications router;

receive, when the credentials are authenticated, a tunnel key from the backend authentication system;

establish, using the tunnel key, a private communications session with a backend vault of the backend authentication system;

retrieve a verification key and an autonomous key from the backend vault;

verify, using the verification key, that the file system was cryptographically signed by the backend authentication system; and

decrypt the file system using the autonomous key to enable the autonomous mode.

9. The autonomous vehicle of claim 8 , wherein the executed instructions further cause the secure start system to:

retrieve, in response to detecting startup of the autonomous vehicle, a basic key from write protected memory of the secure start system; and

unlock, using the basic key, a basic mode of an autonomous vehicle operating system (AVOS), the basic mode enabling network communications with the backend authentication system.

10. The autonomous vehicle of claim 8 , wherein the executed instructions further cause the secure start system to:

receive the credentials from a user of the autonomous vehicle.

11. The autonomous vehicle of claim 10 , wherein the credentials are received via one of a mobile computing device executing a designated application for operating the autonomous vehicle or an input interface of the autonomous vehicle.

12. The autonomous vehicle of claim 8 , wherein the tunnel key comprises an Internet Protocol Security (IPsec) tunnel key, and wherein the private communications session comprises an IPsec tunnel to the backend vault to retrieve the verification key and the autonomous key.

13. The autonomous vehicle of claim 8 , wherein the executed instructions cause the secure start system to transmit the credentials to a demilitarized zone of the backend authentication system to receive the tunnel key.

14. The autonomous vehicle of claim 8 , wherein the executed instructions further cause the secure start system to:

transmit the credentials to a communications gate of the backend vault; and

receive, when the credentials are authenticated by the communications gate, a time-limited token to access the backend vault;

wherein the executed instructions cause the secure start system to retrieve the verification key and the autonomous key from the backend vault using the time-limited token.

15. A non-transitory computer readable medium storing instructions that when executed by one or more processors of a secure start system of an autonomous vehicle (AV), cause the secure start system to:

based on detecting startup of the autonomous vehicle, transmit credentials to a backend authentication system using a communications router;

receive, when the credentials are authenticated, a tunnel key from the backend authentication system;

establish, using the tunnel key, a private communications session with a backend vault of the backend authentication system;

retrieve a verification key and an autonomous key from the backend vault;

verify, using the verification key, that an encrypted file system of the AV was cryptographically signed by the backend authentication system; and

decrypt the file system using the autonomous key to enable an autonomous mode of the autonomous vehicle.

16. The non-transitory computer readable medium of claim 15 , wherein the executed instructions further cause the secure start system to:

retrieve, in response to detecting startup of the autonomous vehicle, a basic key from write protected memory of the secure start system; and

unlock, using the basic key, a basic mode of an autonomous vehicle operating system (AVOS), the basic mode enabling network communications with the backend authentication system.

17. The non-transitory computer readable medium of claim 15 , wherein the executed instructions further cause the secure start system to:

receive the credentials from a user of the autonomous vehicle.

18. The non-transitory computer readable medium of claim 17 , wherein the credentials are received via one of a mobile computing device executing a designated application for operating the autonomous vehicle or an input interface of the autonomous vehicle.

19. The non-transitory computer readable medium of claim 15 , wherein the tunnel key comprises an Internet Protocol Security (IPsec) tunnel key, and wherein the private communications session comprises an IPsec tunnel to the backend vault to retrieve the verification key and the autonomous key.

20. The non-transitory computer readable medium of claim 19 , wherein the executed instructions further cause the secure start system to:

transmit the credentials to a communications gate of the backend vault; and

receive, when the credentials are authenticated by the communications gate, a time-limited token to access the backend vault;

wherein the executed instructions cause the secure start system to retrieve the verification key and the autonomous key from the backend vault using the time-limited token.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 14, 2024
From: UATC, LLC
To: AURORA OPERATIONS, INC.
Reel/Frame 067733/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 27, 2020
From: VALASEK, CHRISTOPHER; MILLER, CHARLES
To: UBER TECHNOLOGIES, INC.
Reel/Frame 051631/0080 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NATURE OF CONVEYANCE FROM CHANGE OF NAME TO ASSIGNMENT PREVIOUSLY RECORDED ON REEL 050353 FRAME 0884. ASSIGNOR(S) HEREBY CONFIRMS THE CORRECT CONVEYANCE SHOULD BE ASSIGNMENT. Recorded Nov 27, 2019
From: UBER TECHNOLOGIES, INC.
To: UATC, LLC
Reel/Frame 051145/0001 →
CHANGE OF NAME Recorded Sep 12, 2019
From: UBER TECHNOLOGIES, INC.
To: UATC, LLC
Reel/Frame 050353/0884 →