Autonomous vehicles, such as vehicles that do not require a human driver, can be used to aid in the transport of passengers or items from one location to another. Such vehicles may operate in a fully autonomous mode where passengers may provide some initial input, such as a pick up or destination location, and the vehicle maneuvers itself to that location.
One aspect of the disclosure provides a system. The system may include memory storing detailed map information identifying a plurality of predetermined locations where a vehicle is able to pick up or drop off passengers. The system may also include one or more server computers each having one or more processors. The one or more server computers may be configured to: receive a request from a client computing device, the request identifying a first location; select a set of one or more suggested locations by comparing the predetermined locations to the first location; and provide the set of one or more suggested locations to the client computing device.
In one example, the one or more server computers are configured to select the set of one or more suggested locations by determining whether the first location corresponds to a predetermined location, and when the first location corresponds to the predetermined location, including the predetermined location in the set. In another example, the one or more server computers are configured to select the set of one or more suggested locations by identifying predetermined locations of the plurality of predetermined location that are within a threshold distance of the first location. In another example, the threshold distance is defined as a walking distance. Alternatively, the threshold distance is defined as a radial distance. In addition, the one or more server computers are configured to select the set of one or more suggested locations by scoring each given one of the identified predetermined locations based on a first plurality of factors related to the difficulty in a person reaching that given one of the identified predetermined locations from the first location and the set of one or more suggested locations is also selected based upon the scoring of the identified predetermined locations.
In another example, the one or more server computers are configured to conduct the scoring of each given one of the identified predetermined locations also based on a second plurality of factors related to the difficulty in an autonomous vehicle reaching and stopping at that given one of the identified predetermined locations. In this example, the one or more server computers are also configured to determine at least one of the second plurality of factors based on a current location of the autonomous vehicle. In another example, the one or more server computers are configured to select the set of one or more suggested locations by identifying a set number of predetermined locations of the plurality of predetermined locations that are within a threshold distance of the first location and closest to the first location. In this example, the system also includes one or more autonomous vehicles, and wherein the one or more server computers are also configured to receive, from the client computing device, a selection of a suggested location of the set of one or more suggested locations and dispatch a vehicle of the one or more autonomous vehicles to the selected suggested location. In another example, the first location is a destination location and the one or more server computing devices are also configured to receive, from the client computing device, information confirming the first location as the destination location and provide instructions to a vehicle to drop off a passenger at the first location. In another example, the first location is a pick up location and the one or more server computing devices are also configured to receive, from the client computing device, information confirming the first location as the pickup location and dispatch a vehicle to the first location.
Another aspect of the disclosure provides a computer-implemented method. The method includes accessing, by one or more processors of one or more server computing devices, detailed map information identifying a plurality of predetermined locations where a vehicle is able to pick up or drop off passengers; receiving, by the one or more processors, a request from a client computing device, the request identifying a first location; selecting, by the one or more processors, a set of one or more suggested locations by comparing the predetermined locations to the first location and identifying predetermined locations of the plurality of predetermined locations that are within a threshold distance of the first location and closest to the first location; and providing, by the one or more processors, the set of one or more suggested locations to the client computing device.
In one example, selecting the set of one or more suggested locations includes determining whether the first location corresponds to a predetermined location, and when the first location corresponds to the predetermined location, including the predetermined location in the set. In another example, selecting the set includes selecting a predetermined number of predetermined locations of the plurality of predetermined locations that are within a threshold distance of the first location and closest to the first location. In this example, the threshold distance is defined as a walking distance. Alternatively, the threshold distance is defined as a radial distance. In addition, selecting the set of one or more suggested locations includes scoring each given one of the identified predetermined locations based on a first plurality of factors related to the difficulty in a person reaching that given one of the identified predetermined locations from the first location and using the scoring of the identified predetermined locations to select the set of one or more suggested locations. In this example, the scoring of each given one of the identified predetermined locations is conducted based on a second plurality of factors related to the difficulty in an autonomous vehicle reaching and stopping at that given one of the identified predetermined locations.
A further aspect of the disclosure provides a non-transitory, tangible, computer readable medium on which instructions are stored. The instructions, when executed by one or more processors, cause the one or more processors to perform a method. The method includes accessing detailed map information identifying a plurality of predetermined locations where a vehicle is able to pick up or drop off passengers; receiving a request from a client computing device, the request identifying a first location; selecting a set of one or more suggested locations by comparing the predetermined locations to the first location; scoring given ones of the plurality predetermined locations based on a first plurality of factors related to the difficulty in a person reaching a respective given one of the identified predetermined locations from the first location; providing the set of one or more suggested locations to the client computing device; and provide instructions to a vehicle to drop off a passenger at the first location.
Overview
The technology relates to an autonomous vehicle service for maneuvering a user or passenger to a destination, for example taking a trip, autonomously. In order to do so, the user may provide a pickup location and one or more destination locations for the trip to a centralized dispatching system via a client computing device, such as a mobile phone. However, not all locations may be accessible or safe for a passenger pick up, for the vehicle to stop and wait for a passenger to perform some task and return to the vehicle, or for the vehicle to drop off a passenger. For example, autonomous vehicles may not be able to drive everywhere a human driven vehicle can. In addition, road conditions such as construction, emergency services activity, and speed limits (some may be too high for autonomous driving or picking up or dropping off passengers) can pose complications for autonomous vehicles and safety issues for picking up or dropping off passengers. To address this, when provided with a location, the centralized dispatching system may provide a set of one or more suggested locations corresponding to locations that an autonomous vehicle can pick up a passenger (pickup location) or locations where the vehicle can wait for an additional passenger, stop and wait for a passenger to perform some task and return to the vehicle, or for the vehicle to drop off a passenger (destination location). These suggested locations may include those provided by the user and/or convenient nearby locations. Thus, the features described herein may provide for increases in the availability, safety, and usefulness of the services of autonomous vehicles.
Pick up and destination locations may be identified in various ways. As an example, the pickup location can be defaulted to current location of the user's client computing device, but may also be a recent or saved location near the current location associated with the user's account. The user may enter an address or other location information, tap a location on a map, or select a location from a list in order to identify a pickup and/or destination location. The user's client computing device may send the location or locations to one or more server computing devices of the centralized dispatching system.
In order to provide suggestion in response, the one or more server computing devices may access detailed map information. The detailed map information may include information about roads, buildings, elevations, fire hydrants, construction zones, real time traffic conditions, etc. from various sources such as governmental institutions, paid informational services, manually entered information, information gathered and provided in real time by autonomous vehicles, etc. The detailed map information may also include information identifying predetermined locations where an autonomous vehicle can stop to pick up or drop off a passenger. These predetermined locations may include reasonable locations where a vehicle could stop selected manually or through some analysis of the characteristics of each location. The predetermined locations may also be limited to locations within a service area of the autonomous vehicle service.
Once a pickup or destination location is received, the one or more server computing devices may access the detailed map information to determine whether the received location corresponds to one of the predetermined locations. If so, the one or more server computing devices may determine that the received location is in fact reachable.
The one or more server computing devices may then provide a notification to the client computing device including a suggested location corresponding to the received location. The user may then approve or select the returned suggested location as a pick up or destination location and initiate (or continue as the case may be) a trip. If the location is a pickup location, the server may then dispatch a vehicle to the selected location to pick up the user for a trip.
When the received location does not correspond to one of the predetermined locations, the one or more server computing devices may use the detailed map information to identify a set of predetermined locations within a threshold distance of the received location. The threshold distance may be defined as a predetermined radial or walking distance from the received location and may also be adjusted by a user. For example, a default threshold distance may be 500 feet, or more or less, radially or in walking distance from a particular location. A user may then use his or her client computing device to adjust this value up or down and any adjustments may be provided to the one or more server computing devices by the user's client computing device.
For example, this set may include all of the predetermined locations within the threshold distance, or the one or more predetermined locations up to a maximum, within the threshold distance, that are closest to the received location. This set may then be provided to the client computing devices as a set of suggested locations for the user. In some examples, the set may be empty and the user provided with a notification that the received location is unavailable.
In one example, rather than returning all of the predetermined locations in the set, one or more predetermined locations may be selected for and returned as a set of suggested locations to the user. For example, each predetermined location within the set may be scored using various factors and the one or more highest (or lowest depending upon scale) scoring locations may be returned as suggested locations to the user.
In addition, as discussed in detail below, the features described herein allow for various alternatives.
As shown in
The memory 104 stores information accessible by the one or more processors 102, including instructions 106 and data 108 that may be executed or otherwise used by the processor 102. The memory 104 may be of any type capable of storing information accessible by the processor, including a computing device-readable medium, or other medium that stores data that may be read with the aid of an electronic device, such as a hard-drive, memory card, ROM, RAM, DVD or other optical disks, as well as other write-capable and read-only memories. Systems and methods may include different combinations of the foregoing, whereby different portions of the instructions and data are stored on different types of media.
The instructions 106 may be any set of instructions to be executed directly (such as machine code) or indirectly (such as scripts) by the processor. For example, the instructions may be stored as computing device code on the computing device-readable medium. In that regard, the terms “instructions” and “programs” may be used interchangeably herein. The instructions may be stored in object code format for direct processing by the processor, or in any other computing device language including scripts or collections of independent source code modules that are interpreted on demand or compiled in advance. Functions, methods and routines of the instructions are explained in more detail below.
The data 108 may be retrieved, stored or modified by processor 102 in accordance with the instructions 106. For instance, although the claimed subject matter is not limited by any particular data structure, the data may be stored in computing device registers, in a relational database as a table having a plurality of different fields and records, XML documents or flat files. The data may also be formatted in any computing device-readable format.
The one or more processor 102 may be any conventional processors, such as commercially available CPUs. Alternatively, the one or more processors may be a dedicated device such as an ASIC or other hardware-based processor. Although
Computing device 101 may include all of the components normally used in connection with a computing device such as the processor and memory described above as well as a user input (e.g., a mouse, keyboard, touch screen and/or microphone) and various electronic displays (e.g., a monitor having a screen or any other electrical device that is operable to display information). In this example, the vehicle includes an internal electronic display as well as one or more speakers to provide information or audio visual experiences. In this regard, an internal electronic display may be located within a cabin of vehicle 100A and may be used by computing device 101 to provide information to passengers within the vehicle 100A.
Computing device 101 may also include one or more wireless network connections to facilitate communication with other computing devices, such as the client computing devices and server computing devices described in detail below. The wireless network connections may include short range communication protocols such as Bluetooth, Bluetooth low energy (LE), cellular connections, as well as various configurations and protocols including the Internet, World Wide Web, intranets, virtual private networks, wide area networks, local networks, private networks using communication protocols proprietary to one or more companies, Ethernet, WiFi and HTTP, and various combinations of the foregoing.
Computing device 101 of vehicle 100A may also receive or transfer information to and from other computing devices. In this regard, system 100 also includes a plurality of computing devices 110, 120, 130, 140 and a storage system 150 connected via a network 160. As noted above, system 100 also includes vehicle 100B, which may be configured similarly to vehicle 100. Although only a few vehicles and computing devices are depicted for simplicity, a typical system may include significantly more.
As shown in
The network 160, and intervening nodes, may include various configurations and protocols including short range communication protocols such as Bluetooth, Bluetooth LE, the Internet, World Wide Web, intranets, virtual private networks, wide area networks, local networks, private networks using communication protocols proprietary to one or more companies, Ethernet, WiFi and HTTP, and various combinations of the foregoing. Such communication may be facilitated by any device capable of transmitting data to and from other computing devices, such as modems and wireless interfaces.
In one example, one or more computing devices 110 may include a server having a plurality of computing devices, e.g., a load balanced server farm, that exchange information with different nodes of a network for the purpose of receiving, processing and transmitting the data to and from other computing devices. For instance, one or more computing devices 110 may include one or more server computing devices that are capable of communicating with computing device 101 of vehicle 100A or a similar computing device of vehicle 100B as well as computing devices 120, 130, 140 via the network 160. For example, vehicles 100A and 100B may be a part of a fleet of vehicles that can be dispatched by server computing devices to various locations. In this regard, the vehicles of the fleet may periodically send the server computing devices location information provided by the vehicle's respective positioning systems and the one or more server computing devices may track the locations of the vehicles.
In addition, server computing devices 110 may use network 160 to transmit and present information to a user, such as user 122, 132, 142 (shown in
As shown in
In addition, the client computing devices 120 and 130 may also include components 128 and 138 for determining the position and orientation of client computing devices. For example, these components may include a GPS receiver to determine the device's latitude, longitude and/or altitude as well as an accelerometer, gyroscope or another direction/speed detection device.
Although the client computing devices 120, 130, and 140 may each comprise a full-sized personal computing device, they may alternatively comprise mobile computing devices capable of wirelessly exchanging data with a server over a network such as the Internet. By way of example only, client computing device 120 may be a mobile phone or a device such as a wireless-enabled PDA, a tablet PC, a wearable computing device or system, or a netbook that is capable of obtaining information via the Internet or other networks. In another example, client computing device 130 may be a wearable computing system, shown as a head-mounted computing system in
In some examples, client computing device 140 may be a concierge work station used by an administrator to provide concierge services to users such as users 122 and 132. For example, a concierge 142 may use the concierge work station 140 to communicate via a telephone call or audio connection with users through their respective client computing devices or vehicles 100A or 100B in order to facilitate the safe operation of vehicles 100A and 100B and the safety of the users as described in further detail below. Although only a single concierge work station 140 is shown in
Storage system 150 may store various types of information as described in more detail below. This information may be retrieved or otherwise accessed by a server computing device, such as one or more server computing devices 110, in order to perform some or all of the features described herein. For example, the information may include routing data for generating and evaluating routes between locations. For example, the routing information may be used to estimate how long it would take a vehicle at a first location to reach a second location. In this regard, the routing information may include map information including roads, as well as information about roads such as direction (one way, two way, etc.), orientation (North, South, etc.), speed limits, as well as traffic information identifying expected traffic conditions, etc. The map information may also include buildings, elevations, fire hydrants, construction zones, real time traffic conditions, etc. from various sources such as governmental institutions, paid informational services, manually entered information, information gathered and provided in real time by autonomous vehicles, etc.
In some instances, the map information may include information identifying areas which have been preselected or preapproved for an autonomous vehicle to pick up a passenger (pickup location) or locations where the vehicle can wait for an additional passenger, stop and wait for a passenger to perform some task and return to the vehicle, or for the vehicle to drop off a passenger (destination location). For example,
As with memory 104, storage system 150 can be of any type of computerized storage capable of storing information accessible by the server computing devices 110, such as a hard-drive, memory card, ROM, RAM, DVD, CD-ROM, write-capable, and read-only memories. In addition, storage system 150 may include a distributed storage system where data is stored on a plurality of different storage devices which may be physically located at the same or different geographic locations. Storage system 150 may be connected to the computing devices via the network 160 as shown in
In addition to the operations described above and illustrated in the figures, various operations will now be described. It should be understood that the following operations do not have to be performed in the precise order described below. Rather, various steps can be handled in a different order or simultaneously, and steps may also be added or omitted.
In one aspect, a user may download an application for requesting a vehicle to a client computing device. For example, users 122 and 132 may download the application via a link in an email, directly from a website, or an application store to client computing devices 120 and 130. For example, client computing device may transmit a request for the application over the network, for example, to one or more server computing devices 110, and in response, receive the application. The application may be installed locally at the client computing device.
The user may then use his or her client computing device to access the application and request a vehicle. As an example, a user such as user 132 may use client computing device 130 to send a request to one or more server computing devices 110 for a vehicle. As part of this, the user may identify a pickup location, a destination location, and, in some cases, one or more intermediate stopping locations anywhere within a service area where a vehicle can stop.
These pickup and destination locations may be predefined (e.g., specific areas of a parking lot, etc.) or may simply be any location within a service area of the vehicles. As an example, a pickup location can be defaulted to current location of the user's client computing device, or can be input by the user at the user's client device. For instance, the user may enter an address or other location information or select a location on a map to select a pickup location. As shown in
In the example of
Once the user has selected one or more of a pickup and/or destination locations, the user's client computing device may send the location or locations to one or more server computing devices of the centralized dispatching system. In response, the one or more server computing devices may provide one or more suggested locations corresponding to each received location.
In order to provide a suggested location in response to a received location, the one or more server computing devices may access the map information of storage system 150 to determine whether the received location corresponds to one of the predetermined locations for picking up or dropping off passengers. If so, the one or more server computing devices may determine that the received location is in fact reachable. For example, as shown in example 500 of
When a requested location does correspond to one of the predetermined locations, the one or more server computing devices may provide a notification to the client computing device including a suggested location corresponding to the received location. For example, in response to receiving the location of map marker 426 and determining that this received location corresponds to the predetermined location of point 326, the one or more server computing devices 110 provide a notification to client computing device 120 suggesting the location of map marker 426 as a suggested location for a passenger pickup or destination location, depending upon the nature of the requested location. As shown in
When the received location does not correspond to one of the predetermined locations, the one or more server computing devices may use the detailed map information to identify one or more other suggested locations. This set of suggested locations may then be provided to the client computing device that sent the received location.
For example, the one or more server computing devices 110 may identify set of predetermined locations within a threshold distance of the received location. The threshold distance may be defined as a predetermined radial distance from the received location and may also be adjusted (increased or decreased) by a user, for example, by providing the one or more server computing devices 110 with a user preference. For example, a user may then use his or her client computing device to adjust this value up or down and any adjustments may be provided to the one or more server computing devices by the user's client computing device.
In one example, a default threshold distance may be 500 feet, or more or less, radially or in walking distance from a received location. In other words, the threshold may be used to draw an area around a received location from a client computing device and identify the set or suggested locations. For example, as shown in
As shown in example 800 of
The set of suggested locations may include all of the predetermined locations within the threshold distance, as shown in
The set of suggested locations may then be provided to the client computing devices. As with the example above, a user may then select or reject any suggested location as either a pick up or destination location, depending upon the nature of the received location. If the location is a pickup location, the server may then dispatch a vehicle, such as vehicle 100A or vehicle 100B, to the selected location to pick up the user for a trip. If the location is a destination location, the server may provide the selected location to the vehicle, with instructions to maneuver the vehicle to the selected location with the passenger and drop off a passenger or wait as the case may be.
In some examples, the set of suggested locations may be empty, so the one or more server computing devices do not have any suggested locations to provide in response to a received location from a client computing device. For example, as shown in
Rather than simply sending the empty set of suggested locations to the client computing device, the one or more server computing device 110 may provide the client computing device with a notification indicating that the received location is not available.
In one example, rather than returning all of the predetermined locations in the set, one or more predetermined locations may be selected for and returned as a set of suggested locations to the user. For example, each predetermined location within the set may be scored using various factors and the one or more highest (or lowest depending upon scale) scoring locations may be returned as suggested locations to the user.
The scoring may be based on various factors that quantify the ease and/or difficulty of reaching the predetermined location by one or both of an autonomous vehicle and the user. Factors related to an autonomous vehicle may include, for example, the location of any autonomous vehicles available to pick up the user (if a pickup location), whether the vehicle would have to first pass the location (on the opposite side of the street) and turn around, whether the autonomous vehicle can currently reach the predetermined location (because access is temporarily prevented due to traffic or construction conditions), the availability of parking or places to pull over and wait at the predetermined location, as well as any other such factors. Factors related to the user may include, for example, the distance from the received location to the predetermined location, the availability and size of sidewalks, the presence and grade of hills, the number and size of roads that would need to be crossed from the received location to the predetermined location, or any other characteristics of roads that would affect the ease of walking to the suggested location. In one instance, each factor may be individually scored for a given predetermined location and the scores summed to provide an overall score for that given predetermined location.
The scoring may be especially useful situations in which a predetermined location very close to the received location is somehow less desirable than another predetermined location farther away. For example, if a predetermined location on one side of a highway is closer in distance to a received location, but because of the difficulty involved in walking there from the received location, the scoring may identify another predetermined location that is farther away from the received location but easier to reach by walking.
For example,
In an alternative, rather than returning a received location as a suggested location if the received location corresponds to a predetermined location, the one or more server computing devices may simply include the predetermined location that corresponds to the received location in a set of predetermined locations (the rest of the predetermined locations in the set being determined using a threshold distance as described above). In this example, the received location may be scored along with the other predetermined locations in the set in order to select the best location or locations to provide as suggestions to a user as discussed above.
Although the examples discussed above relate to a user initiating a trip by providing a pick up and one or more destination locations, the features described above may be used to identify and suggest destination locations for a dropping off of a user during a trip. This may be especially useful where a problem arises with a destination location which was previously approved by a user. In one example, the problem may be that the vehicle is no longer able to reach the destination location. This information may be provided to the vehicle's computing device by way of traffic condition updates received, for example, from the one or more server computing device or a traffic condition service.
In another example, if there is some type of hazard at the destination location where the vehicle would drop off a user, the features described above may be used to provide a user with an alternative destination to drop off the user. Hazards may include pot holes, puddles, slippery ground, objects on top of the ground that would make for uneven footing, cracks in the pavement, uneven ground, high curbs, storm drains, broken glass, etc. For example, various sensors of the vehicle, including lasers, radar, sonar, etc., may provide data regarding the ground next to the vehicle. This data may be used to detect any hazards near the vehicle, using computer vision algorithms and the computing device 101. If a hazard is detected the user may be provided with a new suggested destination or destinations. This new suggested destination may be selected as discussed above by the vehicle's computing device 101 or by the vehicle's computing device 101 requesting such information from the one or more server computing devices 110.
In addition to or instead of providing a new suggested destination or destinations, the vehicle may provide the user with an alert to warn him or her of the hazard. Alerts may take any number of forms including displaying a message on an internal screen, an audible message from a speaker inside of the vehicle, or a notification sent to a smart phone program being used to interact with the vehicle.
As discussed above, the number of suggested locations provided to the user may be a default value such as zero or one or more or less. Alternatively, the number of suggested locations may be set by a user and provided to the one or more server computing devices. In yet another alternative, the number of suggested locations provided may be determined by selecting any of the predetermined locations of the set having at least a particular score.
Unless otherwise stated, the foregoing alternative examples are not mutually exclusive, but may be implemented in various combinations to achieve unique advantages. As these and other variations and combinations of the features discussed above can be utilized without departing from the subject matter defined by the claims, the foregoing description of the embodiments should be taken by way of illustration rather than by way of limitation of the subject matter defined by the claims. In addition, the provision of the examples described herein, as well as clauses phrased as “such as,” “including” and the like, should not be interpreted as limiting the subject matter of the claims to the specific examples; rather, the examples are intended to illustrate only one of many possible embodiments. Further, the same reference numbers in different drawings can identify the same or similar elements.
The present application is a continuation of U.S. patent application Ser. No. 16/196,194, filed Nov. 20, 2018, which is a continuation of U.S. patent application Ser. No. 15/645,297, filed on Jul. 10, 2017, issued as U.S. Pat. No. 10,156,449, which is a continuation of U.S. patent application Ser. No. 14/745,799, filed on Jun. 22, 2015, issued as U.S. Pat. No. 9,733,096 the disclosures of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4361202 | Minovitch | Nov 1982 | A |
4465155 | Collins | Aug 1984 | A |
5293160 | Kurozu et al. | Mar 1994 | A |
5367456 | Summerville et al. | Nov 1994 | A |
5640323 | Kleimenhagen et al. | Jun 1997 | A |
6236333 | King | May 2001 | B1 |
6298304 | Theimer | Oct 2001 | B1 |
6356820 | Hashimoto et al. | Mar 2002 | B1 |
6591172 | Oda et al. | Jul 2003 | B2 |
6680675 | Suzuki | Jan 2004 | B1 |
6963794 | Geber et al. | Nov 2005 | B2 |
7113864 | Smith et al. | Sep 2006 | B2 |
7859386 | Lundkvist | Dec 2010 | B2 |
7928829 | Hermann | Apr 2011 | B2 |
8044771 | Nakajima et al. | Oct 2011 | B2 |
8078349 | Prada Gomez et al. | Dec 2011 | B1 |
8126450 | Howarter et al. | Feb 2012 | B2 |
8352112 | Mudalige | Jan 2013 | B2 |
8494765 | Konet et al. | Jul 2013 | B2 |
8532862 | Neff | Sep 2013 | B2 |
8768565 | Jefferies et al. | Jan 2014 | B2 |
8676427 | Ferguson et al. | Mar 2014 | B1 |
8676430 | Ferguson et al. | Mar 2014 | B1 |
8688306 | Nemec et al. | Apr 2014 | B1 |
8718861 | Montemerlo et al. | May 2014 | B1 |
8736438 | Vasquez et al. | May 2014 | B1 |
8880270 | Ferguson et al. | Nov 2014 | B1 |
8935034 | Zhu et al. | Jan 2015 | B1 |
9060003 | Wang et al. | Jun 2015 | B2 |
9191514 | Cavanaugh et al. | Nov 2015 | B1 |
9304513 | Ichikawa et al. | Apr 2016 | B2 |
9733096 | Colijn et al. | Aug 2017 | B2 |
20040036622 | Dukach et al. | Feb 2004 | A1 |
20040249569 | Oh | Dec 2004 | A1 |
20040260470 | Rast | Dec 2004 | A1 |
20050021227 | Matsumoto et al. | Jan 2005 | A1 |
20050153707 | Ledyard et al. | Jul 2005 | A1 |
20060253251 | Puranik et al. | Nov 2006 | A1 |
20070073472 | Odinak et al. | Mar 2007 | A1 |
20070073552 | Hileman | Mar 2007 | A1 |
20080061931 | Hermann | Mar 2008 | A1 |
20080136674 | Jang et al. | Jun 2008 | A1 |
20080195428 | O'Sullivan | Aug 2008 | A1 |
20080266139 | Kim | Oct 2008 | A1 |
20080312817 | Kawauchi | Dec 2008 | A1 |
20090171566 | Morimoto et al. | Jul 2009 | A1 |
20090187538 | Grun | Jul 2009 | A1 |
20090216600 | Hill | Aug 2009 | A1 |
20090248231 | Kamiya | Oct 2009 | A1 |
20090287367 | Salinger | Nov 2009 | A1 |
20090327011 | Petroff | Dec 2009 | A1 |
20100007525 | Shanbhag et al. | Jan 2010 | A1 |
20100017084 | Riegel | Jan 2010 | A1 |
20100070168 | Sumcad et al. | Mar 2010 | A1 |
20100106397 | Van | Apr 2010 | A1 |
20100075656 | Howarter et al. | May 2010 | A1 |
20100117585 | Fitch et al. | May 2010 | A1 |
20100183409 | Checketts et al. | Jul 2010 | A1 |
20100256836 | Mudalige | Oct 2010 | A1 |
20100284771 | Stierler | Nov 2010 | A1 |
20100286845 | Rekow et al. | Nov 2010 | A1 |
20110099040 | Felt et al. | Apr 2011 | A1 |
20110112969 | Zaid et al. | May 2011 | A1 |
20110144865 | Niemz | Jun 2011 | A1 |
20110144980 | Rysenga | Jun 2011 | A1 |
20110191019 | Holsinger et al. | Aug 2011 | A1 |
20110301985 | Camp et al. | Dec 2011 | A1 |
20120041675 | Juliver et al. | Feb 2012 | A1 |
20120072051 | Koon | Mar 2012 | A1 |
20120083959 | Dolgov et al. | Apr 2012 | A1 |
20120083960 | Zhu et al. | Apr 2012 | A1 |
20120083964 | Montemerlo et al. | Apr 2012 | A1 |
20120173080 | Cluff | Jul 2012 | A1 |
20120188100 | Min et al. | Jul 2012 | A1 |
20120232943 | Myr | Sep 2012 | A1 |
20120271500 | Tsimhoni et al. | Oct 2012 | A1 |
20130024049 | Yoshioka et al. | Jan 2013 | A1 |
20130110342 | Wuttke et al. | May 2013 | A1 |
20130231824 | Wilson et al. | Sep 2013 | A1 |
20130238783 | Alexander et al. | Sep 2013 | A1 |
20130289825 | Noh et al. | Oct 2013 | A1 |
20130321178 | Jameel et al. | Dec 2013 | A1 |
20140135598 | Weidl et al. | May 2014 | A1 |
20140156182 | Nemec et al. | Jun 2014 | A1 |
20140172292 | McGee et al. | Jun 2014 | A1 |
20140172727 | Abhyanker et al. | Jun 2014 | A1 |
20140189096 | Miller et al. | Jul 2014 | A1 |
20140285361 | Tippelhofer et al. | Sep 2014 | A1 |
20140297090 | Ichinose | Oct 2014 | A1 |
20140365250 | Ikeda et al. | Dec 2014 | A1 |
20140365913 | Santamaria | Dec 2014 | A1 |
20140380424 | Thompson | Dec 2014 | A1 |
20150073645 | Davidsson et al. | Mar 2015 | A1 |
20150081362 | Chadwick et al. | Mar 2015 | A1 |
20150127191 | Misra et al. | May 2015 | A1 |
20150148989 | Cooper et al. | May 2015 | A1 |
20150149320 | Smirin | May 2015 | A1 |
20150185034 | Abhyanker | Jul 2015 | A1 |
20150219464 | Beaurepaire et al. | Aug 2015 | A1 |
20150321641 | Abou Mahmoud et al. | Nov 2015 | A1 |
20150324708 | Skipp et al. | Nov 2015 | A1 |
20150334187 | Pesola et al. | Nov 2015 | A1 |
20150338849 | Nemec et al. | Nov 2015 | A1 |
20150339928 | Ramanujam | Nov 2015 | A1 |
20150369621 | Abhyanker | Dec 2015 | A1 |
20150370251 | Siegel et al. | Dec 2015 | A1 |
20160019790 | Tobolski et al. | Jan 2016 | A1 |
20160027307 | Abhyanker et al. | Jan 2016 | A1 |
20160042303 | Medina et al. | Feb 2016 | A1 |
20160116293 | Grover et al. | Apr 2016 | A1 |
20160125735 | Tuukkanen | May 2016 | A1 |
20160148514 | Iwami et al. | May 2016 | A1 |
20160170410 | Ichikawa et al. | Jun 2016 | A1 |
20160203377 | Irie et al. | Jul 2016 | A1 |
20160209848 | Kojo et al. | Jul 2016 | A1 |
20160221495 | Cunningham, III et al. | Aug 2016 | A1 |
20160301698 | Katara et al. | Oct 2016 | A1 |
20160318518 | Suzuki et al. | Nov 2016 | A1 |
20160327949 | Wilson et al. | Nov 2016 | A1 |
20160349751 | Sugimoto | Dec 2016 | A1 |
20170075358 | Zhang | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
101383089 | Mar 2009 | CN |
101894462 | Nov 2010 | CN |
101971116 | Feb 2011 | CN |
102460535 | May 2012 | CN |
102939230 | Feb 2013 | CN |
103514739 | Jan 2014 | CN |
104166663 | Nov 2014 | CN |
102005049380 | Apr 2007 | DE |
2573720 | Mar 2013 | EP |
2629269 | Aug 2013 | EP |
3362622 | Jan 1997 | JP |
H10162291 | Jun 1998 | JP |
3362622 | Aug 1998 | JP |
10208195 | Aug 1998 | JP |
H10207504 | Aug 1998 | JP |
H10208195 | Aug 1998 | JP |
H11184521 | Jul 1999 | JP |
2001005524 | Jan 2001 | JP |
2001234653 | Aug 2001 | JP |
3362622 | Jan 2003 | JP |
2006308390 | Nov 2006 | JP |
2009014704 | Jan 2009 | JP |
2011226441 | Nov 2011 | JP |
2014019301 | Feb 2014 | JP |
2014048047 | Mar 2014 | JP |
2014092408 | May 2014 | JP |
03080391 | Oct 2003 | WO |
20110158347 | Dec 2011 | WO |
2013117205 | Aug 2013 | WO |
2014024254 | Feb 2014 | WO |
2015117813 | Aug 2015 | WO |
2015169204 | Nov 2015 | WO |
Entry |
---|
“Decision of Rejection for Japanese Patent Application No. 2016-563820, dated Jul. 2, 2018”, 8 pages (5 pages of English Translation and 3 pages of official copy). |
“Examination Report No. 1 for Australian Patent Application No. 2015263981 dated Aug. 25, 2017”, 7 pages. |
“Examination Report No. 1 for Australian Patent Application No. 2016283946, dated Nov. 23, 2018”, 4 pages. |
“Examination Report No. 2 for Australian Patent Application No. 2015263981 dated Nov. 8, 2017”, 8 pages. |
“Examination Report No. 3 for Australian Patent Application No. 2015263981 dated Jan. 29, 2018”, 9 pages. |
“Examination Report received for European Patent Application No. 15796123.6, dated Sep. 7, 2018”, 4 pages. |
“Examination Report received for European Patent Application No. 18156156.4, dated Sep. 7, 2018”, 5 pages. |
“Examiner's Report for Canadian Patent Application No. 2,947,995 dated Sep. 14, 2017”, 4 pages. |
“Examiner's Report for Canadian Patent Application No. 2,947,995, dated Jun. 4, 2018”, 4 pages. |
“Examiner's Report for Canadian Patent Application No. 2,990,016, dated Nov. 2, 2018”, 4 pages. |
“Extended European Search Report for Application No. 16815024.1, dated Jan. 18, 2019”, 6 pages. |
“Extended European Search Report received for European Patent Application No. 15796123.6, dated Mar. 8, 2018”, 6 pages. |
“Extended European Search Report received for European Patent Application No. 18156156.4, dated Mar. 28, 2018”, 6 pages. |
“Federal Transit Administration, Topic Guides on ADA Transportation—Topic Guide 6, On-Time Performance”, <http://dredf.org/ADA!g/OTP.shtml>, Jul. 2011, 50 pages. |
“Federal Transit Administration, Topic Guides on ADA Transportation—Topic Guide 7, No. Shows”, <http://dredf.org/ADAtg/noshow.shtml>, Jul. 2011, 27 pages. |
“First Office Action received for Chinese Patent Application No. 201580023657.2, dated Jul. 27, 2018”, 21 pages (13 pages of English Translation and 8 pages of Official copy). |
“International Preliminary Report on Patentability for International Application No. PCT/US2016/035977 dated Jan. 4, 2018”, 10 pages. |
“International Preliminary Report on Patentability for PCT Application No. PCT/US2015/032171, dated Dec. 8, 2016”, 12 pages. |
“International Search Report and Written Opinion for PCT Application No. PCT/US2016/035977 dated Sep. 29, 2016”, 12 pages. |
“International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032171, dated Sep. 17, 2015”, 13 pages. |
“International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032181, dated Sep. 4, 2015”, 12 pages. |
“North Las Vegas—Code of Ordinance”, Available Online at <https:lllibrary.municode.com/nv/north_las_vegas/codes/code_of_ordinances/196159?nodeId= TIT1 OVETR_CH1 0.48STSTPAGE_1 0.48.180STPACULOZO>, May 21, 2013, 13 pages. |
“Notice of Acceptance received for Australian Patent Application No. 2015263981, dated Apr. 30, 2018”, 3 pages. |
“Notice of Preliminary Rejection for Korean Patent Application No. 10-2016-7030982, dated Apr. 30, 2018”, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
“Notice of Preliminary Rejection for Korean Patent Application No. 10-2016-7030982, dated Nov. 29, 2018”, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
“Notice of Reasons for Rejection received for Japanese Patent Application No. 2016-563820, dated Feb. 16, 2018”, 11 pages ( 6 pages of English Translation and 5 pages of Official copy). |
“Office Action for Japanese Patent Application No. 2017-564890, dated Dec. 26, 2018”, 11 pages (6 pages of English Translation and 5 pages of Official copy). |
Baydere , et al., “MR 302: The Future of the Automobile: Car-Sharing Service using Autonomous Automobiles”, Spring 2014, 2014, pp. 1-10. |
Bluetooth® Keyless , “FAQs about the Bluetooth® Passive Keyless Entry Module”, downloaded from <http://bluetoothkeyless.info/bluetooth-keyless-information/>, 2014, 3 pages. |
Chevrolet , “OnStar Remote Link™: Control you Chevy even when you're not driving it”, Available online at <http://www.chevrolet.com/onstar-remotelink.html>, 2014, 2 pages. |
Fagnant , et al., “The travel and environmental implications of shared autonomous vehicles, using agent-based model scenarios”, Transportation Research Part C, vol. 40, 2014, pp. 1-13 (The attached Reference includes 22 pages). |
Goodwin, Antuan , “Add-on module auto-unlocks your car when your phone is near”, c|net, Available online at <http://www.cnet.com/news/add-on-module-auto-unlocks-your-car-when-your-phone-is-near/>, Nov. 19, 2013, 5 pages. |
Jaffe, Eric , “The First Look at How Google's Self-Driving Car Handles City Streets—Citylab”, Available at <https jjwww.citylab.com/life/2014/04/first-lookhow-googles-self-driving-car -handles-city-streets/8977/>, Apr. 28, 2014, 1-18 pages. |
Junqing Wei , et al., “Towards a viable autonomous driving research platform”, In: Intelligent Vehicles Symposium (IV), 2013 IEEE, Jun. 23-26, 2013, pp. 763-770. |
McFadden, Colin-Druce , “Autonomous car concept swaps steering wheel for gesture controls”, Available online at: <http://www.dvice.com/2014-3-12/autonomous-car-concept-swaps-steering-wheel-gesture-controls>, Mar. 12, 2014, 4 pages. |
McKeegan, Noel , “Autonomous taxi can be hailed with and iPad app”, Available online at: <http://www.gizmag.com/autonomous-taxi-ipad/16649/>, Oct. 14, 2010, 2 pages. |
Quora, et al., “In Between Rides, Is it in an Uber (Company) Drive's Best Interest to Stay Put or Drive Around?”, Quora.com—A Place to share knowledge and better understand the world. Available online at < https://www.quora.com/Inbetween-rides-is-it-in-an-Uber-company-drivers-best -interest-to-stay-put-or-drive-around>, Feb. 25, 2014, 2 pages. |
Ranoa, Raoul , “lnfographic:The car that drives itself”, Los Angeles Times, copyright 2014, Available online at <https://www.latimes.com/local/lanow/la-sci-g-google-self-driving-car-20140528-htmlstory.html>, 2014, 5 pages. |
Ridden, Paul , “ATNMBL—the concept car with no steering wheel, brake pedal or driver's seat”, Available online at : <http://www.gizmag.com/atnmbl-autonomous-concept-passenger-transport/15877/>, Jul. 29, 2010, 3 pages. |
Schwarz , et al., “Towards Autonomous Vehicles”, University of Nebraska—Lincoln. Final Reports & Technical Breifs from Mid-America Transportation center. Reort# MATC-UI:117, Available Online at <http://digitalcommons.unl.edu/cgi/viewcontent.cgi?article=1 092&context=matcreports>, Dec. 2013, 79 pages. |
uberpeople.net , “How Long Do You Wait? Post Your Times”, UberPeople.NET-Independent Community of Rideshare Drivers, Available Online at <https://uberpeople.netlthreads/how-long-do-you-wait-post-your-times.2162/>, Aug. 20, 2014, 5 pages. |
uberpeople.net , “Wait Time for Riders”, UberPeople.NET-Independent Community of Rideshare Drivers. Available Online at < https://uberpeople.net/threads/wait-time-for-riders.2441 >, May 12, 2014, 7 pages. |
Urmson , et al., “U.S. Appl. No. 61/391,271, filed Oct. 8, 2010, titled “Autonomous Vehicles””, 56 pages. |
European Patent Office Action for Application No. 16815024.1 dated Nov. 12, 2020. |
Japanese Office Action for Application No. 2019-204532 dated Dec. 8, 2020. |
Japanese Office Action for Application No. 2019-204532 dated Apr. 23, 2021. |
First Chinese Office Action for Application No. 201680035905.X dated Jun. 11, 2020. |
Number | Date | Country | |
---|---|---|---|
20200292333 A1 | Sep 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16196194 | Nov 2018 | US |
Child | 16886823 | US | |
Parent | 15645297 | Jul 2017 | US |
Child | 16196194 | US | |
Parent | 14745799 | Jun 2015 | US |
Child | 15645297 | US |