IP Library Granted Patent US 9,953,283
Granted Patent B2
US 9,953,283 · App. 15/358,033 · Granted Apr 24, 2018

Controlling autonomous vehicles in connection with transport services

Inventors: Matthew Sweeney (Pittsburgh, PA); Emily Bartel (Pittsburgh, PA); Jean-Sebastien Valois (Pittsburgh, PA)
Assignee: Uber Technologies, Inc.
G06Q10/063114G05D1/0022G05D1/0027G07C5/008
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 9,953,283
App. No.
15/358,033
Granted
Apr 24, 2018
Kind
B2
Abstract

Systems for controlling autonomous vehicles are disclosed. Using one or more location detection resources, the system can receive vehicle data from an autonomous vehicle as the autonomous vehicle progresses towards a pickup location of a requesting user and receive requester data from a mobile computing device of the requester. The system can determine when the autonomous vehicle and the requester are at or within a threshold distance of the pickup location. Subsequently, the system can instruct the autonomous vehicle to perform one or more non-driving operations to facilitate use of the autonomous vehicle by the requester.

Claims (52)

1. A method for controlling an autonomous vehicle, the method being implemented by one or more processors and comprising:

receiving vehicle data from the autonomous vehicle as the autonomous vehicle progresses towards a pickup location of a first requester;

receiving first requester data from a mobile computing device of the first requester, the first requester data indicating that the first requester is at or near the pickup location;

receiving second requester data from one or more additional mobile computing devices of one or more additional requesters, the second requester data indicating that the one or more additional requesters are located at or near the pickup location;

setting a threshold distance based on a number of the one or more additional requesters;

determining when a position of the autonomous vehicle and a position of the first requester relative to the pickup location is within the threshold distance; and

instructing the autonomous vehicle to perform one or more non-driving operations to facilitate use of the autonomous vehicle by the first requester.

2. The method of claim 1 , further comprising:

receiving user input from the mobile computing device of the first requester;

verifying the user input; and

wherein instructing the autonomous vehicle to perform the one or more non-driver operations includes instructing the autonomous vehicle to perform the one or more non-driving operations in response to verifying the user input.

3. The method of claim 2 , wherein the user input includes one or more of (i) a code provided by the first requester, (ii) a unique identifier for the first requester or the mobile computing device, or (iii) a command entered through a service application on the mobile computing device to perform the one or more non-driving operations.

4. The method of claim 2 , wherein a server receives the user input from the mobile computing device and the server verifies the user input.

5. The method of claim 2 , wherein a server receives the user input from the mobile computing device and transmits data associated with the user input to the autonomous vehicle, and wherein the autonomous vehicle verifies the user input.

6. The method of claim 2 , wherein the autonomous vehicle receives the user input from the mobile computing device using a short-range wireless communication medium.

7. The method of claim 6 , wherein the short-range wireless communication medium includes one or more of Bluetooth, Near-field communication (NFC), or Wi-Fi.

8. The method of claim 1 , wherein the first requester data includes one or more of global positioning system (GPS) data, data generated by a service application on the mobile computing device, or user input from the first requester.

9. The method of claim 1 , wherein the one or more non-driving operations include deactivating one or more locking mechanisms of one or more doors of the autonomous vehicle.

10. The method of claim 1 , wherein the one or more non-driving operations include notifying the first requester that the autonomous vehicle has arrived by operating one or more of (i) a set of lights, (ii) a set of sound-making devices, or (iii) a set of output components of the autonomous vehicle in a predetermined pattern for a duration of time prior to the first requester entering the autonomous vehicle.

11. The method of claim 1 , wherein the one or more non-driving operations include opening a trunk of the autonomous vehicle.

12. A system for controlling an autonomous vehicle comprising:

one or more processors; and

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

receive vehicle data from the autonomous vehicle as the autonomous vehicle progresses towards a pickup location of a first requester;

receive first requester data from a mobile computing device of the first requester, the first requester data indicating that the first requester is at or near the pickup location;

receive second requester data from one or more additional mobile computing devices of one or more additional requesters, the second requester data indicating that the one or more additional requesters are located at or near the pickup location;

set a threshold distance based on a number of the one or more additional requesters;

determine when a position of the autonomous vehicle and a position of the first requester relative to the pickup location is within the threshold distance; and

instruct the autonomous vehicle to perform one or more non-driving operations to facilitate use of the autonomous vehicle by the first requester.

13. The system of claim 12 , wherein the memory resources store instructions that when executed, cause the one or more processors to:

receive user input from the mobile computing device of the first requester;

verify the user input; and

wherein the instructions further cause the one or more processors to instruct the autonomous vehicle to perform the one or more non-driving operations in response to verifying the user input.

14. The system of claim 13 , wherein the user input includes one or more of (i) a code provided by the first requester, (ii) a unique identifier for the first requester or the mobile computing device, or (iii) a command entered through a service application on the mobile computing device to perform the one or more non-driving operations.

15. The system of claim 13 , wherein the one or more processors are provided on, at least, a server.

16. The system of claim 12 , wherein the first requester data includes one or more of global positioning system (GPS) data, data generated by a service application on the mobile computing device, or user input from the first requester.

17. A system comprising:

one or more servers to:

receive vehicle data from an autonomous vehicle as the autonomous vehicle progresses towards a pickup location of a first requester;

receive first requester data from a mobile computing device of the first requester, the first requester data indicating that the first requester is at or near the pickup location;

receive second requester data from one or more additional mobile computing devices of one or more additional requesters, the second requester data indicating that the one or more additional requesters are located at or near the pickup location;

set a threshold distance based on a number of the one or more additional requesters;

determine when a position of the autonomous vehicle and a position of the first requester relative to the pickup location is within the threshold distance; and

send instructions to the autonomous vehicle when the position of the autonomous vehicle and the position of the first requester relative to the pickup location is within the threshold distance; and

an autonomous vehicle to:

perform one or more non-driving operations to facilitate use of the autonomous vehicle by the first requester based on the instructions.

18. The system of claim 17 , wherein the one or more servers receive user input that verifies the first requester.

19. The system of claim 17 , wherein the autonomous vehicle receives user input that verifies the first requester.

20. The system of claim 19 , wherein the autonomous vehicle receives the user input over a short-range wireless communication medium.

21. The system of claim 17 , wherein the autonomous vehicle performs one or more non-driving operations that include deactivating one or more locking mechanisms of one or more doors of the autonomous vehicle.

22. The system of claim 17 , wherein the autonomous vehicle performs one or more non-driving operations that include notifying the first requester that the autonomous vehicle has arrived by operating one or more of (i) a set of lights, (ii) a set of sound-making devices, or (iii) a set of output components of the autonomous vehicle in a predetermined pattern for a duration of time prior to the first requester entering the autonomous vehicle.

23. The system of claim 17 , wherein the autonomous vehicle performs one or more non-driving operations that include opening a trunk.

Assignments (5)
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 Feb 8, 2017
From: SWEENEY, MATTHEW; BARTEL, EMILY; VALOIS, JEAN-SEBASTIEN
To: UBER TECHNOLOGIES, INC.
Reel/Frame 041200/0600 →
Continuity (2)
Provisional Application 62258066 · Nov 20, 2015
Related Publication 20170147959A1 · May 25, 2017