IP Library Granted Patent US 12,432,567
Granted Patent B2
US 12,432,567 · App. 18/341,231 · Granted Sep 30, 2025

Systems and methods for matching an autonomous vehicle to a rider

Inventors: Molly Castle Nix (San Francisco, CA); Sean Chin (San Francisco, CA); Eric J. Hanson (San Francisco, CA); Richard Brian Donnelly (Pittsburgh, PA); Dennis Zhao (Pittsburgh, PA)
Assignee: Uber Technologies, Inc.
H04W12/64G06Q10/02G06Q50/40H04W4/021H04W12/06H04W4/40H04W12/47
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 12,432,567
App. No.
18/341,231
Granted
Sep 30, 2025
Kind
B2
Abstract

Systems and methods are directed to matching an available vehicle to a rider requesting a service. In one example, a computer-implemented method includes obtaining, by a computing system comprising one or more computing devices, a service request from a rider. The method further includes obtaining, by the computing system, data indicative of a current location of the rider; and determining that the current location of the rider is within proximity of an autonomous vehicle queuing location. The method further includes providing, by the computing system, data to the rider to provide for selection of an available autonomous vehicle at the autonomous vehicle queuing location. The method further includes obtaining, by the computing system, rider authentication data upon a selection of an autonomous vehicle by the rider; and, in response to obtaining rider authentication data, matching an autonomous vehicle selected by the rider to provide for performance of the service request.

Claims (46)

1. A computer-implemented method for matching an autonomous vehicle to a rider, the method comprising:

obtaining, by a computing system comprising one or more computing devices, a service request from the rider for a rideshare service, the service request comprising an indication of a requested vehicle type;

obtaining, by the computing system, data indicative of a current location of the rider from a device of the rider;

determining, by the computing system, that the current location of the rider is within a first proximity of a location that comprises a plurality of autonomous vehicles available to provide the rideshare service;

based on the determining that the current location is within the first proximity of the location, initiating a rider-match service that allows the rider to select from the plurality of autonomous vehicles to provide the rideshare service;

determining, by the computing system, that the rider has selected the autonomous vehicle from the plurality of autonomous vehicles at the location, a vehicle type of the autonomous vehicle corresponding to the requested vehicle type;

obtaining, by the computing system, rider authentication data upon the selection of the autonomous vehicle by the rider, the obtaining comprising using radio frequency communication to obtain the rider authentication data from a vehicle service application operating on a device of the rider;

in response to obtaining the rider authentication data, matching, by the computing system, the autonomous vehicle to the rider to provide for performance of the service request for the rider; and

in response to the matching, causing trip data of the service request to be provided to the autonomous vehicle, the trip data causing the autonomous vehicle to initiate the rideshare service.

2. The computer-implemented method of claim 1 , the indication of the requested vehicle type describing at least one of a requested vehicle size or a requested vehicle capacity.

3. The computer-implemented method of claim 1 , the indication of the requested vehicle type describing a requested vehicle accessibility.

4. The computer-implemented method of claim 1 , further comprising directing the user to the location that comprises the plurality of autonomous vehicles to provide the rideshare service and to select from the plurality of autonomous vehicles.

5. The computer-implemented method of claim 1 , the autonomous vehicle being at least one of a ground-based autonomous vehicle, an air-based autonomous vehicle, or a watercraft autonomous vehicle.

6. The computer-implemented method of claim 1 , the autonomous vehicle being configured to communicate an autonomous vehicle status via an indicator located on the autonomous vehicle.

7. The computer-implemented method of claim 6 , the indicator comprising a light, the autonomous vehicle being configured to change a color of the light to display an indication that the autonomous vehicle status is available.

8. The computer-implemented method of claim 1 , the determining that the rider has selected the autonomous vehicle is based on a second proximity of the rider to the autonomous vehicle.

9. The computer-implemented method of claim 1 , further comprising providing data indicative of the autonomous vehicle to the rider.

10. A computing system comprising:

at least one processor; and

at least one memory comprising instructions that, when executed by the at least one processor, causes the at least one processor to perform operations comprising:

obtaining a service request from a rider for a rideshare service, the service request comprising an indication of a requested vehicle type;

obtaining data indicative of a current location of the rider from a device of the rider;

determining that the current location of the rider is within a first proximity of a location that comprises a plurality of autonomous vehicles available to provide the rideshare service;

based on the determining that the current location is within the first proximity of the location, initiating a rider-match service that allows the rider to select from the plurality of autonomous vehicles to provide the rideshare service;

determining that the rider has selected an autonomous vehicle from the plurality of autonomous vehicles at the location, a vehicle type of the autonomous vehicle corresponding to the requested vehicle type;

obtaining rider authentication data upon the selection of the autonomous vehicle by the rider, the obtaining comprising using radio frequency communication to obtain the rider authentication data from a vehicle service application operating on a device of the rider;

in response to obtaining the rider authentication data, matching the autonomous vehicle to the rider to provide for performance of the service request for the rider; and

in response to the matching, causing trip data of the service request to be provided to the autonomous vehicle, the trip data causing the autonomous vehicle to initiate the rideshare service.

11. The computing system of claim 10 , the indication of the requested vehicle type describing at least one of a requested vehicle size or a requested vehicle capacity.

12. The computing system of claim 10 , the indication of the requested vehicle type describing a requested vehicle accessibility.

13. The computing system of claim 10 , the operations further comprising directing the user to the location that comprises the plurality of autonomous vehicles to provide the rideshare service and to select from the plurality of autonomous vehicles.

14. The computing system of claim 10 , the autonomous vehicle being at least one of a ground-based autonomous vehicle, an air-based autonomous vehicle, or a watercraft autonomous vehicle.

15. The computing system of claim 10 , the autonomous vehicle being configured to communicate an autonomous vehicle status via an indicator located on the autonomous vehicle.

16. The computing system of claim 15 , the indicator comprising a light, the autonomous vehicle being configured to change a color of the light to display an indication that the autonomous vehicle status is available.

17. The computing system of claim 10 , the determining that the rider has selected the autonomous vehicle is based on a second proximity of the rider to the autonomous vehicle.

18. The computing system of claim 10 , the operations further comprising providing data indicative of the autonomous vehicle to the rider.

19. At least one non-transitory computer-readable medium storing computer-readable instructions that when executed by at least one processor cause the at least one processor to perform operations, the operations comprising:

obtaining a service request from a rider for a rideshare service, the service request comprising an indication of a requested vehicle type;

obtaining data indicative of a current location of the rider from a device of the rider;

determining that the current location of the rider is within a first proximity of a location that comprises a plurality of autonomous vehicles available to provide the rideshare service;

based on the determining that the current location is within the first proximity of the location, initiating a rider-match service that allows the rider to select from the plurality of autonomous vehicles to provide the rideshare service;

determining that the rider has selected an autonomous vehicle from the plurality of autonomous vehicles at the location, a vehicle type of the autonomous vehicle corresponding to the requested vehicle type;

obtaining rider authentication data upon the selection of the autonomous vehicle by the rider, the obtaining comprising using radio frequency communication to obtain the rider authentication data from a vehicle service application operating on a device of the rider;

in response to obtaining the rider authentication data, matching the autonomous vehicle to the rider to provide for performance of the service request for the rider; and

in response the matching, causing trip data of the service request to be provided to the autonomous vehicle, the trip data causing the autonomous vehicle to initiate the rideshare service.

20. The at least one non-transitory computer-readable medium of claim 19 , the indication of the requested vehicle type describing at least one of a requested vehicle size or a requested vehicle capacity.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2023
From: NIX, MOLLY CASTLE; CHIN, SEAN; HANSON, ERIC JAMES; DONNELLY, RICHARD BRIAN; ZHAO, DENNIS
To: UBER TECHNOLOGIES, INC.
Reel/Frame 064634/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2023
From: UBER TECHNOLOGIES, INC.
To: UATC, LLC
Reel/Frame 064641/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2023
From: UATC, LLC
To: UBER TECHNOLOGIES, INC.
Reel/Frame 064641/0048 →
Continuity (4)
Continuation 17204588 · Mar 17, 2021
Continuation 15799323 · Oct 31, 2017
Provisional Application 62564331 · Sep 28, 2017
Related Publication 20230333555A1 · Oct 19, 2023
References Cited (76)
US 5289369A · Hirshberg et al. · 1994 [cited by applicant]
US 6859009B2 · Jablin · 2005 [cited by examiner]
US 7366677B1 · Liu et al. · 2008 [cited by applicant]
US 8118223B2 · Hammad et al. · 2012 [cited by applicant]
US 9229905B1 · Penilla et al. · 2016 [cited by applicant]
US 9599477B1 · Aula et al. · 2017 [cited by applicant]
US 10969782B2 · Nix et al. · 2021 [cited by applicant]
US 11747808B2 · Nix et al. · 2023 [cited by applicant]
US 20020186144A1 · Meunier · 2002 [cited by examiner]
US 20030034873A1 · Chase et al. · 2003 [cited by applicant]
US 20060157563A1 · Marshall · 2006 [cited by applicant]
US 20120109721A1 · Cebon et al. · 2012 [cited by applicant]
US 20120208454A1 · Chai · 2012 [cited by applicant]
US 20130061044A1 · Pinkus · 2013 [cited by examiner]
US 20140005921A1 · Voronel et al. · 2014 [cited by applicant]
US 20150081362A1 · Chadwick et al. · 2015 [cited by applicant]
US 20150161832A1 · Esselink · 2015 [cited by examiner]
US 20150310510A1 · Kelly et al. · 2015 [cited by applicant]
US 20150339928A1 · Ramanujam · 2015 [cited by applicant]
US 20160247109A1 · Scicluna et al. · 2016 [cited by applicant]
US 20160253848A1 · Taniguchi · 2016 [cited by applicant]
US 20180033310A1 · Kentley-klay et al. · 2018 [cited by applicant]
US 20180037164A1 · Newman · 2018 [cited by examiner]
US 20180067620A1 · Adler et al. · 2018 [cited by applicant]
US 20180209803A1 · Rakah et al. · 2018 [cited by applicant]
US 20180321688A1 · Chase · 2018 [cited by examiner]
US 20180322775A1 · Chase et al. · 2018 [cited by applicant]
US 20190094859A1 · Nix et al. · 2019 [cited by applicant]
US 20210200217A1 · Nix et al. · 2021 [cited by applicant]
CN 107063286A · 2017 [cited by applicant]
CN 111357021A · 2020 [cited by applicant]
CN 111357021 · 2024 [cited by applicant]
EP 3688688A1 · 2020 [cited by applicant]
JP 2017010189A · 2017 [cited by applicant]
JP 2017168047A · 2017 [cited by applicant]
JP 2018112930A · 2018 [cited by applicant]
JP 2020535549A · 2020 [cited by applicant]
WO WO2015151862A1 · 2015 [cited by applicant]
WO WO2019067226A1 · 2019 [cited by applicant]
Wong; Avoid rental car roulette with National's Emerald Aisle; Jul. 2015; The Milelion; https://milelion.com/2015/07/23/avoid-rental-car-roulette-with-nationals-emerald-aisle/ (Year: 2015). [cited by examiner]
Flyer Talk Forums; What happens if a Emerald Aisle member takes car from Executive Aisle; May 2016; https://www.flyertalk.com/forum/national-emerald-club/1763685-what-happens-if-emerald-aisle-member-takes-car-executive-… [cited by examiner]
Apple Store, National Car Rental App; https://apps.apple.com/us/app/national-car-rental/id675304115, review data Sep. 22, 2017 (Year: 2017). [cited by examiner]
“U.S. Appl. No. 17/204,588, Supplemental Notice of Allowability mailed Aug. 3, 2023”, 2 pgs. [cited by applicant]
“Chinese Application Serial No. 201880073911.3, Respond filed Sep. 26, 2023 to Office Action mailed May 11, 2023”, w English claims, 16 pgs. [cited by applicant]
“Chinese Application Serial No. 201880073911.3, Office Action mailed Feb. 28, 2024”, w English Translation, 9 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Advisory Action mailed May 19, 2020”, 4 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Examiner Interview Summary mailed Jan. 28, 2020”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Examiner Interview Summary mailed Apr. 28, 2020”, 4 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Examiner Interview Summary mailed Oct. 23, 2020”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Final Office Action mailed Mar. 10, 2020”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Non Final Office Action mailed Jul. 27, 2020”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Non Final Office Action mailed Nov. 5, 2019”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Notice of Allowance mailed Dec. 1, 2020”, 16 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Response filed Jan. 23, 2020 to Non Final Office Action mailed Nov. 5, 2019”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Response filed May 6, 2020 to Final Office Action mailed Mar. 10, 2020”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Response filed Jun. 10, 2020 to Advisory Action mailed May 19, 2020”, 15 pgs. [cited by applicant]
“U.S. Appl. No. 15/799,323, Response filed Oct. 27, 2020 to Non Final Office Action mailed Jul. 27, 2020”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/204,588, Non Final Office Action mailed Nov. 22, 2022”. [cited by applicant]
“U.S. Appl. No. 17/204,588, Notice of Allowance mailed Apr. 19, 2023”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 17/204,588, Preliminary Amendment filed Mar. 17, 2021”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/204,588, Response filed Feb. 22, 2023 to Non Final Office Action mailed Nov. 22, 2022”, 11 pgs. [cited by applicant]
“Chinese Application Serial No. 201880073911.3, Office Action mailed May 11, 2023”, w/o English Translation, 9 pgs. [cited by applicant]
“European Application Serial No. 18789281.5, Communication Pursuant to Article 94(3) EPC mailed Oct. 13, 2021”, 8 pgs. [cited by applicant]
“European Application Serial No. 18789281.5, Response filed Feb. 23, 2022 to Communication Pursuant to Article 94(3) EPC mailed Oct. 13, 2021”, 10 pgs. [cited by applicant]
“European Application Serial No. 18789281.5, Response to Communication pursuant to Rules 161(1) and 162 EPC filed Nov. 17, 2020”, 11 pgs. [cited by applicant]
“European Application Serial No. 18789281.5, Summons to Attend Oral Proceedings mailed Jun. 20, 2022”, 9 pgs. [cited by applicant]
“International Application Serial No. PCT/US2018/050883, International Preliminary Report on Patentability mailed Apr. 9, 2020”, 10 pgs. [cited by applicant]
“International Application Serial No. PCT/US2018/050883, International Search Report mailed Nov. 22, 2018”, 3 pgs. [cited by applicant]
“International Application Serial No. PCT/US2018/050883, Written Opinion mailed Nov. 22, 2018”, 8 pgs. [cited by applicant]
“Japanese Application Serial No. 2020-517968, Notification of Reasons for Rejection mailed Jan. 13, 2022”, W/English Translation, 5 pgs. [cited by applicant]
“Japanese Application Serial No. 2020-517968, Response filed Apr. 6, 2022 to Notification of Reasons for Rejection mailed Jan. 13, 2022”, w/ English Claims, 12 pgs. [cited by applicant]
“Japanese Application Serial No. 2020-517968, Voluntary Amendment filed Sep. 13, 2021”, w/ English Translation, 13 pgs. [cited by applicant]
Firnkorn, Jorg, et al., “Free-floating electric carsharing-fleets in smart cities: The dawning of a post-private car era in urban environments?”, Environmental Science & Policy. vol. 45, (Nov. 6, 2014), 30-40. [cited by applicant]
Griswold, Alison, “The first driverless buss on America's public roads travels only 1000 feet”, Quartz, <https://qz.com/884564/the-first-driverless-bus-on-americas-public-roads-only-travels-1 000-feet/>, (Jan. 2017). [cited by applicant]
Patti, Antonion, “Self-driving bus service models and passengers user experience”, Linked In, <https://www.linkedin.com/pulse/self-driving-bus-service-models-passengers-user-experience-patti>, (2016). [cited by applicant]
“Chinese Application Serial No. 201880073911.3, Response filed Apr. 24, 2024 to Office Action mailed Feb. 28, 2024”, w English claims, 21 pgs. [cited by applicant]