Patent Description:
When a person (or user) wants to be physically transported between two locations via a vehicle, they may use any number of taxi services. To date, these services typically involve a human driver who is given dispatch instructions to a location to pick up the user. These services, while useful, generally fail to provide users with real time information about what actions a taxi is taking on the way to pick up the user.

<CIT>describes a method and a system of variable bus stops across a bus route in a regional transportation network, according to one embodiment. A method of a bus server includes analyzing a current geospatial location of a mobile device responsive to a pick up request of a prospective bus passenger, associating a closest street intersection with the current geospatial location of the mobile device, and determining if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. A message may be communicated to the mobile device based on the determination of whether the bus route traverses the closest street intersection. A bus associated with the bus route may be instructed to pick up the prospective bus passenger when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. <CIT> presents technologies that provide a cloud-based context-aware distributive taxi cab dispatching service to registered users. A method of providing this service may include receiving, from a user device of a registered user, a request for taxi information, obtaining the requested information from one or more computing devices of one or more taxi cabs or taxi service companies and one or more data stores, and providing the obtained information to the user device. The provided taxi information may be based on a passenger profile of the user and may include a list of taxi cabs recommended based on the profile. The method may further include scheduling a selected taxi cab. The method may also include monitoring the user's location and updating the scheduling of the taxi based on the user's location. The method may also include monitoring the user's location while in a taxi for data collection and safety reasons.

The subject-matter for protection is defined in the claims.

One aspect of the disclosure provides a method for arranging a pickup between a driverless vehicle and a passenger according to claim <NUM>.

In one example, the user input indicates a tap at a location on the map, and wherein the indication includes a location on the map that corresponds to the user input, such that the location on the map is sent to the computing device associated with the vehicle. In another example, the computing device is incorporated into the vehicle. In another example, displaying the location of the vehicle includes displaying a first indicator on the map and displaying the location of the client computing device includes displaying a second indicator on the map. In this example, the method also includes receiving, by the one or more processors, updated location information for the vehicle; determining, by the one or more processors, updated location information for the client computing device using a sensor of the client computing device; moving the first and second indicators on the map based on the updated location information. In addition, the method also includes when edges of the first and second indicators are moved to contact one another, displaying a notification on the display indicating that the passenger is able to attempt the fly-by pickup; and in response to the notification, receiving user input indicating confirmation that the passenger would like to attempt the fly-by pickup. The indication includes the confirmation that the passenger would like to attempt the fly-by pickup. In addition or alternatively, the method also includes receiving, from a sensor of the client computing device, information indicating that the client computing device is currently being moved, and wherein the indication includes the information indicating that the client computing device is currently moving. In addition or alternatively, the method also includes receiving, from the computing device associated with the vehicle, a request for the passenger to perform a task in order to confirm that the passenger would like to attempt the fly-by pickup, wherein the indication includes confirmation that the task has been performed by the passenger.

Passenger pick-up for self-driving vehicles can be challenging due to changing environmental conditions, the absence of a human driver, and uncertainty as to how long a vehicle may have to wait (or is able to wait) for the passenger. For instance, there may be other parked cars, busy traffic, construction, or other obstacles that require the vehicle's computing devices to determine whether stopping at a given location is safe, permissible, or even a possibility. In addition, without a driver to make eye contact with the passenger and gesture his/her intention to stop at a different location, the passenger can be confused about where to meet up with the vehicle. Moreover, given the changing environmental conditions mentioned above, the user may be uncertain about how long the vehicle may have to wait for the user to arrive and board the vehicle. This could change relatively quickly, for instance, based on whether a vehicle is pulling over on a busy or quiet street.

By increasing the amount of information available to a passenger and facilitating communications between the passenger and the computers of the vehicle, many of the issues discussed above can be addressed. In addition, this may also allow the passenger and vehicle to achieve "fly-by pickups" in real time or pickups at locations other than an original pickup location. A fly-by pickup is a pickup of a passenger that is achieved prior to when the vehicle reaches a predetermined pickup area for the vehicle to pick up the passenger. In other words, after a vehicle is dispatched to a predetermined pickup location or area in order to pick up a passenger, a new pickup location or area is identified for the passenger and the vehicle. If a fly-by pickup is successful, the passenger is safely picked up at the new pickup location or area by the vehicle. This new pickup location or area is outside of the predetermined pickup area. As such, a fly-by pickup may be result of last minute change to the pickup location or area for the passenger in view of a better or alternative pickup location or area for the vehicle, the passenger, or both.

In order to achieve the fly-by pickup, information about the vehicle's status may be shared with a potential passenger (or simply passenger). At the same time, information about the passenger's location may be reported to the vehicle. Because of this exchange of information, the vehicle and/or the passenger may attempt or initiate a fly-by pickup.

During a fly-by pickup, rather than pulling into a parking area and waiting for the passenger, the vehicle may simply double park, for instance, stopping in a lane when safe to do so and waiting only a few seconds for the passenger to get into the car, close the door and fasten his or her seatbelt. If this occurs, the fly-by pickup has been successful. If not, the vehicle may have to pull away and continue towards the original pickup location. In some cases, the vehicle and passenger may need to rearrange a new pickup location after an unsuccessful fly-by pickup attempt.

Before actually attempting a fly-by pickup, in addition to the current location of the passenger's client computing device, the vehicle's computing devices may take into consideration current conditions, such as whether it is a busy or quiet street and how disruptive a fly-by pickup might be. Once the vehicle's computing devices have determined that a fly-by pickup is safe given the current and expected (historical) conditions, the vehicle may initiate a fly-by pickup.

When initiated by a vehicle, the fly-by pickup may occur automatically. In this regard, if the passenger's reported location indicates that the passenger is already waiting at a particular spot such as by a curb and therefore likely ready to go, the vehicle can stop at that location. Alternatively, the vehicle may ask the user if he or she is interested in a fly-by-pick-up in real time, for instance by displaying a popup notification with options for the user to select to accept or deny the request to do the fly-by pickup. In some examples, the fly-by pickup notification can be made using visual representations of the relationship between the vehicle and the location of the passenger's client computing device.

A fly-by pickup may also be initiated by the passenger. The user may signal physically to the vehicle that he or she is interested in a fly-by pickup by stepping into the street. Alternatively, the passenger may initiate a fly-by pickup using his or her client computing device.

To achieve a fly-by pickup, the passenger may be asked to perform some task to further facilitate the fly-by pickup. This may include a special gesture, which the vehicle's computing devices could detect either from the laser, camera, the passenger's client computing device, or some combination of the above. In another example, the passenger may be asked to take a picture, hold his or her client computing device in a particular way, walk to a certain location, provide verbal cues, review and provide feedback regarding an image captured by a camera of the vehicle, etc..

In addition to considering the current location of the passenger's client computing device and current and expected conditions, the vehicle's computing devices may also consider the passenger's past history with attempting and achieving fly-by pickups. In some cases, the passenger may be offered discounts, free rides, or other perks in exchange for accepting or initiating a fly-by pickup. This may also be dependent upon whether the fly-by pickup was successful (and the passenger made it into the vehicle).

Fly-by pickups can be extremely helpful to both passengers and vehicles. For instance, a fly-by pickup can save both the vehicle and passenger time and effort to reach the original pickup location. This increases the efficiency of the vehicles and reduces the time needed to find a spot to park, stop and park the vehicle, and to wait for the passenger.

As shown in <FIG>, a vehicle <NUM> in accordance with one aspect of the disclosure includes various components. While certain aspects of the disclosure are particularly useful in connection with specific types of vehicles, the vehicle may be any type of vehicle including, but not limited to, cars, trucks, motorcycles, busses, recreational vehicles, etc. The vehicle may have one or more computing devices, such as computing device <NUM> containing one or more processors <NUM>, memory <NUM> and other components typically present in general purpose computing devices.

As an example, data <NUM> of memory <NUM> may store predefined scenarios. A given scenario may identify a set of scenario requirements including a type of object, a range of locations of the object relative to the vehicle, as well as other factors such as whether the autonomous vehicle is able to maneuver around the object, whether the object is using a turn signal, the condition of a traffic light relevant to the current location of the object, whether the object is approaching a stop sign, etc. The requirements may include discrete values, such as "right turn signal is on" or "in a right turn only lane", or ranges of values such as "having an heading that is oriented at an angle that is <NUM> to <NUM> degrees offset from a current path of vehicle <NUM>. " In some examples, the predetermined scenarios may include similar information for multiple objects.

The one or more processor <NUM> 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 <FIG> functionally illustrates the processor, memory, and other elements of computing device <NUM> as being within the same block, it will be understood by those of ordinary skill in the art that the processor, computing device, or memory may actually include multiple processors, computing devices, or memories that may or may not be stored within the same physical housing. As an example, internal electronic display <NUM> may be controlled by a dedicated computing device having its own processor or central processing unit (CPU), memory, etc. which may interface with the computing device <NUM> via a high-bandwidth or other network connection. In some examples, this computing device may be a user interface computing device which can communicate with a user's client device. Similarly, the memory may be a hard drive or other storage media located in a housing different from that of computing device <NUM>. Accordingly, references to a processor or computing device will be understood to include references to a collection of processors or computing devices or memories that may or may not operate in parallel.

Computing device <NUM> may 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 <NUM> (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 <NUM> as well as one or more speakers <NUM> to provide information or audio visual experiences. In this regard, internal electronic display <NUM> may be located within a cabin of vehicle <NUM> and may be used by computing device <NUM> to provide information to passengers within the vehicle <NUM>. In addition to internal speakers, the one or more speakers <NUM> may include external speakers that are arranged at various locations on the vehicle in order to provide audible notifications to objects external to the vehicle <NUM>.

In one example, computing device <NUM> may be an autonomous driving computing system incorporated into vehicle <NUM>. The autonomous driving computing system may capable of communicating with various components of the vehicle. For example, returning to <FIG>, computing device <NUM> may be in communication with various systems of vehicle <NUM>, such as deceleration system <NUM> (for controlling braking of the vehicle), acceleration system <NUM> (for controlling acceleration of the vehicle), steering system <NUM> (for controlling the orientation of the wheels and direction of the vehicle), signaling system <NUM> (for controlling turn signals), navigation system <NUM> (for navigating the vehicle to a location or around objects), positioning system <NUM> (for determining the position of the vehicle), perception system <NUM> (for detecting objects in the vehicle's environment), and power system <NUM> (for example, a battery and/or gas or diesel powered engine) in order to control the movement, speed, etc. of vehicle <NUM> in accordance with the instructions <NUM> of memory <NUM> in an autonomous driving mode which does not require or need continuous or periodic input from a passenger of the vehicle. Again, although these systems are shown as external to computing device <NUM>, in actuality, these systems may also be incorporated into computing device <NUM>, again as an autonomous driving computing system for controlling vehicle <NUM>.

The computing device <NUM> may control the direction and speed of the vehicle by controlling various components. By way of example, computing device <NUM> may navigate the vehicle to a destination location completely autonomously using data from the map information and navigation system <NUM>. Computer <NUM> may use the positioning system <NUM> to determine the vehicle's location and perception system <NUM> to detect and respond to objects when needed to reach the location safely. In order to do so, computer <NUM> may cause the vehicle to accelerate (e.g., by increasing fuel or other energy provided to the engine by acceleration system <NUM>), decelerate (e.g., by decreasing the fuel supplied to the engine, changing gears, and/or by applying brakes by deceleration system <NUM>), change direction (e.g., by turning the front or rear wheels of vehicle <NUM> by steering system <NUM>), and signal such changes (e.g., by lighting turn signals of signaling system <NUM>). Thus, the acceleration system <NUM> and deceleration system <NUM> may be a part of a drivetrain that includes various components between an engine of the vehicle and the wheels of the vehicle. Again, by controlling these systems, computer <NUM> may also control the drivetrain of the vehicle in order to maneuver the vehicle autonomously.

As an example, computing device <NUM> may interact with deceleration system <NUM> and acceleration system <NUM> in order to control the speed of the vehicle. Similarly, steering system <NUM> may be used by computing device <NUM> in order to control the direction of vehicle <NUM>. For example, if vehicle <NUM> configured for use on a road, such as a car or truck, the steering system may include components to control the angle of wheels to turn the vehicle. Signaling system <NUM> may be used by computing device <NUM> in order to signal the vehicle's intent to other drivers or vehicles, for example, by lighting turn signals or brake lights when needed.

Navigation system <NUM> may be used by computing device <NUM> in order to determine and follow a route to a location. In this regard, the navigation system <NUM> and/or data <NUM> may store map information, e.g., highly detailed maps that computing devices <NUM> can use to navigate or control the vehicle. As an example, these maps may identify the shape and elevation of roadways, lane markers, intersections, crosswalks, speed limits, traffic signal lights, buildings, signs, real time traffic information, vegetation, or other such objects and information. The lane markers may include features such as solid or broken double or single lane lines, solid or broken lane lines, reflectors, etc. A given lane may be associated with left and right lane lines or other lane markers that define the boundary of the lane. Thus, most lanes may be bounded by a left edge of one lane line and a right edge of another lane line.

<FIG> is an example of map information <NUM> for a section of roadway including intersections <NUM> and <NUM>. In this example, the map information <NUM> includes information identifying the shape, location, and other characteristics of lane lines <NUM>, <NUM>, <NUM>, traffic signal lights <NUM>, <NUM>, crosswalks <NUM>, <NUM>, sidewalks <NUM>, stop signs <NUM>, <NUM>, and yield sign <NUM>. Areas where the vehicle can drive may be associated with one or more rails <NUM>, <NUM>, and <NUM> which indicate the location and direction in which a vehicle should generally travel at various locations in the map information. For example, a vehicle may follow rail <NUM> when driving in the lane between lane lines <NUM> and <NUM>, and may transition to rail <NUM> in order to make a right turn at intersection <NUM>. Thereafter the vehicle may follow rail <NUM>. Of course, given the number and nature of the rails only a few are depicted in map information <NUM> for simplicity and ease of understanding. Although not shown, the detailed map information may also include historical information identifying typical and historical traffic conditions at various dates and times.

Although the detailed map information is depicted herein as an image-based map, the map information need not be entirely image based (for example, raster). For example, the detailed map information may include one or more roadgraphs or graph networks of information such as roads, lanes, intersections, and the connections between these features. Each feature may be stored as graph data and may be associated with information such as a geographic location and whether or not it is linked to other related features, for example, a stop sign may be linked to a road and an intersection, etc. In some examples, the associated data may include grid-based indices of a roadgraph to allow for efficient lookup of certain roadgraph features.

<FIG> are examples of external views of vehicle <NUM>. As can be seen, vehicle <NUM> includes many features of a typical vehicle such as headlights <NUM>, windshield <NUM>, taillights/turn signal lights <NUM>, rear windshield <NUM>, doors <NUM>, side view mirrors <NUM>, tires and wheels <NUM>, and turn signal/parking lights <NUM>. Headlights <NUM>, taillights/turn signal lights <NUM>, and turn signal/parking lights <NUM> may be associated the signaling system <NUM>. Light bar <NUM> may also be associated with the signaling system <NUM>. As noted above, vehicle <NUM> may include various speakers <NUM> arranged on the external surfaces of the vehicle corresponding to the one or more speakers <NUM> as noted above.

The one or more computing devices <NUM> of vehicle <NUM> may also receive or transfer information to and from other computing devices. <FIG> and <FIG> are pictorial and functional diagrams, respectively, of an example system <NUM> that includes a plurality of computing devices <NUM>, <NUM>, <NUM>, <NUM> and a storage system <NUM> connected via a network <NUM>. System <NUM> also includes vehicle <NUM>, and vehicle 100A which may be configured similarly to vehicle <NUM>. Although only a few vehicles and computing devices are depicted for simplicity, a typical system may include significantly more.

In one example, one or more computing devices <NUM> 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 <NUM> may include one or more server computing devices that are capable of communicating with one or more computing devices <NUM> of vehicle <NUM> or a similar computing device of vehicle 100A as well as client computing devices <NUM>, <NUM>, <NUM> via the network <NUM>. For example, vehicles <NUM> and 100A 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 <NUM> may use network <NUM> to transmit and present information to a user, such as user <NUM>, <NUM>, <NUM> on a display, such as displays <NUM>, <NUM>, <NUM> of computing devices <NUM>, <NUM>, <NUM>. In this regard, computing devices <NUM>, <NUM>, <NUM> may be considered client computing devices.

As shown in <FIG>, each client computing device <NUM>, <NUM>, <NUM> may be a personal computing device intended for use by a user <NUM>, <NUM>, <NUM>, and have all of the components normally used in connection with a personal computing device including a one or more processors (e.g., a central processing unit (CPU)), memory (e.g., RAM and internal hard drives) storing data and instructions, a display such as displays <NUM>, <NUM>, <NUM> (e.g., a monitor having a screen, a touch-screen, a projector, a television, or other device that is operable to display information), and user input devices <NUM>, <NUM>, <NUM> (e.g., a mouse, keyboard, touch-screen or microphone). The client computing devices may also include a camera for recording video streams, speakers, a network interface device, and all of the components used for connecting these elements to one another.

Although the client computing devices <NUM>, <NUM>, and <NUM> 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 <NUM> 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 <NUM> may be a wearable computing system, shown as a head-mounted computing system in <FIG>. As an example the user may input information using a small keyboard, a keypad, microphone, using visual signals with a camera, or a touch screen.

In some examples, client computing device <NUM> may be concierge work station used by an administrator to provide concierge services to users such as users <NUM> and <NUM>. For example, a concierge <NUM> may use the concierge work station <NUM> to communicate via a telephone call or audio connection with users through their respective client computing devices or vehicles <NUM> or 100A in order to ensure the safe operation of vehicles <NUM> and 100A and the safety of the users as described in further detail below. Although only a single concierge work station <NUM> is shown in <FIG> and <FIG>, any number of such work stations may be included in a typical system.

Storage system <NUM> 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 <NUM>, in order to perform some or all of the features described herein. For example, the information may include user account information such as credentials (e.g., a user name and password as in the case of a traditional single-factor authentication as well as other types of credentials typically used in multi-factor authentications such as random identifiers, biometrics, etc.) that can be used to identify a user to the one or more server computing devices. The user account information may also include personal information such as the user's name, contact information, identifying information of the user's client computing device (or devices if multiple devices are used with the same user account), as well as one or more unique signals for the user.

The storage system <NUM> may also store 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, not necessarily as particular as the detailed map information described above, but including roads, as well as information about those road 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 storage system <NUM> may also store information which can be provided to client computing devices for display to a user. For instance, the storage system <NUM> may store predetermined distance information for determining an area at which a vehicle is likely to stop for a given pickup or destination location. The storage system <NUM> may also store graphics, icons, and other items which may be displayed to a user as discussed below.

As with memory <NUM>, storage system <NUM> can be of any type of computerized storage capable of storing information accessible by the server computing devices <NUM>, such as a hard-drive, memory card, ROM, RAM, DVD, CD-ROM, write-capable, and read-only memories. In addition, storage system <NUM> 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 <NUM> may be connected to the computing devices via the network <NUM> as shown in <FIG> and/or may be directly connected to or incorporated into any of the computing devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc..

In one aspect, a user may download an application for requesting a vehicle to a client computing device. For example, users <NUM> and <NUM> may download the application via a link in an email, directly from a website, or an application store to client computing devices <NUM> and <NUM>. For example, client computing device may transmit a request for the application over the network, for example, to one or more server computing devices <NUM>, 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 <NUM> may use client computing device <NUM> to send a request to one or more server computing devices <NUM> 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 <FIG>, user <NUM> may use his or her finger <NUM> to tap on a map <NUM> displayed on the display <NUM> of client computing device <NUM>. In response, as shown in <FIG>, the location of the tap on the map, displayed as map marker <NUM>, may be identified as a requested location. Allowing the user to input or select a location may be especially helpful where the user is not currently located at the pickup location but will be by the time the vehicle arrives.

In the example of <FIG>, a user is provided with a plurality of options for inputting locations. As shown, the user is able to select from a series of saved locations under a saved option <NUM> previously saved by the user as discussed above. The user may also be provided with option <NUM> which provide the user with the ability to view a list of recent locations. By selecting option <NUM>, the user may be able to conduct a location search. For example, a user may enter a search query ("fast food restaurant" or "doctor doe" or "gas station near me") and receive a set of locations corresponding to the search query as with a typical map or location-based search engine.

Once the user has selected one or more of a pickup and/or destination locations, the client computing device <NUM> may send the location or locations to one or more server computing devices of the centralized dispatching system. In response, one or more server computing devices, such as server computing device <NUM>, may select a vehicle, for instance based on availability and proximity to the user. The server computing device may then dispatch the selected vehicle to pickup to the user by providing the vehicle with the pickup and/or destination locations specified by the user.

When a vehicle, such as vehicle <NUM>, is dispatched to the user, the client computing device <NUM> can show information about where the pickup location will be. This information may be provided to the client computing device from the server computing device <NUM>. For example, the server computing device <NUM> may access the information of storage system <NUM> in order to identify a map and determine a route along the map between the vehicle's current location and the pickup location. This information, along with a potential pickup area or zone, may then be provided to the client computing device for display to a user.

Once received by the client computing device, the information may be displayed as shown in <FIG>. For instance, client computing device <NUM> displays a map <NUM> (corresponding to map <NUM>) identifying a potential pickup zone <NUM> around the pickup location identified by marker <NUM>. In addition to the map and potential pickup zone <NUM>, the client computing device may also display a marker <NUM> indicating the current location of the client computing device. The current location of the client computing device may be determined using various methods such including GPS and/or other location services at the passenger's client computing device.

As noted above, information about the vehicle's status may be shared with a potential passenger, or simply passenger. This may include, for instance, displaying the vehicle's up to date location and route to the passenger on the map so that the passenger can plan ahead how he or she will meet the vehicle. For instance, a passenger viewing the displayed map may be able to readily recognize whether he or she needs to cross the street, or move to where the car is likely to find parking along the route. As shown in <FIG>, marker <NUM> identifies the current location of the vehicle <NUM>. In this example, the route the vehicle is currently taking towards the potential pickup zone <NUM> is also identified by path <NUM>.

In addition, the passenger can be provided with narrative updates about what the vehicle is currently doing. For instance, as shown in <FIG>, narrative updates <NUM> and <NUM> are displayed which indicate the status of the vehicle as being dispatched and on the way to pick up the passenger. Other examples of narrative updates may include such as "Looking for a spot to pull over. ", "Found a spot to pull over", "Can't find a spot, circling around the block.

At the same time, information about the passenger's location may be reported to the vehicle. For example, the location determined using GPS and/or other location services at the passenger's client computing device may be sent directly (or indirectly by way of a dispatching server computing device) to the vehicle.

Because of this exchange of information, the vehicle and/or passenger may attempt or initiate a fly-by pickup. As noted above, during a fly-by pickup, rather than pulling into a parking area and waiting for the passenger, the vehicle may simply double park, for instance, stopping in a lane when safe to do so and waiting only a few seconds for the passenger to get into the car, close the door and fasten his or her seatbelt. If this occurs, the fly-by pickup has been successful. If not, the vehicle may have to pull away and continue towards the original pickup location. In some cases, the vehicle and passenger may need to rearrange a new pickup location after an unsuccessful fly-by pickup attempt.

Before actually attempting a fly-by pickup, in addition to the current location of the passenger's client computing device, the vehicle's computing devices may take into consideration current traffic conditions, such as whether it is a busy or quiet street and how disruptive a fly-by pickup might be. This may include processing real time data from sensors of the vehicle as well as querying the map information of the navigation system <NUM> for historical information to determine how safe a street/location is (or is expected to be) for pulling over. Of course, because a fly-by pickup does not involve stopping and waiting for the passenger for long periods (more than a few seconds), the vehicle may be able to do a fly-by pickup even on streets where the vehicle would normally not be able to stop or pick up a passenger.

Once the vehicle's computing devices have determined that a fly-by pickup is safe given the current and expected (historical) conditions, the vehicle may initiate a fly-by pickup. When initiated by a vehicle, the fly-by pickup may occur automatically. In this regard, if the passenger's reported location indicates that the passenger is already waiting at a particular spot such as by a curb and therefore likely ready to go, the vehicle can stop at that location. For instance, as shown in <FIG>, the marker <NUM>, representing the current location of the client computing device <NUM> (and presumably also the current location of user <NUM>), indicates that the passenger is very close to a curb and may be ready to be pickup up. As this information is shared directly with the vehicle's computing devices <NUM>, the vehicle may use this information to initiate a fly-by pickup. At the same time, the vehicle's computing devices may send a notification to the client computing device (either directly or via server computing devices <NUM>) indicating that the vehicle is attempting an fly-by pickup. The notification may be displayed on the display of the client computing device in order to let the passenger know that the vehicle is attempting the fly-by pickup.

Alternatively, rather than initiating the fly-by pickup automatically, the vehicle's computing devices may use the indication as a basis to ask the user if he or she is interested in a fly-by-pick-up in real time. In this regard, the vehicle's computing devices <NUM> may send a request to the client computing device <NUM> to query whether the passenger is interested in a fly-by pickup. At the client computing device <NUM>, this may be achieved as shown in <FIG> by displaying a popup notification <NUM> with options <NUM> and <NUM> for the user to select to accept ("YES" option <NUM>) or deny ("NO" option <NUM>) the request to do the fly-by pickup. Of course, such notifications should only be used once or twice for any given pickup in order to avoid cluttering the screen of the client computing device and discouraging passengers to attempt fly-by pickups. In this example, narrative update <NUM> provides further details on why the vehicle's computing devices are requesting a fly-by pickup, again to provide information about the status of the vehicle. Again, once confirmed by the user, the vehicle's computing devices may send a notification to the client computing device (either directly or via server computing devices <NUM>) indicating that the vehicle is attempting an fly-by pickup. The notification may be displayed on the display of the client computing device in order to let the passenger know that the vehicle is attempting the fly-by pickup.

In some examples, the fly-by pickup notification can be made using visual representations of the relationship between the vehicle and the location of the passenger's client computing device. For instance, as shown in <FIG>, the location of the vehicle and the passenger's client computing device may be represented by bubbles <NUM> and <NUM>, respectively. As the passenger's client computing device and the vehicle approach one another, the bubbles will move towards one another. Once the bubbles "meet" as shown in <FIG>, the display may change, for instance, by flashing once or twice and displaying the notification (as shown in <FIG>) asking if the passenger wants to attempt a fly-by pickup. Again, once confirmed by the user, the vehicle's computing devices may send a notification to the client computing device (either directly or via server computing devices <NUM>) indicating that the vehicle is attempting an fly-by pickup. The notification may be displayed on the display of the client computing device in order to let the passenger know that the vehicle is attempting the fly-by pickup.

In some instances, the fly-by pickup may be initiated by the passenger. For instance, as indicated above, the passenger may be able to view the current location of the vehicle relative to his or her location (or rather the location of the passenger's client computing device) via a map displayed on the passenger's client computing device. This can give the passenger a clear indication of when a fly-by pickup is possible and even encourage him or her to initiate fly-by pickups as discussed below.

In one example, the user may also signal physically to the vehicle that he or she is interested in a fly-by pickup by physically stepping into the street. In this example, the vehicle's perception system <NUM> may detect the downward motion of the passenger stepping into the street, and the computing devices <NUM> may use this information to determine that the passenger is interested in a fly-by pickup. At this point, the passenger may be prompted (if the fly-by pickup is determined to be safe given the current and expected (historical) conditions as noted above) as shown in <FIG> and a confirmation notification displayed to the user indicating that the vehicle is attempting a fly-by pickup. Alternatively, rather than requesting confirmation from the user, the client computing device may display the notification that the vehicle is attempting a fly-by pickup and the vehicle may simply stop at a location proximate to the passenger.

Alternatively, the passenger may initiate a fly-by pickup using his or her client computing device. For instance, the passenger may tap or double tap on a map to pick an alternative pickup location as shown in <FIG>. For instance, in <FIG>, user <NUM>'s finger <NUM> double taps on the display. In response, a marker <NUM> appears indicating the location of one of the first or second taps. The geographic location of the marker relative to the map <NUM> is sent to the vehicle's computing device <NUM> (directly or indirectly via the server computing devices <NUM>). While this is occurring, the narrative update <NUM> may be displayed to indicate that the client computing device is checking with the vehicle's computing devices <NUM> to confirm that the fly-by pickup can and/or will be attempted. Again, at this point, the passenger may be prompted (if the fly-by pickup is determined to be safe given the current and expected (historical) conditions as noted above) as shown in <FIG> and a confirmation notification displayed to the user indicating that the vehicle is attempting a fly-by pickup. Alternatively, rather than requesting confirmation from the user, the client computing device may display the notification that the vehicle is attempting a fly-by pickup and the vehicle may simply stop at a location proximate to the passenger.

In another example, the passenger may drag a marker representing the current pickup location to another point on the map, or draw a line on the map from his or her current location towards a street in order to signal path that the user is going to take. As can be seen between the examples of <FIG> and <FIG>, marker <NUM> of <FIG> has been dragged across the display <NUM> to a new position in <FIG>. The geographic location of the new position may be sent to the vehicle's computing devices <NUM> and at the same time, the narrative update <NUM> may be displayed. Again, the passenger may be prompted (if the fly-by pickup is determined to be safe given the current and expected (historical) conditions as noted above) as shown in <FIG> and a confirmation notification displayed to the user indicating that the vehicle is attempting a fly-by pickup. Alternatively, rather than requesting confirmation from the user, the client computing device may display the notification that the vehicle is attempting a fly-by pickup and the vehicle may simply stop at a location proximate to the passenger.

Once the vehicle is attempting the fly-by pickup, in order to achieve the fly-by pickup, the passenger may be asked to perform some task to further facilitate the fly-by pickup. This may include a special gesture, which the vehicle's computing devices could detect either from the laser, camera, the passenger's client computing device, or some combination of the above. In another example, the passenger may be asked to take a selfie so vehicle's computing devices can recognize him or her, or to take a picture or video of the area near the passenger (e.g. buildings, vegetation, etc.) so the vehicle can recognize the exact location of the passenger. In yet another example, the passenger may be asked to hold his or her client computing device out while the device's screen flashes or a flash is lit in order to allow the vehicle's computing devices to identify the passenger's exact location visually. Similarly, the passenger's client computing device may play a particular sound which a microphone on the vehicle captures and is used to determine the location of the passenger. In addition or alternatively, the passenger may be asked to walk towards the vehicle, such as into the road in front of the vehicle.

These tasks may also include asking the passenger to provide verbal cues. For instance, the passenger may speak while an external microphone on the vehicle picks up the sound and matches the sound to a signal received at the microphone on the user's client computing device. In another example, the passenger may provide a verbal description of his or herself so that the vehicle's computing devices can recognize the passenger. In yet another example, if the vehicle determines that it is unable to pull over where the passenger is standing, the vehicle can open a window and slow down while the passenger speaks instructions into the cabin of the vehicle.

For passengers with visual impairments, the vehicle may provide audible cues to assist the passenger and the vehicle in achieving a fly-by pickup. For instance, the vehicle could make (by playing through a speaker) or send audio ques to the passenger's client computing device such as a specific beeping sound to guide or lead the passenger towards the vehicle. If the vehicle's perception system is able to localize the passenger very well, the vehicle's computing devices may provide more specific audible instructions to the client computing device to be played to the user such as "walk to your right along the sidewalk for <NUM> feet; then, step off the curb to your vehicle, which is parked <NUM> feet into the road.

In other examples, the vehicle's computing devices may send the passenger's client computing device a picture. This picture may have been captured by a camera of the vehicle's perception system <NUM>. The picture may be displayed on the user's client computing device with a notification indicating to the passenger that the vehicle has identified him or her as being nearby. In some instances, the notification may include a request for the passenger to confirm whether the vehicle has identified the correct person. For example, as shown in <FIG>, image <NUM> of people <NUM>, <NUM> is displayed on the display <NUM> with narrative update <NUM> indicating the vehicle has captured an image which may include user <NUM>. The narrative update also requests that the user tap on the image of his or herself to confirm that the user is actually included in the image and which of people <NUM>, <NUM> is the user <NUM>. The picture may be sent as part of the notification/request to achieve the fly-by pickup or as part of the typical process for picking up a passenger.

To further determine whether a passenger is ready for a fly-by pickup, the passenger's client computing device may send information to the vehicle's computing device about whether the client computing device is currently moving. Movement information may be provided by an accelerometer and/or gyroscope of the client computing device. This alone or combined with information from the vehicle's camera may indicate whether the passenger is currently walking or standing. In that regard, if a passenger is standing, he or she may be more interested in being pickup at the original pickup location. If walking, he or she may be more interested in a fly-by pickup. Of course, the reverse may also be considered true in certain circumstances.

In addition to considering the current location of the passenger's client computing device and current and expected conditions, the vehicle's computing devices may also consider the passenger's past history with attempting and achieving fly-by pickups. For instance, if the passenger has little or no history of attempts, the vehicle's computing devices may be more willing to attempt a fly-by pickup than if the same passenger has a history of failing to meet the vehicle after accepting or requesting a fly-by pickup. Of course, if a passenger has a history of being successful at achieving fly-by pickups, the passenger may be more likely to receive notifications to attempt a fly-by pickup. Similarly, for a passenger who is more successful at achieving fly-by pickups, the vehicle's computing device may attempt riskier fly-by pickups than for someone who has not attempted a fly-by pickup or has been unsuccessful in the past.

In some cases, the passenger may be offered discounts, free rides, or other perks in exchange for accepting or initiating a fly-by pickup. This may also be dependent upon whether the fly-by pickup was successful (and the passenger made it into the vehicle).

<FIG> is an example flow diagram <NUM> in accordance with some of the aspects described above that may be performed by one or more computing devices such as client computing device <NUM>. For example, at block <NUM>, a request for a driverless vehicle to pick up a passenger at a pickup area is received. Confirmation that the vehicle has been dispatched to the pickup area is received at block <NUM>. After the vehicle has been dispatched, location information identifying a location of the vehicle as the vehicle is moving towards the pickup area is received at block <NUM>. The location of the vehicle and a location of a client computing device of the passenger are displayed on a map on a display of the client computing device at block <NUM>. An indication that the passenger is interested in a fly-by pickup in real time is identified at block <NUM>. The fly-by pickup allows the passenger to safely enter the vehicle at a location outside of the pickup area and prior to the vehicle having reached the predetermined pickup area. The indication is sent to a computing device associated with the vehicle at block <NUM>. Confirmation that the vehicle will attempt the fly-by pickup is received at block <NUM>. A notification indicating to the passenger that the vehicle will attempt the fly-by pickup is displayed on the display based on the received confirmation at block <NUM>.

<FIG> is an example flow diagram <NUM> in accordance with some of the aspects described above that may be performed by one or more computing devices such as vehicle computing devices <NUM>. For example, at block <NUM>, dispatch instructions dispatching a driverless vehicle to a predetermined pickup area in order to pick up a passenger are received. The vehicle is maneuvered towards the predetermined pickup area to pick up the passenger at block <NUM>. While maneuvering the vehicle, a location of a client computing device of the passenger is received at block <NUM>. An indication that the passenger is interested in a fly-by pickup in real time is received at block <NUM>. The fly-by pickup allows the passenger to safely enter the vehicle at a location outside of the predetermined pickup area and prior to vehicle reaching the predetermined pickup area at block <NUM>. The fly-by pickup is determined to be appropriate based on at least the location of the client computing device and the indication at block <NUM>. The vehicle is further maneuvered in order to attempt the fly-by pickup based on the determination at block <NUM>.

Claim 1:
A method for arranging a pickup between a driverless vehicle (<NUM>, <NUM>) and a passenger (<NUM>, <NUM>, <NUM>), the method comprising:
sending, by one or more processors of a client computing device (<NUM>, <NUM>, <NUM>) associated with the passenger, a request for the vehicle to pick up the passenger at a pickup area (<NUM>);
receiving, by the one or more processors, confirmation that the vehicle has been dispatched to the pickup area;
receiving after the vehicle has been dispatched, by the one or more processors, location information identifying a location of the vehicle as the vehicle is moving towards the pickup area;
displaying, by the one or more processors on a display (<NUM>, <NUM>, <NUM>) of the client computing device, the location of the vehicle and a location of the client computing device on a map (<NUM>, <NUM>);
displaying, by the one or more processors on the display, a notification indicating that the passenger is able to attempt a fly-by pickup that allows the passenger to safely enter the vehicle at a location outside of the pickup area and prior to the vehicle having reached the pickup area;
identifying, by the one or more processors, an indication that the passenger is interested in the fly-by pickup in real time, wherein identifying the indication comprises receiving, by the one or more processors, responsive to displaying the notification, user input indicating confirmation to attempt the fly-by pickup;
sending, by the one or more processors, the indication to a computing device associated with the vehicle;
receiving, by the one or more processors, confirmation that the vehicle will attempt the fly-by pickup;
displaying on the display, by the one or more processors, a further notification indicating to the passenger that the vehicle will attempt the fly-by pickup based on the received confirmation; and
receiving, by the one or more processors, a request for the passenger to perform a task to facilitate the fly-by pickup.