Autonomous vehicles, such as vehicles which do not require a human driver, can be used to aid in the transport of passengers or items from one location to another. With a typical taxi or car service, a human driver can interact with a passenger to identify himself to that passenger. However, when an autonomous vehicle attempts to pick up a passenger or drop off a delivery, it can be difficult for the user being picked up or retrieving the item to know which autonomous vehicle is assigned to them. This can be exacerbated if there are numerous vehicles being sent to the same location to pick up multiple passengers or items. A passenger may not know how to confirm which vehicle belongs to, or was dispatched to, him or her. As an example, this can also lead to passengers interacting with vehicles which were not assigned to them.
One aspect of the disclosure provides a method. The method includes receiving, by one or more computing devices, a request for a vehicle. This request identifies user information. The method also includes identifying, by the one or more computing devices, a client computing device based on the user information. The one or more computing devices also identify a location of the client computing device. In response to the request the one or more computing devices dispatch a driverless vehicle to the location of the client device. The one or more computing devices generate signaling information based on a set of rules. The set of rules includes first rule that the signaling information does not identify, indirectly or directly, a user and a second rule that the signaling information does not identify, indirectly or directly, the user information. The one or more computing devices send the location of the client computing device and the signaling information to the driverless vehicle for display to the user, and the signaling information to the client computing device for display to the user.
In one example, the request further includes a destination location and the set of rules further includes a third rule that the signaling information does not identify, directly or indirectly, the destination location. In this example, the method also includes providing the driverless vehicle with the destination location. In another example, the set of rules further includes a third rule that the signaling information is unique to the user. In another example, the set of rules further includes a third rule that the signaling information cannot already have been generated for the user previously. In another example, the method also includes using the user information to identify user account information including identifying information of the user, and the set of rules further includes a third rule that the signaling information cannot, directly or indirectly, identify the user account information. In another example, a notification is received by the one or more computing devices from the driverless vehicle that the driverless vehicle has reached a threshold distance or time from the location of the client computing device, and the signaling information is sent to the driverless vehicle only after the notification is received. In this example, the signaling information is sent to the client computing device only after the notification is received. In another example, the set of rules includes a third rule that requires that the unique signal is to expire a specific amount of time after the driverless vehicle is expected to reach the location of the client computing device. In another example, the request is received from a particular client computing device other than the client computing device. In this example, the method also includes sending a request to the client computing device for the location of the client computing device, and identifying the location of the client computing device includes receiving the location of the client computing device in response to the request.
Another aspect of the disclosure provides a system. The system includes an electronic display positioned external to a vehicle and one or more computing devices. The one or more computing devices are configured to receive, from one or more server computing devices, a message with dispatch instructions including a location; maneuver the vehicle to the location; receive, from the one or more server computing devices, signaling information; determine when the vehicle reaches a particular location that is a threshold distance from the location; and after the vehicle reaches the particular location, display the signaling information on the electronic display to identify the vehicle to a user.
In one example, the system also includes the vehicle, and the one or more computing devices are incorporated into the vehicle. In another example, the one or more computing devices are also configured to, when the vehicle reaches the particular location, send a notification to the one or more server computing devices and the signaling information is received in response to the request. In another example, the one or more computing devices are further configured to determine a route to the location, and the threshold distance is a distance in time along the route. In another example, the one or more computing devices are further configured to determine a route to the location, and the threshold distance is a physical distance along the route. In another example, the one or more computing devices are also configured to periodically receive an updated location and use the updated location to update the location such that the particular location is also updated. In another example, the one or more computing devices are also configured to periodically receive an updated location and use the updated location to update the location such that the vehicle is maneuvered to the updated location. In another example, the system also includes the one or more server computing devices. In this example, the one or more server computing devices are configured to receive a request for a vehicle identifying the location and user information; in response to the request, send the message to the one or more computing devices; generate the signaling information based on a set of rules including a first rule that the signaling information does not identify, indirectly or directly, a user and a second rule that the signaling information does not identify, indirectly or directly, the user information; and send the signaling information to the one or more computing devices. In this example, the set of rules also includes a third rule that the signaling information cannot already have been generated for any user previously.
A further aspect of the disclosure provides a non-transitory computer-readable storage medium on which computer readable instructions of a program are stored. The instructions, when executed by one or more processors, cause the one or more processors to perform a method. The method includes, in response to the request, dispatching a driverless vehicle to the location of the client device; generating signaling information based on a set of rules, the set of rules including a first rule that the signaling information does not identify, indirectly or directly, a user and a second rule that the signaling information does not identify, indirectly or directly, the user information; sending the location of the client computing device and the signaling information to the driverless vehicle for display to the user; and sending the signaling information to the client computing device for display to the user.
The technology relates to providing a user with a way to identify or verify a vehicle dispatched to pick up a user or drop off a delivery to the user. For examples the vehicle may be a driverless (autonomous) vehicle, such that a driver would not be available to help the user identify the correct vehicle. In this regard, once the vehicle is within a certain distance of the user, the vehicle may signal to the user in order to identify the vehicle to the user and avoid confusion. This signaling could include a display or audio including a unique string of text.
As noted above, the technology may be applicable in various circumstances. In one instance, a user may use a client device, such as a mobile phone or wearable computing device or system (e.g., head-mounted, wrist, clip-on, etc.), to request a vehicle. The request may be sent to a centralized dispatching system which selects or assigns a vehicle to the requesting user. At the same time, the centralized dispatching system may generate a signal to identify the vehicle to the user. In another instance, the centralized dispatching system may assign a vehicle to a particular user in order to make a delivery. Again, the centralized system may generate a signal to identity the vehicle to the user.
The signal may include a unique, distinct, and/or easily distinguishable string of text or image rather than the user's name, destination, etc. This protects the user's privacy. The signal may also be selected by the user, for example, when setting up an account to use the dispatching service. In some examples, if the user is to be a passenger of the vehicle, the unique string may be an authentication token which expires after some event.
As the vehicle approaches the user's client device, the vehicle's computing device may receive from the centralized dispatching system location information generated by the user's client device. The vehicle's computing device may use this information to maneuver the vehicle to the user's client device as well as to determine a distance or time to reach the user's client device. Once the vehicle is within a certain distance of the user's client device, the vehicle's computing device may display the signal on an external display of the vehicle such that the signal should be visible to the user as the vehicle approaches the user's client device.
For confirmation, the signal may also be provided to the users client device. As an example, the centralized dispatching system may send the signal when the vehicle is dispatched or when the vehicle is within the certain distance or time relative to the user. Thus, rather than simply getting a notification that the user's vehicle is “here,” the user also receives information which may be used to identify the vehicle to the user without compromising the user's privacy.
As shown in
The memory 130 stores information accessible by the one or more processors 120, including instructions 134 and data 132 that may be executed or otherwise used by the processor 120. The memory 130 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 134 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 132 may be retrieved, stored or modified by processor 120 in accordance with the instructions 132. 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 120 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 110 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 150 (e.g., a mouse, keyboard, touch screen and/or microphone) and various electronic displays (e.g., a monitor having a screen, a small LCD touch-screen or any other electrical device that is operable to display information). In this example, the vehicle includes an internal electronic display 152 as well as an external electronic display 154. In this regard, internal electronic display 152 may be located within a cabin of vehicle 100 and may be used by computing device 110 to provide information to passengers within the vehicle 100. External electronic display 154 may be located eternally or mounted on an external surface of the vehicle 100 and may be used by computing device 110 to provide information to potential passengers or other persons outside of vehicle 100.
In one example, computing device 110 may be an autonomous driving computing system incorporated into vehicle 100. The autonomous driving computing system may capable of communicating with various components of the vehicle. For example, returning to
As an example, computing device 110 may interact with deceleration system 160 and acceleration system 162 in order to control the speed of the vehicle. Similarly, steering system 164 may be used by computer 110 in order to control the direction of vehicle 100. For example, if vehicle 100 is 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 166 may be used by computing device 110 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 168 may be used by computing device 110 in order to determine and follow a route to a location. In this regard, the navigation system 168 and/or data 134 may store detailed map information, e.g., highly detailed maps identifying the shape and elevation of roadways, lane lines, intersections, crosswalks, speed limits, traffic signals, buildings, signs, real time traffic information, vegetation, or other such objects and information.
Positioning system 170 may be used by computing device 110 in order to determine the vehicle's relative or absolute position on a map or on the earth. For example, the position system 170 may include a GPS receiver to determine the device's latitude, longitude and/or altitude position. Other location systems such as laser-based localization systems, inertial-aided GPS, or camera-based localization may also be used to identify the location of the vehicle. The location of the vehicle may include an absolute geographical location, such as latitude, longitude, and altitude as well as relative location information, such as location relative to other cars immediately around it which can often be determined with less noise that absolute geographical location.
The positioning system 170 may also include other devices in communication with computing device 110, such as an accelerometer, gyroscope or another direction/speed detection device to determine the direction and speed of the vehicle or changes thereto. By way of example only, an acceleration device may determine its pitch, yaw or roll (or changes thereto) relative to the direction of gravity or a plane perpendicular thereto. The device may also track increases or decreases in speed and the direction of such changes. The device's provision of location and orientation data as set forth herein may be provided automatically to the computing device 110, other computing devices and combinations of the foregoing.
The detection system 172 also includes one or more components for detecting objects external to the vehicle such as other vehicles, obstacles in the roadway, traffic signals, signs, trees, etc. For example, the detection system 170 may include lasers, sonar, radar, cameras or any other detection devices which record data which may be processed by computing device 110. In the case where the vehicle is a small passenger vehicle such as a car, the car may include a laser mounted on the roof or other convenient location.
The computing device 110 may control the direction and speed of the vehicle by controlling various components. By way of example, if the vehicle is operating completely autonomously, computing device 110 may navigate the vehicle to a location using data from the detailed map information and navigation system 168. Computer 110 may use the positioning system 170 to determine the vehicle's location and detection system 172 to detect and respond to objects when needed to reach the location safely. In order to do so, computer 110 may cause the vehicle to accelerate (e.g., by increasing fuel or other energy provided to the engine by acceleration system 162), decelerate (e.g., by decreasing the fuel supplied to the engine or by applying brakes by deceleration system 160), change direction (e.g., by turning the front or rear wheels of vehicle 100 by steering system 164), and signal such changes (e.g. by lighting turn signals of signaling system 166).
Computing device 110 of vehicle 100 may also receive or transfer information to and from other computing devices.
As shown in
The network 240, and intervening nodes, may include 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. 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 210 may include one or more server computing devices that are capable of communicating with computing device 110 of vehicle 100 or a similar computing device of vehicle 100A as well as computing devices 220 and 230 via the network 240. For example, vehicles 100 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 210 may use network 240 to transmit and present information to a user, such as user 222, or 232, on a display, such as displays 224 or 234 of computing devices 220 or 230. In this regard, computing devices 220 and 230 may be considered client computing devices.
As shown in
Although the client computing devices 220 and 230 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 220 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. In another example, client computing device 230 may be a wearable computing system, shown as a head-mounted computing system in
Storage system 250 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 210, 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 250 may also store a set of rules for generating the unique signals. As an example, one rule may require that the unique signal generated for a given user cannot identify, directly or indirectly, the user by name or any of the user's other account information such as the user's contact information or identifying information of the user's client computing device (or devices)). For example, if the user's name is “Robert,” such as rule would require that unique signal cannot include “robert”, as an example of a direct reference to the user's name. Similarly, as an example of an indirect reference to the user's name, variations or portions of the name “robert” such as “bob”, “bobby”, “bert”, “obe”, etc. as well as cyphers, codes or information generated using for “Robert” or any variation or portion of “Robert.”
Another rule may require that the unique signal cannot identify, directly or indirectly, a prior or current location of the user or rather, the user's client computing device. And, if the user is to be transported to a particular destination location, the rules may require that the unique signal cannot identify, directly or indirectly, that particular destination location. For instance, a location may be identified directly by an address, geographic coordinates, a name of a point of interest, etc. A location may be identified indirectly, by reference to an image of the location, an image of an object at or near that location, an image of an activity at that location, by reference to another location proximate to the location, a general description of the location (the building next to Bob's house), or any other cypher or code that could be used to identify the location.
A further rule may also require that the signal actually be unique. For example, this may mean that it cannot already have been generated for another user or for the given user previously. As another example rule, the unique signal cannot be used for another user within a certain geographical area (e.g. the same city, state, within 50 miles, etc.), for instance the same unique signal cannot be used for two users within the same state. In another example rule, the same unique signal cannot be used again within a certain period of time (e.g. a day, a month, a year, etc.) Similarly, combination of these time and geographic rules may also be used. For instance, the same unique signal may not be used for users in the same state unless there is at least 1 month between uses. In this regard, if these geographical area and/or time rules would not apply, then a unique signal may be reused or recycled for another user or even the same user.
The storage system 250 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.
As with memory 130, storage system 250 can be of any type of computerized storage capable of storing information accessible by the server computing devices 210, such as a hard-drive, memory card, ROM, RAM, DVD, CD-ROM, write-capable, and read-only memories. In addition, storage system 250 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 250 may be connected to the computing devices via the network 240 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 222 and 232 may download the application to client computing devices 220 and 230. The client computing device may then transmit a request for the application over the network, for example, to one or more server computing devices 210, and in response, receive the application. The application may be installed locally at the client computing device.
As part of an initial set up of the application, the user may be assigned or provide credentials for using the application. For example, a user may select a username and password. In some instances, a user may select, identify, or be asked to confirm a unique signal to represent the user. The unique signal may be generated by the one or more server computing devices 210 as described in more detail below. This information may be sent to one or more server computing devices 210 and stored as part of the user account information of storage system 150. In addition, the user may grant the application permission to send the location of the user's client computing device as needed in order to provide vehicle dispatching services to the user.
Once the application is installed and setup, the user may request a vehicle. As an example, a user such as user 232 may use client computing device 230 to send a request to one or more server computing devices 210 for a vehicle to deliver an item to another user, such as user 222, at the user's current location. In this regard, the request may identify the user 222, and not any location information for user 222. In response, the one or more server computing devices 210 may communicate with client computing device 220 in order to determine the current location of client computing device 220, assumed to be the current location of user 222. Alternatively, user 222 may request a vehicle to transport that user to a particular destination location, and the location of client computing device 220 may be sent to the one or more server computing devices 210 as part of the request.
In response to receiving a request, the one or more server computing devices may select a vehicle to be dispatched based upon the location of the client computing device. In order to do so, the one or more server computing devices 210 may identify vehicles that are available to be dispatched, such as any vehicles of the fleet that are not currently being used to transport a user or item. The one or more server computing devices may then use the routing information of storage system 250 to determine which of the available vehicles is closest to the location of the client computing device. The one or more server computing devices may dispatch the closest available vehicle, or rather, send instructions to the computing device of the closest available vehicle to go to the location of the client computing device. If the user is to be transported to another location, the one or more server computing devices may also identify the particular destination location to the closest available vehicle.
Once the request has been received, the one or more server computing devices may also generate a unique signal according to a set of rules. For example, the set of rules may correspond to the set of rules discussed above with regard to storage system 250. Thus, one or more computing devices 210 may use that set of rules to generate a unique signal. This unique signal may include a unique string of text or alphanumeric characters or an image such as an icon or photograph. In some examples, the unique signal may include a series of nonsensical letters (e.g. they do not form a word), a sequence of colors, a barcode, etc. In this regard, for any combination of the above, the set of choices would be large enough so that the unique signal would not repeat for a given user or trip location such that it would be difficult to impossible to understand the trip patterns for a particular user (e.g. 59007, FLADSOR or the blue boat icon). The unique signals may also be generated using a random number generator. Again, as noted above, the unique signal may also be generated as part of an initial set up of the application.
The unique signal may also be sent to the user's client computing device as part of a confirmation that a vehicle has been dispatched to that user. For example, the one or more server computing devices may send the unique signal to the client computing device of the user when the vehicle is dispatched or when the vehicle is within some threshold distance (or time) to the user. If the request originated by another user, the one or more server computing devices can optionally not send the unique signal to the another user in order to further protect the privacy of the user to which the vehicle was dispatched.
Once the vehicle is dispatched, the vehicle's computing device may control the vehicle in order to reach the location of the user provided by the one or more server computing devices. The vehicle's computing device may communicate with the vehicle's navigation system in order to identify a route to the location of the user. The one or more server computing devices may also send updated location information should the location of the client computing device change before the vehicle has reached the location.
As the computing device controls and guides the vehicle to the location of the user, the computing device may continuously estimate its distance from the user in order to determine when the vehicle has reached a threshold distance to the user. This threshold distance may be determined, for example, as a duration in time (e.g., there are 2 minutes or more or less left along the route to reach the location of the user). Alternatively, the distance threshold may be a physical distance such as 50 meters, 0.2 miles, 2 city blocks, or more or less, directly between the vehicle and the user (e.g., a straight line) or along the route until the vehicle reaches the location of the user or a distance. Returning to the example of
Once the vehicle's computing device determines that the vehicle has reached the threshold distance or time, the vehicle may display the unique signal. For example, as discussed above, the unique signal may be displayed in an external electronic display of the vehicle. In order to further protect the user's privacy, if there are multiple external displays of the vehicle, the unique signal may be displayed only on those displays that are likely to be visible for example using a line-of-sight to the location of the user's client computing device. Alternatively, to further protect the privacy of the user, once the vehicle reaches the threshold distance or time, the vehicle's computing device may request the unique signal from the one or more server computing devices. In response, the one or more server computing devices may provide the unique signal to the vehicle, and the vehicle, in turn, may display the unique signal.
When the vehicle reaches the location point 702, the computer 110 may display a unique signal on a display such as an external electronic display 154, if a unique signal has been received from the one or more server computing devices. Alternatively, when the vehicle reaches location point 702, the vehicle send a notification of the same to the one or more server computing devices 210 and receive a unique signal in response. The received unique signal may then be displayed on the electronic display.
Flow diagram 1000 of
In response to the request, a driverless vehicle is dispatched to the location of the client device at block 1008. In addition, signaling information is generated based on a set of rules at block 1010. For example, this set of rules may include the rules discussed above with regard to the storage system 250. The location of the client computing device and the signaling information is sent to the driverless vehicle for display, for example, to a user at block 1012. The signaling information is also sent to the client computing device for display, for example to the user at block 1014.
Accordingly, rather than simply getting a notification that the user's vehicle is “here,” the user also receives also information which may be used to identify the vehicle to the user without compromising the user's privacy. Thus, as the vehicle approaches the user, the user is able to quickly and easily identify that the vehicle has been dispatched to the user (or rather, the user's client computing device) by comparing the unique signal received on the client computing device (or assigned as part of the initial set up for the application) to the unique signal displayed on the electronic display of the vehicle. In addition, the likelihood of confusion of other users or persons is very small given the fact that the displayed unique signal is unique to the user.
In some instances, the unique signal may also be used to authenticate the user to the vehicle, or rather so that the vehicle can confirm that it has reached the correct user. In such an example, the unique signal may be an authentication token that will expire a short amount of time after the vehicle is expected to reach the location of the user. In another example, the authentication token can expire once the user (or user's client computing device) is located within the vehicle, as confirmed by communication between the client computing device and the vehicle's computing device, or when the user interacts with an in-vehicle interface such as the internal electronic display 152. The functionality of such a token may be determined by the one or more server computing devices when generating the unique signal in response to a request to dispatch a vehicle as described above. In this regard, a further rule of the set of rules of storage system 250 may require that the unique signal expire a fixed period of time after a dispatched vehicle is expected to reach the location of the user.
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. 17/034,784, filed Sep. 28, 2020, which is a continuation of U.S. patent application Ser. No. 16/504,784, filed Jul. 8, 2019, now issued as U.S. Pat. No. 10,821,887, which is a continuation of U.S. patent application Ser. No. 15/633,073, filed Jun. 26, 2017, now issued as U.S. Pat. No. 10,384,597, which is a continuation of U.S. patent application Ser. No. 15/084,568, filed Mar. 30, 2016, now issued as U.S. Pat. No. 10,272,827, which is a continuation of U.S. patent application Ser. No. 14/244,404, filed Apr. 3, 2014, now issued as U.S. Pat. No. 9,494,938, the disclosures of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4876812 | Haralson | Oct 1989 | A |
6356838 | Paul | Mar 2002 | B1 |
6414635 | Stewart et al. | Jul 2002 | B1 |
6545601 | Monroe | Apr 2003 | B1 |
6812851 | Dukach et al. | Nov 2004 | B1 |
7840427 | O'Sullivan | Nov 2010 | B2 |
7920071 | Baillot | Apr 2011 | B2 |
8346426 | Szybalski et al. | Jan 2013 | B1 |
9020533 | Mangiardi et al. | Apr 2015 | B1 |
9343002 | Hagemann et al. | May 2016 | B2 |
9429947 | Wengreen | Aug 2016 | B1 |
9436180 | Fredinburg et al. | Sep 2016 | B1 |
9547307 | Cullinane et al. | Jan 2017 | B1 |
9551992 | Barton-Sweeney et al. | Jan 2017 | B1 |
9733096 | Colijn et al. | Aug 2017 | B2 |
10384597 | Kemler et al. | Aug 2019 | B1 |
20020028002 | Whited | Mar 2002 | A1 |
20020038181 | Okude et al. | Mar 2002 | A1 |
20020058517 | Furukawa et al. | May 2002 | A1 |
20020075201 | Sauer et al. | Jun 2002 | A1 |
20020183920 | Smith et al. | Dec 2002 | A1 |
20030125845 | Carlstedt et al. | Jul 2003 | A1 |
20030222794 | Mal | Dec 2003 | A1 |
20040076280 | Ando et al. | Apr 2004 | A1 |
20040102898 | Yokota et al. | May 2004 | A1 |
20040128065 | Taylor et al. | Jul 2004 | A1 |
20050018066 | Hofer | Jan 2005 | A1 |
20050104745 | Bachelder et al. | May 2005 | A1 |
20050114014 | Issac | May 2005 | A1 |
20050153707 | Ledyard et al. | Jul 2005 | A1 |
20050225636 | Maemura et al. | Oct 2005 | A1 |
20050231419 | Mitchell | Oct 2005 | A1 |
20070197231 | Lin | Aug 2007 | A1 |
20070279521 | Cohen | Dec 2007 | A1 |
20080270204 | Poykko et al. | Oct 2008 | A1 |
20080275645 | Hoshino | Nov 2008 | A1 |
20090156241 | Staffaroni et al. | Jun 2009 | A1 |
20090192851 | Bishop | Jul 2009 | A1 |
20090234573 | Notarantonio | Sep 2009 | A1 |
20090326991 | Wei et al. | Dec 2009 | A1 |
20100194596 | Wang et al. | Aug 2010 | A1 |
20100228574 | Mundinger et al. | Sep 2010 | A1 |
20100241349 | Wu | Sep 2010 | A1 |
20100265048 | Lu et al. | Oct 2010 | A1 |
20100293030 | Wu | Nov 2010 | A1 |
20100332133 | Harris et al. | Dec 2010 | A1 |
20110050463 | Yu et al. | Mar 2011 | A1 |
20110053642 | Lee | Mar 2011 | A1 |
20110059693 | Osullivan | Mar 2011 | A1 |
20110068954 | Mcquade et al. | Mar 2011 | A1 |
20110099040 | Felt et al. | Apr 2011 | A1 |
20110216200 | Chung et al. | Sep 2011 | A1 |
20110313594 | Kato et al. | Dec 2011 | A1 |
20110313880 | Paul et al. | Dec 2011 | A1 |
20120041675 | Juliver et al. | Feb 2012 | A1 |
20120109694 | Lee et al. | May 2012 | A1 |
20120130627 | Islam | May 2012 | A1 |
20120137256 | Lalancette | May 2012 | A1 |
20120154591 | Baur et al. | Jun 2012 | A1 |
20120191269 | Chen et al. | Jul 2012 | A1 |
20120277952 | Macneille | Nov 2012 | A1 |
20120290979 | Devecka | Nov 2012 | A1 |
20130046456 | Scofield et al. | Feb 2013 | A1 |
20130074383 | Hagemann et al. | Mar 2013 | A1 |
20130144660 | Martin | Jun 2013 | A1 |
20130149998 | Yi et al. | Jun 2013 | A1 |
20130204463 | Chiappetta | Aug 2013 | A1 |
20130211916 | Putman | Aug 2013 | A1 |
20130218647 | Kroll et al. | Aug 2013 | A1 |
20130286206 | Ozaki et al. | Oct 2013 | A1 |
20130289858 | Mangiat et al. | Oct 2013 | A1 |
20140051465 | Ruys et al. | Feb 2014 | A1 |
20140172727 | Abhyanker et al. | Jun 2014 | A1 |
20140200739 | Kirsch | Jul 2014 | A1 |
20140300449 | Kounavis | Oct 2014 | A1 |
20140365250 | Ikeda et al. | Dec 2014 | A1 |
20150032328 | Healey et al. | Jan 2015 | A1 |
20150081362 | Chadwick et al. | Mar 2015 | A1 |
20150142484 | Huang et al. | May 2015 | A1 |
20150154810 | Tew et al. | Jun 2015 | A1 |
20150161554 | Sweeney et al. | Jun 2015 | A1 |
20150175072 | Sabeti | Jun 2015 | A1 |
20150199619 | Ichinose et al. | Jul 2015 | A1 |
20150220791 | Wu et al. | Aug 2015 | A1 |
20150302342 | Yeh | Oct 2015 | A1 |
20150338849 | Nemec et al. | Nov 2015 | A1 |
20150339923 | König et al. | Nov 2015 | A1 |
20150346727 | Ramanujam | Dec 2015 | A1 |
20160021154 | Schoeffler | Jan 2016 | A1 |
20160161266 | Crawford et al. | Jun 2016 | A1 |
20170153714 | Gao et al. | Jun 2017 | A1 |
20170286884 | Shoval et al. | Oct 2017 | A1 |
Entry |
---|
“International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/031780, mailed on Jul. 16, 2018”, 15 pages. |
Bose , et al., “Autonomously Controlled Storage Management in Vehicle Logistics—Applications of RFID and Mobile Computing Systems”, International Journal of RF Technologies: Research and Applications, iFirst Article, 2008, pp. 1-20. |
Brownell, Christopher Kirlin, “Shared Autonomous Taxi Networks: An Analysis of Transportation Demand in NJ and a 21st Century Solution for Congestion”, Submitted in partial fulfillment of the requirements for the degree of Bachelor of Science and Engineering, Princeton University, Apr. 15, 2013, 122 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 17034784 | Sep 2020 | US |
Child | 18079924 | US | |
Parent | 16504784 | Jul 2019 | US |
Child | 17034784 | US | |
Parent | 15633073 | Jun 2017 | US |
Child | 16504784 | US | |
Parent | 15084568 | Mar 2016 | US |
Child | 15633073 | US | |
Parent | 14244404 | Apr 2014 | US |
Child | 15084568 | US |