IP Library Granted Patent US 10,501,091
Granted Patent B2
US 10,501,091 · App. 15/602,234 · Granted Dec 10, 2019

Software version and mode switching for autonomous vehicles

Inventors: Dima Kislovskiy (Pittsburgh, PA); David McAllister Bradley (Pittsburgh, PA)
Assignee: Uber Technologies, Inc.
B60W50/0098B60W50/0205H04L67/34H04W4/021H04W4/025H04W4/44B60W2050/0072B60W2050/0077B60W2050/022B60W2050/0215B60W2550/12B60W2550/14B60W2550/20
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,501,091
App. No.
15/602,234
Granted
Dec 10, 2019
Kind
B2
Abstract

An on-trip monitoring system for an on-demand transportation service can receive log data from autonomous vehicles operating throughout a given region. Based on a set of triggering conditions, the on-trip monitoring system can transmit switching commands to cause the AVs to switch between software versions and/or operative modes.

Claims (38)

1. An on-trip monitoring system for autonomous vehicles (AVs) comprising:

one or more processors; and

one or more memory resources storing instructions that, when executed by the one or more processors, cause the on-trip monitoring system to:

monitor AVs operating throughout a given region by receiving AV data from each of the AVs;

based on a triggering condition of an AV operating within the given region, transmit a software switching command to the AV, the software switching command instructing the AV to terminate execution of a current software version and begin executing a new software version for autonomous operation.

2. The on-trip monitoring system of claim 1 , wherein the executed instructions further cause the on-trip monitoring system to:

monitor current environmental conditions for the AV;

wherein the executed instructions cause the on-trip monitoring system to further transmit the software switching command based on a change in the current environmental conditions.

3. The on-trip monitoring system of claim 2 , wherein the change in the current environmental conditions comprises at least one of a change in lighting conditions, weather conditions, or road conditions.

4. The on-trip monitoring system of claim 1 , wherein the executed instructions further cause the on-trip monitoring system to:

monitor current traffic conditions for the AV;

wherein the executed instructions cause the on-trip monitoring system to further transmit the software switching command based on a change in the current traffic conditions.

5. The on-trip monitoring system of claim 1 , wherein the triggering condition is indicated in the AV data of the AV.

6. The on-trip monitoring system of claim 5 , wherein the AV data includes at least one of AV telemetry data and AV diagnostics data.

7. The on-trip monitoring system of claim 6 , wherein the executed instructions cause the on-trip monitoring system to transmit the software switching command based on the at least one of the AV telemetry data and the AV diagnostics data indicating a degraded state for the AV.

8. The on-trip monitoring system of claim 7 , wherein the degraded state corresponds to at least one of a degraded quality of sensor data for the AV, a sensor fault or failure, or a mechanical fault or failure.

9. The on-trip monitoring system 5 , wherein the AV data includes AV location data from a location-based resource on-board the AV, and wherein the executed instructions cause the on-trip monitoring system to transmit the software switching command based on a location and direction of the AV as indicated in the AV location data.

10. The on-trip monitoring system of claim 1 , wherein the triggering condition corresponds to at least one of the AV picking up a passenger, the AV dropping off a passenger, a location of the AV relative to a boundary of an autonomy grid on which the AV operates, the AV encountering a road closure, the AV failing to complete a given path segment as planned, or one or more efficiency parameters.

11. The on-trip monitoring system of claim 1 , wherein the executed instructions further cause the on-trip monitoring system to:

dynamically determine an aggregate risk quantity for a remainder of a current trip for the AV;

wherein the triggering condition corresponds to the aggregate risk quantity exceeding a predetermined risk threshold.

12. The on-trip monitoring system of claim 11 , wherein the executed instructions further cause the on-trip monitoring system to:

transmit an operation mode switching command to the AV when the aggregate risk quantity exceeds a second risk threshold, the operation mode switching command causing the AV to hand over manual control of the AV to a human driver.

13. The on-trip monitoring system of claim 1 , wherein the AV stores at least one verified software version for fully autonomous operation and at least one unverified software version requiring safety driver supervision during execution.

14. The on-trip monitoring system of claim 1 , wherein the AV data comprises data indicating the AV's interactions with other entities.

15. The on-trip monitoring system of claim 14 , wherein the triggering condition corresponds to a dose call with another entity as indicated in the AV data.

16. The on-trip monitoring system of claim 1 , wherein the executed instructions further cause the on-trip monitoring system to:

transmit the AV data from the AV to other AVs within a given proximity of the AV.

17. The on-trip monitoring system of claim 16 , wherein the executed instructions cause the on-trip monitoring system to transmit the AV data to other AVs within a given proximity of the AV in response to detecting at least one of a change in environmental conditions, a change in traffic conditions, or a change in road conditions in the AV data.

18. A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:

monitor AVs operating throughout a given region by receiving AV data from each of the AVs;

based on a triggering condition of an AV operating within the given region, transmit a software switching command to the AV, the software switching command instructing the AV to terminate execution of a current software version and begin executing a new software version for autonomous operation.

19. The non-transitory computer readable medium of claim 18 , wherein the executed instructions further cause the one or more processors to:

monitor current environmental conditions for the AV;

wherein the executed instructions cause the one or more processors to further transmit the software switching command based on a change in the current environmental conditions.

20. A computer-implemented method of facilitating on-demand transport by autonomous vehicles, the method being performed by one or more processors and comprising:

monitoring AVs operating throughout a given region by receiving AV data from each of the AVs;

based on a triggering condition of an AV operating within the given region, transmitting a software switching command to the AV, the software switching command instructing the AV to terminate execution of a current software version and begin executing a new software version for autonomous operation.

Assignments (6)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 14, 2024
From: UATC, LLC
To: AURORA OPERATIONS, INC.
Reel/Frame 067733/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNMENT DOCUMENT PREVIOUSLY RECORDED AT REEL: 054919 FRAME: 0026. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 2, 2022
From: UATC, LLC
To: UBER TECHNOLOGIES, INC.
Reel/Frame 059692/0280 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2021
From: UATC, LLC
To: UBER TECHNOLOGIES, INC.
Reel/Frame 054919/0026 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2017
From: BRADLEY, DAVID MCALLISTER; KISLOVSKIY, DIMA
To: UBER TECHNOLOGIES, INC.
Reel/Frame 042729/0972 →
Continuity (1)
Related Publication 20180339712A1 · Nov 29, 2018
Cited By (1)
US 12,327,103